yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
Rarely seen a Dev like you, who explains what he does and why he made these choices.

Even if I don't understand all ins and outs, it's really appreciated.

Keep up this amazing work, and take your time for your new tree, there's no hurry.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
Installed the test kernel and my phone does feel snappier, apps seem to load faster. Running well at the moment. On another note, Magisk uninstalled earlier, don't know what happened.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
just flashed the test version on top of the previous one, and magisk is still here.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
I probably wrote that in the wrong order, had the magisk issue before I installed the test kernel.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yup. would be 100%

ya, no idea why magisk wouldn't be there. it wouldn't have anything to my kernel's flashable zip.... there's no way it would remove magisk... it detects if magisk is present, so that it can systemless-ly patch the init.rc and add my init.exnoshadez.rc, aside from flashing the kernel, etc...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
Oh I see. I've flashed the 15.2 beta after installing latest it's and since then I have no probs. Have you got it sorted?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
Yep got it sorted, don't know why it disappeared. My phone is sleeping very nicely with the test kernel by the way.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aoaleman:
Test kernel is running very nicely, thank you!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
Just flashed to latest stock 8.1, from the previous 8.1

Setup device, reboot, flashed ExNoShadez, reboot, magisk, setup modules, reboot.

Running AMAZING. idle uses almost nothing. Smooth, snappy. Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
Hey guys. Should i worry about the high numbers of these wakelocks? TiaView attachment 4381686
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no, you should not be concerned. I realize that there are lot of apps out there for abusing / disabling wakelocks... but more often than not, messing with wakelocks can cause problems... it's the reason why I don't include either of the kernel patches for disabling them(WiFi ones anyway).. (also, the reason boeffla's patch doesn't disable any by default).... strange things can happen when u start messing with wakelocks; everything from not receiving messages, WiFi being buggered up to far more serious issues...

there was a time when disabling wakelocks was helpful. in older versions of android (lollipop, KitKat, etc), but I advise against messing around with them... in fact, if someone does and bumps into problems; i'm not interested in hearing about it / don't report...lol
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
Thanks a lot for your answer. Tbh I was concerned to see those high numbers but I'm good now . Thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
From now on, you have to flash Magisk before ExNoShadez kernel (and don't need to flash magisk again with future kernel updates).

And you don't need to reboot between Magisk and kernel too.

;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
So since I'm up and running with magisk, when the updated kernel drops I'll just flash it, it'll detect and keep magisk and I'll just reboot?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Ya, if you've already flashed magisk zip - then on any subsequent update you would just flash the kernel zip.... It's only if you re-flash the stock boot.img or a monthly firmware update, where you would need to flash magisk. (situations where you lose root).

To clarify a point though; It's not that it detects magisk, in order to keep magisk.... When flashing the kernel, it alters the init.rc and add it adds my own init.exnoshadez.rc .... So with magisk being present/detected ~ AnyKernel2 will perform "systemless" modifications consistent with Magisk. (it actually should detect non-root, magisk or SuperSU and act accordingly).

However, without magisk being present ~ my init.rc / init.exnoshadez.rc would NOT be added in, which would mean any settings that I have to be applied on boot - wouldn't happen.... I use this method because it makes more sense than using an init.d shell script (or /magisk/.core/service.d or whatever), it doesn't require mounting /system parition and/or giving an additional script for you guys to use / manually add yuorself, etc....

It's far easier to just create my own init.exnoshadez.rc ~ and patch/hook it into the init.rc, so that it applies on boot (it's one of the nice features of AnyKernel2 and tools like it).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
So does it matter that I flashed magisk after your kernel?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yes and no.... if magisk wasn't present, then it will not have added my init rc changes...

however, afaict flashing magisk after shouldn't matter, if magisk was already flashed (but isn't a needed step)... you only need to flash magisk after monthly firmware updates (or to update magisk to a new version)... the rest of the time, you can just flash the kernel.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] almightysiman:
Does sdcardfs enabled in this kernel?@nine7nine
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nevermindthelabel:
Yes
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Test kernel running great! Flashed over magisk just great :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
[MENTION=7810360]nine7nine[/MENTION] Kernel has been running so well that I gave it a little wallpaper love ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bryanx86:
Flash magisk first. Has anyone tried with flashfire yet?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
Flashfire didn't work for me. Just had a lockup & restart, don't know if it's kernel related
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
attached the bug report, hope it helps, if not let me know what's the best way to help.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
attached the logcat
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I don't think flashfire works with the last couple of magisk versions... I think I read that somewhere recently.

