Haldi's Benchmark Thread for Governors&Overclocking&Testing the HTC 10

Search This thread

Haldi4803

Senior Member
Introduction:
Hello..... people.... i'd love to say friends but i'm new in the HTC section on XDA.
I've been lurking around in the Sony subforums on XDA for a while and owned 3 Sony devices, the X10i, the Z and the Z2. Sadly my Z2 broke down due to waterdmg last month and i bought a cheap replacement phone. Worked pretty well..... until i saw the HTC 10 exhibited in Taipei. Playing around with it for a while made me want to buy a new phone, after more indepth research about the LG G5 and the SGS7 my patience waiting for news about the Zuk 2 or OnePlus 3 was gone and i just bought a HTC 10 :) Luckily prices are pretty cheap in Taiwan. Worst case i can sell it back home for same value.
So yeah, about Me.... I'm not a developer or anything. My coding skills are horrible, more like scripting to fulfill my needs.
I'm a tech Enthusiast that loves gadgets and everything that's new. I spend money on Kickstarter to often just because i want to see tomorrows technology today. While there is the love for the technology there is also the love for knowledge. Just having something is no fun, knowing how it works is what makes it interesting. Same goes for smartphones. Android is awesome in this case, you can tamper around with so many settings and change so many things.
In the last few years i had so much entertainment with my phones..... looking around the Forums here, there seem to be some competent people around, I'm sure I'm gonna have a great time here :)


About:
This thread is for gathering informations about Governors, their efficiency, their reaction in daily world usage and not in Antutu benchmark. Or at least that was the original intention. I also did some Benchmarks on Overclocked and Undervolted devices to check if you really gain any benefit. Batterylife was a big concern so i've measured absolut maximum possible and absolut minimum screen on time. After the Z2 Quickcharge hack was made (Japanese Z2 has it, European not) i've started doing more specific Charging time Benchmarks, and i dare say you won't find many as specific charging benchmarks around the web.
Well yeah.... in short whatever i take an interest in i'll benchmark it and document it troughly. :)
You can see my old threads for the Xperia Z2 or the Xperia Z to get an idea about what i'm talking.

Benchmarking:
Powerdrain: Find out how much the Phone is using under specific circumstances.
Governor: Find out how a governor acts on a specific benchmark course.
Charging: How fast does the Device charge from 1% to 100%


Benchmarking Apps:
Qualcomm Trepn Profiler: CPU and GPU frequency and load, also Powerdrain
Repetitouch: To create custom Benchmarks that simulate normal everyday usage.
BatteryLog: For Charging Benchmark, Voltage and Battery% per Minute
GameBench: For FPS in games. (Make sure you deactivate Screenshot function for HTC10)

Benchmarking Hardware:
YZX Powermonitor: USB 3.0 QC3.0 4-13V 0-3A USB A Male-> USB A Female Powermonitor that measures Voltage and Current passing trough.

Benchmarking Process and Display of Data:
Can all be read in Post NR 80
GPU Logs in Post NR48

More......
I guess that's it for now.
I'll add more if there is more to add about benchmarking.
 
Last edited:

Haldi4803

