yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] tramane:
Confirmed!

Android OS is now a distant memory

And of course because that's no longer an issue it shows display as the biggest battery hog at 80% or more

But then again, shouldn't it be?

GPS Lock super fast.
[EVO 4G Android Development] ahow628:
I flashed all the newest items from the thread linked a few posts up and I'm currently down 15% after 4.5 hours. MUCH better. And actually better than before any of this.
[EVO 4G Android Development] Cyclonut:
Mine is dropping about the same on wifi also.
[EVO 4G Android Development] igotroot:
You know the OP made me look at my Savage Zen Mod 2.3.4 and lo and behold my android system was like 67%.... I did a full overnight SBC charge....shut down......then rebooted....all is good. I have all the latest radios NV PRI etc and I'm good. I didn't need the 1.77. I'm current and loving the fact I can keep all the latest specs.

I'm on my 11th hour with battery... 60% left . Not bad for my heavy usage.
[EVO 4G Android Development] r.storm85:
Would flashing jus the gpsfix do anything?? I dont wany to mess with my radios, im on synergy nightly 6/9 and have wake lock
[EVO 4G Android Development] droidiac13:
Same here.
[EVO 4G Android Development] timdawgdentist:
The GPS fix pinned my CPU. However the radio combo is giving me 5-7 down and an average of 1.4-1.6 up. I thought sprint capped up but damn that's nice. Now to see if it drops my android usage to nada I'm a happy camper. Will report back.

Tim

cm7 nightly #100

tiamat 3.37
[EVO 4G Android Development] Chaosmaker2k:
Worked for me, deck 2.1x with savage 2.2.1, thanks for the hard work bro
[EVO 4G Android Development] Chaosmaker2k:
I assume if we do a full wipe and switch Rom we need to reflash the GPS fix
[EVO 4G Android Development] A1Lonestar:
This did not work for me on cm7 stable with savaged zen 2.1.0. After doing fix android system was over 50% as soon as i made a phone call. If i dont make a call it never shows up.
[EVO 4G Android Development] JBabey:
That was happening to my roomate, he redid the PC36IMG.zip and then flashed the 1.77 NV zip file, then did the GPS... charged full, reboot, and it hasnt come back on his phone.

try downing your NV to 1.77 from 1.90

Seems hit or miss, I just called him to ensure he did this, said he ran through the steps twice before it finally "took" so good luck.
[EVO 4G Android Development] lawsonmh15:
No go for me on GingerAle V4. Android system disappeared, but caused 100% wake time.
[EVO 4G Android Development] JBabey:
Can you give a little bit more information. If Android System dropped off of your battery usage, what replaced it that would tack your CPU and continue to wake-lock your phone.

Appreciate it, hopefully we can get this resolved for you.

EDIT:::: updated OP with some additional information and steps for the few people that this is not working on. Please PM me if you have specific questions that are not thread related.

Thank you,

~J
[EVO 4G Android Development] szav:
Galaxy s2 have same problem . But now it can't fix. Somebody could help me this ?
[EVO 4G Android Development] :
Try asking in the proper forum. This is for the EVO 4G only.
[EVO 4G Android Development] crypt0kiddie:
What is the difference between the two? I know the PRI is the PRI, but what is the NV one?

EVO_PRI_1.77_003.zip (154.5 KB, 11 views)

EVO_NV_1.77_003.zip (178.4 KB, 27 views)

I'm not sure that this is working for me. I mean, my GPS is locking QUICK as **** now but the Android System never goes away. However I'm getting 24 hours+ (sometimes up to 36 hours) with medium to heavy usage. I've always gotten battery life like that, it's just that the Android System as states, never goes away. On a side note, I lost my factory red colored HTC EVO battery so I'm exclusively using those cheap Chinese batteries that came out back when the EVO first came out. The ones that were like $10.00 shipped for two batteries and a charger from Hong Kong. They seem to work as well as my HTC red battery ever did.

That said, I'm using the ROM and Kernel in my signature. I'm pretty loyal to Fresh Rom with Launcher Pro Plus installed. I tried 4.1.1.0 but it was laggy as hell and my voice mail count was locked to two and I couldn't clear it so I went back to 3.5.0.1 which seems much smoother to me.
[EVO 4G Android Development] Digitalkarma:
Sweet. I've already been using this combination forever. The only thing I ever had to do was downgrade the PRI to 1.77 to fix the wakelock issue using Viruskingdom. Had no need to change it since. I also noticed old Froyo roms had wakelock issues with 1.90

