This post is about getting great battery life for the average, every-day user. It is not inclusive or exhaustive, so it will reference other posts. What is talked about is what I did, the user-level stuff, explained in a more user-friendly fashion than some of the more diagnostic-focused posts out there (still invaluable reading, though).
Note: I originally wrote this for the Hyperdrive ROM on GS4 thread, but I've had many requests to break it out into a separate [GUIDE] post and update it here for ease of subscribing and discussing. Also note, that therefore, this should be considered sort of Android 4.2 specific and may not apply to all versions of Android. So, here it is. I'll link the old post to here shortly.
Preface
Okay, I'm writing this because I believe that @sbreen94 @eschelon @iceandfire @Imoseyon @TrevE and @ktoonsez all have done awesome, awesome dev work from which I have benefited. There are SO many other devs, as well. These are some from whom I directly benefit, regularly, daily, or did at one time. If you want a name added to the list, I'll update my post. This post, though, is sort of Hyperdrive specific since @sbreen94 has added a few tweaks that make it SO EASY to address some major offenders of ... sucking the life out of your battery.
Why do I mention this? Because does anyone truly think that a ROM dev or Kernel dev, compiles code, puts it on their device, runs it for days/weeks, validates it with experienced, community testers, and then releases it, all the time thinking, "well, the battery life sucks, but I'm gonna push this out anyways."??? NO! So, then, WHY does every ROM/Kernel thread have post after post, of people saying “Hey, I loaded this ROM and my battery life sucks now.” Do you REALLY think it's the ROM/Kernel?
We also have those that think they have no apps loaded, or “only 3, 4, 5, or whatever number” - so it can't POSSIBLY be an app! If you think that, then do this, Wipe your Dalvic Cache, reboot your phone, and tell me the number of apps it says Android is now optimizing. That is the number of apps you have on your phone, not the number you personally loaded. That means each one of those is a potential culprit for causing battery drain.
BTW – at one time or another, I've probably been guilty of every of the above mindsets. So, I'm not calling YOU out, if YOU are reading this and think that I am. I'm just saying, it's not the ROM, and it's not the Kernel.
Background Reading
The below two threads had everything I needed to know to get started increasing my battery life. I, probably like many reading this, had for a long time followed along, envious of screenshots of people getting those 3, 4, 5+ hours of screen time, and day+ or days of battery. After reading these threads, doing the analysis, and basically just changing some app settings, I can now get the 4-5 hours of screen and full day of battery out of my GS4. Kernel doesn't have much effect, ROM doesn't have much effect, most all of them do what they're designed to do, and do it well. Sweet.
In the next section, Real World Battery Saving, I'll explain what I did, so if you want to skip the background stuff, you can.
These two threads contain basically everything you need to know about improving battery life. They have great details about diagnostics, what's what, etc. What many threads/posts like these sometimes lack, is, the straight-forward answer of “This is what you should do after analyzing x, y, z.” That's what's in the Real World Battery Saving section of this post.
[APP][2.1+][09 Sept. - V1.14] BetterBatteryStats
[GUIDE] Wakelocks Definition and how to prevent them
Read those threads, and do some analysis, and the majority of what I've posted below you'll figure out on your own. If you just wanna jump into fixing things without the above understanding, then just go to the next section. Provided there aren't any seriously misbehaving apps on your phone, you should be able to get great results without becoming a Wakelocks, Alarms, Deep Sleep, etc., expert.
Real World Battery Saving
For those of you that don't want to read too much more about the analysis of apps, etc., to get to better battery life, here's the summary of what's in the section below:
Minimize screen brightness
Disable all Push
Disable all system sounds (Dialing keypad tone, Touch sounds, Screen lock sound, Haptic feedback)
Install Xposed Framework and use:
Greenify Donation (Experimental features)
NLPUnbounce
Greenify any app that you don’t need to notify you of things - Note: If you pay for Greenify Donation and use Xposed, you can still get alerts from any GCM-enabled app (look for the blue GCM icon next to apps in Greenify)
Greenify every Google app (except Voice and Hangouts, both of these may significantly delay or prevent proper message notification, despite being GCM-tagged in Greenify, and they seem to behave okay on their own)
Uninstall GMail (use any other client with IMAP)
Disable all GPS (enable as necessary upon use) Note: I really don't do this anymore. With apps under control with Greenify, I just leave my GPS on and let apps use it when necessary. I have noticed that GPS will stay active during Airplane mode, though, so as not to have my phone dead upon landing, I generally always turn off GPS when in the air.
Disable the autostart of almost everything, at almost any time, on an app-by-app basis. AutoStart Check delivers in spades for this function, at no charge, though, I recommend donating (as I do for all apps here, I have either donated or bought them all, Lux, Greenify, etc.). Note: With Greenify, I no longer worry as much about stopping apps/services from auto-starting. I do still use Xposed plugin BootManager to prevent certain apps from starting, mostly just to increase boot speed (or so I feel like it might). I don't use AutoStart Check at all anymore.
Continuing on with details...
Note: Required app functionality. You don't have to use these if you know another way to do it. But, to accomplish what I recommend, there are 3 key apps you absolutely must have. I'm not going to explain them all in great detail, as there are plenty of other places that go into great depth on all of them. The 3 essential apps that I use to increase battery by more than 50% are:
Lux (Pro - I'll explain why below)
Greenify
Xposed Framework
In general:
You want your phone to sleep when not in use.
You want apps to not be doing anything when you're not using them.
You want your screen to only ever be as bright as it needs to be, no brighter (including, off when you're not looking at it).
Display Brightness
Lux – Get it here Lux Auto Brightness
Thread here: [APP][2.3+] Lux Auto Brightness 1.51
Update: After posting this, and getting a lot of questions/comments that Lux doesn't really rock like I think it does, I checked it out on a phone without using the Pro version. Okay, I agree, the free version really doesn't deliver. It doesn't poll right, and you can't really set your custom lighting scenarios and lock them in correctly without using Lux Pro. Basically, if you want to save tons of battery life without a lot of constant manual intervention, you're going to have to purchase Lux.
Screen uses more battery than anything. You can do all kinds of things to address this, for me, Lux has been a (battery) life saver. It's easy, it reads the ambient light in your environment. Open its dashboard, slide the slider to the brightness that works for you at that lumen level, hold down the link button in the middle, and there you have it, locked in for those conditions. You only have to do this a few times and you now have custom lighting profiles that fit your eyes' needs under all conditions. Note, sometimes, when waking the phone in the sun, you'll have to wait a few second for Lux to activate and bring the screen up bright enough. This means that Lux is behaving extremely well and not constantly running in the background (Wakelocks) sucking up battery.
Applications
For applications, firstly, if you have an app that has Push available, disable it. Nothing keeps your phone from deep sleep like a Push-enabled application. If you can't wait 5/10/15 minutes for updates, then you can't achieve maximum battery life. Sorry, I don't make the rules of Android app-physics, I'm just sharing them with you.
In my mind, I think of applications in categories. I guess, I have 4 now.. I started with 2. Point being, there are different apps that behave differently so you treat them differently with different solutions for extending your battery life.
Category 1 Apps I want running and want notifications from them. When configured properly, they generally do not misbehave and eat my phone's battery
Category 2 Apps that I cannot seem to control, regardless of their settings, but I still want to be able to use, but getting regular or instant updates from them is not that important to me
Category 3 Apps behave without any special settings and without any Greenification. Just load them, run them, use them, don't worry about them. I haven't seen them cause any sort of bad battery drain.
Category 4 Apps are apps you DO think are vital/desirable (to you) but cannot control their battery consumption with mere settings. For those, only the developer can help you, or you have to accept the battery loss that app's notifications bring with it.
Category 1 apps, well-behaved when configured properly, along with the settings I used to make them behave well and still deliver their updates to me.
Corporate E-mail: Built-in e-mail, TW or AOSP. Disable Push for any account, use Priority settings for 15 minute interval on work days. Non-prioirty times set to 1 hour.
Maildroid: For every account, you must do this separately, under Preferences / Advanced – Connection Management, select first account, the rule (usually 1. Default), Connection Management, Wi-Fi: Close connection when I exit mailbox, GPRS, 3G: Close connection when I exit mailbox, Interval to check mail: 10 (or to your liking), Check Mail Periodically. Go back, go back in (confirm settings were kept, I've seen it not keep them and have to do this a few times, per account). Alternatively, select Let device sleep, and it will only check when you wake it up. Go back to Accounts and select your next account, do this again. You must do this for all accounts listed.
Note about all mail client: If you have more than 2 or 3 e-mail accounts, Maildroid and all other IMAP clients I have tried get moved to Category 2. Basically, they start to keep enough Wakelocks that they keep the phone from going into Deep Sleep as much as I'd like. This is a difference of 1-3% per hour at idle, but if you're looking for 4+ hours screen time, then you need to Greenify them and just check e-mail manually.
Viber: Just make sure your Wi-Fi sleep policy is set to device and not constantly on, and Viber seems to behave pretty well as far as messaging apps go, but it's probably going to make the Category 4 list, as well.
WhatsApp: This one appears to work well (better than Viber from a wakeup perspective) and not have any sort of unnecessary battery drain. I generally don't use it any more since I feel they bait-and-switched me from free to fee, but I dethawed it to check it out. If anyone sees problems with it, let me know.
Category 2 Apps. These apps were keeping my phone awake at night with nightmares, and no amount of settings changes seemed to fix the problem altogether. If you have a solution of app settings that would move these to Category 1, please let me know. When I say solution, I mean, you've done the Wakelock and Alarm analysis and they're eliminated or minimized. For these, I Greenify them all. None of these apps' updates are so important to me that I can't just check up on them when I have a moment.
Facebook: I didn't play too much with settings here, but it seems that if FB is running, it's keeping your phone awake. I Greenify it and check it manually. I'd be interested in hearing if someone knows settings that will get it to not wakelock / alarm constantly.
FB Messenger: I love the chat heads and ease of use, but it's a big-time battery offender. I keep it installed and Greenified. If I get messages, I'll see them when I open the FB app, and when I reply, FB Messenger takes over and I use it normally until the conversation is done. At some point, Greenify takes over, and FB Messenger's battery damage is contained.
Google Maps: You can't fix this thing. No amount of settings will stop it from going after your phone. I love its functionality, though, so, unlike many guides that say uninstall it, I say Greenify it.
Google Goggles: A fun one to have around sometimes, but it will also chew up battery. Just Greenify it.
Google Play Store: There are plenty of apps and Android wakeups for the Play Store. I'm not worried about missing an update notification, or whatever else it might be sending my way. Greenifying it seems to have fixed the Google Play Services Alarms issue.
Almost everything else: If it's an app that doesn't need to provide you updates, just Greenify it. Why not? One of the first things I do after loading a new ROM and getting most of the configuration stuff done, is I go into Greenify, and I add every mundane app on my phone, for example: Vonage, Adobe Reader, Airbnb, Angry Birds, APN Manager Pro, Google Authenticator, Barcode Scanner, Citibank, Craigslist, Google Drive, DroidVPN, ES Task Manager, Fast Charge, FasterGPS, Flashlight, GasBuddy, GNotes, GooManager, GPS Status, Hyatt, Lucky Patcher, Office Document Viewer, Office Suite, OpenTable, Opera Classic, PayByPhone, SoundHound, Squeezebox, Street View, etc. My list goes on... You aren't going to lose their functionality, they don't suddenly stop when in use, and you don't have to worry about them ever causing problems you weren't thinking you had to look for.
Category 3 Apps that behave, no special settings, no Greenification
Alarm Clock Xtreme: I don't use the built-in Alarm Clock. I like all the features of Xtreme, it's never failed me, and it doesn't show up in Wakelock/Alarm offenders lists in my analyses.
Google Voice: Of all the Google offenders, this isn't one of them in my experience, and I love its features.
Lux: Nuff said.
WhosCall: A caller-ID type app. I don't love it, but haven't gone looking for something better, that said, it hasn't popped up on my battery draining radar, so that's a plus.
Hangouts: While I don't care for the new Google Talk, it sure doesn't seem to be a battery offender, and I use it to chat regularly.
Category 4 Apps are anything that would have gone into Category 2, but you want them as active as possible.
Line: In Settings, Chats and Voice Calls, I turn off Receive Voice Calls. This made Line tolerable (as in, way better), but it's still a Category 4 until (if ever) its devs reduce its number of wake-up Alarms
Exchange Services: Despite Corporate E-mail being a Category 1 now, Exchange Services is still keeping my phone awake more than I'd like. Nothing I can do here, though, so I live with it.
Viber: As stated, it's not a terrible offender, but it's still on the radar for keeping my phone awake. We'll see what their “any day now” major update brings. (someone remind me to update this post if I haven't post-Viber release)
Have Your Google and Your Battery
The Xposed module NLPUnbounce is awesome. I've given it a nice test, and it seems to perform excellent. NLPUnbounce allows you to use Google services as usual, including Android Device Manager features, like Remote Locate and Remote Wipe, but not do the crazy, crippling and disabling of Google Play Services like many guides have you do. It changes the polling rate of NLP (Network Location Provider) to something VERY reasonable. I haven't modified any of its settings, and it's reduced average idle consumption from ~4-5% to ~2-3%. I tested locating my phone and ringing it, all working.
Automatically Launching Applications
Not so much needed anymore. Just make sure you Greenify. For the "big things", use Xposed BootManager module.
AutoStart Check - Get it here https://play.google.com/store/apps/details?id=ro.rbrtoanna.autostartcheck&hl=en
Fire up AutoStart Check (or any other autostart configuration app), set your view to Group by App, and expand every one of them and look at just how many different places some of these apps are set to start. Your Gallery starts with your Camera? ES File Explorer starts when you mount media or remove bad media? Facebook fires itself up just because you plugged in your phone. Google Goggles sees fit to start with every picture you take - and of course, it will then either drain your battery trying to get a GPS signal while your GPS is off, or drain your battery by getting one – fail. If you use S Health, it starts when your time zone changes – that's important. YouTube, seriously, YouTube – change accounts, mount media, connect power, every boot – you obviously need YouTube to fire up. Yeah.
A note here, read some guides on these before turning off too many system services. For example, don't disable messaging, bad idea, bad things happen. But most of this stuff, turn it off. You aren't killing your ability to use it, you're just making sure it isn't turning on all the time. If you've also Greenified well, after using any of these, they'll hibernate in the background without you having to worry.
Disable all system sounds (Dialing keypad tone, Touch sounds, Screen lock sound, Haptic feedback)
This is explained in some of the other threads, but, if you don't want to do the research, basically, the background services in Android that manage these things keep your phone awake. Turn them all off, battery life goes up.
Media Scanner
@sbreen94 included in the Hyperdrive Tweaks tools a one-button solution to turning it off. If it's drainging your battery, or you just want to make sure it doesn't, go click the button. This thing is better than the Staples button!
I'm sure there's probably a more generic way of stopping/managing Media Scanner. Someone please let me know and I'll update this section!
Battery Save Apps
I used to be madly in love with 2x Battery. Others swear by JuiceDefender. I guess if you don't/won't want to take the time to optimize apps and Greenify, they might be beneficial. You know what I found, though, when I started down this path? Some of the biggest offenders of Wakelocks and keeping my phone from sleeping when it should, are these battery saving apps!!! I now get BETTER battery life WITHOUT 2x Battery!
Short thoughts on this and example concepts of what's going on...
It may sound counterinterintuitive, but it seems most of the apps are so vigilant they keep your phone awake when it could be sleeping. And the vigilance isn't so necessary when you've properly configure things to not need this sort of overactive management of things. I'd love to see 2x Battery properly manage my data connection for me, without Wakelocks, but what's to say that the app trying to sync when the data is off won't now stay awake with new Wakelocks trying to get out to the internet? There's a cascading effect of whatever approach you might choose, so try to think about that, and keep it in mind when you look at your Wakelocks and your Alarms and you do your analysis.
The End
Okay, so I think that's aobut it. I may have forgotten some things, and I know this is a long post. But, this leaves very little excuse for people to blame ROMs/Kernels, while at the same time giving you the straight-forward, real world answer to battery savings 101. Yes, there are apps and details I left out. If anyone thinks of some obvoius ones, just let me know and I'll happily update this post.
You don't have to analyze any statistics or logs to do this. The principles are sound, and you'll see a dramatic improvement in battery if you don't already get a day of usage and 3.5 to 4.5 hours of screen time on your GS4. You just make some of these relatively straight-foward, user-level, common-sense changes.
If these changes don't give you the results you'd like, then do the analysis work in the threads linked above and find out what's the real culprit. Profit, enjoy, be happy. And remember... It's not the ROM.
Thanks for the thread, Bill. Here are a few of my questions/comments:
Regarding Lux, I used it for a few days, but could never seem to get a setting that worked for me. Whether using periodic updating or any of the other modes, the brightness level always seemed to adjust either too frequently or too slowly. Then I started experimenting with night mode and it got even worse. Do you have any suggestions to a quick and simple setup that won't drive me insane?
In terms of greenifying different apps, I always make sure that my SMS app and alarm clock are not greenified, and I don't use any widgets on my homescreen, but what about apps like Better Battery Stats, Boot Manager (for Xposed) and Automagic (flow chart based automation app) that are monitoring events and automating my phone? Will Battery Stats stop recording data is I set it to hibernate? Will Automagic miss a trigger I've set if it's hibernating? I would like to greenify EVERYTHING that I know won't cause any issues, but notifications aren't the only thing happening in the background that I want to allow.
Then, expanding on the autostarts, I mentioned that I use the Xposed module Boot Manager. This doesn't seem able to handle all of the situations that you described, like apps being launched based on SD card state, network state, etc. Am I missing something in this app or will I need to go another route to get all the options you've descibed?
Regarding the SD media scanning, my current ROM is a very debloated lean and mean stock Touchwiz ROM that doesn't have a native way to disable media scanner like the AOSP ROMs I used to run. Is there an app that does ONLY this, as I prefer to use dedicated apps rather than giant monsters which can control tons of things I don't need.
Anyway, I already do a lot of the practices you're advocating here, but I'm always looking for ways to do things in a more efficient or streamlined way. Using Greenify, keeping the stock clock speeds, and making sure that nothing is syncing (I keep backgruond sync disabled, but use an Automagic flow to enable it periodically throughout the day and then turn it back off again), keeps my battery life pretty solid. Add to that Deep Sleep Battery Saver which automatically turns off my connections when the screen is off, but will periodically turn them back based on my preferences, keeps my battery level pretty much steady wheen the phone is idle.
Hello guys
I have an old pronlem -- all the gapps I have tried(slim, pico, delta) are eating too much at all the roms ive used(purity, sultan, orion os, aosparadox, exodus)
Even amplify does not help.
What can you reccomend?
To be precise, its Google Play Services that's eating away at your battery, the recent updates have increased this threshold even more so, I'm pretty blank on how to tackle this, maybe someone else can help.
Joshwin Aranha said:
To be precise, its Google Play Services that's eating away at your battery, the recent updates have increased this threshold even more so, I'm pretty blank on how to tackle this, maybe someone else can help.
Click to expand...
Click to collapse
Well, I have tried almost everything and I can't blame anyone except google for this. Peculiar thing about this is that it happens on mobile data, almost never on wifi. Mobile Radio is active half of the times. You will see google play services, gmail, google app and other google apps in battery stat.
What I have tried so far: amplify, greenify, all possible location combo, blocking alarms, wakelocks, wiping google play services, google accounts, blocking permission to google apps. Most of these things broke functionality .
Solution: Just ignore. There are various threads on google forums,xda and not even a single working solution. If someone finds it, I am keen to try that (unless it asks for my credit card).
saurabh40629 said:
Well, I have tried almost everything and I can't blame anyone except google for this. Peculiar thing about this is that it happens on mobile data, almost never on wifi. Mobile Radio is active half of the times. You will see google play services, gmail, google app and other google apps in battery stat.
What I have tried so far: amplify, greenify, all possible location combo, blocking alarms, wakelocks, wiping google play services, google accounts, blocking permission to google apps. Most of these things broke functionality .
Solution: Just ignore. There are various threads on google forums,xda and not even a single working solution. If someone finds it, I am keen to try that (unless it asks for my credit card).
Click to expand...
Click to collapse
Well the thing is, Google Play Services (GPS from here on out), handles literally everything that Google Apps do on your device, from Geo-Positioning (Maps) to Sync (SyncAdapter) to Emails (Gmail/Exchange) to everything. To put in view, apps that crash on our devices, give a pop up, saying "XYZ apps has stopped working" and gives us 2 options "OK" & "Report", now if you "Report" the error, you'd think the report (and device logs!) go to the developer of the app, Yes ? NO! These are sent to the Almighty Overlords at Google, aside from the data-mining issue here, this just astonished me beyond belief. So that being said, what my personal view is, Google is, like every new Android Iteration, upgrading the old apps to use the Android N-ish architecture & stuff, and maybe, just maybe that this new stuff that's being implemented is better off in Android N, and not in LP or MM. But then again, I might be horribly wrong about all of this
Joshwin Aranha said:
Well the thing is, Google Play Services (GPS from here on out), handles literally everything that Google Apps do on your device, from Geo-Positioning (Maps) to Sync (SyncAdapter) to Emails (Gmail/Exchange) to everything. To put in view, apps that crash on our devices, give a pop up, saying "XYZ apps has stopped working" and gives us 2 options "OK" & "Report", now if you "Report" the error, you'd think the report (and device logs!) go to the developer of the app, Yes ? NO! These are sent to the Almighty Overlords at Google, aside from the data-mining issue here, this just astonished me beyond belief. So that being said, what my personal view is, Google is, like every new Android Iteration, upgrading the old apps to use the Android N-ish architecture & stuff, and maybe, just maybe that this new stuff that's being implemented is better off in Android N, and not in LP or MM. But then again, I might be horribly wrong about all of this
Click to expand...
Click to collapse
Though you are right about first half (can't say much about later part, as I don't understand why it should make google services go crazy )
This problem traces back to Kitkat and probably jell bean but only thing which I do not understand is why only in mobile data ?? I don't see any of them popping up in wifi .
Just when I thought I could ignore it, it started non stop feast on mobile data. I had to stop background data for this. Damn you google.
try A-gapps, it allows battery optimization for google play services (open-gapps etc don't allow this)
it helped me to have less battery drain by google play services
http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606
Yeah... Mine are pretty obese too
Hi,
when using aggressive doze on a rooted Nexus 4 with Android 6.0.1 in my GPS tracking app (I tried several), even though whitelisted, the tracking stops after a few minutes.
The apps still show as tracking thus I suspect the GPS itself gets killed and provides no signal/values anymore.
Is it a bug or a feature?
Thanks for the great work
DarsVaeda said:
Hi,
when using aggressive doze on a rooted Nexus 4 with Android 6.0.1 in my GPS tracking app (I tried several), even though whitelisted, the tracking stops after a few minutes.
The apps still show as tracking thus I suspect the GPS itself gets killed and provides no signal/values anymore.
Is it a bug or a feature?
Thanks for the great work
Click to expand...
Click to collapse
Uninstall Greenify and check.
If I disable aggressive doze it works.
If I uninstall the app too of course.
This is a limitation of the doze mode itself enforced by Android. I'm afraid there's no way to workaround that.
A new Tasker plug-in is added in 2.9.5 beta 1 to toggle Aggressive Doze. Hope this could do some help here.
Ah no problem, I thought it might be something like this. I'll just disable aggressive doze while using the app.
The tasker plugin would do this automatically for me, did I get this right?
oasisfeng said:
This is a limitation of the doze mode itself enforced by Android. I'm afraid there's no way to workaround that.
A new Tasker plug-in is added in 2.9.5 beta 1 to toggle Aggressive Doze. Hope this could do some help here.
Click to expand...
Click to collapse
Shouldn't it be enough to disable "Doze on the go" to maintain the gps sensor on?
I have this same problem, and the only way to allow a foreground sports tracking app to access the gps data is to disable both "Agressive doze" and "Doze on the go"...
daniel.mota said:
Shouldn't it be enough to disable "Doze on the go" to maintain the gps sensor on?
I have this same problem, and the only way to allow a foreground sports tracking app to access the gps data is to disable both "Agressive doze" and "Doze on the go"...
Click to expand...
Click to collapse
No. As someone tested before, the stock Doze also disables GPS.
Hello,
I had the same behaviour. I tested something this morning : added to whitelist my navigation app + LocationServices + FusedLocation.
And while I was on the road, the gps worked till I arrived. In the agressive doze log I see that the device did'nt went in Doze during that time.
Don't know if this is directly related, I'll give it another try tonight.
Didn't work tonight, lost gps signal. Something else prevented doze this morning.
Will give a try to the beta and the toggle.
Any news on the subject? I get GPS signal lost while using maps...
RFrancis said:
Any news on the subject? I get GPS signal lost while using maps...
Click to expand...
Click to collapse
I'm now using the beta + Tasker to prevent doze when my navigation apps are on. Works great.
madxxcow said:
I'm now using the beta + Tasker to prevent doze when my navigation apps are on. Works great.
Click to expand...
Click to collapse
Could you export the profile
Here is an example for Google Maps.
madxxcow said:
Here is an example for Google Maps.
Click to expand...
Click to collapse
You should probably re-enable aggressive doze with an exit task. This does not seem to be one of those system settings that will auto restore when the task terminates. Also note that this profile will not trigger if Maps or your GPS app is in the background. I am debating whether aggressive doze is worth the hassle.
I've been having the same issue for a while. I use Locus Maps to record tracks on airplanes (so it may run for 12hrs) and it turns off GPS. Sometimes its hard to tell if its lost because of Doze or I simply lost the signal.
Also, it is plugged into a power source (charging) so I believe Doze should be disabled while charging.
I see above mention of "Tasker". What is this?
eng3 said:
I've been having the same issue for a while. I use Locus Maps to record tracks on airplanes (so it may run for 12hrs) and it turns off GPS. Sometimes its hard to tell if its lost because of Doze or I simply lost the signal.
Also, it is plugged into a power source (charging) so I believe Doze should be disabled while charging.
I see above mention of "Tasker". What is this?
Click to expand...
Click to collapse
The simple solution is to avoid aggressive doze which is tagged 'experimental' and is known to cause some odd device/radio/app behaviors.
Davey126 said:
The simple solution is to avoid aggressive doze which is tagged 'experimental' and is known to cause some odd device/radio/app behaviors.
Click to expand...
Click to collapse
I'm sorry, I should have clarified. I was broadening to Doze itself as I thought I read that it will also disable GPS (but not as fast or "aggressively").
My behavior has been a little different. I notice that if I run maps navigation at the same time as recording my track, there is no issue. but if I just record my track, then it not be able to prevent GPS from stopping.
Perhaps this should go in another forum, I'm just not sure which
eng3 said:
I'm sorry, I should have clarified. I was broadening to Doze itself as I thought I read that it will also disable GPS (but not as fast or "aggressively").
My behavior has been a little different. I notice that if I run maps navigation at the same time as recording my track, there is no issue. but if I just record my track, then it not be able to prevent GPS from stopping.
Perhaps this should go in another forum, I'm just not sure which
Click to expand...
Click to collapse
Try running a GPS Status app (example) concurrent with your tracking app. Aside from helping to keep the GPS 'awake' most have a variety of useful features and functionality.
I have tried that but it does not seem to work. I'll have to check the GPS status options to see if there's something for keeping it awake.
I have noticed that if I run Navigation (not just Maps) in parallel, then the GPS will stay awake.
eng3 said:
I have tried that but it does not seem to work. I'll have to check the GPS status options to see if there's something for keeping it awake.
I have noticed that if I run Navigation (not just Maps) in parallel, then the GPS will stay awake.
Click to expand...
Click to collapse
- as previously noted make sure Aggressive Doze is disabled as it can break cross-app/component communications
- also add you tracker app to 'white list' of you haven't done so already
- good chance Google Maps (any navigation app) is using wakelocks to keep GPS active
- assume all is well when you disable Greenify
- if true you many need to step away from Greenify or consider another app with similar functionality like Force Doze
Hi all,
I did not have this enabled but the standing advice seems to be that it has to be enabled. What does this do exactly?
Loving the app though keep up the good work!
Jeroen1000 said:
Hi all,
I did not have this enabled but the standing advice seems to be that it has to be enabled. What does this do exactly?
Loving the app though keep up the good work!
Click to expand...
Click to collapse
Not needed except w/unrooted device to facilitate screen off operations.
Davey126 said:
Not needed except w/unrooted device to facilitate screen off operations.
Click to expand...
Click to collapse
Thanks Davey126. There was an option in Greenify once to ensure compatibility with finger print readers. It was called "alternative screen off mode". I hoped this option got dubbed the Automator now but it doesn't look that way judging from your reply. I can't find it any more (maybe it got removed for some reason?). Sometimes the fingerprint reader on my OPO5T is a bit slow. I need to lift and touch it twice to get an unlock. Maybe I need to whitelist ...something as I have "Greenify system apps" checked. Amongst the optimised apps is "GFManager" which has a fingerprint icon.
At any rate, do you know what happened to "alternative screen off mode" option?
Jeroen1000 said:
Thanks Davey126. There was an option in Greenify once to ensure compatibility with finger print readers. It was called "alternative screen off mode". I hoped this option got dubbed the Automator now but it doesn't look that way judging from your reply. I can't find it any more (maybe it got removed for some reason?). Sometimes the fingerprint reader on my OPO5T is a bit slow. I need to lift and touch it twice to get an unlock. Maybe I need to whitelist ...something as I have "Greenify system apps" checked. Amongst the optimised apps is "GFManager" which has a fingerprint icon.
At any rate, do you know what happened to "alternative screen off mode" option?
Click to expand...
Click to collapse
Don't know but removal is likely referenced (somewhere) in a change log or forum post. XDA search is your friend.
As for the fingerprint recognition issue why is "GFManager" and likely other benign system apps in Greenify's overt hibernation list? Only demonstrated 'bad actors' should be there; ideally the list will be quite small gravitating to zero.
Do you take 23 aspirin in the morning for the hell of it to protect yourself from some pain that has never materialized? Over greenification (new word!) is just asking for trouble.
Davey126 said:
Don't know but removal is likely referenced (somewhere) in a change log or forum post. XDA search is your friend.
As for the fingerprint recognition issue why is "GFManager" and likely other benign system apps in Greenify's overt hibernation list? Only demonstrated 'bad actors' should be there; ideally the list will be quite small gravitating to zero.
Do you take 23 aspirin in the morning for the hell of it to protect yourself from some pain that has never materialized? Over greenification (new word!) is just asking for trouble.
Click to expand...
Click to collapse
I didn't put GFManager in the Doze optimising list manually. It could just be the management app (judging by its name) for fingerprints for all I know not the actual code that does the detection. I just blame Apple for just having 2% drain per 8 hours idle and then some of us wanting that on an Android phone.
Jeroen1000 said:
I didn't put GFManager in the Doze optimising list manually. It could just be the management app (judging by its name) for fingerprints for all I know not the actual code that does the detection. I just blame Apple for just having 2% drain per 8 hours idle and then some of us wanting that on an Android phone.
Click to expand...
Click to collapse
Android battery optimization (Android 6+) is different from explicitly adding items to Greenify's hibernation list (which I assumed you were doing as some [incorrectly] use the terms interchangeably). Most likely the intermittent touch recognition hesitation you are experiencing is not related to GFManager being "optimized" but rather the time it takes the device to arise from a deep slumber. Are you using Aggressive Doze by chance?
iOS and Android can both idle efficiently on appropriate hardware. I typically see 0.2-0.5%/hr idle drain on my various devices depending on conditions. Apple has the advantage as it controls both hardware and software. Android must accommodate a wide variety of hardware platforms (including crappy kernels) many of which are not well optimized for power savings.
Davey126 said:
Android battery optimization (Android 6+) is different from explicitly adding items to Greenify's hibernation list (which I assumed you were doing as some [incorrectly] use the terms interchangeably). Most likely the intermittent touch recognition hesitation you are experiencing is not related to GFManager being "optimized" but rather the time it takes the device to arise from a deep slumber. Are you using Aggressive Doze by chance?
iOS and Android can both idle efficiently on appropriate hardware. I typically see 0.2-0.5%/hr idle drain on my various devices depending on conditions. Apple has the advantage as it controls both hardware and software. Android must accommodate a wide variety of hardware platforms (including crappy kernels) many of which are not well optimized for power savings.
Click to expand...
Click to collapse
Yes, I am using aggressive doze. Via the whitelist you can access in Greenify, it seems almost everything gets Optimised (dozed).
I would assume the fingerprint scanner would be exempt from doze but the non-optimised apps list doesn't have anything in it that I can connect to the reader. I would likewise assume I'd have to look for something like com.qualcomm... instead of looking for an actual app name. I could use a tip as to what I'm looking for...
So to be clear, I did not add stuff to the hibernation list manually with regards to the fingerprint reader. Just some stuff that by far has nothing to do with it.
For full disclosure: Via a Magisk module, my Google Play Services also get dozed. It is called "Enable Doze for GMS Magisk Module".
a bit off topic:
I can get an idle drain around 0.5% and using HEBF optimiser's "Improve Battery" switch this goes down to 0.4%. What are you doing to get even lower? I'm betting turning off WIFI and nuking play services entirely?
Jeroen1000 said:
Yes, I am using aggressive doze. Via the whitelist you can access in Greenify, it seems almost everything gets Optimised (dozed).
I would assume the fingerprint scanner would be exempt from doze but the non-optimised apps list doesn't have anything in it that I can connect to the reader. I would likewise assume I'd have to look for something like com.qualcomm... instead of looking for an actual app name. I could use a tip as to what I'm looking for...
So to be clear, I did not add stuff to the hibernation list manually with regards to the fingerprint reader. Just some stuff that by far has nothing to do with it.
For full disclosure: Via a Magisk module, my Google Play Services also get dozed. It is called "Enable Doze for GMS Magisk Module".
Click to expand...
Click to collapse
Again, doze and hibernation are different things. I would expect every user app and virtually every system app (with exception to Google Play Services) to be 'battery optimized'. Observations:
- analysis begins with disabling referenced Magisk module as Google Play Services is deeply intertwined with most apps and services (system and user)
- disable aggressive doze; putting your device into a comma isn't helpful when trying to diagnose a responsiveness issue
- multiple deferred tasks often fire-up immediately when exiting aggressive doze temporarily overwhelming device and introducing lag
- nothing should be in Greenify's active hibernation list except apps/services that are demonstrated offenders
Pretty good chance you have created the problem you are trying to solve my over managing your device.
Jeroen1000 said:
a bit off topic:
I can get an idle drain around 0.5% and using HEBF optimiser's "Improve Battery" switch this goes down to 0.4%. What are you doing to get even lower? I'm betting turning off WIFI and nuking play services entirely?
Click to expand...
Click to collapse
Nope. Stock ROM (rooted/unlocked); stock Google Play Services, WiFi and mobile radios on 7x24, location services generally on and set to 'high accuracy', BT and NFC cycled as needed, other than Greenify no 3rd party 'power saving' tools in play. Full believer in lite-touch management with results to back-up religion on multiple devices. YMMV. Choose your apps wisely.
Thanks for the tips. I'll revert my changes one by one and see what turns up. Don't want to loose aggressive doze though... I will report back if I find the culprit.
I understand the difference between doze and hibernation. I was just trying to point out it's not me putting stuff manually on the hibernation list. And yes, I support your observation, using too many apps trying to get even lower drain often works counterproductive. Same goes for apps monitoring battery stats. They too use up some juice.
Jeroen1000 said:
Thanks for the tips. I'll revert my changes one by one and see what turns up. Don't want to loose aggressive doze though... I will report back if I find the culprit.
Click to expand...
Click to collapse
Suggest a reconsideration of position on aggressive doze. While the glossy looks great measurable benefits don't always offset liabilities. With AD active device will likely show reduced drain during extended screen-off operations. A win, right? Possibly - until you factor in higher drain rates as the device races to catch up after exiting doze which is often triggered by an overt wake request (ie: using your device). Several minutes of high CPU utilization at max (and often power inefficient) frequencies can wipe out hours of slow savings while introducing lag and other undesirable side effects. You should disable AD for a few days to see if it improves your situation.
As an aside, brief sprints at high CPU frequencies are not necessarily evil as finishing a task quickly and returning to idle (see "race to idle") can be more efficient than drawing it out over an extended period of time at lower frequencies. That said, servicing multiple tasks over several minutes when the device first wakes is often less efficient than allowing them to complete 'naturally' when the screen goes off (which is why doze doesn't kick in immediately) and/or during normal doze maintenance windows.
Aggressive doze can be beneficial in certain circumstances - but those are few and far between (at least based on my personal work flows and observation of others).