yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
[MENTION=7810360]nine7nine[/MENTION] were you able to make the ramdisk tweaks stick on your P kernel?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yeah, i changed it. I'll update the OP

(...but I'd note that CPU-boost driver isn't going to be used at all in future builds, but it is currently still used in v2.8.2)..
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
updated v3.8.1 build; https://github.com/nine7nine/Apps/raw/master/exns_eas_v3.8.1p_bca050b.zip

Changes:

- Merged in "Adaptive Battery" support

- disabled RT_RUNTIME_GREED feature (likely a source of drain)

- Explicitly hard-coded some defaults that used to be handled by my init rc script. (so these settings are now applied/enabled without needing script on boot).

- Important fix for touchscreen driver

- fix for Boostbox

- tackled a couple of suspend/pm issues

- Updated Coccinelle and used it to analyze / improve some of the code base.

On this release, you still must execute ~/boostbox script (root folder) ~ I'll get this sorted on next update, but at least now I've reduced what my init rc script does (now it only creates cpusets, nothing more)... So that's one step closer to my goal... I'm hoping later today / tonight I can have a stab at getting the need to execute boostbox manually resolved.

I'd encourage anyone using v3.8.1 to upgrade, as a few of the fixes are important. Also, I didn't bump the version, it's still v3.8.1 ~ I won't bump the version until I've resolved the need to execute boostbox script manually.

anyway, I have to head off to work ~ but hopefully, I can tackle the next bunch of todo's on my list later.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dark2099:
Had this happen when I executed the boostbox script, is this correct, or no? Also my boostbox script isn't in the /system folder, in the root folder.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
What is boostbox?? I've googled it and can't find really anything. Anything to do with LTE?

Also, so far so good on the latest 3.8.1. Thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
that indicates that my init rc isn't being applied on boot ~ which creates those cpusets.

How did you install the kernel? I can't vouch for any other method working properly, except using TWRP + making sure that magisk (v16.7?) is present before flashing my kernel (otherwise those cpusets never get created, so the script will fail). Other methods may work, but they may not....

and yeah, it's in the root folder ~ I'll correct that in the post (just was thinking about the magisk, there i think).

No, it has absolutely nothing to do with LTE.... It's a cpu / schedtune boosting driver for my kernel that aims to replace perfd. Google doesn't turn up any results because it only exists in my kernel, is new and still a work-in-progress....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Ah gotya. Do I have to disable perfd in EXKM first?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Nope. my boostbox script does that ;)

EDIT: EXKM also currently can't enable or disable perfd on Pie. (already reported to flar2 by me).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Look at you, answers to everything! How do we solve world hunger??
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
LOL. Wish I had an answer to that question.

Most of the time, i really hate having to do anything manually, i prefer having things automated / taken care of (plus, boostbox requires a lot of setup, see below).

creating it's cpusets + schedtune boostgroups (on init);

############################################################################
# Boostbox: Cpusets: add custom cpusets for Boostbox Driver
############################################################################

mount cpuset none /dev/cpuset

# GFX
mkdir /dev/cpuset/gfx
copy /dev/cpuset/cpus /dev/cpuset/gfx/cpus
copy /dev/cpuset/mems /dev/cpuset/gfx/mems
chmod 0664 system system /dev/cpuset/gfx/cpus
chmod 0664 system system /dev/cpuset/gfx/mems
chmod 0664 system system /dev/cpuset/gfx/tasks
# better for low latency tasks
write /dev/stune/gfx/schedtune.prefer_idle 1

# AUDIO
mkdir /dev/cpuset/audio
copy /dev/cpuset/cpus /dev/cpuset/audio/cpus
copy /dev/cpuset/mems /dev/cpuset/audio/mems
chmod 0664 system system /dev/cpuset/audio/cpus
chmod 0664 system system /dev/cpuset/audio/mems
chmod 0664 system system /dev/cpuset/audio/tasks
# better for low latency tasks
write /dev/stune/audio/schedtune.prefer_idle 1

############################################################################
# Boostbox: Schedtune: add custom Schedtune Boostgroups
############################################################################

mount cgroup none /dev/stune schedtune

mkdir /dev/stune/gfx
mkdir /dev/stune/audio
chown system system /dev/stune/gfx
chown system system /dev/stune/audio
chmod 0664 system system /dev/stune/gfx
chmod 0664 system system /dev/stune/audio

and populating them, disabling perfd, etc (boostbox script);

############################################################################
# Cpuset / Schedtune: Move threads and Configuration for Boostbox Driver
############################################################################

