yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
OK, so I ran out of time lastnight, but wanted to give an update / discuss a couple of things, so here goes;

Android P support.

I had mentioned that I would be trying out P sooner than later - and I now have. however, due to bugs and incompatibilities - I wiped it and won't be switching back until it's officially released... so while I had considered supporting it earlier, i'm definitely not doing it...but as most of you know; stable v2.8 works fine...

I'm Moving all development to Gitlab.

with Microsoft's aquisition of github, it's time to move on... this probably won't happen for a week or two, but I do plan on migrating away from 'winhub'...

Dev branch troubles

to those few people who have had issues or instability... last week a friend of mine tried the v3.3 build and experienced similar problems... we did eventually get it running with stability, but not before wiping the device...

i'm not sure why that instability happens on the odd device, but I think it may be some kind of 'saved state' / saved data by some system apps or possibly within gapps... it's odd, but I've seen similiar issues in the past...

since wiping, my friend hasn't had any issues with the v3.x builds at all... now, obviously, i'm not recommending that you wipe your device - that's a hassle... instead, I would say that when I release my Dev branch kernel for android P - try it again, at that point (when you'll likely be starting with a fresh install anyway)...

lastly, I'll be pushing out updated builds on the weekend. they'll contain the mssing LTS + I have some patchwork for the Dev branch that I've been testing for a few weeks, which I think is probably ready to land...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] xavieraden:
So i am somewhat of a newb here and would really appreciate some help. I have the pixel XL and I am wanting to get the most performance out of it I can while staying close to the stock pixel experience. So I installed pixel dust and it runs way better than stock. But I still get the occasional stutter. I am wanting to install this kernal hoping it will help with performance. But I don't know how to load the stock recovery back. I tried using fastboot on my PC but I keep getting "waiting for device after typing the command. It seeing my pixel because when I type adb devices it shows the serial number. Is there an easier way to load this kernal on my phone?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aoaleman:
Check if" fastboot devices" sees it, if not check that the fastboot drivers are installed correctly.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] xavieraden:
when i do that, it just starts a new line with the same text as before "c:\users\username". no errors, device list etc.

---------- Post added at 02:44 AM ---------- Previous post was at 02:41 AM ----------

its as if it didnt even check. it just jumped right down to the new line instantly. I installed the adb everywhere quick setup. so i am not actually starting the command from the adb folder. i dont have the option since my pc is windows 10 and uses powershell. could this be a issue?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bryanx86:
It doesn't seem like you have fastboot installed, or maybe a quick adb and fastbootreference guide could help you. I found on the through the search optionon the xda labs app. Not sure how new you are....https://xdaforums.com/showthread.php?t=2225405

---------- Post added at 02:49 AM ---------- Previous post was at 02:46 AM ----------

I have to use ./ in front of commands on win10 powershell, took me awhile to figure that out
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] xavieraden:
thanks for the link. i just needed to update my fastboot driver while in bootloader mode. but i did manage to install without installing the boot.img. i remembered that after flashing pixel dust i needed to reinstall magic and twrp because it deleted them. so i just dirty flashed pixel dust to clear twrp to make room for this kernel. so far so good. seems a little snappier, but that could just be the placebo effect lol. time will tell. thanks again for the help. also would you recommend any settings to change to get peak performance without sacrificing the devices health or battery?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bryanx86:
No, this kernel works really well on "stock" settings. Glad you got it working.:highfive:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
An update on the above, as I've had a bit of switch in plans and will be holding off on new builds, for (at least) a few days...

the reason? -> I've decided to rebase my kernel. I have a few motivations here;

#1 - I want to start with fresh && up-to-date vanilla Marlin sources (with LTS included)

#2 - I want to review all of my patchwork (1600 commits, give or take 50 patches)

#3 - I want to re-organize and group patchwork that could/should be applied together

#4 - I'll be removing/omitting any hacks, dropping unwanted patchwork and/or reverted code

#5 - rework some patchwork to include fixes that were applied much later in development.

#6 - simplify certain groups of patchwork via squashing commits && documenting revisions.

#7 - to help simplify (future) rebasing and help with code portability, in general.

#8 - preparation to more easily support Android P on release (and future releases)