I need more background on your lockup / restart... what were the circumstances, exactly?

these bug reports shouldn't be publicly posted in a forum. they can contain personal info, although, yeah. they are pretty thorough... that said;

the contents of /sys/fs/pstore would've been more helpful.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
logcat isn't helpful for deadlocks or reboots, unless u happened to be using logcat at the exact moment it happened...

logcat is for monitoring in realtime... it's handy for debugging apps, selinux stuff, etc.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
Ok I'll remember that for the future. I was just using the timer for my son's exercises & it shut down, didn't actually restart, I had to turn it on. Also shut down last night at 13% battery whilst just browsing G+.

---------- Post added at 05:41 PM ---------- Previous post was at 05:40 PM ----------

If it happens again I'll get the info for you, thanks for the assistance.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yeah, definitely do that... right after it happens, grab the pstore stuff...

lastnight I actually drained my battery too. I got home at like 2am with 9%, no shutdown or reboot... I haven't had anything like that... ***but then again, my running kernel is ahead of yours by a number of commits. it's possible that I be fixed something that you are tripping over.

I'll try n post a build later, maybe it will sort u out.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
Thanks for your work, it's running beautifully, the shutdowns are not a big issue for me right now. Got health issues so I'm at home most of the time, so not mission critical or anything ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
OK. sincerely very sorry to hear about your health issues.

when I finish up with some changes, I'll get a new build up.

on a general note; I would be curious, if anyone else has bumped into a similar issue?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] memreh:
I had a similar issue trying to flash the latest kernel via flashfire, with magisk installed... phone shut down. Had to reboot manually & the new kernel wasn't installed.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
as I mentioned already flashfire doesn't seem to work with the last few releases of magisk. AFAIK, it doesn't work past magisk 14.2.

ref: https://xdaforums.com/showpost.php?p=75061297&postcount=1074

it's been discussed numerous times in the flashfire thread. nothing to do with my kernel and nothing that I can do about it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aoaleman:
Sometimes I'll have a non-responsive screen. Double tapping or power button does not turn the screen on. Any others? Can only recover by holding down power button.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] firephoenixctk:
My Pixel XL had an issue with the battery shut down at 13%. This was in October last year I think. I had to send mine back for a replacement. Hopefully this isn't the same thing. If you Google it you'll find a lot of people had this issue too.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I've read about this in a few threads, reddit and elsewhere... seems to be a December update onward issue, affecting some devices, while not others (and not exclusive to the pixel 1.... that said; I've never had this happen... some have suggested it's a magisk issue (I don't see why it would be), others claim google knows about it.... but I haven't really dug into Google's bug tracker for verification.... here's an example, from the pixel 2 forum; https://xdaforums.com/pixel-2-xl/help/screen-coming-solved-t3721095

they say solved, but I don't see how uninstalling magisk is a real solution. lol.... anyway, seems like there's lots of conflicting info regarding this issue.... not entirely sure about this one, unfortunately.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
ah, lets wait and see after another update or two.... assuming it drained well below 13% for him before the test kernel, it's a bug.... most likely resolved by a subsequent update.... that's said; doesn't happen for me.... but hey, sometimes these things are tricky, subtle issues in h/w differences cam introduce subtle bugs, with changes in the kernel here and there...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aoaleman:
Thank you for this. I am testing to see if it's Kernel Adiutor and the settings I set. Nothing with CPU speeds or anything like that but I have disabled it and am now testing if it goes away. I will report back today!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
what sort of things are you setting in kernel auditor?

it might be helpful for me to know, as I could test, reproduce and debug the issue...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aoaleman:
I was setting DT2W in there, disable the vibration, disabling S2W, in sound setting the headset high performance mode, and in Misc, setting the overall vibration to about 20%.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
I'm using EXKM and the only thing I've changed is the Mac randomisation.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
i'll have a look a bit later and see if I can recreate your issue.

I'm curious though; why use kernel auditor for setting that exkm provides? (the DT2w, s2w, etc) ....