Senior Member
Index:
  • Powermeasuring with Trepn Profiler & Wallcharger Post NR3
  • Idle Powerdrain with Minimum and Maximum Screenbrightness Post NR4
  • Thermal Throttling on CPU and GPU Post NR5
  • Charging Stock Charger Post NR6
  • Charging QC2.0 Aukey PU-A28 Post NR7
  • Charging Compare QC3.0 vs QC 2.0 Post NR8
  • Charging Efficiency Post NR9
  • Camerabug in old Firmware, max 0.7sec Shutter Post NR10 (now Fixed in 1.80)
  • Camera High speed test Post NR11
  • Charging in Cold environement Post NR18
  • Testing Ghostpepper v8 profile Post NR21
  • Testing Ghostpepper v9 profile Post NR22
  • RAW performance of SD820 in DMIPS, Singlecore, 2 Cores, 3 cores, all cores Post NR27
  • Energy Efficiency, small cores vs Big cores Post NR30
  • Gaming and Throttling on Stock Kernel (1.80.709.5) Post NR35
  • Gaming with PnP&Thermals tweaks Post NR36
  • More Tests about Efficiency of Small and Big Cores Post NR38
  • Charging on 1.80.709.1 Firmware Post NR39
  • Charging while using the device Post NR40
  • Video Analyse Frameskipping? Post NR41
  • Guess what you will find in PostNR42
  • Screen Batterydrain in Idle Post NR43
  • PnP Tweaks compared PostNR46
  • Elemental X Kernel v19 with GPU Transitions Post NR49
  • Battery Discharge Linearity Post NR50
  • Elemental X Kernel v19 + Ivicask's PnP Tweaks v17 UC/OC/Powersafe Post NR51
  • Charging Beanstalk CM13 Post NR59
  • GPU Benchmarks stop at 58FPS.... Post NR71
  • Google account during Doze time, how much is caused by Google Services? Post NR73
  • Power_profile.xml how accurate is it? Post NR74
  • What about the Power_profile.xml from other Devices? Post NR75
  • 6 Years of Video recording Post NR76
  • Charging on 1.96.709.5 Post NR77
  • Thermal Throttling in a Longterm test Post NR78
  • How I Benchmark / Create those Graphs Post NR80
  • Audio Testing.... or something like that... Post NR84
  • Idle Screen Only Powerdrain Post NR85
  • Charging 2.41.709.71 and Battery Deterioration Post NR86
  • Charging 3.16.709.3 Stock Oreo Post NR87
  • Oreo: Standby Drain in Flightmode Post NR 89
  • Oreo: Standby Drain in Flightmode Safemode Post NR 90
  • Comparison of the both above Post NR 91
  • Comparison in Daily Usage Scenario Post NR 96
  • Charging LOS 15.1 with Nebula Alpha Post NR 97
  • Per Core Powerdrain, try nr 2 Post NR 98
  • Smartpixels Feature on IPS not usefull... Post NR 99
 
Last edited:

Haldi4803

Senior Member
Powermeasuring:
How do we know how much power our device is using right now?
the Ampere App shows a rough estimate, Qualcomm Trepn profiler shows a better BatteryPower value.
The best way would be to dismantle the phone and use hardware on the wire between battery and phone.
This does seem a little bit extreme so there is another way, plug the phone to the wallcharger and measure how much the charger draws.

So.... are all these measurements accurate?

I've done the comparison: While being plugged to the wall what does the Hardware say, what does Trepn Profiler say.
One thing needs to be said here. On SD810 and onwards Qualcomm decided to limit the "Direct BatteryPower" to once every 30 seconds. If you want a faster update you need "estimated BatteryPower*", thats also what is used when the phone is connected to a charger.
So i did one Benchmark (Stability Test v2.7 CPU Bench) while connected to the Wallcharger at 100% and transfered the info via bluetooth to my phone, at the same time run Trepn Profiler in estimated* mode.
To make sure being connected to the charger does not make a difference i've unplugged the phone and did another run in estimated* mode.
Then i made the 3rd run unplugged while using direct batterypower mode.

Here is the Graph of all 3 runs consolidated into one:
mC1Cp5Y.png


As you can see the Estimated* graph is far off from the direct and wallcharger. (EDIT: Seems like the early version of Trepn had issues with Big cores Clock and other stuff so estimated usage was totally off)
The problem with the direct mode is that it only gets updated once every 30 seconds, so to get accurate results you need to have stable conditions for 30s or more.

So yeah.... thats the situation under heavy load. But what about Idle?
Maybe it works better when idle? Nope.
I've set manual Brightness to the minimum. Activated Flightmode, disconnected WiFi (bluetooth still active for measuring.....) Screen timeout to 1h and left the phone alone for 10 minutes on the Homescreen.

