Database Develop

Bad battery life after KitKat upgrade - Solution

You've probably seen a ton of complaints on the bad battery life after KitKat upgrade. Google Services is seen at 90+% in battery stats, and the battery is discharging very quickly.
Factory reset is reported to cure the problem. Many are disabling Google Location services. There's also a workaround suggested by Sony, to disable backup and interest-based ads, or uninstall the latest Google Services.
[edit Jul-1-2014]
New Google Play Services 5.0 is now out, and its APK can be downloaded and installed just by searching for it in Google. It's reported to cure the problem for some, temporarily or permanently. It's recommended to try it first, before going with the suggestion below.
[previous post contents starting here]
However, there's no need to resort to the above, a much "lighter" solution may work. I've attempted it on my father's ZR and it worked.
Thanks to grim_ripper for mentioning steps that I forgot.
What needs to be done:
1. Go to Settings / Security / Device Administrators, disable Android Device Manager, if enabled.
2. Go to Settings / Apps, disable Google Play Services. It'll ask you to uninstall all updates, agree to it. After disabling it, some of other phone services might crash. Don't mind it.
3. This step might not be required according to the feedback from grim_ripper, however I'll list it "just in case": press "Clear data", or "Control data usage" and then "Clear all data". Make sure that in the Google Play Services app page, it's listed as disabled and has 0kB data usage.
4. Re-enable Google Play Services. Hangouts will immediately ask for its upgrade, get into Google Play Store and upgrade it.
5. Reboot the phone. You should see no crashes at this point.
6. In case you want Android Device Manager to function - go to Settings / Security / Device Administrators and enable it.
That's it, Google Play Services battery usage will be back to normal, and battery life seems even improved over JellyBean.
[edit Jul-13-2014]
The fix might stick for some, and some will find the battery drain coming back after several days. I'm over a month with it, and everything is still fine. However, the results are mixed.

Jack_R1 said:
You've probably seen a ton of complaints on the bad battery life after KitKat upgrade. Google Services is seen at 90+% in battery stats, and the battery is discharging very quickly.
Factory reset is reported to cure the problem. Many are disabling Google Location services. There's also a workaround suggested by Sony, to disable backup and interest-based ads, or uninstall the latest Google Services.
However, there's no need to resort to the above, a much "lighter" solution may work. I've attempted it on my father's ZR and it worked.
What needs to be done:
1. Go to Settings / Apps, disable Google Play Services. It'll ask you to uninstall all updates, agree to it. After disabling it, some of other phone services might crash. Don't mind it.
2. Press "Clear data", or "Control data usage" and then "Clear all data". Make sure that in the app page, it's listed as disabled and has 0kB data usage.
3. Re-enable Google Play Services. Hangouts will immediately ask for its upgrade, get into Google Play Store and upgrade it.
4. Reboot the phone. You should see no crashes at this point.
That's it, Google Play Services battery usage will be back to normal, and battery life seems even improved over JellyBean.
Click to expand...
Click to collapse
I confirm that this works, I didn't even clear data.Just disabled android device manager, uninstall google play services, enabled android device manager, re-install play services and finally reboot

Thank you, I completely forgot about Android Device Manager blocking the app disable. With your permission, I'll update the instructions.

I have just tried that thing you posted, will see how the results are in a few days.
One thing I noticed after upgrading to KK is night time for about 8 hours the battery drains 10% while in JB 4.3 it drains about 20% or more.
But the usage draining is similar to JB in KK. Will see if this thing works. Don't like to go to barebones CM11 cause I will be missing on the many features of the phone.
Let's see

It s working here too!
At first, I didn't even thought I had a problem but I looked in the processes and saw this f... Google service running.
Now my batterie last even better than when I was on 4.3.
Thanks

Jack_R1 said:
Thank you, I completely forgot about Android Device Manager blocking the app disable. With your permission, I'll update the instructions.
Click to expand...
Click to collapse
No Problem. I found out that this method only works as long as you don't reboot the phone after the fix, otherwise you'll need to do the whole process again. Mine went well until I waited till my battery was fully discharged before charging, hence forcing a reboot which play services started misbehaving again

I just realized a new battery drain problem, the Xperia social services keeps draining my problem

grim_ripper said:
I just realized a new battery drain problem, the Xperia social services keeps draining my problem
Click to expand...
Click to collapse
Oh yes, I have all these disabled. Perhaps this is why I had to restart the phone a couple of times already (changing SIM cards back and forth), and the original Google Services problem didn't come back.