1.77 is the sweet spot
[EVO 4G Android Development] JBabey:
It is my understanding, and I could be TOTALLY WRONG (disclaimer) that the PRI is your "baseband" and the NV is how the phone stores the PRI in memory. Looking back on some of netarchy's posts about the issue, he recommends sticking to the same PRI as NV, but also notes in the same sentence that any combination will work. SOURCE ~> http://xdaforums.com/showthread.php?t=719763

In this case PRI 1.77 & NV 1.90 are the bees knees, but half the PM's I am getting are saying that 1.77 NV & 1.77 PRI are the win (using of course the files on the front page for radio/wimax/gps)

About 10,000 page views and a lot of win here, so try one of the 2 combinations, post your ROM, if you know your evo version, and what combination worked for you.

Thanks for checking this out and good luck.
[EVO 4G Android Development] JOEOZUNA4U:
So the "GPS_FIX_Flashable_Kingdom.zip" works for cm7, even though its an AOSP rom?
[EVO 4G Android Development] JBabey:
Yes, the file is a pre-compiled driver, that works regardless of the "source" it was compiled from. Cyanogen is using a hacked up open source driver, it works about half the time, but its inconsistent and takes a long time to lock. This one is built directly for the chip the evo uses by HTC, works everytime, is stable, and locks extremely quickly.

If i had to wager a "guess" (disclaimer) the EVO3D uses the same GPS chip as the EVO4G. 4G development stopped, but the 3D development has been in full swing. Hence they most likely improved upon the driver for their new top end phone, and never bothered to port that change into the 4G.

By pulling that file, from that ROM, we are getting a vastly superior driver than what initially shipped with our handset.

The best part..... it plays nice with all AOSP ROM & SENSE!

Yay!
[EVO 4G Android Development] JOEOZUNA4U:
ok im sold! lol... giving it a try now..
[EVO 4G Android Development] crypt0kiddie:
So far the only thing I had done was to flash the PC36xxxx.zip and the GPS_FIX_Flashable_Kingdom.zip from the main page of this thread.

My phone shows I have PRI 1.77 003 but it seems to me I downgraded from 1.90 a while back actually.

That said, I currently have the following now downloaded from this thread:

PC36xxxx.zip

GPS_FIX_Flashable_Kingdom.zip

EVO_PRI_1.77_003.zip

EVO_NV_1.77_003.zip

Will try them out per the instructions in post #1 when I get home from work.

On a side note, I'm on hardware rev 002 (updated my signature) which I got the first day the EVO 4G went on sale. I've had ZERO issues with this handset! Knock on wood! Hope I don't jinx myself now. ;)
[EVO 4G Android Development] Sunsparc:
I haven't had issues with wake lock since I flashed the PRI down to 1.77.

Current:

CM7 nightly 100

PRI 1.77

NV 1.90

Baseband: 2.15.00.11.19

Wimax: N/A

GPS: Whatever comes with CM

Been unplugged for 1hr 20m at the time of this post, still 100% battery. That's a phone call and misc browsing for about 10 minutes.
[EVO 4G Android Development] blueblur:
howdy!

I used the second set of instructions and I'm experiencing 100% cpu usage (i'm using SeePU++ to see this) and before it would do this but would stop after a few minutes. I've been up for over 20 minutes and my battery level keeps dropping rapidly.

Is this normal? Will it stop on its own?

Cynogen Mod 7.0.3.1 w/ kernel that comes with it

v003 model hardware

----edit----

rebooted (again) and reflashed 1.77 for the third time and it looks like it stopped the high CPU usage

CPU usage dropped to idle because I turned on AIRPLANE mode prior to restart.. so it looks like its something related to a cell signal or data signal, turned off airplane mode and it skyrocketed back to 100% usage

---FINAL EDIT---

So I went back to this thread: HERE and got all the individual radios. did Radio & WiMax first.. then tried the lower PRIs and NVs as suggested in the second part of the first post in this thread. No matter what PRI or NV same result.. the only way I got it to go back down is to Reflash cyanogen 7.0.3.1 back on and it went away. Sounds to me like the GPS driver is to blame since re-flashing the ROM causes the driver to have to be reflashed. I no longer have a high CPU problem after applying one of the other GPS drivers found in this forum.

FYI... Your mileage may vary!
[EVO 4G Android Development] F1reF1ghter:
Thanks so much. Followed your steps and worked right after final reboot.
[EVO 4G Android Development] k4p741nkrunch:
I'm having trouble getting this to work 100% on Myns TwoPointTwo RLS5.