ALBaM3H.png


Same problem here. The Wallcharger shows way more than direct which is also way over estimated mode.
Why is the charger so much more? No idea. I've made sure the phone was on 100% battery, and the Powermeter shows 0.032A and 5.93V so about 0.19W when the screen is off.

Here are the Screenshots that show CPU load and Frequencies.
Estimated run while plugged:
https://drive.google.com/file/d/15YLBTjgcK69qNvL14Ubn67qlmuzEn68HLQ/view?usp=sharing
https://drive.google.com/file/d/1nVwAFMrJDhcYhor0Bq9oDLDgg4alF8vzWg/view?usp=sharing

Direct Power run while unplugged:
https://drive.google.com/file/d/1wgrCGWa1afsjjXBXmqxPkxauL_zbS9YsRg/view?usp=sharing
https://drive.google.com/file/d/1mHo6uV0BuAgj7HDHPgurRVZAxeuifPBMJw/view?usp=sharing


I've contacted the Dev's from Qualcomm and asked what they have to say about this, because their last statement was "estimated mode should be fairly accurate"
(EDIT: Seems like the early version of Trepn had issues with Big cores Clock and other stuff so estimated usage was totally off)
 
Last edited:

Haldi4803

Senior Member
Screen Brightness

So,
I've been doing these Idle Benchmarks with minimum brightness, so why not just do another with maximum brightness. All in Manual Screen Brightness so it's not the brightest it can get but the brightest you can set.

69RZmMH.png


Average usage in Watt:
Min Wallcharger: 1.23W
Max Wallcharger: 1.66W
Difference: 0.43W

Min Estimated: 0.14W
Max Estimated: 0.63W
Difference: 0.49W


I might be doing another test in direct mode when i have to much time on my hands :)
 
Last edited:

Haldi4803

Senior Member
Performance and Throttling:

CPU:
Originally the SD820 has 2 Cores at 2150,4mhz and 2 cores at 1593,6mhz
Because this can use almost 10W it's impossible to cool passive. So after a short while the CPU starts throttling to prevent overheating.
I currently do not have Root so i don't see my CPU temperature in the status bar but have to open CPU-Z which is way to much hassle to find out a what temperature the SoC starts throttling.
After a longer time stressed out the CPU (and CPU Only) rests at 1324,8mhz on the 2 fast cores and if that's still not enough all 4 cores will drop down to 1324,8mhz

in this Stabilitytes v2.7 Benchmark i did with a cold phone (Room temperature 24°C) the fast cores went down to 1324,8mhz after 30 Seconds and the slow cores reduced their speed from 1593,6mhz to 1324,8mhz at the 200 seconds mark. This frequency (1324,8mhz on all cores) persisted during the 10 Minute Benchmark.

Screenshot_20160510-183622.png



If you activate the Powersafe mode in settings, your CPU clockspeed will also be Limited to 1324,8mhz.



GPU:
The Adreno530 is by far the fastest current Mobile GPU, but thanks to the 2560x1440pixel screen we really need this performance. If you don't have enough FPS in your games, activate Boost+ GameBoost. It reduces screenresolution for this game to 1920x1080.
To give you an impression on how fast.... if we take the old Epic Citadel Benchmark and keep it running in UltraHigh Quality.... we have about 70% GPU usage ^^

Screenshot_20160510-193608.png

Screenshot_20160510-194806.png





But.... it's not a sustainable performance. The top clock of 625mhz cannot be kept for very long.

TRex_Rundown_H10.png

(Source: Anandtech)

More detailed Benchmarks will come when i've found a great game to test.....
recommendations are welcome :)
 
Last edited:

Haldi4803

Senior Member
So.... here we go. First full charging Benchmark on my HTC 10 completely logged with an USB Powermeter.
From 1% to 100% takes 95 Minutes.

Statistics from BatteryLog app
1d0af0fcbdd10d40a5672fa5a6fed2ae.jpg


