Aggressive Doze and Hibernation, App Auto-launch - OnePlus 3 Questions & Answers

Can someone please explain what aggressive doze and hibernation on Open Beta 12 is? How is it different from Doze mode and should I enable or disable it for better battery life?
I don't seem to notice any difference in spite of it being enabled. My phone discharges around 6-8% every night.
Now, regarding App auto-launch, I seem to be losing out on notifications if apps are not white-listed in app auto-launch page. Is this a known issue? Putting more and more apps in white-list is straining my battery and boot time.
Thanks

Related

Deep Sleep app? How to make it work?

Have the h811 and using the app but don't know if it's working. On slumber mode
Which app are you referring too?
The deep sleep battery app? That's the first relevant thing I found in the playstore. And the comments on it don't seem too good.
A lot of folks here will recommend the greenify app instead and picking the apps you want to go into a sleep mode until triggered to wake up.
spartan268 said:
Which app are you referring too?
The deep sleep battery app? That's the first relevant thing I found in the playstore. And the comments on it don't seem too good.
A lot of folks here will recommend the greenify app instead and picking the apps you want to go into a sleep mode until triggered to wake up.
Click to expand...
Click to collapse
Yeah that's what I am referring to the deep sleep battery app, I as well am using greenify with xposed module for deeper sleep
With the screen off, you can just swipe down on the off screen to see the time. You will see that your mobile data is shut off. At least this works for me. I can clearly see my LTE symbol disappearing.
Sent from my LG-H811 using XDA Free mobile app
HeartUnderBlade said:
With the screen off, you can just swipe down on the off screen to see the time. You will see that your mobile data is shut off. At least this works for me. I can clearly see my LTE symbol disappearing.
Sent from my LG-H811 using XDA Free mobile app
Click to expand...
Click to collapse
Have you been noticing difference with using deep sleep battery saver?
wadamean said:
Have you been noticing difference with using deep sleep battery saver?
Click to expand...
Click to collapse
To be honest, I have. I also know that it's working because I swipe down when my screen is off and I see that my mobile data has shut off. Last night, I fell asleep without charging my phone at 67% and woke up to.... 67%, I was asleep for about 6 hours. I came from the Sony Xperia Z2 and kept stamina mode on 24/7. I was able to pull off well over 30 hours with that phone. Using deep sleep battery saver (which was based off the same idea as Stamina mode) I definitely noticed a difference in idle battery. Of course, once you get into any sort of task with the screen on then that's a different story.
The LG G4 already had pretty amazing idle times but I have a lot of apps that loves to wake up the phone when I'm sleeping. Before the app, I noticed that I'd wake up to maybe a 5% drain at minimum over the course of 6~7 hours. Sometimes, when my apps update on their own, I'd notice a significant drop of maybe even 10%.
I paid for the app since it's pretty cheap but honestly, I don't notice any real benefit to having the paid version. The paid version allows you to set some whitelist apps which is what Sony's Stamina mode allowed. However, if you're okay with not having that control then the free version is more than enough. Who knows, maybe some people will benefit less from it :/
I just want to make a point that I am also using it in conjunction with Greenify. I'm not sure if using the two really bears any great benefits but under my impression, greenify hibernates user apps while deep sleep can basically prevent anything from accessing data since it also shuts off mobile data. I can't see how using the two would hurt so why not? It looks like they both do different things that combined would be a very powerful battery saver.
HeartUnderBlade said:
To be honest, I have. I also know that it's working because I swipe down when my screen is off and I see that my mobile data has shut off. Last night, I fell asleep without charging my phone at 67% and woke up to.... 67%, I was asleep for about 6 hours. I came from the Sony Xperia Z2 and kept stamina mode on 24/7. I was able to pull off well over 30 hours with that phone. Using deep sleep battery saver (which was based off the same idea as Stamina mode) I definitely noticed a difference in idle battery. Of course, once you get into any sort of task with the screen on then that's a different story.
The LG G4 already had pretty amazing idle times but I have a lot of apps that loves to wake up the phone when I'm sleeping. Before the app, I noticed that I'd wake up to maybe a 5% drain at minimum over the course of 6~7 hours. Sometimes, when my apps update on their own, I'd notice a significant drop of maybe even 10%.
I paid for the app since it's pretty cheap but honestly, I don't notice any real benefit to having the paid version. The paid version allows you to set some whitelist apps which is what Sony's Stamina mode allowed. However, if you're okay with not having that control then the free version is more than enough. Who knows, maybe some people will benefit less from it :/
I just want to make a point that I am also using it in conjunction with Greenify. I'm not sure if using the two really bears any great benefits but under my impression, greenify hibernates user apps while deep sleep can basically prevent anything from accessing data since it also shuts off mobile data. I can't see how using the two would hurt so why not? It looks like they both do different things that combined would be a very powerful battery saver.
Click to expand...
Click to collapse
I have Greenify as well and my battery life is TERRIBLE on this phone. I am lucky to get 8 hours before going from 100% to under 50%...I have a ton of bloat frozen and a ton of apps Greenified. What system apps are you Greenify'ing? The battery life is killing me on this phone, thank God I got a free battery with the promotion.
pettigrew95 said:
I have Greenify as well and my battery life is TERRIBLE on this phone. I am lucky to get 8 hours before going from 100% to under 50%...I have a ton of bloat frozen and a ton of apps Greenified. What system apps are you Greenify'ing? The battery life is killing me on this phone, thank God I got a free battery with the promotion.
Click to expand...
Click to collapse
I didn't greenify any system apps. I just greenified every single user app that could potentially run while the phone was not in use. I also used tasker to force greenify my facebook app the minute the screen turns off instead of waiting for greenify to activate. I also used kernel adiutor to change the big core's governor to powersave and then changed the LITTLE core's governor to interactive.
Like I said in a previous post, I most use greenify for user apps as I kind of don't want to touch system apps at this moment. I use deep sleep battery saver for anything else that could potentially dodge greenify (like system apps that tries to access data). As all these settings so far are for when the screen is off, the Kernel Adiutor settings are for helping with battery life when the screen is on. I don't think the tasker setting is necessary as it very well could just be a placebo effect but I don't like how facebook isn't hibernated immediately.
So to sum it up; the settings I used:
Greenify all user apps
Use tasker to immediately greenify select apps that are power hungry
Use deep sleep battery saver
Use Kernel Adiutor and set big.LITTLE governors to powersave and interactive
**I should mention that I have the T-mobile H811 model which has an unlocked bootloader with a custom recovery.
HeartUnderBlade said:
I didn't greenify any system apps. I just greenified every single user app that could potentially run while the phone was not in use. I also used tasker to force greenify my facebook app the minute the screen turns off instead of waiting for greenify to activate. I also used kernel adiutor to change the big core's governor to powersave and then changed the LITTLE core's governor to interactive.
Like I said in a previous post, I most use greenify for user apps as I kind of don't want to touch system apps at this moment. I use deep sleep battery saver for anything else that could potentially dodge greenify (like system apps that tries to access data). As all these settings so far are for when the screen is off, the Kernel Adiutor settings are for helping with battery life when the screen is on. I don't think the tasker setting is necessary as it very well could just be a placebo effect but I don't like how facebook isn't hibernated immediately.
So to sum it up; the settings I used:
Greenify all user apps
Use tasker to immediately greenify select apps that are power hungry
Use deep sleep battery saver
Use Kernel Adiutor and set big.LITTLE governors to powersave and interactive
**I should mention that I have the T-mobile H811 model which has an unlocked bootloader with a custom recovery.
Click to expand...
Click to collapse
Awesome, thanks for the informative reply. One question, wouldn't putting the CPU governor on powersave make the phone run really choppy/laggy? Also, I have the Verizon G4 no unlocked bootloader but root.
pettigrew95 said:
Awesome, thanks for the informative reply. One question, wouldn't putting the CPU governor on powersave make the phone run really choppy/laggy? Also, I have the Verizon G4 no unlocked bootloader but root.
Click to expand...
Click to collapse
Most day to day tasks are done with the "LITTLE" cores while intensive tasks are done using the faster "big" so you won't normally notice any lag since the governor for the littles is interactive. I figured the only time I would really drain my battery is when I'm using intense tasks that would utilize the big cores. You will notice a little lag when in really heavy apps like the camera but it's really not that bad - it's not like a "I'm-going-to-miss-my-shot-because-it's-so-laggy" bad. Just give it a shot and you'll see what I mean. I don't use my phone for gaming but I do use it for almost everything else including streaming videos and I don't notice any lag other than in the camera - which, like I said, isn't that bad. If you do want to tweak around with the governor though, I high recommend Kernel Adiutor since it is compatible with the big.LITTLE system (meaning it can set the separate governor for both big and little cores) unlike Rom Toolbox Pro.
While I can bear with the slight lag for the extra battery life, you may not be able to take it. Your mileage may vary I guess. Battery life is much more important to me than high performance since I don't do anything intense like gaming or heavy rendering and I'm always on the go so I'm willing to make that sacrifice.
For me deep sleep has been giving me battery drain issues and uninstalled it after two days of use on slumber and my custom mode that didn't let no app awake and also the force tune cpu and what not yet still battery drain. With it off battery drains much much more less

