[EVO 4G Android Development] JBabey:
Thread has shed some light on new issues and some other fantastic developers have chimed in with a lot more insight into this issue than I had originally anticipated when I started this thread. Please read the below post in FULL, and skip to page 31 for where this discussion picks up. ~> http://xdaforums.com/showthread.php?t=1128135&page=31

I have left the previous OP in-tact so if you would like to follow from the beginning you may. At this time, I can no longer recommend the below steps!!!, but I can still let you know that the GPS driver files below are pretty damned awesome.

~J

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I believe I have FINALLY figured out how to solve the infamous "Wake-Lock" or "Keep Awake" of Android OS that seems to drain the battery on end. It took several hours of reading forum posts, several DAYS of testing on 5 different EVO's (I work at Sprint) and have tested the fix across a multitude of ROM's, including Sense.

I will post a short history of the issue as I know it here for those of you hitting this thread for the first time, skip below for the solution I have found.

Requirements:

-Radio S-OFF

-AmonRA Custom Recovery

-Android System always at or near the top in your battery usage

History

To the best of my knowledge the issue first started to appear in AOSP ROMS when the Cyanogen team stopped using HTC Blobs to control the driver for the GPS, As a great many custom roms utilize cyanogen for many of their own enhancements and fixes the problem began to propagate out to the community at an alarming rate. Restoring your system back was a hit or miss on if it actually solved the issue or not, and more RADIO files were getting leaked/posted online and many people were flashing a multitude of firmwares to their handset making the issue confusing and seemingly with no correlation on handsets with the people having issues.

I came across ViRuS Kingdom ROM and read about 1000 pages of posts and the conclusion from their team was that the PRI needed to be downgraded to 1.77 and behold, it worked......(mostly)......

I wondered how the PRI had anything to do with the fix, and mixed that with many, many other forums I have read on the issue realized myself that there was a correlative cause and that we all did indeed have something in common. Everyone was on a different radio/pri/nv/wimax combination. I decided to run some tests myself as I have access to ****loads of handsets being a Sprint employee and here is what I have found.

I have found exactly 1 combination that has fixed the issue on every single handset I have tried it on, hands down across the board on a great cross-section of ROMS.

-Cyanogen

-Kingdom

-MIUI

-SavagedZen

-Synergy

-Mik's

-Sense 3.7 build

-Sense 4.22 build

-FreshEVO 3.5

-FreshEVO 4.1

______________________________________________________________

THE FIX!

The fix is a combination of...

Radio: 2.15.00.05.02

PRI: 1.77_003

NV: 1.90_003

WiMAX: 27243

GPS: HTC VISION GPS ".so" file

-Download the below PC36IMG.zip It is a custom Combo Radio installation I created that will set your Radio/Pri/NV/WiMAX to the above settings

-Move the PC36IMG.zip file to the root of your SD-Card and reboot the phone into bootloader. It will load the file and prompt you for an update, you will see on the left 3 items that will be upgraded on your handset. Hit volume up to accept

-Reboot the phone after the Radio update, go ahead and remove the PC36IMG.zip file from the sd-card and put it in a safe place

-Download "GPS_FIX_Flashable_Vision.zip" and put on your SD-Card

-Reboot into Recovery (I highly recommend AmonRA 2.3)

-Wipe Cache & Dalvik Cache. Now wipe them again just to be safe

-Choose "Install zip file from SDCard"

-Navigate to GPS_FIX_Flashable_Vision.zip and choose install

-Once installed go down to "Other" and "Fix UID mismatches"

-Reboot the phone

______________________________________________________________

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.

I have tested this on 5 handsets hardware revision 0002 0003 & 0004, and about 6-7 ROMS both AOSP & Sense and have yet to see Android OS re-appear. This is not to say that it will work for everyone, but I think that after my testing, there's an excellent chance that this will work for you.

Please leave feedback if this works or does not work for you please so that everyone can benefit from your experience, either good or bad. Please, please please, follow the final instructions carefully, it does literally take a few hours to test and get the old stat to wipe from the battery history, that is why I started this, literally 2 weeks ago, and am just posting now. I tried TONS of combination's and this is the one that struck gold, then I needed to test this combination on all of the phones I had sitting in the back for this. If mirrors are needed please let me know, and I will upload.

Good Luck!

PC36IMG.zip

Radio: 2.15.00.05.02

PRI: 1.77_003

NV: 1.90_003

WiMAX: 27243

http://www.multiupload.com/HJOWHOLW4G

Qualcomm Vision GPS Driver

Sense GPS Driver File from Qualcomm Vision

http://www.multiupload.com/11IWQ99VKH

EDIT:

A few reports on certain ROMS of excessive CPU usage after Android OS has dropped off the list

Please use one of the two below GPS drivers if you experience 100% CPU usage (Source: http://xdaforums.com/showthread.php?t=1132412 )

~>AOSP<~

CyanogenMOD 7 Nightly 39 GPS Driver (HTC Blob File Compiled)

http://www.multiupload.com/NIJEKWGDEQ

~>SENSE<~

KingdomROM GPS Driver FIX

Sense GPS Driver File from EVO 3D aka "Kingdom"

http://www.multiupload.com/ZMOXSDJBOE

EDIT: It has come to my attention from a few members in PM, that the issue doesn't always "take" right away. People have reported that it can take 2 or 3 attempts, and 9 different people have reported that they have run the 1.77_003 NV after flashing the radio, and then running the GPS to resolve the issue.

---------------If the above fails for you after a 2nd attempt. Please follow these Modified Instructions

-Download the below PC36IMG.zip It is a custom Combo Radio installation I created that will set your Radio/Pri/NV/WiMAX to the above settings

-Move the PC36IMG.zip file to the root of your SD-Card and reboot the phone into bootloader. It will load the file and prompt you for an update, you will see on the left 3 items that will be upgraded on your handset. Hit volume up to accept

-Reboot the phone after the Radio update, go ahead and remove the PC36IMG.zip file from the sd-card and put it in a safe place

-Download "GPS_FIX_Flashable_Vision.zip" and put on your SD-Card

--MODIFIED STEP-- Download "EVO_NV_1.77_003" ~> http://www.mediafire.com/file/i1p436188iw0iqb/EVO_NV_1.77_003.zip (source: http://xdaforums.com/showthread.php?t=715485) & put the file on your SD-Card

-Reboot into Recovery (I highly recommend AmonRA 2.3)

-Wipe Cache & Dalvik Cache. Now wipe them again just to be safe

-Choose "Install zip file from SDCard"

--MODIFIED STEP-- Navigate to EVO_NV_1.77_003.zip and choose install, once installed you will see a note at the bottom to reboot the phone. Choose the "Reboot Phone" option in AmonRA and let the phone reboot

-You will see the screen blink, go into recovery and hang, this is completely normal, just wait about 30 seconds and the phone will Automatically put you back into your recovery

-Choose option Flash zip file from SD-Card

-Navigate to GPS_FIX_Flashable_Vision.zip and choose install

-Once installed go down to "Other" and "Fix UID mismatches"

-Reboot the phone

Pickup the rest of the steps from above. PLEASE REPORT back your experience!

++++++++++++++++++++++++++++