Database Users

Backlight settings for optimal battery life?

hey guys! which backlight settings do you use for optimal battery life? 40% brightness? or do you just use the automatic version?

I use 50% when watching films, 30% general use and 20% to 10% around the house in the evening! Bright screen on this beast - no need to use the auto settings as this seems to give me the equivalent of 20-30% "overbrightness".
I use a program called "Backlight control" by Ulrik Jensen, and I have it as a short cut on the today screen to quickly alter the settings...

[TIPS] Thoughts on improving battery life for Android on the HD2

After countless tweaking, I found what is an acceptable battery management scheme for my HD2.
I thought: what parts of the phone suck up the most battery life (based on CurrentWidget)?
1) processor (1 GHz)... this is overkill for most applications. Basically I decided to dial this down to 384mhz which is rather acceptable using SetCPU. So basically Max: 384000 Min: 245000; scaling ondemand and set on boot checked. Under Profiles, I added Screen Off with Priority: 100, 245 max and 245 min. Set this ondemand setting.
2) I enabled Autokiller (downloaded from the Marketplace) and set to Extreme (150, 160, 170).
3) Under Settings--> Accounts & sync--> I turned off Background data (unchecked this) and Auto-sync as well.
4) Under Wireless & Networks --> Mobile networks --> I turned off Enable always-on mobile data (unchecked this) too.
Well, things are much better... with heavy usage (not a moderate guy here) I unplugged my phone at 8:30 AM and now it is 2:35 PM and my battery is down to 76% now. So basically I will be getting around 24 hours straight of moderate-heavy usage here.
Not bad?
Personally I wish that we could throttle the processor based on the mAh of drawn current. I think that 300-400 mah (according to Currentwidget) is way too high for processor usage? Not sure.
Any opinions?

wow that sounds sooooo slow, good for you though

I rather charge my phone everyday after work than turn my phone to 2005 phone then still have to charge it everyday.

Well that's great battery life, but I'd prefer it if my processor didn't suck more than the G1's 528MHz P.O.S.

I use a spare battery (8 bucks ebay) I make no attempt other than adjusting screen brightness appropriately, to conserve battery or resources. I have never had any issues. sometimes my spare floats around in my pocket two to three days unused mostly on days that I work that happens.
I learned the value of a spare shortly after I got my tp2.
Sent from my HTC HD2 using XDA App

qipengart said:
After countless tweaking, I found what is an acceptable battery management scheme for my HD2.
I thought: what parts of the phone suck up the most battery life (based on CurrentWidget)?
1) processor (1 GHz)... this is overkill for most applications. Basically I decided to dial this down to 384mhz which is rather acceptable using SetCPU. So basically Max: 384000 Min: 245000; scaling ondemand and set on boot checked. Under Profiles, I added Screen Off with Priority: 100, 245 max and 245 min. Set this ondemand setting.
2) I enabled Autokiller (downloaded from the Marketplace) and set to Extreme (150, 160, 170).
3) Under Settings--> Accounts & sync--> I turned off Background data (unchecked this) and Auto-sync as well.
4) Under Wireless & Networks --> Mobile networks --> I turned off Enable always-on mobile data (unchecked this) too.
Well, things are much better... with heavy usage (not a moderate guy here) I unplugged my phone at 8:30 AM and now it is 2:35 PM and my battery is down to 76% now. So basically I will be getting around 24 hours straight of moderate-heavy usage here.
Not bad?
Personally I wish that we could throttle the processor based on the mAh of drawn current. I think that 300-400 mah (according to Currentwidget) is way too high for processor usage? Not sure.
Any opinions?
Click to expand...
Click to collapse
I am not sure if you did enough there ... best preservation of the battery is if you actually TURN YOUR PHONE OFF and take the battery out... then when u need it, pop the battery in, use it, and again - take it out...
Who cannot deal with battery drain should get probably Nokia E71 sine its battery runs for at least 4 or 5 days with moderate use including navigation...
Sent from my HD2 using XDA App

