yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kentexcitebot:
I can also confirm. Tried updating to your test build after your stable, but same bootloop where the "G" logo spins, screen blacks out, and reboots. I had this problem with your previous kernel releases, the only way I was able to boot your kernel is to erase everything. And yes, I'm using Magisk 15.2 without tampering with the system image. I tried the suggestion made by the other guy -- flash stock kernel, boot into system, reboot to TWRP, flash magisk, reboot, boot back into TWRP, and flash kernel -- but I never made it past boot with stock kernel either.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
very odd.... given that I know several people who migrated from the stable build to test builds... many without issue, aside from the odd hangup, or issue with a mod..

I think for now, I'm not going to post any test builds, until I finish up with my changes.... then I'll go from the stable build to my latest build and see if I can reproduce what u are describing...

***so anyone on the stable build, just stick with that***
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
Just wanted to chime in that I went from the stable build to your test 1, 2, & 3. I upgraded by flashing Magisk 15.2 then your kernel using the boot twrp.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] natri23:
I'm on latest 8.1.0 with Jan patch elementalX 3.01 with Magisk 15.2, Tried to flash stock Jan boot.img >magisk15.2> your test2 kernel and failed (bootloop) and then I cant flash elementalX or stock boot.img anymore. Something has messed up the system. I had to reinstall factory image. System failure could be cause I disabled fsync but even b4 doing that I still get bootloop with the switch to Magisk b4 kernel stable. Either the switch or magisk 15.2 was the cause
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kentexcitebot:
By any chance, is your system booting into stock recovery with the message "command not found"? If so, I also have this screen. I was wondering why flashing stock boot images didn't work!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] natri23:
Yes, after flashed test 2 and failed (constant reboot). I tried stable exNoShadez > still reboot > flashed stock boot.img > bootloop > wipe Dalvik cache > still bootloop > factory reset > "command not found" > reinstalled factory image
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] almightysiman:
I have tried test1 2 3，all boot fine.Thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nevermindthelabel:
I have also gone from the stable build thru all the test kernels with no issues. Wanted to make sure (for those with bootloop issues) if twrp is used it's being fastboot booted instead of fastboot flashed. That messed me up a while back, old habits...took me a few minutes to figure that out. But since then, rock solid!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
Just flashed the test 3 over the test 1 (which was flashed over January Stable), without touching anything else and no bootloop, root still here with Magisk.

Only get stuck at Google logo screen ( [MENTION=7810360]nine7nine[/MENTION] said it could happen at first boot following flash), but all is good after forcing reboot by holding the power button.

Thought at first the same thing as [MENTION=5996385]Nevermindthelabel[/MENTION] , but someones were using this kernel before the test builds, so not sure.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
hmmmm....

why did you flash the stock Jan boot.img?

what pixel firmware do u you use?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] natri23:
OPM1.171019.012

I reflash the boot.img so that it would be clean no?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
only if twrp was installed would you flash a stock boot.img to remove it.... that step is under the heading 'twrp removal' in the OP.... you shouldn't need to be flashing the stock boot.img for any other reason (well, other than on monthly firmware updates)...

I'd really love know why there is a couple of you who this happens too, while everyone else seems to move from builds without issue... something fishy is going on here, I'm just not sure of what it is yet... ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] natri23:
Could be caused I jump from different kernels, specifically elementalX. But yeah, that was still fine until the switch and Magisk 15.2
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
ya, I'm not sure if it's possible that the couple of people who are having issues are doing that or something else that is screwing up their system.... it's really frustrating though, as I don't have that problem and most other people don't either...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] FBI Surveillance Van #23R:
Getting my Pixel XL tomorrow. I saw that ElementalX was available, but this kernel also intrigued me and seeing it used to be based on ElementalX I believe there might exist some common philosophies between the two. So it will be the first kernel on my phone. :) I also read the OP stating I cannot have TWRP as well, and I'm totally fine by it.

Can I increase the sound using a kernel manager(EXKM or KA) and also edit the color profile?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nevermindthelabel:
I have used both and highly recommend this one. Nothing against elementalx, but this follows EAS more and that intrigued me. As for the color and sound, they are present in EXKM but I don't use them so I can't say for sure
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
Yep you can.

Flashed the latest test version and booted up with no problems same like the previous versions. Works great so far, thanks a lot for your work man!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] xonelith:
Is it "command not found' or 'No Command'.

If it is the latter, that's the stock recovery (well sort of). Hit Power + vol up and you will get into the stock recovery menu.

