yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] JBabey:
Odd, I am on cyanogen nightly 100, had the issue, and it was resolved on me and my wifes phone, both on that nightly. The only difference for the two of us, is that we are running savaged-zen kernel 2.2.1 sbc. Possibly rewipe the cache/dalvik and run the gps driver install again, fix permissions.

does your GPS lock immediately?
[EVO 4G Android Development] dgrobe2112:
Kingdom Revolution 1.3, off the charger for roughly 1.5hrs.. battery 90% lot of texting, and a couple of calls.. no AndroidOS in my list.. use of battery

Display 70%

Dialer 9%

Wifi 6%

Cell standby 4%

Phone Idle 3%

Handcent SMS 3%

Bluetooth 1%
[EVO 4G Android Development] mswlogo:
I had this issue on one of the early versions of MikG's ROM's.

I never downgraded to PRI 1.77.

Since the OTA update with new Radios and Kernels I have not seen the problem with the half a dozen or so ROM's I've tried.

MikG's 1.04 ROM (Sense 2.0 and some 3.0 Goodies) with latest OTA Kernel and latest OTA Radios works great.

I may just be lucky because I see a few posts with wake issues in the MikG thread but I don't know which radios and kernels they are using.

I appreciate the investigation but if you still have to run PRI 1.77 it doesn't sound like you got to the bottom of it.
[EVO 4G Android Development] Tipharet:
So after flashing this cause I assumed it would be a good set of radios. I NOW have this issue when system never showed up before hand.
[EVO 4G Android Development] dgrobe2112:
he said it would.. and would go away...
[EVO 4G Android Development] k2buckley:
I would just go back to the setup you were using when you didn't have any issues.....

out of curiosity, if you never had the problem that this fix addresses, then why did you use the fix? If it ain't broke, don't fix it....
[EVO 4G Android Development] JBabey:
I specifically put in the requirements you have to be having the issue.... as ANY change to your radio's can create this anomaly. I may not be to the bottom of the issue, but this has worked on every phone I have in the store that DOES have the issue.

Good luck, maybe re-run the steps to alleviate your new issue..

again, please dont do this if you dont have issues, you are tempting fate.

ALSO: try reverting to your old .so file, it may have been playing nice w/ your setup /shrug

sorry.
[EVO 4G Android Development] Tipharet:
I understand that. I was reflashing radios as I been having issues with 3G speeds. I have been trying radios and PRI all this week and this is the first time system has popped up. There was something specifically in either the hboot flashing process or this combination of radios that cause me issues.

old .so file?
[EVO 4G Android Development] dinoman22:
Wow, the Gps fix and locking is amazing. The difference is night and day. I'm glad you posted great work !!!
[EVO 4G Android Development] dirkyd3rk:
Interesting find.

Sent from my PC36100
[EVO 4G Android Development] locoboi187:
im on salvage mod with the latest drivers and PRI and never got this wake lock issue. Android system never shows up on my gingerbread...well atleast i dont see it. I think it goes away after a few mins
[EVO 4G Android Development] lowspeed:
What's 'AlerterService' ? I have it listed as partial wake.
[EVO 4G Android Development] cheapskate88:
Clearly having some ussler error issues but I can't get my sensors back... I swapped in the so.bak file and renamed it to so. I also rebooted and wiped cache... any suggestions on what I'm doing wrong? I've also flashed the no proximity phone apk. Thanks!

Maybe someone can post his working sensor.so file?
[EVO 4G Android Development] wryun:
Did you try re-flashing your ROM?

Not a full wipe and flash, but just wiping cache & dalvik, then flashing your ROM on top of the current one?

Worked for me. :-)
[EVO 4G Android Development] cheapskate88:
That's a great idea! Thanks!
[EVO 4G Android Development] wryun:
Of course, don't forget to flash the gapps for your ROM as well.
[EVO 4G Android Development] ropodope:
why isn't it already in your rom? Oh yeah, must be cm7. Sorry.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. No bricks here.
[EVO 4G Android Development] wryun:
Why isn't *what* already in my rom? I use Deck 1.2 btw.
[EVO 4G Android Development] ropodope:
gapps. I never need to flash gapps on aosp so I forget sometimes that others do.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. No bricks here.
[EVO 4G Android Development] wryun:
Gotcha! :D
[EVO 4G Android Development] JBabey:
2 days and 4 handsets, the

NoProximityPhone.zip