Any option to force doze during the night?

Is there any way, to force deep sleep/hibernation/intensive doze or anything during night time?
Looking for automatic option to turn it on e.g. from 1am - 6am and disable most of wakelocks, move most processes to lowest power mode.
Currently running CM13 nightlies with EXKernel and with custom options battery seems to be pretty ok (talking about SOT and daily use), but still having like 5-10% overnight drop.
Anyone?
Thanks
5-10% drop over 8 hours says that doze is working well to me.
Sent from my ONEPLUS A3003 using Tapatalk
Well it's not something that is killing my phone experience, but heard of people having 1-2-3% overnight drop.
It's not dissapointing either but having my good'ol Nexus 7 with LTE+sync get like 1% overnight drop is something to look for. Of couse - it's a tablet, has a bigger battery. Just saying
5-10 percent drop is definitely not normal to me. I would install better battery stats and see what's keeping your phone awake.
Also apps like greenify and force doze have aggressive doze options
Use this app called force doze and make sure u don't kill it from task manager
use force doze app and it also have full tasker support so that you can automate force doze on/off on particular time
_______
8-10% drain over 8 hr is not normal.
I am using force doze & my iddle drain for night (11pm-8m) is only 3%

Oreo: Ending music program overnight; disable battery savings on it?

I use the "relax and sleep" android app overnight to sleep, and each night, after several hours, it ends. I think Oreo is ending it, but I don't see how to disable battery savings or optimization on it in Oreo?
Is that what the issue is?
If so, how do I fix that?
H0wdy said:
I use the "relax and sleep" android app overnight to sleep, and each night, after several hours, it ends. I think Oreo is ending it, but I don't see how to disable battery savings or optimization on it in Oreo?
Is that what the issue is?
If so, how do I fix that?
Click to expand...
Click to collapse
Not sure if Battery Optimization is your issue or not. I know I had a similar issue on Nougat with Google Music cutting out in the middle of a 4 mile run and I solved it by setting it to "Not Optimized". From a quick look, it looks like you can tweak app battery optimization settings as follows:
Settings->Apps&Notifications->App Info->Select App->Battery->Battery Optimization->Toggle "All Apps/Not Optimized"->Select App->Toggle Optimize/Don't optimize
Hopefully there is an easier method to get to that Battery Optimization control - but it is the one I found....
Good luck!
Thanks!

Rapid battery drain while screen is off due to this Samsung app. Anyone knows why?

I Googled but could not find anything regarding this app. The battery drains about 1% per hour. I remember it used to be 2% or 3% overnight. Look at the video on hours. I'm gonna disable all of the Bixby related apps using adb and see what happens.
Edit: I disabled it using adb but this thing just came back. If any of you knows, please let me know. TIA.
If you disable Bixby Vision and Bixby Vision Framework the cam will lose functionality. They only run when the came is being used.
Deep six the rest of Bixby though. Enabling stand by apps or other adaptive power saving features can cause excessive battery use.
In Developer options>standby apps all buckets should show as active otherwise some power saving feature is running.
Disable it. On Pie I know it causes conflicts; let Android manage the apps and avoid using all 3rd party power management apps.
Goggle Backup Transport and any cloud services are habitual offenders.
Playstore only needs to be enabled when you need to use it.
You'll need to play with it. Nominal idle current is roughly 140-350 ma average. If much above this something(s) are running in the background. Nominal battery consumption with a plain jane AOD on is about 1%@ hr.
I'm running a 10+ so your numbers will be slightly different.
If the phone is running warm at idle you definitely have some witch hunting to do...

Question Prevent apps from being killed?

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.

Categories

Resources