| d3tul3 | could be an easy check for all this | 00:00 |
|---|---|---|
| d3tul3 | i think most of the acoustic business is disabled if the libs can't find /dev/htc_acoustic_wince | 00:00 |
| d3tul3 | and we are currently chmoding that one in the rootfs | 00:00 |
| d3tul3 | comment out the chmod make it inaccessible, i think the libs then default to old_style routing | 00:01 |
| bzo | that's a good tip, I'll give it a try | 00:01 |
| *** rpierce99 has quit IRC | 00:11 | |
| bzo | bingo, camera works | 00:12 |
| d3tul3 | without acoustic? | 00:12 |
| bzo | yeah | 00:12 |
| bzo | I have a feeling that if you use the phone for a while so that acoustic starts using a different pmem region | 00:13 |
| bzo | the camera works sometimes | 00:13 |
| bzo | but from a fresh boot, seems to clash | 00:13 |
| bzo | I'm just glad I got lucky and caught it working with the first fix | 00:14 |
| d3tul3 | uh this pmem business with acoustic could be the source of a lot of grief | 00:14 |
| bzo | that at least got us working at single factors | 00:14 |
| bzo | yeah, acoustic does not seem to be playing nice | 00:15 |
| d3tul3 | good job on tracking that down - good night | 00:20 |
| bzo | thanks to your tip :) | 00:21 |
| bzo | gn | 00:21 |
| *** d3tul3 has quit IRC | 00:21 | |
| *** bzo has quit IRC | 01:09 | |
| *** kalemas has joined #xdandroid | 02:24 | |
| *** drakaz has quit IRC | 04:03 | |
| *** drakaz has joined #xdandroid | 04:23 | |
| *** hardwalker has quit IRC | 05:22 | |
| *** mgross029 has joined #xdandroid | 08:19 | |
| *** SytheZN has joined #xdandroid | 09:01 | |
| SytheZN | Greets | 09:01 |
| SytheZN | what are the most likely causes of a corrupted data.img? | 09:02 |
| *** SytheZN has quit IRC | 09:06 | |
| *** SytheZN has joined #xdandroid | 09:07 | |
| *** helicopter88 has joined #xdandroid | 09:09 | |
| *** rpierce99 has joined #xdandroid | 09:10 | |
| *** fishhead2567 has joined #xdandroid | 09:11 | |
| *** Sythe_ZN has joined #xdandroid | 09:13 | |
| *** SytheZN has quit IRC | 09:13 | |
| *** SytheZN has joined #xdandroid | 09:14 | |
| *** Sythe_ZN has quit IRC | 09:14 | |
| *** SytheZN has quit IRC | 09:14 | |
| *** rpierce99 has quit IRC | 09:17 | |
| *** rpierce99 has joined #xdandroid | 09:31 | |
| *** rpierce99 has quit IRC | 09:32 | |
| *** kalemas has left #xdandroid | 09:47 | |
| *** emwe has joined #xdandroid | 10:10 | |
| emwe | mgross029: need to get some stuff sorted before i get back to you... | 10:12 |
| *** mgross029 has quit IRC | 10:13 | |
| detule | hey emwe it occurred to me that any lingering SODs you may have in .35 may be microp-keypad related | 10:14 |
| emwe | detule: i am listening ... haven't caught up with any patches. just read your last nights convo | 10:14 |
| detule | Alex mentioned this yesterday in #htc-linux and this was my experience as well -> i would get green light sods as soon as the phone would go into suspend after bringing microp-keypad from your tree | 10:14 |
| emwe | have you seen sth like gpio_get_value() issues in some traces? | 10:15 |
| emwe | i think i had something strange quite recently. | 10:15 |
| detule | anyways this is probably a consequence of the fact of slight differences in implementation perhaps....but at any rate, there's no reason to have those suspend calls in microp_keypad | 10:16 |
| emwe | microp-keypad is a 1:1 of alex' | 10:16 |
| emwe | the wq syncs? | 10:16 |
| detule | there's a cancel_sync as well as a led_trigger making sure the kbd bcklight is off | 10:16 |
| detule | the led trigger can safely go into the suspend hook of your board file | 10:16 |
| emwe | question is do we need both, led trigger and userland doing it? | 10:17 |
| detule | also instead of cancel sync, do a flush workqueue | 10:17 |
| emwe | perhaps that's where stuff acts up? | 10:17 |
| detule | that's a question for another day | 10:17 |
| emwe | you got stuff pushed out so i can look later? | 10:17 |
| emwe | readying up for kexec... | 10:17 |
| emwe | still need .35 kernel modded regarding clock_late_init | 10:18 |
| detule | https://gitorious.org/linux-msm-rhod/linux-msm-rhod/commit/614498f3496519016eadf0124566fceb34beb192 | 10:18 |
| emwe | and regarding location... dunno if we'll have a shitload of mods to the files. i am gogin to push kexec+.sh to system image. | 10:18 |
| detule | just keep in mind that with hyc's patch shutdown really does a reboot | 10:19 |
| detule | btw, is the LS/auto_bl in .35 working as it should? | 10:20 |
| detule | with ACL's driver i could not get auto_bl to turn off | 10:20 |
| emwe | it's all fine here. otherwise i wouldn't have moved on. actually auto-bl was kinda of the first things working | 10:20 |
| detule | you're going to make me boot .35 | 10:21 |
| emwe | there's all kinds of crazyness... i finally added ksc button lights support and mgross said they were working all the time for him on .35 | 10:21 |
| emwe | not for me... | 10:21 |
| emwe | so on RHOD500 setting button lights like for TOPA was working for him | 10:21 |
| emwe | not for me. | 10:21 |
| detule | like i kept seeing ioctl enables being sent from userland to the LS even after i unchecked auto-brightness in settings | 10:22 |
| detule | as in perhaps being an issue with libsensors rather than the kernel | 10:22 |
| emwe | you can enable debugging in the sensor classes. | 10:22 |
| emwe | btw, where's the microp-keypad stuff you mentioned earlier? | 10:23 |
| emwe | am i mixing things up? | 10:23 |
| detule | https://gitorious.org/linux-msm-rhod/linux-msm-rhod/commit/614498f3496519016eadf0124566fceb34beb192 | 10:23 |
| detule | couple of other things in there as well | 10:24 |
| detule | but moving the suspend stuff out of microp-keypad into board-*-led is also there | 10:24 |
| emwe | ehm, where? sorry i am sick and apparently my brain isn't up to par, but where? there's no microp-keypad.c mods | 10:25 |
| detule | hm perhaps i am not seeing well when i click on that link the last file that is modded on that page is microp-keypad | 10:27 |
| emwe | detule: bzo: regarding pmem memory, you guys got this from jb? https://gitorious.org/~ast/linux-on-qualcomm-s-msm/alex-linux-xperia/commit/524d6e8264d3346a4d0d9b1b98017d90fad5dee3 | 10:27 |
| emwe | fawk... | 10:28 |
| emwe | i opened up the last commit on gito page and thought it was it. sorry. | 10:29 |
| emwe | detule: shouldn't userland take care of all that? i mean it does except for caps/fn in some situations... | 10:34 |
| detule | ideally i guess, there are other spots in microp-keypad where we are triggering on the backlight ? every key-press? | 10:35 |
| detule | you are saying take all of it out? | 10:35 |
| detule | or no | 10:35 |
| detule | wait this is for keypad | 10:35 |
| detule | i guess buttons | 10:35 |
| emwe | userland is controlling all here imho. | 10:36 |
| detule | ok emwe i have auto_bl question....how come auto_bl is working fine over here without acl's driver | 10:37 |
| detule | just with the auto_bl enable disable in the board file | 10:37 |
| emwe | the ls driver has no cool use at all... might take a bit to write down.... one sec. | 10:37 |
| detule | this is the LCD auto-backlight i guess -> should i expect other backlights to be broken since userland i assume is not reading values from the light sensor | 10:37 |
| emwe | when auto_bl=1 the lcd itself manages the lcd brightness by directly reading the sensor. reporting "correct" lumen to userland via ls-driver just makes userland set button and keyboard (and lcd brightness) based on the autorbightness arrays in the overlay config.xml (we are ignoring userland setting a lcd backlight value in liblights when auto-mode is in place. we could also pass it on to userland) | 10:39 |
| emwe | we are "misusing" auto-bl in the terms userland thinks it should work | 10:40 |
| emwe | ideally we'd be never enabling hw-controlled auto-bl in kernel | 10:40 |
| emwe | but always rely on the lumen->overlay-table->liblights cycle. | 10:40 |
| detule | i see thanks for that, i suspected this hw-controlled auto-bl | 10:40 |
| emwe | this is more or less we've been doing so for always. | 10:41 |
| emwe | just that we now report "good" values to userland. | 10:41 |
| detule | and these values are only used for kbd and buttons | 10:41 |
| emwe | yes, liblights ignores lcd-bl when automode=1 | 10:42 |
| detule | ok perhaps i shouldn't touch those led triggers in microp-keypad without figuring out how to incorporate acl's driver | 10:42 |
| emwe | well, evaluate first if the led trigger really triggers | 10:42 |
| emwe | because always on boot - when android chimed in here - the led trigger for keyboard-backlight was reset to none | 10:42 |
| detule | i swear i got frustrated at one point and copy pasted from your tree, and i got the same outcome, could not shut the damn auto backlight OFF | 10:42 |
| emwe | you can cat the led_trigger atrribute ( i think that was the name) and see if it is set | 10:43 |
| emwe | it has always reset for me on boot | 10:43 |
| emwe | so might be the trigger isn't acting... btw... it won't. you haven't set the trigger in rhod-led.c iirc. i skipepd it also | 10:44 |
| detule | this in htc_ls_microp? | 10:44 |
| emwe | nah, the led_trigger i mean... it's set for the keyboard-backlight led device | 10:44 |
| emwe | and i was wrong, you kept it in rhod-led file.. | 10:44 |
| emwe | .default_trigger = "microp-keypad", | 10:45 |
| detule | oh yeah yeah sorry | 10:45 |
| emwe | michael@think:~> adb shell cat /sys/class/leds/keyboard-backlight/trigger | 10:45 |
| emwe | [none] rfkill0 microp-keypad mmc0 mmc1 timer heartbeat sleep battery-charging-or-full battery-charging battery-full usb-online ac-online rfkill1 | 10:45 |
| emwe | ^^ initially it's on and short after android starts up it's reset. | 10:46 |
| detule | really | 10:46 |
| detule | that's strange i guess could be causing all sorts of issues | 10:46 |
| emwe | so the led trigger might not actually do something. | 10:46 |
| emwe | perhaps the search for a matching led takes so much time :) | 10:47 |
| emwe | btw, which io scheduler are you guys using on .39? | 10:47 |
| detule | back to noop | 10:47 |
| detule | though the deadline test was skewed since lmk wasn't working back there | 10:48 |
| emwe | i added ~2GB of mp3 and i had three freezes/SODs until it finished scanning though. | 10:48 |
| *** fishhead2567 has quit IRC | 10:48 | |
| emwe | i think i wen't cfq->deadline because of IO .. but this was before lmk patches. | 10:48 |
| emwe | i had wake SODs often just when RHOD was on... | 10:49 |
| emwe | so much stuff to figure... pita. | 10:49 |
| detule | my trigger is set to none as well | 10:49 |
| emwe | when you are quick and you cat immedeatly when adb chimes in, you can still see it set to microp-keypad | 10:50 |
| emwe | adb wait-for-device shell cat .... | 10:50 |
| detule | that's so strange :) | 10:50 |
| detule | perhaps userland claims it somehow | 10:50 |
| emwe | might be kernel led framework resets the trigger whenever something external calls the sysfs brightness hook? | 10:51 |
| emwe | as otherwise one would use led fx methods to trigger | 10:51 |
| emwe | aka led_trigger_event() | 10:51 |
| detule | sounds to me like all those led_trigger calls then are ripe for the taking-out | 10:52 |
| emwe | in case of android-userland likely, yes :) | 10:52 |
| emwe | i think alex had something in mind when doing it like that. | 10:52 |
| emwe | SHR or whatnot. | 10:53 |
| emwe | but really, then it's the distros issue, not kernels... | 10:53 |
| detule | btw the qdsp5 patches are in the 39 tree | 10:53 |
| detule | this pmem business with acoustic could be the reason behind some of the acoustic bugs | 10:54 |
| emwe | perhaps it's worth diffing to alex' android-2.6.35 tree and look for diffs? | 10:55 |
| detule | and in .39 there are these built-in debugging messages in pmem that spew all over dmesg about mapping protected regions | 10:55 |
| emwe | bzo's patches had some more changes then alex has/did | 10:55 |
| emwe | i think i'll let you guys figure cam :) | 10:55 |
| emwe | somebody burried me with userland work... who was it again? | 10:55 |
| emwe | btw, is bma150 working on .39 in terms of userland integration? | 10:56 |
| emwe | might be some missing piece, or rather something i broke in libsensors. | 10:56 |
| detule | well it was working in 06+ before i deconstructed microp-klt last night | 10:56 |
| emwe | ok | 10:56 |
| emwe | i am out a bit. coffee time. | 10:56 |
| detule | bzo pointed out last night there's some interaction re: the spi bus between -klt and bma? | 10:56 |
| detule | i'll talk to you about it some other time later | 10:56 |
| emwe | spi should only be topa iirc | 10:56 |
| emwe | yeah ;) | 10:56 |
| emwe | spi=off had been wake issue on topa for some time... | 10:57 |
| emwe | anyway, laters :) | 10:57 |
| *** mgross029 has joined #xdandroid | 10:57 | |
| mgross029 | emwe, not a problem. when you have time | 10:58 |
| *** rpierce99 has joined #xdandroid | 11:01 | |
| *** helicopter88 has quit IRC | 11:04 | |
| *** helicopter88 has joined #xdandroid | 11:04 | |
| *** fishhead2567 has joined #xdandroid | 11:08 | |
| *** fishhead2567 has quit IRC | 11:11 | |
| *** fishhead2567 has joined #xdandroid | 11:11 | |
| *** fishhead2567 has quit IRC | 11:19 | |
| *** fishhead2567 has joined #xdandroid | 11:19 | |
| *** fishhead2567 has quit IRC | 11:22 | |
| *** fishhead2567 has joined #xdandroid | 11:22 | |
| emwe | mgross029: yeah, busy as usual... | 11:56 |
| emwe | stinebd: got a minute? | 11:58 |
| NeoMatrixJR | anyone know if something broke bluetooth? I had it working at one point... I know I did. I'M NOT CRAZY! | 12:22 |
| rpierce99 | something = you | 12:31 |
| rpierce99 | bluetooth still works, assuming you boot winmo with bluetooth disabled and you don't have the pandora app installed | 12:31 |
| rpierce99 | i believe those are the 2 current caveats | 12:31 |
| NeoMatrixJR | huh | 12:39 |
| NeoMatrixJR | Well, I pulled out an old backup and it works... so something I've done along the way must have killed it in my current loadout... | 12:40 |
| NeoMatrixJR | bluetooth has to be disabled when winmo boots up or when you boot xdandroid? | 12:40 |
| *** |Jeroen| has joined #xdandroid | 12:51 | |
| rpierce99 | both | 12:59 |
| rpierce99 | you don't want winmo to initialize the hw at all | 12:59 |
| *** kalemas has joined #xdandroid | 13:05 | |
| mgross029 | emwe, did we go back to fast instead of jit? | 13:18 |
| emwe | looks like, yeah. according to bzo and detule they found it better. at least not worse. | 13:19 |
| emwe | i think you where ok with fast, too. arrrghhh also. | 13:19 |
| |Jeroen| | my experience is that jit makes it a lot faster | 13:20 |
| mgross029 | I was good either way. jit or fast | 13:21 |
| mgross029 | I'm still running jit at the moment | 13:21 |
| emwe | |Jeroen|: can't notice a real difference. except for synthetic benchmarks. | 13:21 |
| *** AndersG has joined #xdandroid | 13:21 | |
| |Jeroen| | i sure noticed it | 13:21 |
| |Jeroen| | whitout benchmarks | 13:22 |
| emwe | i've been running with JIT on GB for some months now and since yesterday without. can't spot really any obvious difference in daily use. | 13:24 |
| mgross029 | As long as it works it doesn't really matter I guess. :p | 13:24 |
| emwe | we are talking GB, though. on froyo it might be quite different. | 13:24 |
| mgross029 | tru | 13:25 |
| |Jeroen| | i was talking froyo, it was damm slow whitout it | 13:25 |
| |Jeroen| | didn't try ginger without jit jet | 13:25 |
| emwe | which ginger? GBX0A? | 13:25 |
| |Jeroen| | i build my own GB a few weeks ago | 13:26 |
| |Jeroen| | works great except for the new market and gps | 13:26 |
| mgross029 | Hmmm Maybe that can go as an option in arrrghhh's speed improvment section on xda for froyo | 13:26 |
| emwe | gps? worksforme | 13:26 |
| |Jeroen| | mine reboots on gps fix | 13:26 |
| emwe | which device? | 13:27 |
| |Jeroen| | diam100 | 13:27 |
| emwe | oh. | 13:27 |
| emwe | raph100 is fine here iirc. | 13:27 |
| emwe | had been using it for fixing gps on gb the whole time. | 13:28 |
| |Jeroen| | mhhz with app u use ? | 13:28 |
| emwe | mhhz? | 13:28 |
| |Jeroen| | i only tied andnav and navigon | 13:28 |
| |Jeroen| | both rebooted | 13:28 |
| emwe | "GPS Test" by chartcross ltd | 13:29 |
| emwe | but these all rely on the gps library | 13:29 |
| emwe | it shouldn't matter which app | 13:29 |
| emwe | i am navigating fine with the RHOD here... | 13:29 |
| mgross029 | waze is a good one too | 13:29 |
| mgross029 | nav app that is. | 13:30 |
| emwe | anyway, think we need to pursue this later. already burried with a shitload of stuff... | 13:30 |
| emwe | |Jeroen|: don't forget to mention the issue once in a while... | 13:30 |
| |Jeroen| | yeah its not a priority | 13:30 |
| |Jeroen| | k will do | 13:30 |
| NeoMatrixJR | does anyone know if we're still using brcm_patchram_plus to initialize bluetooth? I'm trying to port some of the work to get this chipset working over to another project. I just pulled apart our stuff and I can't find references to it anymore (other than the file exists) | 13:30 |
| emwe | system/bluetooth repository. and yes, still used. | 13:31 |
| emwe | laters. supper time. | 13:31 |
| mgross029 | emwe, later | 13:31 |
| NeoMatrixJR | tried checking the bt repo...I keep getting a "too many redirects" error | 13:42 |
| *** |Jeroen| has quit IRC | 13:45 | |
| mgross029 | NeoMatrixJR, https://gitorious.org/xdandroid/system_bluetooth/trees/froyo | 13:55 |
| mgross029 | NeoMatrixJR, Link right to brcm_patchram_plus https://gitorious.org/xdandroid/system_bluetooth/trees/froyo/brcm_patchram_plus | 13:57 |
| *** SytheZN has joined #xdandroid | 13:57 | |
| emwe | stinebd: i have some prebuilt binaries. will git preserve the permission bits so they are good/same when image is built? | 14:20 |
| SytheZN | I've installed java5, but I'm getting the incorrect version error... any thoughts? | 14:33 |
| emwe | detule: you had to add the clock-wince.c patch from hyc on .39? | 14:33 |
| emwe | apparently not, just whondering... | 14:34 |
| detule | for kexec? | 14:35 |
| detule | kernel was kexec enabled dating back to june | 14:35 |
| detule | it was all jonpry's doing way back when | 14:35 |
| emwe | yeah, clocks look like .35... so .. | 14:36 |
| emwe | guess it's save. | 14:36 |
| emwe | trying on .27 with raph first, though ;) | 14:36 |
| detule | clocks should be identical | 14:37 |
| emwe | ok, that didn't work... | 14:37 |
| emwe | raph resets. | 14:37 |
| emwe | just executing the script should also do i take it? | 14:38 |
| emwe | you been running loop mounted or partitioned? | 14:38 |
| *** fishhead2567 has quit IRC | 14:39 | |
| emwe | [ 320.778472] init: kexec.sh failed, errno 2: No such file or directory | 14:39 |
| emwe | oopsi. | 14:39 |
| detule | :) | 14:39 |
| detule | i am currently looped | 14:39 |
| emwe | ^^ does this say something to you? | 14:40 |
| emwe | i mean the error. | 14:40 |
| emwe | wtf.. where is the binaries. | 14:40 |
| emwe | nah... | 14:40 |
| emwe | ok, not copied to the image... err... | 14:41 |
| detule | you sound like you need some sleep friend | 14:41 |
| emwe | well, what shall i say if the android build system sucks? | 14:42 |
| emwe | it's in out.. msm/system/xbin/ but not in the generated image. just mounted and checked. | 14:42 |
| detule | push the damn things in | 14:43 |
| emwe | nevertheless the whole image must be complete. that's what i am doing besides... | 14:43 |
| detule | perhaps something similar to what we are doing with the gapps binaries needs to be done to the kexec binary | 14:43 |
| detule | aren't we copying them over from vendor/ | 14:43 |
| emwe | ai, kexec'ing now :) | 14:44 |
| emwe | just pushed by hand... | 14:44 |
| emwe | worki worki | 14:44 |
| detule | doesn't that put a smile on your face | 14:44 |
| emwe | yes. now .35 :P | 14:45 |
| emwe | ok, and to repeat android build system sucks | 14:45 |
| emwe | deleted system.img and ./system/xbin/ from "out" and make'd again. now it's in. | 14:45 |
| emwe | this is what i mean. | 14:45 |
| emwe | you said something about a shutdown is actually a reboot now? | 14:46 |
| emwe | there's that additional return; statement in the reboot section of ShutdownThread, though it looks entirely legit. | 14:46 |
| emwe | allthough it wasn't before.. | 14:46 |
| SytheZN | can I ignore the java version check in the makefile or is there somethin else i need to do? | 14:48 |
| detule | wasn't some patch applied to frx to fix the shutdown=reboot issue | 14:49 |
| rpierce99 | shutdown still = reboot to windows for me | 14:49 |
| detule | 7.1? | 14:50 |
| detule | or maybe it's just GB that has that fixed and we are now in the process of breaking again | 14:50 |
| *** fishhead2567 has joined #xdandroid | 14:50 | |
| AndersG | For me shutdown sometimes just reboots android (FRX7.1), a second shutdown usually really shuts down the phone, though. | 14:50 |
| emwe | sometimes it seems on clean data it's shutdown'ing fine. | 14:51 |
| emwe | after some time it won#t do so anymore. but i am seldomly shutting down ;) | 14:51 |
| detule | i don't really care about shutting down much either | 14:51 |
| emwe | detule: raph shut down good just now. | 14:52 |
| detule | but hyc's patches they are pretty elaborate -> shutdown now goes through init right? | 14:52 |
| emwe | yes. this what i grasp from the system/core patches. | 14:54 |
| emwe | i think i should have pursued kexec earlier. it's like 5 minutes saved per new kernel build testing. | 15:03 |
| mgross029 | Is that something in your build system? | 15:04 |
| emwe | nah, ability to load an alternate kernel into ram and restart it. | 15:04 |
| emwe | so you don't have to go through wince again | 15:05 |
| emwe | saves a shitload of time. | 15:05 |
| *** fishhead2567 has quit IRC | 15:06 | |
| *** fishhead2568 has joined #xdandroid | 15:06 | |
| mgross029 | Ahhh... That's a nice feature... | 15:07 |
| mgross029 | Sure would save me a lot. | 15:07 |
| *** SytheZN has quit IRC | 15:12 | |
| NeoMatrixJR | mgross029: thanks for pointing out the patchram, but I was looking to where it was being called. I found it though. The init.froyo.rc called an hciattach in the rootfs that called it (for rhod only). | 15:19 |
| mgross029 | NeoMatrixJR, Yep. Didn't see you asking that question. Glad you found it | 15:20 |
| *** fishhead2568 has quit IRC | 15:21 | |
| *** fishhead2567 has joined #xdandroid | 15:24 | |
| *** drakaz has quit IRC | 15:30 | |
| emwe | detule: i am frightened. worked on .35 RHOD after enabling KEXEC kernel option. | 15:32 |
| emwe | of course it just died on me... WSOD with panel on... | 15:33 |
| *** drakaz has joined #xdandroid | 15:34 | |
| *** fishhead2567 has quit IRC | 15:39 | |
| detule | cool so very little work done to enable it on the kernel side | 15:40 |
| emwe | yeah. whondering why the clock_late_init() is ok to be performed. but cool thing. | 15:47 |
| emwe | thanks for being so insistent getting it in and thanks hyc for work! | 15:47 |
| detule | yeah hyc was well ahead of the curve on that one | 15:48 |
| *** fishhead2567 has joined #xdandroid | 15:48 | |
| detule | emwe, i hate to be the bearer of bad news | 15:50 |
| emwe | i hate when i read this. | 15:50 |
| detule | but i just booted .35 and looks like, here as well hw auto_bl can not be turned off | 15:50 |
| emwe | so it always auto-changes when you change the light conditions? | 15:51 |
| emwe | even when set to manual mode? | 15:51 |
| detule | yes | 15:51 |
| emwe | you got the sysfs entry for auto-backlight i take it? | 15:52 |
| emwe | is it getting called? | 15:52 |
| detule | i am pretty sure it is i dont have adb going on right now | 15:52 |
| emwe | you can echo to the lcd-backlight/autobacklight attribute by hand? | 15:52 |
| emwe | ok | 15:52 |
| detule | auto_backlight is set to 0 | 15:53 |
| detule | i don't think it's the board-*-led auto_bl enable disable function that's the problem, i think it's some weird interaction with the ls_microp that's causing this | 15:54 |
| detule | i need to check back in .39 but i think without the ls driver i can disable the hw backlight fine | 15:54 |
| emwe | i assume you don't have htc_ls_microp.c pushed yet to your tree? | 15:57 |
| emwe | i don't see it. | 15:57 |
| detule | no, i have it locally | 15:57 |
| emwe | k | 15:57 |
| emwe | perhaps it's worth comparing to .35 | 15:57 |
| detule | what is? | 15:57 |
| detule | i am saying this is happening on your .35 | 15:58 |
| detule | and was also happening with .39 with the identical setup (ls_microp included) | 15:58 |
| emwe | ouch, sorry. perhaps i really need some rest. | 15:58 |
| emwe | sickness is a pita. | 15:58 |
| detule | you see it on your rhod? | 16:03 |
| emwe | <7>[ 1697.575561] microp_led_set_auto_backlight: off (0) | 16:04 |
| detule | sure i just cat-ed the auto_backlight param and it's set to 0 the logic is working fine | 16:05 |
| detule | however the hw auto-bl still functions | 16:05 |
| mgross029 | Does this have to also do with the buttons staying on when the phone is awake? | 16:08 |
| emwe | this is userland behaviour mgross029. | 16:09 |
| emwe | mgross029: it's still totally puzzling the buttons where always on for you before i added support for them... | 16:09 |
| detule | did he boot with them on? | 16:09 |
| emwe | i am off'ing them on boot | 16:09 |
| emwe | well hmm. | 16:10 |
| emwe | mgross029: good question by detule... you haven't had them lit when haret'ing, no? | 16:10 |
| mgross029 | Actually the buttons would come on and go out normally before. Now they are enabled all the time. | 16:10 |
| emwe | absolutely strange. | 16:10 |
| mgross029 | I've hit that bug before too and know to wait until they go out. | 16:10 |
| emwe | i need to test on the topa how userland behaves | 16:10 |
| mgross029 | If I put the phone to sleep with the top button they go out. | 16:11 |
| emwe | mgross029: you can now safely boot with all lit what is possible. it's all unlit on boot now ;) | 16:11 |
| detule | yeah i see the enable all the time here as well, are the lux xml tables in GB perhaps off for buttons? | 16:12 |
| detule | "here" = .35, fine in .39 without the light sensor | 16:12 |
| emwe | ah hm!... i whonder what we are reporting to userland... | 16:13 |
| emwe | perhaps you can debug libsensors? | 16:14 |
| mgross029 | emwe I think it was a part of this commit that changed the way they were working. https://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/commit/ecb5c3f38f07ea640a2868212bd92765f08726e8 | 16:14 |
| emwe | hm, the code just got moved. nothing fancy | 16:15 |
| emwe | all is the same here for me. | 16:16 |
| mgross029 | Sorry gotta run. bbl guys | 16:17 |
| detule | emwe, where's that config.xml file that contains the lux tables for autoBrightness for kbd lcd and buttons? | 16:19 |
| *** helicopter88 has quit IRC | 16:19 | |
| *** helicopter88 has joined #xdandroid | 16:19 | |
| *** AndersG has quit IRC | 16:20 | |
| emwe | detule: one sec... but we are using the same images... | 16:21 |
| emwe | you'd might wan't to check what get's reported to userland. | 16:21 |
| *** kalemas has left #xdandroid | 16:21 | |
| emwe | detule: https://gitorious.org/xdandroid/device_xdandroid/blobs/gingerbread/msm/overlay/frameworks/base/core/res/res/values/config.xml | 16:22 |
| emwe | actually we need to inverse them like abel dir | 16:22 |
| emwe | more light, less brightness | 16:22 |
| emwe | or let's say, we could inverse them for buttons and keyboard. | 16:22 |
| emwe | you could also look if logcat spits out an error that it couldn't enable sensor 1 or 2 | 16:23 |
| emwe | they are listed once in the order they are registered. | 16:23 |
| detule | i'll perhaps look into it but i have very little motivation if hw auto_bl can not be turned off with the lightsensor driver | 16:26 |
| emwe | just see what logcat spits out and what it reports. LOG_NDEBUG 0 in LightSensro and be doen with it | 16:29 |
| emwe | detule: kexec stuff pushed to gito. have fun. | 16:38 |
| emwe | gnight. | 16:38 |
| detule | later good night | 16:39 |
| *** emwe has quit IRC | 16:43 | |
| *** Tandyman100 has quit IRC | 17:04 | |
| *** helicopter88 has quit IRC | 17:13 | |
| *** Tandyman100 has joined #xdandroid | 17:29 | |
| *** fishhead2567 has quit IRC | 18:03 | |
| stinebd | xdandroid: later tell emwe git will preserve permissions yes | 18:05 |
| xdandroid | stinebd: The operation succeeded. | 18:05 |
| *** mgross029_ has joined #xdandroid | 18:13 | |
| *** d3tul3 has joined #xdandroid | 18:14 | |
| *** mgross__ has joined #xdandroid | 18:15 | |
| *** mgross029 has quit IRC | 18:17 | |
| *** mgross029_ has quit IRC | 18:19 | |
| *** vinceweis has joined #xdandroid | 18:48 | |
| *** mgross__ is now known as mgross029 | 18:53 | |
| *** rpierce99 has quit IRC | 19:15 | |
| *** vinceweis has quit IRC | 19:38 | |
| *** Ivo has quit IRC | 20:14 | |
| *** Ivo has joined #xdandroid | 20:14 | |
| *** hardwalker has joined #xdandroid | 20:20 | |
| *** Ivo has quit IRC | 20:28 | |
| *** Ivo has joined #xdandroid | 20:49 | |
| *** rpierce99 has joined #xdandroid | 21:18 | |
| *** mgross029_ has joined #xdandroid | 22:06 | |
| *** mgross029 has quit IRC | 22:10 | |
| *** TheSeven has quit IRC | 22:52 | |
| *** [7] has joined #xdandroid | 22:52 | |
| *** bzo has joined #xdandroid | 23:13 | |
| *** Duplicant117 has joined #xdandroid | 23:37 | |
| Duplicant117 | Hey | 23:37 |
| arrrghhh | hi | 23:38 |
| arrrghhh | do you have a question? | 23:38 |
| Duplicant117 | Yes I do | 23:40 |
| arrrghhh | ok... | 23:41 |
| Duplicant117 | Alright I have a Lenovo Thinkpad tablet and I'm trying to root it | 23:41 |
| Duplicant117 | I've figured out how to to put it into apx mode | 23:41 |
| arrrghhh | what does that have to do with XDAndroid | 23:41 |
| Duplicant117 | and it shows up under device manager | 23:41 |
| Duplicant117 | Oh sorry guess I'm in the wrong channel | 23:42 |
| Duplicant117 | forgiveme | 23:42 |
| arrrghhh | np | 23:42 |
| *** Duplicant117 has left #xdandroid | 23:42 | |
| *** rpierce99 has quit IRC | 23:50 | |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!