I've got a very good understanding of how this all functions, and even so I followed the instructions down to the obscurities (make a call...)

I originally followed the first set of instructions. Everything went smoothly and as expected. I charged the phone up to 100% and let it sit for 15 minutes, then rebooted immediately and turned on application monitoring. I see the system app taking up just as much CPU usage as before, literally NO change. Previously I had been on the most updated radio, PRI, and PRI-NV. I let it sit for an hour and watched the android system go down over time, but it was still at 29% after 1 hour, so I decided to follow the 'modified' instructions. Basically it's the same process but this time matching the PRI and PRI_NV, the latter you flash in recovery. Performed all the steps and everything went exactly as described again. Upon initial checking android system is at 51% usage and second in line is display at 15%. That's a pretty significant jump, and in the 20 minutes since the first boot after flashing it hasn't gone down much. I'm going to let it fully charge (and then some) again then reboot and see if this changes, but at this point my hopes are no higher than the progress.

Thankfully, if all else fails I'll just use the built-in updater to get back all my latest radios. Aside from that, the GPS fix is very good! I tested it outside and it was almost immediate and a very solid lock. Has anyone else tried this fix on Myns TwoPointTwo? If so, what is your situation looking like?

Thanks for finding this OP!
[EVO 4G Android Development] Tragicwayz:
Will this work on MikFroyo 4.5, I want to go back to the stock battery.
[EVO 4G Android Development] lowspeed:
So after i did all this i still have android system using 90% of the CPU at all times....
[EVO 4G Android Development] JOEOZUNA4U:
Even after this

"Now heres the weird and tricky part so listen closely. At this time you will still see the Android System in your battery stats. This is normal. To see the fix, you need to charge your phone fully to 100%.... and honestly give it an extra 10-15m on the charger after it says its full. Now..... REBOOT the phone when you pull it off the charger. Use the phone a little bit, make a phone call... it may still pop up around 5%.... again this is normal..... after 2-3 hours however it will be gone, completely and utterly gone... it will never show up again."
[EVO 4G Android Development] lowspeed:
Indeed weird ... :) I'll give it a shot !
[EVO 4G Android Development] JBabey:
I see someone replied w/ the final part and that is good (thank you) also please give a little bit more information such as what hardware your evo is, what ROM you are running and any other customizations such as kernel.

My wife had Android OS on hers hovering around 70% or so after she updated to the latest cyanogen nightly 105, this time around she did the bottom method, and hasnt had it show up yesterday or today after much use and several reboots.

Its a "glitchy" and unpredictable issue, and as such theres no magic bullet solution unfortunately, it does seem that this is working for most people across roms/hardware and the more information we gather here, the better off everyone will be.

Keep me posted please.

2 previous posters have reported it to be working for them on MikFroyo
[EVO 4G Android Development] k4p741nkrunch:
Since the 'modified' instructions were run, including the charge and reboot, my device is only getting 456 kbps down and 450 kbps up, jumping from no bars to 3 bars every 15 seconds. I'm going to update it all back to the latest for now. Looks like this isn't really compatible with my phone.

Hardware Rev: 003

Rom: Myns TwoPointTwo RLS5

Kernel: Netarchy sbc-cfs-nohavs-staticUV

PRI : 1.77

NV: Tried 1.90 and 1.77, had better stability with 1.90

I'm sure there's something that I'm not factoring in. I haven't seen anyone discussing Myn's rom in this thread so it might be unique to that ROM or my kernel. I'm going to follow this thread and try and figure this out. Number one issue with Android IMHO.
[EVO 4G Android Development] JBabey:
Ill grab a phone and flash MYN on it later today and see what I can come up with, I know its an uber popular ROM, it just wasnt one of the originals that I had tested on. Keep in mind that the new Radio was built around Gingerbread, and that may be the issue. I would recommend radio 11.19 for Froyo as that is what I had the best luck with when I used to run Fresh 3501
[EVO 4G Android Development] MizzouBrent:
I did this fix the other day and it seems to have eliminated my android system issues. I would routinely show 50 or 60% usage. However, this morning I noticed that I had like 3 reboots in a 15 minute span. I am on CM7.0.3.1 with Tiamat 4.0.5. After the three reboots, I flashed over to GoDm0de v8 thinking that maybe the kernel wasn't playing nicely. However, now I notice that my CPU seems to be stuck at 100% usage. I'm thinking that maybe it's the Virus GPS Driver, but I'm not 100% sure. Is there anything that will show you exactly what is causing the CPU to spike? I have never really had to mess with this before, and I'm not even 100% sure what is causing this.
[EVO 4G Android Development] JBabey:
I am glad you posted, yes it is the ViRuS GPS driver, head over to this thread here