Jack_R1 said:
You've probably seen a ton of complaints on the bad battery life after KitKat upgrade. Google Services is seen at 90+% in battery stats, and the battery is discharging very quickly.
Factory reset is reported to cure the problem. Many are disabling Google Location services. There's also a workaround suggested by Sony, to disable backup and interest-based ads, or uninstall the latest Google Services.
However, there's no need to resort to the above, a much "lighter" solution may work. I've attempted it on my father's ZR and it worked.
Thanks to grim_ripper for mentioning steps that I forgot.
What needs to be done:
1. Go to Settings / Security / Device Administrators, disable Android Device Manager, if enabled.
2. Go to Settings / Apps, disable Google Play Services. It'll ask you to uninstall all updates, agree to it. After disabling it, some of other phone services might crash. Don't mind it.
3. This step might not be required according to the feedback from grim_ripper, however I'll list it "just in case": press "Clear data", or "Control data usage" and then "Clear all data". Make sure that in the Google Play Services app page, it's listed as disabled and has 0kB data usage.
4. Re-enable Google Play Services. Hangouts will immediately ask for its upgrade, get into Google Play Store and upgrade it.
5. Reboot the phone. You should see no crashes at this point.
6. In case you want Android Device Manager to function - go to Settings / Security / Device Administrators and enable it.
That's it, Google Play Services battery usage will be back to normal, and battery life seems even improved over JellyBean.
Click to expand...
Click to collapse
I confirm that it works. At least for a week or so - after that the GogglePlayServices problem appeared again....

Dont helps in my case too.
At first it seems that it works, but after a day the google services are again over 75 prozent or so.
Thinking of going back to 4.3 or hoping that a fix will come soon.

Is it necessary to factory reset after update to kit kat to encounter the battery drain problem?

I had these problems and the only save cure is to disable the location services. Some times you would think a solution helps but stucked with an empty Phone suddely is a bad thing.
Sent from my C5503 using XDA Premium 4 mobile app

Is something known of a fix from Google for the google services?
I ask cause since yesterday evening the akku works normal in my case. Dont see the google services as first in line of accu consumption like before. Seems that everything works fine again.

Lemmi1 said:
Is something known of a fix from Google for the google services?
I ask cause since yesterday evening the akku works normal in my case. Dont see the google services as first in line of accu consumption like before. Seems that everything works fine again.
Click to expand...
Click to collapse
After I disabled the location service I see the android system in the second line. And the google services almost at the bottom line. The battery usage still not very good.

Been through several reboots by now, everything enabled, location is used, the problem didn't return, on both mine and my father's phones.
The only thing worth noting is my phone configuration - not rooted, STAMINA mode disabled, Low battery mode disabled, Queue background data disabled, Location-based WiFi enabled.
Waiting patiently for the next Sony update.

OK, the method seems to be obvious.
Does it need to be repeated after every reboot?
I also do not understand why installing the latest Google Play (after removing it the way it is written here) is not bringing the problem back .
Thanks anyway.

By the looks of it, the issue might be caused by user data being present already in Google Services since before the KitKat upgrade, but this is some type of data that's not necessarily present once it's deleted. Maybe some sort of duplication / overloading of data from multiple places, and this changes the order of loading.

one word: AMAZING
after this all the lagging of UI and keyboard is removed.
I was intending to install CM11, but after this fix I think I will stay with stock ROM

Ok this worked well for a couple of days including the UI lag fix but now Play services is destroying my battery again. I'm fed up with my ZR (Bluetooth issues and all) Just ordered a Nexus 5 yay!
Sent from my C5502 using Tapatalk 2

New Google Play Services 5.0 is out, if it didn't reach you yet - you can install it. It stops the battery drain.

SystemUpdateService always on

Hi all,
I just installed cm-11-20140609-SNAPSHOT-M7-galaxysmtd.zip and I have a big problem with SystemUpdateService which is always on and draining my battery. The phone will not go in deep sleep, it will just stay awake.
I tried all of the following:
1. Installed Disable Service and went on to disable SystemUpdateService, but it was already disabled.
2. Installed Autorun Manager and went on to disable com.google.android.gsf.update.SystemUpdateService$Receiver. but it was already disabled
3. I copied FOTAkill.apk in the System folder with RS Root Explorer and restarted, but the problem kept persisting
The only way to stop is is to disable GoogleServiceFramework, which will cause my phone to display the "unfortunatelly google play has stopped" error now and then, which is annoying and just a crude fix to the problem.
Does anybody know what else I could do?