# move all gfx related threads to gfx cpuset
echo -n `toybox pgrep -x surfaceflinger` > /dev/cpuset/gfx/tasks
echo -n `toybox pgrep -x rot_thread_0` > /dev/cpuset/gfx/tasks
echo -n `toybox pgrep -x rot_thread_1` > /dev/cpuset/gfx/tasks
echo -n `toybox pgrep -x mdss_dsi_event` > /dev/cpuset/gfx/tasks
# move all audio related threads to gfx cpuset
echo -n `toybox pgrep -x audioserver` > /dev/cpuset/audio/tasks
echo -n `toybox pgrep -x audio@2.0-servi` > /dev/cpuset/audio/tasks

# GFX: add all PIDs to schedtune "gfx" tasks / cgroup
for pid in $(cat /dev/cpuset/gfx/tasks); do echo $pid > /dev/stune/gfx/tasks; done
# AUDIO: add all PIDs to schedtune "audio" tasks / cgroup
for pid in $(cat /dev/cpuset/audio/tasks); do echo $pid > /dev/stune/audio/tasks; done

exec stop vendor.perfd

# Reset Top-app
# Needed for when using DSB without perfd
echo > 0 /dev/stune/top-app/schedtune.boost

I've obviously done all of this setup, manually using a shell too (while i was figuring outthis part) ~ not something that one wants to be doing though. ROFL
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Honestly don't know what half that means lmao. How do you execute it though? I run this in Termux:

su
./boostbox

And it says it can't be found
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
EDIT: I just tried Termux, it isn't sandboxed, just doesn't start in the root directory... So you need to first;

# cd /
# su
# ./boostbox

note: you could also execute this from a file manager (that supports executing scripts as root).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
I use Jrummys Root Browser, it can execute scripts. I'll give it a go, thanks!

Edit:

Output:

/boostbox[8]: can't create /dev/cpuset/gfx/tasks: No such file or directory
/boostbox[9]: can't create /dev/cpuset/gfx/tasks: No such file or directory
/boostbox[10]: can't create /dev/cpuset/gfx/tasks: No such file or directory
/boostbox[11]: can't create /dev/cpuset/gfx/tasks: No such file or directory
/boostbox[13]: can't create /dev/cpuset/audio/tasks: No such file or directory
/boostbox[14]: can't create /dev/cpuset/audio/tasks: No such file or directory
cat: /dev/cpuset/gfx/tasks: No such file or directory
cat: /dev/cpuset/audio/tasks: No such file or directory
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
read my edit; I tried termux, it works ~ Termux doesn't start in the correct path (while Terminal Emulator does).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
how did you install the kernel? was magisk present?

This should only happen, if my init rc settings aren't being applied on boot.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
TWRP (Booted)... Flashed Magisk 16.7 and then the Kernel

Also, same errors on Termux
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dark2099:
I did flash Magisk first. What I did to get it working was manually starting the init.d script, then tried via adb shell instead of Terminal Emulator to run the boostbox script, didn't get the error readout. So at least for me it seems an issue with the init.d script not auto executing on launch. I did install the init.d Magisk module, just in case, which didn't change anything.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
give me 5min, I think I know the issue ~ I'll upload a new build... I think I forgot to add a line in AK2 to make sure it wipes/replaces the boostbox script (because I may/do make changes to it)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
What init.d script are you talking about? I don't even have an init.d folder lol.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Ignore that.... init.d support isn't needed (it's also something that's pretty much deprecated, even if people still do use it).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Yeah, I used to always alternate between init.d and su.d on my S7 Edge. There's service.d with Magisk, but that's really not used either.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
[MENTION=4816406]dark2099[/MENTION] [MENTION=6801459]Craz Basics[/MENTION]

(and anyone else who've bumped into the same/above issue)

Re-download the zip; https://github.com/nine7nine/Apps/raw/master/exns_eas_v3.8.1p_bca050b.zip (I've just updated it)

...and re-install the kernel. It should properly replace the boostbox script now. (i believe that is the problem).

but, if you want to be extra thorough;

- flash the stock pie boot.img (sorry don't have them up yet),

- flash magisk

- then, flash the kernel.

....That said, I think only re-flashing the kernel should be necessary.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
K. it'll probably be a couple/few of days though - I'm kind of in the middle of tracking down an issue, so It might take me a bit to resolve.... For the most part the Test build is ok - but there are a few situations where it's being a pain... nothing bad like FCs/crashing or any kind of instability like that, just being "held up" or contentious when it shouldn't be - So just not upto snuff, slight regression / where the Stable build handles better... ~ Kind of expected (but not hoped for. LOL).

I'll get to the bottom of it and get it sorted out for the next test build though. just no definite ETA.

*So I pushed the Stable, because it was ready to go and the default changes were worth pushing, along with LTS (which the test build already had).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
I had one random reboot and it was when it had been sitting idle for roughly a minute after clearing all apps.

Didn't manage to capture a log and can't reproduce it. ??*♂️

Can't comment on battery life but I can attest to responsiveness. So far so good.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stryker09:
Almost one full cycle, I'd say it's on par or slightly better than Kirisakura, looking forward to more great stuff!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] housepabldroid:
I've got this issue..

It seems that the minimum CPU frequency is locked to 1440Mhz instead of 307Mhz.

But at the same time I haven't any kind of extra expensive battery use.. :eek:

Any ideas?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] montbazon:
You'd better to try to find a app or apps, which let your phone be waken all the time.