Actually, this isn't bad at all. I managed to get about 3-4 hours of Angry Birds to play this evening. Sadly enough, I work nights so I have no way to plug during the middle of the day. This is awesome and man, I only get serious lag during hard animation or graphics processing during gaming. By 10 PM tonight, I got down to 28% battery life before recharging now
Everything else is kosher. I am a happy dude now.

Screen Glows - Even on standby
Anyone else notice their screen glowing at night using Android. (Not bright enough to notice during the day).
When i turn off the screen using red button, I see a glow coming from phone. Seems screen isn't shutting off correctly. This will be causing unnecessary battery drain.
When i switch back to Windows then turn off, the glow isn't there. (Only on Android).
Anyone know a setting/hack to fix this?

freebieman said:
Anyone else notice their screen glowing at night using Android. (Not bright enough to notice during the day).
When i turn off the screen using red button, I see a glow coming from phone. Seems screen isn't shutting off correctly. This will be causing unnecessary battery drain.
When i switch back to Windows then turn off, the glow isn't there. (Only on Android).
Anyone know a setting/hack to fix this?
Click to expand...
Click to collapse
Yeah, that doesn't sound right at all, but considering you gave no info what so ever on your build setup it may be next to impossible to help.

Ok, seems overkill but good for you.
for me, using ShubCraft 2.0 drop mode, stock kernel, no underclocking/overclocking/undervolting/overvolting, and just a little bit of display brightness tweaking I get 16 hours out of my phone with I would say moderate use. Probably an average of two hours mp3, two hours gaming, at least 90 mins talk time, about 30-40 texts, light 3G browsing and email use and probably an hour or so gaming. Obviously the rest of the time in that 16 hours is "standby" time. Even then I probably only get down to about 40% charge.

