yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] fitz420:
I can also confirm that the flashable phone.zip provided by daklown does work. No more mpokelock after making a phone call, and so far no issues whatsoever related to flashing it. Thanks for your hard work. I'm running decks 1.2 and SV 2.2.1.
[EVO 4G Android Development] lowspeed:
Same. Thanks :)
[EVO 4G Android Development] MizzouBrent:
Another confirmation that the phone zip releases pokelock
[EVO 4G Android Development] cheapskate88:
Yeah, how do you switch out those drivers? Anyone have any idea?

Also, where can we find the latest NV?

Edit:

Found the latest combo

http://xdaforums.com/showthread.php?t=1110733
[EVO 4G Android Development] DaKlown:
I just realized that maybe the second part of my post isn't clear about the high android system issue. First let me say that the phone app provided does not cause the high android system problem on aosp roms. My theory is that the proximity drivers used in cm cause it. Here is how to check. In my post the second zip file contains 2 files. One is called " sensors.supersonic.so". This file tells tells android the location of the drivers for the phone's proximity drivers. I have edited this file so that no drivers are loaded. If you use root explorer or adb you can go to /system/lib/hw and replace the file with the one I provided. Your proximity sensor will no longer work but the android system spike in battery usage should stop. This is just a temp solution until I find working drivers. The second file in the zip is named "sensors.supersonic.so.bak". It is a backup of the original unedited driver location file. This is so you can turn your proximity sensor back on if needed. Basically you are just turning it off temporarily to see if your android system spike is caused by the proximity sensor. Hope I was clearer this time. Sending this from my phone so I apologize for spelling and grammar in advance.
[EVO 4G Android Development] cheapskate88:
You were already pretty clear on your origianl instructions, but thanks for the additional clarification. Also thanks for adding instructions to where and how to switch out the drivers. I'll be testing that out in a minute.

Replacing in /system/lib/hw

Update:

The phone app works perfectly. Anyone replacing the drivers might need to reboot for the system to take it. Otherwise, it works!!!!!!! No more android system spike after a call!!! And honestly, I'm ok with losing the proximity sensor for now. You can just as easily hit the power button.

Thank you!!!
[EVO 4G Android Development] wryun:
Just applied the new files.

I wiped cache and dalvik.

