yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Cool. thanks ~ I've updated the boot.img on the OP / github.

I had one for Sailfish, but not Marlin. appreciated.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AlkaliV2:
I'm downloading the marlin image to upload now. Give me about 15 minutes

Edit: done https://www.androidfilehost.com/?fid=889964283620776073
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Donric13:
Thx for update. After 1 day with stock kernel is great to have the snappiness and battery life back from your kernel. Just wondering what further things you gonna optimize because in my feeling your kernel seems already near to perfection.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
so I need some help. I flashed the boot image, then magisk, then the kernel but then it just boots to the android symbol with no command.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
nevermind, got it sorted, up and running again :D
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
Same here, always factory image without the -w.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Queentus:
what should I do with this error :confused:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Sgace:
I think you have twrp installed instead of booted, am I right?

Get rid of twrp install and then fastboot boot twrp and flash kernel again.

Cheers
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Queentus:
wow you're right. I thought installed and booted are the same. So I was not reading OP carefully enough. Sorry everyone.

---------- Post added at 04:29 PM ---------- Previous post was at 04:19 PM ----------

can I ask one more qustion...? flashed the kernel successfully, but my phone blacked out and reboot itself right after the bootanimation, the same happens once last month after I flashed NSFW kernel and I had to give it up. what's the problem here?

thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Donric13:
Had similar issues when coming from other kernel and arise mod. Had to reflash factory image (without - w to keep data) and then start to flash the kernel. Since latest update don't forget to flash magisk before kernel! Maybe this helps.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AlexBrookes:
Looks great! Does this kernel support color tweaking for the display? I didn't see it listed in the post.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nil253259:
Not sure, might be placebo...but scrolling on chrome seems slightly choppy.....again, I'm really not sure.... whatever it is, it's really minimal and doesn't seem to happen always.. please have a look if you find anything similar...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yes, it does. KCal colour control.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
hey, I'll take a look. I actually tend to use firefox... I do have chromium swe (snapdragon optimized version that has all of the adblock, privacy plugins), it scrolls smooth like butter...

but that's obviously not the default chrome. will look now
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Speaking of chromium builds, why'd they nerf the chrome sync for unofficial builds ?

I used to use tuga but without chrome sync it's useless.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stryker09:
Okay so for some reason:

1. OP kernel boots up to recovery

2. Test kernel results in a bootloop

I have flashed the stock boot.img to both slots as per OP, reboot bootloader, then fastboot boot twrp img, then flash kernel, in that order, then reboot system.

Is there anything I can provide in terms of logging?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
OK. this is not typical. I have questions;

1. are u running Oreo-8.0 November firmware? if not, that's your problem... I don't support outdated systems.

2. op build has never booted to recovery. test build may bootloop, but on subsequent reset / reboot should boot fine...

3. are u flashing anything else along with the kernel?. ... supersu, aroma installer, etc? if so (and u are running the latest firmware), try flashing just the kernel.

something seems fishy here.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stryker09:
1. yep i am

3. tried both with magisk 14.5 and just with the kernel on its own, to no avail

interestingly i flashed back the stock boot.img and it went to recovery as well, so i reflashed the system image to get back in, now will proceed with attempt #2 :)

update: still boot looping on test kernel, flashed stock boot img and could get back in to the system, going to attempt #3 on OP kernel
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
OK. so I had a look. I did notice s slight lag, when chrome was loading and caching some images in a search, but they were minor, neglible. it's also hard for me to do a 1:1 test; as i'm enrolled in the beta for webview....

anyway, this could be a temperary hiccup, as i'm merging in planned changes to subsystems, it also could be due to biasing determinism over throughput (although this is neglible)... give me a build or two to see if i can improve that ok?. .. that's for bringing it up... admittedly, i despise chrome - so while chromium swe gets tested chrome hasn't had much love. lol.

it orobqbly relies on some proprietary crap, or has some spying feature - like other chrome features that have been ripped out... not a chrome fan.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
don't use the test kernel, unless you've already bern using the release - there is no point. you have no reference to test against, having not used the release... plus, it's a test build, may have instability...although it doesn't here, at all.

yeah, try the op.... also... maybe try actually powering off your device, first.... also, do you have any odd ball software starting on boot? any init or scripts, etc???. ...

something is very much, atypical about your setup.

I have tons of people using the release and quite a few testing the current test build. no probz...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Yeah I should just start using autofill and import my bookmarks once and be done with it.

Btw I tried to flash the test kernel but it would just bootloop. Couldn't get it to boot and I tried all my tricks.

---------- Post added at 07:21 PM ---------- Previous post was at 07:20 PM ----------

