Related
Really, it comes down to installing Xposed framework and Greenify.
Sometimes we need to be told straight up what works, and its installing XPosed Framework, and installing Greenify to identify what's waking up and consuming battery - and then telling Greenify to put it to sleep.
I'm doing this write up because it's something I know a lot of us are facing with our Relay's as they age and we try to stay current with new roms.
Like quite a few of us I've sacrificed battery life for an updated rom that looks decent and runs fast. Between builds and Kernels I was lucky to get through the day let alone to 24 hours without my phone needing a charge - even if I didn't play any games.
I tried flashing clean and not using titanium backup - didnt have any effect once I had the apps I desired installed.
I checked OS Monitor, wakelock detector, battery usage things, juice defender... nothing really extended or identified what he true cause, things said Android System UI or Display or Graphics was eating it all up. I started wondering if it was the latest roms with the transparent pull down notifications or the annoying pop ups that show you text messages and emails in the top foreground of the screen ..
Turns out for me, it was my "Transparent Weather Widget" I wanted something that showed a 5 day forecast and this sucker was DRAINING my battery.
I'm now running SlimKat initial build (Mar 15 2014) with Xposed framework, Juice Defender and Greenify. Everything is working perfect on my phone now. I keep checking in greenify and sleeping apps that don't need to be using any resources until I execute them. One item about SlimKat is you need to 2 finger pinch together the recent tasks to close all apps at once, other than that it has every feature I wanted, less annoying pop ups than the most recent KitKat's and my battery today - 50% after 14 hours. Usually at the most by a day like today I would have is 15% but more likely 6%.
This may be long winded, but its the steps we've all been mystified on why System UI or Display is the leading cause of battery use.. I think it has to do with the transparency of my widgets .. Food for thought if it helps others.
yohan4ws said:
Really, it comes down to installing Xposed framework and Greenify.
Sometimes we need to be told straight up what works, and its installing XPosed Framework, and installing Greenify to identify what's waking up and consuming battery - and then telling Greenify to put it to sleep.
I'm doing this write up because it's something I know a lot of us are facing with our Relay's as they age and we try to stay current with new roms.
Like quite a few of us I've sacrificed battery life for an updated rom that looks decent and runs fast. Between builds and Kernels I was lucky to get through the day let alone to 24 hours without my phone needing a charge - even if I didn't play any games.
I tried flashing clean and not using titanium backup - didnt have any effect once I had the apps I desired installed.
I checked OS Monitor, wakelock detector, battery usage things, juice defender... nothing really extended or identified what he true cause, things said Android System UI or Display or Graphics was eating it all up. I started wondering if it was the latest roms with the transparent pull down notifications or the annoying pop ups that show you text messages and emails in the top foreground of the screen ..
Turns out for me, it was my "Transparent Weather Widget" I wanted something that showed a 5 day forecast and this sucker was DRAINING my battery.
I'm now running SlimKat initial build (Mar 15 2014) with Xposed framework, Juice Defender and Greenify. Everything is working perfect on my phone now. I keep checking in greenify and sleeping apps that don't need to be using any resources until I execute them. One item about SlimKat is you need to 2 finger pinch together the recent tasks to close all apps at once, other than that it has every feature I wanted, less annoying pop ups than the most recent KitKat's and my battery today - 50% after 14 hours. Usually at the most by a day like today I would have is 15% but more likely 6%.
This may be long winded, but its the steps we've all been mystified on why System UI or Display is the leading cause of battery use.. I think it has to do with the transparency of my widgets .. Food for thought if it helps others.
Click to expand...
Click to collapse
Really good post, I can say I using 20140315 version (last working camera) and last kernel for it (don't remember the version) get really good performance and similar battery, using the same xposed
OmniToad now includes methods to turn off specific alarms and wakelocks at a lower level than greenify and/or Xposed.
Magamo said:
OmniToad now includes methods to turn off specific alarms and wakelocks at a lower level than greenify and/or Xposed.
Click to expand...
Click to collapse
You can try the battery performance already?
yohan4ws said:
I'm now running SlimKat initial build (Mar 15 2014) with Xposed framework, Juice Defender and Greenify. Everything is working perfect on my phone now. I keep checking in greenify and sleeping apps that don't need to be using any resources until I execute them. One item about SlimKat is you need to 2 finger pinch together the recent tasks to close all apps at once, other than that it has every feature I wanted, less annoying pop ups than the most recent KitKat's and my battery today - 50% after 14 hours. Usually at the most by a day like today I would have is 15% but more likely 6%.
Click to expand...
Click to collapse
What kind of wireless networks do you use throughout the day and what kind of screen on time are you juicing out in your 14 hours??
hbk.vix said:
What kind of wireless networks do you use throughout the day and what kind of screen on time are you juicing out in your 14 hours??
Click to expand...
Click to collapse
30 second timeout on the screen, i check it to read emails and texts, the odd phone call, sometimes i will run a wifi diagnostic for the networks i support using fing and wifi analyzer.. i keep my phone off and locked otherwise. in the car bluetooth is enabled. i was going wifi diagnostic yesterday when i got such great battery life.
today i have android weather and clock widget (cant recall the exact name) running w 3hour update .. after 8 hours i have 58% remaining, im in an area with horrible cell coverage , stats say 38mins screen on time.
there is nothing different of my usage over the passed cpl weeks, just enabling greenify and sleeping a voip app, facebook, google maps and the weather widget.
yohan4ws said:
there is nothing different of my usage over the passed cpl weeks, just enabling greenify and sleeping a voip app, facebook, google maps and the weather widget.
Click to expand...
Click to collapse
I'm using dashclock with 15min weather update, greader app with over 120feeds (aggregated in feedly) with 15 min update interval too and lots of other apps including the evil facebook+messenger. I switched recently from latest LiquidSmooth to Omnitoad and the result is I got the battery dropped by 9% overnight (10 hours) in idle mode.
Nota bene: without any tweaking.
I installed the Xposed framework and successfully used it to get rid of the "Just Once" app picker annoyance.
Edit: the play store has a Greenify which requires Xposed framework. Tutorial on Greenify use is on Youtube. Up and running now, but noticed that I am not getting a GPS fix now ever since the altrnt app picker MOD. It's always something!
Sent from my SGH-T699 using XDA Free mobile app
How can install xposed on cm 11?
subzerobob said:
I installed the Xposed framework and successfully used it to get rid of the "Just Once" app picker annoyance.
Edit: the play store has a Greenify which requires Xposed framework. Tutorial on Greenify use is on Youtube. Up and running now, but noticed that I am not getting a GPS fix now ever since the altrnt app picker MOD. It's always something!
Sent from my SGH-T699 using XDA Free mobile app
Click to expand...
Click to collapse
Hi! Do you have your relay with CM11 or stock ROM? I can't manage to install xposed with CM11. Thanks!
ninguno2 said:
Hi! Do you have your relay with CM11 or stock ROM? I can't manage to install xposed with CM11. Thanks!
Click to expand...
Click to collapse
I'd be curious to know too. I recently tried to install xposed again (last time I used it was probably a couple of years ago) on my Relay running the last official CM11 nightly, and it didn't work either. First the installer complained that xposed isn't compatible with my version of the Android SDK, but there is a fix for that (I forget where, but it is somewhere on XDA). But even when I applied the fix, it still failed, I started getting bootloops. So yeah, I'd love to know how to install xposed on the Relay too...
I have to say, I have been using my Relay more lately, as my main phone has been having some issues, and the main thing that keeps me from using it more is battery life. I'm not crazy about the screen, but I can live with it, and I have just about everything else running fairly smoothly - and the keyboard is just a joy to use. This thing is a real workhorse. But when the battery plummets down to ~70% or 60% within a couple of hours of use, that's just not cool...
cucumbers said:
I'd be curious to know too. I recently tried to install xposed again (last time I used it was probably a couple of years ago) on my Relay running the last official CM11 nightly, and it didn't work either. First the installer complained that xposed isn't compatible with my version of the Android SDK, but there is a fix for that (I forget where, but it is somewhere on XDA). But even when I applied the fix, it still failed, I started getting bootloops. So yeah, I'd love to know how to install xposed on the Relay too...
I have to say, I have been using my Relay more lately, as my main phone has been having some issues, and the main thing that keeps me from using it more is battery life. I'm not crazy about the screen, but I can live with it, and I have just about everything else running fairly smoothly - and the keyboard is just a joy to use. This thing is a real workhorse. But when the battery plummets down to ~70% or 60% within a couple of hours of use, that's just not cool...
Click to expand...
Click to collapse
Hi, i got it working with the files in this posts
https://forum.xda-developers.com/showpost.php?p=72133164&postcount=210
https://forum.xda-developers.com/showpost.php?p=72133164&postcount=209
I download both files, first I install the apk and got a bootloop, and then flash the zip from recovery. That fixes the bootloop and keep xposed installed.
ninguno2 said:
Hi, i got it working with the files in this posts
https://forum.xda-developers.com/showpost.php?p=72133164&postcount=210
https://forum.xda-developers.com/showpost.php?p=72133164&postcount=209
I download both files, first I install the apk and got a bootloop, and then flash the zip from recovery. That fixes the bootloop and keep xposed installed.
Click to expand...
Click to collapse
So - install .apk, then flash the .zip - correct? And xposed is working well now for you?
[EDIT] So the .apk you posted worked just fine for me, no need to flash the .zip! Odd, but grateful this worked. Thanks!
Just wanted to confirm: Greenify (root) + Greenify xposed module + Amplify xposed module make a huge difference. Battery lasts much longer, and I have this sneaking suspicion the phone is generally smoother and less laggy. Might well be placebo, I know, but with useless background processes being sht down it might well have an effect on performance...
cucumbers said:
So - install .apk, then flash the .zip - correct? And xposed is working well now for you?
[EDIT] So the .apk you posted worked just fine for me, no need to flash the .zip! Odd, but grateful this worked. Thanks!
Click to expand...
Click to collapse
Great! I don't know why, but i had to flash the second one too.
Could you tell me which options have you check in Greenify and Amplify with xposed to get better battery life?
Thanks!
Greenify: Root mode + Xposed, of course. I've got automatic hibernation set, and for xposed features, I set all of them except Deep Hibernation
Amplify: even just selecting the default wakelock blocks in the free version helps a lot, but I use the paid version and I limited just about every wakelock that the app said was safe to limit (but only ones that were also described as safe in their blurb - some in the "safe" list are described as "we don't have any information for this wakelock yet") except for a few that were really light wakelocks.
Before I begin I just want to say that I have been using Android for a while and understand wakelocks etc. I have already made sure none of my apps are causing wake locks by uninstalling them but it has made no difference.
Here are my GSam screenshots: http://imgur.com/a/1Cp9z#0
As you can see, Android System and Android OS are the culprits that are draining my battery, but the phone isn't "awake" when they are draining it, so I am not quite sure what is happening. There is no wake-lock but there is a lot of CPU usage for some reason,
Please ignore the average times shown by GSam at the bottom, I get nowhere near 5hrs screen time, I reset the histories yesterday so its not yet calculated average properly yet.
I have tried - Stock COS11S, the latest COS 12.1 and also CyanogenMod 12.1 nightlies and the recent snapshot and they all exhibit this issue even with no apps installed. Is there a ROM out there that has no issues with this stuff?
Thanks!
Same problem. No idea the solution. No matter what battery app I use to try and tell me what is going on, it's always just listed as "android system" or "system" that is draining battery. I didn't have this on sultan's build so I guess it's back to that.
I dont want to give yo spoilers...
you can try every rom here, every kernel, every mod...
it really up to your personal use... you do this 3 simple things and like me will reach 5, 6 hours SOT.
disable lte and go for EDGE
restrict privacy guards things on apps: keep awake, auto start, wake up... on every app you install
use your social network on browsers... installed apps use background...
Sup XDA!
When I updated to android 5.1.1 (cm12.1, rooted) android system started to drain my battery, even more than my screen would. This wasn't an issue back on 5.0 and I wonder what the problem is, and I thought you guys could be able to help me out as this forum has helped me before, thx for that!
Ive attached 3 screens, first is from battery monitor and the other 2 are screens of my battery 'page' in settings. Let me know if you need any additional information and or screenshots and I'll be happy to provide.
Thanks in advance
Disable all of the google services you feel that take RAM (and so, battery) using the Disable Service app. Don't disable GCM Service. Don't disable FusedLocation Service if you use GPS. The only google service running on my phone is GCM. Disable location services, key chain, pppreferences, CM logger, dev tools, etc. just anything that you find isn't important and takes battery! Use apps like Greenify, Disable Service and Titanium backup to greenify, disable and freeze the apps/services.
TheHighLife said:
Sup XDA!
When I updated to android 5.1.1 (cm12.1, rooted) android system started to drain my battery, even more than my screen would. This wasn't an issue back on 5.0 and I wonder what the problem is, and I thought you guys could be able to help me out as this forum has helped me before, thx for that!
Ive attached 3 screens, first is from battery monitor and the other 2 are screens of my battery 'page' in settings. Let me know if you need any additional information and or screenshots and I'll be happy to provide.
Thanks in advance
Click to expand...
Click to collapse
This seems to be a common issue.... the fix involves downgrading the modem. However downgrading the modem requires downgrading your TWRP Recovery... which you cannot do if you are running CM12.1, the downgrade will fail every time no matter which "tricks" you use.
lotherius said:
This seems to be a common issue.... the fix involves downgrading the modem. However downgrading the modem requires downgrading your TWRP Recovery... which you cannot do if you are running CM12.1, the downgrade will fail every time no matter which "tricks" you use.
Click to expand...
Click to collapse
You don't need to downgrade TWRP to flash a modem. You can very easily flash a modem without TWRP even installed; fastboot. It isn't even certain that the modem is causing this drain either.
Working on the likely assumption that it is the same problem, the modem is indeed not to blame.
I have moved through COS12.1, CM12.1, sultan, paranoid android, and exodus, with and without flashing the modem and gapps, using both stock and Boeffla kernel.
They all exhibit the same drain, 9-11% overnight or 16-40mA/h (via dumpsys). This is regardless of wifi/cellular/ambient and other features being disabled.
The only obvious anomalies differing from 5.0.2 are high system_server cpu (25-450% via top) when asleep, and intermittent floods of "unknown" wakeups without wakelocks (Observed by dumping batterystats, and are not registered by settings - battery).
On one of my many reflashes Exodus 12.1 suddenly began behaving reasonably, with 6-10mA/h drain and 2% overnight.
The high System_sever cpu and intermittent wakeups were still present at this point, and may be unrelated oddities.
I later made the mistake of flashing a newer nightly (and later the correct modem), upon which the problem reappeared.
Doing a wipe and reflashing in the same manner did not resolve the issue, and many attempts later I have been unable to reproduce the same state.
Coming from kitkat I figured 5.0.2 would be the same, but it has been smooth sailing since flashing it last night (Exodus), with 6-10mA/h drain and 0% overnight.
Roughy said:
Working on the likely assumption that it is the same problem, the modem is indeed not to blame.
I have moved through COS12.1, CM12.1, sultan, paranoid android, and exodus, with and without flashing the modem and gapps, using both stock and Boeffla kernel.
They all exhibit the same drain, 9-11% overnight or 16-40mA/h (via dumpsys). This is regardless of wifi/cellular/ambient and other features being disabled.
The only obvious anomalies differing from 5.0.2 are high system_server cpu (25-450% via top) when asleep, and intermittent floods of "unknown" wakeups without wakelocks (Observed by dumping batterystats, and are not registered by settings - battery).
On one of my many reflashes Exodus 12.1 suddenly began behaving reasonably, with 6-10mA/h drain and 2% overnight.
The high System_sever cpu and intermittent wakeups were still present at this point, and may be unrelated oddities.
I later made the mistake of flashing a newer nightly (and later the correct modem), upon which the problem reappeared.
Doing a wipe and reflashing in the same manner did not resolve the issue, and many attempts later I have been unable to reproduce the same state.
Coming from kitkat I figured 5.0.2 would be the same, but it has been smooth sailing since flashing it last night (Exodus), with 6-10mA/h drain and 0% overnight.
Click to expand...
Click to collapse
So right now you are on the 5.0.2 exodus builds and having minimal battery drain? Which modem are you using?
f41lbl0g said:
So right now you are on the 5.0.2 exodus builds and having minimal battery drain? Which modem are you using?
Click to expand...
Click to collapse
Correct, with the Xposed Mobile Radio Active fix applied.
bacon_firmware_update_2015_04_03.zip from ... <10 posts and am not allowed to post links yet.
It's on Exodus' 5.0.2 download page along with the roms.
As usual the modem will not flash in TWRP, and has to be done manually via fastboot.
Paresh Kalinani said:
Disable all of the google services you feel that take RAM (and so, battery) using the Disable Service app. Don't disable GCM Service. Don't disable FusedLocation Service if you use GPS. The only google service running on my phone is GCM. Disable location services, key chain, pppreferences, CM logger, dev tools, etc. just anything that you find isn't important and takes battery! Use apps like Greenify, Disable Service and Titanium backup to greenify, disable and freeze the apps/services.
Click to expand...
Click to collapse
I did all of this but it's still draining battery, should I post new screenshots?
TheHighLife said:
I did all of this but it's still draining battery, should I post new screenshots?
Click to expand...
Click to collapse
As you have tried many things to improve your battery life, last option I wanna suggest you to use your device in safe mode for one complete charge cycle from 94% down to 5% (I know that this mode is pathetic).
If you still find that it's causing battery drain, you need to reflash the ROM and please do not restore any backup(restore only those which are most important).
If you find that Android system is not causing anymore battery drain, then it's one of the third party app that is doing so.
Mr hOaX said:
As you have tried many things to improve your battery life, last option I wanna suggest you to use your device in safe mode for one complete charge cycle from 94% down to 5% (I know that this mode is pathetic).
If you still find that it's causing battery drain, you need to reflash the ROM and please do not restore any backup(restore only those which are most important).
If you find that Android system is not causing anymore battery drain, then it's one of the third party app that is doing so.
Click to expand...
Click to collapse
Ive only tried to disable some services that show up under android system. How do I put it in safe mode tho?
By the way, I just noticed that the CPU total time for android system is exactly the same time as the SOT, what does this mean? It only drains this much battery when the screen is on?
TheHighLife said:
Ive only tried to disable some services that show up under android system. How do I put it in safe mode tho?
By the way, I just noticed that the CPU total time for android system is exactly the same time as the SOT, what does this mean? It only drains this much battery when the screen is on?
Click to expand...
Click to collapse
Boot your device into safe mode https://support.google.com/nexus/answer/2852139?hl=en
Just post some screenshots of the battery (complete overview of graph screen and app list screen) after using your OPO in safe mode atleast for one charge cycle (90%+ down to 10%)
This will help us to figure out what is the exact issue you are facing.
If you are not interested in troubleshooting, just flash fastboot images of this build(CMOS12.1) using following guide
forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
For OnePlus One, about a month ago after systems update, my battery started draining fats and it has gotten worse over the past week. The battery barely holds four hours of after a full charge and the phone gets very hot. Also, over the past week, my main SMS messaging app (SMS) crashes nine out of 10 times -- I can start the app but when I click any of the messages I was to read or type, it freezes and crashes. Also, since yesterday, my phone dilaer crashes very often. Any thoughts/help? I am not familiar with how to flash ROM, etc. Also, since yesterday, charging has been very slow -- overnight, the charge went from 35% full to 74% full. I tried safe mode as well and no luck -- battery still keeps draining at 1% every three minutes.
I have the same issue. Any fixes which work ?
Hi there,
i was playing around now for some time to expand my battery life in our phone. Maybe some of you know this but i wanted to share my experience which helped me a lot with battery issues.
My main problem was the short standby time. Taking a look into the battery statistics always says my main battery drainers where external applications und the google (play) services. Taking a little more deeper looks says that my main battery drain seemed to be caused in the 'Mobilfunkschnittstelle aktiv' (mobile radio interface active?) entry. I had values of multiple hours here beeing active.
I usually disable the location services because i dont need them. Which can be different for you, of course. Also i usually play around with BetterBatteryStats and Autostarts app for analyzing and disabling various services. This time i skipped this and went across a xposed module in the web.
So, the simple trick for me was to flash xposed with twrp (root needed of course) and install the xposed MobileRadioActiveFix module.
After fixing this i now have a 4 days run time with at least 6 accounts syncing and a weather app and so forth. I didnt have that before on any other device. By the way: i'm not using my phone very often and i don't wont to say: 'i have the biggest', don't want to compete but only suggest giving it a try if you suffer from low standby time.
Regards.
A little PS: some other good xposed modules i'd like to suggest:
- GEL settings: to edit google launcher, eg. removing the google search bar and the homescreen grid
- Battery Percentage Text
are you on lollipop or MM ???
I am on lollipop and I had tried this module a while back it didn't work.
and are you on mobile data or WiFi ???... because with mobile data on ..radio active shows on my battery stats.
what is your SOT now ???
bablu048 said:
are you on lollipop or MM ???
I am on lollipop and I had tried this module a while back it didn't work.
and are you on mobile data or WiFi ???... because with mobile data on ..radio active shows on my battery stats.
what is your SOT now ???
Click to expand...
Click to collapse
lollipop, as the title says
Usually i am on mobile data. And of course there is still some time on radio active in the stats but its way less then before. My first entry in the battery stats where 'google (play) service' with 15% or more. Second was a 'mail client' with 12% and other external apps. This all went better after installing the xposed fix. My first entry now is 'mobile standby'
My SOT is something around 5 hours. Please, dont forget: i really not using my phone very often. My main goal was extending the standby time.
My experience with other devices: depending on the quality of your signal strength your battery can vary heavily. But i guess, thats something you already know. I, btw. have a good 4g signal here.
aVe2000 said:
lollipop, as the title says
Usually i am on mobile data. And of course there is still some time on radio active in the stats but its way less then before. My first entry in the battery stats where 'google (play) service' with 15% or more. Second was a 'mail client' with 12% and other external apps. This all went better after installing the xposed fix. My first entry now is 'mobile standby'
My SOT is something around 5 hours. Please, dont forget: i really not using my phone very often. My main goal was extending the standby time.
Click to expand...
Click to collapse
well cheers, we have the same goal. i used amplify+greenify then i uninstalled exposed and started testing how long i could extend battery on stock and doze+greenify. i have removed maximum google apps and i am constantly getting 1+hour of SOT for every 10% battery. i am on dual sim[one of it is roaming] and i am on mobile data. now i am gonna give exposed another shot, hope radiofix works this time.
'Mobile standby' is a problem i have tried to fix it many times but failed, it eats battery when i am on data which is always, if you find a solution please post it here.
you could disable background data for play services to squeeze more juice out of your battery and about mail app drain i suggest you take a look at F-Droid it's a collection of open source softwares.
aVe2000 said:
Hi there,
i was playing around now for some time to expand my battery life in our phone. Maybe some of you know this but i wanted to share my experience which helped me a lot with battery issues.
My main problem was the short standby time. Taking a look into the battery statistics always says my main battery drainers where external applications und the google (play) services. Taking a little more deeper looks says that my main battery drain seemed to be caused in the 'Mobilfunkschnittstelle aktiv' (mobile radio interface active?) entry. I had values of multiple hours here beeing active.
I usually disable the location services because i dont need them. Which can be different for you, of course. Also i usually play around with BetterBatteryStats and Autostarts app for analyzing and disabling various services. This time i skipped this and went across a xposed module in the web.
So, the simple trick for me was to flash xposed with twrp (root needed of course) and install the xposed MobileRadioActiveFix module.
After fixing this i now have a 4 days run time with at least 6 accounts syncing and a weather app and so forth. I didnt have that before on any other device. By the way: i'm not using my phone very often and i don't wont to say: 'i have the biggest', don't want to compete but only suggest giving it a try if you suffer from low standby time.
Regards.
A little PS: some other good xposed modules i'd like to suggest:
- GEL settings: to edit google launcher, eg. removing the google search bar and the homescreen grid
- Battery Percentage Text
Click to expand...
Click to collapse
But most have already updated to MM. If it works then it's a good thing.
Sent from my XT1562 using Tapatalk
I found that disabling background data for affect apps seemed to help on 5.1, but this limits device experience.
I'm on MM now and usually get all day stand by and about 5 to 6 hours SOT. Today I have 5 hours of voice calls and 2 of SOT and am at 40% battery which isn't bad. Off charge at 5:30 am and it is currently 8:30pm. That's excellent for me. MM is a great update for battery on these phones.
Edit: I meant to say as well that the 5 hours of voice was over a Bluetooth headset. Pretty busy day
K.khiladi said:
But most have already updated to MM. If it works then it's a good thing.
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
I am not sure about this. In europe its still not rolled out (at least not in germany).
aVe2000 said:
please delete
Click to expand...
Click to collapse
Why
you can play with the values of animation in developer options,
Enviado desde mi XT1563 mediante Tapatalk
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------What I have right now out of Doze are "Bluetooth MIDI Service", "Bluetooth Share", the "Clock" app and two other Clock apps.
I am not sure how effective is the method listed below after the last update. Stay tuned.
Also I think the current version of Facebook Messenger is draining too much battery.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Hello everyone,
when I bought my Zenfone 3 ZE520KL, I was amazed by it's battery life. I could easily get around 8 hours of SOT in a single charge with moderate usage. My device was running Android Marshmallow 6.0 out of the box, but performance wasn't as good. On Nougat, performance is much better and faster, also I used to get some lags and frozen screen, the capacitive keys also sometimes froze when I was charging my phone, but now I don't get issues like that as often as before. Interface is so much more appealing and I love it.
But what about battery life? I started getting around 5 hours of SOT.. which is still good, but not really close to 8 hours. I thought a lot about these 3 hours that were missing so I decided to start investigating. I wanted to share my findings with you so maybe you would know something that could help.
It's been two weeks since I have been testing out different things. The apps I used to do my research are:
Carat. What I love about this app is the process list. It shows exactly which apps and system processes are running in the background, so I can control them very easily.
Greenify. Thanks to the Carat app, I can see which apps continue running in the background, so I can use Greenify to hibernate them after I'm done using them. (Examples: Youtube, Snapchat etc.). Also I bought the Donation Package, and unlocked the other modes using adb commands (my device is not rooted).
BetterBatteryStats. This app is usually used to detect wakelocks. I limited the Google Calendar App from syncing so it doesn't use too much battery in the background. This app is paid in Google Play but you can get it for free from here.
What I did to get better battery life:
I excluded the services, that were always running in the process list from the Carat App from Doze. Apparently, the new Doze in Nougat gives us permission to optimize more system processes and services than before, which can backfire - Doze starts trying to kill processes that can't be killed, and this results in consuming more battery juice than saving it.
How to enter Doze settings and make the following changes:
Go to "Settings" > Select "Battery" > Tap on the three dots at the upper-right corner > Select "Battery Optimization" > Select "All Apps" > Find and tap on the Apps/Services/Processes I have listed below > Select "Do not optimize". The other apps and services should stay optimized.
The apps, processes and services that I removed from Doze are:
Android Services Library
Android System
ASUS Calling Screen
Bluetooth MIDI Service
Bluetooth Share
Camera
Clock
com.android.smspush
com.asus.keyboard
com.asus.shim
com.qti.qualcomm.datastatusnotification
com.qualcomm.qti.tetherservice
org.codeaurora.bluetooth
org.codeaurora.ims
com.qualcomm.qcrilsgtunnel
ICESound Service
Mobile Manager
MobileManagerService
System UI
Telecom Service
Telephony Service
ZenUI Keyboard
ZenUI Launcher
Some other apps that I'm using: Do It Later, Greenify, Messages, Nova Launcher, Timely, Weather.
Please do a full charge to 100% afterwards and check if the battery still drains as quickly as before. Your feedback will be greatly appreciated.
I am already starting to see improvement in my battery life. I was losing around 2% on Stand By and battery was draining fast when I was using the phone, but now I lost 0% on Stand By overnight and 10% for 1 hour of SOT (before this I was losing 10% for 30 min. of SOT). I am still trying to figure out which services exactly are causing the drain, when they are being optimized. Maybe the services, included in the Android System? (Check them from Settings > Battery > Android System > Included Packages). I deleted Facebook and Twitter apps and started using them from Chrome (almost the same thing, I quickly got used to that). Please check the updates below for more info and share your opinion or advice in the comments so we can all reach a better experience with this amazing smartphone.
Thank you for reading!
Update1: 6h30min SOT with 30% left (917mAh, 35%), but I will have to charge now. I have been messing with Doze a lot, maybe I'll get more clean results later. Progress has been made though, at least with my device.
Update2: Something interesting - my J-Score with the Carat app before and after starting this experiment: http://i.imgur.com/Q8u6HBD.jpg
Update3: There is a battery drain when making voice calls - 226mAh (7%) were lost because of 43 minutes long talk time.
Results were worse after testing with the second list removed, although there wasn't much draining with the screen on: SOT - 5h20min for 70% of battery (752mAh, 20%).
Update4: com.android.phone appears as a wakelock at BBS (Wakeups:8). Also 2h30 SOT for 30% used battery (100-70%~408 mAh). I'm updating the list and trying again.
Please note that my phone is updated to the latest firmware WW_Phone-14.2020.1703.28-20170410.
Update5: com.android.phone is still an active wakelock (Wakeups:14), but SOT is 2h34min for 30% used battery (100-70%~343mAh). At 30% battery left, SOT is almost 6hrs(28%~787mAh), Device Idle is at 10% (291mAh). The MobileManagerService is causing way too many wakelocks and is probably the reason for the high Device Idle battery usage.
Update6: MobileManagerService is no longer showing as a frequent wakelock. com.android.phone (Telephony Service - Wakeups:9) and com.google.android.apps.messaging are the most persistent wakelocks, other than that battery life is amazing at the moment. SOT is 2h45min for 30% used battery (100-70%~366mAh). I also had 27 min of talk time (4%~145mAh). At 30% left, I have 6h33min of SOT (32%~912mAh). Device Idle is again at 10% (292mAh). We are ready for the final test.
Update7: The results are quite interesting. After removing com.qti.qualcomm.telephonyservice from Doze, com.android.phone stopped appearing as a frequent wakelock at first, but now, at 70% it has 16 wakeups. SOT is 2h22min (100-70%~318mAh), so it's not better. I'm going to try a few more changes.
Update 8: I posted it as a reply here.
Update 9: I shouldn't have put Task Manager out of Doze, I get so much better battery life now. The update is ready, check it here.
Good post, thank you for investigating this, please let us know if you find more stuff or what exactly is responsible for it and an easy way of fixing.
1noob said:
Good post, thank you for investigating this, please let us know if you find more stuff or what exactly is responsible for it and an easy way of fixing.
Click to expand...
Click to collapse
Hello! Thank you for your reply. I'm so happy I could help others and myself with this thread, but I also need to know if you are also seeing any difference. Please check here regularly!
Also, I'm guessing that when you put your system processes and services in Doze, you also decrease their performance, which causes battery draining, as they try to run normally and do their work. Doze is trying to prevent them from doing that. This is my conclusion, but only results will show if I'm correct. If you own yourself a Zenfone 3, please feel free to report if you experience any changes using my method.
Thank you and have a nice day!
Hi, thank you for the post. I have a zenfone 3 here and will try your method.
I'm trying it on ze520kl with marschmallow, it seems working fine. :highfive:
Do you remove the first and second list from doze ? or ate testing with only the second list now?
Nice findings btw
pedromms86 said:
Do you remove the first and second list from doze ? or ate testing with only the second list now?
Nice findings btw
Click to expand...
Click to collapse
I have removed everything from both of the lists. It's still early to say but no major battery drain is noticed for now. Thanks!
bibbomio said:
I'm trying it on ze520kl with marschmallow, it seems working fine. :highfive:
Click to expand...
Click to collapse
Awesome! :good:
Thank you so much for this article. Well written as well. I have applied the changes and so far no issues (it has been 6 h is). Will report once I have more history
I remove the apps from doze, and can say it really improve battery (test for one day)
thanks !
@Blackrose110 any news improvements after update3 ?
New update is released via OTA (~500MB).
pedromms86 said:
@Blackrose110 any news improvements after update3 ?
Click to expand...
Click to collapse
Too early to say, also I got a weird wakelock, and lost 2% overnight. I lost the results (100-90%) after a restart. Now I'm going to update my phone and start again.
I had 8% used up on 43 minutes of SOT, and 2% lost on voice calls (100 and something mAh). I went to bed with 92%, I guess the other 2% were lost on that wakelock and the clock wakelock. These 2% were lost on equal intervals.
It's going to take a while, I'm just using my device normally. I don't have time to be on my phone all the time, also the battery is harder to drain now. At this point, I'm just trying to get better results.
Cheers!
pedromms86 said:
@Blackrose110 any news improvements after update3 ?
Click to expand...
Click to collapse
Check again tomorrow!
RobinRo said:
New update is released via OTA (~500MB).
Click to expand...
Click to collapse
Updating...
I don't think it is a good ideea to change Doze settings for system services like com.qualcomm.* or telephony*.
In theory, these services should be compatible with operating system and they should work as designed. I would focus on third-party apps who doesn't work well on Nougat.
Anyway, is just an opinion and i'm looking forward for updates
ci6i said:
I don't think it is a good ideea to change Doze settings for system services like com.qualcomm.* or telephony*.
In theory, these services should be compatible with operating system and they should work as designed. I would focus on third-party apps who doesn't work well on Nougat.
Anyway, is just an opinion and i'm looking forward for updates
Click to expand...
Click to collapse
Hello ci6i, I also agree with you, and that's why I excluded all of them from Doze when I first tried this out. At the moment, I removed only those system services, that run in the background all the time. My goal is to find the least amount of system services and processes, that are causing battery drain when the phone is in use.
I am not saying that you should do exactly what I did. It's best if you try out yourself on your own device what works and what doesn't.
I also have only excluded from Doze apps that I use daily. But everyone is using different apps and it depends only on the developers to update them.
You can download Carat for free from Google Play and check the process list, it's very useful. The app itself doesn't use any battery.
Good luck!
Blackrose110 said:
...
I am not saying that you should do exactly what I did. It's best if you try out yourself on your own device what works and what doesn't.
I also have only excluded from Doze apps that I use daily. But everyone is using different apps and it depends only on the developers to update them.
...
Click to expand...
Click to collapse
I agree with you and i really appreciate your work Yesterday I've installed Carat after i read your first post and today i did new OTA update and cleared cache partition. Let's see how it works in the next few days.
What should I do next, guys? Remove other com.qualcomm/com.android/com.asus services or remove just MobileManagerService from Doze? I'm thinking about the second one, I'm curious to see if ti makes any difference. I think the results from the first test were the best, and the MobileManagerService was out of Doze as far as I remember. Might as well try and see what happens.
It's a bit hard to drain the battery these days, so updates might not be fast. Patience is key!
Yeahh final test!! Looking forward to the result