Re-flashed my ROM (deck's 1.2)

Re-flashed the GAPPS

Flashed the latest radios from here

Flashed Savaged Zen 2.2.1 Kernel

Flashed phone .apk

Booted phone, replaced the .so file

Rebooted phone

Now it's time to see how my phone does during the day.
[EVO 4G Android Development] DaKlown:
Thank you for the quick feedback. Looks like I might be right about a number of evos not being compatible with the current cm proximity drivers. I'm away from my desktop right now but I will try to have a more permanent fix later this evening. We shouldn't be forced to lose functionality just because we want to use aosp roms.
[EVO 4G Android Development] jae04cc:
Yup it was the drivers..the replacement fixed it

Sent from my Evo powered by CM7 Nightlys
[EVO 4G Android Development] BuddaBelly:
Wish we could get some pokelock love for sense.
[EVO 4G Android Development] fitz420:
DaKlown is DaMan.
[EVO 4G Android Development] JBabey:
I have updated my OP if you dont mind with your comments and I really appreciate you and rope chiming in on this thread to help everyone in the community understand where the actual root of the issue lies. I am assuming the proximity sensor is what turns the screen off when you hold the phone close to your ear. I have inner ear problems and cannot hold a cell phone to my ears, as such I use an auto-speakerphone program and it turns my screen off when the speakerphone comes on after I answer the phone. This may account for all of my testing w/ radios not triggering the wake-lock, and when I test the phones, I place test calls and set them on the tech-bench and let them run.

I am pretty amazed how it all came about like a "perfect storm" of inaccuracy, and a little more amazed how well the previous fix seemed to work for a lot of members in the community. My assumption is that the GPS was just borked on a lot of peoples customs.

I look forward to a full bout of testing, and corrected drivers that can be incorporated into the source code for cyanogen and that the authors basing roms off of their branch all see relief from this issue going forward.

Thank you very much for your help, and I look forward to an approved, tested, fully functioning fix here shortly.

If you need any help from myself, I have access to near unlimited phones so please PM me.
[EVO 4G Android Development] lowspeed:
Yeah i don't think it has anything to do with the radio combo.

GPS driver maybe.

I'm surprised Google is not working on this issue.
[EVO 4G Android Development] cheapskate88:
Because it's not an Android issue. It's an Evo issue.
[EVO 4G Android Development] lowspeed:
It still reflects on their product. But i see your point.
[EVO 4G Android Development] cheapskate88:
So I think I just found an unwanted side effect... my accelerometer has stopped working.

Fyi, I've applied both fixes. I'm assuming its the replaced driver.

Would someone else confirm?
[EVO 4G Android Development] wryun:
WHOA! Good catch! Doodle Jump doesn't work now. LOL
[EVO 4G Android Development] bigjoexxl:
After flashing the fix,.do I need to update my PRL again? I did notice my 3g speeds aren't as good now..
[EVO 4G Android Development] JBabey:
flashing which fix?

DaKlowN fix = no, it only effects your phone.apk and your proximity sensor driver, has zero effect on your 3G

Original FIX using radio's.... should have no effect, but cant hurt. As the radio appears to NOT be at the root of the issue, I would recommend reverting to the radio combination you had prior that was working best for you.
[EVO 4G Android Development] fitz420:
Tested again......I only installed the phone.zip and my accelerometer works fine.......if any1's is borked I'm assuming its the proximity fix
[EVO 4G Android Development] DaKlown:
Is there a pokelock on sense? If so it wouldnt be as easy to fix since Sense is closed source and you cant just change the code, compile it, and then pull out the phone apk. Let me know and i'm sure we can get to the bottom of it. As I stated earlier I havent been on sense roms for my findings.

Thanks and will do. Also I would like to note that I have done zero testing on sense roms so I have absolutely no idea whats the issue if there is one with the OTA. Maybe the radios fixed it for people running sense?

Technically Google's only responsibility is the Nexus line of phones...

This is why the zip I provided has two files. One is an edited sensors.supersonic.so and the other is the original file which is renamed to sensors.supersonic.so.bak. If you rename sensors.supersonic.so.bak to sensors.supersonic.so you will go back to the original file without needing to nandroid just reboot for it to take. The edited file will most likely bork your sensors yes. As I stated this is only temporary as I was trying to narrow down what was causing the high android system in battery usage on aosp roms. Only use the edited sensors.supersonic.so file if you can deal with not having sensors until I post a more permanent fix. I'm not at my desktop at the moment So It will probably be this evening before I can post another file. Atleast we have pin pointed the cause of the high android system right? :D

Just go back to the original sensors.supersonic.so file until I can fix it permanently. I assure you no harm has been done.
[EVO 4G Android Development] BuddaBelly:
There is for sure pokelock on sence because its always on on my dumpsys power screen. I never have wake lock issues just the pokelock. Looks like we might just have to live with it on sense for now.
[EVO 4G Android Development] cheapskate88:
No worries! I just wanted to make sure I hadn't done something else to screw with the accelerometer. Thanks again for the fix!
[EVO 4G Android Development] JBabey:
You sir... are both a scholar and a gentlemen. I await your solution on bated breath!
[EVO 4G Android Development] spider2346:
Fix worked like a charm!! Android OS has vanished like a fart in the wind! Thanks for the fix :)
[EVO 4G Android Development] lowspeed:
Mine is at about 30% but boy is the battery much better.
[EVO 4G Android Development] jae04cc:
yes i have reverted back to the original .so file, and sensors work again, and there android system is again..good work!..and i too am anxiously waiting for your new fix...thanks! (ill also hit the thanks button lol)
[EVO 4G Android Development] bytes2bits:
Is it normal to have SOME android system when looking in Spare Parts under partial wake loc.?I installed both fixes and I no longer show Android System under battery use after a phone call. I just see it under spare parts partial wake loc. I assume this is just from normal screen use?
[EVO 4G Android Development] MicrosoftBug:
I hope somebody will come up with a way to make this phone.zip work on sense ROMs.
[EVO 4G Android Development] ropodope:
it already does. Flash it and you are done.

