yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
Boot into stock April (full clean flash and stuff)

I set up my stuff, logged in, installed my apps and all.

Rebooted into the bootloader to boot into TWRP 3.2.1-2.

Flashed Magisk 16.3 (1630).

Rebooted to system and unlocked the device to ensure functionality.

Booted back into the bootloader and then TWRP again.

Flashed ExNoShadez 2.7.

Rebooted back into system and unlocked.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
=> visual glitches? an example or be more specific?

=> Out of curiousity; are you using my v3.2 binaries - or your own binaries?

yeah, you should probably try and collect logs, if you want me to look into this.... If it soft-resets; then you should be able to catch that live / as it's happening with logcat...

Obviously, this doesn't happen on stock rom (at all).... but who knows with LOS; they've added a lot of stuff to AOSP and they aren't exactly renowned for code quality / review process.... It's possible that v3.2 is tripping over a bug in LOS that doesn't exist in Stock ROM (and that v2.7 doesn't trip over).... But obviously it's possible that it may be a kernel issue too ~ can't know for sure without more info.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
It's happening on stock.

I'm using your builds only.

Visual glitches as in the status bad and navbar not updating the icon colors to match the foreground app.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Nick, you are starting to lose / confuse me.... first you say that v2.7 works on LOS and that v3.2 does NOT... now, are you saying this is happening on Stock rom or.....wat?

I don't see how the kernel would aeffect status bar or navbar colors. explain?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Interestingly I had my own reboot issues with 3.2 on preview and 8.1 stock. Ill try 2.7 and see if there's success there.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
To be more specific (or clear) it appeared as though a system process was hung causing slow/unexpected behavior eventually leading to a crash to the boot animation and never booting.

Also, I have used both 2.7 and 3.2 on Lineage and stock and 3.2 in both cases caused this weird behavior basically rendering the device inoperable until I flashed 2.7 or the stock boot image.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Ok to confirm, I just flashed latest 2.7 on P and everything is humming. 3.2 definitely was the issue.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vijogape:
That's not true, just tried out again, still not workin. think that the problem is the custom recovery that lineage has
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
Could be the build of Lineage you're using.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vijogape:
Ok, I have used both April builds (in your process you stated that you are using an April builds) and still not working, could you share us your process with details (lineage build, link of download if possible, gapps, etc) and I will test it out, so far I tried both April build, with Pico, nano and the gapps from this post, tried installing with your process, tried installing magisk and without reboot installing the kernel, tried installing the kernel without doing the first reboot (clearly didn't work, seems like the installation is correct but then I have a bootloop), I even tried flashing the stock img, which created another bootloop, so please elaborate with your process please and I will confirm
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Dachfenster:
So here's how I got it working:

Install ROM as described in the respective thread as well as TWRP (I know it's not recommended, but that's how it works for me on every ROM I've tried)

Boot into system, let everything set up.

Boot into recovery, flash TWRP again (otherwise I would get Error1 when trying to install the kernel... had this with Kirisakura before) and then flash the kernel.

Boot into system.

Boot into recovery, flash Magisk (it will say insufficient size, high compression mode).

Reboot, you're done.

Again, nine doesn't recommend any thing of this at all (neither flashing Magisk afterwards nor having TWRP besides the kernel).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
I avoid flashing TWRP at all with EXNS kernel, it causes so many issues for little gain.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Dachfenster:
Again (third time I guess) that's how it works for me. Otherwise (without TWRP) it just wouldn't flash on LOS - no matter what I tried. In fact I tried the steps you've listed somewhere here before. No luck. With TWRP it works although the opposite should be the case. Seriously I don't know why it is how it is.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] fizbanrapper:
Maybe TWRP has a smaller ramdisk than stock?

If the EXNO installer appends the ramdisk and the stock ramdisk is too big already, it won't boot. But maybe TWRP subs in a small enough ramdisk that there's still enough room for whatever is being appended?

I'm too lazy to find out for certain, but this is the only explanation I can think of at the moment.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Gil Smash:
Los does a weird custom recovery thing that's I've found myself in before. Not sure how that would apply though...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DR3W5K1:
TWRP is smaller
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
Running fine with April kernel over May factory image. ;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yup. stable should be fine and I also was running v3.3 April build on may firmware, i'm testing the may build right now...

I have an estimate (work related) to do after work, so tonight I'll get everything merged into the v2.7 build and push everything to github... so an update will be out sometime b4 I go to sleep tonight...

it's been a bit of a hectic week for me, so finding time to get everything updated and tested has been a bit of a pain. I'll get it sorted, ASAP.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
But noticed something weird...

I lost root (Magisk) before updating to may firmware (phone was sometimes laggy lately).

Updated to may FW, flashed Magisk then your kernel. All was fine (kernel and root) and today, Magisk manager notified me to install root... (phone was indeed no more rooted)

Don't know how it can lost root, i flashed nothing except may FW (without -w), Magisk and kernel.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
hmmm... not sure, I have seen posts on xda ando reddit of similar experiences (not with my kernel, or even the og pixel, specifically), but I haven't run into this myself... so I can't be sure why that would happen...

I have however had that happen with SuperSU on our device, before switching to magisk... back then I wasn't doing the whole systemless modifications - so I thought maybe that had something to do with it... but again, not sure and I've never bumped into that with magisk.b
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
[MENTION=7810360]nine7nine[/MENTION]

Yes, i do remember people talking about losting root without doing anything special.

Will see if it happens again.

If so, it'll be time to fully wipe. ^_^
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
hey Marlin folks;

Can someone put up a link to the May boot.img for me?

I'm getting ready to throw up builds (in the next 1-2hrs, just rebuilding my toolchain - then compiling + some tests), so I'd like to be able to add in the May Marlin boot.img on the OP / my github. thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I'll get one up in a sec.

---------- Post added at 05:23 AM ---------- Previous post was at 05:03 AM ----------

@nine7nine here is may boot image for Marlin. Here is gdrive link in case afh is slow or something
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
thanks man!

...and just a general update: (as to why there is no build up yet.)

- typically, I always rebuild my toolchain before compiling the kernel (to pull in all of the latest code / fixes).

- the scripts / repo that I use to build my toolchain was out of date and maintainership has switched hands (back to it's original author, *which i didn't know*). Due to this; compilation failed and it was 2am, so I had to get to bed.

- this morning I've enabled NoMachine on my linux box so that I have remote access and get my toolchain built + the kernel builds (I've already committed/applied the May patchwork to my kernel sources, both branches. yesterday).