The good news; As of today, I've mostly completed the first few steps, which were fairly straightforward... However, in general this whole thing is a bit of a daunting task, tbh (steps #4-6, especially #5) - so it'll take a a bit of TLC and time to finish up... When I do finish, i'll push new builds for everyone. The stable v.2.x kernel shouldn't change much at all (beyond some bug fixes added from step #5). While the v3.x kernel will include some EAS && scheduler changes (which is running on my device already).

that's it for now!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Quick question: What's the importance of flashing Magisk before this kernel? I was planning on it however I totally forgot when flashing; However everything is running fantastic on this June image I flashed before hand.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Phalanx7621:
Because you need root to modify system files from TWRP is the easiest way to say it.

edit: and this is just ME, but I always flash Magisk after a kernel as well. I'm not sure if it's necessary with ALL kernels, but I've always done it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Same, doesn't make sense to me haha.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
so, a bit of a progress update;

I've done the vast majority of the work rebasing the v2.8 kernel (as in, it's running on my device, image included ?)...

there's still a handful of features to merge and also a few bits/fixes to pull in from the v3.x kernel, but all of the heavy lifting is actually finished. ~ v3.4 patchwork should be less work, in comparision. (I figure another 1-3days, depending on free time, and I'll have it all done).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cyberace1985:
running lineagos no twrp and magisk but cant get this kernal to install it all im getting pushed out on a error 1 anyone able to give pointers ive searched a bit and tried reflashing in different order as well going magisk then the kernal and vice versa no dice yet.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Phalanx7621:
Yeah LOS has its own recovery included and there isn't enough room to install this kernel on the partition , some people have said they got it working but I'm not sure how.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cyberace1985:
it just uses TWRP but i installed it sans twrp and its running just fine
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Couldn't you just flash the stock boot image over lineage to remove their custom recovery?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cyberace1985:
personally i tried it and some how i managed a boot loop maybe i didnt wait long enough
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
I've had weird boots before... It just won't boot (I've waited a good 10 minutes) however I force restart and it boots up in under a minute... It's weird.

Edit: Any chance you (nine7nine) are working on preventing that message on boot? Not a huge deal but would be nice.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cyberace1985:
i just tried it again while i had spare time and let it bootloop for like 10 minutes and then hard reset it and it bootlooped again and then failed back to recovery(either twrp or android recovery)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
which kernel version are you talking about?

this used to happen more frequently to me on the v3.x kernel, but doesn't seem to be happening anymore, after some recent-ish changes... it's not happening on the rebase, either. ~ so we shall see (if its going to be a future problem or not)...

yeah, message should be fixed on next update... there's a patch for that floating around, sultanxda wrote it... I haven't used it yet, but I'm planning to / add it. so that should be resolved. ~ The gist; userspace does a sanity check on the kernel config, if it's not stock - then you get the message... So, the workaround is to replace the kernel config with stock config...

This sanity check is mildly annoying, as I do actually use this file (/proc/config.gz). It's handy at times, say; if I want to distinguish builds, when I haven't bumped the localversion (but have changed other configs)... It's not a big deal though.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Any idea when we might see the update? No hurry just curious.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dark2099:
Seriously dude?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Deleted
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
July firmware is up, however;

I have a huge family bday thing today (grandma's 91St bday, also my nephew and a neice's bday)... it's very unlikely I will have time today to update ~ so it'lll probably be tomorrow...

it'll have LTS caught up (already done), Google's monthly stuff, etc..

anyway, i'm sure (like always) you can use the June kernel until I update.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
updates in a few hours;

=> LTS is all caught up (3.18.114) on both builds.

=> I'm running july firmware + exns-eas-v2.8.2 since lastnight.

=> flashing v3.x shortly (to run for the rest of the day).

=> when I get home this evening - I'll push updates

PS: Could someone please post Marlin July boot.img for me?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nevermindthelabel:
https://drive.google.com/open?id=1m8xux0tuyC7STuv3LeEOe2d-FcAoiKBL

md5 = 587BF082FFF4FECAE2AED2EB08C26BC1
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
UPDATED / JULY BUILDS:

exns-eas-v2.8.2 stable kernel: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v2.8.2_f94351f.zip

exns-eas-v3.5 dev kernel: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v3.5_108688a.zip

-> Both kernels latest LTS (3.18.114)

-> Both kernels annoying manufacturer warning on boot is gonzo ;)

v3.5 has a few differences, but nothing to write home about. This is because neither of these (July) kernels are the rebase => I'm publishing them for android P (but doing the work now) && the v3.x kernel for P (although running on 8.1 on my device) has a bunch of changes landing that aren't quite fully backed and ready to use yet.

