Hello all! Ive been having a battery drain problem.
According to BetterBatteryStats it is a Partial Wake lock caused by WifiOffDelayIfNotUsed (Screenshots below). It is keeping my phone from entering Deep Sleep and this process or service is apart of the Android System and I'm reluctant to do anything about it since there is a risk of bricking my phone. I cannot find anything on this problem. Any suggestions on how to fix this?
I've tried freezing some apps I thought were causing this (AAT, Google Backup, etc), but no success.
I'am using ICS 4.0.4 (Rooted) on a LG Optimus Showtime. There is no update beyond that for this phone unfortunately.
Bump
Hi,
I'm having some screen lag issues with my I9100g. I used BetterBatteryStats and the CPU Usage option in the settings and I found that this process was running constantly and also causing a lot of wakelocks : irq/281-fsa9480. Can someone shed some light as to what this process does? The process does not run while the phone is charging, which, coincidentally is when the lag stops.
Thanks.
Edit: Seems to have stopped after I cleaned my microUSB port with a toothbrush.
Hi all,
I experience problems with kernel wakelock, named "s5p-ehci". In random moment it's getting seized my phone and the phone stops sleeping. It looks like:
all other kernel wakelocks and partial wakelocks take less than 1 min of activity, whereas s5p-ehci is active during hours. So, for instance, if s5p-ehci is active at night - I am loosing about 4% of charge per hour (phone deep sleep time is 0%).
Temporary solution is to reboot the device: so s5p-ehci's activity time is between seconds and minute, later it gets crazy again and is active constantly. I did not succeed to find some relation between it and applications or system processes.
I am not an Android developer, but since there is no other kernel for my device (Meizu MX2) I'm eager to TURN OFF this damned s5p-ehci... Please, tell me, how to do it:
either via build.prop or via linux command or changing some configs.
I have tried to use other firmware, wiped my phone and tried to work without my apps, but all in vain: so I still don't know, WHY this s5p-ehci is on Earth getting so active so long all of the sudden. It has nothing to do with USB, because my phone is not plugged with cable when it happens
Nafiganado said:
Hi all,
I experience problems with kernel wakelock, named "s5p-ehci". In random moment it's getting seized my phone and the phone stops sleeping. It looks like:
all other kernel wakelocks and partial wakelocks take less than 1 min of activity, whereas s5p-ehci is active during hours. So, for instance, if s5p-ehci is active at night - I am loosing about 4% of charge per hour (phone deep sleep time is 0%).
Temporary solution is to reboot the device: so s5p-ehci's activity time is between seconds and minute, later it gets crazy again and is active constantly. I did not succeed to find some relation between it and applications or system processes.
I am not an Android developer, but since there is no other kernel for my device (Meizu MX2) I'm eager to TURN OFF this damned s5p-ehci... Please, tell me, how to do it:
either via build.prop or via linux command or changing some configs.
I have tried to use other firmware, wiped my phone and tried to work without my apps, but all in vain: so I still don't know, WHY this s5p-ehci is on Earth getting so active so long all of the sudden. It has nothing to do with USB, because my phone is not plugged with cable when it happens
Click to expand...
Click to collapse
Since it persistent across different versions of the software, I'm wondering if it is not hardware related, like the USB is shorting out or messed up (yes, I read that it wasn't plugged in during the main issue, but doesn't mean it is not the root cause). Have you tried using https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector to see if maybe it can narrow down the source of your issues?
es0tericcha0s said:
Since it persistent across different versions of the software, I'm wondering if it is not hardware related, like the USB is shorting out or messed up (yes, I read that it wasn't plugged in during the main issue, but doesn't mean it is not the root cause). Have you tried using https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector to see if maybe it can narrow down the source of your issues?
Click to expand...
Click to collapse
Hi,
yes, i've used Wakelock detector app as well as its advanced colleague - BetterBatteryStats. So that's how I've found out about "s5p-ehci" wakelock. And I can see there is no other reason of phone insomnia, besides s5p-ehci.
All other apps and processes consume CPU moderately. When s5p-ehci activity is moderate - phone sleeps well. When it gets berserk and is active during several hours - phone does not sleep at all during whole this time (deep sleep is 0%), instead works on minimal frequency (300MHz), however, it's about 40% of battery draining per night.
If it's a hardware issue - I wonder who can help me with that investigation. Services do not deal with such cases, since there is no permanent problem signs. In my case the process can behave properly during a day. Then, all of a sudden, it's getting active and some its activity lasts hours! Then it's getting back to normal again. I've looked at kernel log and system log. There is a lot of various events happening there: something is going on, then device sent to sleep, then again something is going on, then wakeup, in various cases wakeup reasons are different, I was unable to find some relevant info... I would send this log to anyone who could help me to find source of the problem.
I've rolled back to Android 4.1 firmware and installed custom kernel.
Here situation is better, but what I have discovered:
phone seems not to detect when it's being plugged off from charger - no matter, USB cable from computer or wall socket wire. s5p-ehci does not go away and sucks off my battery. What only helps is manually resetting EHCI power: setting 0 in ehci_power file. As a result, something is reset, ehci power is on again, but this sucker goes away and after that everything is fine until next charge. But I need to find a root of the problem!
Going on investigation - too view info in Internet...
Ok, this has gone past creepy
I got myself I9300, did all the necessary:
Root, ODIN > Philz, wipe, install rom
I installed PA for i9300, which was nice but battery drain was immediate problem so I just thought it was a bad/unfinished ROM. I then installed Resurrection remix which seemed like really neat and complete ROM only to experience the SAME problem - standby battery drain.
I then started searching for the problem cause. BetterBatteryStats says:
partial wakelocks -
SystemUpdateService on par with Awake. it is ALWAYS on
googled it, here is the problem:
People reporting it on 4.3, making constant wakelock, disallowing the phone to go in deep sleep once it is locked. And it was actually fixed in 4.4 CM and CM based roms (resurrection is one of them) but mine is running still.
I then started searching for the solutions, even though my OS version shouldnt do that. One of them says -
You should disable the service via apps "service diasble" or "Autorun Manager" from Play store in order to stop it. So I download both and the service is actually unticked. Shouldnt run at all. but it is still there destroying my battery. Next thing I found on CM forums says:
"wakelock is disabled by devs so that users wont experience constant OTA updates, and while it is disabled, it still runs (nice logic over here) and enabling it stops the wakelocks"
I then tick it to "enable" via those mentioned apps, but the wakelocks are STILL there, phone wont go to Deep Sleep
Extremely annoyed, I went to Settings>Apps>All and disabled the whole "Google services framework" which containts "SystemUpdateService" and there you go -
it still runs, wakelock on par with awake time ....
Is this God-mode service, is this some magic ? What the F is going on, and why do I even experience this when the problem was solved in 4.4 .. ? Please help me.
Hello forum,
background info:
I have a rare Pansonic Android 5.0.2 phone (DMC-CM1) with an excellent camera, what is the reason why I want to keep this device.
There are NO custom roms available and no info about key combinations on how to get into stock recovery mode. I can go there with adb of course.
I found a key combination to get into fastboot, but Wiping cache/data to reset the device apparently did nothing, even if wating for hours. It seems as well as if Panasonic tampered with the stock bootloader :/ This is why I had to send it to service (adb was not enabled before).
They reflashed the device with 4.4.4 and I installed the updates to 5.0.2 OTA. Everything seemed fine until...
present problem:
...now I have a strange battery drain. Bevor I sent it it, I had about 2-3 days usage time with average usage, a little messageing, a few fotos. I do not use the phone much.
Now I get a maximum of around 16-20 hours out of it while it is just resting on the table. It also gets warm.
what have I done so far:
- I rooted the device and installed better battery stats from the forum here. It shows around 8-10% usage per hour. Before the problem showed, I had 1-2% usage.
- I uninstalled EVERY own installed app and even booted into safe mode -> same problem
- I disabled all google app packages -> same problem, but improved it a little
When I check the battery via android settings, it is telling me that "android-system" is using >20% of the battery. In active apps I can see this app is running the fast dormancy service. When I kill this service and force the complete app to stop, it gets _a little_ better, around 5-6% usage.
I recently killed forced stop on all services that where not qualcom or seemed essential to me and disables wifi and bluetooth and over night usage dropped to <1%/h, which seemed the problem could lie somewhere with services.
However using adb shell and pulling "top" info, I dont see a process using much CPU.
What else have I noticed, which might be unrelated:
-After charging I see a 100% wakelock from qpnp-charger, that disappears only after rebooting. Might indicate that something with qualcom is "wrong".
-I set wifi to be _never_ be running in sleep mode. Better battery stats is telling me, that wifi is 100% of the time running, even if I can see the symbol for wifi is not showing and comes up a few seconds after I wake the phone
You can see, I might need help on how to identify the problem here.
Any hints, tips, advice?
Please excuse my "messy" english, it is not my native language.
regards
Stefan