yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Shaka401:
You're new to this which is fine, but there's clearly a disconnect between the directions and what you're doing.

I'm not sure how we can explain further, so my suggestion is that if you still want help, take a video or screen captures of every step of what you're doing and start over (including downloads). If you hit an issue again, you can hold to your Google drive, and we can review start-to-finish where you're going wrong.

We, including the dev, are more than willing to help, but you'll need to give us a bit more to go on here.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] drxikh:
Would there be any negative effects for using FlashFire to flash the kernel? I have successfully flashed the latest version using FlashFire, but ended up with poor battery life. I think poor battery life may be attributed to something else as I am still getting poor battery life following the OP instructions. I just can't put my finger on what yet....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
If you followed the instructions in the OP to install the kernel, you should check what apps you have installed and eat up your battery. I get constant 6 hrs sot over 2 days.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] drxikh:
I have looked using BBS and GSM, but no apps or wakelocks stick out. GSM reported the biggest battery spenders were the Android System, Screen, and Kernel. I was only able to get just under 4 hrs of SOT on 13 hours of use all on wifi before I had to plug it in. I am hoping that it still has to calibrate itself, as I just redid a fresh install yesterday.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
I take it this is on the Dec update? Give it a few cycles and hopefully it gets better.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sbcrumb:
Running this ROM https://xdaforums.com/pixel-xl/development/rom-pixeldust-marlin-t3581750

Followed the OP directions getting boot loops. Does this kernel only work on 100% Stock?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] liam_davenport:
Don't install twrp zip and I flashed ElementalX kernel after LOS I also stuck at bootlogo/bootloop reflashing magisk after the kernel booted up for me maybe it's the same case here
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I haven't tested and won't be testing against LOS. I only test stock ROM + magisk... in theory, it should work. that is an 8.1 ROM, as someone else suggested you could try flashing magisk, after the kernel...see if that makes any difference... maybe it's an issue with LOS's native su? no idea.

but aside from that, off hand, no idea why it would be bootlooping... I can take a look at their kernel sources later, see if anything pops out at me.. not a ton I can do / I won't be replacing the stock ROM to test with LOS - too much of a hassle for me.

edit; I seem to recall of 8.0 / pixeldust someone having an issue flashing custom kernels, but I don't remember the specifics and not sure if they ended up getting it working...

let me know, if u do get it working. mileage obviously varies with a setup I can't test against. thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
I would suggest the user triple check the steps. I was able to flash just fine on sailfish FYI.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
cool. thanks for pointing that out...

looking at the Los marlin kernel sources, I didn't get the impression that there was much patching or any obvious reason it wouldn't work. good to know it should work fine. thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sbcrumb:
I did also try ElementalX but that didn't work with pixeldust. I wasn't to hip to go stock but I might have to I assumed pixel was close enough to stock it would work. But I followed your instructions with you posted Dec bootage. And flashed magisk15 right after. Then I get the pixeldust boot screen for 2 or 3 secs then it reboots.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I would think it would work fine, maybe not though... but it sounds like it may have for the user a couple of posts up.... but I can't test, so no way to know for myself....

btw, December boot.img is only for removing twrp or reverting to the stock boot.img for the stock firmware... your custom ROM would have it's own kernel / boot.img... so the stock boot.img wouldn't be something you would be using to begin with...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] borxnx:
Latest Pixeldust version (8.1.0_r1, released 12/26/2017) supports custom kernels and Magisk 15. Earlier builds apparently do not, from a quick skim through that thread.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sbcrumb:
Ok I will need to get the boot.img for pixeldust. It is not in the .zip it is a bin file so not sure how to extract it from that. Pixel is all new coming from the Nexus line.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] liam_davenport:
I just flashed this kernel with Benzo rom I'll give my instructions maybe that'll work with pixel dust I don't have time to test Pixel dust sorry

1. Flash stock factory img to both boot slots

2. Make sure in Slot A and boot twrp img: fastboot boot twrp-3.2.0-0-marlin.img

3. Wipe System, Cache, Data

4. Copy rom to internal storage and flash, Reboot and setup (optional) (NOTE: For pixel dust you will need to flash the rom reboot to bootloader fastboot boot twrp-3.2.0-0-marlin.img then flash gapps and reboot)

5. reboot to bootloader flash twrp img again: fastboot boot twrp-3.2.0-0-marlin.img

6. Copy latest exNoShadez-eas zip and Magisk 15.x to your internal storage flash the exNoShades-eas zip followed by the Magisk 15.x zip and reboot = Profit!

Hope that works for that rom :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
[MENTION=7810360]nine7nine[/MENTION] do you mind sharing your recommended settings for your kernel? Running great here, battery is awesome.

