Hello everyone, I put a small tutorial to maximize the battery life of our Oneplus 9. As I describe, I have my unit configured.
If you want you can go reporting in the thread what results your terminal now show you with this configuration.
Greetings.
1.- DEACTIVATE AUTOMATIC UPDATES.
In this way we will avoid that the mobile is constantly looking for updates and therefore consuming battery.
1.1- We go to the Play Store and in Settings / General / Automatically update applications, we mark "do not update applications automatically".
1.2- Once this is done, we go to the Oxygen OS updates. We follow the path Settings / System / System Updates, we give the little wheel that is at the top right and deactivate “Automatic download in Wifi”.
2.- DEACTIVATE THE WIFI ASSISTANT.
This option allows the mobile to automatically change the network, without us having to be aware of it, but it uses the battery unnecessarily. We are going to configure it to do it manually.
We follow the route Settings / Wifi and Mobile Networks / Wifi / Wifi Preferences / Inside we go and deactivate “Select the best Wifi network intelligently”.
3.-DEACTIVATE THE PRINTING SERVICES.
We have these services to connect to printers active all the time and the phone will be constantly looking for printers so that we can connect.
We go to Settings / Bluetooth and device connection / Printing / Default printing services, when pressing it it opens, once inside we deactivate it, we will see that on the screen below, we have a red bar with a text that says "searching for printers" This way we prevent it from being in constant search.
4.- DEACTIVATE EXPERIENCE IMPROVEMENT PROGRAMS.
We follow the route Settings / System / Experience improvement programs and deactivate the four options:
“Oneplus Notifications”, “User Experience Program” and “System Stability Program” and “Embedded Application Update”.
5.- BATTERY OPTIMIZATION.
We follow the route Adjustment / Battery / Battery optimization. Click on the three dots on the top right and Advanced Optimization will appear. Once inside we will activate the three options that we find, "Activate adaptive battery", "Optimization of standby at rest" and "Optimize energy consumption of applications".
6.- OPTIMIZATION OF THE GOOGLE ACCOUNT.
We go to Settings, select Accounts and inside we go to the Google account and open it, once inside we choose "Synchronization", we deactivate the following options:
Google Fit data / People data / Drive / Google Play Movies / Save Play Games in the cloud / Tasks in Calendar.
If you use any of these options, don´t deactivate it or if you don´t use any of the others, deactivate it.
7.- OTHER ADJUSTMENTS.
In addition to the above settings I also have the following:
Screen, dark mode, manual brightness at 85-90%, touch sounds, screen lock sounds, capture sounds, keyboard sounds, all off, vibration off.
In Developer Options:
"Registry Buffer Size", I have it set to 1Mb.
Window Animation Level / Transitions Animation Level / Transitions Duration Level. All three are by default at 1x, I lowered all three to 0.5x.
Hi, just some quick notes:
- the search for new version of apps doesn't stop with the process you mentioned, the auto download and install process will, and in a few days or weeks you will still be forced to update to the new version as the old one won't work. Overall good option to have.
- the printing service uses a negligible amount of power and I think it even does that when you are in it, and it's idle when not using, but I might be wrong (I use it so I won't turn it off)
- be careful with battery optimisation, Oneplus already is quite known for killing apps and then you aren't getting any notifications from these (happens to my WhatsApp all the time until I remember to add it to the ignore list and for some reason it doesn't like SwiftKey as it always says its draining battery even if I use it for typing).
- point 7 has a lot in. First, your MAIN battery drainer, ask anyone, is your screen, that's why they do all these "screen on" tests, and auto brightness will use a small amount of power to have the sensor on, but it will save you much more while decreasing your brightness from 85% when not needed. The power to make the touch sound etc is so, so small it's neglected (even Nokia 3310 would last a week with them on). Registry bigger size (you mean logger?) is an option how long the buffer is, either way those messages are being recorded and sent, I doubt it makes a difference. Don't fully understand how decreasing the animation speed will save battery, probably you don't have to wait the other millisecond for the animation to finish when you do something and finish sooner what you wanted to do and then turn the screen off?
Sorry, it might seem I am really mean here, and I am sorry if it seems that way, but some don't make sense, specially the brightness. You can uninstall unused apps or use adb to disable them but your radios (like turning off 5G if not used or WiFi when not used) and your screen uses 90% of the battery. Also check your app permissions, specially GPS as that is a real hog too so if an app gets your location in the background that takes a lot
Thanks for answering.
Regarding the first, at no time do I say that the process of searching for updates stops, we stop it from installing them without us noticing, so we decide whether to update or not.
Regarding stopping the printing service, spend little or spend a lot, it uses battery. That is why it is not a single point, there are several, among all they drain the battery. If it continues to consume battery even if we deactivate it, the problem would already be Oneplus that would be lying to us and in settings it would not be giving us options even if it says so, I do not think Oneplus does that.
Point 5 is Battery optimization, it may be that Oneplus kills the applications, that is already up to each one, I try to obtain a lower battery consumption but maintaining logical use options of a smartphone. Neither in the Oneplus 8T, nor in the Oneplus 8 Pro, nor in the Oneplus 9 I have noticed that when activating this the phone kills the applications in a drastic way.
Regarding point 7 I know that the battery brightness consumes a lot of battery, more brightness more consumption. Even so I do not like to put it automatic because it does not fit my needs correctly, I like to put it with a brightness of 85-90% because where I live there are many hours of daylight and a lot of sun in this way I always see it well, but this of course this is a personal decisión. I also know that removing the tactile sound, vibration ... etc, does not remove much consumption, but between this and all the other points added everything we will achieve greater autonomy and less battery consumption and that is what it is about. It is as if all the faucets in the house leak, a faucet does not lose much water, but if we put them all together we will surely fill a big bucket.
As for increasing the size of the registration buffer, if we increase the registration buffer it is because by having a larger record size we achieve that the CPU is more freed by having less load, with this we make the CPU available for other tasks and We will be faster when playing a video or when browsing the Internet, if we must be careful and not increase the registration buffer too much because we could suffer a higher latency between audio and video in streaming videos, for example. With this we get our phone to be a little faster, without increasing battery consumption.
In the end, with all these adjustments, we achieve with each one of them small battery savings that when put together all give us greater autonomy with a longer use time before recharging our Oneplus 9, I think that is what we all want. Thank you for your interest, I hope I have been able to solve your doubts. Greetings.
Did those point but still draining battery....
OP, on my Samsung's using any power management as you described will cause erratic behavior and even a permanent increase of battery usage.
Find the battery hogs and deal with each on a case by case basis.
Try temporarily disabling Google play Services when not needed.
Disable all cloud apps. Take out the trash; FB, WhatsApp, Twitter etc shouldn't be installed as apps and are malware.
Using a package disabler or adb edits is the only way to kill some of the unneeded parasite apps on a stock phone.
Use this edit to block ads globally:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
EDIT: Last Update: 10th Sep 2011 with New INfo (trick no.7)
Advanced Tricks for Saving Battery
The following tweaks can greatly save battery if you done it right. But bear in mind that risk are relatively higher since its involve those deep system components.
If you know what you're doing, there is not much to worry about.
Note: I will not responsible for the any damage of your device
My Result:
Before: After moderate usage of 20 hours, Battery Left 30% - 35%
After : After moderate usage of 20 hours, Battery left 70% - 75%
Note: Battery Usage is very subjective matter. The numbers here is not trying to give you an exact calculation, it just trying to give you a feel of how the battery saving. But i have try my best to be consistent on the usage pattern, cpu loads and temperature to do this comparison. Of cause, you might discover different result on your device. With different ROM, kernel, radio, usage, screen brightness, all the other factors come into play, the result would varied.
Kindly please post a feedback on how it works on your device>
1. Use Undervolted Kernel / ROM
- Undervolted means that your device will use relatively less battery to give the same CPU frequency
- (e.g. normally CPU run at 1.61ghz @1350mv, after undervolted it may require only 1275mv at the same frequency)
- Tested on my device, it is the most effective tweak to increase battery life (I reduced -100mv at most of the CPU frequency (except 1), give me about 30-35% more battery)
- Because the undervolting value is varied depend on the ROM and kernel, so no point i post all the numbers here. (PM me if you need the list)
- Ask at your respective ROM thread for the availability of undervolted tweak
- If you wanted to try to change the undervolting value, i recommended to use OC/UV beater2 http://forum.xda-developers.com/showthread.php?t=1207546
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Because the tool have ease-to-use interface (no need use terminal emulator), just few taps will do.
- Most importantly, we can test new UV value with "Temp Activate", if the device freeze, just restart and it will go back to the last good state (last best config for you, instead of kernel's default value), and no need to flash the vddreset.zip / other reset.zip
2. Use "GSM auto (PRL) to save more juice while still connecting through 3G
- in the phone setting>wireless and network>MobileNetwork>NetworkMode
we are only allow to choose GSM only/ WCDMA / Auto between two
- but if you use type "*#*#4636#*#*" to phone Information, you can choose more type of networkmode. It is claimed that choose "GSM auto (PRL)" allow you to save more battery (cell standby) while allow you to connect to 3G network.
- This might somehow depend on your carrier / provider
- Please provide feedback on this. THanks
3. Try out different CPU Governor
- nowadays a lot of ROM have advanced CPU governor like Smoothass, Smartass, Interactive, etc.
- Try different combination during wake up and screen off to look for the best setting that let u save more juice
- This are my settings:
Governor during awake = On Demand
Max Wake = 998mhz Min Wake = 122mhz Governor during Screenoff = PowerSave
Max Sleep = 307mhz Min Sleep = 122mhz - NOTE: if you put min sleep too low, there is a chance that you device might freeze and won't wake up!
- I personally recommended "DaemonController" from Sybregunne for controlling the CPU governors and frequencies. It is a ease-to-use, yet sophisticated enough for the purpose of OC/UC. It is my favourite OC/UC controller since it released.
- DaemonController is a smart tool that it will bypass virtous daemon, and use direct frequency if we choose governors that is incompatible with the virtuous o/c. Hence, only 1 deamon is run which is more efficiency.
- Refer to the original thread here for more details: http://forum.xda-developers.com/showpost.php?p=16726715&postcount=2
- Quoted from original thread: "It is a Graphical tool that allows users to change andrev_oc/virtuous_oc frequencies and governors without having to reboot their device. Confirmed to work on Android Revolution HD 6.1.0 and a lot more ROMS.
4. Use AutoKiller Memory Optimizer
- This tool is different from other app killer
- It fine tunes android systems inner memory manager to keep your device fast over time.
- As a side effect it also lowers battery consumption.
- At certain free memory level (e.g. 250mb), the android os will automatically close those apps not in use (according to original android os logic)
- The lowMemoryKill level can be modified to suit your style of usage. It is to find a balance point between "not killing the apps you're need" and "sufficient free RAM to avoid sudden out of RAM / Laggy ".
- What i experience before is that these values are set to be too low. It keep most of the apps opened in background. So we can use the apps much faster and consump less cpu. Result: we have lower free RAM. The tradeoff: When I open heavy game, I experienced run out of RAM (it tell me not sufficient RAM to run).
- When the values set too high. It will kill the apps in background faster. So we will spend more cpu, and slower to reopen it. Tradeoff: you will have alot of free RAM back there. But for what?
- Therefore, it is to find the middle point that satisfy both ends. Generally, users with more apps better off with lower lowmemorykill value. Users with less apps (always switch between fews app only), are better off with higher lowmemorykill value.
- MY case: I only have 25+ apps installed. and Only use few apps (other rarely use). THis is my setting (in Pages): 3072, 8192, 16384, 50688, 58368, 76288. I have experimented with many values for 3 months. Just 1 month ago, i found these value suit me very much. It keep balance between the two tradeoff mentioned. Maybe you can try to figure out your own.
- Generally, we play with the last 3 numbers only. The first 3 numbers is related to:
(Foreground app)
(Visible app)
(Secondary server)
Which offer no significant benefits if we kill them.
5. Use Autostart
- Instead of closing them, it would be better if we don't let the app start from the begining
- You can choose to disable those app that u feel unnessary, so that they will not run during your phone startup
5. Check your Battery Consumption
- Download "Current Widget" or "battery monitoring widget" from market
- these apps will monitor your battery usage and recoded in a log file
- This is the normal consumption rate (varied across ROM, kernel and CPUI frequency and other factors)
Sleep/ScreenOff Consumption: 2mv - 8mv
WakeUp Consumption (no wifi, just use local apps, no gaming): 150mv - 250mv
Gaming consumption: about 300 - 400 mv (varied across diff games)
- To be comparable, it is suggest that you try to compare the consumption rate with your friends with same ROM, kernel, radio)
- With the monitoring log, you will able to notice adnormal peak / adnormal high drainage easily
6. Use "Battery History for GingerBreak" to check what running in background (Especially thanks for Saluco for this useful way to check battery drainage )
- this is a free tool can be download from xds forum http://forum.xda-developers.com/showthread.php?p=13328125
- Go to "Partial Wake Usage" to see what apps running when your device is sleeping
- Please "thanks" the developers of the apps for creating and letting us use his useful tool
- Give the screenshot of "Battery History for Gingerbreak" to the community of your ROM, this will give them more clues for them to help you
- For consistency, please monitor your usage for at least 3 hours (@ frequency 1 - 5 minutes) in order to have sufficient data and reliable readings.
7. Disable "Receiver" of application using AutoRun Manager (Really for Advanced User ONLY)
- Receivers are the "condition" where if it is fulfilled, the app will be executed
- For stance, Google Map has 8 receivers. Either 1 of these 8 conditions is met, google map will be open and run automatically.
- Now we actually try to disable this autoRUN by disable the "receiver" = means that even if the condition is met, the app won't run
- TO do this we need donated version of AutoRun Manager (available in market) to do this, go setting enable advanced mode
- Go second tap of the menu (advanced menu) to disable the receiver of particular app
- It is HIGHLY recommended to disable 1 receiver at 1 time, so that you can know the impact and trace back to the receiver
- you might get confused if you disable too many receivers at 1 time
- WARNING: ONLY disable those receiver that you know. DIsable system's receiver will make your system instable. So better only disable the user app.
- WHY IT IS USEFUL? Example: i used "Battery History for Gingerbreak (tip 6) to found out that "Facebook for android" is locking my device from being deep sleep (as it shown as high minute usage in the "partial wake menu"). Then i wanted to disable the feature of the that keep my device awake. THen i disable the "awake service" receive of it. Then it will help to save more battery by preventing those app that run automatically when certain conditions are met (example: Wifi-on, location changed..etc_
<More humble sharing is coming>
<<< Please click on "Thanks" if you found this post helpful, your thanks are very much appreciated >>>
------------------------------------------------------------------------------------------------------------------------------------------------------------
(The content is talking about HTC Desire HD, but the tricks can generally apply to any other smartphones, Hope it help you~)
Well it’s been 7½ days since I reviewed the Desire HD in which I said I didn’t want to comment on battery life until I’ve used it for 10 days. Tomorrow morning at 10am will be the 10th day, but I’m ready 14 hours early!
I’ve seen a lot of talk on the internet about terrible battery life, I’ve even experienced it myself (10% per hour on standby) but not wanting to give it a bad name without being sure, I’ve waited. I can now declare – the Desire HD does not have a battery life issue!
Read on after the break for how you can make yours last 24 hours on one charge!
Let me explain first of all, why I don’t think there is an issue. My Desire HD, last night and today, has shown better battery life than my Samsung Galaxy S and Nexus One ever did. It will probably continue to improve for the next week too.
Yesterday, after 10 hours of medium to light use (screen on was 40 minutes), I was still at 59% battery.
Today, I’ve been off for 12 hours and I’m still at 48%. The screen has been on for 50 minutes, 30 minutes of streaming music via bluetooth, 1 hour of podcasts playing through my earphones and a few text messages. Generally, on standby (and not being used) on 3G while at work, it was only using 2% an hour! I’m not [/B]sure any Android phone has ever managed that low consumption for me.
I don’t know how HTC have managed it from a 1230mAh battery, but if anyone manages to produce an ‘extended’ battery that fits, this thing could last a very long time. As for what the Desire Z might be able to do, wow!
So, what have I done to get this? As well as the usual tips I’ve given, here’s a few more for your Desire HD -
Remove apps you don’t use. You’ll need to root your device with VISIONary and then remove system apps like Flickr, Twitter, Stocks, Peep, Gmail and Friend Stream using Titanium Backup.
Syncing kills! Go to Settings -> Accounts & sync and see what apps are set to sync. For me, a big improvement came from turning off syncing my Facebook ‘Live Feed’ (this seems to turn back on at reboot). Also, only have one of the two Facebook apps syncing at all. For me, I stopped HTC Sense, News and Weather from syncing. If you really want these, maybe just drop their frequency an extra hour or two.
Lower e-mail checks. I have 4 e-mail accounts that K9 Mail checks for me. Like the other syncs, I dropped them from 15 minutes, to 1 or 2 hours, 4 for the less important one. Definitely don’t use the push e-mail setting on K9.
Try different connections. Go to Settings -> Wireless & networks -> Mobile networks and change Network Mode. For me, for some reason on Orange in London ‘WCDMA only’ works the best for me.
Calibrate. After 7 to 10 days use, calibrate your battery and you should be good to go, simple as that!
**ADDITION** Once in a while (if not always) try charging via USB rather than mains. It has been reported this is better for the battery and will actually provide better life from one charge. I can’t necessarily say this claim is true, but I have often seemingly got better life from a USB charge. Try it!
Bear in mind, there are people reporting much better life than I get. Some say they can last over 40 hours on one charge.
Also, make use of the ‘Power Saver’ in Settings. I’ve put mine at 30%. When this kicks in I tend to find battery consumption might even drop to 1% per hour, which means it may be possible you could last for 3 days on one charge! I can’t wait to see what happens when we get proper root and can use custom ROM’s!
(source:http://hemorrdroids.net/htc-desire-hd-battery-life/)
<<< Please click on "Thanks" if you found this post helpful, your thanks are very much appreciated >>>
Looking for general guideline for your Lithium Ion Battery?
Have a look at this http://forum.xda-developers.com/showthread.php?p=15631703#post15631703
i might have to try this on my fassy
Is it necessary to have one of these threads every other day?
Sent from my HTC Sensation 4G
Turn off your phone. Battery life will be awesome.
Otherwise carry spare chargers and/or batteries. Simples.
DirkGently1 said:
Turn off your phone. Battery life will be awesome.
Otherwise carry spare chargers and/or batteries. Simples.
Click to expand...
Click to collapse
Lol. I have 3 spare batteries, girlfriend has 2. Still chew through em in a day
ADR6300
Not really sure anything here is new information...
Cheers, I'll try a couple of these.
How about putting your phone into Flight mode while at work.
I, for my part, get my mails to my desktop machine anyways and i like the fact, no one can distract me while I'm hacking in a gazzillion lines of code.
If it's important my lazy colleagues can use their legs and walk into my office.
flight mode is as good as switching off your phone
My battery already goes down like 1% every hour when the screen is off. So it's fine to me. It's only when I'm actively using WhatsApp, Facebook and Twitter that it goes down faster.
Main killer of the battery is the screen. The screen with high backlight burns through it. While idle it hardly drains.
thanks for this
servellia said:
How about putting your phone into Flight mode while at work.
Click to expand...
Click to collapse
I would get fired if I do that
I think you just made s regular phone from your smartphone
Sent from my Desire HD using XDA Premium App
Good reminders - thanks.
cooooll thanksss
DirkGently1 said:
Turn off your phone. Battery life will be awesome.
Otherwise carry spare chargers and/or batteries. Simples.
Click to expand...
Click to collapse
niceeeeeeeeeee
Thanks for the tips, although if Google just closed maps instead of having it open all the time!
Bet that would save some battery!
Good one to see... thanks for the post
I´ll try this...
Thanks!
I use Juice defender beta with ultimate features and i did calibrate my battery. It's 1:26 AM and through moderate to heavy usage i'm still at 41%. It still has a lot to do with your CPU speed (over/under clocked), ROM, Radio and kernel. I'm CM7 Lordmod's CFS kernel and the latest Radio from AT&T Stock (I have the Inspire the Desire HD's identical cousin.) and a RIL to match. Oh and I'm Overclocked to ~1.2 GHz using the ondemand governor.
Hey everyone,
Lately I've been in the works of trying to get better battery life, as I only get about 2 - 2.5 hours of on screen time. I've seen other users get anywhere between 5-7 hours. I do use facebook, and have uninstalled the official facebook app for the friendcaster one, but have yet to still hit anywhere near that amount of time.
Out of curiosity, and hopefully future reference for other users, what are some great ways to boost battery life? Do you use apps? Uninstall software? Please, do share!
justin0025 said:
Hey everyone,
Lately I've been in the works of trying to get better battery life, as I only get about 2 - 2.5 hours of on screen time. I've seen other users get anywhere between 5-7 hours. I do use facebook, and have uninstalled the official facebook app for the friendcaster one, but have yet to still hit anywhere near that amount of time.
Out of curiosity, and hopefully future reference for other users, what are some great ways to boost battery life? Do you use apps? Uninstall software? Please, do share!
Click to expand...
Click to collapse
Manually controlling screen brightness was the biggest increase for me. The other one that helped was 2g data when i turn off the screen.
Freeeeze apps with Titanium Backup. You wont miss anything neither you loose perfomance, no you gain.
Sent from my HTC One S using xda premium
Change notification updates to suit your needs. Stuff that you don't need to know right away, lower frequency or turn to manual. For instance:
- Change weather updates to every 1-2 hours, unless you really need to know that it changed by a couple degrees as it does.
- Decrease facebook notifications (big one. If you use it a lot, then keep it high, but realize that this WILL drain battery.)
- Manually update stocks (again, if you don't need them instantaneously)
- Blog & News apps usually set notifications on by default, disable or lower frequency on them
- Lower screen brightness
- Turn display to auto sleep 30sec-1min tops
Note that while some of the notification controls can be found within the system settings, many apps will require you to go to their individual settings to adjust them.
All depends what you do with it. Navigation, internet, talk time and intense games all suck up more battery. That doesn't mean you shouldn't do that stuff, but it's just the way it is on any device.
Simple, root and install CPU sleeper, that should give u a lot of battery life.. at least that's how I do it and today I unplugged my phone at 10 am and its 9:25 and I have 65% left
Sent from my HTC One S Unlocked
using XDA Premium
justin0025 said:
Hey everyone,
Lately I've been in the works of trying to get better battery life, as I only get about 2 - 2.5 hours of on screen time. I've seen other users get anywhere between 5-7 hours. I do use facebook, and have uninstalled the official facebook app for the friendcaster one, but have yet to still hit anywhere near that amount of time.
Out of curiosity, and hopefully future reference for other users, what are some great ways to boost battery life? Do you use apps? Uninstall software? Please, do share!
Click to expand...
Click to collapse
Almost all of em are running on custom roms I beat and I'm the one you said that with 5 - 7 hours screen time everyday. There are many things to do to maximum the battery performance and first thing is root and unlock your phone and flash a custom rom. If you are on stock rom, it would be almost a no go.
1. Flash ViperOneS 1.2 rom or One maximuS V2.5 rom, they are the best sense based rom with the greatest battery performance I've seen.
2. If you don't need sense, flash cm10 or aokp. They should give you more battery because they aren't as resources hog as sense. However, you couldn't use sense UI and access to the dedicated image chip in camera.
3. Turn the brightness level down to as low as possible, this is the major battery killer.
4. Switch to 2G when you are in standby mode. Disable fast dormancy, it will save you battery in standby mode at the cost of connection speed when you surf web it will be slower but it does save you some battery in standby status. You can disable it in ViperOneS's tweaking but you'll have to do it manually in all other roms but that is very very easy. Personally, I let it on because the 3G speed isn't good in Hong Kong, too many iphone/android everywhere here, over crowed. In every street in HK are messed up by SGS3/Note/Note2/Iphone, think about how horrible it is.
http://forum.xda-developers.com/showthread.php?t=1684604
5. Turn off wifi when you don't use it, disable max performance in wifi setting. Turn the auto-sync off when you don't need it too.
6. Just remove all apps and bloatware you don't want. When you flash ViperOneS/maximuS 's add-on, you will have a list to do it.
7. Some bloatware will still be there after flash the add-on. You have to download systemapp remover to del those apps.
8. Some apps like to run as services mode and they drain battery in background like youtube, google map, playstore. You need to download AutoStarts and force them to disable as an auto-startup services after bootup.
9. Download Systempanel and check any non-system apps running at services mode in background. Force them stop in control panel. I only have four non-system apps let them running as services like whatsapp.
10. Don't run too many widgets, I only have two widgets on. Don't use 3D wallpaper.
11. Use opera mobile to surf web. The stock browser and chrome should faster but sometimes they drain battery real quick.
12. Turn the cpu mhz down when you are just doing some normal/easy works because the stock kernel has very suck governor performance(only ages governor: on-demand, save battery, max performance) and drains battery fast. Turn the cpu mhz back to high level only when you play games, this will save you great battery. Don't worry S4 CPU is still very powerful even you set it to half speed. You can flash custom kernel if you don't like to turn cpu speed up/down, they introduce more efficiency governors to handle it automatically but all 3rd kernels are likely to have some bugs at this time. There aren't many active developers out there.
13. After a heavy or long using like a full battery cycle, reboot the OS to clean up the cache/memory leak.
14. Use nova launcher or apex launcher to replace the sense launcher.
Well, I basically do ALL the stuffs above and got 5 ~ 7hrs screen time. Today, I do surf the web like mad(4hrs), 1hr 720p movie(software decode in MX Player as it's a rmvb movie), 30mins+ music with poweramp. Guess what? I got exactly 5hrs screen time and 1% battery left when I get back to home, very lucky though. I think my usage is a bit high today, normally I have 6hrs screen time average.
A lot of people on stock ROMs can get that sort of battery life too.
This is mine on stock:
http://forum.xda-developers.com/showthread.php?p=27010378#post27010378
Also wrote a quick guide, pretty similar to the above:
Terminator19 said:
Leave "best wifi performance" turned off.
Disable any apps that you don't need in settings>apps>click on app>disable at top right
Don't have weather etc. syncing every 30 minutes etc. set to something like 2 or 3 hours.
Manually control the screen brightness as auto makes the battery life worse, install qbright from the market and set a gesture so when you swipe up or down on the homescreen or dock icons this app is opened like the below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have it set to currently; night is 0%, indoor 30%, outdoor 50% and sunshine 70%
Keep wifi on as much as possible and set to never sleep
Keep GSM mode selected instead of WCDMA in mobile network settings as one; the voice reception is stronger and better battery life even when connected to wifi I found.
If you aren't going to be using any internet at all for quite while (meaning no need for weather, emails to sync etc.) then turn wifi and mobile network data off.
Only enable WCDMA when you want to browse or stream something (only when wifi is not possible)
Don't use any form of a task killer, if an app isn't responding just use the built in one.
Click to expand...
Click to collapse
WOW! Thanks guys! I'll definitely be trying these tips today.
Lets keep'em coming!
I'm running CM10 and all I did was lower my CPU clock to 1134 and I get great battery life. I also try to keep my wifi off as often as possible. I have auto-brightness and auto-sync on and usually get 6-7 hours and don't have to charge it all day. I prefer being able to use the better governers on top of the decreased frequency, but I haven't been able to get the Fusion AOSP kernel working on CM10 for quite some time.
Jewcifer said:
I'm running CM10 and all I did was lower my CPU clock to 1134 and I get great battery life. I also try to keep my wifi off as often as possible. I have auto-brightness and auto-sync on and usually get 6-7 hours and don't have to charge it all day. I prefer being able to use the better governers on top of the decreased frequency, but I haven't been able to get the Fusion AOSP kernel working on CM10 for quite some time.
Click to expand...
Click to collapse
I've always thought about under-clocking my CPU. I'll give that a try too. I'm sure i don't need the full 1.5ghz. I'll play around with them and see which will fit my needs .
My battery lasts twice as much just by turning the mobile internet off. I turn it on only when I need to surf the web/sync my apps and turn it back off right after.:victory:
Change governor to smartass2 and set your max CPU frequency at 1ghz. Also you can install app called llama for profiles switching and battery saving.
i own a stock, un-rooted Galaxy SIII on Verizon. please use this post as a general guide and as my opinion, but i take no responsibility for anything you might do to your phone (i don't think anything i suggest is sketchy or messes about with the phone anyway).
1. the graph below is your friend. you can see it by going to settings > battery and then tapping on the graph at the top of the screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mobile network signal: green is good, yellow is okay, red is bad/no signal.
GPS on: self explanatory
Wi-Fi: self explanatory
Awake: if you see blue, that means the phone is working. it's processing something, it's displaying something, it's sending or receiving data, etc.
Screen on: self explanatory
if you see blue on the Awake line but no corresponding blue on the Screen on line, this means the phone is doing things while it's in your pocket and the screen is off. if this is occurring excessively, it is generally not a good thing, but it's inevitable to some degree. for instance, if you have a weather widget or Gmail syncs regularly, you will see this happen.
if the phone is off (i.e. the screen itself is not being turned on at all) for 8 hours while you're sleeping and the Awake bar is heavily littered with blue or it's a straight blue bar, then 99% of the time you have an app that's causing wakelocks, meaning it's taxing the phone without you even using it. depending on the wakelock, it can really kill your battery fast.
2. if you have lots of wakelocks, you can download an app like BetterBatteryStats. however, it costs money, and some find it to be confusing. a better way to tackle this is to check all of the sync/push settings in each of those apps.
for instance, i use apps like Instagram and Pulse. both of these apps have settings for background updates:
my advice is to uncheck these boxes whenever you can, and many apps out there will have these sort of settings. another thing to look out for are apps that have a "send anonymous usage data" option. tons of apps out there have this functionality checked by default, so you should un-check them wherever possible.
3. the stock Email app. in my limited use, it has proven to be a complete battery nightmare. if you use Gmail exclusively, then use the Gmail app and don't touch the Email app. too often, people will set up one or multiple email accounts via the stock Email app and have them all set to push notifications. this can kill your battery in 6-8 hours with the screen completely off, and the phone will get hot as well. if you absolutely have to use the Email app, make sure you change your settings to sync email once an hour or two instead of push/every five minutes.
4. if you live in an area where your signal is weak (go to settings > about phone > status to see signal strength), your phone is going to drain battery faster than if you had a strong signal, all other things equal. -70 dBm is pretty close to perfect, -90 is decent, -100 is poor, and -110 is pretty bad. likewise, if you're roaming, you will burn through your battery almost as fast as if you were watching a movie via Netflix.
5. this isn't really advertised much, but in general, when you are quitting an app, you should use the BACK button to do so, NOT the home button. the back button usually acts like an "exit" button, but the home button basically leaves that app open and takes you back to your home screen.
to test this out:
- open up Youtube, let it load, then hit your home button to take you to your home screen.
- long press the home button to bring up recently used apps.
- tap Task manager on the lower left.
- observe that Youtube is still an Active application:
now, re-load Youtube, but use your Back button to exit out of it. repeat the steps above to check Task manager and you'll see that it is no longer in the list of active applications.
there are undoubtedly some applications that don't consume much battery even though they might be in the list of "Active" applications, but i still believe that utilizing the Back button to exit apps is a good way to go about using your phone throughout the day.
final various thoughts:
- your mileage may vary, but i haven't found that leaving wifi on constantly or off constantly really makes a difference while i'm home and connected to my network vs. using cellular data (Verizon). my focus is on minimizing wakelocks, and just having wifi on with no wakelocks doesn't seem to cause excessive battery drain. i do also have a very strong signal at -70 dBm or so. i lose about 5-7% with the phone sitting next to my bed overnight. this is normal usage, and when i wake up and check the battery graph, there are only a few wakelocks (Gmail and Beautiful Widgets syncing, and not much else). in the end though, when i'm out and about, i will turn off wifi if i'm not going to be connected to a network.
- leaving bluetooth on or off doesn't really make a difference in my battery life either. i generally connect when i get in my car, but if i have it on and it isn't paired with anything all day while i'm at work, it doesn't really consume my battery at all. therefore, i leave it on all day (even though it is un-paired) and i don't notice excessive drain whatsoever.
- i usually average about 4-5 hours of screen on time over a period of ~18 hours in a normal day, with auto-brightness on.
- if you had good battery life and it started going downhill recently, think about the apps that you have recently installed. chances are really good that there's some setting in those apps that are causing wakelocks, and in turn, excessive battery drain.
- google now seems to drain my phone fast, so i disabled it altogether. it's somewhat of a neat feature, but in the end, i just leave it installed on my Nexus 7 tablet and keep it off of my phone. i have enough things drawing power on the phone as it is, and i can still do voice searches on Google and whatnot.
- i took the 4.1.1 OTA update over the weekend and got pretty marginal battery life for a day, so i decided to do a factory reset and re-do all of my screens and re-install many of my apps. i'm still tweaking it but my battery life seems to have stabilized to something close to what it was with ICS.
anyway, this got very long, but i hope it was informative. your mileage may vary but i do believe that most of these points are pretty fundamental and will apply to your phone's battery life, whether you're rooted or not.
**ADDITIONAL EDIT**
i didn't mention that i also went into settings > application manager and disabled a bunch of applications/processes, where the stock system would let me. the list of things that i disabled are:
accessories
allshare play
apps
exchange services
kies air
media hub (i use google play music)
music hub
s suggest
s voice (is pretty slow, and bad)
SNS
sync service
verizon tones
VZ navigator
i would have disabled more, but it won't allow me to without rooting and flashing a custom ROM and/or freezing/uninstalling apps with Titanium Backup.
here is a screenshot of my battery life from yesterday/last night. you can see that when my screen is off, my phone is generally not getting woken up, and as a result, my battery life has been very stable.
I'd like to start a thread that discusses battery drain from Play Services--no not just specifically about Custom ROMs and Play Services 7.x and the SystemUpdateService issue, but a general Play Services. I see too many threads and "guides" and supposed "fixes" popping up specific device forums, but honestly Play Services affects ALL Android users that have GApps installed.
There's too much misinformation out there, and I know that Android has always had a bad image in regards to battery life, so I see too many people throwing out unvalidated fixes and misguiding users. Meanwhile, tons of users are accepting any fix they can find online in hopes of saving their battery life. That's honestly NOT the best solution. There's often adverse effects being introduced and a lot of compromises. I'd like this thread to have some healthy information AND discussion so we can truly understand WHAT is going on and how to best tackle this perceived drain.
1. Introduction
What is Play Services? To put it simply in the words of Wikipedia:
Google Play Services is a proprietary background service and API package for Android devices.
Click to expand...
Click to collapse
To give more detail, Play Services is in charge of a lot of background services and a lot of core functionality of Android devices from anything ranging from location services to ads to payment services.
2. What causes drain?
Location Services is probably one of the biggest drains of Play Services. Per the Amplify developer, Play Services will fire a location update every 60 seconds to Google servers. Why does Google do this? They probably use our location for their own purposes in addition to other features like Google Now location based updates, and well.... they're Google. They collect our data.
In my testing on a Nexus 5 and OnePlus One, a fresh build of Android with Location Services enabled will drain somewhere just under 1%/hour on LTE while idle. On WiFi, your drain could easily be far below that. To me that's not bad at all. Remember, not all of that is Play Services. Some of it goes to background syncing of Gmail and other Google services. However, there are instances where Play Services can go crazy and potentially drain more.
So that's just out of the box drain. Other apps could leverage Play Services' Location APIs. Google Now for example will do this. Wallet can use location to send you updates about offers or ads. Other apps like Google+ or Facebook have the ability to see nearby friends. Foursquare/Swarm has the ability to send you tips about nearby venues.
3. What you can do to fix this?
Like any process improvement, you should probably understand where your drain is coming from. By default, Play Services has some drain, but a properly set up phone should not be draining more than 1% / hour on mobile network provided that you're not experiencing poor reception or network congestion.
There's essentially what I'd like to take as a two step approach to Play Services Drain:
Understand the default drain of Play Services without the involvement of 3rd party apps - this should be under 1%/hour for most phones on mobile data. Is that too much for you? If so, Amplify is probably the best solution out there.
If your drain is well above 1% / hour, then other questions come up. Is your battery still in the proper condition? Do you have a rogue app syncing? If you can rule that out and still come back to Play Services, then I'd likely say its a 3rd party app USING Play Services and therefore causing excessive drain. BetterBatteryStats will often just lump Play Services drain all into one bucket, but use Wakelock Detector to understand which app is actually causing the drain.
Think long and hard about what apps you have set up to enable background location updates. You shouldn't be blaming play services for using your location, but rather apps themselves for being setup a certain way. Comb through your app settings and understand what's going on. It might be fun to see where your friends are in Facebook, but are you prepared for that background location update that potentially kills your battery? Or what about that weather widget? DO you need every 5 minute updates?
Q: What about switching to Battery Saver for Location Settings?
I honestly think Battery Saver is a red herring. The difference between High Accuracy and Battery Saver is that GPS is not used. But here's the thing--ask yourself when do you actually need GPS? It's not just running in the background all the time. Unless you open Yelp/Swarm/Maps all the time, GPS isn't being used anyway, so why would you disable GPS? High Accuracy maintains the ability to use GPS when an app calls for it, but the background updates which are the most tasking from a long term battery use perspective are still there whether or not you use Battery Saver or High Accuracy. That every 60 second ping to Google still exists on Battery Saver.
This fix is almost always proposed every time someone brings up drain, but you really need to think about how location settings works before falling for that misnomer. In fact, High Accuracy will likely be a better choice for most because say you want to look at the map to see where you are. If you need your location NOW, it gets frustrating to open the app up and realize it points you to a location a mile away. After maybe 30 seconds of pondering you then realize that your GPS was off, you go and switch Location Settings to High Accuracy, and then you wait another 30 seconds for the GPS to lock. Why not leave High Accuracy on to begin with? It gives you GPS when you need it, but when you exit Maps, GPS stops on its own.
4. Conclusion
I'll be writing a lot more, but this is my first stab at a guide. I encourage discussion as I'm likely not the only self-proclaimed expert out there. I just feel there was enough misinformation to warrant a more centralized guide for all devices.
List of Proposed Fixes for Battery Drain with Analysis
Since there's many proposed fixes for battery drain, let's talk about what some individuals have proposed, and I will inject my analysis.
Turn off background data
Many apps use Play Services' location APIs. If you turn off background data, then you end up with an app that cannot communicate because Play Services is always in the background. Why would anyone do this for an app that relies on background data to function? This is a bad fix IMO.
Use Privacy Guard to deny Play Services from Waking Up
This is a possible fix, although once again Play Services has a need for waking up while your phone screen is off. If we review once again what Play Services is responsible for, one can see that apps like Google Now which is supposed to give you updates in the background, requires location updates to work properly, then denying the ability for Play Services to wake up when your screen is off may have some adverse effects.
The good thing is that wakelocks are only required when the screen is off--therefore when your screen is on, your apps should be able to fetch location updates via Play Services and Play Services can function normally. The concern comes from when your screen is off. So if you play on your phone all day at work, it might not be bad, but if you sit with your phone in your pocket all day, and want a traffic alert to show up, it might not show up. Or for a busy guy like me who flies a lot for work, traffic cards showing when I need to get to the airport might not show up because Play Services is not updating my location properly when my phone screen isn't on.
This is a poor fix IMO but slightly better than the option above.
Use Amplify
This is probably the best and least harmless fix to implement. Its safe IMO to implement immediately. Most of us don't need every 60 second updates on location. Every 5-6 minutes should be sufficient. That still gives you enough update interval to get traffic cards. You can always get a location update when an app calls for it in the foreground. This fix should easily clamp down on your background Play Services drain and reduce it significantly. Of course, this is only affecting the periodic update that by default comes out of the box with Play Services. If other apps are constantly calling for location updates, you need to look at what other apps may be requesting location services.
Play Services 7.x Drain
Are you getting unexpected battery drain after your Google Play Services updated to 7.x? Are you on a custom ROM?
If so, this is a bug that affects custom ROMs with SystemUpdateService disabled. It produces a SystemUpdateService wakelock that keeps your phone awake 100% of the time.
Here are several fixes ranked in order
1. Root cause fix
As of March 21, 2015, both CM11 and CM12 trees have had their fixes implemented (see commits http://review.cyanogenmod.org/#/c/91881/ and http://review.cyanogenmod.org/#/c/91882/ for CM11 and http://review.cyanogenmod.org/#/c/91021/ and http://review.cyanogenmod.org/#/c/91579/ for CM12). You can update to a CM build after March 21st, or if you're on another ROM you might want to check if there has been a fix implemented yet.
2. Manual root cause fix
In Terminal Emulator, issue the command:
Code:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
You can help make this more automated via this post here.
Note: Requires root
3. Band-aid Fix
Download Wakelock Terminator, then filter for ONLY the SystemUpdateService wakelock for Play Services.
Note: You need Root and Xposed for this to work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Bigger Band-aid Fix
What separates this from #3 is that this band-aid fix disables other features of Play Services. It will fix the battery drain, but by disabling parts of Play Services, you create unnecessary adverse effects.
Go to: Settings > Privacy > Privacy Guard > Advanced (in the menu) > Google Play services
You can then disable "Wake up" and "Keep awake".
Reserved.
I am running OOS 10.3.8 (rooted) on my OP 7Pro. I run the following command to force a certain app into the "ACTIVE" App Standby Bucket ...
am set-standby-bucket package.name active
After doing this, how long will the app remain in that "ACTIVE" bucket under this version of OOS? Will it live there forever because of the fact that I put it there with the above command? Or will the OS eventually take over and perhaps move it to a different bucket? All the docs I could find about this topic state that each OS has its own way of managing the placement of apps into these buckets. I'm wondering whether anyone knows specifically how OOS 10.3.8 does this.
I want that particular app to always live in the "ACTIVE" bucket, and so if the OS eventually moves it, I will have to periodically put it back into "ACTIVE", which I can easily do via Tasker.
Thank you in advance for any thoughts about this.
On Samsung's if power management is disabled all app buckets stay in the active state.
If you do not enable power management the bucket state will not alter.
Note 10+/Android 9 or 10
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
blackhawk said:
On Samsung's if power management is disabled all app buckets stay in the active state.
If you do not enable power management the bucket state will not alter.
Note 10+/Android 9 or 10
Click to expand...
Click to collapse
Thank you very much. Does anyone know how this functions specifically in Oxygen OS on an OP 7Pro? There is nothing in the settings for that OS called "Power Management".
(This XDA forum is for "OnePlus 7 Pro Questions & Answers".)
HippoMan said:
Thank you very much. Does anyone know how this functions specifically in Oxygen OS on an OP 7Pro? There is nothing in the settings for that OS called "Power Management".
(This XDA forum is for "OnePlus 7 Pro Questions & Answers".)
Click to expand...
Click to collapse
Interesting.
Samsung customizes their UI heavily. Not sure how other manufacturers handle this. Lol, using power management in my case on Samsung's leads to erratic behavior and heavier power consumption even after days
If all buckets show as active and if trying to reset their bucket state will not take (change state, close Developer options then reopen to see if it took), then nothing more should need to be done. The apps apps are already running in their active bucket state which is the default setting.
That doesn't mean they're continously running full bore; Android will generally manage them effectively and efficiently in this state from what I've observed. I deal with power hogs on a case by case basis without power management.
Turning off battery background use in individual apps does not alter the bucket state, at least on my devices.
Play with it... see how it behaves.
blackhawk said:
Interesting.
Samsung customizes their UI heavily. Not sure how other manufacturers handle this. Lol, using power management in my case on Samsung's leads to erratic behavior and heavier power consumption even after days
If all buckets show as active and if trying to reset their bucket state will not take (change state, close Developer options then reopen to see if it took), then nothing more should need to be done. The apps apps are already running in their active bucket state which is the default setting.
That doesn't mean they're continously running full bore; Android will generally manage them effectively and efficiently in this state from what I've observed. I deal with power hogs on a case by case basis without power management.
Turning off battery background use in individual apps does not alter the bucket state, at least on my devices.
Play with it... see how it behaves.
Click to expand...
Click to collapse
Thank you. In my case, OOS doesn't put all apps into the "ACTIVE" bucket. It has some sort of algorithm for deciding between the various states, and different apps appear in different buckets.
That's what the docs about Android's App Standby Buckets say is supposed to happen, and these docs also state that each OS can manage the decisions differently about which apps to put into which buckets, and when to do so.
These docs also state that an app in the "ACTIVE" bucket is supposed to behave as if it's in the foreground, which means that it has normal network priority. Samsung might override this behavior of "ACTIVE" apps, but if so, it would be a deviation from the specs.
I am already playing around with this on my device. I'm just not sure whether an app will stay "ACTIVE" forever after I do the following ...
Code:
am set-standby-bucket package.name active
... or whether at some point after I issue that command, the OS will take over. Eventually I'll figure it out. I'm just asking here in this OnePlus forum in case anyone who is familiar with the inner workings of OnePlus devices and OOS already knows the answer.
HippoMan said:
Thank you. In my case, OOS doesn't put all apps into the "ACTIVE" bucket. It has some sort of algorithm for deciding between the various states, and different apps appear in different buckets.
That's what the docs about Android's App Standby Buckets say is supposed to happen, and these docs also state that each OS can manage the decisions differently about which apps to put into which buckets, and when to do so.
These docs also state that an app in the "ACTIVE" bucket is supposed to behave as if it's in the foreground, which means that it has normal network priority. Samsung might override this behavior of "ACTIVE" apps, but if so, it would be a deviation from the specs.
I am already playing around with this on my device. I'm just not sure whether an app will stay "ACTIVE" forever after I do the following ...
Code:
am set-standby-bucket package.name active
... or whether at some point after I issue that command, the OS will take over. Eventually I'll figure it out. I'm just asking here in this OnePlus forum in case anyone who is familiar with the inner workings of OnePlus devices and OOS already knows the answer.
Click to expand...
Click to collapse
I read the whole Google bucket explanation. In the end I went with what works best real world.
Lol, I played with this a lot a while back.
Google will keep improving something until they screw it up.
After looking around on the web I think you may have similar power management apps on that device ie battery optimization. There could be more on drop down menus as well.
I wouldn't alter the bucket state with abd. If it's already set as active it's probably the optimized already. I use standby apps just to double check that power management isn't active as I've seen first hand the mess it can cause.
blackhawk said:
I read the whole Google bucket explanation. In the end I went with what works best real world.
Lol, I played with this a lot a while back.
Google will keep improving something until they screw it up.
After looking around on the web I think you may have similar power management apps on that device ie battery optimization. There could be more on drop down menus as well.
I wouldn't alter the bucket state with abd. If it's already set as active it's probably the optimized already. I use standby apps just to double check that power management isn't active as I've seen first hand the mess it can cause.
Click to expand...
Click to collapse
I understand, but mine is a special case.
The OnePlus devices and their OOS operating system are particularly bad concerning push-notifications. They over-do the Doze-related, battery-saving procedures so much that many push-notifications don't even get delivered to apps at all until the app is opened up in the foreground, which could be many minutes or even hours after the notification was originally sent.
Turning battery optimzation off for those apps has no effect. Nor do any of the many different Doze profiles that I have tried. And "whitelisting" the apps is simply what happens when battery optimization is turned off, and it therefore has no effect.
I have to put those apps into the "ACTIVE" bucket, and only then do they reliably receive those otherwise highly delayed push-notifications at the time that they are sent.
I have spent a lot of time trying to correct this problem, and I only came up with two solutions: (1) Use Tasker to periodically open those apps in the foreground for a few seconds, so they can repeatedly get caught up with any pending, undelivered push-notifications; or (2) put the apps in question into the "ACTIVE" bucket.
Obviously, the second alternative is less intrusive to my everyday use of my device.
I have not experienced any negative consequences of putting those apps into the "ACTIVE" bucket.