[HTC 10 Guides, News, & Discussion] Haldi4803:
A closer look at SchedTune seetings

Thanks to Nebula Kernel we now have a fully working EAS Kernel with Sched Governor support.

[MENTION=3428502]Freak07[/MENTION] did quite a bit of tweaking and tuning for the perfect values, But what Values are there exactly? And how does changing them affect things?

Quote from the Creator himself:

While there is quite a lot to change, most important things are the first 3 Values.

Quoting this PDF about EAS on the Pixel phone:

So the Top-App is Currently focused by the User.

The Foreground is probably stuff like Music.

And the General SchedTune.Boost is working overall.

All these 3 can be set from -100 to +100. To know what they do you'd have to take a closer look at how EAS works.

To put it very bluntly...

Conventional: Task Scheduler is placing Tasks onto Cores based on how busy the cores are. The Governor is looking at the current CPU Load and decides to increase or decrease the CPU frequency.

EAS: Task Scheduler is placing tasks onto Cores based on their Energy Usage. At the same time the Task Scheduler tells the Governor (named Sched in this case) how much Load it has to expect for the next Timebased window. the Governor then set's CPU frequency in advance.

So by using the Boost Value 0 it sets Frequency expecting whatever Task Scheduler says. If the Value is Positive it's increasing the expected load by Factor X, thus the Governor will increase the Frequency because it's expecting more work. By Decreasing the Boost Value the Governor expects Less work and can not finish the estimated Task during the Time Period.

Theory is always fine and needed... but how does that actually work in reality?

I've tested some different settings and here are my results: (Most tests took 10 Minutes, Stock one is 20 minutes)

You can find all Tests Separately in the Hide button here:

Stock 7.2.0:

SchedTune.Boost 2

Top-App 50

Time20,4

Battery Used5

% per Hour14,7

Temp Started30

Temp Ended30,5

Trans Small: 20167

Trans Big: 22942

Top-App 40

Time10,3

Battery Used3

% per Hour17,4

Temp Started30,7

Temp Ended31

Trans Small: 10366

Trans Big: 11766

Top-App 30

Time10,4

Battery Used3

% per Hour17,4

Temp Started30,2

Temp Ended30,7

Trans Small: 10529

Trans Big: 11997

Top-App 60

Time10,3

Battery Used3

% per Hour17,5

Temp Started31

Temp Ended31

Trans Small: 10540

Trans Big: 11726

Top-App 70

Time10,4

Battery Used3

% per Hour17,3

Temp Started31

Temp Ended31,2

Trans Small: 10850

Trans Big: 12039

SchedTune.Boost 4

Top App 50

Time10,3

Battery Used2

% per Hour11,6

Temp Started31,5

Temp Ended31,5

Trans Small: 11719

Trans Big: 12825

SchedTune.Boost 8

Time10,4

Battery Used2

% per Hour11,6

Temp Started31,7

Temp Ended31,5

Trans Small: 13800

Trans Big: 14436

SchedTune.Boost 16

Time10,4

Battery Used3

% per Hour17,2

Temp Started31,5

Temp Ended32

Trans Small: 16898

Trans Big: 15592

SchedTune.Boost 0

Time10,4

Battery Used3

% per Hour17,3

Temp Started31,7

Temp Ended32,2

Trans Small: 11066

Trans Big: 11565

SchedTune.Boost -2

Time10,3

Battery Used3

% per Hour17,5

Temp Started32,2

Temp Ended32,5

Trans Small: 10917

Trans Big: 11576

SchedTune.Boost -4

Time10,4

Battery Used3

% per Hour17,4

Temp Started32,5

Temp Ended32,2

Trans Small: 10845

Trans Big: 11460

Stock 7.2.2

Time20,4

Battery Used3

% per Hour8,8

Temp Started31

Temp Ended32

Trans Small: 20595

Trans Big: 22070

Or you can look at this consolidated barchart :)

Note: Small cores Frequency are not entirely correct, you only see them in the same color as the Big ones. But it's only 100mhz difference at maximum.

SmallBig
307,2307,2
422,4403,2
480,0480,0
556,8556,8
652,8652,8
729,6729,6
844,8806,4
960,0883,2
1'036,8940,8
1'113,61'036,8
1'190,41'113,6
1'228,81'190,4
1'324,81'248,0
1'401,61'324,8
1'478,41'401,6
1'593,61'478,4
1'555,2
1'632,0
1'708,8
1'785,6
1'824,0
1'920,0
1'996,8
2'073,6
2'150,4

Conclusion:

What do we get out of this?

If you increase the SchedTune.Boost over 8... probably gonna be 10 or 12 ... the IDLE Load is too much for 307mhz to handle, so Idle Frequency is forced at 403/480 mhz

I did NOT check for Lag during my Benchmarking! So using Boost -4 would safe Battery but might add Lag, i'll try dumpsys gfxinfo later to see at which general boost UI lags show up. Or use DiscoMark for app switching tests.

Going from Top-App 30 to 70 does not make any visible difference in the barchart.(EDIT: seems like 7.2.0 had a Bug which made Top-App Boost not working!) To examine this further i'd need to do a 1h (minimum, better 2h) Test and check for battery usage. Might as well be that the Boost value 30 is way above normal already and my current benchmark parcour doesn't need more power.

All in all we know... we have to test more to know more :)

And definitly need a benchmark for UI lags....