[Updated 11-Dec-2018][oxygen] Battery Life / Performance Benchmarks - AOSP Roms

[Hard_Rock83]

Have more ArrowOS benchmarks:



For those arriving now, there is info on this table hidden below:

I am now measuring idle battery drain. For every benchmark I leave the phone alone for as long as possible using AccuBattery to register screen off battery drain.

The above table show a series of benchmarks done with @ROMFACTORY's RRO using different kernel builds, followed by another series of benchmarks of @Hard_Rock83's ArrowOS latest builds.

The table columns need some explanation:

Score - PC Mark Battery Benchmark performance score
SOT - PC Mark SOT (Screen On Time) under heavy mixed usage for 95% battery drain
SOFF T - Screen ofF time with phone idle after the benchmark in days/hours/minutes
SOFF % - Battery drop percentage as measured by AccuBattery
%/hour - Battery drain percentage per hour calculated using previous numbers

For more info on PC Mark benchmarks please read the OP (Opening Post)

It is difficult to catch up with @Hard_Rock83. A new Arrow build comes almost everyday.

@jbmc83, another bench of v7 is just starting.

For those curious with other Pie Roms, for now I will focus on ArrowOS builds, mainly because IMHO it is our best Pìe option.

V8 arrow will be published today with another upstreamnd kernel 3.18.128 and merged CAF tag.and tons of features.HR kernel might be giving best sot on Oreo due to fact that on pie we have more performance and pie is still new in sources which continuously improving day by day..

But performance with that much sot is fine I guess..but still I will check and see if further we can push battery somehow on pie.

 

[[email protected]]

Have more ArrowOS benchmarks:



For those arriving now, there is info on this table hidden below:

I am now measuring idle battery drain. For every benchmark I leave the phone alone for as long as possible using AccuBattery to register screen off battery drain.

The above table show a series of benchmarks done with @ROMFACTORY's RRO using different kernel builds, followed by another series of benchmarks of @Hard_Rock83's ArrowOS latest builds.

The table columns need some explanation:

Score - PC Mark Battery Benchmark performance score
SOT - PC Mark SOT (Screen On Time) under heavy mixed usage for 95% battery drain
SOFF T - Screen ofF time with phone idle after the benchmark in days/hours/minutes
SOFF % - Battery drop percentage as measured by AccuBattery
%/hour - Battery drain percentage per hour calculated using previous numbers

For more info on PC Mark benchmarks please read the OP (Opening Post)

It is difficult to catch up with @Hard_Rock83. A new Arrow build comes almost everyday.

@jbmc83, another bench of v7 is just starting.

For those curious with other Pie Roms, for now I will focus on ArrowOS builds, mainly because IMHO it is our best Pìe option.

I don't know why but I always got reverse sot in RRO and Arrow Pie.

I. e. I got more sot in arrow pie vs rro with same kernel used by you.

 

[kalawy]

Good News and bad news.

I found out the reason of the large SOT variances in my benchmarks.

You are probably aware that I start every benchmark with battery at 80%.

Have you ever wondered how I achieve this? Simple - I use an app that stops charging at an specified percentage.

The app I use and recommend is [APP][ROOT][4.0+]Battery Charge Limit.

This is a tricky app. The way to control charging varies a lot between devices.

Somehow, for the Max 2, the way the app chooses by default to control charging seems to work, but does not!!

Yes, charging LED turns off and yes, battery percentage indicator stays at 80%, but the battery keeps charging.

I figured this out after one of my runs with Hardrock kernel 13.1 reached 22 hours SOT with extreme overclocking. This simply could not be.

After this result I started checking battery voltage levels and found the bug.

Did some research and tests and was able to configure BCL to properly stop the charging at desired level.

All you have to do is change the control file to "qpnp-smbcharger-18" and voilá, all is good again.

The bad new is that the many dozens of benchmarks I have run so far may not be trusted.

The problem only affects the SOT, of course. Performance scores are good regardless of the battery level problem.