EDIT: thought you said aosp roms. Sorry.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.1 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] raphenucleus:
I've posted this before elsewhere, but people still seem to think it's necessary to flash to the latest NV, so I'll post it again. As far as I can tell, there is no 2.15_003 NV. If there were why wouldn't Calkulin have included it already? Why would he pull just three out of the four files for the latest radios from the latest OTA? There's a download of a supposed version here, but it appears to be the same nv.img file as 1.90_003 from back in November; they have the exact same time stamp (11/16/2010 3:39 PM) and are the exact same size (655,360 bytes). I'm not quite sure how to look at the code of a .img file, but it seems pretty convincing to me, especially considering that the radio, PRI, and wimax files in both combo packs are dated 5/23/2011. I'm guessing drmacinyasha mislabeled the NV in his post as EVO_NV-2.15_003 and the NV wasn't even updated past 1.90_003 in the latest stock ROM.
[EVO 4G Android Development] BuddaBelly:
I'm with you man. My dialer is running at 23 percent today because I'm just sick of killing it every time I make a call. I will say I never had this poke lock problem until the latest EVO updates. I'm sure something will be figured out.
[EVO 4G Android Development] pie944:
Had the Android System usage following calls with Deck's 1.2(Kernel is Tiamat latest SBC). Flashed the Phone zip and still had the problem, replaced the prox. sensor file and just made multiple calls without any android system showing up in the usage. Appreciate the time and effort.

pie944
[EVO 4G Android Development] JBabey:
just flashing the phone.zip on my wifes handset resulted in the same... no change... but the sensor file works like gangbusters
[EVO 4G Android Development] ropodope:
Hey daklown, my dev buddy wants to get a hold of scott brady. Know how I can do that? Thanks.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.1 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] sbradymobile:
Just PM me.
[EVO 4G Android Development] ropodope:
hey scott, thanks.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.1 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] pie944:
People just accepting the Prox Sensor change for the time being and loosing the accelerometer?

pie944
[EVO 4G Android Development] ropodope:
Not me. When the fix is here I will be glad to swap it but still want the accelerometer either way.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.1 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] wryun:
I'm not. I will wait for a better fix.
[EVO 4G Android Development] BuddaBelly:
All I need is a dialer fix for sense and I would be happy. 12 hours and now having to charge. Dialer taking up 32 percent second only to Display. Dang pokelock!
[EVO 4G Android Development] jae04cc:
+ 1

Sent from my Evo powered by CM7 Nightlys
[EVO 4G Android Development] imheroldman:
Question: does this replace the dialer or just give another option? If this fix doesn't solve anything how can I revert to stock dialer?

CM7.1 Tiamat 4.0.5

Sent by Supersonic
[EVO 4G Android Development] DaKlown:
It replaces the actual phone app. No matter what dialer you use or download from the market when the actual phone call is placed the android dialer is used which is what this replaces. So in short if you use dialer one or some other dialer it will still remain the same.

Also a better fix is close.
[EVO 4G Android Development] sbradymobile:
Explanation for high Android System usage related to Phone app (CM7)

Basically the Phone app creates a wake lock (the proximity sensor disables the wakelock and allows the screen to sleep) and holds it throughout the duration of the call. This is the keep awake time you see in battery use under android system. Because this is held for much longer than most programs hold a wake lock you will see high android system usage.

Some testing needs to be done to determine whether there are power savings without using the sensors in the Phone app and how large they are.

Below is a flashable Phone app with the proximity and accelerometer parts stripped out. I will update this with a preference to enable / disable proximity in a few days. The default in call screen timeout is 5 seconds (extend to 15 seconds with the Keep screen awake option in Call settings).

NoProximityPhone.zip

To return to your rom's original phone version: extract the Phone.apk from the rom's zip file and replace the Phone.apk in the above zip file then flash.
[EVO 4G Android Development] pie944:
So why do some people have this issue and others do not? Is it hardware dependent? ROM dependent? Seems like it should be a more pressing issue.

pie944
[EVO 4G Android Development] ropodope:
it affects many people but not any one person all of the time. The problem comes and goes. You've probably had the problem here and there and never knew it at the time.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.1 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] imheroldman:
Its definitely a ghost in the machine...

