yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] imheroldman:
@crammed, this is an excellent setup! Actually to the t of what I'm running now.

They updated tiamat to 4.0.6 and I'm getting great results with it. Got a 20+ hour day last weekend!

I also just learned about setting a voltage floor with vipermod, so I an giving that a go @ 850.

I an very thankful for this post as it has made me aware, as well as help to fix the issue. Of course it takes a little for work but its worth it in the end.

Sent by Supersonic!
[EVO 4G Android Development] fitz420:
Ive also had the best battery life and signal with the latest combo as well. First time I've stuck with new radios/pri in a while.
[EVO 4G Android Development] fadi33:
Thank you crammed for a clear setup. There have been so many posts and attachments, I didnt know what I needed to do. You cleared everything up. I also use deck 1.2.1 with tiamat 4.0.6 and -50 undervolted.
[EVO 4G Android Development] AliLaPointe:
Perhaps I am missing something, but I am still having high android system use in Spare Parts and in Battery Information after doing all of these fixes. Ughhh. Im about to give up on AOSP.
[EVO 4G Android Development] imheroldman:
@Ali, how is your battery life on an aosp rom? To be honest, no matter what I've done I don't see more than 15-20 hours. That its with no android system, under-clocking, under-volting, juice defender, you name it.

What gets me is I got a 20 hour day on synergy rom, no custom kernel there... As Sbrady has said there is no conclusive evidence that any of this improves battery life.

Also, let your roms and kernels settle for a few days. I've found better success with this.

I'm satisfied now with aosp, I still do the mods, every little bit helps. Most important to me is how small they all are. Cm7 is just under 80 mb which is one of the biggest I think, which is almost 200 mb less than any new sense rom. OMFGB (SP?) claims to be under 60!

For what its worth...

Sent by Supersonic!
[EVO 4G Android Development] jessesse:
I just wish there was a better explaination for the run away android system on cm. I don't want to lose my sensors. It does only spike after a phone call and I don't want to reboot everytime I hang up.

