yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] eddi0:
Very new to custom roms/kernels for the Pixels so....

What is EAS?

Any point/benefit to using EXKernel vs stock kernel then? My battery life over night was about a 8% drop which is quite high compared to my Nexus 5X hence why I am trying to EX.

Thanks for your response(s).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Energy aware scheduling. I like ex for the wake gestures and a couple other things I don't get from stock. I can't live without them!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
As already answered. EAS (Energy Aware Scheduling), but to give a bit more context. Traditional Linux cpufreq drivers / scheduling code ~ don't consider power management / power saving (at all, really). So EAS is work being done by Linaro group, upstream linux, google, etc ... to make linux scheduling energy aware, so that it can attain much better energy savings...

The Pixel's kernel has some initial support for EAS and/with it's cpu scheduler 'sched'.... upstream development is no longer focused on our (3.18) kernel. So you will notice some custom kernels advertising/using newer EAS code and a scheduler called 'schedutil' ~ which is newer EAS code ported to our device...

I think EX kernel is better than stock for battery life, but mileage always varies with this kind of thing....

8% seems rather high - I think that you must have an app that is causing the drain ~ best to look over your apps in battery settings to see what the cause is - it could be that you just need to block one from running in the background....
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
Update!!

Download:

ElementalX-2.03.zip

Changes:

-November security update
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jiajialing:
hi guy

I'm on stock 8.0 with magisk 14.4 rooted and twrp3.111

I followed instruction,

1. fastboot flash boot.img

2. fastboot boot twrp.img

3. install 2.03 kernel (or 2.02 kernel) zip

4. install magisk 14.4 zip

first boot is good, booted in to system, however phone reboot it self after around a minute, and never back to system, instead to factory recovery, says android os is corrputed

anyone had this issue?

TKS
[Google Pixel ROMs, Kernels, Recoveries, & Other De] phaino00:
Did you reboot system between your step 1 and step 2?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] karthik432:
working with Android 8.1 build?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Droid1019:
I've had the same problem ever since 8.0 Had to give up the kernel unfortunately.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] clothednblack:
From what I've seen and experienced myself, this mostly has to do with the order of flashing everything. When done out of order, you lose recovery. Good thing it only takes about 5 minutes of flashing in different order to find the right combination!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Droid1019:
That may be but I tried all the combinations with the same results as the person I quoted. And I've had no problems flashing a different kernel. I think I'm going back to 7.2.1 anyway because I can't use dbl tap to wake and swipe to wake without the phone waking up in my pocket without flar's other app which doesn't work on 8.0.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] roirraW "edor" ehT:
PSA: I recommend avoiding ElementalX 2.03 on 8.1 Final until it's updated. At first, it seems to be working, but boot loops galore when you reboot. No boot loops without it. Also, just because it's related, SuperSU 2.82 SR5 doesn't work for me (repeated tries on fresh installs) on 8.1 Final. Magisk 14.5 build 1456 seems to, though (thanks [MENTION=3097488]phaino00[/MENTION]).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
Update!!

Update for Android 8.1.0

Download:

ElementalX-3.00.zip

Changes:

-8.1.0 update

-December security patch
[Google Pixel ROMs, Kernels, Recoveries, & Other De] iainaaldrich:
What's your recommendation for installing the 8.1 kernel? I can't seem to get into twrp, my password fails when I try to fastboot boot twrp
[Google Pixel ROMs, Kernels, Recoveries, & Other De] phaino00:
I installed it via TWRP, using usb-otg method.

In TWRP, when prompted to enter password, hit cancel and then swipe 'allow modifications...' at bottom of next screen. From there, mount the usb-otg partition and connect the USB drive to the phone (using a usb-type-c adapter, e.g., one was included with purchase of phone). Install zip and reboot system.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
You can also push it to /cache/

adb push [PATH TO EX KERNEL ZIP] /cache/

I would advise not to swipe to allow modifications, then OTA updates won't work. Lately I keep stock recovery and just fastboot boot TWRP recovery, leaving the stock recovery so I can take OTAs for quick updating.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nil253259:
Do I need to flash stock boot.img before accepting OTAs?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] roirraW "edor" ehT:
Thanks!!! That was fast. Fresh donation for you in a few hours!

I used FlashFire to update from the November 8.0 release to the final 8.1. Don't let it EverRoot. I enabled the option to flash the bootloader, and I had FlashFire update all of the dangerous/protected partitions, while allowing FlashFire to split the flashing up into two sections of safe and non-safe. You can chain flash everything (firmware, ElementalX v3.00 and Magisk v14.5 build 1456 at once, but once you boot into Android 8.1 Final, FlashFire doesn't appear to work.