~> http://xdaforums.com/showpost.php?p=14534313&postcount=2478

and grab one of those "known to not cause wake issue" GPS Drivers. It is reported by several that this has eliminated the 100% CPU issue after the fix takes place.

Enjoy wake-lock free handset!

EDIT: updated OP w/ this information.
[EVO 4G Android Development] MizzouBrent:
Awesome thanks! Was his original driver causing wake issues as well? I notice that he says that these are the fixed drivers. I think my issues with reboots and battery drain started popping up when I started flashing these alternate GPS drivers.
[EVO 4G Android Development] lowspeed:
Still getting android system at 90% :( (After 100% charge)

device feels really slugish.

Any ideas?

Cm 106, hw v3
[EVO 4G Android Development] MizzouBrent:
I assume that galandy's driver won't interfere with your fix, so the GPS driver is essentially interchangeable with Virus? Does Virus have a version that doesn't peg the CPU at 100%?
[EVO 4G Android Development] JBabey:
Please look at the OP, there are 2 methods, and notes that a few members have had to attempt the fix more than once before it would take. In regards to sluggishness, this really wouldnt "slowdown" your overall handset. I just updated to the latest nightly, and its running fine for me. As a sidenote :not topic related: i run savaged-zen 2.2.1 with smartass governer 284 min 1036 max and my phone flies like wonderbread.

The original driver, and some of the ones the AOSP roms are using are conflicting on a low level with something in our baseband or nv, hence the GPS being part of the fix...

Its not that its "interchangeable" or not, its a driver written for the GPS chip inside of our phones... now... how your specific rom chooses to communicate with the driver etc is out of my control. The other reported working driver is from an HTC Vision handset so make of it what you will lol. The ViRuS GPS driver is working amazingly well on my phone (HW 0003, old partition setup) on Cyanogen, and was also working fantastic on MIUI (I switch back and forth a lot).

Take a look at the kingdom thread

~> http://xdaforums.com/showthread.php?t=1071547

Thats where I got the driver from. I can package up the one from the Synergy ROM that he is working on with Myn and a few others if you want to test and report back. Let me know how you wish to proceed.

I have been rambling, which specific issue are you experiencing that the original GPS driver &/OR Vision driver created?
[EVO 4G Android Development] lowspeed:
Well it was slugish before with android system taking 90% of the CPU. So it's not the fix.

I just wiped clean and doing titanium restore for the apps.

not a biggie.
[EVO 4G Android Development] JBabey:
aha, i hate doing a full wipe and restore, good luck with that
[EVO 4G Android Development] MizzouBrent:
Well, I thought I had been experiencing battery drain with Virus/Kingdom driver and was definitely seeing reboots. Seeing as how it was spiking my CPU, that makes sense that I was having those issues.

I had tried the alternate driver posted by Galandy a week or two ago. It seemed like suddenly my battery would drop like a rock at night where before it would barely drop a percent or two at night. On the post you linked, Galandy mentioned it was the "fixed" driver. So I was wondering if there was a version that spiked the CPU (like the Kingdom driver) and then he later fixed it to not do that anymore.

So I guess what I'm saying is, the Virus/Kingdom ROM seems like a no-go and I was questioning whether galandy's posted driver would do the same. It seems ok now, but I'm definitely keeping an eye on it.
[EVO 4G Android Development] Brian Rubin:
I'm in this boat and am quite happy with my battery life (using Cyanogen with SavagedZen BFS), but I'm gonna follow this thread just the same. Nice work. :)
[EVO 4G Android Development] mercado79:
I haven't seen much talk about this, but the Friday before last, Sprint upped the upload cap to 1.5mbps.

http://www.androidpolice.com/2011/0...p-to-increase-from-1-0-to-1-5mbps-on-june-10/

Speeds overall have been very good with this combination though.
[EVO 4G Android Development] DataDork:
I am now getting roughly 1.2-1.34 on my uploads .. its nice to have but i dont even use it lol.
[EVO 4G Android Development] k4p741nkrunch:
After a good 4 hours of use my Android System has dropped underneath my wifi and my cell standby. This is a significant improvement over what it was initially!

I ended up flashing the PC36IMG.zip from the first set of instructions again, this time without re-flashing the GPS fix or fixing the UID mismatches. I actually haven't even over-charged my phone and rebooted yet, which I plan to do when I'm out of work. I think for the most part I have this worked out. Down to 72% at 5:30 PM from when I took it off the charger at 8:30 AM. Thats 3.1% an hour (I flashed these radios while I was still at 100%), but I think most of the battery loss was from time spent in the bootloader and recovery menus (they always drain battery faster).