qipengart said:
After countless tweaking, I found what is an acceptable battery management scheme for my HD2.
I thought: what parts of the phone suck up the most battery life (based on CurrentWidget)?
1) processor (1 GHz)... this is overkill for most applications. Basically I decided to dial this down to 384mhz which is rather acceptable using SetCPU. So basically Max: 384000 Min: 245000; scaling ondemand and set on boot checked. Under Profiles, I added Screen Off with Priority: 100, 245 max and 245 min. Set this ondemand setting.
2) I enabled Autokiller (downloaded from the Marketplace) and set to Extreme (150, 160, 170).
3) Under Settings--> Accounts & sync--> I turned off Background data (unchecked this) and Auto-sync as well.
4) Under Wireless & Networks --> Mobile networks --> I turned off Enable always-on mobile data (unchecked this) too.
Well, things are much better... with heavy usage (not a moderate guy here) I unplugged my phone at 8:30 AM and now it is 2:35 PM and my battery is down to 76% now. So basically I will be getting around 24 hours straight of moderate-heavy usage here.
Not bad?
Personally I wish that we could throttle the processor based on the mAh of drawn current. I think that 300-400 mah (according to Currentwidget) is way too high for processor usage? Not sure.
Any opinions?
Click to expand...
Click to collapse
I've put Darkstone Froyo (no sense) 3.0 on top of my HSPL 2.08, radio 12, Ozz Rom barebone and DID NOT install SetCpu, nor Task killer, nor under/over-clocked or under-volted my CPU.
The result is 4-8 mA in Currentwidget on standby with data sync all the time, Wifi on (while in standby wifi gets disconnected automatically - you don't have to do anything), bluetooth and GPS off when I do not need them.
So, my battery delivers at least 24hrs of Anroid use without any tweaks or additional apps, just BARE/STOCK Android Froyo 2.2

I have realized that the "reboot method" is working. I'm running HyperDroid Sense 1.1 with Hastarin r8 together with Omega XT 17.2 and radio 2.15. The power consumption was 57-65 mAh in standby - but today I simply tried the "reboot until consumption is being reduced" method - and now it consumes 9-11 mAh in standby.
I'm using SetCPU with the recommended settings.
With other words: simply reboot the phone and check the consumption with CurrentWidget. After 1 - 3 reboots it should be reduced to an acceptable level.

nzxtneo said:
Yeah, that doesn't sound right at all, but considering you gave no info what so ever on your build setup it may be next to impossible to help.
Click to expand...
Click to collapse
Good point! - HD2 Tmous Running Android 2.2 mdeejay eVo Sense REVOlution build.
Runs fine in windows mode, but in Android screen continues to have dim glow when switched off. For the moment i've taken to switching back to windows to save battery life.
Any thoughts?

E90 Commie said:
I have realized that the "reboot method" is working. I'm running HyperDroid Sense 1.1 with Hastarin r8 together with Omega XT 17.2 and radio 2.15. The power consumption was 57-65 mAh in standby - but today I simply tried the "reboot until consumption is being reduced" method - and now it consumes 9-11 mAh in standby.
I'm using SetCPU with the recommended settings.
With other words: simply reboot the phone and check the consumption with CurrentWidget. After 1 - 3 reboots it should be reduced to an acceptable level.
Click to expand...
Click to collapse
I have two flavors of Android that are currently my favorites. Great performance, no freezes fully functional and acceptable as an alternate for everyday use. One is phiredrop's Skinny EVO v1.5 and the other is mDeejays Sense rEVOlution v2.3. Both are based on the EVO ROM and both are Sense builds. After a lot of experimentation I have found battery life to be excellent with the following procedure.
Always boot your Android using Excellers Android loader. Boot up into Windows Mobile. Once it is settled in tap on the Exceller Loader icon but do not launch Android at this point, instead hit your home hardkey to light up the hardkeys then immediately tap on the Exceller Loader icon again and load your choice of build before the hardkey lights go off.
Once Android is fully loaded turn off screen auto rotation and disable auto brightness in settings. Then set the brightness level one notch below what is default. Do not use SetCPU nor any task killers whether they be manual or automatic. These are not needed for great battery life and can be detrimental to your performance and battery life rather than beneficial. Go to the Market and download and install CurrentWidget and set it to show on your main screen. Turn off GPS, Wifi, and bluetooth since you do not use them full time anyway.
If you spend most of your day inside of a factory as I do, or any other place where carrier signal is not good, get an airplane mode widget to put your device into Airplane Mode whenever the signal is spotty. If you have a signal fulltime then the airplane mode is not necessary as I have found the drain on the battery to be exactly the same with it off or on when I have a good signal.
Do all of the above then hit the hard end key to put your phone in standby. Let it set a couple of minutes then hit the key again to light it up, unlock it and take a look at the mA reading on your current widget. I think you will be pleasantly surprised at the results.
I am downloading SkinnyEVO v1.7 as I type. I will report back on the drain that this new build requires as it has a newer version of Haret, some folks are reporting that it causes severe battery drain.
By the way, when at home with good signal and Wifi turned on, this setup for these two builds draws only 4mA in standby.
Below are screenshots of two different EVO based builds and on two different days. It's not a coincidence folks, this does work. I also set 11.02.miui.english build up this exact same way and it was only drawing 3mA in standby also. Give it a try and let me know your results for your build. I would like some info specifically on the non-EVO builds, as well as Sense and non-Sense builds for this method.
One more thing to consider, I am NOT using hot reboot to get these readings. These are readings that I get on each and every boot with the method explained above. Hot Reboot is a handy tool to have installed if you have some crazy app that wants to drag your device down and won't turn loose, but it is totally unnecessary for good battery life.
HTR
{
"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 checked the CurrentWidget earlier today after upgrading the kernel to Hastarin r8.1. 9-10 mAh with HyperDroid Sense 1.1 and everything is working great.
I have the screen rotation enabled and use SetCPU paired with WatchDog (I prefer to receive warnings about processes running away).
I use the EBL to load Android immediately after WM has loaded and everything is working just great. I got the impression that I have almost a better battery life with Android now than with WM.

hitekredneck said:
I have two flavors of Android that are currently my favorites. Great performance, no freezes fully functional and acceptable as an alternate for everyday use. One is phiredrop's Skinny EVO v1.5 and the other is mDeejays Sense rEVOlution v2.3. Both are based on the EVO ROM and both are Sense builds. After a lot of experimentation I have found battery life to be excellent with the following procedure.
Always boot your Android using Excellers Android loader. Boot up into Windows Mobile. Once it is settled in tap on the Exceller Loader icon but do not launch Android at this point, instead hit your home hardkey to light up the hardkeys then immediately tap on the Exceller Loader icon again and load your choice of build before the hardkey lights go off.
Once Android is fully loaded turn off screen auto rotation and disable auto brightness in settings. Then set the brightness level one notch below what is default. Do not use SetCPU nor any task killers whether they be manual or automatic. These are not needed for great battery life and can be detrimental to your performance and battery life rather than beneficial. Go to the Market and download and install CurrentWidget and set it to show on your main screen. Turn off GPS, Wifi, and bluetooth since you do not use them full time anyway.
If you spend most of your day inside of a factory as I do, or any other place where carrier signal is not good, get an airplane mode widget to put your device into Airplane Mode whenever the signal is spotty. If you have a signal fulltime then the airplane mode is not necessary as I have found the drain on the battery to be exactly the same with it off or on when I have a good signal.
Do all of the above then hit the hard end key to put your phone in standby. Let it set a couple of minutes then hit the key again to light it up, unlock it and take a look at the mA reading on your current widget. I think you will be pleasantly surprised at the results.
I am downloading SkinnyEVO v1.7 as I type. I will report back on the drain that this new build requires as it has a newer version of Haret, some folks are reporting that it causes severe battery drain.
By the way, when at home with good signal and Wifi turned on, this setup for these two builds draws only 4mA in standby.
Below are screenshots of two different EVO based builds and on two different days. It's not a coincidence folks, this does work. I also set 11.02.miui.english build up this exact same way and it was only drawing 3mA in standby also. Give it a try and let me know your results for your build. I would like some info specifically on the non-EVO builds, as well as Sense and non-Sense builds for this method.
One more thing to consider, I am NOT using hot reboot to get these readings. These are readings that I get on each and every boot with the method explained above. Hot Reboot is a handy tool to have installed if you have some crazy app that wants to drag your device down and won't turn loose, but it is totally unnecessary for good battery life.
HTR
View attachment 434968 View attachment 434969
Click to expand...
Click to collapse
Update: Nov 9th - I have tried the SkinnyEVo v1.7 and have had no luck in getting it to run. Even changed out the kernel to newest 8.1, tried it with the supplied data image and without. No luck at all, it will not get past the HTC splash screen. I wish there were a way to disable that splash so I could see what is causing the problem and get this thing to launch.
Anyways, I have now tried the above method the tytung NexusHD2-FRG83 v1.4 PPP/RMNET build and had the exact same results that I had with SkinnyEVO v1.5 and Sense rEVOlution v2.3. 3 mAh in standby. Works like a charm, now if only SkinnyEVO v1.7 would cooperate.
HTR

It really works, thanks!

qipengart said:
After countless tweaking, I found what is an acceptable battery management scheme for my HD2.
I thought: what parts of the phone suck up the most battery life (based on CurrentWidget)?
1) processor (1 GHz)... this is overkill for most applications. Basically I decided to dial this down to 384mhz which is rather acceptable using SetCPU. So basically Max: 384000 Min: 245000; scaling ondemand and set on boot checked. Under Profiles, I added Screen Off with Priority: 100, 245 max and 245 min. Set this ondemand setting.
2) I enabled Autokiller (downloaded from the Marketplace) and set to Extreme (150, 160, 170).
3) Under Settings--> Accounts & sync--> I turned off Background data (unchecked this) and Auto-sync as well.
4) Under Wireless & Networks --> Mobile networks --> I turned off Enable always-on mobile data (unchecked this) too.
Well, things are much better... with heavy usage (not a moderate guy here) I unplugged my phone at 8:30 AM and now it is 2:35 PM and my battery is down to 76% now. So basically I will be getting around 24 hours straight of moderate-heavy usage here.
Not bad?
Personally I wish that we could throttle the processor based on the mAh of drawn current. I think that 300-400 mah (according to Currentwidget) is way too high for processor usage? Not sure.
Any opinions?
Click to expand...
Click to collapse
Max: 384000 ?!?!?!? then whats the point of getting a good , expensive phone with huge 1GHz proccessor !?!?!?

