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.
I've looked through the threads and on the internet trying to resolve the following issue with no luck:
Sleep of Death occurs (SOD) (i.e. must restart tablet by holding in power button after tablet goes into sleep mode). This occurs while either plugged in or on battery. Sleep of Death occurs faster while on battery.
I have tried Captivate Keep Alive and REGPON wifi KeepAlive. REGPON keeps SOD from occuring longer than Captivate, but SOD still ocurs. WiFI appears to be on when this occurs.
I am using CM7 (2.3.3).
Any ideas on what I can try? This is frustrating.
Thanks in advance,
Paul
http://forum.xda-developers.com/showthread.php?t=1172404
pmuch12345 said:
I've looked through the threads and on the internet trying to resolve the following issue with no luck:
Sleep of Death occurs (SOD) (i.e. must restart tablet by holding in power button after tablet goes into sleep mode). This occurs while either plugged in or on battery. Sleep of Death occurs faster while on battery.
I have tried Captivate Keep Alive and REGPON wifi KeepAlive. REGPON keeps SOD from occuring longer than Captivate, but SOD still ocurs. WiFI appears to be on when this occurs.
I am using CM7 (2.3.3).
Any ideas on what I can try? This is frustrating.
Thanks in advance,
Paul
Click to expand...
Click to collapse
If you are overclocking, set the minimum to 450 MHz. What works best for me is to enable volume rocker to wake in the settings. That way I use the volume button to wake the tab. Never had a sleep of death after that. I am using Icewyngs CM7 for BL 1.2.
I have a DNA that I have in my car and never take out. I use it for all sorts of things to replace my radio ect..
I have it connected to the charger but I want to be able to download an app that will force it to go into deep sleep when not charging. (ie: when the car isn't on.)
I was thinking of different ways I could help prevent the battery from draining when my car isn't started since I won't be using it.
The key is to be as lazy as possible without having to touch the phone to turn it off/on.
Does anyone know of an app or apps that would help turn the phone on/off when charging or just key features like the screen, LTE, cpu freq?
Thanks for any help.
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?
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...