keeekeeess said:
Hi all,
I just installed cm-11-20140609-SNAPSHOT-M7-galaxysmtd.zip and I have a big problem with SystemUpdateService which is always on and draining my battery. The phone will not go in deep sleep, it will just stay awake.
I tried all of the following:
1. Installed Disable Service and went on to disable SystemUpdateService, but it was already disabled.
2. Installed Autorun Manager and went on to disable com.google.android.gsf.update.SystemUpdateService$Receiver. but it was already disabled
3. I copied FOTAkill.apk in the System folder with RS Root Explorer and restarted, but the problem kept persisting
The only way to stop is is to disable GoogleServiceFramework, which will cause my phone to display the "unfortunatelly google play has stopped" error now and then, which is annoying and just a crude fix to the problem.
Does anybody know what else I could do?
Click to expand...
Click to collapse
I installed (cm-11-20140609-SNAPSHOT-M7-galaxysmtd.zip) on my device
and i am not found this problem?

try wakelock detector to see what's keeping it awake http://forum.xda-developers.com/showthread.php?t=2179651

Starting today, I got this issue as well on a Nexus 4 device running the M7 snapshot with hellscore kernel. The first 2 steps you took didn't work for me too. Didn't know about #3 this far.
keeekeeess said:
The only way to stop is is to disable GoogleServiceFramework, which will cause my phone to display the "unfortunatelly google play has stopped" error now and then, which is annoying and just a crude fix to the problem.
Click to expand...
Click to collapse
Doesn't sound pretty, but how did you do this? Still better than running out of battery halfway through the day, I'd guess.
pryerlee: WLD says exactly that - Google Play Services -> SystemUpdateService, for me currently 4h23m, being 100% of the time - plus it says "x2" (what's that precisely?)

not sure if this will help but read tho the post http://forum.xda-developers.com/showthread.php?t=2388243 http://forum.xda-developers.com/showthread.php?t=2378962

it is not work this servicein with lock screen!!
(i speek arabic good but english not good)
Sent from my GT-I9000 using XDA Free mobile app

pryerlee: Couldn't make anything out of those.
Just linking the other way round as well, maybe it'll help - the issue popped up on CM forums too: http ://forum.cyanogenmod. com/topic/96459-systemupdateservice-wakelock-on-cm11-m7-massive-battery-drain/
(sry for destroying the link, I'm blocked from posting it.)

pryerlee said:
not sure if this will help but read tho the post http://forum.xda-developers.com/showthread.php?t=2388243 http://forum.xda-developers.com/showthread.php?t=2378962
Click to expand...
Click to collapse
I did all of the options, the service is closed yet it was still running.
I compromised and installed Paranoid Android 4.4.2 and the problem is no more.

So just trying stuff without any deeper thoughts, I just did two things, locked the phone afterwards and now the wakelock seems to be gone:
1. I enabled SystemUpdateService using Disable Service App, which had already been disabled when we first looked.
2. I looked into the CM update function, where - having selected all stable releases - nothing was showing and refreshing didn't work. Got the idea to look into Disable Service App again, and found that UpdateCheckService of CyanogenMod-Updater was disabled. Enabled it, refreshed CM updater, got a list of stable releases.
My beginner's guess would be #1 did it - but why was #2 even an issue in the first place?

Running CM 11 M7 Snapshot 6/9/14 msm8960 on Motorola Atrix HD MB886. Have seen something similar.
Details:
- Have not seen this issue for weeks of running this ROM until now.
- This seems to have started a few (2?) days ago after an update. Google Play Music, Maps, Search, Drive, Sheets, and Docs all received updates in the past week.
- Typically, based on the configuration and usage of my phone, when the screen on is off the phone is in Deep Sleep (percentage in high 90s).
- At some point after some app or service is run, the phone stops going into deep sleep.
- Better Battery Stats shows SystemUpdateService as having partial wakelock for about the same percentage of time that the phone should be in deep sleep (high 90s).
- SystemUpdateServices does not seem to be hogging battery even considering that it might be folded into another category, but the wakelock causes the phone to use battery more than twice as fast as in deep sleep.
- A restart clears it up until the SystemUpdateService is invoked again by... whatever... seems to be something I do manually - still chasing it.

IronTechmonkey,
confirming your descriptions, up to the point where you describe that a reboot clears the issue up until a certain unknown event some time after boot. This is clearly not the case for me.
Instead, I was just able to reproduce the behaviour I described above. The wakelock remained gone since my last post, then I had to reboot for another reason, and it was there again basically from the first second (100% awake time since boot). Looking into Disable Service, SystemUpdateService was unchecked / disabled - again I checked / enabled it, and the wakelock stopped immediately.

Silkeyway said:
IronTechmonkey,
confirming your descriptions, up to the point where you describe that a reboot clears the issue up until a certain unknown event some time after boot. This is clearly not the case for me.
Instead, I was just able to reproduce the behaviour I described above. The wakelock remained gone since my last post, then I had to reboot for another reason, and it was there again basically from the first second (100% awake time since boot). Looking into Disable Service, SystemUpdateService was unchecked / disabled - again I checked / enabled it, and the wakelock stopped immediately.
Click to expand...
Click to collapse
I've been able to consistently replicate the problem 100% by running the Google Play app when the phone has a data connection.
If I run the Google Play app when the phone has no data connection the problem does not occur until the next time the phone has a data connection, whether or not Google Play is running.
I do have all auto-updating disabled in google and elsewhere which makes this easier to chase.
See if it happens when your phone has no data connection, with apps and google things set not to autoupdate.
As for the temporary fix: Like you said: Disable Service app, System Apps list, Google Play Services, SystemUpdateService enable/disable.

I'll try with those conditions asap. No time just now.
However, doesn't this all raise the question why SystemUpdateService is disabled? Shouldn't this default to enabled?
Or to put it differently: Is enabling SystemUpdateService a workaround, or is it being disabled the issue?

I also had the wakelock on my P990.
systemupdateservice was disabled in gooogle service framework, but it was still active as receiver and actice receiver in google play services - disabling it there solved the wakelock for me.

Silkeyway said:
I'll try with those conditions asap. No time just now.
However, doesn't this all raise the question why SystemUpdateService is disabled? Shouldn't this default to enabled?
Or to put it differently: Is enabling SystemUpdateService a workaround, or is it being disabled the issue?
Click to expand...
Click to collapse
Now that I've tested during a work day I'm seeing the problem occur more pervasively as some of you are
- It starts any time I go on line.
- Reboot sometimes but not always fixes
- Toggling using Disable Service app no longer works reliably
- Must stop Google Services Framework to fix issue until next time I go on line
= Royal PITA!
As for your question; It is not uncommon in the world of computers (and phones) to have to toggle a setting on/off or off/on to get the setting to stick, especially when something deeper in the system is turning it on and off without a flag letting the user know.

Just summarizing what was found on the CM forums where I tried to link previously:
Seemingly permanent workaround: http://forum.xda-developers.com/showpost.php?p=53739230&postcount=5031
Related fix, merged into nightly since Jun 29: http://review.cyanogenmod.org/#/c/66894/
Haven't tried that workaround, had no time to go for the nightly... hopefully the fix will already be included in the M8 stable release(?).

Silkeyway said:
... hopefully the fix will already be included in the M8 stable release(?).
Click to expand...
Click to collapse
Indeed hoping the same, and it looks like M8 and the nightly to which you refer will not yet be using the KK bootloader (great for my old Moto AtrixHD MB886 w/JB bootloader). Found that same XDA post referring to Autorun Manager which looks like a good temporary fix - working good so far. Does not hold setting through restart but still more effective than others..

I've the same issue here since 2/3 days on my 9001 running CyanogenMod 11.0 by ADC-Team - Release 8, maybe it was some app update occurred recently... I didn't have any issue with the same rom before.
---------- Post added at 10:29 AM ---------- Previous post was at 10:00 AM ----------
I can confirm that downgrading Google Play Services to version 4.3.25 is a working workaround.
http://forum.xda-developers.com/showpost.php?p=53851739&postcount=3026

Silkeyway said:
Just summarizing what was found on the CM forums where I tried to link previously:
Seemingly permanent workaround: http://forum.xda-developers.com/showpost.php?p=53739230&postcount=5031
Related fix, merged into nightly since Jun 29: http://review.cyanogenmod.org/#/c/66894/
Haven't tried that workaround, had no time to go for the nightly... hopefully the fix will already be included in the M8 stable release(?).
Click to expand...
Click to collapse
Hey everyone,
i can confirm the issue for CM11 M7 and it all started with the recent update to Google Play Services 5 v84.
The workaround mentioned before works very well until a reboot ... lets hope the best for CM11 M8!

Best workaround I've found:
"Finally I was able to block the SystemUpdateService wakelock, using this app:
https://play.google.com/store/apps/d...com.rs.autorun
go to settings, enable the option to show system entries
find google play services and disable:
SystemUpdateService$Receiver
SystemUpdateService$ActiveReceiver
SystemUpdateService$SecretCodeReceiver
done... no more wakelock and it didn't break anything, syncs all work ok
I know this app doesn't look the best, but I tried others like "Android Tuner Free", "Disable Services", "Gemini App Manager", etc, but they allowed me to only disable the main service and didn't show the other receivers that had to be disabled."
As the other user said, this is all caused by the Google Play Services update that has being rolling out this last week. The solution above is reboot proof (At least for me). Thanks to the user who posted it.

auto closing high power usage apps bug?

Does anyone experience any problems with this setting on 4.1.3? On my phone if i switch it off it sometimes switches itself back on. It also seems to close down apps without notifying me. They are just greyed out and cannot be cleared or removed. (Podcast republic and swipe). Those two apps are also the reason i want it switched off as they stop functioning properly if on.
It seems to be linked to the power saving auto rotate switch-off bug as it tends to happen most of the time when the auto rotate isn't switched on again when i charge the phone. Anyone else experiencing this?
Phone is not rooted and run on stock rom

Lol everybody learning how to set up the new power savers that the development community has been using since the days of ics.
1st problem sounds like you ambient display enabled which will turn on your phone every time you receive some sort of notification. To fix this simply go into your settings, display and turn off ambient display and don't get it confused with adaptive brightness.
2nd problem to me sounds like you have aggressive doze mode active on all your apps or auto close high power apps. To fix this just go to settings, battery, click the 3 dots next to the refresh symbol near the top right corner, click aggressive doze..., if it's turned on make sure the slider is not enabled next to the apps you desire, hit the back button, click on the 3 dots top right corner again, click on high power usage apps, turn it off if it's on.
These battery savers in the Android os are basically hacked and slashed from development on xda. Greenify did most of these functions alone then if you were to mash greenify with power nap you basically got yourself aggressive doze with closing of high usage apps.
Sadly Google is still behind the curve as the power saver app on my Asus Zenfone 2 does a better job at saving power on lollipop because in addition to hibernating and closing apps it allowed you to turn off networks allowing only phone, sms, and alarm to work after the device is asleep and enabled upon waking or you could do super saving which did the same thing except the network stays disabled the whole time boosting standby time from 92 hrs to 105 hrs
Seriously though the best course of action here if this does not help you is to contact the developer of the app and tell them the issues your having, your device and a detailed log report and you will see better results faster because it's probably just an incompatibility​ due to the new os as apps always have issues with fresh out of the gate os systems and your might not be the only person with this issue but you just might be the only person to point it out for a long time.
Sent from my ONEPLUS A3000 using Tapatalk

i snort flour said:
Lol everybody learning how to set up the new power savers that the development community has been using since the days of ics.
1st problem sounds like you ambient display enabled which will turn on your phone every time you receive some sort of notification. To fix this simply go into your settings, display and turn off ambient display and don't get it confused with adaptive brightness.
2nd problem to me sounds like you have aggressive doze mode active on all your apps or auto close high power apps. To fix this just go to settings, battery, click the 3 dots next to the refresh symbol near the top right corner, click aggressive doze..., if it's turned on make sure the slider is not enabled next to the apps you desire, hit the back button, click on the 3 dots top right corner again, click on high power usage apps, turn it off if it's on.
These battery savers in the Android os are basically hacked and slashed from development on xda. Greenify did most of these functions alone then if you were to mash greenify with power nap you basically got yourself aggressive doze with closing of high usage apps.
Sadly Google is still behind the curve as the power saver app on my Asus Zenfone 2 does a better job at saving power on lollipop because in addition to hibernating and closing apps it allowed you to turn off networks allowing only phone, sms, and alarm to work after the device is asleep and enabled upon waking or you could do super saving which did the same thing except the network stays disabled the whole time boosting standby time from 92 hrs to 105 hrs
Seriously though the best course of action here if this does not help you is to contact the developer of the app and tell them the issues your having, your device and a detailed log report and you will see better results faster because it's probably just an incompatibility​ due to the new os as apps always have issues with fresh out of the gate os systems and your might not be the only person with this issue but you just might be the only person to point it out for a long time.
Click to expand...
Click to collapse
Thanks
A) ambient screen is off already
B) already done that but the apps work better if battery optimisation is on for them than off. They really misbehave if not optimised.
How do I produce the logs? Checking under the specific app under apps doesn't seem to have an app log option.