Are there kernel differences with OP1 and OP3? Because I'm on Nov Canada/Fi release.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
op1 op3??? there's only one build on the op... I stopped supporting anything but binder_rt (and that download hasn't changed).

Edit: or did u mean OPR*???. .. that I do not know.... I can't be downloading all of the Marlin images to compare, either... on sailfish. I'm using Canada/fi build. I'm on Rogers...

what are all of your tricks? just curious...

I'll try n post another test build later. I've already made some changes - it could be that it has been resolved in my current running test build.

for now, just run the release. maybe on some Marlin devices there is an issue with that test build. sailfish is fine...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stryker09:
alright so the OP build booted fine now, but continued to try the following:

1. dirty flash test build over working OP - bootloop

2. clean flashed test build over stock boot image - bootloop

3. clean flashed OP build over stock boot image - success

3. flashed magisk 14.5 over OP build - success

i dont have any weird stuff going on at boot, i do just general stuff in exkm like default io scheduler and stuff, no init and weird scripts :/

but im genuinely excited with your work! :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nil253259:
Yeah, it's negligible...and your correct that the slight bit of lag happenings when chrome was loading...also sometimes when you press the back button and close chrome to go back to home screen, I think I can see some frame drops... ?. But they don't bother me much of course

Thanks!

P.S. though I'm Sailfish, this thread seems more active.. so I'm replying here :p
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
OK. thanks. this is helpful.... I will post a new test build later. I suspect I might know why the test build is having issues on Marlin... if I'm right my changes have already fixed that issue.

so my release is fine, boots, etc... great - and this is why I never rush to update the OP download ??? . test. test. test.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no no. please use the sailfish forum. this is for Marlin, you might cause confusion... this thread isn't more active, it's just newer only a couple of days old.... sailfish forum has 5000 views and almost 3/400 replies...

this just seems more active because it's just getting started.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
[MENTION=4429310]Nil253259[/MENTION] - also, every few times I go back to the main pixel forum page, it says my thread is one of the top most active thread in the whole forum.... so yeah, definitely more active than here....

regardless, having Xl users post here and sailfish users post there is better - although we use/the same kernel. the zips are packed for each device. XL's display and settings are different, they have a bigger battety and their init rc is different than sailfish, etc..... so ya, don't post here. XL thread only.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
[MENTION=1007992]everyone[/MENTION]

Could I get you guys to post the stock factory firmware versions of the boot.img(s) for Nov??? (opr3, opr1)

I would like to do a diff comparison between these to look at any differences between them, but I'm not inclined to download multiple factory images - when I only want this particular file.

thanks.

EDIT: I do have another test build uplaoded with a couple of changes; ready to be tested - but I kind of like to look at the boot.img(s) first.

but if, you are eager to see; https://github.com/nine7nine/Apps/raw/master/Marlin_exNoShadez_eas_3.18.84_Binder_RT_a1f0684.zip

NOTE: boot issues are always hard to trackdown, so if you aren't in a big rush. wait - but if, you want to see/test - go for it! it will at least verify if one particular commit is responsible (on my end)...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Yeah that's what I meant, derp.

I'm also on Rogers in Vancouver. Isn't that new LTE rollout just the bee's knees?

Yeah I'm back on the release binder rt build.

I just meant all the tricks to get it to boot, I flashed back to stock kernel, wipe cache etc. Nothing fancy.

---------- Post added at 09:01 PM ---------- Previous post was at 08:59 PM ----------

Just setup fastboot on my Chromebook so I can do this easy peasy now.

I'll flash the new test kernel and report back.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
all good - I figured out what you meant. Just confusion - OP = original post, OPR = firmware LOL.

My bad ;)

also, if you don't mind - post your stock firmware boot.img. I'd like to collect OPR3/1 ....

this shouldn't make a difference (because there are no differences between OP download and test build ramdisk && the way anykernel2 patches boot images) - but hey; I'd like to cover all bases - trying my best to make sure Marlin is well supported

I very much would like to continue with the changes present in the test build - as it's lining me up to add some new features (all kernel / non-user facing stuff, but desired) .
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
well, I have a few areas I'd like to improve. I've been tinkering with binder to speed up asynchronous transactions and performance, in general... another example; years ago linux use to have what was called 'the big lock' which was a bottleneck for performance back then.... even when they removed the big lock, it largely was just moved into another layer / subsystem where the impact was less noticeable. however, on mobile, it is more noticeable / has more of an impact than say, a server or desktop... So, I'd like to have a stab at improving locking in the affected subsystem and driver code....

there's also a handful of patches from preempt-rt that I've been thinking about merging in, as well. as it would allow me to have better control over scheduling... I actually have a preempt-rt kernel for Marlin, but realtime linux isn't well suited for our phone (but it is handy for some testing/experiments that I've done).

