[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
[MENTION=1007992]everyone[/MENTION]

My current Pie v3.8.1 build is available on my github. https://github.com/nine7nine/Apps/raw/master/exns_eas_v3.8.1p_b325e69.zip

i won't be updating v2.9 until tomorrow because #1 - i hit a couple small issues that I needed to fix on v3.8.x (which has slowed me down) && I have to be out the door before 5am tomorrow (it's 10pm here) ~ There is no way I can stay up tonight to finish working on it... Due to differences in v2.9 (which is an older codebase), I have a couple of extra hoops to jump through to finish merging everything in.... I had hoped that I would've had more time today, but it just didn't pan out.... So either flash v3.8.1 or wait until tomorrow night.

A few important details for v3.8.1

:

- Currently, after just updating anykernel2 ~ it's not applying some of my settings on boot, however this sort of doesn't matter (for this build) because I've disabled "sched" && the majority of CPU governors (schedutil will be the default, regardless)... but it obviously means a few other bits won't be tuned / enabled (e.g: usb fast charge and some other bits.... not a huge deal / temp). * I'll fix this in the next build, I just don't have time tonight to deal with it.

- Due to the above issue (and because I've been testing different setups / haven't automated everything), there is a manual with is technically optional, but IS a recommended step. After booting/rebooting, the new cpufreq driver "Boostbox" needs a script run ~ which can be done, in a few of different ways;

1. open a terminal app (or use adb shell) and *as root/su*, execute;

# ./boostbox

2. Open a file manager that supports executing shell scripts *as root/su* and execute the script (e.g: FX File manager + root add-on can do this).

* the boostbox script lives in /system/boostbox (root directory).

All this script does is figure out the process ID's for tasks that need to be moved into their correct cpuset group, then migrated into their corresponding Schedtune boostgroups... and finally, it disables the "perfd" service and resets the "top-app" schedtune value.

- this only needs to be done on boot/reboot, but I will automate this step in the next build. Also, by "optional", I mean that by NOT executing the script; some boosting done by the boostbox driver, just won't have any affect (but it will otherwise work).

- Boostbox has a bunch of tunables, but for now ~ I want them to stay *as is*... I will give explanations on them later + provide exkm user settings for my kernel/boostbox for you guys. ~ It's tempting to tweak away, but blindly doing so would be a bad idea + I would like to see how my current default settings pan out, in general... but yes, I expect there will be some tuning and tweaking over the next build or three, so keep that in mind. - I'm also not done implementing everything in boostbox. Audio boosting is one example, I'm still playing with that ~ so it's not in there. (although, the audio cpuset/schedtune groups exist and are populated.)

IMPORTANT / Troubleshooting:

There still still a possibility that bootloops can happen on v3.8.1 (although, it very rarely happens to me), however:

#1 - they cam happen after flashing the kernel, every once in a while....

#2 - if your device powers off (as you are using it) because you've drained your battery (this is usually when I will hit a bootloop)....

* In either case, force rebooting fixes it (hold down volume down + power button). && the good news here is that I have some patchwork that I'm working on that should fix this ~ but I haven't had time to integrate/finish with it yet (but I plan on doing that sooner than later. Most likely in a couple of weeks, when I have more free time)....

#3. About two weeks ago, Magisk seems to have been responsible for a bootloop on my device. It just wouldn't stop bootlooping / i couldn't get it to boot... I thought I had borked something in my kernel ~ but a couple of hours later; I removed magisk and *it booted up just fine* (I wanted to scream! ROFL) ~ it kept puking over the audio hardware service ( [MENTION=3209043]jimbub[/MENTION] IIRC it sounds like it was the issue that you hit, maybe with v3.x??)...

if you happen to get stuck like #3 ~ I would suggest removing magisk and seeing if it fixes the above scenario, as it certainly fixed it for me. (and this only happened once, I've never been able to figure out what happened and it hasn't happened since. so no clue here...).

Any other show-stopping bugs or issues, just switch back to v2.8.2 (and make sure, if you can; to provide me with as much info on the issue as possible!).... I (obviously) won't be taking down the v2.8.2 from my github (and it's still linked on the OP)... I also won't update the OP either, until I have both new Pie builds up.

Anyway.....

I'm super tired. bed time. Sorry I couldn't get both builds up and that I'm still hacking away on it. Crazy busy with work + all of the issues kind of hit at once. I expect to get everything smoothed out soon though && thought I should at the very least post the current build, that I'm using that doesn't have the issues that were stopping me from pushing updates.

thanks for your patience!