Eggstones said:
Thanks
A) ambient screen is off already
B) already done that but the apps work better if battery optimisation is on for them than off. They really misbehave if not optimised.
How do I produce the logs? Checking under the specific app under apps doesn't seem to have an app log option.
Click to expand...
Click to collapse
Grab a catlog off of the play store they are fairly simple to figure out and they are free. I can't remember for sure but I believe I liked logcat the best as it provided a better ui with a more detailed and easier to read log.
Sent from my ONEPLUS A3000 using Tapatalk
---------- Post added at 01:46 AM ---------- Previous post was at 01:35 AM ----------
Eggstones said:
Thanks
A) ambient screen is off already
B) already done that but the apps work better if battery optimisation is on for them than off. They really misbehave if not optimised.
How do I produce the logs? Checking under the specific app under apps doesn't seem to have an app log option.
Click to expand...
Click to collapse
That's weird that it keeps turning back on hopefully it's not a hardware issue. Most likely due to a rogue incompatible app. Also if you haven't already done so check for an update and make sure you have the latest version and if that don't work the last thing I could think of to try would be to download the latest update and put it on your phone somewhere you can remember, reboot into recovery and erase your cache and perform a factory reset followed by another cache wipe just to be sure. Then select install update from zip file, navigate to it's directory and open it, allow it install the update and after it completely has finished booting don't use it but keep the screen from turning off for about 2 minutes
Sent from my ONEPLUS A3000 using Tapatalk
---------- Post added at 02:07 AM ---------- Previous post was at 01:46 AM ----------
Sorry I can't be of more help to you but I just got my phone today and I'm on the oos 4.1.3 and mine is doing just fine so far but I don't sync mail, push notifications, or use any social media which drain your battery like a hooker with your bank account. So far I'm at 10+ hrs uptime with 4 hrs of sot sitting at 66% battery life with an estimated 20 hrs left.
hope you find your problem or at least know where you got take your issue to which will be discovered in your cat log so you will know if it's the apps, kernels, os or hardware that is to blame and be able to address it to the proper source.
Sent from my ONEPLUS A3000 using Tapatalk