- Due to switching to the new repo - I have to (re-)download/clone all of the sources for building the toolchain (gigs of data) before I can rebuild it. So now, I am just waiting for that to finish. (it's going to take a while to pull)

the good news is that once I have my toolchain rebuilt, I shouldn't have any issues with compilation. I can push builds to github; flash the stable kernel (at work) and run some tests (before updating the links on the OP. Note: I've already tested the v3.3 build, but I do need to rebuild with the updated toolchain, regardless)...

So sometime today, I will have builds up. (probably in the afternoon. It's morning still here).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
UPDATED builds.

Changes (both builds):

- May patchwork

- linaro gcc-7.3.1 (for now). building gcc-8.1 failed compiling, so I went the path of least resistance ;)

NOTE: I'll be doing another build with gcc8 (on the weekend) and at that point I will add in the remaining few LTS patches, as well.

Stable Build is v2.8 on OP link (and here: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v2.8_8dbed4.zip )

Beta v3.3 build is here: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v3.3_34eda3c.zip

NOTE: If you are flashing the v3.3 build, I would ask that;

#1 - you also wipe your cache in twrp before rebooting (your next boot will take a while - so be patient).

#2 - if it doesn't boot, try force rebooting (even multiple times, if necessary)

#3 - if v3.3 still doesn't boot, please run adb shell + logcat on boot (connected to a PC);