Just to add, I'm one of the ones having zero issues with the new builds. I've just been re-flashing the new kernels; nothing special. In the old days when we needed to flash Magisk after the kernel, I had issues, but they are all gone:)

I'm using Magisk 15.2 and only the ViperAndroid module installed.

Thanks for the great kernel!:good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kentexcitebot:
Yes, as I said earlier the message is from stock recovery. I mentioned this because whenever I tried booting to the system, it would go straight to stock recovery with the error message. That includes going into TWRP and tapping the "System" button, fastboot reboot, etc. Keep in mind: TWRP isn't installed on my phone; I always hotboot into it.

That being said, I started over from scratch because I need a bootable phone. I am running the latest test build without problems for now, but the issue always starts when I either update the kernel -- I enter my device into fastboot, flash stock January boot image on both boot slots, hotboot into TWRP, flash Magisk (also tested without flashing Magisk), then flash the kernel -- or flash a different kernel. I always flash the stock boot images first before I update or switch kernels so I can avoid overlapping kernel configurations, or when I want to test a different kernel. However, I did not test flashing the test build on top of the stable build (which I'll try next update); I also did not test flashing the vendor image. Unfortunately, I'm stumped of why this problem even happens as I was able to update NSFW and EX Kernel without a hitch.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
[MENTION=7810360]nine7nine[/MENTION] What are the best tweaks and governors to use in the ex kernel manager for your kernel (i'm currently on the stable January build)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
When I update I just use the zip within the image but without the"w" and boots up fine.

Flash the kernel and forget it. Kernel is already optimized out of the box, if you scroll a few pages back the developer mentions it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
you don't need to flash the stock boot.img on every update of the kernel, your logic for doing so; makes no sense - if I change my init rc / kernel configs - it will replace the previous one on update.... Updating my kernel is as simple as flashing the new build - THAT'S IT! ;) ... none of those other steps are needed, at all.... you are making things way too complicated.... I'm also guessing that few people are doing what you are doing - which makes me wonder, if that's part of your problem...? (but I may try doing what you're doing, just to see if I can bump into the issue).

could you PM me your exact steps with full commands?

One thing that I'm wondering now is something to do with Magisk, that may be causing the issue (indirectly). It's a bit long to explain, but I'm going to ask the dev of Magisk about a couple of details...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Donric13:
In my thoughts something in magisk 15.2 has the potential to mess something up in the kernel updating process. Yesterday i started from the scratch. Flashed actual stock firmware again (leaving -w on, so all data was erased). After inital boot and installing apps only through Google playstore (Google drive backup while setting up new rom) i flashed magisk (only magisk, no modules). Rebootet to device. Then i went back to twrp (through fastboot) and flashed your testkernel (3) over stock boot. Rebooted the device and checked magisk. Had the "2x" problem (apps in magisk manager showed up 2 or even 3 times). Was really surprised. But in the last days this happend quite often to me after flashing an updated kernel over the old kernel leaving magisk on the device. I don't know yet, if this "x2" thing leads to problems - but i think it's not really normal. But i don't think it's kernel related - it's more on magisk side. BTW now i uninstalled magisk. Reinstalled magisk and reflashed test3 (all over already flashed test3-kernel). Now magisk is showing normally all apps only one time.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dr_drache:
this is meaningless (as I don't have logs) but the sleep/off situation still there for me -

you said you wanted a full bug report, other than /sys/fs/pstore ; what else would help? (it happens every couple of hours, so next time I want to be able to provide the most proper data)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Well, your last /sys/fs/pstore wasn't helpful... it actually looked like it was from TWRP not my kernel. (it showed another kernel version and the pstore files were different than those produced by my kernel).

That said, I think i _may_ have found where the issue is, even if I can't reproduce your issue at all. I would suggest that you run the stable build for now.... Also, your the first person that I am aware of who's having this happen every couple of hours. interesting, but very odd....

You could provide me with a full bug report, which you can collect under;

settings->developer settings->Take Bug Report

it takes a few minutes to collect and it will notify you when it's finished... You'll probably have to email it to yourself or save it to disk ~ then PM me ~ I'll give you one of my email addresses and you can send it to me (I don't recommend posting it in the forum, just in case there is any sensitive data collected)... You can try including pstore again too (maybe this time it will be from my kernel)

Or you can upload it to https://tmpfiles.org/ (make sure you set it to 120min MAX ~ in case, I can't download it right away) and send me a link via PM....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SynisterWolf:
asking for ETA's is rude. Wait patiently for the developer to update the thread.

thanks

Wolf
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] natri23:
Using the test 3 and Magisk 15.2, I also experienced random black out every hour. The phone was not off since it still responded to DT2W (vibrate) but the screen doesn't turn on. Have to hot reboot
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
natri23, your going to have to collect info / logs, telling me this is happening is pretty useless without providing more information.

#1 - I can't reproduce your issue.

#2 - you can, so if you want me to look into it - you need to do a couple of things;

=> hook your phone up to a pc, when this is happening and run logcat - try to use DT2W and watch the output of logcat (it will likely tell you/me exactly what the problem is)... try hitting the power button and fingerprint scanner to unlock/turn on the display... *You can cut and paste the output into a text file and send/pm it to me.

=> I'd also like a full bug report (you can create one in develpoer settings.). It might show some other details/info that could be useful....

IMPORTANT GENERAL NOTE:

Those of you who do not know how to debug or provide logging, may be notice/noobs, etc ~ really need to stop using test builds, stop spamming the thread AND just stick with the *STABLE BUILD*.... it's called stable for a reason... right? ;)

Seriously, ask yourself; why you would want to use a test build (a work in progress), if you can't collect debugging info yourself? Honestly, it doesn't make much sense, right?

~ it's not like the test builds have a bunch of new user facing features, stick with what won't give you headaches / just works ~ and wait for the next stable build.... That's my advice / rant....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] natri23:
I dont have a PC with me when that happened but I will try to get the logcat next time

P.S: Nevermind. back to stable build
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Queentus:
remember me? the one with the same bootloop problem with all your previous builds.

however, the weird thing is I got no bootloop with the latest test3 build eventually...

Finally got a taste of sweet exNoShadez :cool:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Cool. ya, stable build is probably best to stick with until I wrap up my changes and stabilize things...

I've actually backtracked a bit anyway, meaning; I undid a bunch of changes and upgraded some core subsystems (then reapplied some commits), as there were some fairly heavy changes post-3.18 kernels.... There's been some stuff that I've wanted to merge but without some of the reworked / updated components, functions, syscalls, etc ~ merging isn't fun (at all) and also the cause of some issues... so I would rather not have to mess around with compatibility issues (or flakiness), so it's easier in the long haul to just grab up some related core kernel changes...

So I've sort of being undoing and redoing parts commits, to make sure that I've grabbed up all of the changes (in full).

Cool. I would've stuck with the stable build, if I were you. Some people definitely had issues with the test builds (although, I didn't)... anyway, I'm reworking things fort he next build. Just a slow go, as there are many changes, so it's not an overnight sort of process....