Phone not entering deep sleep

So, I've tried all Pie ROMs. PixelExperience to Syberia and Havoc OS. None of them enter deep sleep. I've tried everything posted wherever I can find on the internet:
1. Change ROM
2. Change CPU governor.
3. Change Kernel.
4. Make changes to those values which govern the time it takes for the phone to enter deep sleep.
Nothing worked!
Any suggestions? I shifted to MIUI 10, which DOES enter deep sleep. But I don't want MIUI, not right now, at least...

Okay, got it. T'was a problem with the opengapps. I used to flash mini. I flashed nano and everything's good now...

Nope. Not working.
Come on, you guys...52 views and not one person answered?

Looks like you've tried almost all possible things. is all sensor detection is turned off? such as pocket detection hand wave? maybe try turning of those. also the ambient display too.
if it still doesn't works then i think we might have this issue on all pie roms such as we had screencast issue on all pie roms.

livingongh325 said:
Nope. Not working.
Come on, you guys...52 views and not one person answered?
Click to expand...
Click to collapse
Maybe there is no solution... xD
I've experienced the same issue for a long time on the LOS 15.1 build where System usage is high despite long Phone Idle time and low usage.
The battery report actually does not make sense, but my battery life is certainly not what it should be compared to what some other users are getting.
It would be great if an expert can provide a solution on the deep sleep problem to extend battery life with these custom ROM's or a way to identify the culprit that keeps my phone awake.