did it boot into android, after the initial reboot?

I used to have that happen, every once in a while (like 1 of 50 flashes), but it hasn't happened even once, since I reverted some changes to smpboot.... it's odd when it happens and the logs / traces vary... so off hand, not sure why itrebooted for you..
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
Would just like to get everything straight. If I follow the OP, is that the same as using flash-all? As flash-all is not working for me, when I get to reboot system I get asked to install TWRP, if I choose no my device boots with "no command". I had to recover my phone using the Rescue OTA method and would like to start again with a blank slate. I'm on a Mac by the way.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Queentus:
Unfortunately no. Reboot happens right after the bootanimation shows up.

I've been having this issue for a while, but only on NSFW and exNoShades, EX and Kirisakura works fine. Just don't have that luck to try new options :crying:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Sgace:
Happend to me too. For me the solution was going back to fastboot, boot twrp again and reflash the kernel. After that my pixel booted to system.

Cheers
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no flash-all.sh is for flashing the entire firmware... the OP makes no mention of flashing firmware, only flashing the stock boot.img, only if TWRP has been installed.... (and then flashing magisk, the kernel...).

however, if you need to flash the January Firmware. flashing the firmware on a Mac, should be the same as on linux. (Mac and linux distros both have bash shells, sh scripts, etc. both are *nix systems, very similar environment.). so....

1. edit the flash-all.sh script, removing the -w flag (and save it)

2. Open the terminal app; cd into the directory with the flash-all.sh script and execute from the commandline:

./flash-all.sh

3. after that completes, boot into android and let it finish applying system updates... then reboot into twrp.

4. flash magisk v15.2 zip

5. flash kernel zip

6. reboot (select no to installing twrp).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
OK I'm going to give that a go now
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
Been pretty impressed with the kernel so far. But I want to ask you guys, is it possible to have twrp after the kernel is installed?

Also, is anyone using L Speed for extra battery tweaks or is not needed with this kernel? Tia
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kentexcitebot:
There's an important step you forgot that may prevent flash-all.sh from executing. Depending on the Linux distribution, flash-all.sh will not run with the latest fastboot from Google sources nor from the android-tools in the distribution's repository unless you edit out these lines from flash-all.sh:

"if ! grep -q dtbo.sig $(which fastboot); then echo "fastboot too old" exit 1 fi"

otherwise the script will complain about fastboot being too old and will quit, because dtbo.sig doesn't exist in the fastboot binary at /usr/bin. I'm not sure if macOS or Ubuntu requires the user to modify out those lines as I'm running Fedora (I had to remove the lines for flash-all.sh to run), but nevertheless: I felt this needed to be said.

As mentioned by the OP, TWRP can't be installed alongside this kernel because the kernel size is too large to accommodate both TWRP and the kernel. The developer explains this in his second post of this thread. To run TWRP, you must fastboot your device and boot to the TWRP image directly.

About LSpeed: the tweaks it offers is snake oil. Unless you're modifying the animation speeds to x0.75 or x1.25 I'd uninstall it. It can interfere with the default settings and actually slow down your device.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
cheers bud for your answer. :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I personally dislike L_Speed ~ It has a habit of overriding other apps that have similar settings that I use. I don't think it's really needed, necessarily. I have no complaints about battery life or SOT.... that said; there's nothing wrong with experimenting ~ it's your device, after all. ;)

Well, Being as the person asking for help isn't using Linux and seems to be a bit of a noob ~ I wouldn't want to confuse him with such information....

IMHO, it is a distribution package maintainers responsibility to address these types of issues as they crop up (and I would know having been a package maintainer for Archlinux for a number of years). This really shouldn't be something that an end user even has to deal with. ~ That said; I'm not sure your information is even correct, I think this sounds like a Fedora problem.... on Archlinux, I don't have to do anything like that, anytime that I've seen that message - I update abd/fastboot and it goes away ~ and reviewing the pkgbuild that provides adb and fastboot - they've done ZERO modifications on Archlinux, it works OOTB....

anyway, I think this goes a bit beyond the scope of the thread. But who knows, I could be wrong and it is an issue on MacOSX (although, i'm doubtful) - We'll see how things go, when he reports back...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kentexcitebot:
That's alright. I just wanted to post the workaround for other members to read as some people (including myself) are running into the same "fastboot is too old" error on Reddit and XDA:

https://www.reddit.com/r/AndroidPreviews/comments/7g6xb5/81_dp_fastboot_too_old/

https://xdaforums.com/pixel-xl/help/bootloop-8-1-upgrade-t3715482

https://xdaforums.com/pixel-2-xl/ho...KA8cQFgg8MAM&usg=AOvVaw0UqnQSimnDaIicIWQJEtbX

But who knows, maybe it IS just Fedora.

Also, kudos for being a Arch package maintainer! I used to run Arch exclusively on my desktop and laptop for years, but I ran out of time to manage my packages and I'm a FOSS pleb anyways ¯\_(ツ)_/¯
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
Yes I did have to edit out those lines, found out after a bit of reading up, thanks for your help, if I'd known about that I could have saved myself a lot of time, anyway all's good now.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Apparently not just Fedora. lol... I guess google has dropped the ball, maybe ;) ...

