Friday, 2011-10-21

*** rpierce99 has quit IRC00:44
*** BulitPruf has joined #xdandroid03:29
*** BulitPruf has left #xdandroid03:30
*** BulitPruf has joined #xdandroid03:33
*** BulitPruf has left #xdandroid03:33
*** kalemas has joined #xdandroid04:07
*** raffadna has joined #xdandroid04:26
*** hardwalker has quit IRC04:45
*** hardwalker has joined #xdandroid04:46
*** raffadna has quit IRC04:59
*** hardwalker has quit IRC06:23
*** Drgb_ has joined #xdandroid06:50
Drgb_hi there, I have an HTC Touch Pro (raph100) running FRX07.1. I noticed that optional keys in the physical keyboard are not mapped correctly. This should depend on the fact that it's an italian phone, as I've seen the same model with several keyboard layouts on the wiki. Is there any "physkeyboard" option for my layout? If not, how can I write my own layout? Would it require rebuilding the kernel?06:56
*** mgross029 has joined #xdandroid07:54
*** caliban2 has joined #xdandroid08:20
ryannathansDrgb_: look in the rootfs08:22
*** caliban2 has quit IRC08:55
*** virsys has quit IRC10:06
*** rpierce99 has joined #xdandroid10:14
*** virsys has joined #xdandroid10:24
*** |Jeroen| has joined #xdandroid10:33
*** helicopter88 has joined #xdandroid10:33
Drgb_ryannathans: thanks very much, found the keymaps directory, I'll just edit the default keymap10:37
*** caliban2 has joined #xdandroid10:42
*** emwe has joined #xdandroid10:45
mgross029Hey emwe, buenos dias. heh10:46
emweDrgb_: regarding your keys, i dunno the state of the RAPH100 key mapping allthough i have a RAPH100. the keymaps are defined in rootfs repo @ gitorious.org/xdandroid you'd need to track the keycode reported from kernelland and map it to a userland key.10:47
emwehi mgross029.10:48
emwemgross029: regarding bt, yeah, it might be broken in the test kernel. tested out the sleep issue when bt is off10:48
emweunfortunately i have no bt hardware around except my laptop. don't think i can test much with it.10:49
mgross029emwe, Not a problem.  I have a headset and there are plenty of people walking around my office with random bt enabled on their phones I can hack into. :p10:49
mgross029emwe,  After I pulled up the gitorious dashboard and looked at you latest commits to .35 I noticed an entry for the CM3602.  Not sure but I think I found the Far / Near issue in the capella_cm3602.c.10:54
mgross029Here is your commit, https://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/commit/f5778176e0905463a580927c254398c1e94d168910:55
mgross029Should this be D("proximity %d\n", val ? "FAR" : "NEAR"); instead of D("proximity %s\n", val ? "FAR" : "NEAR");?10:55
mgross029%d basically10:55
emwenope, because the strings are printed, not val.10:56
emwebut this doesn't influence the userland reported value at all. just dmesg output.10:56
emweand it's correct. :)10:56
emwethe "possible" - not sure - fix might be in that area of the code though... i think htc is reading out the gpio value several times in order for it to stabilize and then they report back.10:57
emwebut unless my prox hardware isn't fix, i won't come around to do much in that area.10:57
mgross029Ok...  The reason it stuck out to me is I pulled up another capella_cm3602.c and from another site and it showed %d10:57
emweyeah, but it only printed the value originally10:58
emwebut i changed to actually print a human readable value.10:58
mgross029Ahh. Makes sense that is why the "FAR" : "NEAR"10:59
emweproximity 1 is what? one could interpret it as near.. but it actually is far. that's why printing the string literal10:59
emweval is evaluated. if true (!= 0) FAR, otherwise NEAR11:00
mgross029Yep, understood that part.  Thanks11:00
emwemgross029: http://dl.dropbox.com/u/12183048/htctopaz/dot35/kernel-packages/linux-msm-2011-10-21-A-3c92c74-package.zip << this is a build with the instant plug notification disabled. we had to disable on .27 as well as it provoked many SODs. so if your SODs get better, i will pack my bags and leave.11:01
mgross029Still learning and following logic to see if I can help further.  I know everyone is swamped with rl these days11:01
emwei really whonder why my TOPA and RHOD here don't SOD with this instant plug notification enabled...11:02
mgross029heh well I don't think you need to do that...11:02
mgross029It could be another problem with your devices.  Like prox. :)11:03
emwehighly unlikely as topa has no prox :P11:03
mgross029Just failing equiment I meant. :p11:03
emwemgross029: you ever tried to pair with a device having to confirm a "number"?11:04
emwei don't get any confirumation popup on the phone.11:04
mgross029There are times where that will pop and other times where it does not11:04
emwehm never seen it. bummer.11:05
mgross029Things got really messy on this gb build with all of the kernel changes so I am killing the data.img and starting fresh.  I'll test out with the latest kerenl ^^ first to let you know how that works11:06
emweok11:06
emwebt *might* be still broken.11:06
emwei don't have much to test out.11:07
emwebut with the latest autobuild bt was ok for you, yes?11:07
emwe(except the bt-off-sleep-bug, right?)11:07
mgross029with autobuild .35 all bt seemed to work normally11:08
emweok, good.11:08
mgross029Always had it bt on so that wouldn't have effected me11:08
emweit's a super upside-down bug that when bt is enabled it sleeps fine, off not. that's totally inverse to what we usually have happen :)11:08
mgross029Yeah from what I tested this morning I had no problems with the phone sleeping11:09
mgross029emwe, Just loaded the build, paired an bt headset, it prompted me for the 4 digit pairing code.11:24
emwehmpfs.11:24
emwei need a bt headset. now.11:24
stinebdwant me to order you one with warchest money?11:24
mgross029Actually made a call and it routed audio properly.  Also noticed on this kernel after it detected the bt the screen went from off to on11:25
stinebdwe got a bit over $500 in the account11:25
mgross029emwe, The bottom hard keys are staying lit just as before.  Going to connect usb now and let the screen shut off to test SOD11:26
emwestinebd: you can share some warchest after the next releases.11:26
emwemgross029: well, that is actually a "feature" in autobacklight mode imho.11:27
mgross029lol11:27
emwedid they ever turn off on any other release?11:27
mgross029Yes all others did11:28
emwemgross029: ah no, sorry. you are on .35. and you had them lit in wince when starting haret.11:28
emwemgross029: i haven't managed to put button lights in, yet.11:28
mgross029Not a problem.  Just an observation I was informing you about.11:29
emwejust a missing piece ...11:29
mgross029SOD on usb still.  Can't get adb to connect either11:29
emwemgross029: this is good news :P11:30
emweit's not the instant plug notification then.11:30
mgross029So you can keep you're clothes in the closet. :p11:30
emwewell, we need to move anyway. a 2 room flat is too small.11:30
mgross029s/you're/your11:30
mgross029Well that is for other reasons, not for the instant plug notification :)11:31
emweyeah, we call "it" roomer for the time being.11:34
mgross029emwe, I can donate my headset to you if you'd like.  I've only used it when testing in my office. :)  Only really use bt when in my car.11:36
emwemgross029: thanks for the offer, but there#s too much overhead in shipping really11:42
emwei'll go fine one. just never did much with bt...11:42
emwes/fine/find11:42
mgross029Yeah shipping is terrible anymore but I would be happy to send it.11:48
emwewow, can become quite expensive these little beasts..11:48
emweit's ok, thanks for the generious offer.11:48
emwebut i'd be easier to just buy one. my gf could at least make use of it in her car when required11:49
emweor me...11:49
*** programmer8922 has quit IRC11:49
emwedon't have a free speech thingy in my car either.11:49
mgross029Understood...  You can tell her you're buying it for her.11:51
mgross029:p11:51
mgross029Also, the H710/H720/H730 usually are pretty cheap online.  I paid $25 USD for mine11:52
emweshe's buying enough stuff, no reason for an argumentation :)11:52
mgross029lol11:52
mgross029But that is what they do. :p11:53
mgross029Switching back to the autobuild .35 kernel now11:53
emweH730 not available here. H720 for 52€ @ amazon. that is ehm...ridiculous compared to your $25 USD11:54
mgross029Yeah I looked around and found on at site other than Amazon.  Amazon wanted $50 USD at the time I bought the H710 iirc11:58
*** Drgb_ has quit IRC12:26
emwewow, ICS in the emulator feels as slow as GB12:35
stinebdfeels as slow as gb on our phones or gb in the emulator?12:42
emweactually both12:44
emwethis C2D T9600 actually resembles our msm quite good regarding speed in qemu12:44
emwethey are not too far off. the phone even feels a tad bit snappier at times.12:44
emweand agreed, ICS is a tad bit slower in the emulator compared to GB after looking around a bit.12:45
emwereally feels like our device speeds though... apps taking a while to open and so on..12:45
mgross029emwe, I captured some further info on the SOD here is a pastebin of dmesg and logcat when the phone went to sleep while connected to USB. http://pastebin.com/2iwfH2Ga13:09
mgross029The 22.10-21 13:06:55.224 E/SurfaceFlinger( 1311): ioctl(26, VT_RELDISP, 1) failed 22 (Invalid argument) does not look good13:15
emwemgross029: ok, i'll take a look.13:17
mgross029Did a grep on my local repo and it looks like that line is reported in DisplayHardwareBase.cpp in frameworks_base13:17
*** |Jeroen| has quit IRC13:23
mgross029I noticed this difference in .27 I found this linux-msm/fs/compat_ioctl.c:ULONG_IOCTL(VT_RELDISP), when I did a grep on .35 it did not show up.  Hope that provides some help.13:23
emweoh!?13:29
emweok, remember that information when i got a bit more time. I have no idea it is the solution... just got no idea about anything. :)13:30
mgross029Not a problem.  Just throwing that out there to see if it helps.  Since that looks like it could be kernel fs which some of that isn't being built yet in .35 iirc.13:42
*** programmer8922 has joined #xdandroid14:23
*** rpierce99_ has joined #xdandroid14:37
*** rpierce99 has quit IRC14:38
*** rpierce99_ is now known as rpierce9914:38
*** detule has joined #xdandroid14:44
*** programmer8922 has quit IRC14:49
detulemgross029, try disabling FRAMEBUFFER_CONSOLE in arch/arm/configs/htc_msm_android_defconfig14:50
emwehey detule. might to elaborate?14:59
detulein displayhardwarebase, checks for presence of /sys/class/graphics/fbcon before using the undefined ioctl in releaseScreen....(at least from what i gather)....disabling fbcon should force it to use something more benign15:15
detulecould be a quick way of checking if this is what is causing whatever issues mgross029 is experiencing ....15:16
emwespeaking of issues.. had a sod before.. wouldn't enable screen again... yay.15:17
mgross029detule, Thanks I'll check it out in a moment15:17
mgross029Recreating errors is so much fun. :p15:18
detulebeware without fbcon, not sure what exactly you'll see on boot - perhaps emwe's got insight on booting with fbcon disabled15:19
emwedetule: unfortunately i have no idea. we'll likely see black until bootani.15:19
detulehear that mgross029 - don't freak out when no flying text15:20
mgross029Nah... It's a feature :p15:20
mgross029I'll feel like I'm back in Winblows15:21
mgross029heh15:21
detulerpierce99, these should hopefully rid you of all the dmesg and logcat prox spam http://dl.dropbox.com/u/38520332/prox/prox2.tar.gz15:30
rpierce99thanks15:30
emweah, which reminds me, i left debug enabled on gb ...15:32
mgross029Yeah...  No kidding. :p15:32
mgross029I constantly see the prox messages. :)15:33
mgross029detule, I did have a simple work-around for the problem.  I just enabled Stay Awake when on charger in Application -> Developement15:43
mgross029SOD has only happened for me so far in gb and .35 when I am connected to USB15:45
*** kalemas has left #xdandroid15:52
*** detule has quit IRC16:11
*** Kraln has quit IRC16:21
*** Kraln has joined #xdandroid16:23
*** caliban2 has quit IRC16:23
*** caliban2 has joined #xdandroid16:25
emwestinebd: what's the deal with switching a remote to git://android.googlesource.com, it's just not editing manifest.xml?16:26
emweah.. https://?16:27
emweah lol, ok. forget.16:27
*** helicopter88 has quit IRC16:36
*** programmer8922 has joined #xdandroid16:42
*** programmer8922 has quit IRC16:54
*** caliban2 has quit IRC17:02
*** mgross029 has quit IRC17:08
*** blue_byte has joined #xdandroid17:28
*** XirXes has quit IRC17:31
*** blue_byte has left #xdandroid17:38
*** fishhead2567 has quit IRC18:01
*** emwe has quit IRC18:09
*** phh has quit IRC18:09
*** phh has joined #xdandroid18:10
*** emwe has joined #xdandroid18:11
*** emwe has joined #xdandroid18:11
*** XirXes has joined #xdandroid18:13
*** emwe has quit IRC18:50
*** rpierce99 has quit IRC19:41
*** rpierce99 has joined #xdandroid21:20
*** arrrghhh has quit IRC21:22
*** arrrghhh has joined #xdandroid21:26
*** rpierce99 has quit IRC21:40
*** Recnamoruen has quit IRC22:05
*** tiad8 has joined #xdandroid22:06
tiad8been long time guys22:07
ryannathans-.-22:08
ryannathansgoing to come steal more work?22:08
tiad8no my friend, i'm not here to fight we no one22:09
tiad8i just need to ask acl a quick question. if he let me22:11
*** [7] has quit IRC22:26
*** TheSeven has joined #xdandroid22:26
*** rpierce99 has joined #xdandroid22:31
*** NiteSnow has left #xdandroid22:40
*** tiad8 has quit IRC22:41
*** programmer8922 has joined #xdandroid23:13

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