metelhammer said:
Looks like you've tried almost all possible things. is all sensor detection is turned off? such as pocket detection hand wave? maybe try turning of those. also the ambient display too.
if it still doesn't works then i think we might have this issue on all pie roms such as we had screencast issue on all pie roms.
Click to expand...
Click to collapse
Yes.
I turned them off on the outright.
Which ROM are you using by the way?

livingongh325 said:
Yes.
I turned them off on the outright.
Which ROM are you using by the way?
Click to expand...
Click to collapse
I am using Havoc OS 2.6 20190609 build (which is latest one as i am writing). and i must say battery backup is great on stock kernel.

metelhammer said:
I am using Havoc OS 2.6 20190609 build (which is latest one as i am writing). and i must say battery backup is great on stock kernel.
Click to expand...
Click to collapse
Have you installed viper4android?

livingongh325 said:
Have you installed viper4android?
Click to expand...
Click to collapse
No, i haven't.

livingongh325 said:
So, I've tried all Pie ROMs. PixelExperience to Syberia and Havoc OS. None of them enter deep sleep. I've tried everything posted wherever I can find on the internet:
1. Change ROM
2. Change CPU governor.
3. Change Kernel.
4. Make changes to those values which govern the time it takes for the phone to enter deep sleep.
Nothing worked!
Any suggestions? I shifted to MIUI 10, which DOES enter deep sleep. But I don't want MIUI, not right now, at least...
Click to expand...
Click to collapse
Check if "pocket mode" is on, or "double tap to wake" or things like that, some months ago I lost one week trying to figure out, but was just the "pocket mode".

