[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Now playing history works just fine. It´s most probably not caused by the kernel as [MENTION=6791680]_LLJY[/MENTION] already suggested.

didn´t I already answer about performanced and gentle fair sleepers? ;)

https://xdaforums.com/showpost.php?p=78194287&postcount=184

Performanced

I honestly wouldn´t disable performanced. AFAIK it controls also heat/thermal/battery throttling functions. Remember this is a phone with a non removable battery.

Gentle_Fair_Sleepers

I already said disabling gentle fair sleepers was a thing back when the SOCs were not even half (or a quarter as much) as powerful as today. (therefore this tweak could improve UI fluidity back then) The tweak originally was used when kernels used the CFS. Later it was still being used then HMP came up. But already there the logic to disable it was flawed because most of the upcoming SOCs at this time were big.LITTLE! EAS unifies now CFS, cpuidle and cpufreq in its own scheduler.

Have a read here: https://www.xda-developers.com/google-pixel-fastest-android-phone-eas/

As I already said Google (also CAF and ARM) are aware of all mechanisms in kernel/sched/features.h . I knew there was some experimentation from e.g. ARM with these tunables and it all turned out to have no effect, not the intended/desired or a negative effect. (I tried it on Pixel 2 XL and it didn´t have a notable effect on EAS)

If you personally feel your phone runs faster disabling these functions you´re free to do it :) However there might be other drawbacks that are not completely visible at first maybe never at all. If it works for you disable it.

Tracing

persist.traced.enable=1

enables perfetto traced which is a relatively new tool for tracing performance in android. I think this relates to the new "system-tracing" entry in dev options but I could be wrong.

https://android.googlesource.com/platform/external/perfetto/+/master/README.md

More information here under DOCs

Encryption

Go through the logs, both logcat and dmesg, while the device is booting and setting itself up. If I had to do it I´d capture logs on both encrypted and unencrypted with the exact same setup. Compare the logs, see where a check is getting tripped and search what exactly happens. This is probably some other daemon, app and not in the kernel (that´s my guess). On the HTC U12 where faceunlock gets inaccessible, the check is not in the kernel at all. (just an example)

The powerhal of Pixel 3 wouldn´t probably tolerate CPU overclocking at all and just keep resetting itself back to the default "max" freq which btw is already 2,8 GHZ (!) for the big cluster. (just like it does on Pixel 2)

GPU overclock maybe we´ll see :) but so far the performance on the sd845 is enough for everything? :)

Dankeschön :) Kaffee ist immer gut!

No I don´t upgrade each canary version as soon as it comes out. I rooted the phone with v17.4-411ea56a and kept this version as everything is working as intended. The few changes needed for Pixel 3 are in this version. I´ll upgrade when the next bigger beta/stable release gets published probably.

thanks for actually taking the time and reporting back! that´s greatly appreciated. I hope it works for all now.