one thing you could also do; if the device does it again. connect it to a PC, run adb shell && logcat... you should see some kind of warning or error, maybe... if u do, copy and paste it... I'd like to have a look....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
Reading the last few issues posted by the users, I ran my phone down to 9% and did not have any reboot or shutdown and still had 6 hrs SOT. This is with Magisk 15.2 and flashing the latest test kernel over the last stable version with boot twrp and not flashfire. I suggest flashing the kernel and leaving it as is, don't adjust any settings.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Only with latest test kernel but I've also had the unwakeable device issue FYI. I'll try NSFW kernel and see if it occurs there with the Jan patch.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aoaleman:
So in my testing throughout the day, not touching Kernel Aduitor app, the screen responded normally when waking up. That must have been the issue. Thank you, for making me realize that, [MENTION=7810360]nine7nine[/MENTION]! :D
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
just curious, are you using kernel auditor too?

but yeah. test kernel. unfinished merging of changes. my current running kernel is a number of commits ahead... and I'm working on getting MM to a point where I can just manually update the rest by comparison... getting close to that point, but might be another day or so, depending on time to do so...

interesting. ya, I noticed in Kernel auditor it says 'out of range' by default, for s2w and I know previously (when I used to use kernel auditor) it would crash sometimes when using custom controls for some stuff - it also wouldn't show correct values.... buggy app, I think...

good to know you aren't seeing that issue though... very odd stuff.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
Had another shutdown this morning at 98%. Tried to save the contents of /sys/fs/pstore but FX file explorer crashed. I'll have another go if it happens again.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Ok. you really do need to start providing me with something other than telling me your phone is shutting down or an app is crashing.... Unfortunately, it's pretty much 100% useless information to me, without logs to go with it...

I also find it curious that you are having apps crash - FX (nor any other apps) ever crash for me. I can't reproduce this issue with random shutdowns/reboots either (and I ran that build for a long time and subsequent builds for days after). regardless, you can try a slightly newer build;

https://github.com/nine7nine/Apps/raw/master/exNoShadez-eas_59c7fd9_test2.zip

I'd also be curious to know if you have any other tweaks or things that you switch around? ( not necessarily kernel specific, but just any odd ball software or tweaking that you do? )

anyway, if you bump into anymore problems, provide logs or switch back to the stable build.... there's very little use in telling me about a crash, without more info....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
I'm sorry, I did attempt to grab the info for you using the file explorer as soon as I restarted the phone.

---------- Post added at 09:57 AM ---------- Previous post was at 09:54 AM ----------

The only tweaks I can think of are the Google DNS & volume settings installed from magisk.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
all good. no apologies. I'm just pointing out, that without more info. nothing that I can really do, right?

volume settings installed from magisk? ... what is that?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
it's a module that doubles the number of steps in volume adjustment for media and in-call volume.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Donric13:
delete (something messed up my system not kernel or modul related)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I know you deleted your comment, but I'm still going to give a bit of a response as I think it's relevant, to some degree..... I tend to think to be of the opinion that whenever adding in modules and modifications you risk the chance that there will be breakage or instability. This is certainly true of tinkering with kernel code, but equally true of userspace modifications, such as those you might find with Magisk modules.... I believe that some modules are well-written and can work really well, while others not so much.... it really depends and mileage varies....

I personally tend to avoid using many mods (at least those provided by Magisk and I wouldn't/don't use Xposed). I've experienced instability with some of the audio mods, in the past - for example. so now I avoid them.

as far as flashing over kernels, no that wouldn't cause issues ~ and I also don't modify the system partition directly. So that shouldn't cause issues, either.

I really should add a note about this on the OP - I think it's important that before users report issues that they've verified that other modifications that they've done aren't the cause of their grief.... It's impossible for me to test every configuration, mod, app, etc out there ~ and it really sucks to end up spending time on someone's issue, only to find out later that it's something they've done....

A really funny example of this was, I spent 45min one night trying to help someone solve a boot loop, only to find out that they didn't even read the thread title ~ They were running an old version of android (so of course it bootloooped. lol).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Donric13:
Totally agree. I also have the feeling that it's better to unroot device and flashing stock kernel before flashing a custom kernel. Even upgrading your kernel on my side works better when i first uninstall magisk, flash stock kernel, reboot, flash your kernel and then directly magisk. Flashing your kernel over magisk gave me problems (for example two lines for every rooted app in magisk su and other strange behavior)...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
Without having any concrete evidence, I tend to agree re the Magisk modules, my phone seems to be ok since removing the volume steps module I had installed, and installing the 2nd test kernel.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I think I saw the x2 apps in magisk su once.... I flash way too much to be doing what you suggest. I always flash over top of my previous kernel, I don't need to be adding an extra few minutes of steps in there / big hassles... (and in theory, it REALLY should not make a difference).

