Saturday, 2011-10-08

*** programmer8922 has quit IRC01:13
*** SpecR has quit IRC02:09
*** emwe has joined #xdandroid04:30
emwearrrghhh: mgross029: just catching up logs: i have the mobile network mode selection menu in mobile network settings. there i can switch freely between all variants. that it is switching to gsm somehow and crashes seems like the "culprit" for your call issues.04:46
emwearrrghhh: regarding touchscreen: sometimes on wake it's defunct for ~5seconds occassionally. issue with pm in the msm_ts driver iirc. issue cropped up again after updating to the CodeAurora code allthough PM got disabled. needs to be investigated. Same goes for touch sensitivity. have the threshold pretty high.04:48
emwearrrghhh: regarding prox, i think i need it going physically first before i can figure how it behaves.04:48
emwearrrghhh: regarding LS, it's not yet enabled in autobuild. doing so later on.04:49
emweKraln: btw, thanks for your reply. bummer it is kinda broken here. apparently physical. dunno what might cause it except my stock HTC screen protector.05:13
*** |Jeroen| has joined #xdandroid07:26
f00bar80anybody tried GBX0A  and know exactly if it can be rooted or not and how if yes?07:36
*** helicopter88 has joined #xdandroid07:39
*** helicopter88 is now known as helicAWAY07:46
*** helicAWAY is now known as helicopter8808:30
*** helicop1 has joined #xdandroid08:44
*** helicopter88 has quit IRC08:45
*** helicop1 is now known as helicopter8808:45
helicopter88f00bar80,grx0a should be already rooted09:12
*** caliban2 has joined #xdandroid10:04
emwearrrghhh: Kraln: disassembled the rhod400. a "shitload" of dust near the sensors. also directly under the digitizer/screen plastic where the prox sits. hope that's been it. now i need glue for getting the digitizer seated safe again.10:04
*** helicopter88 is now known as heli_bf310:31
*** JesusFreak316 has joined #xdandroid10:55
Kralnemwe: woo11:18
emwehey Kraln. just back from buying glue. hope it works out... didn't find "foamy" one as was the original from what it looks.11:23
emwethere's been quite some dust which made it under the digitizer. likely because it wasn't that hermetically glued in. (pardon my english)11:24
Kraln:-(11:25
emwestill hope the dust under the plastics/digitzer irritated the sensor.11:25
Kralnhopefully that was it11:25
emweif not, bad luck ;)11:25
emwebut thanks for your reporting that it works.11:25
emwewas driving me nuts it worked for the others but not me :)11:25
emwenow let's hope i can reassemble that bitch functional. first doing some cleaning... will take some time.11:26
Kralnyeah that's the hard part11:26
Kralnand any dust on the screen makes me twitch11:26
emwethere's been a lot between panel and digitizer. especially in sunlight this was highly noticeable.11:27
emweamazed how thin that panel is.11:27
arrrghhhheh11:28
arrrghhhi remember you said that when you got it emwe11:28
Kralnmust have been sneaking in since I shipped it11:28
arrrghhhremember what i told ya?  :P11:28
emwethat people broke their rhods doing so?11:29
arrrghhhnah, that beggars can't be choosers.  you got that RHOD cheap :P11:29
emweof course. i am not complaining. just stating facts.11:29
arrrghhhyeayea i'm just teasin ya11:29
emweyou teased me enough saying prox works for you.11:30
arrrghhhtouche.11:30
Kralncheap? cost of shipping. I found out later that was still worth like 200 USD11:30
arrrghhhi'm sure that's maddening.11:30
arrrghhhKraln, ?  really?11:30
arrrghhhi thought he paid like $16.  Oo11:30
emwei hope you don't wan't it back.11:31
arrrghhhhahaha, i would hope not either.  kind of a crappy donation.11:31
Kralnnah, I was telling arrrghhh I'm verry happy with my T757511:31
emweis that touch pro 7?11:31
arrrghhhyea11:31
arrrghhhpro7 or the "arrive" lol11:31
Kralnyeah11:31
arrrghhhit's arrived.11:31
arrrghhhemwe, so that system image, it has the data patch?11:33
arrrghhhor does it also have LS, and you just need to update the kernel?11:33
arrrghhhOo11:33
arrrghhhseems kernel i updated alreadys.11:33
emwels is in latest autobuild. prox, ls, data and everything else in system image.11:34
arrrghhhso i ran .35 on the acoustic froyo build11:34
arrrghhhi can call just fine...11:34
arrrghhhemwe, you haven't had any SOD's in .35 in a while?11:35
emweone on last sunday in the morning. but usually nada since i am using the lowmemorykiller tweaks and have set another io scheduler11:35
arrrghhhhrm11:36
arrrghhhi seem to get them either charging overnight11:36
arrrghhhor plug in usb, adb/etc11:36
emwetaht sounds like when had insta cable plut notification on .2711:36
arrrghhhi don't think i've had "any" with unplugged usage...11:36
emwestrangely i don't have issues with that11:36
arrrghhhwell what's odd is, it's not instant.11:36
emweperhaps it's a gsm thing again?11:36
arrrghhhdamn you.11:36
emwewhat is not instant? cable plug?11:37
emwethat is definitively instant here.11:37
emwe.3511:37
arrrghhhno, the SOD from cable plug11:37
emweah11:37
arrrghhhcable plug recognition is instant, unlike .2711:37
arrrghhhbut i've frequently had SOD's shortly after USB11:37
emwealex looked into the windows driver and cable plug should be technically how we do it.11:37
emwe:/11:37
arrrghhhwell11:38
emwei could build a kernel without cable plug noti for you to test out.11:38
arrrghhhi'll try to get ramconsole or LAST_KMSG logs for you here11:38
arrrghhhi really do like the plug noti... :(11:38
emweme too ;)11:38
arrrghhhtis nice11:38
emweyou'll likely see the plugs/unplugs in kernel and everything will function11:38
arrrghhhit's funny, there's all these little things that are getting functional on .3511:39
emwebut you can't adb in11:39
emwecam,bt, wifi missing11:39
emweand button backlight, caps, fn11:39
arrrghhhyea11:39
arrrghhhis you going to rebase?11:39
emwei dunno when i find the time to do that11:40
arrrghhhi think my horrible IRC grammar is going to make foreigners speak goodly.11:40
arrrghhhhehe11:40
emwei rather have a working .35 and can work on userland and kernelland11:40
arrrghhhyea11:40
emwefor now that is.11:40
arrrghhhi thought you said it would save you the work of catching up to where he is at.11:40
emweit will take a while until all is functional again on after the rebase methings11:40
emwei am not cathing up anymore.11:41
emwealex' been working on another non-android branch so to say11:41
emwenothing to catch up for now.11:41
arrrghhhah11:41
arrrghhhyea, i know he got that hd mini11:41
emwethink i'll postpone that rebase until userland get's more polished. especially gb11:42
emwewe got acoustic, froyo sensors, gb gsensor pending.11:42
arrrghhhokie11:42
arrrghhhacoustic is going to be a beast11:42
emweapart from quite some .35 work for rhod/topa...11:42
arrrghhhi keep hoping JB can find the time to help :P11:42
emwei just need time11:42
arrrghhhyea11:42
arrrghhhtime is a bitch.11:42
emwegoing into dust cleaning mode.11:43
arrrghhhlol11:43
arrrghhhok11:43
emweplz cross your fingers guys.11:43
arrrghhhgood luck11:43
*** heli_bf3 is now known as heli_AWAY11:48
*** caliban2 is now known as cal2_afk11:48
arrrghhhuhm11:51
arrrghhhsomething in GB userland is not right.11:51
arrrghhhre: the whole gsm/cdma system select.11:52
arrrghhhi can't choose it in either mode it seems.  in CDMA mode there's no way to choose GSM in the UI, and when the radio fails horribly and goes into GSM mode, likewise there's no place to set it back to CDMA... hum.11:53
arrrghhhemwe, light sensor is working :D11:54
emwegood.11:55
arrrghhhseems pretty jumpy, depending on how lights hit it lol11:55
emweregarding radio.. hm... you disturb me. i am cleaning :P11:55
arrrghhhbut covering the sensor makes it go down to 16011:55
arrrghhhlol sorry.  continue cleaning sir.11:55
emwei can select anything from cdma home mode(?) and which network11:55
emweno idea if i miss something kernel'ish what ril looks up.11:56
emwehtc_hw is there.11:56
emweneed to look later it seems :)11:56
emweyou rely on some kernel module params?11:56
emwefake_gsm or sth?11:57
arrrghhhno11:57
emwedunno what they actually do..11:57
arrrghhhnot anymore...11:57
arrrghhhjust under mobile network settings11:57
arrrghhhall i have is system select11:57
arrrghhhand APN's11:57
arrrghhhofc data enabled/roaming as well, but that's it.11:57
arrrghhhget back to cleaning, we can try to figure it out later.11:58
arrrghhhhrm.  phone seems to have SOD'd again after a usb plug.  i'll wait a bit and reboot, try to pull logs...12:21
*** programmer8922 has joined #xdandroid12:33
*** heli_AWAY is now known as heli_bf312:38
arrrghhhcan't cd to /data/system/dropbox?  wth?12:40
arrrghhhcrap12:43
arrrghhhdidn't su12:43
*** JesusFreak316 has quit IRC12:47
arrrghhhbleh, these dropbox logs seem useless.12:48
arrrghhhhrm i can ping 169.254.2.112:59
arrrghhhbut i can't telnet to it?  isn't that what you do...?12:59
arrrghhhputty just dies.13:00
*** |Jeroen| has quit IRC13:09
ryannathansblame all but oneself13:12
arrrghhhnah i'm probably doing it wrong.13:13
arrrghhhi haven't used haretconsole in a while13:13
arrrghhhand i always seem to forget everything i new about it13:14
arrrghhhknew*13:14
arrrghhhi thought i was supposed to telnet to 169.254.2.1 on port 999913:14
arrrghhhthen use that dump command13:14
arrrghhhbut... no dice.  can't telnet.13:14
arrrghhhi wonder if there's something else i need to run before i can telnet...13:14
arrrghhhoh13:16
arrrghhhi'm a fucking dumbass.13:16
arrrghhhlol....13:17
arrrghhhforgot to actually run haret and hit listen for connections.  gawd.13:17
*** cal2_afk is now known as caliban213:21
arrrghhhbleh13:23
arrrghhhjust a lot of adb/usb poop13:24
arrrghhhthen the jibberish.13:24
arrrghhhdamn...13:24
arrrghhhemwe, still cleaning?  :P13:24
emwearrrghhh: just done reassembling. prox still broken. damnit.13:27
arrrghhhaw13:27
emwethe dust is away, but i rather had dust then no-worky prox.13:27
arrrghhhthat's a bummer...13:27
arrrghhhdoesn't work in winmo either?13:27
arrrghhhyou flashed some energyrom poop?13:28
emweenergy reference, yes. 21219 or how hat was called.13:28
arrrghhhstill fail in winmo?13:28
emwething is it's active but doesn't seem to get to report correctly.13:28
emwetrying vm in winmo again13:29
arrrghhhhrm13:29
emwejust fired up android.13:29
arrrghhhdefinitely works for me in winmo in a call to vm.13:29
emwevery likely a phyisical thing then here.13:29
arrrghhhyea13:29
arrrghhhthat sucks!13:30
emwenow i need a driver module param which allows me to set it to always report far ...13:30
arrrghhhi was going to ask about that13:30
emweotherwise i'd be having call touch iu trouble as i wouldn't reach it.13:30
arrrghhhit seems when the driver is first initialized13:30
arrrghhhit thinks its near13:30
arrrghhhit isn13:30
*** programmer8922 has quit IRC13:31
arrrghhhit isn't until it detects something near before it'll recognize far.13:31
arrrghhhif that makes ses.13:31
arrrghhhsense*13:31
arrrghhhdamn i can't type today..13:31
arrrghhhor think straight evidently.13:31
emweyou got some strangeness in behaviour actually?13:32
arrrghhhimho, yes.13:32
arrrghhhwith the call issue i can't thoroughly test13:32
arrrghhhbut it seems to be consistent with the zDeviceTest app13:32
arrrghhhassumes something is near when it is first initialized13:32
arrrghhhand doesn't change until you put something near to it, and pull away.  then it'll recognize far.13:33
arrrghhhIMHO it should do the opposite13:33
arrrghhhassume far, until somethings near on first init...13:33
emweit jumps from far to near for me and stays like that13:33
emweyeah13:33
arrrghhhhrm13:33
arrrghhhi'll have to try again13:33
arrrghhhbut IIRC it always starts with near on zDeviceTest13:33
arrrghhhand won't change until i put a finger near, and pull it away.13:33
emweyes, right, what i said13:33
arrrghhhok13:34
emweon userland trigger it jumps from far to near and that's it for me.13:34
arrrghhhah ok.13:35
arrrghhhyea, to me that's improper - and will obviously cause issues for you and anyone else who might have similar problems.13:35
emwewinmo no go.13:37
emwehad to enable it manually though.13:37
arrrghhhdamn...13:38
arrrghhhthat's really odd.13:38
emweman, panel is shiny with the dust away.13:38
arrrghhhlol that's good13:38
emwei dunno what else to do..13:38
arrrghhhyou said LS works tho!??13:38
emweyes.13:38
emweit's not the same "spot" though as i have seen13:38
arrrghhhhm13:38
emweit's the transparent plastic right to earpiece13:39
emweit goes to it's own "chip". if in the end the cm3602 handles the logic is another story. dunno13:39
emwethe prox is 45° down left of color led13:39
emwebetween the htc "c" and color led. on that diagonal line.13:40
emweand there is two sensors sitting there.13:40
arrrghhhoh13:40
arrrghhhinteresting...13:40
emwebut ls must be right to earpiece as when i cover that, ls reports different values13:40
emwenow tell me i shall open it again and try harder, plz.13:44
emweforgotten a foil under the sensor electronics... should harm, though.13:45
emweif disassembly wouldn't have been quite strenious.13:45
arrrghhhseems taking apart the phone to that level would be a PITA13:46
emweyeah, because it's the last part of disassembly.13:47
emweyou have to get everything torn apart to get the screen open from the back.13:47
arrrghhhofc13:47
emwehttp://www.youtube.com/watch?v=SYqNlM68_as&NR=1  <<< this gave me quite some hints13:47
arrrghhhhehe13:47
emwesounds my gf is coming home. going to be a couch evening. i feel sad...13:48
arrrghhhaw13:48
emwewould have been cool.13:48
emwewill post the disassembly pics later. waiting for upload finish...13:49
arrrghhhnicd13:49
arrrghhhnice*13:49
arrrghhhshame about your prox dude13:50
arrrghhhit seems the plug is causing SOD's13:52
arrrghhhit's consistent13:52
arrrghhhso uh... how can i help debug it?  i pulled all sorts of logs, i don't see anything even remotely useful.13:53
*** drakaz has quit IRC13:59
*** heli_bf3 has quit IRC14:01
*** drakaz has joined #xdandroid14:03
emwearrrghhh: for the viewing pleasure: https://www.dropbox.com/gallery/12183048/1/rhod400-disassembly?h=adb67714:23
emweregarding sod debug... i can build a insta plugless kernel. likely not today.14:23
emwesupper time on the couch. laters.14:23
*** helicopter88 has joined #xdandroid14:30
*** DieSchlager has joined #xdandroid15:23
*** DieSchlager has left #xdandroid15:24
*** emwe has quit IRC16:23
*** ringer has joined #xdandroid16:24
*** caliban2 is now known as cal2_afk16:34
arrrghhhi haz your serial numberz16:44
arrrghhh:P16:44
arrrghhhseriously tho, that's awesome16:44
arrrghhhwhat is just above the "sprint" logo?16:45
arrrghhhin uh... pic 5119 - looks like a front facing cam lol16:45
arrrghhhbut that's cool emwe, no worries.  whenever you can make a insta-plugless kernel.16:46
arrrghhhi was more hoping to help debug "why" the insta-plug was causing it16:46
*** ImCoKeMaN has joined #xdandroid16:59
*** helicopter88 has quit IRC17:04
*** programmer8922 has joined #xdandroid17:30
*** ringer has quit IRC17:31
arrrghhhstinebd, did you hear the good news?21:44
arrrghhhemwe seemingly fixed the TI BT explosion21:57
arrrghhhhe threw me a system image that allowed BT to turn on the RAPH80021:57
arrrghhhand i was able to pair, but it didn't connect to my RHOD in WinMo.  not sure what's up with that21:58
arrrghhhi didn't try any other devices, but it scanned and saw a few things to connect to.21:58
arrrghhhso i assume that means its fixed... AFAIK the bug was as soon as you enabled BT, explosions.21:58
*** TheSeven has quit IRC22:55
*** [7] has joined #xdandroid22:56

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