Related
Overview
Battery Saver Ultimate application provides the best power settings to saves the battery time of your device or your tablet. Whenever the battery runs low or goes too much down, just tap the power saver app to turn on the saving mode.
Battery savers help you to switch off all the extra functions like WiFi, Bluetooth, GPS, sound and other energy consuming apps on the device. The app will notify when the power gets down in percentage and it even shows the charging stages.
Charging Stages:
Free Battery Saver Ultimate app regulates the manner in which your device is charged with a Unique 3 Stage Charging system to ensure you get the most out of your battery and reminds you not to over charge.
Types of Mode :
1. Saving Mode: (Use in lowest Battery Status)
Device Brightness set to 10%
In Activate WiFi of the Device
Stand By time to 15 seconds
2. Sleep Mode: (Use when you sleep)
Turn Off Call & SMS and turn ON the Flight Mode
Set Vibrations Off.
Airplane Mode.
Sound Off and mute media sound too.
Brightness set to 10% or minimum level.
3. Customized Mode
You can Customize app usages as your need to save Battery Power.
Can adjust the battery saving setting freely depend on your need and usage.
Can adjust WiFi, Bluetooth, vibration, sound, device brightness, synchronization and stand by time.
Features and Requirements
Accurate battery remaining time
Shows Standby Time.
Accurate charging remaining time
Schedule power saving modes for work/class/sleep and more!
3 Stage Charging system 1. Fast charge 2. Continuous Charging 3. Tickle Charging.
Wifi/Data/Bluetooth/GPS/Flight Mode toggle!
Brightness control!
Shows Battery Health, Current Battery Power in mAH, Temperature, Voltage and Battery life status.
Interesting app. I installed it on my tablet. Look up how it will work. Pity that application is not in material design...
Can I say dodgy app here full of ads and nothing as you say it is. Gives me to play games and full of ads. Avoid
Looks very Good though
Full of ads, nothing like advertised. Avoid.
mr_stax123 said:
Looks very Good though
Click to expand...
Click to collapse
Please state more
i want to prevent apps to auto start to save battery and ram, which app should i use, grrenify or autorun manager or any other?
First, you need not concern yourself with free ram on an Android device. Android manages resources better by itself. As for the apps that launch on startup, you can got to menu>settings>apps and select the "running" tab to show you exactly what is really running. Then, the easiest way is to uninstall the app in question.
Automated task killers do nothing but cause more problems than they can potentially solve.
You might find this thread enlightening.
mr_stax123 said:
i want to prevent apps to auto start to save battery and ram, which app should i use, grrenify or autorun manager or any other?
Click to expand...
Click to collapse
The task killer discussion gets old. I think there is risk of oversimplifying both sides. ie on one side people want to treat it like pc...not correct. On the other side people seem to imply any discussion of memory management considerations is irrelevant/rejected because "android will handle it all"....which is not always entirely correct either. The latter may be closer to the truth especially for new devices, but there is still room for middle ground. Not all programs are equal, some launch "services" which takes priority over other app processes. Too many of those services can eventually crowd out cache and slow your phone down. Maybe most people with newer phones will never get there, but there are still people with older phones (including the op for all we know) and also some folks with new phones who (if they listen to the oversimplifications) may get carried away on the number and type of apps they install over the life of their phone
---------- Post added at 12:47 AM ---------- Previous post was at 12:43 AM ----------
Even so, killing off those services is not the answer. If an older phone has too many running services so it taxes it's resources then it's either time to uninstall some or get a device that can handle it. If it's a problem with the app itself hogging resources, then let the developer know and find an alternative.
If you try to tow a boat with a bicycle, the answer isn't to throw away the boat's engine to make it lighter. Similarly, a task killer may make the phone's performance improve briefly, but over time it will make things worse. And it fixes nothing.
An app preventing another app from "auto-starting" is a task killer. Look at it this way: The phone boots up and runs it's processes. The auto-start blocker detects an app it doesn't want to run, so it kills it. Now, depending on what app it is, the phone may call for it again and thus running it later, which defeats the purpose of an auto-start killer, unless that app is a task killer which again kills said flagged app to keep it killed.
The way to properly manage an app you don't want to have enabled on the phone at bootup is to disable the app on the system manager (newer phones have it AFAIK), freeze the app via Titanium or similar apps, get into the app settings and disable certain features like auto-sync and set everything to manual.
However, the OP did not specify what phone and which apps. It may be apps which the phone requires to run at some level, like Maps (which several apps call for), or maybe the apps he is seeing are just RAM cached, which really don't matter at all.
Adjusting with app settings is preferred if you can, but does not always solve the problem (I referred to wakelock/battery drain problem with a certain version of Maps on my previous phone ... many people we having the same problem at the time and the only way to stop it was to block the app from starting as indicated in link below, or else to freeze it). Freezing has the disadvantage that you cannot run the program easily (requires you to launch TiBu to thaw the program). If you have blocked the program from autostarting, then it does not start at boot or other automatic time, but it remains available to manually launch the normal way (clicking the program icon). At that point (if it's a program like Maps), it will probably stay running until next reboot. It was my preferred solution when maps was giving me wakelocks and battery drain on my phone. Maps didn't run automatically on boot and never started until I manually started it. After that point I could live with the battery drain or reboot
Rom Toolbox Pro is a great app with many features and of course, there's an auto start manager that allows you to disable various receivers off the apps that start on boot. There's also a freeze/deep freeze feature as well. Great app
The guide to get incredible battery on your S7E!
A lot of people are having trouble to push the 3600mah battery to the absolute max, so I will here show you how to do so. This will mainly be a link to another post made my @v7, which have made an incredible guide to get a good idle drain. I will mainly explain what works on our S7E and what not, while giving a few other tips. Most of these tips can be found all over the internet, but I just want one thread, where they're all collected, so people can read every tip in one thread. As most guides are general through out all devices, they is what works and what don't on our devices. You're free to share your own tips!
REMEMBER TO MAKE A NANDROID BACKUP. ANYTHING YOU DO ARE NOT MY FAULT NOR ANYONE ELSE BUT YOUR OWN FOR MAKING THIS CHANGES!
Firstly, use a debloated rom.. That do a lot..
As said, @v7 have made this guide here. Remember to thank him!
Greenify:
Get the donation package and greenify everything that runs in the background and you don't need push notifications with. With the Shallow Hibernation, it still runs nice and smoothly when you open them. After that, you enable GCM push for hibernated apps and look, if any of the apps that you need push notifications for, supports GCM push and if they do, hibernate them. You will still get notifications, but remember to check "Do not delete notifications from hibernated apps".
I have almost everything hibernated - Maps, Facebook Messenger etc, when still working smoothly - besides Play Store, as that gives problem with paid app licenses. I also enabled Aggressive Doze. You should whitelist the same as in Powernap, that will be listed below here.
Amplify:
I have everything in mentioned in the thread Amplified without problems. I hadn't touched the services, but they should be save to disable anyways. Network Location service, have given me problems with Android Wear communication before.
Powernap:
Here comes where you need a permissive kernel. The SuperKernel that just came out, is the only one on XDA for now. In Powernap you should whitelist the following
Amplify
Android System
Google Account Manager
Google Play-Services
Google Services Framework
Greenify + Donation package
Apps you need push notifications from (like Facebook Messenger)
Xposed Installer
Your alarm clock
Basically, you should whitelist anything that you want to run in the background while the screen is off.
Better Battery Stats:
Check the app after a sleep, but leave everything on as if you were using the phone (data, bluetooth etc) as this is about lowering power usage on normal use and not seeing how long standby time you can get while everything is turned off. GCM_Reconnect and Heartbeat might be high for Google Play-Services, but for me, limiting them gave late or non push-notifications, but test it yourself (remember to restart after limiting/unlimiting).
All the small things:
Turn off location history
Turn off services you don't need and let Tasker control it. (Turn GPS on when maps open, hibernate and turn maps of when closed etc)
Turn off bluetooth and wifi scan all the time
Get Smart Network from Xposed and set your network to Edge when screen is off and 3g/4g when screen is on.
A dark theme with dark icons can save quite some power
Samsungs own greyscale can be enabled in accesibility and then triple tab on homebutton, when you know you're out for a long day.
UPSM Manager from the Play Store can add apps to the Ultra Power Saving Mode, so you can add apps like Facebook Messenger and suddenly it's way more useable.
Use Tasker to force sync, instead of having it activated. I force sync every 2 hours with Tasker + Synker
I have turned off features that I DO NOT USE. Under Advanced Functions, almost anything + edge screen features.
More connection settings and "always search for devices" - Off
Custom kernel settings:
There are no custom kernel out on XDA yet that supports full Synapse, but the Echoe Team have successfully build one.
I have set both governors to conservative, which actually is impressive smooth, while it should be the most battery saving governor which don't lag (like Powersave).
The I/O schedulers should be set to noop which have quite good battery life, without limiting performance too much. I haven't felt a difference yet.
TCP Congestion is set to Westwood (but I think that is standard anyways).
Everything have been undervolted by 25mV. That is nothing from a battery saving perspective, but well, i'm still testing.
L Speed from @Paget96 (thank him!) here is quite nice too!
I haven't had any lags with these battery saving options yet. Everything not mentioned is just standard.
OOM Killer - Enabled
Cache Reclaiming - Minimum
Kernel Tweaks - Light
Kernel sleepers optimization - On
Battery improvement - on
Wifi sleeper - On
Flag Tuner - On (Some people on S7E have mentioned problems with this.. Lag, reboots and bootloops, but I haven't had any problems).
IO Boost - On
I have power saving mode enabled, with background data enabled and my phone is still butter smooth, Also, check for apps to add in the battery saving menu, as I have enabled some apps I don't use or need notifications from, manually.
I get around 5-6 hours SOT where 3-4 of them are Clash Royale, if not more.... Yeah, I game quite a lot.
I think that was all for now, but I will keep it updated when I get new ideas to push it to the limit.
This is still keeping the phone "smart", as you adjusts it for your needs.. Inb4 all the people saying, why buy a smartphone if you disable every feature.
hmm that would kill performance in tekken and AB2 as those games are heavy on QHD but i try it nonetheless, ty.
Thanks for credits
Sent from my Nexus 5 using Tapatalk
hmmmm . nice thread ! thank you !!!
Paget96 said:
Thanks for credits
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Of course ?
Good guide,
But why are you mentioning a kernel none of us have access to???
el7145 said:
Good guide,
But why are you mentioning a kernel none of us have access to???
Click to expand...
Click to collapse
There are two kernels on here now.
You could ask for permission to get on the forum where the kernel is or you could simply wait. I knew it would only be a question about days, before there would be kernels on XDA too.
With all this stuff I might as well activate ultra power saving mode and let it be
lvnatic said:
With all this stuff I might as well activate ultra power saving mode and let it be
Click to expand...
Click to collapse
Why if I may ask? That makes your phone way more restricted than the above do.
lvnatic said:
With all this stuff I might as well activate ultra power saving mode and let it be
Click to expand...
Click to collapse
Exactly.
I've gone through a lot of these kinds of tweaks in the past, and generally found having to re-load apps and disable features I like having wasn't worth the small battery life increase I saw.
That said, Everyone uses their device differently though, so what doesn't work for me may work well for others. Remember that before you say I'm spouting nonsense about small battery life increases.
Sent from my SM-G930W8 using Tapatalk
Devhux said:
Exactly.
I've gone through a lot of these kinds of tweaks in the past, and generally found having to re-load apps and disable features I like having wasn't worth the small battery life increase I saw.
That said, Everyone uses their device differently though, so what doesn't work for me may work well for others. Remember that before you say I'm spouting nonsense about small battery life increases.
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
I certainly agree that it depends how you use your phone. But if you only rely on a few apps when display is off, like a few messaging apps, Power Nap can certainly increase your battery life. I have a idle drain around 0.0-0.2% (note, 0.0% is not the same as zero drain.) and I still receive messages, and Tasker turn everything on that I need when I need it (GPS, nfc, sync and so on). So if you just install the apps, yes it decreases functionality a lot, but by tweaking it to exactly match your usage and not limiting what you use, you can certainly get increase battery life without losing features. I use my phone the same way now as uprooted, not limiting anything I use..
Most people have a lot running in the background they don't really need or depend on or that can wait till the screen turns on.
Hello guys. This topic is pretty long and it is hard to read all of it but try to read all of it till end.
Well, let me begin. The main problem of the nougat update is the dramatic increase of battery consumption (for me at least) But why this is happening?
Actually this is a matter of battery managers. Huawei had created a great phone but obviously they messed things up in the software side. Google announced "Doze" feature with Marshmallow. If we could have a brief explanation of "what doze is" is it is basically a battery protection policy created by google. In Android, apps have the ability to use what’s called a “wakelock” to prevent your phone from going into a power-saving deep sleep mode. This deep sleep mode usually kicks in when your phone’s screen is off, but that can get in the way of how some apps work. For example, if you’re using a fitness tracker, you don’t want your phone turning off GPS or your accelerometer just because your phone is in your pocket with the screen turned off.
In principle, this is a good concept. Apps keep your phone awake and working when they need to, and let it sleep when they don’t. This is a problem, though, when every developer thinks their app is important enough to keep your phone on all the time. That’s why apps like Facebook kill your battery, even when you’re not using them.
Doze helps solve this problem by periodically blocking wakelocks and shutting off network access if your phone goes unused for a while. It will then periodically allow apps to check in during “maintenance windows” every so often (these windows occur less frequently the longer you don’t use your device). Here is a graphical explanation of how doze works versus time:
http://itresan.com/wp-content/uploads/2016/05/doze-header.jpg
Doze helps solve this problem by periodically blocking wakelocks and shutting off network access if your phone goes unused for a while. It will then periodically allow apps to check in during “maintenance windows” every so often (these windows occur less frequently the longer you don’t use your device)
If we turn back to the main topic, as I mentioned before, Huawei has some difficulties combining it's own features with google's. Huawei has its own battery manager. That's why you are not receiving some notifications from facebook or whatsapp. That is because that freaking battery manager shuts everything off but still, since it has a very poor approach, the system drains battery. It is basically a matter of doze does not kicking in. As you can see, the battery usage when the screen is turned on is about the same. However, the same thing cannot be seem when the screen is off.
So what to do in order to save some juice?
-There is some workarounds for doze kicking in like these ones:
https://play.google.com/store/apps/details?id=com.yirgalab.dzzz
https://play.google.com/store/apps/details?id=com.suyashsrijan.forcedoze
These two apps have different approaches. I prefer ForceDoze as it seems the google's intended way.
I want to highlight this item because this might be the most important thing in this topic. If you don’t do anything with your phone, Doze will still do its job. It runs almost invisibly in the background. Occasionally you’ll get a few messages at once, rather than spread over a few minutes, but for the most part there’s no noticeable change. In other words this is a bit different from the conventional full deep sleep and you do not have to afraid from doze as you do with the full deep sleep.
-DO NOT CLEAN YOUR RAM TOO OFTEN. This will cause closed apps re-open and hence, more cpu usage.
-No! Cleaners, Task managers and other stuff does not work! As I mention before, they even lead more battery consumptions.
-Huawei has poor google service implementations. Even one or two implementation has some bugs that causing battery drain(for example: google backup). Try to turn them off.
-Know when to reboot your phone. Too frequent reboots may do the same thing as you cleaning your ram. However, rebooting cleans app caches so the system will work smoother. Once a week or two weeks is fine I suppose.
Please hit the "Thanks" button if you like and please point out the missing things and if you see a mistake please warn me for correcting it. I hope you liked the topic.
Have a nice day!
Doze is problem for me. I don't have push notification by the night.
darrr1 said:
Doze is problem for me. I don't have push notification by the night.
Click to expand...
Click to collapse
It's probably not because of the doze but the huawei's power manager itself.
Problem starts when phone is not active longer than 2-3 hours. In root I removed phone manager and it did not help fix the push notification problem
darrr1 said:
Problem starts when phone is not active longer than 2-3 hours. In root I removed phone manager and it did not help fix the push notification problem
Click to expand...
Click to collapse
Assuming that you are on huawei release (not los releases), untick your app from close apps after screen lock. Then go to apps, settings, special access, and make the system ignore battery optimizations for the spesific app you want to get notification from.
I did everything what I can without succes.
furkey said:
Assuming that you are on huawei release (not los releases), untick your app from close apps after screen lock. Then go to apps, settings, special access, and make the system ignore battery optimizations for the spesific app you want to get notification from.
Click to expand...
Click to collapse
first thanks for this tip. i hate it that i dont receive whatsapp messenges all the time, i hope it will work now.
BTP:
I assume huawei did not remove "doze" from our firmware, but maybe they replaced it with theire own battery manager?
Is there a complete source for doze, so we can check if everything is there? If yes it should not be that hard to activate doze and deactivate the huawei one.
But i guess we need at least the kernel sources to clear things up?
xtcislove said:
first thanks for this tip. i hate it that i dont receive whatsapp messenges all the time, i hope it will work now.
BTP:
I assume huawei did not remove "doze" from our firmware, but maybe they replaced it with theire own battery manager?
Is there a complete source for doze, so we can check if everything is there? If yes it should not be that hard to activate doze and deactivate the huawei one.
But i guess we need at least the kernel sources to clear things up?
Click to expand...
Click to collapse
Doze is not on kernel level but it is on software level. Programmatically we can activate what is left from doze or at least simulate it. However, if there is a certain need for doze we should cook a whole new rom and yes, it requires open source too.
But, let's clear a thing here: Huawei did not completely removed doze. Actually, I think they can't do that if they wish to use Android. Just some settings of Huawei conflicts with doze and prevent its functioning.
I'm using the honor 9 with emui 5.1 (android 7.0) and screebl (app used to control how and when screen locks/times out) is constantly getting killed. I have added it to ignore(=allow to run) in battery optimization and it's activated as a device administrator. It is not selected to close (power intensive app prompt) or instructed to close when screen goes off. Yet it repeatedly is getting killed - is there something else I need to do? I can't seem to find anything else I can do to stop it from being killed and it's a major nuisance.
antimatter.web said:
I'm using the honor 9 with emui 5.1 (android 7.0) and screebl (app used to control how and when screen locks/times out) is constantly getting killed. I have added it to ignore(=allow to run) in battery optimization and it's activated as a device administrator. It is not selected to close (power intensive app prompt) or instructed to close when screen goes off. Yet it repeatedly is getting killed - is there something else I need to do? I can't seem to find anything else I can do to stop it from being killed and it's a major nuisance.
Click to expand...
Click to collapse
Could you finally solve this?
I also have and Honor 9, and have the same problem with aplicacition radardroid. Is getting killed, and also have all configured to prevent this...
Try by having both in the Settings
-Battery/Close apps after lock screen (uncheck in the list)
-Apps/Settings gear/Special access/Ignore battery optimization (make it allowed)
Thank szgfg,
Both are already well configured, but still closing the app.
mikicl said:
Thank szgfg,
Both are already well configured, but still closing the app.
Click to expand...
Click to collapse
Check also is not being closed by the automatic cleanup (so add it to clean whitelisted apps) and that is not being closed due to high consumption...disable that on battery settings... Let the advertisement but do not let phone administrator close that apps automatically
Enviado desde mi EVA-L09 mediante Tapatalk
Hi jcalderonv74,
Thanks for your answer. I didn't know about the clean whitelisted apps, was a surprise to find it. But unfortunetly, everything was well configured.
Option to avoid being closed due to high consumption was already OK.
So nothing to change, everything was as it has to be. Seems more a software problem in EMUI 5.0
After some days without touching anything in the phone's configuration, finally observed that everything is working fine. All aplications configured keep opened, and it's only Radardroid aplication that sometimes closes alone (only sporadically after a recent update)
Seems more an error in Radardroid aplication that in telephone's software. So I'm not worring more about that.
Given the less friendly finger print reading I have taken to double tapping on the screen to turn it on. But relatively often it does not respond to a double tap. Is anyone else experiencing that?
The other one is that at many web sites I go to a pop up message box will come up asking if they can read my device's location. The answer box NEVER responds to a click. The screen will be dim. I have to back up 1 screen which closes the query box. I actually expect that one of my apps that have privileges to over write other apps is the culprit, but I don't see why they would mess with that one function, especially when at that moment those apps aren't being brought up. Any thoughts on this?
Increase screen sensitivity if you haven't already.
Yes I've experienced the double tapping unresponsiveness and decided to have AOD on all the time instead despite additional battery drain just to bypass this issue.
boogiecornejo said:
Yes I've experienced the double tapping unresponsiveness and decided to have AOD on all the time instead despite additional battery drain just to bypass this issue.
Click to expand...
Click to collapse
That's what I do on the 10+
Battery drain is slightly less than 1% @ hour.
For me it runs best/most efficiently with no power management* running other than the system power setting to optimized.
*some apks are package blocked otherwise all buckets show as active in Developer Options. If this is not the case unwanted power management is active.
I'm running Pie; not sure how Q will respond. I found it's best to let Android handle power management exclusively other than blocking serial power hogs like Google Backup Transport and Framework Services Framework. I don't use these.
blackhawk said:
Increase screen sensitivity if you haven't already.
Click to expand...
Click to collapse
Thanks for the suggestion. It is already active.
Here's another interesting thing: every now and then (actually several times during the course of a day) after turning the screen on the bio didn't with nor the location, and it forces me to enter the pin to get into the phone. I even have it set to not lock if hooked to my hearing aids and it still happens.
ewingr said:
Thanks for the suggestion. It is already active.
Here's another interesting thing: every now and then (actually several times during the course of a day) after turning the screen on the bio didn't with nor the location, and it forces me to enter the pin to get into the phone. I even have it set to not lock if hooked to my hearing aids and it still happens.
Click to expand...
Click to collapse
I keep my phone with me at all times, don't let others use it and never lock it. Makes life easier.
It's a steep learning curve with these devices... make sure it has the permissions it needs like being able to change system settings.
blackhawk said:
That's what I do on the 10+
Battery drain is slightly less than 1% @ hour.
For me it runs best/most efficiently with no power management* running other than the system power setting to optimized.
*some apks are package blocked otherwise all buckets show as active in Developer Options. If this is not the case unwanted power management is active.
I'm running Pie; not sure how Q will respond. I found it's best to let Android handle power management exclusively other than blocking serial power hogs like Google Backup Transport and Framework Services Framework. I don't use these.
Click to expand...
Click to collapse
Hmmm... The setting to read it loud is a system setting itself (in Accessibility settings). I don't think there are any permissions to make. I did just look and nothing is apparent.
ewingr said:
Thanks for the suggestion. It is already active.
Here's another interesting thing: every now and then (actually several times during the course of a day) after turning the screen on the bio didn't with nor the location, and it forces me to enter the pin to get into the phone. I even have it set to not lock if hooked to my hearing aids and it still happens.
Click to expand...
Click to collapse
ewingr said:
Hmmm... The setting to read it loud is a system setting itself (in Accessibility settings). I don't think there are any permissions to make. I did just look and nothing is apparent.
Click to expand...
Click to collapse
Permission to change system settings is in it's own listing apart from permissions in each app settings.
Could be more than one apk needed to make all work right.
Make sure power management not doing it.
In Developer Options>Standby Apps, all apps listed there should show as having their buckets as "active" if they not, power management is active.
You don't want that.
ewingr said:
I actually expect that one of my apps that have privileges to over write other apps is the culprit
Click to expand...
Click to collapse
one of the apps is interfering as you correctly suspect
Ive got a SM-N770F/DS and I always have medium power saving mode on. I have also always had an issue with Google Maps not wanting to detect location after I turn the screen off. I assumed it was a google issue until I turned optimized power saving mode on today and Maps suddenly started reading my location and giving directions while the screen was off. Is it possible to disable the "prevent background location access" part of medium power saving mode? Long pressing my power saving settings doesnt give any options to do this, im thinking my only option is to root. Would rooting fix this? If so, does anyone know of some roms on here that would allow me to do this? I dont care about much else from the rom, I like the phone as is and this is the only issue I have with it
Do not toggled on any power management other than the power mode (optimized) and fast charging.
They screw up functionality and increase battery usage on my unrooted 10+ running on Pie.
In Developer options>standby apps all buckets should show as active otherwise power management is active. Android will manage apps well without any power management options turned on. Track down any remaining battery hogs on a per case basis and deal directly with them. Sometimes closing the window gets it done like with Brave. Others need to be dealt with by package disabler and/or Karma Firewall.
This may or may not help you.
Gmaps is crapware. Runs best on original factory load and is a parasitic drain wanting to constantly run in the backup from boot sucking up battery and bandwidth.
Unlike you my goal is to keep it from doing this
Also review Gmaps notification and other settings. It's a mess; buried settings galore.
blackhawk said:
They screw up functionality and increase battery usage
Click to expand...
Click to collapse
blackhawk said:
Android will manage apps well without any power management options turned on
Click to expand...
Click to collapse
I feel like I have experienced the opposite. I felt like my battery was draining faster with optimized on today (2nd pic) compared to the past few days with medium power saving on (first pic). Obviously more testing needs to be done to see. Going off of the pics I lost about 50% each day, so optimized seems to be worse for battery life but the reduced screen on time makes up for it in this scenario