:(

This issue is so hit or miss... I didn't have a problem for the longest time until sometime a couple weeks ago.. hard to pinpoint when it started for me.
[EVO 4G Android Development] crammed174:
Yeah my lowest is 850, I can run 825 stable but boot loop on reboot so why bother. and for me 4.0.6 was unstable :-/ and after using the phone today and on the road I will note google maps stayed around 40% battery use even though i used it a few minutes although battery was fine. however commuting home when running gmaps on the highway going around 60mph it was locked on at 3m accuracy and was incredibly accurate, literally the length of the car on a 7 mile trip with almost no lag. When I got home battery was great bout I just got off a 2 hr voice call and checked my stats and android os is at 60% and battery dropped Fromm 50ish to 20% and the phone was 'awake' the whole time, I'm pretty sure that normal since it's actually in use and now it seems as though the phone was 'awake' throughout the day but battery info did not list ts as I checked throughout the da so I'm perplexed. But hey I just reflashed everything yesterday so it takes time for kernel to set in. I'm not going crazy yet. I can say this, until this call my android os use was 5% and I've NEVER had such a fast and accurate lock on gps.

Also terminal command 'dumpsys power' still shows 0 for both mlock and pokelock. So considering the amazing 3G speed with latest everything, and perfect gps I am going to disregard battery stats and only depend on actual performance for a few days until the kernel sets in because something is up, keep awake lists 26 minutes all day even though I had 2 hour long consecutive call, several others throughout out the day, data use and so on.

Right now 13 hrs 10 min on battery and 16% battery android os 62% so it may just be a reporting info error as mentioned before YMMV. Im gonna let the battery die so it can go through a full cycle then start over snd charge up to 100 w/o use to really push the sbc.

My guide to how I flashed got me working gps and norms, battery use when idle so I'll stick to it for now. Any questions please ask and if you liked my tips please hit the "thanks" button.

I'll follow up in 2 days unless someone has a question sooner. Good luck
[EVO 4G Android Development] ro_bro:
Few questions as I try to understand this.

Does anyone know what caused the phone app's wakelock problem in the first place?

Was it always a problem in AOSP?

If not, does anyone know the root cause of this problem? For ex, what Android release introduced this problem?

Lastly, is this unique to the EVO, or all phones running an AOSP ROM?

Sorry for all the questions, just trying to understand the root cause and what it really affects.
[EVO 4G Android Development] apheonixboy:
2% cell standby!
[EVO 4G Android Development] Redneck Trash:
How'd you achieve that?

*please do not feed the trolls*
[EVO 4G Android Development] apheonixboy:
Well I live in a city without 4G, so no 4G switching back and forth from 3G. And sometimes I even get 1x.

But maybe its the ROM I'm using. I'm using Rewind 3.0. Nothing special. No setCPU or anything.

Just a 3500 mAh battery.

Oh and switching from CDMA with PRL to CDMA only.
[EVO 4G Android Development] Redneck Trash:
Oh and switching from CDMA with PRL to CDMA only.

I forgot all about that.

*please do not feed the trolls*
[EVO 4G Android Development] crammed174:
out of sync battery stats?

might seem dumb to ask but would pulling the nexus s 4g dialer be of any use or is the samsung dialer inherently incompatible with another brand i.e. HTC? i'm not sure if the phone.apk is an AOSP cross platform app or still specified. i wouldn't even mind different layout, just functionality right.

as for my experience with this threads recommendations:

I originally flashed the OP's radio fix after i noticed the high android OS use and it eliminated it from my stats... for a few days and it started to kill my battery. i actually had great battery life (like 30hrs and always above 20% before going to bed w/ solid use through the day) so obviously i'm dumb for fixing a working product, i just thought maybe it could have adverse effects.

anyway i then had some 3G radio issues and went back and forth btwn roms and finally returned to deck 1.2.1 and I flashed your phone.apk and wrote detailed instructions in this thread on what I did and it worked for a few days. only problem is now my android OS is back up high but battery is semi decent, not where it used to be and sysdump power always shows pokelock at zero but the issue is my phone says its awake often and it seems to be in sync with when the screen is allegedly on as well (it isn't). and my battery stats are completely wacked meaning when i go into the info it says on battery 10 hours and if i click the graph for details it might show 7 hours or 8.5 etc and the info in there isn't accurate and i'm sure... never had this problem and don't think this is related to phone.apk but it's kinda annoying since i can't keep accurate track, i've calibrated as well and let the kernel set... also before the awake would be often and for longer periods on the chart but now it seems like its still frequent, if not more frequent but for minute amounts of time that they're slivers on the chart but i can't be sure considering the reporting errors. rebooted and wiped caches thus far. any thoughts or tips? should i bother reflashing rom or wiping?

i'm currently on what my sig lists.

attached some screen shots in case i confused more than clarified.

you see one from yesterday showing the out of wack use, today the awake werent as bad and long. then you see my phone fresh off charge, screen off the whole time and 42 mins yet 0 sec in details. then android OS pops up after 1 min test phone call. mlock and pokelock still 0
[EVO 4G Android Development] tlxxxsracer:
Should I update my PRL? Mines at 01115 :confused:

And since Im running MIUI, would I have to flash to a sense rom to check if the PRI, NV changed?

So far I charged 100% through the night and unplugged this morning. Made a few random calls, now to drain the battery to 0% and charge back up. Should there be a need to wipe battery stats in CWM whenever 100% is reached?

Looks promising though! ill report later

Update: my phone has been off the charger for about 4hours now. My battery is at 64%. My awake bar is almost completely solid while the majority of my screen on is blank. But yet my system usage is only at 5% right now. Ive used facebook, email, XDA app, cut the rope game

Update 2: I flashed to a sense rom to update my PRL and profiile. And before that I reflashed the PC36img file just to be sure it stuck while I was in sense. Got things updated and nandroided back to my MIUI. PRL, PRI stayed- so hopefully this fixes my issue.

I would really suggest to those not on sense- to flash to a sense rom before you flash the img file. This way you can quickly check if the wimax, pri, NV were properly flashed.
[EVO 4G Android Development] tlxxxsracer:
Not sure if this fixed anything.. But- my awake is one complete solid bar as about 90%+ of the time i have the screen turned off. It didnt do this before.

In my battery usage, system is at 17%. Im letting the battery drain to 0 and then will charge up completely and whipe battery stats/reboot.
[EVO 4G Android Development] NeroDan:
This is so frustrating...

I'm trying to stay away from eliminating the proximity sensor, I'd really like to keep all functionality. But I feel like I've tried every combination to get rid of android system. Boo!!
[EVO 4G Android Development] ropodope:
it's just the sensor that causes the light in your screen to come back on once you remove the phone from your ears when in a call. easy workaround is to touch the on/off switch. Big deal, the tradeoff is tremendous. The choice is yours.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. Gapps? What are gapps?
[EVO 4G Android Development] NeroDan:
Solid point. I may give it a shot. I like that I can easily switch back and forth if I need to. We'll see.
[EVO 4G Android Development] NeroDan:
Well, that file is a nogo for me. It broke all my sensors. Screen brightness, rotation, etc. No "android system " though, haha. Guess I'm gonna have to wait for an actual fix. HUGE difference in battery life since I disabled the sensors though. Oh well.
[EVO 4G Android Development] mikeyinid:
Flashed noProximityPhone.zip and android system is still showin in battery stats, although its not at the top any more.. And the "double tap to unlock" padlock is a nice feature :)
[EVO 4G Android Development] mikeyinid:
NoProximityPhone.zip does fix high "android system", to bad it breaks my phone and makes me sound like a robot in a tunnel. Flashed my original phone.apk back in and all is well so I guess high android system and no working auto brightness are just a part of running aosp on the EVO :/
[EVO 4G Android Development] NeroDan:
I have no idea what fixed it, but I flashed the latest tiamet kernal and 140 cyanogen nightly aand my system use is staying at 4% and the battery life is great with heavy usage. I'm not gonna question it though!
[EVO 4G Android Development] mikeyinid:
Have you made any calls yet?

Anyway, I just wanted to share something I'm finding with my nexus s. I never really payed much attention to battery use on my nexus. I actually haven't had bad battery life on my evo running aosp either. I started reading through some threads and seeing people with issues and android system and all that and saw that I was also having the high android system issue. I switched back to my nexus out of curiosity and noticed that android system is second in battery use only to display(Samoled). So is it possible that its not an evo issue but rather an aosp issue? Is it possible its by design? If the nexus didn't have the Samoled screen I'm sure android system would be tops in battery use. Idk, just wanted to throw it out there.
[EVO 4G Android Development] NeroDan:
Damn. Spoke too soon.
[EVO 4G Android Development] crammed174:
what did you do exatly? im on miui 1.7.22 and after applying some of the tips and flashing gps fix flash 3 since my gps wasn't working stock, i have what you call a 90% bare but it's not continuous, in a lot of places its split for like a second b/c you have to look hard. but also my battery reporting is completely inaccurate. the data doesn't update. clean wipe and install everything was good except gps, one i touched that all went down... my first nights use was almost non stop and i still got like 12 hours out of the included kernel. but then i noticed the runaway wake lock, android os and android system. plus pokelock is always 1 for me in miui but not on deck.
[EVO 4G Android Development] apheonixboy:
Honestly... Why is everyone's percentage so high?

The only thing high (past 75%) is my display.... But why? Everything else is under 5%.

Evo 4G .

Hw: 003.

Stock HTC kernel #8.

Sense 3.0

Display at full brightness.

No overclocking or scripts.

Regular 1500 mAh battery.

3 bars of signal all day.

Sent from my Supersonic rockin that 3D sense!
[EVO 4G Android Development] NeroDan:
Hence the reason for this thread. Furthermore, this problem affects AOSP roms, not sense roms like you have.
[EVO 4G Android Development] imheroldman:
Had a 3.5 hour wake lock from XDA premium today... What the world?

Sent by Supersonic!
[EVO 4G Android Development] jayshocka:
Thanks for your hard work! just finished the process will check back with you in day or so.

savaged zen
[EVO 4G Android Development] jayshocka:
ok here is what I got: running savaged zen RC4 with 2.2.0 cfs havs sbc kernal

hardware 0003

after flashing and following instructions t-o t-h-e L-e-t-t-e-r

android system... as advertised is gone my battery life has improved enough to notice ( happy about any little bit i could get ). Unfortunatly my gps is kaput. i flashed gps_supersonic_restore_flash.zip and it is now working But guess what android system spiked to about 67 %

This may be a savaged zen problem that I have been encountering and have not yet found a solution for

Thanks for This
[EVO 4G Android Development] fitz420:
I've used the noproximityphone on decks old 2.3.4 based roms with perfect results.

Now that decks 1.3b is a 2.3.5 based rom, will this fix still work or will it cause problems. I'd try it for myself but i'm traveling and don't have much time to be nandroiding and flashing roms.

Thanks in advance for your help.
[EVO 4G Android Development] cheapskate88:
I'm running the fix on the latest beta and it works fine.
[EVO 4G Android Development] helpmeplis:
same herem but i had to update the pri and all that combo to get it to work

spoke too soon still have the lock
[EVO 4G Android Development] JBabey:
My wife was having wake-lock issues after the fix, and after using a program called "BetteryBatteryStats" (linked here somewhere on XDA) it turns out her wake-lock was caused by the new facebook app update.

Link to thread w/ stats program

http://xdaforums.com/showthread.php?t=1179809

the new CHAT feature they added leaves your phone in awake status permanently.

To disable, open facebook app, open the chat portion, click on menu on the phone, then choose "logoff".

Once you do that reboot the phone, and the wakelock will go away (if you are using the tools from this thread of course)

I was rackin my brain on why the fix worked for me and not her.

____

to use betterbattery open the program

click on process

change it to partial wakelocks

now look at the list and the percentage,,,, this is the defenitive "whats keeping my phone awake"

if facebook chat is at the top, and the percent is 100.00%

its facebook, logoff that chat.

anyways hope this helps.

~J
[EVO 4G Android Development] MizzouBrent:
I have really high android system usage running cm7.0.3.1 and the latest sz cfs kernel. I have flashed the phone zip file that has been posted here so my poke locks are being released so I'm not sure what is causing it. I have all the current radios installed with pri 1.77.

I thought the phone zip would get rid of high android system usage. An I missing a step?
[EVO 4G Android Development] imheroldman:
@Brent, you can look in spare parts to see what is causing other wake locks.

Realistically, use your battery life as a gauge for how your phone is operating. A.S.usage is normal. Even on stock AOSP roms. I have even seen it on my wife's un rooted Evo.

I have used this fix and still believe it holds some value, though, I am using all current radios and am getting excellent battery life. AS spikes every so often, but I keep an eye on my partial wake usage.

Sent by Salvaged Supersonic!
[EVO 4G Android Development] MizzouBrent:
That's what I don't understand. I don't have any significant wake locks but android system apparently has been responsible for 54% of my battery usage. Just seems odd.
[EVO 4G Android Development] imheroldman:
If you look under what Android system includes you will notice there is quite a list. There is a lot going on there so it really doesn't surprise me that it will be so high.

What ends up killing your battery is the wake locks, if you address those you should be good. Calibrate your battery also for good measure.

Sent by Salvaged Supersonic!
[EVO 4G Android Development] tlxxxsracer:
I used this fix a while back and it helped.

I upgrade my MIUI to 1.8.26 and i get about 30% system usage.

What do I try next?? Using tiamat 3.3.7 too :rolleyes:

I've tried fixing permissions as well and doesnt help :confused:

Even did a factory wipe in recovery to start fresh instead of just installing the new rom update over.

Great guide though! :D
[EVO 4G Android Development] cushockey66:
Can someone post the modified phone apk..can't seem to find it?
[EVO 4G Android Development] ropodope:
http://db.tt/MilQKXW

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. 499mhz is the new 998mhz.
[EVO 4G Android Development] cushockey66:
Thanks man..just flash it through recovery?
[EVO 4G Android Development] ropodope:
yes sir.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. 499mhz is the new 998mhz.
[EVO 4G Android Development] BlazinThat:
Thanks for this post it helped me with a problem i didnt know i had till i looked here trying to solve another issue. You guys rock!
[EVO 4G Android Development] MizzouBrent:
Ok I'm on cm7 nightly 180 and tiamat 4.0.7. I flashed the phone zip file and show no wake locks when I run dumpsys power from terminal. I'm showing 62% android system usage. Wasn't flashing the phone zip file supposed to fix this?

I don't show any apps are in wake lock but I have almost two hours worth of sensor usage by android system, dialer and camera. How can I see what is causing my high android system usage? Is there an app that will tell me?
[EVO 4G Android Development] ropodope:
constant screen on. Turn off the screen for a bit and the usage goes down.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. 499mhz is the new 998mhz.
[EVO 4G Android Development] MizzouBrent:
Well it's been 6 hours since unplugging my phone and I haven't used it a whole lot, so my screen has been of a lot. Would it be something else?
[EVO 4G Android Development] ropodope:
your proximity sensors may be wonky or you may not have a very good cell signal right now.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. 499mhz is the new 998mhz.
[EVO 4G Android Development] MizzouBrent:
Signal is good. I guess I'll try the proximity sensor fix
[EVO 4G Android Development] MizzouBrent:
After doing the proximity sensor fix I think my wake issue its fixed but now it seems I can't rotate my screen anymore. My backlights don't work on my home, menu, back and search keys either. Maybe I should just try a different rom.
[EVO 4G Android Development] ropodope:
sounds like you removed your proximity sensors, wasnt the fix I was talking about.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. 499mhz is the new 998mhz.
[EVO 4G Android Development] BlazinThat:
So now my android system is back at 31%. It came outta no where. So do I just try again?
[EVO 4G Android Development] MizzouBrent:
I took the zip that was posted here, put the two files in the directory with my existing driver, so it overwrote the old file and I also had the one with the .bak at the end. What was I supposed to do? I read the instructions that were posted back on page 31.
[EVO 4G Android Development] tlxxxsracer:
If Im running MIUI, do I still use

Qualcomm Vision GPS Driver

Sense GPS Driver File from Qualcomm Vision

??

Or do I use

~>AOSP<~

CyanogenMOD 7 Nightly 39 GPS Driver (HTC Blob File Compiled)
[EVO 4G Android Development] imheroldman:
Use the Qualcomm driver always. Just works all around.
[EVO 4G Android Development] b0tes:
I personally ran the AOSP CM7 GPS driver for MIUI, and although my wake locks don't seem to be any less according to battery monitor, my actual battery life is much more improved.
[EVO 4G Android Development] tlxxxsracer:
Now idk which to use :( miui is aosp...

The gps zip is thr only thing i have left to try. I installed the img. System is 54% :o
[EVO 4G Android Development] ropodope:
Those files removed your proximity sensors for testing purposes. restore back to where you were so that the proximity sensors work. Take this single file and replace it with the one you have. Now your proximity sensors will work again and be very very responsive like they should be. This is not a flashable file. The file goes in /system/lib/hw with rw-, r--, r-- permissions. No reboot needed. Works instantly.

Proxsensorfix.zip

http://db.tt/bJm4tsX

ropodope

I don't give a crApple what you think
[EVO 4G Android Development] tlxxxsracer:
Bump for the above.

Should I use the sene or AOSP gps drivers- if im using MIUI
[EVO 4G Android Development] MizzouBrent:
Awesome. Thanks ropodope, you're one helpful guy.

So in theory, drop this in the right directory, flash the phone zip file and I shouldn't have any more system drain? Sounds good to me.
[EVO 4G Android Development] ropodope:
That's right. Its as noticeable as night is from day. You are very welcome for the help bro.

ropodope

I don't give a crApple what you think
[EVO 4G Android Development] b0tes:
I actually nandroided and flashed the 1.1 Qualcomm Vision GPS Drivers found here, and they worked like a charm.
[EVO 4G Android Development] MizzouBrent:
@ropodope

Hey I copied the proximity drivers to the directory you listed and rebooted to flash the phone zip and now it appears that my proximity its messed up. Backlights aren't working for home and menu etc and my screen won't rotate
[EVO 4G Android Development] tlxxxsracer:
Well i reinstalled the img file, then flashed the gps 1.1 drivers.

After wiping battery stats and restarting this morning I still have 45% system usage.

Guess next is to try the phone and sensors

Edit: Still showing the same amountof system usage. I used GPS this morning to track a run, made 2 phone calls, a good amount of texting, music. Ive kept my data turned off.

Being off the charger for 3.5hrs My battery is down to 66%.

More help would be wonderful!
[EVO 4G Android Development] Sean-El:
I am on Deck's AOSP Rom and all I did was follow the directions and everything worked correctly. Today there was no more Android usage and my battery life is better.
[EVO 4G Android Development] tlxxxsracer:
Wish I could say the same for me.. I even installed amonRA recovery. I still got a huge 43% android system in my stats.

Im going to try (after my battery charges back up to 100%) to flash to a sense rom and update my prl and profile.
[EVO 4G Android Development] Sean-El:
What exactly did you do when you installed all this? If it is the same as me then idk, usually people try different stuff and don't have the same results.