also, flashing magisk after the kernel won't retain my settings. So, do whatever you like, but magisk shouldn't cause issues at all - being installed before-hand (that is how things SHOULD be). So I don't reccomend that anyone listens to your advice (no offense intended, but you're just wrong here.. So i need to clarify that for other users).

Yeah, I can't be too sure about that magisk module - I suppose I could install it and see if it happens to me - but it also could've been the first test kernel. It's hard to know without backtracking, which I don't really want to be doing.... Glad that things are working now though ;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Donric13:
Thanks for clarifying. So i gonna reflash your kernel for your settings... (thought your settings also stick when flashing magisk directly after the kernel). At least the x2 thing in magisk disappeared.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no problem.

as I've explained before; AnyKernel2 (used to make the kernel zip) detects the presence of Magisk, SuperSU or a non-rooted device.... if the device doesn't have magisk (or supersu) it skips adding in my init.rc changes because on a non-rooted device => there is no way for it to add in my changes systemless-ly.... So it just flashes the kernel and skips that part, in that case....

anyway, I NEVER re-install magisk, unroot / flash the stock boot.img or any of that jazz. (other than on monthly updates to android, when I lose root after flashing the whole firmware).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dr_drache:
Ok,

Hopefully I'm doing this right..

Was running the recent test kernel, was getting times where the phone would screen off and I would have to hold the power down to reboot.

Came here to see what logs I needed to provide (/sys/fs/pstore)

noticed that test2 was out, so tried that... Brings me to :

Stock Jan update (had to wipe because I'm an idiot)

Magisk flashed first - rebooted to verify I was rooted

Test1 was flashed then used

Test2 flashed after - no magisk reflash

Was in Facebook app, used power button to turn off screen and put phone in my pocket, took it back out in 15-20 seconds because I forgotten to check something.

No screen on.. held power to reboot.

Compessed pstore directory.

Hopefully I did this right.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
[MENTION=762102]dr_drache[/MENTION]

I'll have a look at that in a bit. I'm just about to have dinner... also, I'll have another build up shortly...

thanks for reporting, but also keep in mind; 1. those aren't stable builds and 2. since I'm about to update again, it is probably going to require that it happens on the,next build...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dr_drache:
Not a problem sir. Only reported because it happened on 2 different builds.. I will try your newer build whenever you get the time.

Appreciate your time and effort.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] natri23:
Unfortunately, since the switch to Magisk before kernel, I cant get the kernel to work. It keeps getting bootloop no matter what I tried.

Reflash stock Jan boot.img > boot to TWRP3.2.1.0 > flash Magisk (14.5 or 15.2) > flash kernel > auto reboot at Google spin or bootloop

I've even cleared cache with no help.

Elemental X 3.01 kernel still works fine though.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dr_drache:
in this case - I installed magisk, then booted fully (from an unrooted rom) verified it was installed;

THEN attempted the kernel.

if I was you, I'd reflash both slots with stock kernel, make sure you boot.. reboot into TWRP, flash magisk, boot, then try the kernel.

A lot of work right now, but it gets you to where you need to be to go on.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
thanks I do appreciate the mention. (new test build in next post)

Hmmm.... not sure what your issue is here. Could you please clarify a few details; which build are you using? do you have any other mods that you are using?... You should be using the latest magisk (15.2), not 14.5, just as an fyi... Whenever I upgrade Magisk, I tend to also remove the old version (magisk manager too).

I'm not sure what else might be going on on your system, but you could try flashing both the boot.img and system.img from the firmware for your device and then flash magisk and the kernel....see if that makes a difference (as maybe you have modified the system.img in some way... no idea

your the first person to mention this and I've talked to quite a few people running my kernel (a few people in person too). No one seems to have this issue... I'm not sure what's going on on your phone....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
another test build (still a work in progress), but flash if you like.

https://github.com/nine7nine/Apps/raw/master/exNoShadez-eas_test3.zip

lots of changes;

- scheduler code

- serial/tty drivers

- rt/mutex && (pi)futex updates

- locking updates / fixes

- workqueues updates

- misc fixups and changes

any instability, either report (including a full bug report and contents of /sys/fs/pstore) or switch back to the stable OP build, until I've finalized all of my commits (which will likely still be a few days... busy week).