Overall I'm pretty excited about this fix! I'm going to run some more rigorous testing when I get home, though I've been monitoring the 'system' process specifically all day with System Monitor Pro so I should have some good stats already. Thanks OP!
[EVO 4G Android Development] s2kdriver:
I also had the pegged CPU after loading the GPS fix, but I just happened to have the old CM7-N37 GPS flash file still on my sdcard, so I figured what the heck. Well it worked for me. Brought the CPU back down to normal.

Post 4591 for CM7-N39-GPS-Driver_Supsersonic.zip
[EVO 4G Android Development] thearch1tect:
I'm currently on miui but when I was using cm I'd have the high android os all the time. Most notably it would spike after a phone call. My question is I'm seeing high voice call usage on miui so would this fix that issue since it seems to spike after making calls on this rom as well?

My current voice call usage is at 71% and I've been off the charger for 15.5 hours and the usage under voice calls shows 2 hours 9 mins. Seems exceptionally high considering i use my phonw constantly throughout the day with texts, Facebook, xda, etc.

Thanks for any help!
[EVO 4G Android Development] sudhirkhanger:
No Android system or OS in past two hours. Thanks a ton.
[EVO 4G Android Development] JBabey:
To be completely honest, voice calls should be at/near the top as it is the single largest drain on the phone you can do, followed closely by the display. Heck, take a look at the attached picture one post up... that is normal!

If you dont see "Android System" or "Android OS" then you are NOT suffering from wake-lock and I would avoid making any changes to your system. I run MIUI pretty frequently and you would know if you suffered from this issue (trust me).

If you do decide to switch back to Cyanogen and your wake is spiking after a call then yes, you should run through the steps in part 1.

_______________________

EDITED OP: the Vision GPS Driver is showing more consistency for working on the first go around with the radio combination and is not giving 100% CPU on miscellaneous ROMS. I want to thank the testers that have been working with me behind the scenes for particularly troublesome handsets.
[EVO 4G Android Development] rocker2344:
Thanks

This will help

Just finished flashing everything (i also had to downgrade cynmod due to a wifi issue) i hope this will increase my battery life even more so. if not, well nothing ventured nothing gained.
[EVO 4G Android Development] sudhirkhanger:
4% of Android System usage after 4-5 hours of use. I used to get around 4-5% of display battery usage with chainfire 3D which have now spiked to 30-40%.
[EVO 4G Android Development] timdawgdentist:
well its better the first day and a half android usage went up to 50% after a few days. However my device temp is down overall. And battery usage isnt to bad for a 3500. I am going to downgrade the nv to 1.77 and see if that makes a difference.

tim
[EVO 4G Android Development] thearch1tect:
Thanks for the input!
[EVO 4G Android Development] MizzouBrent:
I am still seeing some kind of wake lock issue even with the Vision driver. I was getting 100% CPU usage with the Kingdom driver, and I am certain that I am NOT getting high CPU usage with the vision driver, so I am puzzled. My setup is

CM7.0.3.1

GoDm0dev8 (but have also used Tiamat 4.0.5 and SZ 2.2.1 and seen this)

Radios as posted in the OP (current baseband, 1.77 PRI, current wimax)

I believe I first noticed this after the new radio updates came out. Nothing looks fishy on my battery usage stats in the Settings menu. Cell Standby and Idle are the leading processes.

I don’t have any wakelock issues in Spare Parts. I’ve noticed that “Sensor Usage” for Android System, Dialer, Camera and Gallery are all in the 3 to 5 hour range, but maybe that’s normal? I don’t normally look at this menu.

I am starting to think that maybe I am having some issue with Wifi with these radios and that maybe it is conflicting with Wimax. I say this because when I’m at work, with no wifi, my battery drain seems normal. But at home, where I use wifi, my phone will routinely drop 50% by just sitting on the table overnight. Last night it dropped from 66% to 18%. I can’t figure out what is causing this. Should I re-flash the radios? Flash to a Sense ROM and update Profile? I’m at a loss.
[EVO 4G Android Development] dirkyd3rk:
I feel like my phone is constantly overheating with the 05.02 radio; I switched to the 11.19 radio and its not hot anymore. I did one day with each radio to test. How is this possible? All I changed was the radio 0_o
[EVO 4G Android Development] manup456:
Worked with no issues at all thanks for the tweak.