[Galaxy S 5 General] ikzouhetnietweten:
I use the 900F version. For most of us, the phone is more asleep than it' s in operation. That's why choosing the correct ROM & Kernel is essential for your battery.

I wanted to figure out which ROM is best regarding battery life when the screen is off and how to reach the best result.

Calculation:

BetterBatteryStats Calculation.

If I look at my stats: View attachment 3907706 I can see the voltage went down from 4327 to 4143 (-184) in 1168 minutes. That's 60 x 184 / 1168 = 9.45%/hour, which is correctly showing in BBS. Now I translate this to percentages: 9.45% voltage decrease x 4% battery decrease / 184 = 0.205%/hour battery. This is again correct according to BBS. I guess this is a fair calculation. the voltages seem to go up and down all the time, so I don't understand how it's an exact calculation but ok.

A thing that doesn't make this calculation 100% right is the number of % decrease. I have a good example of 3 battery stats that I saved in the same period of time: 22hours and 58 min, then one a few hours after that, and then last one that's one hour after the last one.

Stage 1. View attachment 3913114 -------96% (60 x 126 / 1379 min = 5,48% voltage/hour x 4 % drain / 126 V drain = 0.17% /hour

Stage 2. View attachment 3913113 ----96% ( 94 minutes later it reached Stage 2 = 0.16%/ hour. With the SAME % = 96% ! (Makes sense)

Stage 3. View attachment 3913112 --------95% ( 130 min after Stage 2 I saved another log = 0.187% / hour. You see, it just turned 95% and it goes way up again.

Conclusion: Try to save the BBS as far as you can get to the end of the % to get the lowest %/hour calculation. You'd think: Try Battery History and calculate the exact time and use these minutes in your calculation. But then I realized that the voltage has to change as well, and as I do not know the voltage, the calculation would be messed up. So best is to do as shown above, try to save the BBS manually as far as you can get to the end of the %.

Settings:

Screen off all the time. Just try to peak once or twice a day for one second.

Disabled: NFC, wifi, BT, Location, screen settings: standard screen, double tap to sleep, no rotation, no color adaptation, balanced battery mode, no ambiant color but standard, no notification lights, no gestures.

Disable auto update Google Play Store, even on Wifi, disable all Sync on Googleaccount, disable Location Services

For Touchwiz I used the Barebone Cleaner.

General apps installed Section 3: Whatsapp (not logged in), Battery History, CNN, NOS, NU.nl, Line (not logged in), MyMail (not logged in)

Battery savers:

- Section 1: Amplify, Powernap, AppOpsXposed, BBS---------------------------------Terminated as of 16/10/2016

- Section 2: Greenify------------------------------------------------------------------------Terminated as of 15/10/2016

- Section 3: Amplify, Powernap, AppOpsXposed, BBS, Greenify --------------------In Progress since 17/10/2016

- Section 4: Amplify, Powernap, AppOpsXposed, BBS, Greenify, Forcedoze ------In Progress since 17/10/2016

Conclusion: (as of 01/11/2016)

CM13 is much more stable regarding battery life than Phoenix. At this moment I can suggest CM13 with the following settings:

Ondemandplus, internal + external IO = noop, undervolt -25, aggressive multicore saving, disabled greenify, enable other battery savers as shown above.

Section 4:

:

Phoenix ROM-------------------------------------0.8%/hr Enabled Greenify, forcedoze, uninstalled Kernel adiutor so default kernel settings.

CM13 + boefla 3.3 beta5-------------------------0.24%/hr. Enabled Greenify, Enabled forcedoze, multicore saving aggressive, 2 cores max, ondemandplus, noop, noop, undervolt light, rest same as below.

CM13 + boefla 3.3 beta5-------------------------0.42%/hr. Enabled Greenify, Enabled forcedoze, multicore saving ON, Interactive, bfq, bfq, no udnervolt, rest same as below.

CM13 + boefla 3.3 beta5-------------------------0.35%/hr. Enabled Greenify, Enabled forcedoze, multicore saving ON, Ondemand, rest same as below.

CM13 + boefla 3.3 beta5-------------------------0.30%/hr. Disabled Greenify, disabled forcedoze, aggressive multicore saving etc, same as below.

CM13 + boefla 3.3 beta5-------------------------0.21%/hour. Disabled Greenify, aggressive multicore saving , same as below.

CM13 + boefla 3.3 beta5-------------------------0.231%. View attachment 3923067 Ondemandplus, internal + external IO = noop, undervolt -25, aggressive multicore saving, disabled greenify, zzmoove 2 cores max, GPU 320mhz max

CM13 + boefla 3.3 beta5-------------------------0.256%/hr. Governor: Ondemandplus, Internal IO = Noop, Undervolting -25, Installed ForceDoze and activated in Xposed, limited some more Wakelocks, and Activated Greenify again and selected all the options in Experimental.

CM13 + boefla 3.3 beta5-------------------------0.305%hour. View attachment 3920399 Governor: Ondemandplus, Greenify autohibernation disabled and deselected all the Xposed options and limited the cleaner service of greenify in Amplify that caused many alarms.

CM13 + boefla 3.3 beta5-------------------------0.24%/hour. View attachment 3918644 Boeffla config app: OnDemand Governor., Internal IO Noop. Can't say I' m excited. Greenify had a lot of wakelocks, I' ll stop the auto hibernate option in Greenify in the next test.

Section 3:

: The BetterbatteryStats (BBS) are published from now on.

Phoenix ROM -------------------------------------0.26%/hour. View attachment 3917759 The same settings as the 0,16%/hour but still a significant difference. I guess it's just different every freaking time. I' m done with Phoenix, next few tests will be on CM13 with boeffla to see a clear pattern on which is best. (with and without governors)

No Kernel auditor installed, no IO scheduler etc, just as it comes with the ROM. the Kernel auditor had some wakelocks so I blame the low score to this app. Changed in dev options: Limit background processes to : No background processes and Do not keep activities.

Phoenix ROM -------------------------------------0.38%/hour View attachment 3916665 Basic settings as the 0,16%/hour. BBS show a perfect clean run. Seems like one day its lower than the other day.. I guess it's just random luck to get a low %/hour.

Phoenix ROM -------------------------------------0.545%/hour View attachment 3916666 Governor: Interactive, io Internal: Noop. Rest same. Cant explain it, seems a huge difference to my record. Weird.

Phoenix ROM -------------------------------------0.227%/hour View attachment 3915425

Looks like changing the governor isn't helping, so I recommend to stick to Interactive (which was default anyways)

Governor CPU: Ondemand, rest is basic (IO = Cfq, aggressive multicore saving = Disabled - somehow it makes my phone reboot every time in combination with Ondemand and IO Noop, disabled touch boost)

Phoenix ROM -------------------------------------0.33%/hour View attachment 3914306

Kernel auditor app installed: Governor: interactive. IO governer: Noop for internal. No touchboost. Multicore Saving: Aggressive. Rest is same as below.

Phoenix ROM -------------------------------------0.16%/hour! View attachment 3913071 Calculation, see method above. When I look at the BBS log when it turned 95%, I see it went up to 0,18%/hour. View attachment 3913075. I think it's best to let the Battery history app let you save the timestamps when it turned 95% to get the exact moment and calculate the exact % so it could have been lower if I knew the last second before it turned 95%.

CM14, Haggert Kernel ---------------------------0.48%/hour.........Couldnt install Amplify, AppOppsXposed and special features in Greenify cus there's no Xposed for CM14 yet.. Bummer, guess we have to wait. Installed Powernap and SuperDoze and DisabledServices.

CM13 + Boeffla 3.3 beta4 ------------------------0.5% and 0,4%/hour, okay that didn't work... View attachment 3910944 & View attachment 3910945

Boeffla config: GPU governor Powersave, CPu: Light undervolt, external IO to cfq. Governor Ondemandplus, uninstalled Screenoff app, batterymode: power save, battery optimization (settings android) for all battery savers. (were off)

CM13 + Boeffla 3.3 beta2 ------------------------0.205%/hour View attachment 3907706. Calculation, see above.

Sweet. Could be higher when stopping the test at 95%.

When it reached 96% the average was 0.24%/hr = average 246 min.. (984 / 4%) (23:15 -> 15:39 timestamps 96% = 984 min. 60 x 4 / 984 = 0.24% per hour.

Amplify showed me more wakelocks in the past 19 hours so I limited those as well. Its like a learning process. I' ll tweak more and do a new test below. Exciting stuff! =)

I installed the boeffla config, and put the governor on: Ondemand and scheduler IO both on NOOP. No widgets on homescreen.

CM13 + Boeffla 3.3 beta4------------------------ Again 0.23%/hour. View attachment 3909923 . I saved another log a few hours before this one and it shows less voltage then the last log, how is that possible??? View attachment 3909924

I disabled the Keep awake function in Privacy Guard of Google Services Framework, disabled some other wakelocks that showed up. Clock was giving me many alarms so disabled the deskclock_on_quarter_hour alarm to 2400 secs. Deleted WakelockDetector (not using anyways). Added Greenify to Powernap. Boeffla config: CPU Voltage: Undervolting seems to work (initially it kept rebooting but I put the IO for external to default in boeffla config) The rest: Same settings as test above.

Section 1:

CM13 + Boeffla 3.3 beta2 ------------------------0.6%/hour View attachment 3907816

Phoenix ROM 14.2 ------------------------------- 0.4%/hour View attachment 3907818

Section 2:

(TESTS TERMINATED)

Timestamp calculation: Write down the exact time when you take out the charger. Wait a few hours, open the battery history and write down the latest timestamp it saved.

If I look at the percentage in my battery history: 100% = 11:54:39 @ 17-10-2016. It turned 96% at 15:36:43 the same day. According to the real time stamps: This is 222 minutes for 4% = 1.08%/hour.

Greenify with Xposed settings: Agressive doze, Wakeup Time Coalescing, Dont remove Notifications, Deep Hibernation, GCMPush, Greenifying system apps, reveal hidden sync.

Phoenix ROM 14.2 ------------------------------- 329/89/91 minutes (No explanation on the 329min, looks like an error...)

CM13 + Boeffla 3.3 beta1------------------------ 192 minutes (whatsapp not logged in)

OMEGA ROM------------------------------------- 172 minutes

CM13, ROM Kernel------------------------------- 161 minutes (whatsapp not logged in)

Alexander Rom, ROM Kernel------------------- 141 minutes

CM14 (11-10-2016) + ROM Kernel haggertk--- 140 minutes

Resurrection Remix------------------------------ 129 minutes

CM13, Boeffla 3.2---------------------------------- 74 minutes

Specification tests

Test 1: CM13, Boeffla 3.2 - 100, 99 (31 min), 98 (30 min), 97 (13 min), 96 (13 min), 95, (26 min), 94 (26 min), 93 (63 min), 92, (240 min), 91 (168 min). Average: 68 min.

Test 2: CM13, Boeffla 3.2 - 100, 99 (119 min), 98 (35 min), 97 (64 min), 96 (79 min). Average: 74 min.

Test 3: Alexander Rom, ROM Kernel - 100, 99 (27 min), 98 (21 min), 97 (30 min), 96 (53 min), 95 (106 min, 94 (192 min), 93 (513 min!!), 92 (189 min). Average: 141 min.

Test 4: CM13, ROM Kernel, Screen on for nearly 2 minutes, so could have been higher. - 100, 99 (56min), 98 (34 min), 97 (96 min), 96 (111 min), 95 (178 min), 94 (150) min), 93 (419 min), 92 (240 min). Average: 161 min.

Test 5: Resurrection Remix: 99 (32 min), 98 (12 min), 97 (29 min). 96 (86 min). 95 (91 min), 94 (522 min). Average: 129 min[/U][/B]

Test 6: Omega, 99 (44 min), 98 (27 min), 97 (80 min), 96 (123 min), 95 (126 min), 94 (157 min), 93 (520 min). Average: 172 min

Test 7: CM14 (cm-14.0-20161006-UNOFFICIAL-klte, HaggertK kernel): 100, 99 (103 min), 98 (120 min), 97 (150 min), 96 (141 min). Average 128 min.

Test 8: Phoenix Rom, I had my screen on for 1 second for 5 times in these 3 days. No whatsapp logged in, just installed. Okay, this is starting to mindblow me.. So I started with 100% and took out the charger at @ 19:48 on 08-10-2016. I stopped at 19:02 (it turned 87% on this moment) on the 11/10. that's an average of... 329min..

Specification: 99 (161 min), 98 (152 min), 97 (209 min), 96 (238 min), 95 (242 min), 94 (284 min), 93 (898 min), 92 (438 min), 91 (307 min), 90 (360 min), 89 (324 min), 88 (336 min), 87 (326 min)

Total wakelocks in those 3 days are very few! System UI 4x, SCPM Client 9x, Samsung Keyboard 1x. That must explain it.

Test 9: CM13 + Updated Boeffla 3.3[/SIZE][/B] (beta 3.3). Took the charger out on 11-10-2016 @ 23:11. On 13-10-2016 at 16:33 it turned 87%. That's an average of.. 192 min Wakelocks: System UI 4x, Greenify 1x, Clock 5x, Phone 1x. Even less than the Phoenix, so it's surprising that it drains more battery.. Results are better than before the update, but not anywhere near Phoenix.

Test 10. CM14 (11-10-2016) + ROM Kernel haggertk + Android 7 Gapps 9.8.77 + No Greenify + No Xposed. Started on 20:38 13/10. Ended on 14-10-2016, it turned 91% on 17:35. This is an average of.. 140 min.. Not anywhere near Phoenix.

Test 11. Phoenix ROM, Surprising, started on 15-10-2016 on 00:55. Now at 12:49 it's 91%. That's an average of 89 minutes! Thats way worse than the first test. No differences in settings between the Phoenix Rom tests.. The 329 Min must be an error.

The 2nd and 3rd test show 89 and 91 minutes. HUGE Difference. I can't explain the difference so I did a 4th test:

Test 4

- Phoenix: Installed: Betterbatterystats, Amplifying, Greenify etc according to this thread: http://xdaforums.com/android/general/guide-extreme-battery-life-t3095884. Then let the screen off for a few hours. Limit the highest wakelocks. RILJ0 seemed to be a high wakelock, so limit it to 800 seconds. And the ContextManager to 99999 seconds. I put in another Simcard, charged to 100%, reboot. Let it charge for 10 min, Reset Amplify, take out charger. Started on 16/10/2016 @ 16:45:00. At 17/10 at 05:09 it turned 95%. Average: 148 minutes....

I'm starting to wonder how I got to 329 min in the first test after amplifying wakelocks, alarms, services, greenifying, powernap etc.

Test 13. CM13 + Boeffla 3.3 beta2. No widgets on homescreen, everything disabled. Installed Amplify and limited most used wakelocks, alarms and services. Powernap enhanced mode, appsxposed disabled Google Services. In Progress, started at 11:54.