Hi.
I've got a problem with a sudden drop in the battery work time of my phone. Deep sleep not working or working for a while. I checked all applications and did not find any guilty app. Somehow, after a few days, I came to that, the deep sleep stops working after phone contact with a USB cable. It makes no difference whether it's plugged to the charger or the computer.
I checked in BetterBatteryStats, what could be wrong - it's kernel wakelock: musb_wake_lock, which is probably not allowing the handset to go sleep, so I need everytime to reboot my phone. I did factory reset, reflashed phone few times (stock ROM's, CM9) - it did not help.
Do you have any suggestions?
I have exactly the same problem with the exact same kernel process name taking up cpu with the exact same scenario too!
So, bump?
Related
I keep it on sleep mode and the next day may battery is fully spended can anyway tell me why or how to prevent this?
Thats a known problem (just in the newest firmware)
I would install Urukdroid
No it is not.
in 100% of the cases an App is holding the Archos from going into deep sleep.
Just check that wifi can sleep, no Sync is on, mail, facebook or other inet apps are not holding connections.
I usually just keep it in Airplane mode, and only turn on the WiFi when I need it. This has helped with the power use problem.
I tried setting it to deep sleep, but I found that it would invariably crash when asleep (or when waking up--I don't know which).
I just turn my wifi off and put mine into Deep Sleep. I can leave it for days and the battery only drains a few percent (usually ~1-3% per day).
Some app must be waking your device, and causing the drain.
Installing UrukDroid is not the answer to all problems. I know some people here seem to think so, but there are bugs there too.
I'm not trying to knock UrukDroid at all, or the work that Sauron has done, but just switching your OS is not the best answer.
Something strange happened to my phone. One night I installed an app that can turn the phone into sleep mode instead of pressing the button at the uppermost right of it. I still have around 70+% battery by that time. The next morning, I was surprised that my battery is already out. I charge it but was stuck at the cyanogen logo. I removed the battery and tried to open it, this time the animation boot happened twice before finishing. I removed the app but noticed that my battery begun draining much faster than before. Just letting it on idle state will reduce it to 40% in 9 hours. The bootup problem is also present every time I boot the phone - it will get stuck at first at the logo,remove the battery, turn it on again where the animation will happen twice before the phone become usable.
Checking the phone usage, mobile standby and phone idle have the largest usage. I read some threads mentioning something about wakelock or something that prevent the phone from going to sleep. Checking the Spare parts battery history, only two things are present - Running (100%) and Screeon on (5.1%).
Any help or tips to know the real problem? Thanks
sinscythex said:
Something strange happened to my phone. One night I installed an app that can turn the phone into sleep mode instead of pressing the button at the uppermost right of it. I still have around 70+% battery by that time. The next morning, I was surprised that my battery is already out. I charge it but was stuck at the cyanogen logo. I removed the battery and tried to open it, this time the animation boot happened twice before finishing. I removed the app but noticed that my battery begun draining much faster than before. Just letting it on idle state will reduce it to 40% in 9 hours. The bootup problem is also present every time I boot the phone - it will get stuck at first at the logo,remove the battery, turn it on again where the animation will happen twice before the phone become usable.
Checking the phone usage, mobile standby and phone idle have the largest usage. I read some threads mentioning something about wakelock or something that prevent the phone from going to sleep. Checking the Spare parts battery history, only two things are present - Running (100%) and Screeon on (5.1%).
Any help or tips to know the real problem? Thanks
Click to expand...
Click to collapse
this will happen when install every crappy tweak **** - i'm not understand why users have to install extra apps for buttons
to help you something:
wipe your system, not the data - only if it doesnt work after wiping the caches.
than try to boot ... if its doesnt nrmal booting, reinstall the rom and do a full wipe. sometimes apps installing libraries in system.
^
I was thinking of reducing the usage of the hard button so I used it. Will resintallation of the ROM afefct my partition? I have a nandbackup before this problem happened, but I still do not have the partition by that time.
And how do you do it by the way? Just flash again the ROM? Thanks
Edit: Wiping the cache seemed to help. It doesn't stuck at the logo, but the animation still happens twice instead of once. Gonna observe the battery usage. Thanks.
100% running, that means your phone is not in sleep, but only with LCD off. Grab betterbatterystats([email protected]) and check your wakelocks.
Sent from my LG-P500 using XDA App
Based on the betterbatterystats, the gpslocationprovider is the culprit. But my gps apps are off and are not running any services. Any idea how can I stop it?
sinscythex said:
Based on the betterbatterystats, the gpslocationprovider is the culprit. But my gps apps are off and are not running any services. Any idea how can I stop it?
Click to expand...
Click to collapse
Off GPS ,on only when needed
Sent from my LG-P500 using XDA App
I copid a gpa.conf somehere in this forum. I replaced it with the originial and I'm currently observing whether it will return to normal. My gps apps are off, and both wireless and gps sattelites are disabled on my location & security tabs.
I'm planning on doing a restore to at least remove the boot up problem. But my last nandbackup was still before I partitioned my sd card and flashed dark tremor, and configre a2sdgui. If I do the nandrestore, do I have to disable or remove dark tremor and a2sdgui, or remove the partition of my card? Thanks
sinscythex said:
I copid a gpa.conf somehere in this forum. I replaced it with the originial and I'm currently observing whether it will return to normal. My gps apps are off, and both wireless and gps sattelites are disabled on my location & security tabs.
I'm planning on doing a restore to at least remove the boot up problem. But my last nandbackup was still before I partitioned my sd card and flashed dark tremor, and configre a2sdgui. If I do the nandrestore, do I have to disable or remove dark tremor and a2sdgui, or remove the partition of my card? Thanks
Click to expand...
Click to collapse
I has the same gps wakelock even disabling GPS- reboot and the thing is gone
I changed it, but my phone still doesn't sleep. Although this time, the gpslocationprovider is no longer shown with the betterbatterystats. It just states that my phone is awake for around 47 minutes but my screen is just on for around 4 minutes. I've already rebooted several times and wipe the cache but its still like this. Still trying to find other ways.
Hi everyone,
I've done very much try and erroring to find out which app is draining my battery and if it's really neccessary.
As you can see on the attachment, it looks really nice already. The only thing which drives me crazy are those long and often "Aktiv" (Awake) parts. I couldn't find any information on the SDK pages.
My Phone seems to be very often Awake while in standby. I can't understand why it has to wake up that often. Am I right, that this "Awake" means, that the cpu is running (not in sleep mode)?
Is there any way to log which software is waking the device up?
Greetings
Chris
Yep, "awake" means that cpu is running. Try Badass Battery Monitor, it has a list called AppSucker, that lists the apps by battery consumption
Thanks. That is exacly what I was looking for.
Now I'm still sure, that there is somethink wrong with the battery consumtion. As you can see on the attachment, "Android-System" takes 2 hours(!) for some stupid things.
These are the datas for one night (it was a short one ) The phone wasn't used at all. Is that normal? I mean, thats nearly 30% of the time. Okay, the total capacity loss seems okey, but the phone hast absolutly nothing to do. Except for some interrupts of from the baseband and some cronjobs maybe. But that doesn't need 2 hours.
Any suggestions what courses these long awake times? Or another way to debug this?
Thanks
Chris
Android-system, huh? Seems like you have a wrong config, or a service is keeping awake the CPU...
Sorry, I dunno other way to debug it, but you already tried to calibrate your battery? (let that your battery runs out, charge it fully and, without unplug the charger, go to Recovery >Advanced >wipe battery stats. Unplug and reboot).
Yep, that was the first ding I did.
I'm running IceColdSandwich - 7.4 - AOKP STRIPPER EDITION. Maybe this is some kind of bug.
Maybe someone have another idea how I can debug this. Nevertheless thanks for helping.
You should check to see if Sync is turned on. This will cause the phone to wake up to contact any accounts you have set up to sync... I would suggest setting sync to off unless wifi is available.
On my rom (Gingerbread base) the wifi is turned of when the screen is off, which will make sure that google will never try to sync while the phone is idle.. The downside you will have to wake the phone in order to receive emails and stuff via wifi, and if not on wifi you will have to check your email manually.
I think I found it. Badass Battery Monitor showed that "Google Backup Transport" is part of Android-System, so I removed it. I didn't use it anyway.
My phone is not crashing, I still runs smoothly. The keep-awake time shrinked to 30m during 7h (including short uses). That seems totally legit for me.
Thanks for helping
Chris
**my mistake, can someone move this to the AT&T forum?**
Hi there, I have this problem; my AT&T GS4 does not use the deep sleep state. I have made some research, and from what I understood, this problem has to be a result of any program that keeps triggering the phone to get awake.
So, I have the phone unlocked, rooted and ALL the sensors off, expect from gsm signal. With titanium back I have uninstalled the programs that I´ll never gonna use (mostly AT&T bloadware) and frozen the ones that I don’t want to use right know, but maybe by deleting them I would get into a problem (like S-Voice) or just because some day I would like to give them a try. Finally, there are the programs that I would like to keep, but I don’t want to let them make any cpu use while I am not using them. I used an application called Greenyfi, a good example of why this program is the best for the last propose, is the use of programs like google maps, in where I do want to use it, but, just when I open the app. Also, I used the app “Autostarts” to prevent applications to start after some events (like startup, state change, etc..)
With all that been said, I am steel not getting deep sleep, in any situation. I´am not saying that my battery life is bad, I think I can get easily 4-5 screen time use. But, by not getting into deep sleep, the phone is allways using the cpu at 384mhz, so the battery goes down in a range of 1.5 to 2 % per hour (10 hours of no use and 20% less battery).
SO, for you to see the problem better. I did a little experiment. Restart the phone, put it into flight mode and let it “sleep” for the night, the results are attached.
PD: Whatsapp isn’t the problem; I can froze it and still 0% deep sleep.
did you ever solve this.. my t mobile s4 is not going into deep sleep staying at 384mhz
Had this problem a while ago. Ran Greenify and froze things with TiBu but the phone didn't go into deep sleep. I ended up flashing back to stock then re rooted. Problem solved.
same here. reset didn't work.. flashing back to stock didn't work, flashing stock and then a reset worked.. and reinstalled everything and still going into deep sleep now.. now sure what it was, but something in system was ffd up.
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...