Examples; rework and porting (more); sched/locking code (much closer to linux/android-4.9, but I'm still chipping away at it), I have some changes coming for MM, rcu, etc... I'm working on improving the use of threaded IRQs (via (re-)prioritizing a few interrupts ~ the benefit here being that this can help avoid potentially contentious situations && also reduce the changes of buffer underruns happening with audio... other stuff. (it's all shaping up nicely, but I still have a todo list).

....

Note: I also update the OP download links (including the latest twrp boot.img).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rbaskin2009:
I wanted to start by saying that exNoShadez is by far my favorite custom kernel, and I have been using it for quite a while. I have Oreo 8.1.0 with the 3.18.16-exNoShadez-v2.0 kernel and a systemless root via Magisk, and was wondering how I might update to the latest July build without losing data/having to start fresh while also updating the kernel and keeping root (a lot I know). Thanks in advance for your help.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] borxnx:
You could try flashing the July firmware without wiping, then flashing Magisk and the kernel. It might work for you. But if you run into any issues, you'll have to do a clean install.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rbaskin2009:
How would I go about flashing the July firmware without wiping? Also, does NoShadez alter /system or /vendor in any way, because if not I might be able to follow the guide for OTA updates here.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nevermindthelabel:
It's actually a pretty straightforward process. I haven't done a clean install in a while, but of course ymmv. Remove the - w from the flashall script. Think it's the last line (fastboot - w update to fastboot update). I have never used the OTA, but in theory if you restore the stock boot.img it should work I think
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] borxnx:
To flash the July firmware without wiping, either remove the "-w" from " the flash-all script (found in the command "fastboot update -w...", or use fastboot to flash the files.

This is not an OTA update. OTA updates are either automatic on your device, or found as an "OTA update" package. The entire stock firmware is not an OTA update.

And yes, if you have root and a custom kernel, you have modified /system and/or /vendor. Don't follow the guide for OTA updates, use a regular fastboot method.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Just to be clear, the latest release works on the Dev Preview?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I tried it for testing purposes (any kernel 2 testing) and it worked great for me
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Thanks, however I just flashed it and it's a no go. I'll try without flashing Magisk ;)

Edit: Bootloop every time, even without flashing Magisk. I've tried both new updates.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Hm, I'll try it out later, it did work for me though last time I tried it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Maybe I'm missing something. I flash stock boot.img via fastboot (both a and b partitions) and then boot twrp (not flash) and flash the kernel. Then I flash Magisk, and finally reboot system. It goes to the Google logo and restarts. The last time I tried it went into a recovery loop and had to flash stock firmware. (Removed -w)

One time, after the Google it showed a white "Android" on a black screen before it rebooted. It was there for 1/2 to 1 second.

I've even tried not flashing Magisk
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Before flashing the kernel, flash magisk. So flash stock boot.img>fastboot boot twrp>flash magisk>flash kernel>reboot

You won't need to reflash magisk after the kernel either :svetius:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
It worked! Much appreciated! Also [MENTION=7810360]nine7nine[/MENTION] , thanks for the dope kernels!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
[MENTION=266157]shag[/MENTION]913 [MENTION=4902973]borxnx[/MENTION] [MENTION=5996385]Nevermindthelabel[/MENTION]

i appreciated u guys stepping in and helping getting issues sorted out... i've had a craxy busy day (and week for that matter), so i haven't really had time to provide assistance today...

I just walked in the door and am 100% having a nap. lol. I guess hacking several nights until 4am qnd then working all day (rinse and repeat) has finally caught up with me ?

no probz... and speaking of 'dope things', i have something dope that i'm working on that should be in the next v3.x build. - hoping to push that out in the next couple of days (almost, but not quite ready just yet).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bryanx86:
Just want to say I love this kernel. Very snappy. I have a question about Mac randomization option though. I've enabled through ex kernel manager, and set option to 1, and set to apply on boot, but it shows the same Mac address in system settings on reboots. I'm running dp4 so maybe this could be the reason? Thanks for all your hard work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rbaskin2009:
I tried this, but when selecting zips in fastboot TWRP there was an option to verify the zip signature for exNoShadez_eas_v2.8.2_f94351f.zip which then proceeded to fail during installation. I unticked the verification option, and it installed fine; hopefully that was the right choice. Everything seems to be working nonetheless.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] borxnx:
I have never checked the signature verification option in TWRP for as many years as I've used it. I'm not even sure what that option is for (does it look for a nearby md5 and check it against the zip or something?) but I usually use my workstation to verify file integrity rather than my mobile device.