And the Voltage and Current recorded via external Powermeter.
153cb2e9ad5bd9139ce65db6a66a2335.jpg


Funny How the charge control completely kills the charging to switch Voltage in Big steps.... as seen on Minute 10 and 48.

Another fun fact is that we see the Battery reach 100% After 95 Minutes.
But does it stop charging? No!
It continues until 150 Minutes..... yes no joke. 2.5 hours! That's 1 hour longer than it needed to reach 100%
31c22dcdc3ff5f31cb457e7f0dbf906b.jpg



And one more Longtime Charge.
What happens if you leave your charger connected over night?
a87a24cb78b3fd051644b5a1aa1c12c2.jpg

(Nope, not the same date as the 3 above, was on another charge)


(If the pictures are to small, blame Tapatalk resize algorithm. I will Upload full size when I'm back at my PC, which might be somewhen between 2 and 6 months.)
 
Last edited:

Haldi4803

Senior Member
Charging Efficiency:
Using the USB Powermonitor we have a decent Information about how much power flows out of the Wallcharger. U*I=P and we have the Watt flowing out.
On the phone side this seems a little more complicated. To get an accurate value it would be nice to tear down the phone and connect all important points to a Hardware measurement Tool. But yeah. No one is gonna break down his private phone for that.
So we have to take a look at Software.
Battery Monitor Widget does Report the current flowing into the Battery.... same as Ampere.
If we assume the Battery is getting charged at 4.4V we can again calculate the Watt inside the phone.
Comparing the Outside and Inside Watt against each other we have the efficiency. Or at least something that does look like that ....

Quick Charge 3.0
1e2fba89919d2a3c90cd527285058e30.jpg



Quick Charge 2.0
501f9480af504e39fb2ec475a973aaae.jpg


I tried to synchronize the graphs but yeah... seems like the logging is a bit unexact. Not sure which one tough.
 

Haldi4803

Senior Member
Camera Testing:
EXIF Info says our Camera does not take 2sec pictures but 1 second only...
How true is that?

I tried different Tests but found out that the blur Buster UFO Test at 480pixel/sec gives the best results.
Link: http://www.testufo.com

To compare vs reality I took an EOS 600D and a Macbook with Chrome.

0.5 seconds.
0f21e2f013889871a4404162bb187b1c.jpg


1 second
dfe8c2dac800988c3c87a621cb6dadfe.jpg


2 seconds
d330c7ed3e3a64afc07df16ae2eacf6e.jpg


Then I took my HTC 10 with 1.30.709.1 and HTC Camera App 8.10.748210 Pro Mode JPG iso 100 and set Shutter to:

0.5 seconds
a42ffe3a9bd7289f4e33edcba8840d9c.jpg


1 second
ce93629ba740e5e9ef5cdd9dfa9c87f3.jpg


2 seconds
0d621524074c55207b2f39650a8de8d6.jpg



As you can see from 0.5 to 1 second is nearly no difference and 2 seconds surely doesnt look like 2 seconds from the DSLR at all! What are you doing HTC?


Original files:
https://drive.google.com/folderview?id=0BwqG3liwGXQHVlIyOGZVSWpqOG8

Edit: 17.07.2016
In the latest 1.80 Update this Bug has been fixed :)

0.6 Seconds:
https://drive.google.com/file/d/0BwqG3liwGXQHbVhkVHBSLWVZd0E/view

1 Second:
https://drive.google.com/file/d/0BwqG3liwGXQHYjRibXFWMkkxTVE/view

2 Seconds:
https://drive.google.com/file/d/0BwqG3liwGXQHU2t4LVJIcEZ5eTQ/view
 
Last edited:
  • Like
Reactions: paul_59

Haldi4803

Senior Member
Well....We did the slow Tests. So now come the fast ones.
How do you do that? You need a fast object. 60hz screen? Nope...
Well what did I have around? A fan xD

Auto:
1/30 iso 250
3b2f3a2f623a1eaf152dc7bea26d668f.jpg


