What exactly does that feature do on an individual app? Security apps like cerberus recommend not using it.
Sent from my Nexus 5X using Tapatalk
Hi
km8j said:
What exactly does that feature do on an individual app? Security apps like cerberus recommend not using it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
During Doze mode (this kicks in when you've not moved or used the phone for a period of time, such as overnight when it's left alone) stops apps from waking the phone or running background tasks, the idea being if the phone isn't being used, it's a waste of power for apps to keep going off on line chattering or receiving notifications and displaying them to the user. Notifications that you might have got immediately, don't ping through until you press the power button the next morning.
I suspect security apps like Cerberus don't want to partake in Doze mode as they want to wake your phone up every few hours regardless and scan it, or be able to download new signatures any time.
Despite setting an app to not be optimised, it still gets stop from waking the phone using alarms during Doze (alarms are something an app can set to say wake the phone up and run the app every 10 minutes or on the hour etc). However the developer of the app can work around this by setting a new type of alarm, for Google this work around is easily detected and it wouldn't surprise me if they start alerting on the Play store about apps that are potential battery drains because they by-pass Doze. Of course some apps have to, for example an alarm clock to wake you in the morning, or something like Tasker that you set to run things at specific times, so it will be up to the developer to explain why and the person downloading to make a decision about it.
Regards
Phil
Hi
PhilipL said:
However the developer of the app can work around this by setting a new type of alarm, for Google this work around is easily detected and it wouldn't surprise me if they start alerting on the Play store about apps that are potential battery drains because they by-pass Doze. Of course some apps have to, for example an alarm clock to wake you in the morning, or something like Tasker that you set to run things at specific times, so it will be up to the developer to explain why and the person downloading to make a decision about it.
Click to expand...
Click to collapse
That was my post in October, this happened to Tasker: http://www.androidpolice.com/2015/1...y-reasons-this-time-its-the-notorious-tasker/
It seems Google has perhaps pulled the plug on Tasker a bit too quickly due to a BETA version, but I think overall this approach is good for Android if it gets rid of battery draining apps, which usually are up to no good downloading ads or sending back data for marketing reasons. Obviously some apps are the exception to this like Tasker, which will need this exception to continue working correctly, as otherwise it will be restricted to one wake-up every 15 minutes only when the phone goes into doze mode.
Regards
Phil
PhilipL said:
Hi
That was my post in October, this happened to Tasker: http://www.androidpolice.com/2015/1...y-reasons-this-time-its-the-notorious-tasker/
It seems Google has perhaps pulled the plug on Tasker a bit too quickly due to a BETA version, but I think overall this approach is good for Android if it gets rid of battery draining apps, which usually are up to no good downloading ads or sending back data for marketing reasons. Obviously some apps are the exception to this like Tasker, which will need this exception to continue working correctly, as otherwise it will be restricted to one wake-up every 15 minutes only when the phone goes into doze mode.
Regards
Phil
Click to expand...
Click to collapse
Interesting reading. The question is why they even allow apps to use permission for ignoring doze, whe it most liley means ban in Play Store. Should be available to system apps only.
Note: Google Play policies prohibit apps from requesting
direct exemption from Power Management features in Android 6.0+ (Doze and App
Standby) unless the core function of the app is adversely affected.
Click to expand...
Click to collapse
Now the question is what authority can JUDGE whether certain app needs it or not.
Guys, it looks like my doze feature does not do a good job. What do you guys think I can do to improve it. I don't have any facebook app or snapchat only bluetooth is on and wifi . Under battery stats only OS services are listed and lookout 1%. Any suggestions?
Which services do you have running in the background? Those would be the usual suspects. In Android 6.0 you can see them in Developer Options > Running Services.
bblzd said:
Which services do you have running in the background? Those would be the usual suspects. In Android 6.0 you can see them in Developer Options > Running Services.
Click to expand...
Click to collapse
under battery stats I had Bluetooth, android os, android system, google services, phone idle and lookout. I have bunch more in the developer menu. Should I start uninstalling some of them? looks like google goggles , gas buddy, rocket player, light manager, swiftkey , battery saver have been running for a while.
erikmarko said:
under battery stats I had Bluetooth, android os, android system, google services, phone idle and lookout. I have bunch more in the developer menu. Should I start uninstalling some of them? looks like google goggles , gas buddy, rocket player, light manager, swiftkey , battery saver have been running for a while.
Click to expand...
Click to collapse
Anything that runs in the background as a service can wake the phone during Doze. Some of them might not be necessary and can be closed, but just swiping certain apps away doesn't always mean they close if they choose to run as a service.
Process of elimination would be a good way to determine which might be causing issues. Sometimes there's a setting within the app (notification manager, etc.) that allows it to run in the background and that can be disabled without removing the app entirely. This is especially true for games that like to notify you of random events.
Another way to see what has been eating RAM and processes recently is the Settings > Memory tab. Last 3 hours (set to max usage instead of average) is often surprising to see how many apps chose to do some background stuff despite me never even using them in days.
Hello
By following many, many XDA forums, downloading/ buying apps, trial and error, advice, ect. I think I may have a solution to the battery drain some of us experience with our devices. I feel confident my process applies to most phones running Nougat.
*This procedure will also cover most Android devices running 6.0 and up.
This guide is on the assumption you are rooted, and removed all bloatware. But may help some for the non-rooted idk.
*Create a Nandroid backup...Reboot.
*Delete any battery saving apps/ task killers/ antivirus apps.
1. Disable Wi-Fi. (You can re-enable later) Personally, I leave it disabled until needed.
2. Clear data in Google Play Services, Google Maps, and Google Play Store.
3. Go to Settings> Power> Battery Optimization> Reset App Preferences...Reboot.
4. In Settings, turn off Body Sensors, Bluetooth, Vibration, Location, Auto Sync, disable 'Backup and Reset'. (You can enable later)
5. Delete/ disable all apps you do not use. Less apps means less background operations while idle, a good thing. Delete Facebook/ Instagram/ Twitter apps, Viber, Whatsapp, and any other known battery hogs. (You can download again them later)...Reboot.
6. Follow this link. Thanks @MeggaMortY !!! The link cuts down some of the wakelock/ chatter/ cpu usage during idle.
https://forum.xda-developers.com/oneplus-3/how-to/guide-stop-google-play-services-t3549760
Follow the steps he has provided. I personally used MyAndroid Tools Pro for disabling Services and Broadcasts.
Next...
*Download App Ops from PlayStore. Open App Opps, and scroll down to Google Play Services. Select 'Prevent Phone from Sleeping' -Select 'Ignore'...Exit App Ops.
*Download Greenify from Play Store.
Using Greenify settings, select:
1. Shallow Hibernation, and Automated Hibernation.
2. Greenify System Apps (Requires Donation Package)...Exit Greenify.
*Download ForceDoze from Play Store.
*Personally, I use ForceDoze. (Try using your personal doze app if you wish).
In ForceDoze settings select:
1. 'Turn off ForceDoze While Charging'.
2. 'Ignore Lockscreen Timeout'.
3. 'Disable Wi-Fi during Doze'.
4. 'Doze delay '0' seconds'.
5. 'Disable Motion Sensing...Exit ForceDoze'.
*Return to phone settings, go to Power> Battery Optimization> All Apps list. Select ForceDoze, Greenify, App Ops, MyandroidTools, (Or whatever app you used to disable your services) as 'Do Not Optimize'.
Reboot to recovery (Also assuming you are using TWRP).
Select 'Advanced Wipe'.
Wipe 'Dalvik/Art Cache' and 'Cache'...Reboot.
Charge to 100%.
Remove charger. Let idle for 6+ hours minimum let to your battery monitor (BBB or GSAM, ect) have a good look. You can trim the excess fat afterwards...Then slowly add your social/ email/ sports/ weather/music apps. I would suggest you use your browser instead for these things. (Less battery stress during idle).
I also keep sync off, and manually sync, and only use Wi-Fi / Location/ Bluetooth when needed. (Optional, but saves battery)
**After you see your improvement, feel free to try out the device settings/ apps that balance functionality with battery savings!
*Mileage may vary depending on how many apps/ settings you have enabled (smartwatch, Facebook, ect. The less apps/ settings running, the better).
Sorry for the length. but I wanted to make this easy to follow.
Hopefully, this at least reduces some of the drain. Let me know.
fossils-n-dents said:
Hello
By following many, many XDA forums, downloading/ buying apps, trial and error, advice, ect. I think I may have a solution to the battery drain some of us experience with our devices. I feel confident my process applies to most phones running Nougat.
This guide is on the assumption you are rooted. But may help some for the non-rooted idk.
*Create a Nandroid backup...Reboot.
*Delete any battery saving apps/ task killers/ antivirus apps.
1. Disable Wi-Fi. (You can re-enable later) Personally, I leave it disabled until needed.
2. Clear data in Google Play Services, Google Maps, and Google Play Store.
3. Go to Settings> Power> Battery Optimization> Reset App Preferences...Reboot.
4. In Settings, turn off Body Sensors, Bluetooth, Location, Auto Sync, Disable Backup and Reset (You can enable later)
5. Delete/ disable app you do not use. Less apps means less background operations while idle, a good thing. Delete Facebook/ Instagram/ Twitter apps, and any known battery hog. (You can download again them later)...Reboot.
6. Follow this link. Thanks MeggaMortY !!! The link cuts down some of the chatter/ cpu usage during idle.
https://forum.xda-developers.com/oneplus-3/how-to/guide-stop-google-play-services-t3549760
Follow the steps he has provided. I personally used MyAndroid Tools Pro for disabling Services and Broadcasts.
*Download App Ops from PlayStore. scroll down to Google Play Services. Select 'Prevent Phone from Sleeping'...Exit App Ops
Using Greenify settings, select:
1. Shallow Hibernation, and Automated Hibernation.
2. Greenify System Apps (Requires Donation Package)...Exit Greenify.
*Personally, I use ForceDoze. (Try using your personal doze app if you wish).
In ForceDoze settings select:
1. Turn off ForceDoze While Charging.
2. Ignore Lockscreen Timeout.
3. Disable Wi-Fi during Doze.
4. Doze delay '0' seconds.
5. Disable Motion Sensing...Exit ForceDoze.
*Return to settings, go to Power> Battery Optimization> All Apps list. Select ForceDoze, Greenify, App Ops, MyandroidTools, or whatever app you used to disable services as 'Do Not Optimize'.
Reboot to recovery (Also assuming you are using TWRP).
Select 'Advanced Wipe'.
Wipe 'Dalvik/Art Cache' and 'Cache'...Reboot.
Charge to 100%.
Remove charger. Let idle for 4 hours minimum. (You can peek in an hour, but you gotta start over).
Milage may vary depending on how many apps you have installed. The less the better.
Hopefully, this at least reduces some of the drain. Let me know.
Click to expand...
Click to collapse
Will this work on other phones? I have an s7 edge
orlans21 said:
Will this work on other phones? I have an s7 edge
Click to expand...
Click to collapse
It should. This should apply for Android devices in general. Make a backup, give it a try.
fossils-n-dents said:
It should. This should apply for Android devices in general. Make a backup, give it a try.
Click to expand...
Click to collapse
Not rooted and don't have twrp
orlans21 said:
Not rooted and don't have twrp
Click to expand...
Click to collapse
I would suggest all the steps except the cache wipes in TWRP. Remove Whatsapp, Facebook, Twitter, ect. Disable google Now, Google Drive, Google Photos, (You can connect them later).
You want the minimum of apps interfacing with Google Play Services/ Android system during your first idle run.
fossils-n-dents said:
I would suggest all the steps except the cache wipes in TWRP. Remove Whatsapp, Facebook, Twitter, ect. Disable google Now, Google Drive, Google Photos, (You can connect them later).
You want the minimum of apps interfacing with Google Play Services/ Android system during your first idle run.
Click to expand...
Click to collapse
I already have google drive, photos, whatsapp, Facebook disabled. Google now I'm not opted in if that's alright. I can still do the cache wipes in stock recovery as well. I do use the official twitter app and 3rd party twitter apps.
orlans21 said:
I already have google drive, photos, whatsapp, Facebook disabled. Google now I'm not opted in if that's alright. I can still do the cache wipes in stock recovery as well. I do use the official twitter app and 3rd party twitter apps.
Click to expand...
Click to collapse
Give it a go with what you have installed. Preferable if you disable the Twitter apps, and re-enable them later.
Hopefully, you will see a better idle time.
fossils-n-dents said:
Give it a go with what you have installed. Preferable if you disable the Twitter apps, and re-enable them later.
Hopefully, you will see a better idle time.
Click to expand...
Click to collapse
Well just to show you what I've been getting I did a factory reset last week because I was getting annoyed by this and these are what I got. I wasn't happy with them.
orlans21 said:
Well just to show you what I've been getting I did a factory reset last week because I was getting annoyed by this and these are what I got. I wasn't happy with them.
Click to expand...
Click to collapse
My personal experiences taught me Google Play services is not broken, nor is Android OS. It's the inefficient way that apps send/ receive data, take constant analytics, perform background tasks, pushing notifications, ect. Then, Google Play services must tend to these apps, plus do it's own tasks, send/ receive data, analytics, and Android OS tries to keep it all together.
(It reminds me of Windows 10 high cpu/ disk usage while idle before I hardened it from Microsoft servers as best I could).
All of those processes hammer away at your cpu, and kill your battery while you sleep a little at a time. Or a lot.
I have no idea how to read a Logcat, and this will probably be seen as overkill to some, but my results speak for themselves.
Try it. You can always download apps after you see your result. Good Luck.
fossils-n-dents said:
My personal experiences taught me Google Play services is not broken, nor is Android OS. It's the inefficient way that apps send/ receive data, take constant analytics, perform background tasks, pushing notifications, ect. Then, Google Play services must tend to these apps, plus do it's own tasks, send/ receive data, analytics, and Android OS tries to keep it all together.
(It reminds me of Windows 10 high cpu/ disk usage while idle before I hardened it from Microsoft servers as best I could).
All of those processes hammer away at your cpu, and kill your battery while you sleep a little at a time. Or a lot.
I have no idea how to read a Logcat, and this will probably be seen as overkill to some, but my results speak for themselves.
Try it. You can always download apps after you see your result. Good Luck.
Click to expand...
Click to collapse
Would you like to pm me so we can go through this process step by step?
orlans21 said:
Would you like to pm me so we can go through this process step by step?
Click to expand...
Click to collapse
I sent PM 5 times. It says I have 0 sent messages. Will try again
fossils-n-dents said:
I sent PM 5 times. It says I have 0 sent messages. Will try again
Click to expand...
Click to collapse
I don't think whatever we did worked. I think its the rooted process that fixes it
fossils-n-dents said:
Hello
Using Greenify settings, select:
1. Shallow Hibernation, and Automated Hibernation.
2. Greenify System Apps (Requires Donation Package)...Exit Greenify.
*Personally, I use ForceDoze. (Try using your personal doze app if you wish).
In ForceDoze settings select:
1. Turn off ForceDoze While Charging.
2. Ignore Lockscreen Timeout.
3. Disable Wi-Fi during Doze.
4. Doze delay '0' seconds.
5. Disable Motion Sensing...Exit ForceDoze.
.
Click to expand...
Click to collapse
are you using both greenify and forcedoze together???
timytimy said:
are you using both greenify and forcedoze together???
Click to expand...
Click to collapse
Yes.
fossils-n-dents said:
I sent PM 5 times. It says I have 0 sent messages. Will try again
Click to expand...
Click to collapse
Here are the results for the 2nd test. What is up with that Samsung accessory alarm? Pm me when you see this. Whoops accidentally upload the wrong picture
Here you go.
Results from last night idle test. I wanna know what all those android alarms are.
orlans21 said:
Results from last night idle test. I wanna know what all those android alarms are.
Click to expand...
Click to collapse
I would guess to say Samsung apps, Notification pushes, scanning for updates, ect. This looks like the behavior of Android dealing with multiple apps sending/ receiving data (Anaylitics, polling, crash reports, ect) causing the wakeups. My way (Unscientific) is to delete/ disable them all, and add them one by one, until you notice this behavior again. (Takes days of installing, and many idle runs).
Or, you could post the BBS idle dump (At least 6 hours idle) on the XDA Better Battery Stats forum, and let one of the guys take a look. They will tell you the offending app/ process far quicker.
But, at 1.0 drain per hour, you may be on the verge of 0.8-0.5 per hour idle drain (Or better). Wi-FI off will do even better. Simply engage Wi-Fi when you need it.
If you can, make a backup of your current setup, if something goes wrong, you can always revert back to it and start over.
Everything else looks great for a non-rooted device.
fossils-n-dents said:
I would guess to say Samsung apps, Notification pushes, scanning for updates, ect. This looks like the behavior of Android dealing with multiple apps sending/ receiving data (Anaylitics, polling, crash reports, ect) causing the wakeups. My way (Unscientific) is to delete/ disable them all, and add them one by one, until you notice this behavior again. (Takes days of installing, and many idle runs).
Or, you could post the BBS idle dump (At least 6 hours idle) on the XDA Better Battery Stats forum, and let one of the guys take a look. They will tell you the offending app/ process far quicker.
But, at 1.0 drain per hour, you may be on the verge of 0.8-0.5 per hour idle drain (Or better). Wi-FI off will do even better. Simply engage Wi-Fi when you need it.
If you can, make a backup of your current setup, if something goes wrong, you can always revert back to it and start over.
Everything else looks great for a non-rooted device.
Click to expand...
Click to collapse
How would i be able to get the BBS idle dump? is wifi off and having data on overnight a better option in terms of minimizing battery drain? I also know i have scanning for updates off since i deny that all the time
orlans21 said:
How would i be able to get the BBS idle dump? is wifi off and having data on overnight a better option in terms of minimizing battery drain? I also know i have scanning for updates off since i deny that all the time
Click to expand...
Click to collapse
Click where the circle is, You will see 'Share Data As'...Dumpfile should be checked by default. Click save.
It will be stored a the root of your memory card, or root of internal storage (Phone). I cannot remember which.
Access the dumpfile by plugging USB to computer. It will be a *txt* file. It should be visible as soon as you access storage. Then copy the dumpfile to your desktop, and upload to XDA BBS forum.
For me, drain is slower as I don't have any processes for Wi-Fi running at all in the background. You should try both ways to compare what is best for you. (Yes, yet another idle run).
Turning off 'Scanning for Wi-Fi' is good. Shutting Wi-Fi off completely is better. All those little processes add up. The less processes running, the better.
You should really practice the 6 hour idle runs, as more process come to the forefront in longer runs. Sometimes, extra idle drain from processes kick in after 3-1/2 hours. I used to get 0% idle drain in the first 3 hours, Then android would go nuts. LockerMaster app was the culprit. Got rid of it.
I am testing a faulty app that it's being faulty during deep sleep, therefore to fasten testing I would need an app which can force the phone to enter deep sleep mode immediately.
Any idea?
Macrodroid or Tasker maybe
Sent from my SM-N986U1 using Tapatalk
Hello
look for an app called napptime it may help you.
Jay
j1978 said:
Hello
look for an app called napptime it may help you.
Jay
Click to expand...
Click to collapse
As he said naptime is the better option for this?
Thanks guys!
Try disabling all power management apps ie all the toggles in Device Care are toggled off except fast charging.
Do not enable sleep for any; Developer options>stand by apps, all buckets should show as active if not power management is active.
Close apps when done with them especially ones like Brave.
The phone will automatically go into a deep sleep state at screen off unless a 3rd party apk is misbehaving.
On my 10+ running on Pie this is how it runs best and gets the best battery life.
Goggle Play Services, Gmail, Playstore, Google Backup Transport, Google Framework and Samsung cloud backup are prime offenders*.
Disable these and all Google, Samsung, carrier and apk feedback. I use Karma Firewall to find rogue apks and lock the phone down as well as a package blocker.
I also use Battery Tracker from the Galaxy Store.
Nominal battery usage is 7-10%@hour heavy usage like vids and surfing. Off screen usage with AOD on is 1%@hour.
*enable when and as needed
Try Naptime and what blackhawk says!
TheViciousGames said:
Try Naptime and what blackhawk says!
Click to expand...
Click to collapse
You'll need to play with it; what works with my configuration may not work for others.
These are my current observations. My stock AT&T 10+ variant is heavy modified and watched over. As I intend to continue to use the current Pie firmware, I continue to tweak it.
What I've observed though over the last year to my dismay is any power management interferes with functionality sometimes randomly and unpredictably. It actually ends up increasing battery usage within a few days although initially it may seem to improve it.
Apparently it causes system conflicts.
I have no power management active other than the screen is set to "optimize" in Device Care and even Device Care is package blocked then unless I wish to use it to clear the cache (which the factory load version does very well).
I toggle Google Play Services/Gmail on as needed and a few other battery hogs. Point is I know their status; no random shutdowns or apk failures... and the best battery life I've ever seen on this device.
You need to go explore, find the resource hogs one by one and find a way to tone them down.
All the shotgun get it done power management apks failed miserably for myself multiple times....
Android runs very well by its self once your rein in a couple problem apks.
Many times the factory loaded versions run better then their updated versions. Gmail, Gmaps, Device Care... may or may not be true on your load; trust nothing!
ReeX said:
I am testing a faulty app that it's being faulty during deep sleep, therefore to fasten testing I would need an app which can force the phone to enter deep sleep mode immediately.
Any idea?
Click to expand...
Click to collapse
Naptime
for me, forcedoze was the best, you can download apk
blackhawk said:
Try disabling all power management apps ie all the toggles in Device Care are toggled off except fast charging.
Do not enable sleep for any; Developer options>stand by apps, all buckets should show as active if not power management is active.
Close apps when done with them especially ones like Brave.
The phone will automatically go into a deep sleep state at screen off unless a 3rd party apk is misbehaving.
On my 10+ running on Pie this is how it runs best and gets the best battery life.
Goggle Play Services, Gmail, Playstore, Google Backup Transport, Google Framework and Samsung cloud backup are prime offenders*.
Disable these and all Google, Samsung, carrier and apk feedback. I use Karma Firewall to find rogue apks and lock the phone down as well as a package blocker.
I also use Battery Tracker from the Galaxy Store.
Nominal battery usage is 7-10%@hour heavy usage like vids and surfing. Off screen usage with AOD on is 1%@hour.
*enable when and as needed
Click to expand...
Click to collapse
When I go into standby mode in developers options each app has 3 options. Frequent, rate, working set. What should I put them on?
Also what exactly does standby mode do? Is it manually disabling that app while not in use or only when you close it? As far as closing the apps, will closing them via the recent apps screen suffice or do I need to force close them?
And my last question is what do you mean by disabling an app such as play services?
Sent from my SM-N986U1 using Tapatalk
TheViciousGames said:
Try Naptime and what blackhawk says!
Click to expand...
Click to collapse
yungzoe0624 said:
When I go into standby mode in developers options each app has 3 options. Frequent, rate, working set. What should I put them on?
Also what exactly does standby mode do? Is it manually disabling that app while not in use or only when you close it? As far as closing the apps, will closing them via the recent apps screen suffice or do I need to force close them?
And my last question is what do you mean by disabling an app such as play services?
Sent from my SM-N986U1 using Tapatalk
Click to expand...
Click to collapse
It shows the app's bucket state when power management is enabled.
Your power management is enabled... and likely wasting battery even though it's suppose to do the opposite. If power management is disabled as I suggested, all buckets are locked to active.
Right now I have GPS enabled; I disable Device Health Services com as it was constantly accessing the internet.
Usually closing the app is all that's needed.
Use Karma Firewall and Battery Tracker to help ferret out bad apps.
Depending on your model, OS/firmware load, 3rd party apks and settings configuration your system may respond differently.
I have heavily modified them on this 10+ Pie variant; it's an ongoing process. I have around 88 apks packaged disabled as well.
Androids wuv to be played with...
Is there a way to prevent an app from ever being killed? I have 2 examples:
1) Fitbit app (background sync service, specifically) - when this stops running, some features on my watch quit working until I launch the app and sync manually.
2) Battery monitor app - I've tried AccuBattery (my preferred app), GSam, and BBS, but they all get killed and restart, and therefore give inaccurate information. BBS doesn't die as often as the others, but I don't like it as well. All 3 have persistent notifications, so I can tell when they last restarted.
I've set Battery Optimization to "Don't Optimize" for all of these. I've tried turning off all 3 of the settings under Advanced Optimization (probably unnecessary, no noticeable difference). I've also Locked each of these from recent apps. Are there any other settings I'm missing that could prevent an app from being killed? Possibly something new to Android 11? Fitbit and AccuBattery worked fine on my previous OP7P with Android 10.
terlynn4 said:
Is there a way to prevent an app from ever being killed? I have 2 examples:
1) Fitbit app (background sync service, specifically) - when this stops running, some features on my watch quit working until I launch the app and sync manually.
2) Battery monitor app - I've tried AccuBattery (my preferred app), GSam, and BBS, but they all get killed and restart, and therefore give inaccurate information. BBS doesn't die as often as the others, but I don't like it as well. All 3 have persistent notifications, so I can tell when they last restarted.
I've set Battery Optimization to "Don't Optimize" for all of these. I've tried turning off all 3 of the settings under Advanced Optimization (probably unnecessary, no noticeable difference). I've also Locked each of these from recent apps. Are there any other settings I'm missing that could prevent an app from being killed? Possibly something new to Android 11? Fitbit and AccuBattery worked fine on my previous OP7P with Android 10.
Click to expand...
Click to collapse
I have try to to go to developer mode and go to standby application. go inside and set the app you want to always on to active and remember still set battery to don't Optimize and locked the app. Do not click the clear all button.
fifasax said:
I have try to to go to developer mode and go to standby application. go inside and set the app you want to always on to active and remember still set battery to don't Optimize and locked the app. Do not click the clear all button.
Click to expand...
Click to collapse
Interesting, I haven't seen that before. Thanks for introducing me to something new. All of the apps in question are currently grayed out and say Exempted, so they shouldn't ever be put into standby.
Disable all power management*, Android does fine without it. Address any remaining power hogs individually on a case by case basis.
Power management will cause erratic behavior and can even increase battery usage even after its lame "adjustment" period.
To check if it is fully disabled go to Developer options>Standby apps, all buckets should show to be in their active state (and can't be manually assigned), if not power management is enabled.
Make sure allow background usage isn't disabled on the apps you want to run.
*yeah turn all those optimizing toggles OFF.
Only fast charging should be toggled on if you use it.
blackhawk said:
Disable all power management*, Android does fine without it. Address any remaining power hogs individually on a case by case basis.
Power management will cause erratic behavior and can even increase battery usage even after its lame "adjustment" period.
To check if it is fully disabled go to Developer options>Standby apps, all buckets should show to be in their active state (and can't be manually assigned), if not power management is enabled.
Make sure allow background usage isn't disabled on the apps you want to run.
*yeah turn all those optimizing toggles OFF.
Only fast charging should be toggled on if you use it.
Click to expand...
Click to collapse
How does one disable all power management? I don't see any sort of global switch for that. Turning it off entirely seems drastic, but I agree that power management is generally more trouble than it's worth.
I did verify that the apps in question are allowed to run in the background and use unlimited data.
terlynn4 said:
How does one disable all power management? I don't see any sort of global switch for that. Turning it off entirely seems drastic, but I agree that power management is generally more trouble than it's worth.
I did verify that the apps in question are allowed to run in the background and use unlimited data.
Click to expand...
Click to collapse
It seems like you're setting up right. Check the Stand by apps status.
When you first load Accubattery it gives an option to disable task killing in settings, Pro version.
Uninstalling then reinstalling it sometimes works for me; clearing its data does not. I was getting the same error message until I just reinstalled it
Just don't take Accubattery too seriously... it's useful up to a point.
I'm on Pie. Google really screwed up 10 and especially 11... so yeah it could something new as Google insists on changing things even if they're already nearly perfect
If that fails check with Accubattery for guidance with 11. They are responsive to emails.
They may also be punching out an update.