you will have to first execute "adb shell", sometime just after the G logo appears (you may need to execute the command several times). After that execute "logcat" and watch the output (until it stops or keeps spinning on the same error(s). -> from there, you need to copy/paste that into a text file (as much as possible) and send it to me (either as an attachment or using a service like pastebin and linking to it)...

NOTE: As most of you know, I don't really support anything but stock 8.1. If it works on P or custom roms, then awesome. it it doesn't. not much I can do.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
I have a GCC 8.1 AArch64 cross toolchain built, it CAN build, what went wrong?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
temp issue, some build faililure in GCC's sources. so the compiler itself was failing to build... I was at work, trying to get packages out, so rather than waiting, I switched to the linaro branch...

not a big deal, I'm sure when I go to build it again, it'll be fine. but I was under time constraints, so it made sense to just swap compilers - there shouldn't be any huge differences in performance (gcc-7.3.1 vs. gcc-8.1) anyway.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
Oh, by the way, GCC 8.1 throws up a lot of new fangled warnings when building lol.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
lol. Nick, I've been using pre-releases of gcc-8 for months... and gcc-8.1 is also now the default compiler on my Archlinux box.

i'm already familiar with some of the changes, new warnings and features.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
I know, I just like talking.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yeah, I think the jump from gcc-7 to gcc-8.1 was pretty minor with regard to compiler warnings, changes needed, etc... far bigger changes needed when going from gcc-4.9 to gcc-6+ ...

new versions of gcc are definitely better with pointing out code issues, more robust and insightful warnings...

I've been tempted to try clang, if even just to see how it compares... although tbh, I prefer gcc and am more used to using it and Intel's compiler suite vs. clang/llvm...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
I've seen a few articles with evidence that code compiled by Clang can execute slower but I may be wrong, maybe it was the compiler speed.

Either way, Clang can be used to build the 3.18.x kernel, check out Flash kernel for Pixel 1 by [MENTION=6842057]nathanchance[/MENTION], he is using Clang 7.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
historically, clang is slower / less performant, but that may not be the case these days with the kernel, not sure. since I don't realy use clang/llvm very much, i'm not in the loop...

yeah, I've looked at Nathan's kernel sources... and I have other kernels/devices where clang can be used. I may try clang out at some point and do some comparisons (and just for a learning experience), but it's nothing pressing, just passing thoughts for now.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] petiolarissean:
Android P support?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] liam_davenport:
No official support from OP if it works it works
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] petiolarissean:
test it and chime back
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] petiolarissean:
no go on android P
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Stable works fine on Android P DP2 on Pixel fyi.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
just an FYI; it's always good to give specifics... I have two versions floating around and as someone else pointed out; stable v2.7 definitely works on P... I know of many people using it.

you never said which version, nor what 'no go on android P' means...?!

anyway, I am in the process of rebasing on P's kernel. this coming weekend I'm hoping that I'll have time to test out P for myself - and I'm reasonably sure that whatever issue is blocking my v3.x kernel from working will be trivial to fix...

but yeah, I won't support P until I've tested it for myself.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] petiolarissean:
sorry,I tried 3.3 but I was also in hurry cause of mother's day and just arrived home but was going to try again but I will wait for update,thank you so much for shareing and responding so quickly.Your works bomb bro!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vijogape:
There are a lot of changes of how the system use the resources that I think that your kernel will break, but I will test it and tell if I notice some difference between stock and custom kernel.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
all good. no worries! ?

well, since you seem to be the expert, i'd appreciate hearing your insights and expertise - please explain the finer points of how android P handles resources differently and give specific examples on how my kernel breaks the way it handles resources...

thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
I'm not trying to answer any questions or anything but rather just state my thoughts on the P beta kernel.

They have it updated to 3.18.100 now and several hundred commits merged for fixing lots of buggies, it's super nice that they're at least trying a little to keep the device running well. :p
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Nick, you do relize that I was replying to [MENTION=7202857]vijogape[/MENTION], not you...right? ...

Ya, we've all paid Google for this support, so this should really be an expectation, I think.

personally, I've found them to be slow to pull in LTS and they really didn't even start to work on lts more seriously until they had pressure on them to do so.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
I know I wasn't being asked but I like to make sure things aren't unclear.. :crying:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] petiolarissean:
lol
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] PFusion:
Hotspot

I like the ROM so far!

Though just 2 issues, how to I get the native hotspot feature working? I'm on a Google Pixel, 8.1 with ezNoShadez MAY 2018 release. I have magisk 16.4 installed.

also anyone know how I can get the floating call status to pop up on my calls? I like that feature

Lastly when I boot up my phone I cannot swipe the screen to login, I need to tap it a few times, is this just a feature of the kernel?

Thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nevermindthelabel:
Must be the wrong thread. This is the kernel
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Phalanx7621:
Out of curiosity, how many folks leave the touch boost enabled? I was considering disabling it, wondering what kind of battery life impact it has for those using this kernel, I just switched to it
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] almightysiman:
I already disabled it and only experiencing shutter on some occasion.overall it is running smooth and great battery life.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AllusionPDX:
Will this work on fire hound or pixel dust?

edit: nevermind, apparently it will. used search feature.