I don't have that issue
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] housepabldroid:
Which app or other thing can I use to find what it wake cpu?

I've tried with gsam, but nothing seems wrong
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
hmmm. i've never had a single random reboot.

clearing apps, how?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Cool. That's good then, because; There is more run-time overhead than Kirisakura has., due to some hardening features and the use of rt_mutexes in binder.... I also don't optimize for battery use + bias performance in a couple of build-time kernel configurations && run-time sysctl settings.

It's all very intentional though and I do try to make sure that Battery life is good. So even when I do make a decision to bias performance, I also try to find ways to balance out battery life.... So far so good.

Ya, I don't think that's the kernel doing that - it shouldn't be getting stuck at a given cpu-frequency like that. It would be hard for me to have any ideas ~ based on just a single screenshot from EXKM of cpu-frequencies used....

I believe there is something else on your system that is responsible. Some app or rogue process.

I don't use gsam myself. although it's useful.... Mostly, to check what's running or might be chewing battery - I look under battery settings, to see what % apps are using... I use Accubattery, in the same way....

Then I use OS Monitor, as my main system monitor - for more specific and detailed info;

-> See all system processes (including native linux processes, when enabled).

-> % of CPU each process is using... (also; CPU time info, etc)

-> Pid, thread, status, priority and other useful state info

-> tracking networking connections,where they are connecting to (with google maps integration), etc.

you might get some clues in there, but it will take getting used to using the app and having monitored things for a bit.... I good indicator would be if there is always a process / app using cpu % that never sleeps that probably should be.....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Just as an side; I decided to add a donate/Pay Pal button to my account. The reason?

Well, like so many other XDA / android kernel developers; all of the hard work and effort that I've put into this kernel is done in my free-time. While I do enjoy working on exNoShadez-eas and providing my work to others => It *is* a lot of work and at times very frustrating, especially when issues crop up -> or when I am trying to integrate new code or features touching certain parts of the kernel. (crazy amounts of hours working on it)

So, I decided that I too would add a donate button. It's definitely not mandatory to donate, by any means - but If you want to or can afford to; Go for it, as it would be very much appreciated... Having a few cups of coffee paid for (which I drink lots of, especially on late nights/early morning hacking on this kernel), contributing/donating because you feel that this Kernel is working nicely and adds value to your Pixel and/or because you feel that my development time and effort is worth something => would be great reasons to throw a buck or two in my direction....

Regardless, I will always continue to develop and work on this kernel and this will be the one and only time that I mention PayPal/donations in the thread. (I did add a ref at the very bottom of the OP though)....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Bluetooth seems to be working a lot better. Sometimes it would connect to my head unit but audio would still play on my phones speaker. So far that bug hasn't surfaced since flashing this kernel.

Other than that everything is working well
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Thanks, good to know. As mentioned before - I don't get a ton of bluetooth testing in (with speakers / headphones). So good to hear that subtle bugs like that may be improved with my kernel.

Is that on the test build or stable (or both?). only reason I am asking; slight difference in bluetooth, between them.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
That's on the latest in the op ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Latest as in stable, you mean, eh? (yes, "eh?" my fellow Canadian. lol)

that's probably due to the RT priority on the bluetooth (rx/tx) transit paths, or it's a happy accident caused by Binder_rt. (I supsect the former though).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] housepabldroid:
With a simple reboot everything goes well and ram is a bit more free then before.

Now I have to understand which app cause that problem..
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
On reboot, android will always be using less ram (or any computer for that matter)... But I wouldn't be overly concerned about memory usage; android tends to put a lot of stuff into memory; so that accessing it is quicker later. it speeds things up - and that is normal.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
* tiny update

So I've gotten in touch with the upstream/Mainline linux mm subsystem maintainer ~ He's been kind enough to give me some advice, things to try, where to look; regarding the missing mmput_async() function that I need to implement, in order to support the last few upstream commits in Binder.

This is great because I had pretty much exhausted most other resources (mailinglists, android kernel dev groups, etc)... So hopefully, later ortomorrow - I can try to get to the bottom of it and finally get this code merged into Marlin/Sailfish... I've spent enough time on this bit - and it kind of drives me nuts - but it's something that should be put into the kernel - will improve Binder and allow some further changes / improvements... So here is me hoping it works out...