I found some ways to figure out bad benchmarks and filtered the ones I ran for Oreo roms. This is my last preview adjusted:



This explains why @Jay_B´s MSM Xtended got the 20 hours SOT. Unfortunately a false result.

Anyway all results from now on will be free from this inconsistency.

I was in the middle of testing kernels using the same rom. RRO 2018-0701.

Still have to decide If I will try to save all good benchmarks from this series or start over again.

My kids school vacation is over this weekend. At least I will have more time from now on.

i have 2 files that mcs can use .. both say they disable charging but the phone says 90 while it's actually 100

mcs is tricky after every clean install and i forget which file i used with the previous rom
what is the file exact location of the file you used

also .. is the app better than magisk's mcs ?

 

[m1n15s]

i have 2 files that mcs can use .. both say they disable charging but the phone says 90 while it's actually 100

mcs is tricky after every clean install and i forget which file i used with the previous rom
what is the file exact location of the file you used

also .. is the app better than magisk's mcs ?

Better u use battery limit charge from playstore

 

[kalawy]

Better u use battery limit charge from playstore

i tried the app but the default control file works as a pseudo effect

that's why i asked for the location of the control file to add in the app

 

[svbarbosa]

i have 2 files that mcs can use .. both say they disable charging but the phone says 90 while it's actually 100

mcs is tricky after every clean install and i forget which file i used with the previous rom
what is the file exact location of the file you used

also .. is the app better than magisk's mcs ?

Better u use battery limit charge from playstore

i tried the app but the default control file works as a pseudo effect

that's why i asked for the location of the control file to add in the app

I did not test MCS. Reading its instructions I did not find a good reason to replace Battery Charge Limit.

To make BCL work on our Mi Max 2 all you have to do is change the control file to "qpnp-smbcharger-18".

Please refer to my previous post #87 for more info.

 

[svbarbosa]

ArrowOS v8 with some alternative CPU governors:

Thought I would catch up with @Hard_Rock83. Silly me! v9 is out.

This time I tried three different CPU governors:

• alucard - is an old favorite of mine. Performance increased a little with no loss in SOT.
• darkness - SOT increases by 1 hour and 30 minutes, but performance suffers.
• smartmax - almost same SOT as darkness with a smaller performance degradation.

So alucard is a good alternative to replace default interactive governor.

@Hard_Rock83, would you like me to try any other cpu governor?


For those here for the first time more info below:

I am now measuring idle battery drain. For every benchmark I leave the phone alone for as long as possible using AccuBattery to register screen off battery drain.

The above table show a series of benchmarks done with @ROMFACTORY's RRO using different kernel builds, followed by another series of benchmarks of @Hard_Rock83's ArrowOS latest builds.

The table columns need some explanation:

Score - PC Mark Battery Benchmark performance score
SOT - PC Mark SOT (Screen On Time) under heavy mixed usage for 95% battery drain
SOFF T - Screen ofF time with phone idle after the benchmark in days/hours/minutes
SOFF % - Battery drop percentage as measured by AccuBattery
%/hour - Battery drain percentage per hour calculated using previous numbers

For more info on PC Mark benchmarks please read the OP (Opening Post)

 

[Hard_Rock83]

ArrowOS v8 with some alternative CPU governors:



Info on this table hidden below:

I am now measuring idle battery drain. For every benchmark I leave the phone alone for as long as possible using AccuBattery to register screen off battery drain.

The above table show a series of benchmarks done with @ROMFACTORY's RRO using different kernel builds, followed by another series of benchmarks of @Hard_Rock83's ArrowOS latest builds.

The table columns need some explanation:

Score - PC Mark Battery Benchmark performance score
SOT - PC Mark SOT (Screen On Time) under heavy mixed usage for 95% battery drain
SOFF T - Screen ofF time with phone idle after the benchmark in days/hours/minutes
SOFF % - Battery drop percentage as measured by AccuBattery
%/hour - Battery drain percentage per hour calculated using previous numbers