hello,
i realy have hight battery drain ... it's between 50 and 60 mA in standby mode no matter if the phone is on flight mode or data on or any other thing enabled ... so i said maybe it's some app that prevent my hpone to go in standby mode ... so i did everything from the start ...task29 +hspl+magldr+recevery ...after installing the hyperdroid v12 and befor installing any app i installed current widget and the same consumption 50 -60 mA ...i've read that in all the night and with flight mode the phone drain 2% - 5% ... for me it's 5% per hour ...
I dont know if it'as a hardware probleme or no but i thought it's my battery but i use 2 battery now and the same thing for both... i used many roms the hyperdroid is the less hungdry ... with cm7 v3.3.5 an amazing battery drain.
does the magldr or CLk have anything to do with battery drain?

[Q] Help, what is your battery drain, and why mine is sooo High???

First - let me state - and it is true - that I used the search function.
I read pages and pages of advices to lower battery consumption on my HD2 Android... without success...
First I used an SD ROM. I read that a NAND would improve battery life. So this is what I did.
I am also using SetCPU with a profile when battery <30% and another one when screen is off to LOWER the CPU speed. In normal use, I set CPU speed at 768MHz trying to lower power consumption...
I use a task killer to free memory and prevent silly programs to drain my battery off...
I use Juice Defender to control wifi, data, etc...
And with all of this in place, my "Current widget" shows a consumption of 180mA with screen on doing nothing, up to 350-400-500!!! mA when acutally using the phone wifi+sync...
In the forum I read consumption like 3 mA - 9 mA!!! This is FAAAAAR Way lower than what I ever had with different builds...
So this is an help scream to everybody: what is your battery drain, and why mine is sooo High???
Hint: I am also a fan of LCD Density changer, with setting at 165... can this have an influence on battery drain??? I reverted to the original 240, doesn't seem to have any influence...
Thanks for your help,
Looki