Flashed the no sensor phone app. Not all that bad to just hit the sleep button when making a call. Waiting on an over night charge to see results tomorrow

Sent by Supersonic
[EVO 4G Android Development] fitz420:
So is this a better fix than the drivers daklown posted before in the sense that the accelerometer wont be borked? The only reason I didnt replace the drivers before is that I need the use of the accelerometer for other apps.

Thanks so much for sharing your hard work, btw
[EVO 4G Android Development] Greatbape:
I applied the fix and my accelerometer still works. Proximity Sensor is off also.

edit: Ok this only disables the phone app accelerometer. Normal accelerometer functions still work. Guess I missed that part. Thanks
[EVO 4G Android Development] Biggie Da Dansa:
I flashed the new cyanogen mod and also did this updated and if been feelin like im geting ****ty 3g is anyone else experiencing that? But other than that thanksbl for the fix jay
[EVO 4G Android Development] Greatbape:
On a side note. I'm also getting very high sensor usage from the gallery, drocap, and camera app. Luckily I can change drocap trigger and use a different gallery app. Still not sure what to do about the camera yet. Just wondering if all the sensors are messed up in cyanogen.
[EVO 4G Android Development] sbradymobile:
Yeah, the no proximity phone version only disables the in call sensor use (and fixes the poke_lock_ignore_cheek_events). In the normal phone app the always use proximity setting disables the phone app's accelerometer listener. The accelerometer listener is used to disable the proximity wake lock if the phone is horizontal. So I just disabled the proximity stuff and removed the accelerometer setting to test if that was the only thing throwing off the stats. This is mainly a test to see if the proximity sensor usage is actually draining the battery faster and/or if it is the main cause of the high android system battery usage stats. I don't expect to see much of an increase in battery life (and personally prefer using the proximity sensor so I'm only going to test for a day or two) but it does allow some relief to see that some android system process isn't running wild.

You can use the first Phone.zip if you don't wan't to disable the in call proximity sensor. The first one fixes the poke_lock_ignore_cheek_events showing up in the power logs, but I haven't tested any battery improvements. The sensor zip should only be used if you wish to disable the sensors in all apps.

@Greatpabe

Gallery uses an accelerometer sensor manager and Camera uses Gallery to show the gallery preview and add images. It isn't a problem with the sensors, it is simply reporting that those are the apps using the sensors. When an app enables the sensor, there will be a report of sensor usage. Most apps are designed to disable the sensor when the app backgrounds; for some apps it needs to run in the background (like screenshots). It is really a problem at the app level; I will see if I am having any problems with Camera or Gallery not turning off the sensor and let you know.
[EVO 4G Android Development] ropodope:
sounds like a question for the cm forums.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.1 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] Greatbape:
I used my camera for about 10 secs to take a pic then went into gallery for about 30 secs. In spare parts under sensor usage Gallery is at over an hour of usage, and camera over 20 minutes. Yet they aren't keeping the phone from sleeping. Not sure if it's draining battery or not, but I'll ask and look around on the cyanogen boards.
[EVO 4G Android Development] ro_bro:
I have a similar issue in both MIUI 1.6.24 and Deck 1.2. It's not the partial wakelock that's high, it's the Android System - SENSOR usage that's high. It's almost equivalent to my phone's total ON time.
[EVO 4G Android Development] BuddaBelly:
I know this has moved on to the sensor discussion but thought I would post a pic of what's going on with the dialer on sense. The strange thing is that voice calls isn't even reporting correctly as it shows me having 28 minutes talk time and it has been double that and the dialer is showing 3 minutes usage but yet its 3rd on my usage list with 17 percent. Something is definitely wonky.
[EVO 4G Android Development] DaKlown:
I can't confirm this on the stock gingerbread rom. What are you using.
[EVO 4G Android Development] BuddaBelly:
MikG 2.1+3.0 Shift Port. Honestly I couldn't tell you if it's really effecting battery or just effecting stats. I didn't use my phone for much today other than phone calls.
[EVO 4G Android Development] DaKlown:
My mistake. It's in the dumpsys now. Maybe its a gingerbread bug. I'll look into it after these senaor issues are resolved. I've been on a stock gingerbread sense rom all day copying logs of sensor usage data on sense and i don't have a high dialer usage in battery stats though.
[EVO 4G Android Development] BuddaBelly:
That's great. I appreciate it.
[EVO 4G Android Development] pandafloski:
just tried the .so file on CM7, but the proximity sensor still works. I just replaxed the original .so in /system/lib/hw/. Did I miss something?
[EVO 4G Android Development] ropodope:
Just flash the noproximity.zip from recovery. Its easier. No fuss no muss.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.1 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] Circular Pastry:
Flashed phone.zip now this... at least system didn't use all the process? LMAO