livingongh325 said:
So, I've tried all Pie ROMs. PixelExperience to Syberia and Havoc OS. None of them enter deep sleep. I've tried everything posted wherever I can find on the internet:
1. Change ROM
2. Change CPU governor.
3. Change Kernel.
4. Make changes to those values which govern the time it takes for the phone to enter deep sleep.
Nothing worked!
Any suggestions? I shifted to MIUI 10, which DOES enter deep sleep. But I don't want MIUI, not right now, at least...
Click to expand...
Click to collapse
Maybe you can use these apps to track what application(s) make your phone awakes: BetterBatteryStats, Wakelock Detector or Simple System Monitor.
I ever used TWRP 3.2.1 + Pixel Experience 8.1 (Oreo), and my phone never entered deep sleep state. I moved to MIUI 9.2.4 and the state was back to normal.
Now I use OrangeFox 9 recovery + Pixel Experience 9 (Pie) and the phone can sleep like a baby. It's been 2 weeks and still acts normally. Love it!

CalveinX said:
Check if "pocket mode" is on, or "double tap to wake" or things like that, some months ago I lost one week trying to figure out, but was just the "pocket mode".
Click to expand...
Click to collapse
Where do you find the "pocket mode" setting ?

Xiaomi Warrior said:
Where do you find the "pocket mode" setting ?
Click to expand...
Click to collapse
I am using Havoc and had the same problems until I decativated everything that reads motion or proximity sensors. Now I can go 4 days without charge.
The most options are in the havoc menue in "Inactivity screen -> Ambient Options" (I am not completly sure about the english labels, as I am using an other language.) "Pocket mode" is the last one in the list, but I have deactivated everything there.

theBoatman said:
I am using Havoc and had the same problems until I decativated everything that reads motion or proximity sensors. Now I can go 4 days without charge.
The most options are in the havoc menue in "Inactivity screen -> Ambient Options" (I am not completly sure about the english labels, as I am using an other language.) "Pocket mode" is the last one in the list, but I have deactivated everything there.
Click to expand...
Click to collapse
Pocket Mode for LOS15.1 it is under Settings -> Display -> Advanced -> Ambient Display or Settings -> Battery -> Ambient Display
I have turned all of this unnecessary trash off.
My phone still drains about 8-10% during night while in airplane mode which I do not think is normal.
I have even gone as far as disabling "Keep Awake" for installed apps under Privacy Guard.

Question Always On Display turns off after an hour or so.

Hey All.
I have always used AOD as a night clock whilst its charging vertically.
But with this phone the AOD always goes off after about an hour.
Which sort of defeats the point of the feature really.
the setting is set to ALLDAY aswell.
is this a fault or is this how it is with phone.

stuatrb04 said:
Hey All.
I have always used AOD as a night clock whilst its charging vertically.
But with this phone the AOD always goes off after about an hour.
Which sort of defeats the point of the feature really.
the setting is set to ALLDAY aswell.
is this a fault or is this how it is with phone.
Click to expand...
Click to collapse
chinese version?

brunolongo said:
chinese version?
Click to expand...
Click to collapse
nah uk

Possibly power management of some type shutting it down?
I use to think always on AOD was a darling... now I only use tap on.
Lol, I sort of like how yours behaves; it waits for you to go to sleep.