My drain is 3-9 ma in STANDBY ONLY now and again slightly more but mainly the values stated. And my screen on between 120+160ma. Turn off auto brightness if you have it on, and set it at the lowest your comfortable with (display is big batt drainer) I DONT use taskillers as they do more harm than good. I use NO undervolting and only the default settings with my rom. I have low lcd density setting 167 i think. Lcd density has no effect on your battery drain!
Found this here. http://forum.xda-developers.com/showpost.php?p=13151738&postcount=11296 Might be of some use to you? (from hyperdroid gbx thread)

Whats youre rom?
And do u use ext partition on sd?
I dont even use SetCpu anymore. Only taskkiller.
Auto-brightness is on
Auto sync is off.
Im using UD 3.3 nand from crawlingcity
Stansby is 3 -6 ma
Using round 160 to 250.
Sent from my HTC HD2 using XDA App

How long does your battery last from 100% to self shut down? As for Current Widget, keep in mind that when people say "Standby", its generally referring to the screen being off. Set current widget to update every 30 seconds, and turn the screen of for 40 seconds. Then quickly turn the screen on, unlock, and check what it is reading then.
If its still high, try "Force Stop" applications in the Settings > Applications menu one by one, i've had to do this more than once to locate problem apps that were destroying my battery in standby mode.