is working perfectly for my testers. I had them also replace their galleries with Quickpic so the only thing triggering wake-lock at the moment is the camera.
[EVO 4G Android Development] MizzouBrent:
Since when does camera cause wakelock? I don't remember hearing about that before
[EVO 4G Android Development] JBabey:
phone camera and gallery all trigger the proximity sensor. Good people are hard at work trying to locate the root cause of the issue. Well keep everyone posted as more information becomes available.
[EVO 4G Android Development] JungWoo:
I flashed the combo and the AOSP GPS driver, and my battery drain was actually worse. I also couldn't get any data in a lot of areas where I once could. I don't know what I did wrong. I ended up going back to the most recent radios, and I am fine with that now.
[EVO 4G Android Development] JBabey:
If you read in the OP, the combo/gps instructions are out-dated and should not be followed, I am glad you got your radios restored and everything is back to normal. There is a link, and I believe it is to page 31.... read from there.. but what you are looking for is

NoProximityPhone.zip

Find that attachment a few pages back and flash that in recovery. Your issue will go away. For GPS I do still recommend the vision driver.

Good luck.

EDIT: I will update the OP to be a little more clear tonight or tomorrow. so I apologize for any confusion.
[EVO 4G Android Development] sbradymobile:
The proximity wake lock shows up under android system usage because the phone app uses the power manager service which runs under the system pid. It is not necessarily a bad thing or a problem, it is just the nature of the current proximity wake lock implementation and battery reporting. I don't know what the difference in power consumption is, and am not personally making any claims that it will be better if you choose to use it. I do think it is good to have the option if that fits your needs.

When I added some logging to the sensor manager it appears everything is working fine, the sensors stop polling at screen off (and most apps will stop polling when closed). I will try to find some more info on the reason that sensor usage time continues to increase in all apps that use sensors after they are opened, but it at least it appears the sensors are being disabled and not reporting any data.
[EVO 4G Android Development] pie944:
When restoring the original file, do you need to reflash the ROM as well? I restored and rebooted but it did not return to its normal state.
[EVO 4G Android Development] bytes2bits:
I encountered the same and ended up just restoring the rom. I don't bother trying to restore the original files any more. It's just as easy to restore the rom and seems to be fail proof.
[EVO 4G Android Development] sbradymobile:
Here is a libsensorservice that should reflect the actual sensor usage in Spare Parts. The current implementation appears to only disable the battery logging if the sensor is off. Because the system uses sensors, the battery logging for apps isn't able to reach the disable state. I just added an additional condition to check for that. This is only for testing purposes; it does not make any changes to the sensors, only the battery logging for the sensors so you can see if there are any problem apps (Google Goggles for instance does not close the accelerometer, so it will continue to increment the sensor usage until it dies on its own or is killed).

libsensorservice.zip
[EVO 4G Android Development] aaanadie:
Hello,

I have

EVO 4G hardware 0003

Seido battery 3500

CM7 nightly #119

SavagedZen-2.2.1-CFS-HAVS

SetCPU:

*****************************

Main: 1075200-245000 Performance Set on Boot

Profiles:

- Screen Off 245-245 PowerSave Priority 100

- Temp > 42C 245-245 PowerSave Priority 95

- Battery < 25% 460-245 PowerSave Priority 90

- Battery < 70% 883-245 Smartass Priority 65

- Battery < 85% 960-245 Interactive Priority 55

- Charging 1190-245 Performance Priority 45

*****************************

Battery stats:

I got 13% Android System just checking my voice-mail (less than 1 min, no message), but my battery was 100% before and after that I had my phone resting on desk for more than 25 min, then I checked and had 98%. Normally I have a heavy phone use because calls, notes, database, remote access my phone to pc, internet, etc, and I return home with more than 40% so I think should not apply any fix, but I had Tiamat_Evo-v4.0.5-sbc and my battery was draining fast.
[EVO 4G Android Development] ropodope:
I dont know why, but every since I have flashed this, I get constant fc closes whenever I try to go back a page at any point in using the standalone xda app. it does not affect the tapatalk pro app. Can I have a flash to reverse this? That way I will know for sure.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. No bricks here.
[EVO 4G Android Development] sbradymobile:
I don't have one, but you can pull the file from your original rom's zip and replace the one in that zip. This doesn't cause any problem with the XDA app, it is seriously buggy to begin with, and it doesn't actually do anything that could break any apps in any way. It only changes the battery reporting for sensors.
[EVO 4G Android Development] ropodope:
thats what I thought. Just didn't have a clue as to what the problem is. Just started happening today even though I've been using it for over two months. Go figure.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. No bricks here.
[EVO 4G Android Development] jae04cc:
Try 3.3.7..its been way better on my batt