Pro Mode jpg.
1/100 iso 756
c8006f0c3b1455211e412e700ad0207d.jpg


1/500 iso 3465
26c2bfabe931c8cc7863fca3821072e6.jpg


Or with Flash
1/500 iso 400
dc5badea16832b126961d784139c31fb.jpg


1/1000 iso 400
7e172457eacf14afeffd7259c5cf605d.jpg


1/2000 iso 800
fda94533b8b42a2c0bb1619ad73cffd8.jpg


1/4000 iso 1600
8fd3c6e75ebbe9e2538dbcede7aba827.jpg


1/8000 iso 3200
f2b51123563cbb2f10710b3b746c4715.jpg


All pictures in original size on gDrive
https://drive.google.com/folderview?id=0BwqG3liwGXQHRlBCUDNIX05BZk0
 

Haldi4803

Senior Member
Memo to myself:
Code:
&devfreq_cpufreq {
m4m-cpufreq {
cpu-to-dev-map-0 =
<  307200   307200 >,
<  422400   307200 >,
<  480000   307200 >,
<  556800   307200 >,
<  652800   384000 >,
<  729600   460800 >,
<  844800   537600 >,
<  960000   672000 >,
< 1036800   672000 >,
< 1113600   825600 >,
< 1190400   825600 >,
< 1228800   902400 >,
< 1324800  1056000 >,
< 1401600  1132800 >,
< 1478400  1190400 >,
< 1593600  1382400 >,
< 1728000  1382400 >;
cpu-to-dev-map-2 =
<  480000  307200 >,
<  556800  307200 >,
<  652800  307200 >,
<  729600  307200 >,
<  806400  384000 >,
<  883200  460800 >,
<  940800  537600 >,
< 1036800  595200 >,
< 1113600  672000 >,
< 1190400  672000 >,
< 1248000  748800 >,
< 1324800  825600 >,
< 1401600  902400 >,
< 1478400  979200 >,
< 1555200 1056000 >,
< 1632000 1190400 >,
< 1708800 1228800 >,
< 1785600 1305600 >,
< 1824000 1382400 >,
< 1920000 1459200 >,
< 1996800 1593600 >,
< 2073600 1593600 >,
< 2150400 1593600 >,
< 2265600 1593600 >;
};

mincpubw-cpufreq {
cpu-to-dev-map-0 =
< 1728000 1525 >;
cpu-to-dev-map-2 =
< 2073600 1525 >,
< 2150400 5195 >,
< 2265600 5195 >;
};
Small cores bench:
307
556
652
1036
1113
1324
1401
1478
1593

Big cores bench:
307
556
652
1036
1113
1324
1555
1824
1920
1996
2073
2150
 

punti_z

Member
Feb 18, 2012
27
0
Can someone post the FPS (over time) difference while running games/benchmarks with and without boost+ .. like sustained FPS on 1440p and then on 1080p.. i have been hunting around for numbers on this but cant find anything.
 

hamdir

Recognized Contributor
Aug 13, 2008
33,281
27,139
Canada
twitter.com
HTC U12+
Samsung Galaxy S21
Can someone post the FPS (over time) difference while running games/benchmarks with and without boost+ .. like sustained FPS on 1440p and then on 1080p.. i have been hunting around for numbers on this but cant find anything.

37fps vs 60fps in Trex long term test, Haldi posted the car chase test somewhere but it was also around 2x, so using Boost+ is essential unless you want to end with M8 like graphics speed
 
Last edited:

Haldi4803

Senior Member
Can someone post the FPS (over time) difference while running games/benchmarks with and without boost+ .. like sustained FPS on 1440p and then on 1080p.. i have been hunting around for numbers on this but cant find anything.
External factors always matter in this Benches.
Whats your room temperature?
Do you have Sunlight on your phone?
What's the screen brightness?
Whats the PhoneCase temperature?

Depending on these values Throttling will start earlier or later.


Gesendet von meinem LENNY2 mit Tapatalk
 

Haldi4803

Senior Member
I thought so.....
Chargig the HTC 10 is NOT Sustainable. The phone throttles charging to safe the Battery from Overheating.
To proof this i've put my phone in the fridge while charging. (you don't have to tell me, I'm fully aware that I'm crazy!)

