Hallo Iv got an Asus Padfone and have an annoying bug when my screen goos of and my phone enters stand-by all data connections are served wifi and mobile.
I can still revive calls but my whatsapp and other programs don't receive updates unless i unlock the phone.
This is very annoying since I have missed a lot of conservation some are 10 hours old.
I have done some research and I'm not sure whats cosing it but I think its something with the deep sleep mode of the processor thud doesn't wake properly.
when I check my cpu status I can see my processor is 96% of the time off line 2% active at 384MHz and 2% at other speeds.
Sow I think my phone cant wake when it needs to.
I have done a factory reset several times and tried diffident firmwares.
I also have tried software like wake lock but the sleep mode just overrides it.
Do you gays have any idea how to solve it like modifying the build.prop ore kernel?
Thanks
*note: I'm not using any power saving apps or settings
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.
I've been using the app BetterBatteryStats as recommended by XDA to determine why my RAZR is awake much of the time, even when the screen is off and data is turned off. It turns out the problem is the internal process IMS_Data_Retry. This process apparently keeps attempting to establish a data connection over cellular data, at least 4G LTE. It aquires a wake lock while doing its work. This one process can keep the phone awake 95% of the time. The only way I have found to semi-stop it is to turn on 4G LTE. Even then, while it stops consuming CPU time (supposedly), the count of retry attempts keeps going up. (Putting the phone in Airplane mode also stops it, but then calls are stopped as well.)
There is a setting in /system/build.prop that I thought controlled this process:
ro.cdma.data_retry_config=default_randomization=2000,max_retries=infinite, 0, 0, 120000, 180000, 540000, 960000
I looked at some code references I found ( http://hi-android.info/src/com/android/internal/telephony/cdma/CdmaDataConnectionTracker.java.html ) and learned that the above values are in milliseconds. It seems that the default_randomization value is added to the other values in the list to create a schedule of retry attempts, but I wasn't able to figure out all the parameters to the method, if I even have the right one. I tried changing "infinite" to a small number under 10, but it had no effect - the process just keeps retrying forever.
Is there a dev out there who knows more about this? I want to limit this process because I seldom use cellular data right now and am usually on WiFi. It hinders any attempt to extend battery life. Is it a bug? Is it fixed in a later release (I'm on .748 stock) ? Do any of the custom ROMs have this problem? Can the build.prop setting I found be given values that limit the amount of time this process holds wake locks?
Thanks.
Did you ever get any resolution on this? For me, I think the problem started with the ICS update this summer. I constantly have gsm_data_tracker, RILJ, and IMS_Data_Retry using up the battery (in that order from highest to lowest). I tried wiping cache which helped the 1st time it cropped up and then it came back. I also tried a tip I saw somewhere for turning on airplane mode, rebooting, and turning off airplane mode (though mine as soon as it reboots, it already turns off airplane mode which it shouldn't). That worked for several weeks, but I had to do it EVERY DAY when I got to work. I think it's something with the 3g repeaters in the building. I did have it so it was wifi only (mobile radio off) on my work profile in profile scheduler, but then I needed cell for some mms stuff, so I ended up enabling it again. Basically when I come in the building and forget about my phone for an hour or 2, I go to get it out of my backpack and it will be hot from processing and 20% or more of the battery gone when I've done nothing in 2 hours of being at work. I saw somewhere that someone though either gsm_data_tracker or RILJ was related to something with the alarm, which I do use my phone as my alarm, but I use a 3rd party app. With the time change, there were a few days I woke up before it ever went off, so I turned it off before it did alarm. There were no differences with the partial wakelocks or battery drain in those cases. Unfortunately, I don't have another alarm readily available to get up for work right now and on the weekends when I don't need an alarm, I can't replicate the cell repeater at work issues, since I wouldn't be around the cell repeaters. As fart as in the building at work, until I reboot with airplane mode and all of that, the cell signal will bounce between like 0 bars/3g and lots of bars (no indication of network) and some bars with 1x network. It's all over the place. The airplane mode/reboot used to stabilize that, but it doesn't seem to be doing the trick anymore the last few days that I've tried that. I have to leave my phone on the charger as much as possible at work so that I don't leave for the day with a dead phone.
I like keeping my wifi on while my screen is asleep so that I can receive chat messages or e-mails without being at my computer. I never had this problem while running ICS on an unrooted TF201, but ever since I installed the upgrade to JB my wifi will always disconnect after the screen has been asleep for a few minutes. I've checked every setting I can think of. In the Wifi Advanced menu, I have it set so Wifi is always on, and in the ASUS customized setting I have Disconnect network during sleep to off. Under Power Saver I have Enable low battery settings off, set Low battery level to 0%, and even set Wifi OFF to off. Despite all of this, it seems like the tablet under JB goes into some sort of deep sleep and disconnects the wifi after about 5 minutes of inactivity.
I have noticed that this problem does not occur when the screen is on. I also have the dock, and set the screen to always on during meetings in the event that I don't need to enter any notes for a few minutes so I don't have to fool with any delays from screen wake .
Is there some setting I'm missing? Is it a hidden setting that I could access by rooting? Or am I dealing with something internal to the build that I can't change at all? This may not seem like a huge deal to most, but it has become one of my main uses for the tablet when I'm at home. I'm very disappointed with JB so far even though the wifi does feel more responsive on the Prime after the update (when it's not sleeping, of course!).
EDIT: I noticed this evening that the wifi turns off even when I'm running something that uses it while the screen is off. I was listening to Pandora, and about 5 minutes after the screen went off, my music stopped. When I turned the screen back on, I saw that the wifi had indeed become disconnected.
hey,
I have exactly the same problem with my tablet. I have checked every option, I did a factory reset several time, I have checked it on 2 different routers but it is still disconnecting the wife when it goes in the sleep modus. Did you or anyone else find a solution?
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...
Hi,
I'm having the following problem:
Short story:
From time to time something triggers battery drain in deep sleep on my Xperia Go. Usually my phone works as it should (battery drain over night is just a few %), but suddenly something starts to drain the battery and only reboot can stop it. I haven't figured out any pattern at which the drain starts, sometimes it works fine for weeks but sometimes it starts just a few hours after a reboot.
More details:
The phone is Xperia Go with the latest stock FW (.100). It is rooted but has locked bootloader. I have no bloatware installed, no Facebook, no Viber, no Whatsup, basically nothing in background and both WiFi and mobile data turned off (even location services turned off). I'm not using neither Sony's Stamina mode nor Low battery mode. I've verified that the system is really in deep sleep during the night by running script like this in terminal (https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en):
i=0
while true; do (( i++ )); echo $i; sleep 1; done
Click to expand...
Click to collapse
It is simply counting seconds while awake. There are only a few lines printed in background during the night so I'm nearly sure that the main CPU is sleeping most of the time. So I can think of 2 other suspects. First would be the radio (GSM module) as that is the only part that is running even in deep sleep. Second would be the Mali GPU as I don't know how to verify if it is really sleeping. Both are also restarted with system reboot which temporarily solves the problem (sometimes even for weeks if I'm lucky).
Anyone can confirm such behavior?
Any idea how to restart radio or GPU only without system reboot?
Any idea how to check whether GPU really sleeps when screen is turned off?
Any other ideas?