I'm knew to Android, let me share you my idea.
I use UD3.3
I removed google stuff
gmail, search, etc
No auto sync
Location off
Always kill market when screen off.
I use beautiful widget for weather manual refresh.
I use battery widget
Auto level for screen
sometimes WIFI on
2g Only
2 or 3 calls,total of 3 to 4 min a day
My battery stay 48 hrs in STBY mode.
I think the most draining factor is
1) google stuff they are battery hog.
2) screen
3) bad written programs (every time they check connection to
internet or looping for doing something, looping will make
CPU in high frequency).
4) bad device driver such as BT which is known as 60ma
drain. it is not the hardware but it is the software doing
the drain.
thanks

pc2058 said:
I'm knew to Android, let me share you my idea.
I use UD3.3
I removed google stuff
gmail, search, etc
No auto sync
Location off
Always kill market when screen off.
I use beautiful widget for weather manual refresh.
I use battery widget
Auto level for screen
sometimes WIFI on
2g Only
2 or 3 calls,total of 3 to 4 min a day
My battery stay 48 hrs in STBY mode.
I think the most draining factor is
1) google stuff they are battery hog.
2) screen
3) bad written programs (every time they check connection to
internet or looping for doing something, looping will make
CPU in high frequency).
4) bad device driver such as BT which is known as 60ma
drain. it is not the hardware but it is the software doing
the drain.
thanks
Click to expand...
Click to collapse
Bt drain has been fixed, wil now get you 6-15 ma.
Google stuff aint bad, just set update frequentcy to manual.
(Helps with alot of other programms that require internet.)
Sent from my HTC HD2 using XDA App

[Ultimate GUIDE] Increase your battery life on Android
Thanks guys for your help!
I made a compilation of all tips I could collect and/or find by myself.
They are here: http://forum.xda-developers.com/showthread.php?p=15229416
Regards,
Looki

[APP] control your phone's brightness and save battery

as we know,screen consumes most of the charge on our x2ds
here is an app that can reduce your phone's brightness to -90
and offcourse minimum brightness helps to save battery .
name : lux
download from here : http://m.apkhere.com/down/com.vito.lux_1.99.9999.2_paid

Sony Xperia Z5 - battery analysis & runtime optimization thread

Alright guys,
step by step I'll post findings in this thread,
therefore I'm reserving a few posts for the following "sections"
- app (software) drainers
- wakelocks
- alarms
- services
- kernel, hardware drainers
Bear with me, that it's currently rather "bare" in appearance since my main focus is currently on scientific work in a different direction ...

- app (software) drainers
There appears to be increased battery drain (consumption) after usage of the Music, (more likely) the Video app by Sony - current focus is the "Image enhancement" (X-reality) when it's enabled

- wakelocks
lots of Google Play Store related
lots of Google Play Services related
...
Stamina Mode (in combination with all the other savers appears to cause higher battery drain, Stamina Mode itself also uses Wakelocks) (Google Services were blacklisted) [pretty certain]
Stamina Mode + Stamina clock (plus the other savers) [maybe]
Forum threads on wakelocks:
http://forum.xda-developers.com/showthread.php?t=1827676 [GUIDE] The Total Newb's Guide to Wakelocks

- alarms
mainly Widgets (which need to synchronize often)
Apps (that depend on state change)

- services