Sent from my Evo powered by CM7 Nightlys
[EVO 4G Android Development] dthomas03:
Do you undervolt as well using Viper boy's mod? If so by how much. My Evo does like Timat 3.3.7 better than 4.0.5 (dont ask me why) but I would like to get a little better battery life.

Thanks ahead of time.

~~~SuperSonic~~~
[EVO 4G Android Development] ropodope:
Do any of the tiamat kernels have wireless n enabled? I have yet to find an aosp kernel for gb that does is why I am asking.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. No bricks here.
[EVO 4G Android Development] wmblalock:
Is anyone still working on finding a true fix to this issue that would allow the proximity sensor to work as it should?
[EVO 4G Android Development] ropodope:
yes

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. No bricks here.
[EVO 4G Android Development] jae04cc:
I do undervolt by 100, but I don't overclock..the people I've talked to that overclock can't undervolt by that much..although I do everything-100 and I know you can undervolt only certain things I just haven't had time to play with it enough

I don't think tiamat has n enabled ropodope..

Sent from my Evo powered by CM7 Nightlys
[EVO 4G Android Development] ropodope:
I didn't think so, thanks for your reply.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. No bricks here.
[EVO 4G Android Development] cnstarz:
thanks for qualcomm gps driver. i'm on cm7 rc1 and it rarely locked on. after installing the qualcomm gps driver, it now instantly locks on. even after several reboots just to see if it was a fluke. locks on instantly every time. much gracias!!!
[EVO 4G Android Development] shakuyi:
what radios do you have installed? latest?
[EVO 4G Android Development] cnstarz:
i haven't manually updated my radios in a long time (at least 9 months). all i did was flash the qualcomm gps driver.
[EVO 4G Android Development] ro_bro:
I flashed back to my prior GPS (old) driver, and my SENSOR usage for Android System use has decreased. I think that was what was causing it, for me at least. I'm on hardware 003.

I just tested this on my MIUI 1.7.1 and it seems to work fine so far.
[EVO 4G Android Development] shakuyi:
still nothing grrr
[EVO 4G Android Development] likwid687:
Sorry, I know this is somewhat unrelated. I have asked about this elsewhere and haven't gotten any answer (no attempted answers either). I have a wakelock issue caused by something called UID 10080. This shows up in Spare Parts on CM. I haven't been able to link to it anything yet. I've tried uninstalling several different apps but nothing has worked thus far. There doesn't seem to be any kind of pattern either. Most days it will keep wakelock on for several hours (2-4), but some days it goes as high as 10. Anyone else seen this?
[EVO 4G Android Development] sbradymobile:
In terminal emulator you can try the command dumpsys batteryinfo. This should give you some idea what the app is.

For onscreen display:

su

dumpsys batteryinfo

To save to a file to view somewhere else:

su

dumpsys batteryinfo > /sdcard/batteryinfo.txt
[EVO 4G Android Development] likwid687:
Bless you, dear sir. I was finally able to find what it was. Handcent is the culprit. Does no one else use this? I'm surprised this isn't a bigger problem. I thought more people used Hancent. Here are the logs if anyone else is interested:

#10080:
Wake lock *vibrator*: 5s 485ms partial (23 times) realtime
Wake lock Managewakelock: partial: 2h 44m 59s 882ms partial (8 times) realtime
Wake lock StartingAlertService: 13s 463ms partial (25 times) realtime
Wake lock StartingPopupUtilsService: 4s 58ms partial (20 times) realtime
Proc *wakelock*:
CPU: 4m 8s 670ms usr + 1m 39s 770ms krn
Proc com.handcent.nextsms:
CPU: 27s 520ms usr + 11s 160ms krn
2 proc starts
Apk com.handcent.nextsms:
24 wakeup alarms
Service com.handcent.sms.transaction.bl:
Created for: 49s 994ms uptime
Starts: 25, launches: 25
Service com.handcent.sms.transaction.t:
Created for: 10s 718ms uptime
Starts: 20, launches: 20
[EVO 4G Android Development] Greatbape:
Download an app called Activity Express. It shows the UID of all apps running. Start it up and long press on each app in the list to the UID of that app. If you have handcent with popups turned on.. it's most likely that. Try Gosms if it is handcent.
[EVO 4G Android Development] WFG:
Flashed on CM 7.1.0 RC1, Lost service & had to reflash ROM... flashing the original phone.apk didn't fix, didn't nandroid because I didn't think swapping phone.apk would be a big deal... Anyone else have an issue?
[EVO 4G Android Development] ropodope:
you are the only one.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. No bricks here.
[EVO 4G Android Development] fitz420:
I flashed the noproximityphone in the new salvagedmod 1.3 odexed and the phone fc's.