no idea (still) about your guys bootloop issues ~ in the last few days, I've swapped back to stock boot.img (once or twice) and swapped back in my own builds, both stable and dev builds ~ the only time I've hit a bootloop ~ was during a botched commit.... other than that no probz.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bryanx86:
If you flash the stock boot image, then fastboot twrp, and flash magisk, then your kernel, and reboot; you will boot loop, I do at least. I always fastboot stock boot image, then reboot fully unrooted(doesn't matter at this point), and then go back to bootloader, fastboot boot twrp, then flash magisk and your kernel. Maybe that's why people are having issues, just a thought.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Queentus:
I'll give it a try later to see if this method applies to me either. Thanks!:highfive:

-------------

edit: IT WORKS!!! dev should really update this method in op. Finally I can get to try the stable version of this kernel!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Shaka401:
I let it boot unrooted as well. No boot loops so far even on Test 3.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TotoBerto02:
Kernel settings and +

Hi, whats the best settings of this kernel to get good battery without affecting the performance of the phone or just a little? And also, in CrDroid, twrp and the kernel (EXNS) work perfectly the two together without causing any brick.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
Set and forget. Best settings according to OP.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TotoBerto02:
You mean, flash the kernel and dont touch nothing?

You mean, flash the kernel and dont touch nothing?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
Correct.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] MArtyChubbs:
- USB Fast Charge not working, only get 500mA on USB 3.0 port. Anyone else having this issue?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I had to enable with ex kernel manager
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
ya, I've heard that works OK. thx for pointing that out for others....

just stick with schedutil, which is the energy aware scheduler. it works very well for battery life and the vast majority of workloads... if you have an app that is very demanding, or is sensitive to CPU frequency scaling (this would mainly be proaudio apps on android), then you could setup performance mode on exkm to use the performance scheduler and switch to it on those types of apps...

aside from that. best way to improve battery life. disable location, Bluetooth, NFC, etc when not in use. you could also disable WiFi when sleeping. turn on data saver, limit/disallow some background apps, limit which apps sync in the background, etc... screen brightness plays a big factor, adaptive brightness also can drain battery a bit... lastly, dark themes (as in black, will save battery, being as the screen is always the biggest source of drain).