- kernel, hardware drainers
Settings -> Display -> Tap to wake up
consumes around 0.2-0.3%/h (measured with BetterBatteryStats & on AndroPlusKernel v9)
Settings -> Display -> Adaptive brightness
(currently evaluating, I imagine having seen some increased battery drain with that, too but not certain yet)
---------------------------------------------------------------------------------------------------------------------
Base drain rate
On Lollypop, AndroPlus Kernel (v9) and RomAur is around 0.7%/h
The Actual drain rate
is however higher - around 1 - 1.5%/h - up to 2+%/h, when including the radio unit (modem) (which accounts for additional 0.2-1%/h
when taking into account lots of wakelocks and alarms (wakeups !) - it's possibly still higher than that (!)
---------------------------------------------------------------------------------------------------------------------
which clearly indicates that either the Qualcomm 810 is a huge battery drainer - Sony delivers not so much optimized software - OR: the community does a much better job in optimizing the heck out of the ROMs and Kernels (e.g. Note 3, n9005 with IdleKernel 6.6.5 + Phronesis v4)
Bear in mind though that LP is the first software release on the Z5 platform, so there's still much room of improvement (which we'll hopefully see with MM, Android Marshmallow 6.0)
so it's probably a combination of all the above,
it's still sad, that there's an hourly battery drain on the Z5 vs. daily battery drain on e.g. the Note 3
For further reading on batteries :
http://batteryuniversity.com/learn/article/does_the_battery_fuel_gauge_lie Does the Battery Fuel Gauge Lie? - Why the Battery State-of-charge cannot be measured accurately
http://phandroid.com/2010/12/25/you...is-lying-to-you-and-its-not-such-a-bad-thing/ Your battery gauge is lying to you (and it's not such a bad thing)

