[HTC 10 Guides, News, & Discussion] Haldi4803:
So, there are so many PnP tweaks out there... what do they do? what do they achieve?

Running a Stock 1.92.709.1 Rom with Magisk v6 and Xposed+Root but except from that fully stock i made some benchmarks.

Benchmarking Setup:

Put the phone in Flight mode to stop signal fluctuations

WiFi activated for Mobile Data

Manual minimum Screen Brightness

Sync Off

Location Off

Using the Repetitouch App i created a "Normal" Benchmark Parcours, this includes:

Browsing trough the App Drawer and Homescreen for 30 seconds.

Opening Chrome and checking computerbase.de Homepage

Reading(scrolling fastly) an article on said homepage.

Opening google Maps and zooming in and out

Opening Mail and scrolling trough

Opening Whatsapp and scrolling trough

Opening Tapatalk and scrolling trough

Closing all apps

And this Loop is repeating itself untill i stop it, mainly after 1 hour.

Why 1 hour? Because i want to see Batterydrain, and you get +-2% Error margin from Android battery percentage, so the Longer the better, but aint nobody got time for that.

And i want to force throttling. Doing a 5 Minute Benchmark on a Cold phone will have a totally different result than a 30min run where the phone gets over 34°C, and sometimes we DO use our phone for a nonstop 30 minutes ;)

While i say *normal* Benchmark this is a rather high load. Not much downtime between the scrolling parts.

On Stock settings i get about 4.5 - 5h SoT (with 100% screen active time)

But well yeah, we want to see how the Governor Settings work, not how the CPU idles around ;)

Results:

First thing first:

Now then, for a closer look at how the settings force the CPU to react to the exact same usage:

Detailed Results:

Lot of Screenshots so i put it in a Hide Tag :)

Stock

22% Battery lost per Hour

37°C End CPU-Temperature after the Benchmark

Butterfly v1

23% Battery lost per Hour

37°C End CPU-Temperature after the Benchmark

Ghostpepper v3

25% Battery lost per Hour

38°C End CPU-Temperature after the Benchmark

Glassfish v1

17% Battery lost per Hour

34°C End CPU-Temperature after the Benchmark

Hawktail v2 Raised Minimum

21% Battery lost per Hour

36°C End CPU-Temperature after the Benchmark

Ivicask PnPtweaks v17

17% Battery lost per Hour

35°C End CPU-Temperature after the Benchmark

Flaws and Errors:

As always nothing is perfect!

The major problem here is that i don't have proper power measuring equiment, so i have to rely on the android internal battery statistics.

So if it shows me 95% Battery when i begin this could drop to 94% in a second or stay on 95% for way to long because it just dropped from 96%. So the Start and End point of measuring could be +-1% wrong. Doing a longer test reduces the significance of this error but can never fully erase it. having a +-2 Error on a value of 22 is a huge span of +-9% but well..... i'm not gonna do longer than 1hour tests.

Another thing i realised after starting was that i did not track the "transitions" next to the "Time_in_state" file there is a "total_trans" log. This shows how many times the CPU has switched frequencies. i.e from 307,2 to 1324,8 when a touch input is registered equals one jump. Especially with different governors this is a very interesting value to see how a governor reacts. Sadly there is only a "total_trans" log which shows one huge number. For the GPU there is a complex table that shows start frequency, target frequency and number of jumps for all possible frequencies switches.

While we're at the "Time_in_state" file exists only for CPU0 and CPU2, because CPU 1 and CPU3 are linked they don't have a dedicated Stats file. Good? Well... uh.... yes, they do have the same frequency inside the Big or Little cluster. But there is still an issue with HTC's Throttling taking away all tasks from CPU3 when the SoC gets too hot. So the Load on the two small cores will increase, the frequency will rise, but it will not decrease on the big cores as one of them is still working as always.... uhgs

Well... that's it for now :)