---------- Post added at 10:37 PM ---------- Previous post was at 10:36 PM ----------

[/COLOR [MENTION=7810360]nine7nine[/MENTION] do you mind sharing your recommended settings for your kernel? Running great here, battery is awesome.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I generally don't stray too much from the defaults that I set, that's why they are defaults.... aside from randomizing my Mac address and setting up performance mode with the performance CPU governor to avoid CPU frequency scaling, when using a select few apps...

sure, I do make available a number of things that u could tweak, but my perspective is that users or myself really shouldn't have to spend much time trying to get a good OOTB experience. So I tend to let the kernel do it's thing - then adjust userspace/android for further gains, improvements / to my liking. Examples;

- disabling/removing apps that I don't use.

- disabling most sync'ing and/or auto-updates

- disallowing most apps from running in the background, or using data in the background.

- amoled friendly substratum theme (swift black).

- WiFi, NFC, Bluetooth, location, etc disabled when not in use (although my mobile data is always on).

most of the above is centered around improving battery life, but I also find auto-sync/updating annoying, aside from email. I try to keep things minimalistic, not too much running in the background, etc...

I do tend to swap out / replace stock apps. examples;

Apex launcher (I dislike pixel launcher).

PEPmail (over gmail app... but the version of PEP that I use isn't publicly available yet).

Firefox nightly with a few plugins, instead of chrome.

I always get rid of Google app, YouTube, etc. (most of Google's apps).

....and a few apps to customize/control settings, interface, adblocking, firewall, vpn, etc.

so yeah, not much kernel tweaking happening on my device... mostly changing how the stock ROM is setup...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
Awesome, I haven't touched it and it's purring. Similar tweaks to stock ROM on my end. Appreciate the detailed response, thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no probz, your welcome.

occasionally, this question or similar ones come up; and although I've answered this kind of thing before => I thought it might be a good time to answer in detail again... so it's good that you brought it up. thanks!

I tend to subscribe to the K.I.S.S principle. So the less tweaking, the better. it also makes testing and/or potential issues/bugs easier to figure out, if/when they crop up... just simplifiies everything.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
Agreed. Is double tap to sleep on lock screen kernel related. I believe pixel dust has the feature enabled, would be convenient since we have DT2W
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I know very little about pixeldust, what features it has, etc... however, from looking at the pixeldust kernel sources earlier, I don't recall seeing any relevant patch. it's probably implemented in the ROM/lockscreen. no idea.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Love me some Swift Black substratum theme. :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
Stock with your kernel and magisk leaves little to be desired. Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yeah, same for me. no need for a custom ROM, really... stock ROM is well-optimized...

I also don't really like using custom ROMs. I would need to be compiling it myself. as if I was to want to use non-stock ROM, there would be features that I would want, not really present in most custom ROMs... there would also be things that I would want removed, probably...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
Well if you decide to make one we'll all Glady run it! Hahaha.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
haha. too much work and requires too much space on my archlinux box. unfortunately.... I maintained my own ROM for a few years, it was really great but too time consuming ...plus, sooner than later I'm going to be working on more than one arm64 SOC / android kernel...

I've got a hikey 960 soc, a Pixel 2 XL on lend and in the next few weeks, I'll be recieving a yet-to-be-released Soc, thru a friend... I'm pretty excited for the last one, although hikey will be a nice board to work with too... so, I'm going to be working on 3.18, 4.4, 4.9 and 4.14 android kernels... not really related to my exns-eas kernel, but there is some overlap...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
Have to agree, your stock settings work great for the stock Rom. I get great battery life without changing anything besides the black substratum theme and some apps.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Just curious, what is preventing bringing the marlin up to 4.4?

Are there hardware dependencies or is it possible to backport 4.4 to the marlin?

Just curious. Thanks in advance.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sbcrumb:
This is getting it booting into PixelDust. However now it complains my vendor image is not the right one. But still appears to work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] liam_davenport:
Just reflash the vendor img in twrp or fastboot and you're good to go
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sbcrumb:
I tried that with no joy. So I gave up on the custom ROM road and loaded up stock with the kernel and so far doing well just setting it up.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nil253259:
Is it material :p
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yes, but also other features... the versions that I use aren't in the playstore / not a public beta or anything like that...

I've had some interaction with the devs, going back months and months, did a lot of bug reporting on the initial material and keysync builds... the builds still have some rough edges, but lots of issues that I ran into were fixed promptly... so barring a few minor issues, good enough... it's just too bad that I can't use my protonmail account with it too.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
hello everyone. been rocking stock 8.1 on my pixel xl + ex kernel, and i wanna give this one a try aswell. can someone tell me the right steps i have to make please? also iim running latest magisk too. thanks in advance
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
All steps are in the OP.

If your coming from a different custom kernel :

- make sure you have the stock recovery (OP doesn't support if TWRP is flashed)

- flash stock boot.img on both slots (you'll find command in OP)

Using TWRP (fastboot boot TWRP_marlin.img)

- flash the latest stable kernel

- flash latest Magisk (v15.2 I think)

- Reboot & Enjoy.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
hey all,

I know the Jan 2018 release is out today, however ~ I won't push any update until tomorrow. * That's the first chance I'll have to be at home, in front of my linux box, to patch the kernel and update. ~ My holiday / housesitting gig isn't done until tomorrow.... At that point, I will push a quick update fo Jan 2018, but after that I'll be doing a rebase and numerous updates to my kernel... So within a few days of that; I will likely push a bigger update.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
If the goal is to port marlin to 4.4, you wouldn't backport at all (that would be a silly/backwards way to go about things). You would use a 4.4 kernel to begin with; migrating all of the Marlin / device specific kernel code into the new kernel, updating/fixing all of the drivers (and/or possibly re-introducing support where qualcomm has removed it, as they moved on to a new soc). But it's a problematic process ~ qualcomm developed msm8996 for 3.18, you have to deal with vendor blobs (that you can't recompile, that expect things to work a certain way), a lot of interfaces change, functionality, etc. It's possible, but would require a lot of effort (far more than cherry-picking or small rewrites) for arguably very little gain (given the short lifespan of devices, the pace that technology moves at, etc)....

I began a port (a month or so ago) and was able to get past a number of initial hurdles, but when I was getting into the really ugly part of the porting process at the beginning of December, I decided to not bother.... For myself things have changed; I picked up a couple of other devices, running newer android kernels (hikey 960, Google Pixel 2 XL with another very new SOC on the way, as well), so my own needs for android kernels 4.4+ based device is fulfilled ~ I can start porting some code / features to newer kernels (and run it on real devices vs. using an emulator for testing/use), which is awesome/ideal.... Which was the main motivation for even considering porting Marlin to a newer kernel, for me.

Generally, all of the android/custom kernels you see with backporting are only touching a very small amount of code in the kernel core and possibly a few drivers, ***when compared to the actual size of any given linux kernel source tree... Backporting is only really useful for porting newer kernel features back into an older kernel... In theory, a person could backport all of the core kernel code for 4.4 to marlin, but to put it in perspective; you would still only be touching a maximum of 5% of the kernel sources (if even, and you'd still need to fix the broken drivers need for the device). Hypothetically, after such an effort ~ you'd be running an android-4.4-like kernel but it would be a largely broken and somewhat unmaintainable 3.18 kernel tree. Most kernel configurations would be utterly broken (drivers, debugging, etc). it would also be a hassle/maintenance burden; in terms of using android monthly security patches and LTS with ease.... So backporting really isn't a path to a successful port, at all...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
Take your time, just enjoy the days left with your family and friends! ;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Thank you for the explanation. You'd be a good teacher man.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stryker09:
You got a P2XL? Here I am still holding out hope to see your work on the Pixel 2 devices :fingers-crossed:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
Thanks a lot mate. Unfortunately I'm not that good with fastboot commands and I just wanted to make sure I don't mess my phone up. Thanks for the response, appreciate it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Shaka401:
How far have you gotten so far?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
Just ask if you need any confirmation/help. Better ask than doing wrong.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no probz... that's why we don't have a easy upgrade path for android kernels. most of the code is out-of-tree. examples; no proper support for kgsl, adreno drivers, etc...

well, I do have the p2Xl, but it's a loaner, so I can port some code to android-4.4 kernel. I probably won't have it for long enough to work on or be able to support a kernel for it. I am kind of tempted to trade in my OG pixel for a pixel 2 (non XL version), because my pixel is paid off and trade in value is still high...

but then again, my pixel works so well and with all of the horror stories I read about with RMAs for the pixel line, I think I'd rather just hold off for now
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
Well I was gonna flash the kernel but then I saw the OP's post and I'll just wait for the next release to flash it together with the Jan build of the stock ROM too.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Cool. It'll be a couple / few hours yet.

On top of adding in the android Jan 2018 chunks, updating to 3.18.91 and a few misc changes ~ I also have to update AnyKernel2, as osmOsis has made some changes over december (some of it is pixel && magisk changes), so I'll need to get all of the latest binaries and adjust some stuff (and test it too, obviously)....

But I am downloading the Jan 2018 firmware now && compiling the kernel (although compiling the kernel only takes 30sec. each run. lol) ~ So, I will probably flash it, run it for a while + sort out the AnyKernel2 / flashable zip stuff, before publishing a new build.....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
take your time mate, theres no rush. thanks for everything you do!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
hey all,

So I'll have an update in a couple of hours (i just want to run it for a bit) ~ I've updated to Jan 2018 firmware, have updated the kernel with the latest Jan patches, LTS 3.18.91 and have also updated Anykernel2 / flashable zip (integrating the latest changes for Magisk / overlays and Pixel changes).... The updating process going forward will be slightly different. (but a bit better, in a couple of ways).

When i push the update - I will update the OP instructions and post here too.

In a couple of days, as I mentioned; I will be doing a bigger kernel update, as well. But I just wanted to get a Jan 2018 kernel up, asap.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
I'll download the january factory image to be ready for your kernel... :D
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
UPDATE: https://github.com/nine7nine/Apps/raw/master/exNoShadez-eas_595ec20.zip

No major changes, beyond Jan 2018 patches, LTS 3.18.91 and updating the AnyKernel2 flashable zip. I do have kernel changes coming, but I wanted to quickly push this update out to go with the Jan 2018 firmware. No time to work on kernels until the weekend.

Ok, so from now on - do NOT flash magisk zip after the kernel, instead magisk should be installed before-hand (the flashable zip will detect it's presence).... So, if you've just flashed the Jan 2018 firmware (with the stock boot.img), you will need to flash Magisk first ~ followed by my kernel zip.

This is now the process, whenever coming from stock or a monthly firmware update (where you've lost root). NOTE: On subsequent kernel updates, with Magisk already installed (between Monthly firmware updates), you can just flash the kernel (you won't lose root/magisk).

Please also be using the Latest Magisk Beta (v15.2); https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
Great !! Flashing your kernel will be even more easy.

Updated to Jan build and your last build !
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Yup. It should be simplified. I was actually going to do this for Dec 5th release (update the AnyKernel2 stuff), but I ran out of time - plus, with the updates osmOsis made to AnyKernel2 over the holidays, it was better to wait (not that I knew that at the time. lol).

I still have to double-check, but non-rooted devices probably work too now (although, I don't recommend using non-rooted. lol).... I also need to double-check SuperSU too - but I'll do that Later. I'm not a fan of SuperSU && I tell people to use Magisk anyway, which as far as I am concerned => _should_ be the defacto-standard of rooting on Android.

anyway, this weekend I'm going to rebase this kernel / work on the next release.

Then assuming I have time (after pushing the next release), I'm going to start to dig into my new devices.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
Trying to update using the OTA file to no avail, I'm giving up for the night, going to get some sleep.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yeah, I never use the OTA method. I always use full firmware images + flashall script (without the -w flag). It's cleaner, as differential updates patch the system - which occasionally introduces subtle bugs and instability... flash-all wipes all of the partitions (minus data) and replaces them. I would recommend not using OTA, personally.

although, obviously OTA can be done with flashfire (although, I've never tested it).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
Yeah I'll do that in the morning. Tried flashfire but that didn't work either, no worries going to get some sleep now it's gone 2am, thanks for getting back to me.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
sounds good. nite!

It could be that flashfire hasn't been updated to handle the recent changes with AnyKernel2. They are very new, like mid-december to Jan 2 commits... Or maybe it has to do with recent Magisk changes (my zip is intended for the latest magisk beta).... But idk, having never used flashfire ~ maybe I'll take a look, when I have more time and try it myself.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
Thank you for your continued work. Will flash this tonight. Thank you again.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kentexcitebot:
Hey all,

In case something goes wrong with the flashing process and you need to revert back to the January stock boot image for Marlin: see this link to my Google Drive:

https://drive.google.com/open?id=1qz0dze4ceL-1FKdN37CT1b2-sbMgSzZi

XDA doesn't allow me to post with attachments ¯\_(ツ)_/¯

Keep up the good work OP :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I see no attachment, but if you post it, I'll do as I have previously done and add it to my github / post the link on the OP
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kentexcitebot:
Yeah, XDA is preventing me from posting the boot image. I'm editing as I type this. Thanks for catching though!

Edit: XDA has a problem, so I posted the January boot image on my Google Drive. Feel free to post it to the OP!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
post it here: https://tmpfiles.org/

and shoot me the link (or point me to your google drive link. lol)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kentexcitebot:
https://tmpfiles.org/download/9499/MarlinStockJanBoot.img

Mirror to my Google Drive:

https://drive.google.com/open?id=1qz0dze4ceL-1FKdN37CT1b2-sbMgSzZi