[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
okay then let me try to explain it a bit more.

I think you didn´t get what I was trying to get at with my post.

I´ll try to simplify it as good as I can. :)

Actually there are three points I want to explain.

The first: you are tricked by the graphical interface of exkm

There is a file on your device, that stores the current minimum frequency for each cluster. All kernel manager apps read that file and display the content of that file.

What you see is what´s stored in that file.

CPU-Input-Boost sets the values of these files to 499mhz for the big cluster and 1036mhz for the little cluster, as soon as you touch the screen for the amount of time that is specified in "cpu boost duration".

Now lets think about what actually happens. you open your CPU Manager and tap on cpu section. You touch the screen and the entries get read when you touch the screen. Of course every cpu manager will show 499mhz and 1036mhz for the minfreqs, because this is exactly what happens. You touch the screen and the minfreqs get set to 499 and 1036mhz.

No kernel manager has a "live view" of the current minfreqs, that would update by itself without you touching the screen.

After the duration of "cpu boost duration" is over, the minfreqs will return back to 300mhz by itself. But the entry you see in exkm, that is showing the minfreqs, will not be updated "live" and thus showing the boosted freqs.

Setting the CPU Boost Duration to 0, is essentially the same as hitting the off button for that mechanism, as the frequencies are boosted for 0 amount of time. They are not boosted at all. That´s why it will display 300mhz for the minfreqs then.

And that boosting is important for smoothness and this device! So don´t disable it.

And monitor your freqs with the CPU frequency distribution tool in EXKM I posted the screenshots from.

Is that understandable?

The second point:

Every "live view" cpu monitor like the ones found in EXKM on the "home page" or the floating one from devcheck, don´t work as well with newer EAS (pixel smartphones) implementations as they did with older HMP (pre pixel) ones.

EAS is way more advanced in predicting the next needed CPU frequency than HMP. What happens is, EAS is that sensible, that it provides horsepower for the "live view" monitor to run and you don´t see the CPU freqs hover around 300mhz as often.

The workaround, so you can actually see that 300mhz gets used when the phone is idling, is what I described in the previous post.

Did you try that? let the phone idle for a minutes and look at the frequency distribution afterwards.

The third point:

Charging and little cluster ramping up to 1900mhz.

When you plug in the phone to your charger, the fast charge driver is loaded. That is requesting "horsepower" that is not UI critical. That is the reason why the load is distributed on the little cluster (saves more energy compared to big cluster) and ramping it up for a short amount of time to 1900mhz.

After a while the frequencies settle at 300mhz.

Try that also with the cpu statistics/cpu times tool found in exkm. Plug your phone to the charger, go to the cpu statistics tool in exkm, reset the freqs, and let it just lay down with screen on for a few minutes. Update the cpu frequency distribution view and you will see that 300mhz is used like 90% of the time.

I just double checked before the post!

I hope that clarifies that behaviour to you.