blackhawk said:
Possibly power management of some type shutting it down?
I use to think always on AOD was a darling... now I only use tap on.
Lol, I sort of like how yours behaves; it waits for you to go to sleep.
Click to expand...
Click to collapse
pretty sure i have looked at most settings that could possibly effect this.
maybe its just the way it is.
it kinda bugs me at night when i wake up disorientated not knowing the time.
always something i have been used to with previous phones.

stuatrb04 said:
pretty sure i have looked at most settings that could possibly effect this.
maybe its just the way it is.
it kinda bugs me at night when i wake up disorientated not knowing the time.
always something i have been used to with previous phones.
Click to expand...
Click to collapse
I hear you. Best to ignore the phone and sleep.
Always being "connected" detrimental to your wellbeing. Quiet time is very underrated.
Lots of power management settings scattered throughout the phone, usually.
Check to see if global power management is running first: Developer options>standby apps, all buckets should show as active otherwise power management is active. It can't be disabled here though.
Check each apk being used for AOD. Make sure they have needed permissions and that battery saving isn't checked.
Disable any power management including Android, 3rd party, carrier or manufacturer ones.
Try in Safe mode.
Clear system cache and AOD data.
Make sure screen lock isn't interfering with AOD.
With a factory reset even if it works the issue will likely reoccur. Exception is if a 3rd party app altered user hidden settings, this can and does occasionally happen with poorly written apps. Sometimes only after you uninstall them
Play with it, find the root cause... fun isn't it?

blackhawk said:
I hear you. Best to ignore the phone and sleep.
Always being "connected" detrimental to your wellbeing. Quiet time is very underrated.
Lots of power management settings scattered throughout the phone, usually.
Check to see if global power management is running first: Developer options>standby apps, all buckets should show as active otherwise power management is active. It can't be disabled here though.
Check each apk being used for AOD. Make sure they have needed permissions and that battery saving isn't checked.
Disable any power management including Android, 3rd party, carrier or manufacturer ones.
Try in Safe mode.
Clear system cache and AOD data.
Make sure screen lock isn't interfering with AOD.
With a factory reset even if it works the issue will likely reoccur. Exception is if a 3rd party app altered user hidden settings, this can and does occasionally happen with poorly written apps. Sometimes only after you uninstall them
Play with it, find the root cause... fun isn't it?
Click to expand...
Click to collapse
ah some things there that i havent tried.
will play around and report back.
yea the joys of android!!!

stuatrb04 said:
ah some things there that i havent tried.
will play around and report back.
yea the joys of android!!!
Click to expand...
Click to collapse
Feels good when you track it down.
I've tracked (and caused, oops) a few bizarre ones down
Stock Androids are generally very robust platforms.

Lately I have had a Oneplus 9, Oneplus 9 Pro and a Oneplus 10 Pro. In all of them, from Android version 12 (it also happens in 13), what is said here happens (AOD turns off at night even if it is programmed so that it is always active).
From what I see here, either it is a bug that has been introduced since the Oneplus and Oppo software were unified, or it is a crap that Google has put in Android since version 12 that there is no way to fix Because I've been trying things for a long time and reading in forums and websites and no solution to this problem is found anywhere.
For those of us who use our mobile phones as a nightstand clock, it is a great disappointment.

dtvenom said:
Lately I have had a Oneplus 9, Oneplus 9 Pro and a Oneplus 10 Pro. In all of them, from Android version 12 (it also happens in 13), what is said here happens (AOD turns off at night even if it is programmed so that it is always active).
From what I see here, either it is a bug that has been introduced since the Oneplus and Oppo software were unified, or it is a crap that Google has put in Android since version 12 that there is no way to fix Because I've been trying things for a long time and reading in forums and websites and no solution to this problem is found anywhere.
For those of us who use our mobile phones as a nightstand clock, it is a great disappointment.
Click to expand...
Click to collapse
Welcome to XDA.
Tap on works fine for me and uses less battery. Constantly looking at the time when you should be sleeping is counterproductive and a bad habit to get into. For me the novelty wore off after about a year as I find it now annoying.

It's the same on OnePlus 8T, Oxygen OS 13. At least after midnight, maybe earlier, the screen turns black with AOD always on after roughly 25-30 minutes if non use. Double tap or more activates it again.
It's broken for people who is working nights and/or is awake and active after midnight.
There's gotta be a setting fixing this through root or adb shell.