Hello,
I have a new BQ aquaris M10, which is flashed to latest android firmware with official tools from the ubuntu version (it's not usable for me yet)...
The problem that I have is MASSIVE lag when wake from deep sleep... at least I guess that's the problem. If tab has been inactive for more than say 30 min it takes about a 1 to 1.5 minutes to wake the screen after pressing the power button. After that it works perfectly.
No idea where to go from here... there' doesn't seem to be any relevant battery drain or such. GSAM battery monitor shows some 30% bat used by apps rest by hardware with screen on top. I have something like 1,8% per hour usage while mostly in standby.
Any help is appreciated.
Just a little update.. After installing the wakelock app and putting it in the partial wakelock mode the problem disappeared entirely.
I've seen some posts with nexus users reporting similar freeze when entering deep sleep after update to Android 5.1
Anyone has any experience or advice?
I flashed mine to bq's Android ROM but ultimately decided I'd rather go back to experimenting with Ubuntu Touch than use an outdated, Google-saturated version of Android. If only there were a Google-free, up-to-date, 3rd party ROM for this thing.
Related
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
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 can’t say I’m impressed at all with the SGS2 battery life running CM11 M7 (KitKat 4.4.2). Quite often the battery won’t last through the day (luckily I can charge it at work, otherwise it wouldn’t even be bearable as a phone).
My crappy Sony Xperia J (JB) I had for a couple of weeks as a replacement could easily reach the end of the day with 70% charge still left when I plugged it in at night.
Android battery stats always show Android System and Android OS as the main offenders (around 20% - 25% each), above Screen usage, Voice calls, Mobile standby...
BetterBatteryStats tells me the phone is in the Deep Sleep most of the time, but also that it is awake (mostly at 200 MHz) quite a lot of time as well.
Here’s what I have already tried:
Disabled location services
Disabled Google Now
Disabled Google+ Auto-backup
Opt out of interest-based ads
Disabled back up data to Google servers
Disabled “Android Device Manager” as Device Administrator
Uninstalled all updates to Google Play Services
Disabled automatic updates from the Play Store
Disabled Mobile Data Limit
Disabled Automatic Date/Time updating
Uninstalled Lookout Antivirus
Uninstalled Viber
Uninstalled Skype
Rebooting the phone before connecting the charger
Rebooting the phone immediately after disconnecting the charger
I really don’t want to perform a factory reset specially since I have read some other comments by Galaxy S5 and Nexus 5 owners (KitKat 4.4.2) saying it didn’t work…
So what exactly is going on here?
Thanks!
Sorry
MegaSharkXDA said:
Hi,
I can’t say I’m impressed at all with the SGS2 battery life running CM11 M7 (KitKat 4.4.2). Quite often the battery won’t last through the day (luckily I can charge it at work, otherwise it wouldn’t even be bearable as a phone).
My crappy Sony Xperia J (JB) I had for a couple of weeks as a replacement could easily reach the end of the day with 70% charge still left when I plugged it in at night.
Android battery stats always show Android System and Android OS as the main offenders (around 20% - 25% each), above Screen usage, Voice calls, Mobile standby...
BetterBatteryStats tells me the phone is in the Deep Sleep most of the time, but also that it is awake (mostly at 200 MHz) quite a lot of time as well.
Here’s what I have already tried:
Disabled location services
Disabled Google Now
Disabled Google+ Auto-backup
Opt out of interest-based ads
Disabled back up data to Google servers
Disabled “Android Device Manager” as Device Administrator
Uninstalled all updates to Google Play Services
Disabled automatic updates from the Play Store
Disabled Mobile Data Limit
Disabled Automatic Date/Time updating
Uninstalled Lookout Antivirus
Uninstalled Viber
Uninstalled Skype
Rebooting the phone before connecting the charger
Rebooting the phone immediately after disconnecting the charger
I really don’t want to perform a factory reset specially since I have read some other comments by Galaxy S5 and Nexus 5 owners (KitKat 4.4.2) saying it didn’t work…
So what exactly is going on here?
Thanks!
Click to expand...
Click to collapse
Sorry I cannot help you, however, I am also contemplating installing cm11 on my sgs2 i9100.
I wanted to ask you if you phone came with android version 2 installed on it? (maybe in that case the problem is incapable hardware)
Mine came with 2.3.4 and i do not want to face the same problem as you are now (sorry).
Thanks
It is normal, that non-stock-based roms consume more power because Samsung haven't open-sourced all drivers. And Kitkat drains more than Jellybean. Try Slimsaber Reborn. It has a decent battery life, an very acitve developer, and is nicely customizable.
Any luck?
MegaSharkXDA said:
Hi,
I can’t say I’m impressed at all with the SGS2 battery life running CM11 M7 (KitKat 4.4.2). Quite often the battery won’t last through the day (luckily I can charge it at work, otherwise it wouldn’t even be bearable as a phone).
My crappy Sony Xperia J (JB) I had for a couple of weeks as a replacement could easily reach the end of the day with 70% charge still left when I plugged it in at night.
Android battery stats always show Android System and Android OS as the main offenders (around 20% - 25% each), above Screen usage, Voice calls, Mobile standby...
BetterBatteryStats tells me the phone is in the Deep Sleep most of the time, but also that it is awake (mostly at 200 MHz) quite a lot of time as well.
Here’s what I have already tried:
Disabled location services
Disabled Google Now
Disabled Google+ Auto-backup
Opt out of interest-based ads
Disabled back up data to Google servers
Disabled “Android Device Manager” as Device Administrator
Uninstalled all updates to Google Play Services
Disabled automatic updates from the Play Store
Disabled Mobile Data Limit
Disabled Automatic Date/Time updating
Uninstalled Lookout Antivirus
Uninstalled Viber
Uninstalled Skype
Rebooting the phone before connecting the charger
Rebooting the phone immediately after disconnecting the charger
I really don’t want to perform a factory reset specially since I have read some other comments by Galaxy S5 and Nexus 5 owners (KitKat 4.4.2) saying it didn’t work…
So what exactly is going on here?
Thanks!
Click to expand...
Click to collapse
Hi MegaShark!
I have almost the same issue you have, my device never go to deep sleep... (by "never" I mean 1 minute deep sleep and 1 hour 200MHz)
After months trying, getting help from Better Battery Status thread, flashing, freezing, going crazy, I commited suicide (flashed stock ROM), but it is driving me mad.
The last try I did was with SlimSaber Reborn (Android 4.3.1), but no luck also.
Installed "Unbounce", prevented nlp wakelock, prevented safe alarms and nothing, it only gets worse...
All I get is my device always warm (always running at minimum of 200MHz) and more than 10% battery drain per hour.
Have you found out what is the problem with our S2 on custom ROMs?
Thank you!
First of all, I would advise you to update your rom. CM11 M7 is old now and is filled with bugs (along with versions around that). Update to CM11 M11 Snapshot which will most likely fix many of the problems you are facing but you will need to do a full wipe (factory reset, wipe dalvik and cache partitions). So sorry, the only way to fix is to wipe your data and update.
Will try!
gsstudios said:
First of all, I would advise you to update your rom. CM11 M7 is old now and is filled with bugs (along with versions around that). Update to CM11 M11 Snapshot which will most likely fix many of the problems you are facing but you will need to do a full wipe (factory reset, wipe dalvik and cache partitions). So sorry, the only way to fix is to wipe your data and update.
Click to expand...
Click to collapse
I remember to have hope until CM11 M9... But I'll give M11 a try and report back here!
Drain NOT related to any of the CM version
I have been facing battery draining problem in my sgs2 (i9100) just after installing CM 11.
Then I tried NeatROM without any Luck!
Every time i cleaned data, cache and dalvik to be sure...
at the end I moved back to Stock ROM - everything fine there...
but again then I decided to have just root and custom recovery installed... which required me to Flash Jeboo Kernel v1.2a (which comes with CWM based recovery 6.0.2.7 preloaded)
then it started same problems again... overheating - battery draining ...
It clearly look like ... the battery draining/overheating problem is because of .... Kernel AND/OR CWM 6.XXX
I think, if one want to install CM 11 in sgs2, after installing ROM, he/she need to flash it with some other kernel.
If anybody have tried some other kernel, which doesn't cause battery draining/overheating problem, then pls post here so that other can also try...
Confused
pankhawala said:
I have been facing battery draining problem in my sgs2 (i9100) just after installing CM 11.
Then I tried NeatROM without any Luck!
Every time i cleaned data, cache and dalvik to be sure...
at the end I moved back to Stock ROM - everything fine there...
but again then I decided to have just root and custom recovery installed... which required me to Flash Jeboo Kernel v1.2a (which comes with CWM based recovery 6.0.2.7 preloaded)
then it started same problems again... overheating - battery draining ...
It clearly look like ... the battery draining/overheating problem is because of .... Kernel AND/OR CWM 6.XXX
I think, if one want to install CM 11 in sgs2, after installing ROM, he/she need to flash it with some other kernel.
If anybody have tried some other kernel, which doesn't cause battery draining/overheating problem, then pls post here so that other can also try...
Click to expand...
Click to collapse
pankhawala, I installed the last available SlimSaber Reborn (4.3) (here: http://forum.xda-developers.com/gal...rivatives/rom-slimsaber-reborn-i9100-t2811657) because o lots of positive feedback on this ROM.
It is really a very nice ROM, but my battery drain problem persisted, I was losing more than 10%/hour in idle.
I just tried to "live with it" and after some weeks it mysteriously gone away.
I was happy for a few days and it went back again.
Now, it has been since this Sunday that it is gone again.
I'm being able to have a very acceptable battery life, very good deep sleep times and less than 4%/h when idle (screen off).
I didn't changed anything and it just got better by itself.
I'm sure it will start to drain again, just don't know when or what is triggering it.
My last hope is that when new Lollipop ROMs start coming out for our S2, some holy developer figure out this problem or that the problem is simply gone.
Hi,
I am very new to this and I created this account in the hope that someone will be able to help me. Please be gentle with me and explain things like I'm five.
I recently installed CM13 on to my Galaxy S2 and the battery drain is ridiculous. For example, it was fully charged fifty minutes ago but it is now at 89% - and for a majority of that time it has been in aeroplane mode. I am using Wi-Fi only when not in aeroplane mode and while this hastens the battery drain, it's not by a huge percentage.
My phones stats are:
Android version: 6.0.1
CyanogenMod version: 13.0-20160404-NIGHTLY-i9100
Kernel version: 3.0.101-CM-g3419d27 [email protected] #1
GAPPS: BaNkS-Dynamic-GApps-6.x.x-10-20-15
TWRP: IsoRec_TWRP_3.0.0-0_i9100
Things I have tried:
Using privacy guard to stop Google Play Store and various other apps from starting on boot and staying awake.
Setting the screen brightness level to the absolute minimum.
Setting the screen to go to sleep after 15 seconds inactivity.
Turning off Wi-Fi scanning.
Setting my e-mail pushes to one hour instead of instantly (which I especially hate).
Turning off voice recognition.
Setting location mode to battery saving.
Installing Advanced Task Killer, Greenify and/or DU Battery Saver.
Recalibrating the (new) battery - manually and with the battery calibration app.
Resetting network settings.
And various other things that I can't recall right now.
I recently installed GSam Battery Monitor, but it's not telling me much at the moment - just that the screen uses 64% and apps use 36%, and the average battery life per complete charge is at 7h 13m (3h 20min active).
If I go to settings > battery, it's telling me even less - the screen has used 4%, CyanogenMod System uses 2%.
I've read on other forums that installing a different kernel will improve it, but others have said it won't make any difference. Either way, I have no idea where to get the kernel from. I'm starting to think I must have installed something very wrong when the battery life on my phone won't even last eight hours. I have spent the past couple of days browsing to try and find out what I can do, and I think I'm about to go cross eyed.
Can anyone please help? Please remember that I am a complete newcomer to this so I may be asking some really stupid questions.
Thank you in advance for any help offered. I really don't want to go back to my 3GS now.
Hey,
I'm also on CM13 and also have battery drain, since Android 6 is really heavy, but definitely not as bad as you.
One thing you else could try is the app "BetterBatteryStats" which is available for free on XDA - just search. In my opinion it's the best available app for battery statistics. You can check out which app is keeping your device awake at standby.
But in your case, as you already tried a lot, I recommend to simply do a clean install of CM again. Really looks like there were little errors while flashing, or the Rom's zip file got somehow corrupted at the download. So download ROM and Gapps again, go to recovery, wipe /system, /data, /cache and reflash ROM and Gapps. Perhaps use another Gapps package than you used before. Also consider choosing the littlest available one. Maybe the issue will be gone then. Really hope this helps somehow.
Was I gentle enough?
Hello! I've been trying to investigate battery drain issues on my Z5C (with nougat) for the last week. It's been quite the annoying experience, to be frank.
Here is a screenshot from Wakelock detector LITE: http://imgur.com/a/2Ljyv
As you can see, for about 13-14 hours, with 30 minute of screen time, these wakelocks have built up to numbers like 20,000, or 70,000, etc. I am not sure if this is normal, but to be fair it seems like it absolutely isn't normal.
I have only used the screen to browse google wakelock searches in these 30 mins, more or less, and to check the wakelock app itself.
Furthermore, I tried using Greenify and it did slow my screen turn-on time considerably. I uninstalled it. My delay with screen wake-up remained... It was a huge mistake to try this app as it seems to have broken my OS and introduced unexplained OS lag at random times, which I did NOT have before at all.
Do you think a factory reset can solve this?
I am starting to think about rolling back to 6.0.1 and staying there forever with root and xposed. This type of erratic phone behavior really plays a number on my nerves.
thanks for reading!
go back and just restrict every non-system sony/xperia and as much of the google things as you can without restricting play service/store or framework