Thursday, 2011-11-10

*** ringer has quit IRC00:22
*** SytheZN has joined #xdandroid00:52
SytheZNoh great masters of the androidian experience...00:53
SytheZNwhat would cause my "desktop" to reset to default, losing all my "widgets"00:54
SytheZNfaq: no i haven't installed anything new, changed any settings or altered anything else prior to or since my last reboot00:59
*** phh has quit IRC01:00
*** phh has joined #xdandroid01:01
*** ImCoKeMaN has quit IRC01:02
*** Sythe_ZN has joined #xdandroid01:02
*** Sythe_ZN has quit IRC01:05
*** SytheZN has quit IRC01:06
*** virsys has quit IRC01:29
*** bzo has quit IRC02:18
*** ryannathansAFK is now known as ryannathans02:30
*** kalemas has joined #xdandroid02:58
*** |Jeroen| has joined #xdandroid03:42
*** kalemas has left #xdandroid04:22
*** panda84kde has joined #xdandroid04:23
*** kalemas has joined #xdandroid04:28
*** virsys has joined #xdandroid04:52
*** hardwalker has quit IRC05:29
*** raymonddull has quit IRC05:56
*** |Jeroen| has quit IRC06:08
*** f00bar80 has quit IRC06:16
*** f00bar80 has joined #xdandroid06:21
*** turbolapin has joined #xdandroid07:26
*** mgross029 has joined #xdandroid08:11
mgross029SytheZN, It sounds like your data.img got corrupted and a new one was created.08:14
*** helicopter88 has joined #xdandroid08:30
*** t0gus4_ has joined #xdandroid08:31
*** t0gus4 has quit IRC08:31
*** f00bar80 has quit IRC09:51
*** turbolapin has quit IRC10:07
*** ringer has joined #xdandroid10:17
*** kalemas has left #xdandroid10:31
*** ringer has quit IRC10:46
*** t0gus4_ has quit IRC11:02
*** t0gus4 has joined #xdandroid11:02
*** kalemas has joined #xdandroid11:06
*** rpierce99 has joined #xdandroid11:18
*** emwe has joined #xdandroid11:21
detulehey emwe11:39
emwehi. still need to catch up with all the mails.11:40
emweso you say we could drop the sixth slot?11:40
detulei have no idea, perhaps worth a try11:40
detuleit seems unreasonable that it would try to free up memory at <80MB11:40
emweas it finds nothing you say, right?11:41
emwei need to get ahold of it and find time to test it out.11:41
emwei had SOD over night... this pisses me.11:41
emwedunno where that comes from.11:42
mgross029emwe: Just as a comparing and grepped in .39 and there statement in htc_acoustic_wince.c is "if (amss_data->mic_bias_callback)"  Same as what you had previously in the .35 kernel.  Just and fyi11:42
emwemgross029: ? pardong?11:42
emwe-g11:42
emwei really whonder what is up with the RHOD500. i have no incall mic issues. perhaps it's a CDMA mode thing?11:43
emwedetule: you are CDMA RHOD400, right?11:43
detuleyes11:43
detulereally the person that doesn't have any issues11:43
detuleis WisTilt211:43
detuleon his gsm rhod11:43
emweyou got incall mic issues?11:43
detuleyes11:43
emweoh?!11:43
emwei got none on RHOD400 GSM11:43
emweso do CDMA perhaps need it?11:44
emwethe original code had it NULLed for RHOD because JB has a RHOD300 as well11:44
detuleemwe, to tell you the truth i had issues when the call back was not nulled out as well11:44
mgross029emwe: Went back to your 11-05 autobuild and the problem went away.11:44
detuleit makes little difference on my end if it's nulled out or not11:44
emweso then I can't seem to get any clue what to try now...11:45
emwedetule: CURRENT = 256 on .39 now?11:45
detuleyes11:45
emweperhaps there's still some more voodoo required with audio routing in userland? who knows...11:45
emwealso my device crashes with nullptr in audmgr.c after two missed calls and then reboots11:45
mgross029emwe, that did help (CURRENT) that is11:46
detuleemwe, my device is perhaps not the best for acoustic feedback, as the speaker is broken and could be causing other issues, bzo needs to chime in, and/or get rpierce99 on the take11:46
emwemgross029: well yeha, for incall volume changes.11:46
mgross029:p11:46
detulebtw emwe, htcrhodium-led.c would make you proud11:47
detule_all_ leds in one board file11:47
emweyou also got ksc client hooked up there for buttons?11:47
emwei've not looked at it :/11:47
detuleyeah pretty slick i2c_new_dummy from old client11:47
detulefrom klt client that is11:47
emweideally we wouldn't duplicate all this stuff for all boards...11:48
emweso much redundant code. that's why i never got really far.11:48
emwestinebd: ping.11:49
emwedetule: how have you visualized all current oom_adj values? you got a script handy?11:50
detuleemwe no, there's got to be some shell command find . | grep "oom_adj" | xargs cat blah blah blah11:55
detulei am just no good at scripting11:55
emwesame reason why i asked you :)11:56
emweok.11:56
emwedetule: the highest oom_adj i see is 8 here currently.12:03
emwesome 8ers 7ers and then 4ers12:03
detulethey get elevated past 1012:03
detuledid you figure out the shell command?12:03
detulethis works on my desktop "find /proc | grep oom_adj | xargs -I {} cat {}"12:05
emweadb shell "find /proc/ -name 'oom_adj' -print0 | xargs -0 cat {}"12:06
emwexargs on device is a bit dumb12:06
detuleyeah i noticed12:07
detulei set the last oom_adj value in GB to 10, and lowmemorykiller went to work12:07
emwegot 0,2,4,7,10 with 1536,3072,8192,10240,12288 now12:09
emweso freemem below 12288*4 kills apps up until 1012:10
detulewith 10 you won't get a lot of things staying in memory, especially if market is open, perhaps 2-3 apps12:10
detulekills apps over 1012:10
emweeek, sorry ;)12:10
emweso at 50mb12:11
detuleyeah somewhere around there12:11
emwe49152kB12:11
emwethe bad thing is, this won't help at all with the SODs...12:12
emweneed to get up a spreadsheet with the iomappings12:12
detuleemwe, your sod's confuse me....can't be clock related12:12
detuleit has to be something with usb12:13
emweperhaps network/radio related12:13
emwebut it's unplugged over night...12:13
detuleit's pretty much automatic with usb/screen off12:13
emwepardon?12:13
detulei mean, the few times i've used .35 whenever the usb is plugged in and screen off i get that sod - perhaps it's not so automatic as i thought?12:13
detulei might be making sweeping generalizations here12:14
emweyou also got that?! i don't have that SOD with usb plugged12:14
emweit magically fixed somehow here.12:14
emwebut mgross029 has exactly the same...12:14
emweso yes, if I can figure your issue, perhaps mine goes away12:14
detulei remember getting it for sure, and i know bzo did as well12:14
emwestrange. why not me?!12:15
emweand regarding notify_usb_connected...12:15
detuleperhaps you are right maybe it is network related12:15
emweit's in the devices-* somewhere.12:15
mgross029detule, I remember when running 39 I did not get them before, so what changed I guess is my question12:16
emweperhaps the board reset is a bit bad.12:16
emwethere's so many factors...12:17
detuleemwe, what i meant about usb_connected was i see in the board file in .35 we are setting .usb_connected to notify_usb_connected.....i don't see that .usb_connected callback being set anywhere in .3912:18
detulebut perhaps grepping is failing me12:18
mgross029emwe: did WisTilt2 pull a lot of his patches for 39 directly from the 35 tree?12:18
emwemgross029: all that code was initially pulled in from .2712:19
emwemgross029: so the old .27 got pulled over there quite harsh.12:19
mgross029Ahh12:19
mgross029emwe, what was the great idea you said I had in the logs and then you pulled your sd?  That confused me..  :p12:20
emwemgross029: forget about that. user error. (mine)12:21
emwei thought i found something regarding my SOD, just fooled myself.12:21
mgross029lol :p ok12:22
mgross029Going to test SOD here.  See if I can find anything12:22
stinebdemwe: please stop pinging me12:22
stinebdi mean hi12:22
emweunderstood. :P12:23
stinebdwhat is super important?12:23
emwethe super important question is, can i setup a new project under XDAndroid for a new fork which get's two lines added in the code?12:23
stinebdsure, you got perms?12:24
stinebdi don't really remember12:24
emwethen i dunno how.12:24
emweis that project created on gitorious.org?12:24
emweor with some repo magic?12:24
stinebdon the site12:24
emwei should see something like "create new project" button?12:24
stinebdlet's see12:25
stinebdhttps://gitorious.org/xdandroid12:25
stinebdadd repository12:25
stinebdright sidebar at the top12:25
emwethen no12:25
stinebdoh right, i was unable to give permissions for that12:26
stinebdbecause their site is broken12:26
stinebdi just tried again and it's still not working12:26
stinebdwhat's the project?12:26
emwehardware_libhardware12:27
stinebdoh yeah12:27
emwefor two freaking lines of code12:27
detulecan't we just do an overlay for that file12:27
emwedetule: no overlays anymore!12:27
stinebdemwe: ok done12:27
emwethat has cost me some nerves with people trying to update after they had to be removed.12:27
detuleok12:28
emwestinebd: thanks! you can go release GBX0B later this evening, then.12:28
emwenah, just kidding.12:28
stinebddon't think i'll be home, sorry12:28
emwethen arrrghhh will do :)12:29
emwethx for taking the time stinebd.12:29
stinebdi want to put the release keys on our distro mirroring account12:29
stinebdarrrghhh has access to the account and i can add you if you email me your ssh pubkey12:30
stinebdbut then that way i'm not the only one with the keys, and they aren't on the web or anything12:30
emwedone.12:31
emweif i can get stuff i am quick, but not getting things done.12:32
detuleemwe, perhaps worth taking a look but htcrhodium_usb_hw_reset in .35 looks a bit different than usb_phy_reset in .3912:33
emweyes.12:33
mgross029emwe, on SOD here is the last line of my last_kmsg [ 1714.166900] ARM11 entering suspend mode  Just fyi12:34
emweheh?!12:34
emwethe htc_battery_smem wakelock is supposed to keep device from idle?!12:34
emwethat is what i added in order to not fall asleep on usb connected.12:34
emweand that had caused me the SODs back then12:34
emwei explicitely changed the wakelock way back then.12:35
stinebdmaybe someone broke it. i'm thinking acl12:35
emwenah...12:35
emwebut something on .27 is keeping the device from idling too12:35
emwedevice will never collapse arm11 on .27 when usb is connected12:35
stinebdticks12:35
stinebd.27 isn't nohz12:35
* stinebd shooting at the dark on that one12:36
emwei whonder why you aren#t a kernel dev, really.12:36
emwei have not the slightest idea :P12:36
stinebd;)12:36
emwemgross029: that was good info though.12:36
detule.39 is tickless too12:37
emwe.35 as well12:37
detulei don't think tick/less would make a difference in terms of wake locks12:37
emweok, gingerbread branch pushed. need to push the other patches for fwbase and msm7k and the manifest extension later.12:38
emweweekly shopping ahead...12:38
mgross029emwe, Here is the whole file if interested.  http://dl.dropbox.com/u/45928762/lastkmsg1110.txt  Lots of msm72k_udc: usb_ept_queue_xfer() tried to queue busy request12:40
detuleso er the usb wakelock expires on change of charging source?12:41
detuleisn't there some voodoo you are doing with the cable status update functions where you notify AC charging first and then notify USB charging next?12:42
detulenvm that probably doesn't matter12:44
stinebdmy theory is clearly the awesomest12:46
*** panda84kde has quit IRC12:46
*** corein has joined #xdandroid13:09
emwere. shopping cancelled.13:12
mgross029is that a good thing? :p13:13
emweyes. ;)13:13
mgross029Last time I was over in Germany I remember daily shopping. :p13:14
emwemgross029: so yeah, seems it's resuming/suspending all the time. which brings it out of trak at some point.13:14
emweit's just the regular week shopping... we aren't here the weekend anyway, so skipped it.13:15
mgross029ARM11 or USB?13:15
mgross029Nevermind.  ARM11 at the looks of it.13:18
emweyap :)13:21
*** AndersG has joined #xdandroid13:21
emwedetule: it might be usb resets all the time or has some connectivity issues and thus the wakelock expires, get's reestablished and so forth... perhaps it's really the usb reset which i did a bit too "simple" compared to .2713:24
detuleemwe, could be, i know in .39 the usb connection seems more unstable than in .27... MACs seem to be a good test case, a simple ls blows up the adb connection13:26
emwei have it failing from time to time... but usually it is good for a while.13:27
mgross029Think this is missing in .35 ./linux-msm/drivers/usb/function/adb.c  ret = usb_ept_queue_xfer(ctxt->out, req);13:27
emwelike after half an hour, it may fail...13:27
emwemgross029: well, let's first start evaluating why it works for me, not for you.13:27
emwemgross029: going to look... comparing with qualcomms msm tree13:27
mgross029emwe you're special13:28
detule.35 doesn't even have that file13:31
detule(nor does .39 for that matter)13:31
mgross029emwe,  Do you turn your BT off?13:31
emwenope. i can't :/13:31
emweperhaps that is another reason for SODs.13:31
emwedunno13:31
emwei know i had sods when my bt headset was shutting itself of or going idle.13:31
mgross029That is another work around for me.  Turn off BT and then the device won't go into SOD on usb.13:31
emweaha13:32
emwebut you had SODs before BT iirc13:32
mgross029With BT off the device doesn't slelep so no SOD13:33
mgross029Same with the Stay Awake option13:33
emwelol.13:34
*** mgross029_ has joined #xdandroid13:36
mgross029_Damn WebIRC junk...  Bleh13:37
*** mgross029 has quit IRC13:38
emweit's likely usb connected.13:39
mgross029_The WebIRC? :p13:40
*** mgross029_ is now known as mgross02913:40
mgross029emwe, can you recreate a SOD on your Rhod?  Pull the /proc/last_kmsg to compare?  Just a thought...  Since yours seems different13:51
emwewhen i wake up in the morning, ramconsole dump and last_kmsg are "empty" just continuous garbage.13:52
mgross029I usually boot back into the system then adb shell cat /proc/last_kmsg.  I did not pull that from ramconsole.  It should remain from the last time your system was up. AFAIK13:54
emweboth are "empty"13:56
mgross029Bleh... Well that doesn't help. :-\13:56
*** rpierce99 has quit IRC13:57
emwedetule: caps/fn userland is out patchwise.14:16
detulegreat sorry it was a pain in the behind14:16
detulenow I just need to build a system image to test functionality14:16
*** panda84kde has joined #xdandroid14:18
*** panda84kde has quit IRC14:18
emwemgross029: voice search bug reproduced. i just started it up, no mic. the "workaround" is.. toggle volume when VS is up and it will recognize your speech. plz confirm.14:20
emwetake your time. nothing urgent.14:21
mgross029emwe: just got your mail I'll load it up now.  Ironically I just missed a call because no ringer and the volume up/down seems to be stuck on in-call volume.  I also try to call my VM to get the message and I have not audio in earpiece eiter.14:21
mgross029s/eiter/either14:21
emwevol up down nogo? man... we are doomed somehow.14:21
emwetest the kernel first. don't worry about the vol/mic issue now14:22
emwe(as a proposal, nobody forces you)14:22
mgross029Well I haven't tried VS just read that post...  Sec14:22
emweand no hurries. i am not getting bored here...14:22
emwedetule: you are building on your own again? i just need to write a mail with the link :) ril hardening patch also made it out.14:23
detulenot building, that was a not so subtle nudge to get you to build me one14:23
detulei need to migrate my machine from 32bit to 6414:24
emweif you confirm it's good regarind caps/fn, i'll share to the rest.14:24
detulesure, but then again if it's broked i won't know if it's the kernel or the patch....i wrote it differently in .39 than in .2714:25
detulei'll give it a go14:26
emwei quickly just spotted caps log output, but was confused not to see fn14:26
emwe(in google search toolbar)14:26
*** vinceweis_ has joined #xdandroid14:32
mgross029emwe, just to let you know my volume is stuck on in-call volume.  Voice Search gets an error.  Phone is not recognizing USB connection.  Bleh...  I did go to terminal and dumped a kmsg and logcat to my sdcard14:34
mgross029Going to reboot now and apply the updated kernel.14:34
emweouchi.14:36
emwei am going to have supper. a little late today...14:36
emwelaters.14:36
detuleemwe, boot ani14:36
mgross029Laters...  Enjoy14:36
emwedetule: i shouldn't look a last time on the monitor... boot ani repeating? that happens for me from time to time after new image build. just reboot, and second boot is fine.14:38
emwe(if that was it)14:38
detulenono booting system now14:38
mgross029I did a repo sync and building on two different VMs so we'll see which one is done first. :p14:38
emwedetule: ok. now i am really off for a bit :)14:38
*** emwe_ has joined #xdandroid14:50
*** emwe has quit IRC14:54
*** helicopter88 has quit IRC14:57
mgross029detule, look at this one.  W/ToneGenerator( 1525): Tone start failed!!!, time 189240414:57
mgross029That was a call which did not ring so I missed it.14:58
detulecould be more than one thing i guess, enable debugging messages in ToneGenerator.cpp perhaps15:05
mgross029I'll post both my logcat and dmsg I pulled from terminal just after I missed the call.  There is more info.  That one just stood out right away.15:07
mgross029This one stood out too W/AudioTrack( 1525): obtainBuffer timed out (is the CPU pegged?) 0x2e9508 user=00000960, server=0000000015:08
mgross029http://dl.dropbox.com/u/45928762/dmsgnoring.txt  http://dl.dropbox.com/u/45928762/lcnoring.txt  For your viewing entertainment15:15
*** helicopter88 has joined #xdandroid15:19
*** SytheZN has joined #xdandroid15:24
*** kalemas has left #xdandroid15:25
*** emwe_ is now known as emwe15:27
emwemgross029: perhaps your CPU is really under high load and/or there's some high IO load going one making it impossible to play the sound15:28
emwemgross029: how's the kernel?15:28
emwedetule: how's the image?15:28
detuleleds work15:29
detuleemwe, need to chown them in rootfs15:29
detulechasing my tail with that one15:29
SytheZNmgross029: you said you think my data.img got corrupted... wouldn't that mean any installed apps would've been lost? or at least lost their config as well?15:31
emwedetule: oh yeah, forgot. i'll prepare a rootfs patch.15:33
* SytheZN just dropped his cigarette in his coffee15:34
SytheZNyou know... ATI drivers aren't worth the MB,s they consume15:35
emwedetule: +    chown system system /sys/class/leds/caps/brightness15:35
emwe+    chown system system /sys/class/leds/func/brightness looks ok?15:35
detuleyeah15:35
SytheZNi've been e-mailing them for 6 months because their drivers stopped using any installed inf's with custom timings embedded15:36
SytheZNi sent them the inf i wrote and they said it's fine15:37
SytheZNbut they can't tell me why it won't work15:37
detuleemwe, it also didn't help that i had patched the kernel incorrectly15:37
detulebut it's been fixed15:37
detuleif you pull .39 you can test the led functionality15:37
detulethanks for all of that -> i know it was a lot of work for a little gain15:38
mgross029emwe, just had to update some updates come across on market.  Going to set up and test now15:38
mgross029SytheZN: Correct you should have went back to your base settings...  That is what I thought you said happened15:38
emwemgross029: take your time. no hurries as mentioned earlier.15:38
emwedetule: nah, it was perfectly ok. we wanted it, anyway. thx for pulling it together. i haven't even tested it...15:39
emwecool the stuff works fine.15:39
SytheZNmgross029: yeah, my "desktop" reset, but none of my apps were lost or lost any of their configs15:40
mgross029SytheZN: did you do a restore from Titanium Backup by chance?15:41
*** SytheZN has quit IRC15:41
*** SytheZN has joined #xdandroid15:41
mgross029emwe: Ha...  Now my computer won't recognize the USB...  LOL15:41
SytheZNmgross029: yeah, my "desktop" reset, but none of my apps were lost or lost any of their configs15:41
SytheZNas far as i can see, only the homescreen widgets were affected15:41
SytheZNsoz, f* network15:42
mgross029SytheZN: Not sure on that one15:42
SytheZNthanks anyways... i'll do some digging, let you know if i come up with anything15:43
SytheZNyou don't think it's possible the homescreen config was corrupted without the rest of the data.img being affected?15:44
mgross029Well I've see that if I've done a TB restore or changed my launcher15:45
SytheZNis it possible for part of it to be rebuilt?15:45
SytheZNchanged your launcher? ie from haret to something else?15:46
mgross029Android Laucher, meaning the one were the apps tray is when you are in Android15:47
mgross029You could just readd the widgets I suppose and reboot to see if they stick or not.15:47
SytheZNah, blonde15:47
SytheZNthe only thing i can see missing is the wireless widget... can't add it again15:48
SytheZNwell they're sticjing15:48
SytheZN*sticking after a reboot15:48
SytheZNfar as i can tell anyways15:49
SytheZNthanks for the help though... much appreciated15:52
SytheZNgotta run15:52
mgross029SytheZN: NP15:52
*** SytheZN has quit IRC15:53
mgross029emwe, So far my system only turns on charging when USB connected.  It will not connect the ADB driver it seems.15:59
detulecheck if adbd is running in ps16:01
detuleif not try running it directly16:01
mgross029detule: Yep running.  I will kill and see if it restarts16:03
detulewhat happens when you "adb devices"16:03
detuleyou linux? try lsusb see if you see the device16:04
mgross029XP Unfortunately...  Linux VMs only which don't have USB connected at the moment.16:06
mgross029I think it is XP hung up on USB16:06
emweso wth did i break... it will detect usb, but not enable usb debugging...16:07
mgross029emwe, I don't think anything unless you are sending me XP bugs. :p16:08
emwenah, i can reproduce16:08
emwea pita though i have to reboot to wince and push kernel over there...16:08
mgross029It has to be my stupid crappy xp system.16:12
emwe? regarding usb? no.16:14
emweit was the kernel i sent along.16:14
*** AndersG has quit IRC16:18
mgross029emwe, sorry but are you saying the kernel you sent disabled my ability to connect via usb to adb?  Just wanted to be clear.16:27
emweyes. i already said i can reproduce16:27
emwei didn't test before.16:27
mgross029Ok gotcha.  Sorry I have usb problems with this xp crap all the time so I thought it was my system. :p16:28
mgross029I know what you mean about booting into wince.  I do it everytime you guys give me something new or when I need to test something out. :p16:32
emweouch.16:35
mgross029emwe, I pulled all of the gb repo changes and already created an image from my local repo.16:37
emwegood to know i didn't screw things up16:38
mgross029I can send out a dropbox link but it will have my Global network change.16:38
emwewe can go over that "later".16:39
mgross029Yeah it actually compiled pretty quick too.  I was surprised...16:39
mgross029Ok16:39
emwepretty quick?16:39
mgross029Well it was about an hour or so I think16:39
emweah lol16:39
emweman... you confuse me with how you say things.16:40
emwe:)16:40
emwebah, i hate my upload speed.16:40
mgross029Which compared to a couple that have taken over two hours.  I think it was because my system wasn't being tied up as much16:40
mgross029That was where I was hoping to help out.  I'll have to build another clean repo. :p16:42
emweplz download a new kernel from the same url i posted earlier.16:42
mgross029I have upload speed to spare, fortunately for me.  I used to have 768 up just a couple of months ago though.  They just boosted us up.16:42
emweit's pretty similar... at least works here.. but you need to test out the rest.16:43
mgross029Ok will do.16:43
emwethanks16:43
emwebrb16:43
mgross029Ok loaded up and booting16:47
*** raymonddull has joined #xdandroid16:51
mgross029Ok. connected to usb after sleep it disconnects adb17:00
mgross029And if you wait too long to wake it up it still goes SOD.17:01
mgross029Ok gotta head out.  Laters all.17:02
*** mgross029 has quit IRC17:02
*** programmer8922 has joined #xdandroid17:07
stinebdemwe: ping17:21
emwemgross029: could reproduce.17:21
emwestinebd: pong17:21
stinebdpm incoming17:21
*** helicopter88 has quit IRC17:29
*** rpierce99 has joined #xdandroid17:33
*** programmer8922 has quit IRC17:35
*** emwe has quit IRC17:55
*** programmer8922 has joined #xdandroid18:05
*** corein has quit IRC18:37
*** Yusuke14 has quit IRC18:38
*** rpierce99 has quit IRC19:13
*** d3tul3 has joined #xdandroid19:17
*** hardwalker has joined #xdandroid20:23
*** hardwalker has quit IRC20:23
*** hardwalker has joined #xdandroid20:26
*** d3tul3 has quit IRC20:38
*** d3tul3 has joined #xdandroid20:55
*** d3tul3 has quit IRC21:01
*** rpierce99 has joined #xdandroid21:28
*** vinceweis_ has quit IRC21:41
*** d3tul3 has joined #xdandroid22:29
*** d3tul3 has quit IRC22:34
*** rpierce99 has quit IRC22:44
*** TheSeven has quit IRC22:56
*** [7] has joined #xdandroid22:57
*** rpierce99 has joined #xdandroid23:16
*** rpierce99 has quit IRC23:20
*** d3tul3 has joined #xdandroid23:56

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!