As always, you need to have the stock boot.img (no TWRP) before flashing ElementalX.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
No, just recovery
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
That dialog is caused by Magisk. It's harmless and everything still works.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] roirraW "edor" ehT:
Apologies! Disregard.

Thanks again! Confirmation number: 65590021S3747643P
[Google Pixel ROMs, Kernels, Recoveries, & Other De] yl1504:
Anyone else getting a new message during start of the device after installing the kernel saying "there is some issue with your device ..." ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] inscythe:
That's literally the post above yours... It's harmless, according to flar2
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
8.1 with this kernel seems super smooth and great battery!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jank4AU:
I can never get this kernel to work for me. I'm totally stock with a fresh install of 8.1, no TWRP, stock recovery. When I fastboot TWRP and flash the kernel from OTG, I just get continuous bootloops. Happens every time. What in blazes am I doing wrong?

Is it that I'm using TWRP 3.1.1.1?

Edit: Got it installed, but only after I swiped yes to "Allow Modifications". Previously, when I bypassed that by canceling, it wouldn't work.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] roirraW "edor" ehT:
Hmmmm. I always do mine read only and it worked. Weird.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
This kernel does not touch system. It only replaces the boot.img.

The only possibility is selecting overclock frequencies that your device can't handle. Other than that, I just can't imagine any scenario where it doesn't work on a stock install. It simply replaces the stock kernel with a custom kernel that is almost exactly the same except for added features.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jank4AU:
[MENTION=4684315]flar2[/MENTION] - that had to be it. Now that you mention it, I selected over clock each time but the last install. However, on that last install, I swiped to deny keep read only. That's what stuck out to me as the difference maker since I didn't know I couldn't select OC. Thanks for helping me solve that riddle! Sorry for the confusion on my end.

Edit: after re-reading your post it sounds like you imply that some of our phones can OC. I guess otherwise it wouldn't be an option in aroma? If that's the case, does that mean I'm one of the lucky ones who got a processor from a crappy bin that can't handle higher clock speed?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] discolemonade:
Possibly a dumb question, but can the schedutil governor profile be used with elementalx?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
There are no dumb questions; if something is learned in the process!...

Schedutil doesn't exist in Elementalx or Stock Marlin's kernel .... It's an energy-aware cpufreq driver / cpu governor that is used in new kernels (linux-4.9) that has replaced the "Sched" cpufreq driver that you've probably noticed on your device by default (Google uses Sched for energy aware scheduling on the Pixel)....

ElementalX also has it's own cpufreq driver - named accordingly ;) ... So you are using one cpufreq driver at a time and they are mutually exclusive.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] discolemonade:
Okay this helps a lot. I didn't understand that governor profiles are built into kernels, I thought they were something outside of the kernel that controlled how the kernel functions. This makes a lot more sense, thanks!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
The profiles aren't built into the kernel they are in EXKM, but the cpufreq drivers / governors are built into the kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] fink.nottle:
I got that message without flashing magisk; just the kernel. I have used magisk in the past, so it may have left some stuff on /data, but otherwise, the december image was flashed with flash-all without the -w switch, followed by the kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I'm not [MENTION=4684315]flar2[/MENTION] - but I know someone else who verified the same thing with my kernel... I had thought [MENTION=4684315]flar2[/MENTION] was correct, but it does seem to be custom kernels tripping the message....

* and magisk doesn't trip the message on the stock kernel; so how could it be responsible?. (something I have tested).

I've had no luck figueing this one out, myself... hmmm...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] fink.nottle:
Does it trigger if you build the stock kernel and flash it ? If it still triggers, it could be the build process itself. If it's some kind of integrity check, it'll fail even with a self-built stock kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
Someone else told me it was magisk. Apparently it is something else. I'm not too concerned about it. The useless warning seems like a dumb idea, since custom kernels work just fine and don't cause any security issue.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I'm not overly concerned either, but still would be good to know why it happens... in the past (because this isn't something new, really) it's been caused by a check / comparison of the prop in the system image and vendor image, if they didn't match; it threw that warning....

but I think this time around there is some other check happening throwing the warning.... I suspect it's something in the vendor partition, but who knows...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
EX only changes the boot.img.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
i know. which probably means that there is a new check that checks the boot.IMG too, not just system + vendor...

that's kind of what I was hinting at... I was just clarifying that the message itself isn't new in android, but it occurring now does seem to be and it does seem to have to do with the boot.IMG, not system/vender or magisk, etc...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
Hey guys! Does anyone know if this kernel works with AM3D Zirene mod?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sh0X31:
nine 7nine:

Source
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Why quote me on that? >> it doesn't fix the issue, as noted... Plus, I'm pretty sure that Flar2 is a very smart guy, with a ton of experience with android - i wouldn't be surprised if he was already aware of that workaround.... (plus, he may have seen that, having already commented in my thread and likely that means he's subscribed).

[MENTION=4684315]flar2[/MENTION] might be interested in the patch that I mention in that post though;

https://github.com/nine7nine/Marlin_exns-eas/commit/11c3a01549badb735e12c06007cd8543e90928a0

it applies over the previous patch to bypass safetynet. It's nice because it adds some flexibility in adding new flags to remove, if/when necessary.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] !n0x:
well, here's yet another post to confirm that the manufacturer's message pops up, even with just kernel.

1. clean flash of factory image (-w), set PIN

2. fastboot boot twrp3.2-1.0

3. adb sideload elementalX, no magisk

4. did some underclocks (as I usually do).

It's a small nuisance but not dealbreaking as it's not everyday I reboot my phone. Hoping this would be figured out soon.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pWEN:
Also confirming that flashing ElementalX on a stock boot.img causes the "internal problem" error to occur. Patching a stock boot.img through the Magisk Manager app (make sure the update channel is on beta) removes the error. I'd like to patch a boot image that has been modified by ElementalX, but I can't find a way to copy it or make a backup. I know I can make a backup with the ElementalX manager app, but the option isn't there if I'm rooted, and I can't root it without patching it first through Magisk.... I tried making a backup through TWRP, but it gives me a *.emmc.win file instead of an *.img file. I tried looking through this thread and Googling for other ways to make a backup, but it seems those methods no longer work on Oreo. Can anyone point me to a good guide for doing this?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I think you may be a bit confused here. the stock boot.img doesn't give the error at all, nor does magisk fix it ... there's nothing to fix... it doesn't contain the modified/non stock kernel...

i also don't understand how the kernel backup option in exkm isn't there... I'm rooted (using magisk zip), I use the kernel backup feature all of the time...

something seems fishy with what you're saying... doesn't make much sense.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pWEN:
I know the stock boot.img does not give the error. Obviously a stock image wouldn't contain anything modified, or it wouldn't be stock. If I flash ElementalX OR Magisk over a stock boot.img, then I get the error. I don't know what exactly happens when flashing that causes the error to get triggered, but that's what happens.

If I follow the boot.img patching process on the official Magisk thread's installation instructions with a stock boot.img, I can get Magisk installed, passing SafetyNet, and without the error. If I flash ElementalX after getting Magisk to work in that way, then the error comes back. According to the official installation instructions and what others have said in the beta Magisk thread, I should be able to do that install process on a custom kernel instead.

My thinking is that if I can flash ElementalX over a stock boot.img, then back up the modified boot to a new image file, I can use Magisk to patch that file. My current issue is that I have ElementalX flashed over stock right now, but I can't make a backup of the new boot image without root using the ElementalX manager app, and I can't properly install Magisk without having an image to patch.

I've attached screenshots showing that I have ElementalX installed and no option to make a backup of the kernel.

EDIT: I looked back at my previous post and realized I meant to say the option to back up isn't there when I'm NOT rooted. Sorry for the confusion there.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
i wasn't getting the error with magisk + stock kernel. only with custom kernels. unless something has changed with magisk 14.6 (?)... but I tested this (and other people I know.).

AFAIK, this isn't going to patch the boot.img any different than using the magisk zip. same end result.

why would it be there? it requires root to use, just like 99% of exkm... catch 22, what u want to do, won't work... nor will it fix the error.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pWEN:
It was happening for me, but when flashing Magisk through TWRP. I believe because it wasn't preserving verity, and maybe also because I was on an older version before. The image patching through the app is a new process to me, so I didn't know to try it initially until 14.6 came out.

I know the question was rhetorical, but I don't know enough about developing a custom kernel to know why it wouldn't or shouldn't. I mentioned its absence because it seemed like what I needed to try and accomplish my goal.

Okay, I thought as much, but was hoping for someone more knowledgeable like yourself to weigh in. Thank you for clarifying and confirming that for me.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] roirraW "edor" ehT:
As usual, ElementalX v3.00 works perfect with the January Pixel update. Not really news at this point, but someone might ask as happens from time to time. This time I flashed Magisk v14.2 after ElementalX so that I can try FlashFire for the February update (or what have you), since FlashFire 0.73 reportedly works with Magisk v14.2 and that's how I did all my updates before - completely without a PC and without an installed TWRP.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] queerquirks:
I'm currently magisk rooted with Elementalx kernel.