Is this because its the odexed version and if so could you kindly make a version for that rom.

I was using it with no probs in decks 1.2

Thank you
[EVO 4G Android Development] MicrosoftBug:
My wakelock got fixed by doing nothing that has to do with this thread. For me, the issue seemed to be the PRL. I updated it yesterday via the PRL update in settings. It went from 01115 back to the older 60679 and I haven't had wakelock since.
[EVO 4G Android Development] WFG:
Okay so I have a file named eri.xml in my /data directory which changed the carrier banner from Sprint, on a hunch I removed this file & reflashed to NoProximityPhone.zip & didn't have my previous problem. not sure if that was just a coinsidents...
[EVO 4G Android Development] Mazda:
Just wanted to share my awesome battery life.......I applied the phone.apk / sensors.supersonic.so fix along with the latest PRI/NV/WIMAX/RADIO and used vipermod.....ALL TOGETHER, is AWESOME!! I've never made it through an entire work day without having my phone die on me UNTIL today!!!....Although I didn't go Angry Birds crazy today...lol, I mainly used it for texting, calling my wife a couple of times today and looking up things I needed for my job......Oh and I chit chated a couple of times on Google+
[EVO 4G Android Development] pie944:
Does the high android system use with phone calls actually lead to worse battery life? Does this fix improve it?

pie944
[EVO 4G Android Development] tstretch:
I did the phone.apk replacement but that's it. Helped some but spare parts still shows 15 hrs of sensor usage for the Maps program and 6 for android system, also under Sensor usage.

What do I need to do?
[EVO 4G Android Development] tstretch:
Pie944: Yes & yes.
[EVO 4G Android Development] imheroldman:
Pie, basically your sensors are running for no reason. This would be like leaving on wifi or 4g when you aren't using them, it is unnecessary use id the battery.

tstretch, you may want to try a gps driver... Is your gps working properly? Does the icon stay up after you close out?

Sent by Supersonic!

Sent by Supersonic!
[EVO 4G Android Development] BuddaBelly:
So can we swap out an older version of the proximity drivers on an older release of CM7? I've swapped back over to CM7 N and the android system is running like crazy and does seem to be using battery. I have tried the fix here and it works great but it would be better to have the sensors working.
[EVO 4G Android Development] imheroldman:
Does anyone have a mirror for the original phone app Daklown posted? Not the no proximity but the one that "works"

Sent by Supersonic!
[EVO 4G Android Development] AliLaPointe:
How do I fix the sensor issue and what are the draw backs?
[EVO 4G Android Development] vrajpal:
Just wanted to check and see if progress had been made with a solution?
[EVO 4G Android Development] asafegous:
+1
[EVO 4G Android Development] vrajpal:
Also I have applied the no proximity zip and when I go to check spare parts it shows a very high usage of sensors by android system is this normal?
[EVO 4G Android Development] linsalata28:
Sorry I've been reading through this thread but its huge I'm not having wake lock issues but I am having high display issues I'm currently on kings alliance 7.6 but this has been on all these sense 2.1 3.0 and 3.0 ROMs has anyone found a fix for this?
[EVO 4G Android Development] BuddaBelly:
Ok first off I'm on a sense Rom namely MikG 2.1+3.0. For those of you with a dialer running rouge give this a try. Been testing for a couple of days and seems to be working. Below is a direct copy of what I wrote over on MikG's forums. I want to add that this doesn't actually release the pokelock but seems to keep the dialer from running crazy in the stats.

