| *** NeoMatrixJR is now known as NeoMatrixJR_away | 00:03 | |
| arrrghhh | aw rpierce99 feeling lonely without your tp2? | 00:04 |
|---|---|---|
| rpierce99 | no not really, i don't miss 8 hours of battery life | 00:06 |
| arrrghhh | lol | 00:06 |
| arrrghhh | yea, i'm sure that epic does better | 00:06 |
| rpierce99 | yeah i leave 4g off all the time, so it goes a whole day | 00:07 |
| arrrghhh | the gayPhone lasts pretty long | 00:07 |
| arrrghhh | even after listening to pandora all day & a lot moar phone calls. | 00:07 |
| *** Entropy512_ has joined #xdandroid | 00:33 | |
| *** Entropy512 has quit IRC | 00:33 | |
| *** rpierce99_ has joined #xdandroid | 00:41 | |
| *** rpierce99 has quit IRC | 00:46 | |
| *** rpierce99_ is now known as rpierce99 | 00:46 | |
| *** ImCoKeMaN has quit IRC | 00:46 | |
| *** NeoMatrixJR has joined #xdandroid | 01:54 | |
| *** NeoMatrixJR_away has quit IRC | 01:55 | |
| *** NeoMatrixJR is now known as NeoMatrixJR_away | 01:55 | |
| *** NeoMatrixJR has joined #xdandroid | 01:58 | |
| *** NeoMatrixJR_away has quit IRC | 02:00 | |
| *** NeoMatrixJR is now known as NeoMatrixJR_away | 02:00 | |
| *** panda84kde has joined #xdandroid | 02:55 | |
| *** rpierce99 has quit IRC | 02:59 | |
| *** rpierce99 has joined #xdandroid | 03:24 | |
| *** rpierce99 has quit IRC | 04:10 | |
| *** kalemas has joined #xdandroid | 04:22 | |
| *** raymonddull is now known as ray|dead | 04:46 | |
| *** kalemas has left #xdandroid | 05:15 | |
| *** hardwalker has quit IRC | 05:30 | |
| *** ke- has joined #xdandroid | 05:37 | |
| *** ImCoKeMaN has joined #xdandroid | 06:42 | |
| *** helicopter88 has joined #xdandroid | 08:36 | |
| *** fishhead2567 has joined #xdandroid | 09:07 | |
| *** mgross029 has joined #xdandroid | 09:13 | |
| *** rpierce99 has joined #xdandroid | 10:25 | |
| *** NeoMatrixJR_away has quit IRC | 12:04 | |
| *** detule has joined #xdandroid | 12:14 | |
| *** NeoMatrixJR_away has joined #xdandroid | 13:01 | |
| *** corein has joined #xdandroid | 14:16 | |
| arrrghhh | detule, thar? | 14:23 |
| detule | yeah what'sup | 14:24 |
| arrrghhh | couple of things | 14:24 |
| arrrghhh | first, XdaLedRegime - does that only work on .35+? | 14:24 |
| detule | depends on which version you have | 14:25 |
| detule | one posted in "Latest Kernels" thread should work on 27 | 14:25 |
| detule | one posted in a message in .39 thread should work in +39 | 14:25 |
| arrrghhh | poop | 14:25 |
| arrrghhh | i bundled one in GBX0B | 14:26 |
| detule | which one | 14:26 |
| arrrghhh | and i honestly don't remember which one. | 14:26 |
| arrrghhh | lol | 14:26 |
| arrrghhh | md5sum tiem. | 14:26 |
| arrrghhh | i want to say i bundled the one for .27, but i might've f-ed up. | 14:26 |
| arrrghhh | ok, i can sort that out. | 14:26 |
| arrrghhh | next question - someone said GBX0B never sleeps for them... i guess it's a new occurrence too. | 14:26 |
| detule | (i may have messed up the versions up in my dropbox too) | 14:27 |
| arrrghhh | they deleted their data.img, and still isn't sleeping... could you look at the logs and see if something jumps out to you? | 14:27 |
| arrrghhh | nothing really did to me, other than a wakelock on PowerManagerService. | 14:27 |
| detule | he mentioned something about having wifi on | 14:27 |
| arrrghhh | oh, and some i2c write failures, which helicopter88 said is 'normal. | 14:27 |
| arrrghhh | yea... | 14:27 |
| detule | at least on .39+ device never sleeps with wifi on | 14:27 |
| arrrghhh | oh | 14:27 |
| detule | i didn't think it happened with .27 | 14:28 |
| arrrghhh | i thought it would sleep, unless you set it not to (which evidently doesn't work anyways) | 14:28 |
| detule | but whoknows | 14:28 |
| arrrghhh | bleh. | 14:28 |
| arrrghhh | well we'll see what he comes back with | 14:28 |
| arrrghhh | i asked him to try a newer kernel lol. | 14:28 |
| detule | also just make sure the led_regime is not messing up because of the apk version | 14:28 |
| arrrghhh | yea | 14:28 |
| arrrghhh | i'll doublecheck what i bundled. | 14:28 |
| arrrghhh | i thought i bundled the one for .278 | 14:28 |
| arrrghhh | er | 14:28 |
| arrrghhh | .27 | 14:28 |
| detule | just have him echo to /sys/class/microp_klt/parameters/led_regime | 14:28 |
| detule | er | 14:28 |
| arrrghhh | yea i said you could do it manually without telling him how lol | 14:29 |
| detule | i guess /sys/module/microp_klt/parameters/led_regime | 14:29 |
| detule | shame we never standardized the location of led_regime | 14:29 |
| detule | you should write a patch :) | 14:31 |
| arrrghhh | hahaha | 14:32 |
| arrrghhh | i still need to figure out this whole dirty module thing | 14:32 |
| arrrghhh | rpierce99 has me second guessing myself now... | 14:32 |
| arrrghhh | i've also wanted to fix that stupid wifi mac issue, but it might be over mah head. | 14:32 |
| *** balans1 has joined #xdandroid | 14:33 | |
| detule | anyways xtra might be a lost cause without the following : the xtra docs that the hd2 people have and are no longer google-able, and a remote_apis_clnt.dll from hd2 ... don't have the time to mess around in windows trying to figure out why romextractor doesn't like vista or whatever | 14:34 |
| arrrghhh | hrm | 14:35 |
| arrrghhh | something i can help with? | 14:35 |
| detule | well need someone chef-ier than me who can find their way around nbhutil and recmod to pull that dll from a leo rom | 14:45 |
| detule | as far as xtra info, need to get in touch with tytung and see how generous he feels, but he does not accept PMs on xda | 14:46 |
| *** balans1 has left #xdandroid | 14:50 | |
| *** balans1 has joined #xdandroid | 14:57 | |
| arrrghhh | crap. | 15:07 |
| arrrghhh | i wonder if he'd accept a PM from me... i am a mod :P | 15:08 |
| arrrghhh | i'm not sure how else to get in touch with him, he's literally never on IRC... | 15:08 |
| *** balans1 has quit IRC | 15:19 | |
| detule | yeah those i2c errors are normal (messy coding) on .27 | 15:29 |
| *** mgross029 has quit IRC | 15:30 | |
| arrrghhh | poop. | 15:30 |
| helicopter88 | What did i tell you arrrghhh? | 15:38 |
| arrrghhh | yeayea | 15:38 |
| arrrghhh | you were right :P | 15:38 |
| arrrghhh | you didn't know why | 15:38 |
| arrrghhh | lol | 15:38 |
| arrrghhh | but you were right. | 15:38 |
| helicopter88 | I've never said i know why shit happens | 15:39 |
| helicopter88 | i just know the truth :P | 15:39 |
| arrrghhh | mmmmhmmmm | 15:39 |
| detule | it's because too many things are trying to access the same i2c client which controls the leds/some kbd functions at the same time...they race....these calls are queued in +35 and everything happens in an orderly fashion....secretly i always thought this was behind the failed panel wakes in 27 | 15:40 |
| arrrghhh | hrm | 15:40 |
| helicopter88 | exactly what i've said | 15:41 |
| helicopter88 | lol | 15:41 |
| arrrghhh | but failed panel wakes happen in newer kernels too... | 15:41 |
| arrrghhh | although i am so out of the loop now... | 15:41 |
| detule | i don't see them in 3.2 though perhaps in some extreme corner cases (rapid power on/off button presses) | 15:41 |
| arrrghhh | hrm | 15:42 |
| arrrghhh | i need to get back on the horse. | 15:42 |
| arrrghhh | although without that dirty patch, i don't have anything to patch | 15:42 |
| detule | as a sidebar, +39 also has some "jonpry special" panel logic which hammers the panel on wake-up with multiple calls to make sure it comes up | 15:42 |
| arrrghhh | other than that wifi-nvram thing | 15:42 |
| arrrghhh | lol | 15:42 |
| arrrghhh | jonpry special, i like that | 15:42 |
| detule | you should fix this led_regime parameter move it to /sys/class/leds/amber/led_regime | 15:43 |
| detule | that's a good place where it can exist on all kernels | 15:43 |
| arrrghhh | that sounds like kernel patches | 15:43 |
| detule | it is | 15:44 |
| detule | oh and perhaps one more patch "rm -rf htc-msm-2.6.27/" | 15:47 |
| detule | not sure how you would properly format that guy | 15:47 |
| detule | stine might not like it | 15:47 |
| arrrghhh | lol | 15:47 |
| *** Mokkun has joined #xdandroid | 15:50 | |
| arrrghhh | stine doesn't care... c'mon now. | 15:52 |
| *** helicopter88 has quit IRC | 15:53 | |
| Mokkun | hey guys. I discovered something interesting. I'm having that no-sleep problem on GB+.27 some of the time. I'm using GenY.Dualboot to load haret, and if I boot to android before inputting my pin in winmo, my phone will not go to sleep and end up draining the battery quickly | 15:55 |
| Mokkun | Though, if I let it settle into winmo for awhile, it'll perform as intended once in android | 15:55 |
| arrrghhh | hrm | 15:55 |
| arrrghhh | some have said that, others have said otherwise... | 15:55 |
| arrrghhh | not sure what, but i'm guessing some winmo roms take longer to boot than others? | 15:56 |
| arrrghhh | or perhaps they initialize hardware in a different order? that would make less sense. | 15:56 |
| Mokkun | it's not all the time, more like 8 out of 10 times sleep won't happen if booted into android straight away | 15:56 |
| Mokkun | depends on what version of wm they're running | 15:56 |
| Mokkun | mine is a clean 6.5 htc install | 15:56 |
| arrrghhh | strange | 15:57 |
| arrrghhh | i used gen.y auto boot after 3 seconds for a long time, never had an issue | 15:57 |
| arrrghhh | i kept wiping and got sick of reinstalling it tho lol | 15:57 |
| Mokkun | I found it strange as well, though it is a noticeable difference | 15:58 |
| Mokkun | that's why I turn my phone back to wm at night to charge it fully, and then during the day I switch it to android | 15:58 |
| arrrghhh | yea | 15:59 |
| arrrghhh | many have noticed charging in Android isn't so great | 15:59 |
| arrrghhh | it happens WAY too quickly | 15:59 |
| arrrghhh | and most say it doesn't charge to 100% - probably true as well. | 15:59 |
| Mokkun | full charge in 30 seconds XD | 15:59 |
| Mokkun | and drained back to original % in 1 min afterwards | 16:00 |
| arrrghhh | lol | 16:00 |
| Mokkun | imho, my laymen sense says the battery in android isn't measuring residual capacity, it's measuring time till no capacity | 16:01 |
| Mokkun | would make more sense actually | 16:01 |
| arrrghhh | perhaps | 16:01 |
| arrrghhh | measuring mV | 16:01 |
| arrrghhh | jonpry put a ton of work into rewriting the entire charging/batt calc algo's | 16:02 |
| arrrghhh | and it was never accepted mainline... | 16:02 |
| Mokkun | had the % go from 80 to 40 due to downloading stuff over 3G, and once finished, half an hour later, the % was back to 70 and consistent through that even while messaging and such | 16:02 |
| arrrghhh | yea | 16:02 |
| arrrghhh | that definitely happens | 16:02 |
| arrrghhh | the current algo doesn't account for peripherals | 16:02 |
| Mokkun | no idea what those are, but I'll nod and pretend I got it | 16:04 |
| arrrghhh | lol | 16:11 |
| arrrghhh | peripherals = anything additional basically' | 16:11 |
| arrrghhh | wlan, bt, cell radio, etc are all peripherals | 16:12 |
| Mokkun | oh ok | 16:15 |
| Mokkun | also, detule, I'll try to extract that .dll file from HD2 for you | 16:15 |
| Mokkun | remote_apis_clnt.dll right | 16:16 |
| Mokkun | anything else? | 16:16 |
| *** ke- has quit IRC | 16:26 | |
| detule | oh you the man | 16:30 |
| detule | gpsdriver.dll | 16:30 |
| detule | if it's not too much work Mokkun | 16:30 |
| *** mes has joined #xdandroid | 16:32 | |
| detule | if you own an hd2, romextractor should do the trick | 16:34 |
| Mokkun | yea, if I owned a hd2, I would've already put them up ages ago. I'm actually extracting them from roms | 16:36 |
| Mokkun | or trying to.. | 16:36 |
| Mokkun | mostly waiting to atm | 16:36 |
| Mokkun | since they aren't downloading as fast as I wished they would | 16:36 |
| detule | i was having issues recmod-ing the folders on a PC when i extracted them from various hd2 roms | 16:37 |
| detule | perhaps you'll have better luck | 16:37 |
| Mokkun | perhaps | 16:37 |
| detule | i ahve to get going, thanks for giving it a go | 16:39 |
| Mokkun | np | 16:40 |
| Mokkun | I'll post a link here to the file when I manage it | 16:40 |
| Mokkun | voila http://www.mediafire.com/file/3fa3s3sf8mzuvwa/detuleswishlist.rar | 16:57 |
| arrrghhh | nice | 17:00 |
| arrrghhh | thanks Mokkun | 17:00 |
| arrrghhh | i like the file name too, lol | 17:00 |
| Mokkun | yea, already had the remote_apis_clnt.dll on my mediafire account, so it kinda errored out | 17:03 |
| Mokkun | this was a somewhat more elegant solution | 17:03 |
| arrrghhh | hah | 17:05 |
| Mokkun | *.dll from my rhod100, so the *.dll from the leo wouldn't upload XD | 17:06 |
| arrrghhh | nice | 17:07 |
| Mokkun | btw, arrrghhh, I'm actaully just realizing how tweaked down my current setup is | 17:07 |
| arrrghhh | tweaked... down? | 17:07 |
| Mokkun | running droidwall blocking anything but message, whatsapp and some other minimum stuff | 17:08 |
| arrrghhh | oh | 17:08 |
| arrrghhh | you just mean how minimal your setup is :P | 17:08 |
| Mokkun | on top of that, got the only connect t 2g setting checked | 17:08 |
| Mokkun | yea | 17:08 |
| arrrghhh | tweaked down makes me think you set things in a silly way | 17:08 |
| arrrghhh | like underclocked the proc | 17:08 |
| arrrghhh | set memkiller to some ridiculously high setting so it never runs | 17:08 |
| arrrghhh | etc | 17:08 |
| arrrghhh | :P | 17:08 |
| Mokkun | well, it's silly if you consider the rhod to be a smartphone, now capable of barely nothing without risking a dead battery | 17:09 |
| arrrghhh | i dunno | 17:09 |
| arrrghhh | when i was using it full time i was getting 8-10hrs of battery life | 17:09 |
| Mokkun | but as I was saying... I'm running an aggressive droidwall setting, 2g only, v6 at aggressive 2, and barely browse - but that's nothing new. | 17:10 |
| arrrghhh | heh | 17:10 |
| Mokkun | can spend up to 8+ hours that way with a full battery messaging people | 17:10 |
| arrrghhh | yea, that's not bad | 17:11 |
| Mokkun | and a few short phone calls | 17:11 |
| arrrghhh | usable i'd say... | 17:11 |
| Mokkun | definately | 17:11 |
| arrrghhh | i wish wistilt2 would've committed his magic from his .39 tweakings | 17:11 |
| Mokkun | though, the daily train trip eats away the battery | 17:11 |
| arrrghhh | i don't think those ever made the light of day, at least the source. | 17:11 |
| Mokkun | can't you contact him | 17:12 |
| Mokkun | ? | 17:12 |
| arrrghhh | he was getting it down to 0.5% drain / hr in sleep | 17:12 |
| arrrghhh | i can, but he's busy. | 17:12 |
| Mokkun | committing that time consuming? | 17:12 |
| arrrghhh | it can be | 17:12 |
| Mokkun | hmm... | 17:12 |
| arrrghhh | especially if you want it to apply cleanly :P | 17:12 |
| arrrghhh | then consider all the different kernels we have... it's kinda crazy. | 17:13 |
| Mokkun | though, my previous install of GB + 3.0 had a 1% drain/hr | 17:13 |
| Mokkun | but that was the first day, then it went bad | 17:13 |
| arrrghhh | hahaha | 17:13 |
| Mokkun | really, first boot, I let it settle | 17:13 |
| Mokkun | added one or two apps | 17:14 |
| Mokkun | and then killed every radio except 3g | 17:14 |
| Mokkun | and it went to sleep | 17:14 |
| Mokkun | and after 6 hours, it was like from 76 -> 70 | 17:14 |
| arrrghhh | nice | 17:15 |
| Mokkun | then I added another app | 17:15 |
| arrrghhh | w/o SCBS tho, trying to accurately determine battery life and drain is not straightforward... | 17:15 |
| Mokkun | and after 2 hours, it was like 70 ->>>>>>> 44 | 17:15 |
| Mokkun | so yea | 17:15 |
| arrrghhh | SCBS is awesome. | 17:15 |
| Mokkun | kinda unpredictable | 17:15 |
| Mokkun | sdcard booster? | 17:16 |
| arrrghhh | nah | 17:17 |
| arrrghhh | that algo i was talking about in relation to battery | 17:17 |
| arrrghhh | jonpry completely rewrote the batt algo | 17:17 |
| arrrghhh | and it works pretty dang well | 17:17 |
| Mokkun | oh | 17:17 |
| arrrghhh | but there's a painful manual process for calibration | 17:17 |
| arrrghhh | and he never got it to work on anything but RHOD | 17:17 |
| arrrghhh | so it never made it mainline :( | 17:17 |
| Mokkun | how painful? | 17:17 |
| arrrghhh | well it kinda varies | 17:17 |
| arrrghhh | but basically you have to do your best to simulate different types of drain | 17:18 |
| arrrghhh | over a day or two | 17:18 |
| arrrghhh | full charge, fast drain, low battery, slow drain etc | 17:18 |
| arrrghhh | best to get the full spectrum of battery too from 100-0 as close as you can... | 17:18 |
| Mokkun | sounds painful indeed | 17:18 |
| arrrghhh | then you'll get this huge file on your SD card | 17:18 |
| arrrghhh | and you have to run the calib tool on the phone | 17:18 |
| arrrghhh | which takes FOREVER because our procs don't support some floating point calc | 17:18 |
| arrrghhh | and obviously the bigger the file, the more data, the longer it takes to create a model | 17:19 |
| arrrghhh | if there was a way to automate that process and update the battery calib every few months without user intervention... it would be perfect. | 17:19 |
| Mokkun | yea, it would be easier... | 17:20 |
| Mokkun | and no idea how wm does it correctly? | 17:20 |
| arrrghhh | well they have the source code for the hardware | 17:21 |
| arrrghhh | no need to hack shit to work.. lol | 17:21 |
| Mokkun | and no way to reverse engineer? | 17:22 |
| Mokkun | sucks | 17:22 |
| arrrghhh | well, that's what this entire project is.. | 17:23 |
| arrrghhh | for the most part | 17:23 |
| arrrghhh | a giant reverse engineering project... | 17:23 |
| Mokkun | oh yea | 17:23 |
| Mokkun | >< | 17:23 |
| arrrghhh | some things are simple to RE. some... are not. | 17:23 |
| *** rpierce99 has quit IRC | 17:33 | |
| *** corein has quit IRC | 17:57 | |
| *** panda84kde has quit IRC | 18:36 | |
| *** Mokkun has quit IRC | 19:14 | |
| *** ryannathans has quit IRC | 19:18 | |
| *** fishhead2567 has quit IRC | 19:26 | |
| *** hardwalker has joined #xdandroid | 19:46 | |
| *** rpierce99 has joined #xdandroid | 21:24 | |
| *** NeoMatrixJR_away is now known as NeoMatrixJR | 21:46 | |
| *** ray|dead is now known as raymonddull | 22:16 | |
| *** rpierce99 has quit IRC | 22:45 | |
| *** rpierce99 has joined #xdandroid | 22:46 | |
| *** cheeto12345676 has joined #xdandroid | 23:19 | |
| cheeto12345676 | hey anyone here | 23:19 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!