I would posit that you should only ever check that box during any TWRP installation if there are explicit instructions to do so.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rbaskin2009:
It's checked by default in fastboot TWRP. I'm really not sure what it checks or why it failed, but I figured I'd let everyone know in case they come across the same issue.

Edit: I did some research, and the signature verification checks to see if the zip has been "signed properly" by the developer, but I'm not really sure what that means. It apparently can also detect if a zip is corrupt, although a better check would be to verify the MD5 sum. Can someone here post the MD5 sum of the zip files so us users can verify that our downloads worked?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
How do you "verify file integrity"? I always just download and flash lol.

Also, any plans on wakelock blocking?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] borxnx:
By checking the md5 (or sha-1) hash of the files you downloaded to make sure that the downloaded file was an exact match and there were no lost bits during the transfer. This used to be more important than it is now, the internet's gotten much better over the years.

And no, I have no plans on wakelock blocking at this time ;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I'll look at this tomorrow, I've run out of time today, gotta friend's bday bqq tonight && this morning I was working on something else (so I kind of forgot to look at this).

nope. I think wakelock blocking is generally not good, being as it can/does break things.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Ah thanks! And that's unfortunate ?

Makes sense, usually my calls or something stop coming in haha.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yup. some devices or apps will have problems with notifications and that kind of thing... My personal opinion; it's a garbage feature. completely unnecessary...

The only time that I can think of where I found blocking wakelocks useful was on an older phone, running a cyanogenmod mod / lollipop ~ where things where broken and the only way to fix the battery drain was blocking a particular wakelock (this was later fixed in CM and wasn't something any of the kernel wakelock patches even address)...

you shouldn't be having problems with wakelocks + my kernels, so it really isn't something that I want to add... it's also too easily abused, users not knowing what they are actually blocking and what problems could arise from doing so.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
[MENTION=1007992]everyone[/MENTION]

I'm hoping to push new builds tomorrow or monday.... assuming; I sort out the mac randomization issue && also resolve this last little immediate issue with a (schedtune based) driver that I'm working on for v3.6...

On the second part; for the last week or two I've been working on a driver that replaces "perfd"... It allows this kernel driver to manage schedtune more dynamically (schedtune is a key part of EAS and has pretty much everything to do with the Pixel's good performance && energy saving...).

Right now, my code is a (working) proof-of-concept and is working very well (not published yet though. will be soon)... It allows more granular control of schedtune / cpu boosting and performance/energy biasing and it is completely event-driven. The layout of schedtune's task & groups (CGROUP_SCHEDTUNE) is also different on my v3.6 kernel vs. stock kernel / userspace... With my driver / setup, it looks like this;

/dev/stune/audio/schedtune.boost
/dev/stune/background/schedtune.boost
/dev/stune/foreground/schedtune.boost
/dev/stune/gfx/schedtune.boost
/dev/stune/rt/schedtune.boost
/dev/stune/top-app/schedtune.boost

(this requires extra setup for cpusets + schedtune, but is already handled/working/tested in AK2/magisk).

The gfx and audio schedtune task cgroups don't exist outside of my own kernel use... I use these groups hooked into certain events (places/drivers within the kernel) to allow performance biasing different types of workloads. (I'm an audio guy ~ so being able to use schedtune more effectively to prioritize my audio stuff is great ~ but likewise; it's also possible to bias gfx pipeline or anything else)...

There are a number of tunables, which should (eventually) allow for creating different energy and performance profiles and there are already a number of events that can be configured via sysfs / modparams... right now, my module params are a bit overkill ~ but I need them for testing purposes, some won't end up being exposed to users...

So assuming today's build (running on my device) pans out, is reasonably good on energy consumption vs. performance ~ I should be able to push out a release for people to test....

After a few more revisions + a week or two of testing ~ my plan is to rebase the driver and all of it's dependencies on msm-3.18-eas ~ so that other devices / kernels could also use / pull in the driver, if they wanted to... It's obviously only been tested on EASv1.5/my kernel - but I don't see why it wouldn't work on say; stock marlin kernel (which uses EAS/schedtune, as well) or non-pixel devices that utilize EAS/schedtune.

anyway, I'll have more info on this soon && when I push a new build for v3.6 I think I might do a bit of a write up on features and such - because I'm not sure if I've ever really done that yet (and being as in the last while it's picked up a lot of features), it might be a good time to do that.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Dachfenster:
Just a little remark: Solid Explorer now works again flawlessly regarding root operations with this kernel (the root directory used to be shown as empty).

In the changelog it says "fixed some root access issues".

Still my go to kernel, thanks for all your great efforts and detailed explanations! :)