Do you mean I can take the Jan OTA, root back again with magisk apk and flash Elx through FlashFire?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] roirraW "edor" ehT:
It depends on what version of Android you're coming from, what root method you're using, possibly what version of the root method you're using.

Short answer since I haven't tested it myself on the January 8.1 with Magisk 14.2 yet: Maybe.

FlashFire definitely doesn't work with Magisk v14.5 and I don't think anything above 14.2, so it depends on what version you have plus I haven't tested it yet even with 14.2 especially in combination with 8.1 (coming from December and flashing January). I don't want to assume which monthly update you're on, too.

I was always on SuperSU when using FlashFire previously, v2.82 SR5 when on the November 8.0, but as you probably know, v2.82 SR5 doesn't work with 8.1.

When I was on November (or previous) 8.0 with SuperSU, I was able to flash the full December 8.1 firmware (I didn't test with OTAs) with FlashFire plus ElementalX all in one go. Once I verified everything was working, I then used TWRP to flash SuperSU v2.82 SR5 at the same time but the phone just bootloops after rebooting after flashing if I remember correctly. I could've had it try to flash SuperSU at the same time as all the rest in FlashFire but I had no idea if SuperSU would have to be updated, and it does.

I then totally clean flashed from a PC, used Magisk 14.5 and tested FlashFire but FlashFire doesn't work with 14.5. I'm told it works with 14.2 and that's the end of my knowledge since I haven't tested FlashFire under 14.2 yet, but when I have something new to flash again, I will do so.

I always recommend having everything backed up before any flash. I perform a full Titanium Backup on user apps and data, I sync it to Google Drive and I also back up the contents of my Download folder to Drive as well.

Since on second thought, I have everything backed up already due to my flashing January 8.1 yesterday, I'll test flashing. Update: I flashed using the full January 8.1 firmware, but I only select the boot.img for this test since I'm already upgraded, I turned off EverRoot which includes an older SuperSU, and had it flash ElementalX v3.00 and Magisk 14.2 in the same go, and confirmed everything booted okay.

Your mileage may vary but you should be able to flash the entire firmware. It's up to you if you want to try the OTA. In FlashFire, go into its settings and enable flashing the bootloader and dangerous partitions. When you tell it to flash the firmware, I choose every single partition when upgrading the entire Android version/security update. FlashFire will at some point offer to split the flashing into first the safe stuff and then the dangerous stuff - I normally let it do that. Then disable EverRoot that it automatically adds, add ElementalX zip and then the Magisk 14.2 zip. If you're not already on SuperSU or on Magisk 14.2 or any other older Magisk that FlashFire works with, I doubt if you'll get anywhere.

Good luck!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
Update!!

Download:

ElementalX-3.01.zip

Changes:

-January security update

-Wireguard support

-TTL iptables support
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kazemitsui:
I am trying to adb sideload the Jan OTA in TWRP recovery, but it keeps failing, and I can't solve it... or did 8.1 disable OTA sideloading in TWRP?

Dec Security Update

Magisk 15.2

ElementalX Dec kernel

TWRP 3.2.1

Anyone have any insight?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Why not flash the stock boot.img and sideload the ota with stock recovery?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kazemitsui:
Because I don't know how to go back to stock recovery...

Do you have a step by step I can follow Haha?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
It's very complicated, but I guess I'll write it out for you:

Step 1: fastboot flash stock boot.img

Done.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kazemitsui:
Thanks and for confirmation that comes from the factory image right?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Yes
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kazemitsui:
Hi there im in bootloader

and typed 'fastboot flash stock boot.img'

FAILED (remote: partition [stock] doesn't exist)

any ideas?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
The correct command is fastboot flash boot boot.img

You might want to read up on what you're doing before messing about with an unlocked bootloader, but good luck!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kazemitsui:
Its been a while and youre probably right, but thanks its sideloading now!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
My single score geekbench score is 200 points lower with this kernel compared to stock.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jesse402:
Are you using ElementalX 3.01 with January Pixel Dust?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Completely stock w/ magisk and a couple modules. I tested the stock kernel with geekbench, flashed ElementalX, and tested that. Both tests were the same and I repeated them multiple times.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
When I use this kernel my used ram averages around 2.3 GB. With the stock kernel it's around 1.8 GB. Anyone else have this issue?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Unused ram is wasted ram. What's your issue?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
After a couple days of use I only have 500 MB free and the phone runs really slowly.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
Not related to the kernel at all
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
Okay I'll stick to the stock kernel
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
Your choice, but there is zero difference in the way memory is handled between this kernel and the stock kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
That's odd. Probably related to an Xposed module not playing well with the kernel.