Ya, I'm far less involved in Archlinux than I used to be, but it's still the only distribution that I would ever use. I can't be bothered with any distro that isn't rolling release && I need a distro that is a combo of binary packages and source packages, so it tends to be my goto....

I'm pragmatic about FOSS. I generally prefer opensource, but some proprietary stuff is good too && Arch tends to work around some of the licensing issues with non-free stuff - which is handy.

good to know. I learn something new everyday! ;) .... Seems odd that google would ship something mildly broken, not that it would be a first. lol
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
just as an aside, things to come:

I have a bit of time tonight. so I'm going to work on some changes for the next build... I've got some changes to binder_rt coming, a number of one-off cherry-picks; stuff that I just didn't have time in December to merge, I'm going to have a stab at improving the locking stuff that I mentioned in this post; https://xdaforums.com/showpost.php?p=75076353&postcount=581 . Some updates to a few drivers (that I'm going to break to upgrade some other kernel stuff), some scheduler code upgrades..... I'm going to ditch zram and have some other bits that I'm working on too.... some of the mentioned stuff is already implemented and running on my device, while others I'm just digging into now.

I'm working off my current/local kernel tree, but on the weekend - I'm hoping to rebase the whole thing, with all of the new changes integrated, lots of cleanups, etc too... Then I should be able to push a more substantial update, that's largely been tested for at least 48hrs.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] teedee29:
that 'fastboot too old' message kept bugging me, I downloaded the tools a couple of times from Google, so I knew they were up to date. After your last instructions it happened again and I started typing a reply to you with that info, but I thought 'surely I can sort this myself' so did a bit of reading. Didn't want to keep bugging you, the answer is usually found if you read enough!! That's what I tell my kids anyway, thanks again for your help, ended up leaving the -w in so I could start with a clean slate. :o
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
It's all good, you definitely weren't bugging me, at all. I'm glad that other people piped in and that you were able to do a bit of research into it yourself too... Yes, the answer is usually found with enough reading! ;) ... every couple of months I completely wipe my device too ~ keeps things fresh and most the settings that require a lot of effort / time, I can backup/restore... Apps take longer to update and install, but that doesn't require me to actually be doing anything, other than waiting.... anyway, glad that you've got it working now!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
If anyone is interested of feeling the need to flash a new kernel. While, I haven't finished with my new kernel tree, nor published it on github, I am testing code and therefore pushed a build. ( and just lumped in a 1000 patches into a couple of commits, with a shell script and committed them to github )

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

the changes are numerous; FS, VM, Block, Memory Management, Binder, etc. Because I touched MM, I had to bump up zram too (also I've reduced swappiness... and it's rarely used anyway.) ~ so I matched zram to the msm8998 version (I'm lazy, so it took all of 5seconds / drop-in replacement. lol). This build is also not using Linaro GCC 7.2.x ~ It's using GCC 8.

I still have a lot of code to merge in, but I'm running this build for now, While I continue to work on code, integrate changes and test (with my current tree)... Other stuff I'm working on; Schedutil, scheduler and energy aware changes, I have binder_rt changes that haven't landed yet (but are running on my device), pulling KSLR changes that landed in AOSP today and as soon I i finish unbreaking the last few drivers, I should be able to remove a rather large bottleneck in I/O performance (present in all older kernels).

I also have a ton of Memory Management commits to go through (and some supporting/related code), as I have plans of getting some code to run with concurrency, that currently does not (on any android shipping device ...and only works on semi-new mainline kernels). I took a look at other custom/android kernels, thought maybe I could speed the process along, but even the ones that have some newer MM commits; are missing a crap ton of commits, brutally so ~ so not really helpful / better off just doing it myself...

So I'm guessing, It might be a few more days before I get a fresh kernel tree on github + a new stable build. But hey, I can still post a test build or three, in between ~ for those who like tinkering.... I expect there may be the odd rough edge on this posted build, although it's been running fine for me, thus far. ~ lots of new code, switching compilers, etc => so if the stable one is working fine; Don't feel the need to switch or anything like that, I just know some people like to, so I'll post a couple until I get everything merged in / a new stable build.