9aa881b99384df1059ed5647d1a87c04.jpg

6a48b4d1a23770a0a6fa38c525497929.jpg


If we compare the charging duration its about the same.
But we can see the BatteryVoltage is waaayyy higher. Probably due the cold Battery.
And. We don't see the charging Votage droping to 4.6V
Its constantly on 7V



So.... here we go. First full charging Benchmark on my HTC 10 completely logged with an USB Powermeter.
From 1% to 100% takes 95 Minutes.

Statistics from BatteryLog app
1d0af0fcbdd10d40a5672fa5a6fed2ae.jpg


And the Voltage and Current recorded via external Powermeter.
153cb2e9ad5bd9139ce65db6a66a2335.jpg
 

ChronoReverse

Senior Member
Jun 14, 2010
1,360
247
I wonder if it'll be possible to find the "most efficient" frequencies (perhaps hold a particular frequency and grind out a fixed workload) where energy over work is minimized for the CPU and GPU.

Very interesting information though, thanks for the graphs and tests.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    Introduction:
    Hello..... people.... i'd love to say friends but i'm new in the HTC section on XDA.
    I've been lurking around in the Sony subforums on XDA for a while and owned 3 Sony devices, the X10i, the Z and the Z2. Sadly my Z2 broke down due to waterdmg last month and i bought a cheap replacement phone. Worked pretty well..... until i saw the HTC 10 exhibited in Taipei. Playing around with it for a while made me want to buy a new phone, after more indepth research about the LG G5 and the SGS7 my patience waiting for news about the Zuk 2 or OnePlus 3 was gone and i just bought a HTC 10 :) Luckily prices are pretty cheap in Taiwan. Worst case i can sell it back home for same value.
    So yeah, about Me.... I'm not a developer or anything. My coding skills are horrible, more like scripting to fulfill my needs.
    I'm a tech Enthusiast that loves gadgets and everything that's new. I spend money on Kickstarter to often just because i want to see tomorrows technology today. While there is the love for the technology there is also the love for knowledge. Just having something is no fun, knowing how it works is what makes it interesting. Same goes for smartphones. Android is awesome in this case, you can tamper around with so many settings and change so many things.
    In the last few years i had so much entertainment with my phones..... looking around the Forums here, there seem to be some competent people around, I'm sure I'm gonna have a great time here :)


    About:
    This thread is for gathering informations about Governors, their efficiency, their reaction in daily world usage and not in Antutu benchmark. Or at least that was the original intention. I also did some Benchmarks on Overclocked and Undervolted devices to check if you really gain any benefit. Batterylife was a big concern so i've measured absolut maximum possible and absolut minimum screen on time. After the Z2 Quickcharge hack was made (Japanese Z2 has it, European not) i've started doing more specific Charging time Benchmarks, and i dare say you won't find many as specific charging benchmarks around the web.
    Well yeah.... in short whatever i take an interest in i'll benchmark it and document it troughly. :)
    You can see my old threads for the Xperia Z2 or the Xperia Z to get an idea about what i'm talking.

    Benchmarking:
    Powerdrain: Find out how much the Phone is using under specific circumstances.
    Governor: Find out how a governor acts on a specific benchmark course.
    Charging: How fast does the Device charge from 1% to 100%


    Benchmarking Apps:
    Qualcomm Trepn Profiler: CPU and GPU frequency and load, also Powerdrain
    Repetitouch: To create custom Benchmarks that simulate normal everyday usage.
    BatteryLog: For Charging Benchmark, Voltage and Battery% per Minute
    GameBench: For FPS in games. (Make sure you deactivate Screenshot function for HTC10)

    Benchmarking Hardware:
    YZX Powermonitor: USB 3.0 QC3.0 4-13V 0-3A USB A Male-> USB A Female Powermonitor that measures Voltage and Current passing trough.

    Benchmarking Process and Display of Data:
    Can all be read in Post NR 80
    GPU Logs in Post NR48

    More......
    I guess that's it for now.
    I'll add more if there is more to add about benchmarking.
    7
    Performance and Throttling:

    CPU:
    Originally the SD820 has 2 Cores at 2150,4mhz and 2 cores at 1593,6mhz
    Because this can use almost 10W it's impossible to cool passive. So after a short while the CPU starts throttling to prevent overheating.
    I currently do not have Root so i don't see my CPU temperature in the status bar but have to open CPU-Z which is way to much hassle to find out a what temperature the SoC starts throttling.
    After a longer time stressed out the CPU (and CPU Only) rests at 1324,8mhz on the 2 fast cores and if that's still not enough all 4 cores will drop down to 1324,8mhz

    in this Stabilitytes v2.7 Benchmark i did with a cold phone (Room temperature 24°C) the fast cores went down to 1324,8mhz after 30 Seconds and the slow cores reduced their speed from 1593,6mhz to 1324,8mhz at the 200 seconds mark. This frequency (1324,8mhz on all cores) persisted during the 10 Minute Benchmark.

    Screenshot_20160510-183622.png



    If you activate the Powersafe mode in settings, your CPU clockspeed will also be Limited to 1324,8mhz.



    GPU:
    The Adreno530 is by far the fastest current Mobile GPU, but thanks to the 2560x1440pixel screen we really need this performance. If you don't have enough FPS in your games, activate Boost+ GameBoost. It reduces screenresolution for this game to 1920x1080.
    To give you an impression on how fast.... if we take the old Epic Citadel Benchmark and keep it running in UltraHigh Quality.... we have about 70% GPU usage ^^

    Screenshot_20160510-193608.png

    Screenshot_20160510-194806.png





    But.... it's not a sustainable performance. The top clock of 625mhz cannot be kept for very long.

    TRex_Rundown_H10.png

    (Source: Anandtech)

    More detailed Benchmarks will come when i've found a great game to test.....
    recommendations are welcome :)
    7
    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:
    eLWZ2Ye.png


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


    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
    wye0Zvs.png


    Butterfly v1
    23% Battery lost per Hour
    37°C End CPU-Temperature after the Benchmark
    K1ODG7G.png


    Ghostpepper v3
    25% Battery lost per Hour
    38°C End CPU-Temperature after the Benchmark
    fURqY6i.png


    Glassfish v1
    17% Battery lost per Hour
    34°C End CPU-Temperature after the Benchmark
    DLdYq7f.png


    Hawktail v2 Raised Minimum
    21% Battery lost per Hour
    36°C End CPU-Temperature after the Benchmark
    GXqquaX.png


    Ivicask PnPtweaks v17
    17% Battery lost per Hour
    35°C End CPU-Temperature after the Benchmark
    HprOfZ9.png




    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 :)
    6
    Index:
    • Powermeasuring with Trepn Profiler & Wallcharger Post NR3
    • Idle Powerdrain with Minimum and Maximum Screenbrightness Post NR4
    • Thermal Throttling on CPU and GPU Post NR5
    • Charging Stock Charger Post NR6
    • Charging QC2.0 Aukey PU-A28 Post NR7
    • Charging Compare QC3.0 vs QC 2.0 Post NR8
    • Charging Efficiency Post NR9
    • Camerabug in old Firmware, max 0.7sec Shutter Post NR10 (now Fixed in 1.80)
    • Camera High speed test Post NR11
    • Charging in Cold environement Post NR18
    • Testing Ghostpepper v8 profile Post NR21
    • Testing Ghostpepper v9 profile Post NR22
    • RAW performance of SD820 in DMIPS, Singlecore, 2 Cores, 3 cores, all cores Post NR27
    • Energy Efficiency, small cores vs Big cores Post NR30
    • Gaming and Throttling on Stock Kernel (1.80.709.5) Post NR35
    • Gaming with PnP&Thermals tweaks Post NR36
    • More Tests about Efficiency of Small and Big Cores Post NR38
    • Charging on 1.80.709.1 Firmware Post NR39
    • Charging while using the device Post NR40
    • Video Analyse Frameskipping? Post NR41
    • Guess what you will find in PostNR42
    • Screen Batterydrain in Idle Post NR43
    • PnP Tweaks compared PostNR46
    • Elemental X Kernel v19 with GPU Transitions Post NR49
    • Battery Discharge Linearity Post NR50
    • Elemental X Kernel v19 + Ivicask's PnP Tweaks v17 UC/OC/Powersafe Post NR51
    • Charging Beanstalk CM13 Post NR59
    • GPU Benchmarks stop at 58FPS.... Post NR71
    • Google account during Doze time, how much is caused by Google Services? Post NR73
    • Power_profile.xml how accurate is it? Post NR74
    • What about the Power_profile.xml from other Devices? Post NR75
    • 6 Years of Video recording Post NR76
    • Charging on 1.96.709.5 Post NR77
    • Thermal Throttling in a Longterm test Post NR78
    • How I Benchmark / Create those Graphs Post NR80
    • Audio Testing.... or something like that... Post NR84
    • Idle Screen Only Powerdrain Post NR85
    • Charging 2.41.709.71 and Battery Deterioration Post NR86
    • Charging 3.16.709.3 Stock Oreo Post NR87
    • Oreo: Standby Drain in Flightmode Post NR 89
    • Oreo: Standby Drain in Flightmode Safemode Post NR 90
    • Comparison of the both above Post NR 91
    • Comparison in Daily Usage Scenario Post NR 96
    • Charging LOS 15.1 with Nebula Alpha Post NR 97
    • Per Core Powerdrain, try nr 2 Post NR 98
    • Smartpixels Feature on IPS not usefull... Post NR 99
    6
    Discharge Linearity
    Some people say the battery from 99% to 90% last way longer than from 89% to 80%. Others say from 10% to 1% lasts way longer than from 20% to 11%.
    But does it really?

    I used my Normal Benchmark on the ExKv19+PnPv17 setup to make a full benchmark, from 100% to 0%
    It took a total of 386 Minutes to reach 0% and shut down. (Ignoring the last 0% which took 15 Minutes we get 371 Minutes. for 99 ticks that would be a pretty much exact 16%/hour drain. Accuracy of the 1h Benchmark +-1% check!)

    Looking at the Graph we see the battery level dropping almost linear.
    LRA5a9B.png


    Well... nope! not at all!
    The Blue line shows the Time it takes from 1% to 2% to 3% to 4% etc... not really constant eh? The Red line shows the Average over a 5% period.
    4WBNn0v.png


    The Mathematical Average for all is 3min 52 seconds, the Median is 3min 56 seconds.

    So what's the distribution Like?
    Most of the ticks from one % to another % took between 3 and 3,1 Minutes. quite a few are also between 3,9 and 4,0 and 4,9 and 5,0
    Pwk8R0b.png


    Btw, if you wonder why i used this Barchart and not a interpolated Line.... don't ask me, ask fkn excel... can't really configurate histographs.


    Conclusion:
    Yes.... it does take longer from 100% to 99% because 100% is not equal 100%. You can charge your phone for 1hour longer on 100% until it's really full. But from 99% downwards it's almost the same until it reaches 5% and again, if we take a look at the battery Voltage below 5%, it drops from 3,6V to 3,25V. That's not healthy! Don't do that to your Battery. Better shut it down and use it for emergency only. You'd still get about 20 minutes of good usage out of these 5%
    So yeah, the Batterydrain of this phone is linear.