edit 2: caused a bootloop =(
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Dachfenster:
Maybe try the instructions I've posted here:

https://xdaforums.com/pixel-xl/deve...0-exnoshadez-eas-stable-t3709035/post76345121

It worked for me on pixeldust yesterday and I'm pretty sure it would work for firehound, too. If you get a bootloop after the kernel flashing just try a reboot again. If it also fails, it's over lol but I've had it a few times that only the first boot after the flash was a bootloop.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] petiolarissean:
It works on custom roms.Never ran into rom that didnt work,running it on p
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AllusionPDX:
Where exactly do you install the kernel or the boot image in this?

my method(makes bootloop)

Firehound installed and running with twrp magisk the works.

fastboot flash boot.img from main post in slot a and b.

fastboot boot twrp.img(correct version)

adb sideload kernel.zip

reboot

boots to start of firehound splash, crashes and reboots

boots into "no command" with dead android screen

will not go past this point(tested a few times) so i restore backup to previous kernel.

it bootloops once

it auto boots into twrp(restored through backup)

restart to system and back to start.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Phalanx7621:
This kernel is not like others. Most kernels compress their size in order to play nice with TWRP and other things, but they sacrifice features to be able to do this. This kernel doesn't do that. It's size is too large to flash alongside TWRP, so you have to use fastboot to boot into recovery when you're using this kernel. The problem is, ROMS built on LOS (Lineage) have a custom recovery built into them (Lineage uses a custom recovery) and therefore won't boot right with this kernel. It's more complicated than that, but that's been my experience and understanding. In other words, use this kernel with ROMS based on AOSP or stock if you want it to for sure work, and flash with caution on anything else because it may not.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AllusionPDX:
i removed twrp by flashing the boot.img

As to firehound(lineageos based) there have been previous people who have had success with both pixeldust and firehound in the thread previously.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Dachfenster:
I don't flash the boot.img. I just do the steps I've written there. Again, that's not how it's recommended by OP but if it doesn't work for you the other why, why not try it.

For LOS-ROMs the only way I got it working was to install it alongside with TWRP. Someone suggested it was because TWRP's size is smaller than the LOS-recovery's one.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AllusionPDX:
LineageOS Install Guide(firehound too):

download kernel

reboot to recovery

adb sideload twrp

adb sideload exNoShadez-eas kernel

adb sideload magisk

reboot to system

Done.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Dachfenster:
Just a remark: pixeldust isn't LOS-based.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AllusionPDX:
whoops. Well my bad. I just figured it was since people were commenting about them in the same breath earlier in the thread.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bryanx86:
How to adb sideload twrp?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AllusionPDX:
Download twrp 3.2.1-2 img and zip file from the many links around here(I'm on mobile or I'd give you a link)

-Reboot to bootloader

-Fastboot boot twrp.img on command line. Read below for how to use adb/fastboot)

-Go through to main menu of twrp

-Click advanced

-Click adb sideload

-Load up adb on your pc and navigate to it on via command line (ran as administrator, I usually use minimal fastboot and adb and install it directly to c:/adb)

-Type adb sideload twrpzipnamehere.zip I tend to just to rename it to twrp.zip for simplicity.

-profit.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bryanx86:
Oh I thought you were adb sideloading through stock recovery, of course can sideloading through twrp...why not just fast boot flash recovery rather than adb sideload? I misunderstood you
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AllusionPDX:
Habit through other phones/twrp versions that have had issues with that. It just seems to be the most consistent way across devices for it to work without fail.

Edit: at least in my experience.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Phalanx7621:
I was always told never to flash twrp via fastboot but only use it to boot into twrp via the boot command, to always flash twrp zip from recovery. Is this no longer the case?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AllusionPDX:
I did notice some issues with firehound 4.5

a.) screen wouldnt come on instantly after deep sleep

b.) some serious battery drainage issues(probably due to wakelocks or something)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AllusionPDX:
I used to ALWAYS do it by fastboot flash recovery twrp.img however I was told the same across a few different places because I was having issues with it, while I am sure you dont HAVE to do it via boot cmd, I have never had any issues doing it that way vs a few doing it the other way.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
hey can one of you guys post the June boot.img for Marlin??

I'm just doing a final rebuild on the stable kernel, and otherwise almost ready to post builds.

thx
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nevermindthelabel:
https://drive.google.com/open?id=1CVj0pRzwrpwTnX2FiUBfHWlZ5zYtmw1J

md5 6ff07058c2cbea137053a0275197835f
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
UPDATES:

Stable v2.8.1: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v2.8.1_8f17e96.zip

Dev branch v3.4: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v3.4_13ec666.zip

It's getting late here, so I'll post some notes and updates tomorrow.