For more info on PC Mark benchmarks please read the OP (Opening Post)

Thought this time I would catch up with @Hard_Rock83. Silly me! v9 is out.

This time I tried three different CPU governors:

alucard - is an old favorite of mine. Performance increased a little with no loss in SOT.
darkness - SOT increases by 1 hour and 30 minutes, but performance suffers.
smartmax - almost same SOT as darkness with a smaller performance degradation.


So alucard is a good alternative to replace default interactive governor.

@Hard_Rock83, would you like me to try any other cpu governor?

Amazing . Bro can u check with dynainteractive governor.its not very fast but well balanced governor and should be providing much backup with balanced speed.

 

[Ruguoli]

I like zzmoove And smartmass- eps .

 

[m1n15s]

Make all and lets see wich one wins :laugh::laugh:

 

[Hard_Rock83]

@svbarbosa i want you to test max 2 life with my 1.3 pie kernel with msm hotplug on.

Let me know the result...i will be waiting for it:fingers-crossed:

 

[svbarbosa]

CPU Governors

Better late then never...

I took the time to run a PC Mark Performance benchmark for each CPU Governor available in @Hard_Rock83's ArrowOS v8.

This is a quick test that takes few minutes to run, using the same philosophy as the battery benchmark of using day-to-day tasks to produce the score.

Here are the results for the 33 CPU Governors:

Next I will work with the new pie kernel with CPU Hotplug.

 

[Hard_Rock83]

Better late then never...

I took the time to run a PC Mark Performance benchmark for each CPU Governor available in @Hard_Rock83's ArrowOS v8.

This is a quick test that takes few minutes to run, using the same philosophy as the battery benchmark of using day-to-day tasks to produce the score.

Here are the results for the 33 CPU Governors:



Next I will work with the new pie kernel with CPU Hotplug.

Test with 1.5 kernel and alucard hotplug ir u can test all hotplugs..

I think dont go for performance test..its all fine..but sot and backup with hotplugs on..test for all hotplugs..and choose interactive, alucard, intelliactive and dynainteractive governors..

Test for your usual sot table..

 

[svbarbosa]

Here are the screenshots missing in my previous post.

XDA has a 20 files limit per post.

 

[svbarbosa]

HR Pie Kernel with CPU Hotplugs

Here are the first numbers of @Hard_Rock83's Pie kernel with CPU Hotplugs.

See results at the bottom of this table:

The last benchmark with interactive CPU governor and MSM Hotplug show a good Screen Off battery drain. Clearly better than the previous kernels with no hotplug.

I will make one more benchmark with Arrow v10 and kernel v1.5 using alucard governor and alucard hotplug.

Then move to Arrow v11.

 

[m1n15s]

Here are the first numbers of @Hard_Rock83's Pie kernel with CPU Hotplugs.

See results at the bottom of this table:



The last benchmark with interactive CPU governor and MSM Hotplug show a good Screen Off battery drain. Clearly better than the previous kernels with no hotplug.

I will make one more benchmark with Arrow v10 and kernel v1.5 using alucard governor and alucard hotplug.

Then move to Arrow v11.

By numbers oreo was more battery friendly than pie 10% to 15%
But performance pie is a little bit better.?i guess

 

[pauldrudd]

Yep I'm noticing battery life is slightly lower than Oreo or Nougat (on Pie Havoc OS and kernel 1.5) but it's a small price to pay in my opinion. We are extremely lucky to have such outstanding support for our device with regularly updated ROMs and kernel, with tons of customisations and eye-opening clever stuff like hotplugs and amazing performance!

 

[svbarbosa]

Just added battery benchmark for alucard governor with alucard hotplug:

The alucard/alucard combination shows improvement in performance score keeping almost the same SOT.

As always @Hard_Rock83 never stops and there are new kernel builds out.

It is hard to keep up with HardRock.