Ok I've been playing with some settings and so far I have found a way to keep the dialer from running rouge. After reading on the shift and desire forums and looking at their workaround I figured there had to be something keeping the sensors awake. For me I went into the sound settings and disabled "quiet ring on pick up", "pocket mode", and "flip for speaker". This has left me with a dialer that is left at 6% usage after 14 hours up time. This is a major improvement as before my dialer would be in the 20-30% range. Something with those settings are keeping the proximity sensors awake but for now this has fixed the issue for me.
[EVO 4G Android Development] jelive:
Going to try the noproximity zip...will report back after testing.
[EVO 4G Android Development] scottspa74:
I've been trying to figure out what's causing my Cell Standby to always be pegged. I hoped it might pop up in this thread, but skimming thru, I haven't seen it. Im wondering if it may be radio or pri related, also. (Haven't had a chance to skim calks thread).

Just wondering if anyone else has run into this. I think I only have it on aosp roms (in the last 2mo only ran sense a few days) . When on sense, (synergy) was testing prl update and went from 01115 to 60679.

on 2.15.009 radio

pri 1.400.03 (from about august '10, only pri that was never flashable)

Like to hear if anyone else experience this. Thanks.

(and yes, that is 3hrs 11min from full sbc charge ;( )

edit: after seeing this in print, it occurred to me I should try newer pri. but reluctant cuz this pri tripled my data from one before it, and there's no way to flash it back. prolly do it anyway)
[EVO 4G Android Development] KyleK29:
I've done the phone.apk and had the supersonic.sensors.so file install .. worked great and had incredible battery life,except my accelerometer/orientation sensors stopped working. So no rotation, had to revert to the original sensors.so file. Running CM7 nightly 122.

Anyone know of a fix that doesn't disable all sensors? I should note, I was using the sensor file from a week or so ago, so if there's a more recent one ....
[EVO 4G Android Development] jossdonn:
my cell standby is always like that too but i've just chalked it up to poor reception in my area.
[EVO 4G Android Development] scottspa74:
Hahahaha. So check it out. I finally, reluctantly, upgrade to pri 1.77....and now my Android System (which is usually at about 4%, is now the top consumer (48%)

Can't win for losing. (And there's no way to get back the pri I had before, damn)
[EVO 4G Android Development] rob_z11:
It was my understanding that sensor file you are updating only cares bout the phone moment while you are talking on the phone, and other apps don't use the same file.

I can open the Opera Mobile, and tell my phone to allow switch, my Opera browser switch from potrait to landscape.
[EVO 4G Android Development] tstretch:
Rob_Z: I believe that's only true for the phone.apk file.. The sensors.so files disable all sensors I think. I have did you only replace the phone.apk file???
[EVO 4G Android Development] HipKat:
What PRI did you come from?? Calk has a thread with all the radios in it.
[EVO 4G Android Development] rob_z11:
Yes, I have replaced the phone.apk file, and also replaced the sensors.so file. YOu may be right that it disables all sensors.
[EVO 4G Android Development] imheroldman:
@Kyle the best option I've found is the no proximity phone apk. currently I am running the phone app from the original post and it is also working well. I do have android system show up every once in a while but goes away with a little use of the phone.

Also, I am running all current radios from caulkin's thread, tiamat 4.0.6 and my battery life is the best it has ever been. No compromising sensors and every thing runs perfectly.

Sent by Supersonic!
[EVO 4G Android Development] crammed174:
deck's fix

So i spent the last 9 hours flashing all sorts of combos to fix wake lock or android os or battery drain.

I tried EVERY option on this thread in the past week but tonight i went hard. I'm running deck 1.2.1 w/ tiamat 4.0.5 sbc and undervolted 75 and a few custom volts.

my definitive fix was the LATEST radio/wimax/pri/nv update and then flashing the phone apk in this post i'm quoting not the new one w/o proximity because i kinda like to have all features working. i did have a crap load of fc's and boot looping but all i did was a battery pull hold down vol to get into bootloader and cleared cache & dalvik and fix uid in amon ra. now i'm working great with excellent 3g speeds. 2-3% android os and running dumpsys power in TE always hae 0 as lock.....

worked on both my evos (other one is running deck 1.2m and also fixed)

hope this helps!

OH and the latest gps supersonic flash fix 3 ... better than ginger or cm, others would run maps or any gps app at like 40+% ...

now i'm having the great battery life again, instead of dropping percents like crazy and no wake in usage.

to be clear

recovery

wipe cache and dalvik

flash radio combo

reboot

let phone load and reboot to recovery

wipe cache and dalvik

flash phone.zip

fix uid

reboot and load

phone prob will have errors or fc's if so battery pull into bootloader -> recovery, if no errors still go to recovery just no need for batt pull

flash gps file

fix uid mismatch and reboot!

sounds like redundant wipes and flashes but hey... it worked!