General - wakelock, alarms & services battery savers
Amplify (or similar)
Greenify (or similar)
Kernel Adiutor (or similar which allows kernel wakelock blocking and capable to detect big.LITTLE cpu technology )
BetterBatteryStats (or similar, wakelock, etc. statistics)
Kernel - battery savers
CPU hotplug mechanisms (e.g. thunderplug in AndroPlusKernel)
fast-switching cpu governors (+ low clocking, #)
fast-switching gpu governors (+ Adreno Idler, #)
# fast switching governors allow the CPU or GPU to serve performance and power, when it's needed and in the other times to stay as low as possible while saving energy
Battery saving forum threads:
http://www.android-hilfe.de/thema/a...tery-extender-kontrolle-von-wakelocks.679757/ [Akku][root][xPosed] Amplify - Battery Extender - Kontrolle von Wakelocks [German]
http://forum.xda-developers.com/android/general/guide-extreme-battery-life-t3095884 ✭[GUIDE][07-02-2016]Extreme Battery Life Thread(Greenify+Amplify+Power Nap)✭ [English]

reserved 2 - just in case

Nice idea
Maybe we can add
Screen enchancements (xreality)
And stamina mode with different settings

Useful thread, thank you. Maybe you can compare this data with MM later. And I agree with sidy93, battery save modes should be included too.

Maybe also include comparision between various stamina modes vs lolipop built in battery saver ?

Is there any way to solve mobile radio active bug??
Sent from my E6653 using Tapatalk

Strange thing worth my Z5 is that with stamina mode on & auto brightness, I get around 4 hrs SOT tops before I'm at 5%
Turned them both off and much better battery life. In now at around 50% remaining and have over 3hrs SOT...
{
"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"
}
Sent from my E6653 using Tapatalk

Wess.a said:
Is there any way to solve mobile radio active bug??
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
yes, there's a fix when you use the XPosed Framework:
http://forum.xda-developers.com/xposed/modules/xposed-mobileradioactivefix-t3189393
haven't tried it though since it didn't occur for me
nookcoloruser said:
Strange thing worth my Z5 is that with stamina mode on & auto brightness, I get around 4 hrs SOT tops before I'm at 5%
Turned them both off and much better battery life. In now at around 50% remaining and have over 3hrs SOT...
[snip] out picture [snip]
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
That's also my observation:
stamina mode on & auto brightness, ON leads to a higher battery consumption than WITHOUT ,
I'm suspecting sensors keeping the phone alive issue, but can't put the finger on it yet

Some intermediate observations:
- sensor and automation-related features appear to worsen battery drain (automatic brightness, X-reality)
- Stamina-Mode in combination might/might not worsen the battery drain rate to 1.5 or 2x (e.g. 0.5 was the base; with stamina raising it to 1 to 1.5% per hour), need more observation what causes this (Greenify ? Amplify ? - all combined with Stamina ?) - like I wrote Stamina Mode itself also uses Wakelocks
- stripping the system radically down to remove lots of Sony's own functionality (Stamina, qualcomm services, Google related services, pre-packaged apps) didn't lead to significant battery improvement or at all (!) - think about that !
(I would have liked to save the list of deactivated, frozen packages - but I had to do a complete factory reset afterwards - after ScreenFilter and another Sensor disabling app completely made the phone unusable )
- Hotplug (Thunderplug) from AndroPlus' kernel doesn't appear to make a difference - at least for me - in terms of base drain per hour (that's 0.5-0.7% at best), so either that's the hardware limit or something else is doing its thing to make us unhappy
When looking at the other side where it's (assumedly) always brighter - you get the following for the Nexus 6P:
https://www.reddit.com/r/Nexus6P/comments/3ru2eo/forget_doze_lets_talk_about_standby_battery_drain/ Forget Doze, let's talk about Standby Battery Drain
where they see similar battery consumption in standby (and that's on Marshmallow ?)
So the "solution" would be to either go all full in with a highly customized ROM + kernel that makes best use of battery saving features (Samsung Note* ?) - hinting at a software limitation,
or looking around for another device with also the Snapdragon 810 chipset to see whether this is the optimum that can be achieved (consider our smaller battery compared to the Nexus 6P ! ) and seeing the 810 as a hothead with great performance - where you can't get best of both worlds (performance, battery) yet

A firewall to limit apps' access to network can have a pretty important effect on battery endurance. Especially limiting Google from calling home at all times. This https://play.google.com/store/apps/details?id=eu.faircode.netguard&hl=en is very powerful and customizable, requires no root and is resource friendly. My battery capacity and SOT significantly improved after setting it up to limit or block most apps', including system app's, access. Try it out.

E5823 said:
A firewall to limit apps' access to network can have a pretty important effect on battery endurance. Especially limiting Google from calling home at all times. This https://play.google.com/store/apps/details?id=eu.faircode.netguard&hl=en is very powerful and customizable, requires no root and is resource friendly. My battery capacity and SOT significantly improved after setting it up to limit or block most apps', including system app's, access. Try it out.
Click to expand...
Click to collapse
Great suggestion @E5823 !
if it's not very demanding on resources, that's a great addition
I got a mayor breakthrough - for now only on the AOSP builds:
previously the battery drain was at least 1% per hour (or under optimal circumstances 0.5-1% per hour,
while the battery stats where still fluctuating heavily around 0.7% per hour.
With some changes in the kernel, configuration and having a few settings off (adaptive brightness and double tap to wake),
the optimum with enforced doze (via Greenify + root) was at 0% per 7 hours, and also 0% per 2 hours (no WiFi or Mobile Radio - yet)
I will keep investigating into it and see whether this reasonably can also be applied to Sony's "stock" ROMs + a custom kernel,
locked bootloaders for now seemingly are out of luck

zacharias.maladroit said:
With some changes in the kernel, configuration and having a few settings off (adaptive brightness and double tap to wake),
the optimum with enforced doze (via Greenify + root) was at 0% per 7 hours, and also 0% per 2 hours (no WiFi or Mobile Radio - yet)
I will keep investigating into it and see whether this reasonably can also be applied to Sony's "stock" ROMs + a custom kernel,
Click to expand...
Click to collapse
Do tell more please

Pretty interesting and useful post. Thanks.

thanks for the info