ie: all settings that can be tuned in android, doesn't require tweaking the kernel...

on kernel tweaking. my general approach / attitude is a kernel is something that u flash and sort of forget about. after all, it isn't really software that a user is directly interacting with. it's the layer between h/w and userspace.... so I try to just pull in features / extras that are useful/beneficial or give users extra security/protections and then set some defaults that are good...

I generally don't buy into the concept of having every scheduler, networking algorithm, misfeatures (like disabling wakelocks) or grabbing random code, partial patchsets / cherry-picks that end up being nops(no operations, as in dead code that doesn't do anything, as I see in some other kernels. ROFL)...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
[MENTION=371528]Everybody[/MENTION]... I am working on a big update, but I may wait until the Feb update to push it... I haven't gone Mia or anything. I've just been a bit busy with life, work and another project... but I do have stuff that i'm working on for the kernel... my current running kernel has a lot of kernel plumbing type updates (block, VM, mm, tracing, ext4, scheduler, drivers, etc, etc)... but i'm still working on a few bits, so I haven't wanted to push an update quite yet.

edit: i'm also waiting to see if google merges in the KPTI patchset (the spectre and meltown side channel exploits that have been all over the news) that landed in mainline linux, some lts kernels and also AOSP - as it will require me reworking a few patches.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TotoBerto02:
Ty for answer my question

Thanks for answer my question!!!!!!! It is helpfull
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
Thank you for your detailed explanation on how to approach battery saving strategy. I do have one question, what is your setup for your mobile browser, I know you don't use chrome. So I am curious as to what setup you have running. Thank you
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no probz.

I use Firefox-Nightly. Some of it is ideological alignment with Mozilla, but also because I like having access to a browser with plugin support (rather than no plugins or just a plugin or two built-in).... I also use Nightly, because I tend to be bleeding-edge (I run lots of beta versions of apps too. bug report, dogfooding, etc)...

in Firefox, addon / plugins;

- noscript

- ublock origin

- smart https

- cookie auto detete

- privacy badger

- dark mode

I also tweak some stuff in about:config to speed up the browser. there used to be plugins for this, but I think since Firefox switched to web extensions, no one has written a new one yet.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no problem. I don't mind at all.

to add additional background;

none of the other cpu schedulers are EAS compatible (at all), except 'sched'... previous to EAS - no schedulers had any notion of power / energy consumption, nor any heuristics or mechanisms in place to help them factor energy into scheduling decisions...

sched (which ships on the pixel) is a precursor to schedutil ... When linaro, google, upstream kernel devs were working on integrating EAS into the linux kernel they hacked on sched (google pulled in a number of eas patches for the pixel. these weren't present on 3.18 mainline kernel).... by creating sched, this allowed kernel devs to put things into the scheduler, where the kernel didn't have proper integration. ie: hacks and working around limitations...

later with schedutil, all of the hacks in sched were no longer needed, as those bits ended up elsewhere... sched has been removed from later kernels / no longer exists.... In the case of the pixel 2 - google backported schedutil to linux 4.4 from linux 4.9... our backport is similar, except there are a couple of stubbed functions which our rather ancient kernel doesn't support and would have made the backport / integration far more invasive. on 3.18.. although, I have been toying with doing a broader backport of the cpufreq code / schedulers.

the kernel definitely is a big factor in energy consumption && plays a non-trivial role (which is why EAS had been worked on for years, why there is interest and why it is still being worked on upstream), but there are obviously different approaches in how/where battery savings can happen. that said, as I mentioned before; the screen will still always drain the most battery on a mobile device (probably followed by location services)... that's by design / unavoidable.

I went the route of EAS because that is the direction of upstream / mainline linux and it's always worked well for me. on my phone, i generally don't want to be needing some convoluted setup and additional tweaks for different scenarios that I have to manage... so it's better to just setup an init script (which I do), let the kernel do it's thing and move on.

As an aside; Desktop linux for me is probably a more involved and complicated setup... but even on desktop linux - everything is automated on boot using systemd on my system... and at this point - I never need to touch a thing. so I have the same attitude; once the system is running, there shouldn't be a need to tweak anything kernel related. it should just work with any workload or type of application.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TotoBerto02:
Wow whats an answer lol

Your question it is so helpfull too. Now I understand things I did not understand very well. So to understand well the best governor to save battery would be schedutil correct? Thanks for your answer, it's very helpful
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yup. schedutil. should be set on boot up anyway...

and you're welcome. other people find those answers helpful too.