Any suggestions as to what the hell happened?

Yes, I will re-read and flash something else or reflash that zip... but I HAD to share.

Tapatalked from my SUpersonic...
[EVO 4G Android Development] Greatbape:
What's your partial wake usage in spare parts. After i applied this fix Handcent was keeping my phone awake with the popup menu. It's bugged currently. Not sure if you use that at all though.
[EVO 4G Android Development] Circular Pastry:
Partial Wakelock:Android System

Total Time:22m 52s

Partial Wakelock:Email

Total Time:6m 23s

Nothing else above 5min. No Handcent, I use Google Voice (even it was <5m)

Trying a new dialer (TouchPal) but that shouldn't matter if I'm not seeing it listed, correct?

Tapatalked from my SUpersonic...
[EVO 4G Android Development] Greatbape:
For 15 hours and only 22 minutes wake lock being the highest is actually pretty good. Don't see a problem overall. I have everything google pretty much turned off though. Only have K9 going in the background. My battery screen looks identical except for the Android system. Only thing that kills my battery now is my weak signal. 0-1 bars at all times.
[EVO 4G Android Development] aaanadie:
I think it is a sense gps driver taken from kingdom, sense roms do not need it but should work in any aosp rom.
[EVO 4G Android Development] linsalata28:
This should work with kings alliance ROM right?

And can anyone confirm that this is working also my GPS locks at 10m should I do the gps drivers or is that good enough?

Sent from my Allianced Evo ! o_O
[EVO 4G Android Development] imheroldman:
Thanks for doing this research! Going to flash tonight I will post back.

Sent by Supersonic!
[EVO 4G Android Development] dgrobe2112:
how long are the batteries lasting like this.. i am using REVOlution 1.3.. not sure how long it will last for a day..
[EVO 4G Android Development] sshark:
People pl stop quoting long-ass posts ...sheeesh
[EVO 4G Android Development] dgrobe2112:
Srry.. fixed.. :)
[EVO 4G Android Development] imheroldman:
Ok couldn't wait, flashed! Just an observation, gps fix says cyanogen gps fix when run in recovery. So apparently not sense based.

Plus, my gps is now spot on and lightning quick and doesn't get stuck on!

Sent by Supersonic!
[EVO 4G Android Development] JBabey:
Android System should NEVER show up in the battery stats after the first 15 minutes or so of being off the charger. It should drop of almost immediately if it shows up at all.

Yes you would as a nightly will overwrite the GPS driver

You can flash the radio as many times as you like. If your GPS is working fine AND your Android System is not showing up, then dont touch it. If your GPS is working fine AND the Android System is showing up, then yes you should flash this. The defunct driver causes the phone to not be able to go to sleep properly and "hibernate" so the battery is draining constantly even with the screen off.

A good compatible set of radios will work wonders on intermittant issues. Im glad this helped.

The kingdom ROM is very solid and this will not help you on this ROM if you are already on the correct radio revisions. Just follow the instructions on the thread and ensure your PRI is 1.77

If your Android OS is NOT showing up in the battery usage, and your GPS works, avoid making any changes to your system...

It does say that yes, I originally posted this on the cyanogen forums as the fix was directed at the ROM I personally use. Once testing was completed on several other AOSP/Sense based ROMS I posted here, but did not remove the writing from the script. This DOES work on sense roms, as it came from a sense ROM in the first place. The very nice side-effect, is that it seems to work wonderfully on AOSP based ROMS as well.
[EVO 4G Android Development] likwid687:
So I followed your instructions to a t. Been off charger for over an hour now. Android system still showing 45% usage. CM7 nightly 103, stock cm kernel, hw 0003.