*also working on some other driver changes, for ones that hook into ION. should yield some improvements, if I get it right. few other tweaks coming to the stable build, most likely too.... next big test build won't be for a bit ~ still working on that - but focusing on getting a few bits into the stable kernel, as the next monthly firmware updates are coming and I'd like to get a few changes in for that release.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Flashed the new DP2 just to play with it. I'll most likely flash back to 8.0 to play with this kernel soon enough. Battery life has been pretty similar actually and it's spectacular on 8.1
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Ya, I took a look at DP2, somewhat quickly... Nothing overly impressive, from my POV. Boot animation is nicer, Pixel Launcher is still not something I'm interested in using...lol. to put it politely ;).... the Kernel's LTS is still out-of-date, not a ton of user facing changes, either (discounting a few minor adjustments to Pixel Launcher).... I took a quick look at the system, boot and vendor images too - a few changes here and there (most likely why my kernel doesn't boot on it), but I won't be upgrading until the final release and source code is pushed... So I don't really care to investigate further or test on it....

I can't really comment on 8.1's battery life, I didn't use it long enough; but just from what I've read in (battery life / SOT) threads, it doesn't seem that much better... It's hard to tell, from people's posts; it tends to be slightly subjective and everybody uses their device differently. so nothing really concrete to base any of it on...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] fizbanrapper:
GZIP compression would reduce the size. Any interest? TWRP is a pretty big thing to have to give up.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Gzip will *marginally reduce size*, but also have the wonderful side-effect of slowing down boot time. (Lz4 has much faster decoding). There are reasons why lz4 was introduced in the kernel a few years ago, in the first place; and why it's used for things like ZRAM too ~ It's faster....

I also sometimes make test builds with more debugging enabled - which increases kernel size, yet again.... I'm not going to fight with trying to make the kernel smaller to (barely, if at all) work with TWRP.... I've been there and done that...

If having TWRP installed is that important to you, I would suggest using a different kernel; one that optimizes for size. I have pretty solid reasons for not supporting TWRP installations. So that's not going to be something that changes, anytime soon....

Ideally, in the next bit - I'm also going to make boot.img(s) available too, so that TWRP isn't needed at all. (ie: Magisk users can just patch and install the boot.img.... ad/or patch it and then place it into EXKM's backup folder and restore the new boot.img from within EXKM; without using fastboot or ADB).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
EXKM also has it's mechanism too. (post-fs-data.d)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
[MENTION=7810360]nine7nine[/MENTION] I use ex auto flasher, but I don't believe it works with ramdisk tweaks anymore since P came out

Looks like twrp is the only solution
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Volume rocker error and random freezing/reboot error is back. Boostbox outputs same errors.

Edit: Back on the 3.8.1 from earlier. All is well (except boostbox)

When it freezes, the screen brightness turns all the way up, I'll grab a logcat if it happens again. Adb works while it's frozen
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Did you flash the stock boot.img first (just curious about the boostbox script here).

Unfortunately; unless you (or someone else with the same issues) start coughing up logs ~ I can't even attempt to fix your issues... It's literally impossible for me to do anything for you at this point, without a significant amount of details being provided to me.... Vague stuff like "freeze/reboot error" means very little.... It's basically useless information. Sorry, but it is what it is.... (*Although, the volume rocker IS something that I'm looking into today, as I think I know what the issue is)...

To be honest; I suspect that your phone _could_ be a bit of a lemon (i've thought this for a long time, long before Pie was released), being as you've NEVER been able to run v3.x, while lots of other people can just fine... ~ I could be wrong, but without logs, dumps, etc ~ I can't verify anything, which sucks.... (and before you mention v2.x working fine ~ they are much different kernels and v3.x puts demands on the hardware that v2.x doesn't - so it's not really a fair comparison)...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Really? interesting.

that might be helpful info
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Yes, I flashed stock first. And I'm aware the details I've given are inadequate for searching for a fix, as I really wasn't trying to. Read my edit above (I'll provide a logcat next time it happens)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AllusionPDX:
Was the pstore and volume bug fixed?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Ok, good to know ~ still doesn't make any sense (on why the boostbox script isn't working correctly.).

but yeah; you do gotta appreciate it from my perspective though; When someone reports problems without info to go with it, it's basically "the worst". ROFL. ;)

There is no "pstore" bug ~ /sys/fs/pstore is where logs are dumped after a kernel crash.... As a user, that's basically of ZREO concern to you, unless you need to collect those files for me....

You could just read like one post above to get your answer on the volume rocker issue ~ looking into it later today.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
So of course I try reproducing the freeze error while taking a logcat and it won't happen. The volume error was present for awhile but now it's fine. Says process system has stopped a couple times.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AllusionPDX:
Like another guy the playstore was just pure white and didn't load and eventually if left open crashed the phone