| 00:04.57 | *** join/#htc-linux jonpry (~jon@adsl-98-85-69-254.mco.bellsouth.net) |
| 00:13.04 | *** join/#htc-linux Rajko (~rajkosto@de.iandoh.info) |
| 00:53.26 | *** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring) |
| 01:07.20 | *** join/#htc-linux mitsutaka (~mitsutaka@219.143.36.82) |
| 01:23.26 | detule | so jonpry er we can forcefully release that wifi wakelock on earlysuspend but I am not sure we are supposed to.... |
| 01:24.22 | jonpry | might need a wow capable driver |
| 01:25.18 | jonpry | i suspect something is terribly wrong is suspend pc since the only >16 hour report was without suspend |
| 01:25.43 | detule | rpierce99 needs to verify but that's without mobile data |
| 01:26.17 | detule | i think everyone that's tried turning mobile data off has reported drastic improvements in battery life |
| 01:27.22 | jonpry | i need to hookup the meter and check this stuff |
| 01:27.51 | jonpry | in theory you can use scbs to calculate the suspend power consumption |
| 01:29.27 | jonpry | hopefully i will have some time come may 1st. absolutely destroyed right now between work and boat |
| 01:29.40 | detule | scbs might just be safe to use now with the new timer and no idle pc |
| 01:29.56 | detule | can you get away with rtc alarms? |
| 01:29.59 | ahigerd | What's scbs? |
| 01:30.10 | jonpry | rtc alarm is how it works |
| 01:30.23 | detule | oh |
| 01:30.26 | jonpry | modified slightly so it can do it all without enabling irq's |
| 01:30.41 | detule | rtc irq is already wake enabled |
| 01:30.51 | detule | (as of recently) |
| 01:31.05 | detule | just seeing if you can get away without any timer.c additions |
| 01:31.11 | jonpry | it has to be for android alarm to work |
| 01:31.40 | jonpry | nothing changes in timer.c i just added some stuff to rtc-7x01 so we can override android alarms |
| 01:32.08 | detule | there's pretty much no more android alarms, we are using almost stock kernel alarmtimer.c |
| 01:33.26 | detule | android just has a userland ioctl interface on top of that |
| 01:33.30 | jonpry | might be able to use some kernel api. but i think its easier to just hook directly into the rtc |
| 01:34.14 | detule | so er https://gitorious.org/linux-msm-rhod/linux-msm-rhod/commit/3108d73907a69ee6206e039a5e00a4bd235ba944 no longer needed? |
| 01:36.20 | detule | though never figured out what was causing issues that looks harmless |
| 01:36.46 | jonpry | it may need that |
| 01:37.03 | jonpry | although i'm not sure why tbh |
| 01:38.05 | jonpry | in theory we can just calculate the time by assuming the measurement is scheduled properly |
| 01:38.22 | jonpry | its clock doesn't even need to have any correlation with the wall clock |
| 01:39.30 | ahigerd | Does it need to synchronize to ANYTHING? Because soft clocks will drift with CPU temp >.> |
| 01:39.42 | detule | anyway alarm_start in kernel/time/alarmtimer.c seems like a winner to me |
| 01:40.03 | ahigerd | ran into that one with an embedded board once |
| 01:40.06 | detule | (that's what android calls to set wake-up alarms) |
| 01:41.07 | jonpry | i dunno using kernel api's is rough. the quickwakup stuff leaves almost everything undone. irq's never get enabled, kernel is not really entered |
| 01:41.40 | ahigerd | It was weird -- normally the kernel clock keeps more reliable time than the RTC, and the RTC is just supposed to be used to track time when the power is off... but on this board, the kernel clock drifted like CRAZY (minutes per day) while the RTC was as stable as my wristwatch |
| 01:41.49 | detule | yeah there's that i wonder why android never mainlined quickwakeup in their trees |
| 01:42.21 | jonpry | maybe they don't have a use for it. motorola is using it for something |
| 01:43.02 | detule | if it does work it seems like it would come in handy |
| 01:43.05 | jonpry | rtc is run by a watch crystal :p |
| 01:43.16 | jonpry | it totally works |
| 01:44.40 | detule | could be that kernel api could still work with quickwakeup |
| 01:45.11 | jonpry | some embedded boards use rc oscillators on the processor which causes all sorts of trouble. modern fancy pmic things actually will sync the high speed pll's to the 32khz somehow |
| 01:45.38 | detule | gtg |
| 01:51.04 | jonpry | ahigerd, scbs is a new battery meter thing i wrote |
| 01:51.22 | ahigerd | Ah |
| 01:51.35 | ahigerd | What's it do? |
| 01:51.53 | jonpry | there are several parts |
| 01:52.43 | jonpry | there is a bunch of kernel stuff that facilitates taking measurements of the things we can measure. like battery voltage and current. at regular intervals even when the phone is sleeping |
| 01:53.02 | jonpry | and this gets downloaded to a userspace program that analyzes it |
| 01:53.54 | rpierce99 | i'm here, something i can help with? |
| 01:54.02 | jonpry | after generating enough data, there is an app that allows you to analyze the data to find the electrical parameters of your battery assuming some simplified model |
| 01:54.14 | rpierce99 | btw i never get a green light with wifi on, but you knew that :) |
| 01:54.23 | jonpry | yeah we figured |
| 01:54.32 | jonpry | can you reproduce the 51 hours? |
| 01:54.54 | rpierce99 | it's fully charged now, i'll disconnect it and see what happens |
| 01:55.24 | jonpry | i guess try again. and then with wifi off? i think it will not last as long |
| 01:55.49 | rpierce99 | ok see you in like 4 days :) |
| 01:56.02 | ahigerd | 51 hours is barely more than two :P |
| 01:56.37 | rpierce99 | 51 + the second time without wifi which will probably be 20+ since data is off |
| 01:56.56 | jonpry | nice to see your on the bandwagon |
| 01:57.33 | rpierce99 | i couldn't stay away |
| 01:57.47 | jonpry | new post on xda says "turning on wifi doubles battery life" |
| 01:58.02 | rpierce99 | i'm killing my $22/mo vonage bill in favor of $10/qtr tmo prepaid for watching caller id and then returning the call on my cell |
| 01:58.09 | rpierce99 | basically i'm paying to hold onto the phone number |
| 01:58.39 | jonpry | google voice? |
| 01:59.23 | rpierce99 | can't transfer vonage to GV without going through cell first |
| 01:59.34 | rpierce99 | so once it's on tmo i could, but then i'd have to pay money to do that also |
| 01:59.53 | rpierce99 | as it is i'm OOP $2.31 and my number is safe until july |
| 02:00.14 | jonpry | sounds pretty good |
| 02:00.23 | jonpry | and we get another rhod user |
| 02:00.31 | ahigerd | :D |
| 02:00.38 | rpierce99 | so now we have 3 |
| 02:01.04 | jonpry | arrrghhh just needs to throw that icrap away |
| 02:01.25 | ahigerd | I'll take it off his hands ;) |
| 02:01.33 | ahigerd | could use an iOS smartphone for dev |
| 02:01.53 | ahigerd | Even though I can't get more than EDGE with it on T-Mobile :( |
| 02:02.49 | rpierce99 | arrrghhh has 3 :) |
| 02:02.59 | rpierce99 | oh you meant iCrap |
| 02:04.09 | jonpry | 3 rhods? |
| 02:04.11 | ahigerd | I mean, I have an iPod Touch, which is almost good enough, but I need to test my software when it's not on the LAN |
| 02:04.23 | rpierce99 | i think it's 2 rhods and a raph, i can never remember |
| 02:04.52 | rpierce99 | not all functional, from what i understand |
| 02:05.07 | jonpry | like detules keyboard? |
| 02:05.23 | rpierce99 | he said one of them doesn't boot anymore since he played with nand on it :) |
| 02:05.50 | jonpry | my phone is actually 100% except for the usb connector. and i have been doing horrible things to it for over 2 years now |
| 02:07.14 | jonpry | you guys hear about tupac being a cylon? |
| 02:07.19 | rpierce99 | i never knew how nicely i took care of phones until i saw my coworkers phones, we got them at the same time and his is trashed |
| 02:07.26 | rpierce99 | scratches and chips everywhere |
| 02:08.08 | jonpry | i've got some serious scratched and this strange film on 210 is peeling off |
| 02:11.16 | ahigerd | I put an InvisiShield on my 210. :P |
| 02:11.19 | rpierce99 | you should really take off the protective film from the factory when you get it, the phone looks much nicer that way |
| 02:11.22 | ahigerd | And I've replaced the battery hatch |
| 02:12.04 | rpierce99 | i haven't used one of those since my htc fuze, it was a complete PITA to put on and even worse to take off |
| 02:12.05 | ahigerd | I gotta say, the InvisiShield makes the screen NICE |
| 02:12.17 | ahigerd | Oh, I paid the $15 to have Best Buy put the thing on for me :P |
| 02:12.26 | ahigerd | Totally worth it |
| 02:12.34 | rpierce99 | <3 Best Buy ;) |
| 02:12.42 | ahigerd | Looks beautiful, easy to keep clean, and the texture is nice for both finger and stylus |
| 02:12.55 | ahigerd | Feels a lot better than the bare screen |
| 02:13.24 | ahigerd | Especially since this is a resistive; I don't feel scared I'm putting too much pressure on |
| 02:14.50 | jonpry | yeah i just scratch it up. when i wear through the screen it will be time for a new phone and it this rate it may actually take a decade |
| 02:15.32 | ahigerd | This thing is bloody invulnerable. XD I saw someone pull out a key ring and whip it over his own phone's screen and not leave a mark |
| 02:16.02 | ahigerd | I mean, I knew these things were tough but I assumed they were ablative and you'd eventually replace them. Nope. |
| 02:18.07 | jonpry | isn't the real screen made of even tougher stuff? |
| 02:18.26 | rpierce99 | harder yes, scratch resistant no |
| 02:18.54 | ahigerd | On a resistive I'm not even confident on the "harder" |
| 02:18.58 | jonpry | isn't that the same thing? |
| 02:19.01 | ahigerd | No way |
| 02:19.15 | ahigerd | Well |
| 02:19.20 | ahigerd | I suppose by a precise definition yes |
| 02:20.33 | ahigerd | The real screen is made of more rigid, more impact-resistant stuff, but the surface isn't hard enough to be immune to scratching |
| 02:20.44 | jonpry | at some point i found the datasheet for the rhod touchscreen. some 3m contraption. looked pretty impressive mohs 7 or something |
| 02:21.30 | ahigerd | The InvisiShield goes the opposite route, being INTENTIONALLY non-hard so that it deforms smoothly instead of resisting the pressure and only deforming in the immediate spot |
| 02:21.34 | ahigerd | Distributes the force |
| 02:22.28 | jonpry | sounds like you may have been taken over by some marketing material |
| 02:22.30 | ahigerd | Nope |
| 02:22.36 | ahigerd | I made that up on the spot based on what I know about it |
| 02:22.42 | ahigerd | The marketing material just says it's scratchproof :P |
| 02:22.50 | rpierce99 | http://www.youtube.com/watch?v=bJH3xZ5ZDwE&feature=relmfu |
| 02:23.12 | ahigerd | I just happen to be good at market-spin ^^() |
| 02:24.19 | ahigerd | So technically that's a GUESS based on my own knowledge of materials physics |
| 02:24.27 | *** join/#htc-linux swc|666 (~goldbond@Aircrack-NG/Friend) |
| 02:24.33 | jonpry | any material that is softer will "distribute the force" but this doesn't really stop scratching/cutting by harder materials |
| 02:24.40 | ahigerd | Cutting is still possible |
| 02:24.48 | ahigerd | If you actually take a blade to it, you can cut it |
| 02:25.00 | jonpry | scratching is just impromptu cutting |
| 02:25.02 | ahigerd | I accidentally put a fingernail hole in the screen protector on my iPad when testing it |
| 02:29.50 | ahigerd | Anyway |
| 02:30.57 | ahigerd | Hardness is only part of the picture; it's an incomplete (and relative) measurement. The REAL physics are plastic vs. elastic deformation vs. shear. Cutting is exceeding the material's shear threshold. Scratching is exceeding the material's elastic deformation range and causing a plastic deformation. |
| 02:33.00 | ahigerd | Being hard means the material resists deformation, but it also means that when it DOES deform it becomes plastic much sooner (or if it's hard enough the force makes it break before it causes it to deform). |
| 02:33.11 | ahigerd | ... and he peered out. whoops |
| 02:36.51 | ahigerd | Okay, well, off to bed |
| 02:36.59 | ahigerd | jonpry, if you do review the logs when you come back, ^ |
| 02:45.10 | *** join/#htc-linux jonpry (~jon@adsl-98-85-69-254.mco.bellsouth.net) |
| 02:45.43 | *** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring) |
| 02:47.21 | *** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring) |
| 02:54.34 | *** join/#htc-linux Bry8Star (~Bry8Star@gateway/tor-sasl/bry8star) |
| 03:02.57 | detule | there's also this mpannen fela on xda who's compiling his own 3.3 i guess that bumps the rhod gbx count to 5 |
| 03:03.04 | detule | (counting you as well jonpry ) |
| 03:07.53 | jonpry | i was trying to figure out the problem with unaligned accesses in tssc |
| 03:09.20 | detule | that would be nice |
| 03:10.00 | detule | emwe once suggested some patch |
| 03:10.03 | jonpry | but i don't see any |
| 03:10.11 | detule | to use with the new toolchain |
| 03:10.20 | detule | but i got the same touch screen behavior with the patch |
| 03:10.32 | jonpry | unless we use tp_calibration_read() somewhere |
| 03:11.36 | detule | this is what he suggested http://dl.dropbox.com/u/12183048/htctopaz/dot35/patches/0001-defconfig-disable-sw-alignment-trap-with-codesourcer.patch |
| 03:12.46 | jonpry | i just want to change the code that is doing the unaligned access |
| 03:14.02 | detule | power to you if you can figure out where it is |
| 03:18.13 | jonpry | are long's 64bit? |
| 03:20.25 | detule | what's long long then |
| 03:21.15 | detule | long long being the largest bit container i know |
| 03:25.57 | jonpry | i think the problem is in msm_tssc.h |
| 03:28.55 | detule | so sorry to be dense about this, this scbs_do that gets executed in if (collapsed) -> doesn't that execute _after_ a11 wakes up? |
| 03:32.53 | jonpry | the superquick thing? |
| 03:33.49 | detule | trying to figure out where's the trigger that starts the polling in suspend |
| 03:35.43 | detule | oh ok that's fine that it executes after power collapse |
| 03:36.52 | jonpry | i think userland turns on rtc alarm when powermanager expires |
| 03:37.22 | jonpry | and scbs has already set the rtc to wake up in 5 seconds max or whatever |
| 03:40.03 | *** join/#htc-linux swc|666 (~goldbond@Aircrack-NG/Friend) |
| 03:42.39 | jonpry | i think if all these unsigned longsamples_avg_1: 16; |
| 03:42.39 | jonpry | unsigned longsamples_avg_2: 16; |
| 03:43.05 | jonpry | get changed to just unsigned short avg_1, avg_2 it will work |
| 04:54.36 | *** join/#htc-linux ALoGeNo (~alogeno@unaffiliated/alogeno) |
| 05:18.02 | *** join/#htc-linux ccxCZ (~ccxCZ@new.webprojekty.cz) |
| 05:22.29 | *** join/#htc-linux bitrot (~rajkosto@de.iandoh.info) |
| 05:37.58 | *** join/#htc-linux rajkosto (~rajkosto@de.iandoh.info) |
| 05:53.40 | *** join/#htc-linux kiozen (~kiozen@p578a42db.dip0.t-ipconnect.de) |
| 05:57.00 | *** join/#htc-linux Bry8Star (~Bry8Star@gateway/tor-sasl/bry8star) |
| 06:30.29 | *** join/#htc-linux Dinde (kayser@sur-internet.net) |
| 06:40.52 | *** join/#htc-linux Alex[sp3dev] (~alexander@media.it.hse.ru) |
| 06:54.19 | *** join/#htc-linux MethoS (~clemens@134.102.106.250) |
| 07:01.47 | *** join/#htc-linux MacDrunk (~marper@201.165.128.158) |
| 07:04.06 | *** part/#htc-linux MacDrunk (~marper@201.165.128.158) |
| 08:18.48 | *** join/#htc-linux gauner1986 (~Miranda@ip-109-91-241-106.unitymediagroup.de) |
| 08:37.04 | *** join/#htc-linux infernix (nix@unaffiliated/infernix) |
| 08:41.44 | *** join/#htc-linux BeVeR (~bever@h90222.upc-h.chello.nl) |
| 08:44.45 | *** part/#htc-linux BeVeR (~bever@h90222.upc-h.chello.nl) |
| 08:48.15 | hyc | long is only 32 bit on arm |
| 08:48.31 | hyc | didn't know long long was supported. that would be 64 |
| 09:00.01 | *** join/#htc-linux phh (~quassel@137.194.15.151) |
| 09:42.40 | *** join/#htc-linux Alex[sp3dev] (~alexander@media.it.hse.ru) |
| 10:21.59 | *** join/#htc-linux gauner1986 (~Miranda@ip-109-91-241-106.unitymediagroup.de) |
| 10:51.20 | *** join/#htc-linux zeusk (77eb360e@gateway/web/freenode/ip.119.235.54.14) |
| 10:55.38 | *** join/#htc-linux ImCoKeMaN (~imcokeman@pool-98-111-113-96.hrbgpa.fios.verizon.net) |
| 11:12.15 | *** join/#htc-linux paulk-desktop (~paulk@lib33-1-82-233-88-171.fbx.proxad.net) |
| 11:49.55 | *** join/#htc-linux helicopter88 (~helicopte@host39-114-dynamic.10-87-r.retail.telecomitalia.it) |
| 13:38.14 | *** join/#htc-linux rpierce99 (~rpierce99@96-42-107-19.dhcp.stcd.mn.charter.com) |
| 13:39.11 | *** join/#htc-linux detule (~detule@unaffiliated/d3tul3) |
| 14:12.28 | *** part/#htc-linux ali1234 (~ajbuxton@s15821883.onlinehome-server.info) |
| 14:30.29 | *** join/#htc-linux jun__ (ca5b311c@gateway/web/freenode/ip.202.91.49.28) |
| 14:30.57 | *** part/#htc-linux jun__ (ca5b311c@gateway/web/freenode/ip.202.91.49.28) |
| 14:48.29 | *** join/#htc-linux mitsutaka (~mitsutaka@221.219.116.16) |
| 15:09.18 | *** join/#htc-linux ahigerd (~ahigerd@173.218.156.102) |
| 15:09.18 | *** join/#htc-linux ahigerd (~ahigerd@libqxt/developer/ahigerd) |
| 15:10.19 | *** join/#htc-linux ahigerd1 (~ahigerd@173.218.156.102) |
| 15:27.50 | *** join/#htc-linux DuperMan (~Duper@46-116-36-66.bb.netvision.net.il) |
| 15:32.03 | *** join/#htc-linux kiozen (~kiozen@p578a42db.dip0.t-ipconnect.de) |
| 16:01.02 | *** join/#htc-linux rob_w (~bob@ppp-88-217-92-106.dynamic.mnet-online.de) |
| 16:01.02 | *** join/#htc-linux rob_w (~bob@unaffiliated/rob-w/x-1112029) |
| 16:23.14 | *** join/#htc-linux LordDeath (~LordDeath@cable-81-173-164-174.netcologne.de) |
| 16:32.15 | *** join/#htc-linux mgross029 (c0234f46@gateway/web/freenode/ip.192.35.79.70) |
| 16:34.54 | zeusk | FUUUUUUUUUUUUUUUUUUUUUUUUUUUUU SPENT 2 hours debugging lk to finally find out heap was being put at a wrong static address >_> |
| 17:04.32 | *** join/#htc-linux Alex[sp3dev] (~alexander@85.202.228.18) |
| 17:08.23 | *** join/#htc-linux mes_ (~mes@sentry.lazo.ca) |
| 17:50.51 | *** join/#htc-linux kiozen (~kiozen@ppp-93-104-64-132.dynamic.mnet-online.de) |
| 18:29.03 | *** join/#htc-linux DuperMan (~Duper@46-116-36-66.bb.netvision.net.il) |
| 18:53.46 | *** join/#htc-linux swc|666 (~goldbond@Aircrack-NG/Friend) |
| 19:00.06 | *** join/#htc-linux kiozen (~kiozen@ppp-93-104-64-132.dynamic.mnet-online.de) |
| 19:04.41 | *** join/#htc-linux detule (~detule@unaffiliated/d3tul3) |
| 19:25.42 | *** join/#htc-linux kiozen (~kiozen@ppp-93-104-64-132.dynamic.mnet-online.de) |
| 20:01.18 | *** join/#htc-linux ahigerd (~ahigerd@173.218.156.102) |
| 20:01.18 | *** join/#htc-linux ahigerd (~ahigerd@libqxt/developer/ahigerd) |
| 20:01.31 | *** join/#htc-linux detule (~detule@unaffiliated/d3tul3) |
| 20:05.44 | *** join/#htc-linux wwwrun (wwwrun@unaffiliated/wwwrun) |
| 20:05.48 | *** part/#htc-linux wwwrun (wwwrun@unaffiliated/wwwrun) |
| 20:08.03 | CptAJ | detule, tell me about that fancy smd of yours |
| 20:09.35 | detule | CptAJ, reboot free? |
| 20:09.57 | CptAJ | yeah, it lasted quite a while yestarday and is doing the same today |
| 20:10.03 | CptAJ | no crashes at all |
| 20:12.26 | detule | alright, i guess it's not surprising the shared memory driver code in .27 i guess dates back to when google people were writing msm specific code ... and google code is usually pretty crappy imo...not to mention that at this point years old |
| 20:12.52 | CptAJ | AND never tested on this device |
| 20:13.07 | detule | that too, though the problems i think are generic |
| 20:13.32 | detule | so you can do one of two things -> one port the patches from 3.3 |
| 20:14.03 | detule | this shouldn't be too hard since .27 and 3.3 have a similar base though /mach-msm has started differing a bit lately |
| 20:14.39 | detule | btw the smd in 3.3 is from codeaurora android-2.6.35 branch |
| 20:14.44 | CptAJ | port my patches to 3.3, you mean? |
| 20:14.51 | detule | no port the 3.3 smd patches to .27 |
| 20:14.57 | CptAJ | ah, I see |
| 20:15.25 | detule | whitestone support in 3.3 and .35 will be difficult at best since both don't use the microp-klt -ksc crap from .27 |
| 20:15.50 | detule | option two is you can try and pick out specific code segments |
| 20:15.52 | detule | for example |
| 20:16.31 | detule | imo one way your issue could be coming up is because the open-close-open chanel sequence in .27 is flawed |
| 20:16.54 | detule | as in we don't wait for acknowledgement that the ch is open before declaring it open |
| 20:17.17 | detule | this has been fixed in the new smd |
| 20:19.06 | detule | more specifically https://gitorious.org/~detule/linux-msm-rhod/detules-linux-msm-rhod/blobs/3.3-smd_update/arch/arm/mach-msm/smd_tty.c#line274 and the code few lines above and below |
| 20:19.39 | CptAJ | so in essence, port that specific change to my source then? |
| 20:20.33 | detule | you need the functionality not just those few lines of code, this means enabling the channel notifier to handle SMD_EVENT_OPEN events |
| 20:22.26 | CptAJ | this is gonna be fun. I have no idea what smd even is and I'm gonna have to fix it XD |
| 20:23.12 | CptAJ | well, thats pretty much what I've been doing so far anyway =P |
| 20:24.08 | CptAJ | alright. name all the things you think I'll have to change and I'll get down to it. I'm gonna start reading that now |
| 20:25.17 | detule | ha i have no idea, but that one is a good place to start, you need to implement that ch_opened_wait_queue |
| 20:26.06 | detule | possible also swap out the work_queues in _tty with tasklets -> this way you can get rid of those wakelocks, and will likely solve your other issue witht the wakelock corruption |
| 20:26.29 | detule | (you don't need wakelocks because tasklets don't sleep unlike workqueues) |
| 21:04.43 | CptAJ | stupid person trying to call me. I don't have a microphone! |
| 21:04.59 | ahigerd | XD |
| 21:06.04 | CptAJ | this other girl was complaining the other day because I never text her on whatsapp |
| 21:06.30 | CptAJ | I was like "ffff... I'm not gonna type this explanation up -_-" |
| 21:16.07 | *** join/#htc-linux ali1234 (~ajbuxton@s15821883.onlinehome-server.info) |
| 21:18.02 | *** join/#htc-linux arif-ali (~arif-ali@91.84.160.181) |
| 22:39.47 | *** join/#htc-linux ahigerd (~ahigerd@173.218.156.102) |
| 22:39.47 | *** join/#htc-linux ahigerd (~ahigerd@libqxt/developer/ahigerd) |
| 23:39.35 | jonpry | he doesn't have microp working anyways |
| 23:43.54 | *** join/#htc-linux detule (~detule@unaffiliated/d3tul3) |
| 23:46.33 | *** join/#htc-linux mitsutaka (~mitsutaka@221.219.116.16) |