yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
2150 MHz
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Droid1019:
Does the Wake Gestures app work with Oreo? It won't let me start the service.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] defconoi:
Battery life is terrible on stock and with this kernel, I believe it has to do with the new sched CPU scheduler keeping all cores as idle above 1.2ghz. [MENTION=4684315]flar2[/MENTION] can you add undervolting and further optimize deep sleep and idle drain with touchboost? I may have to start developing again, I'm the developer of the unleashed kernel series for the Nexus 4, I backported a ton of battery savings and cpu scheduling tweaks to those kernels. I'm not quite sure what Google did to ruin the pixels battery life in Oreo but once I find the time I'll debug and write something up.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
I'm travelling so haven't paid much attention to changes in Oreo. I suspect the changes to CPU behavior are on the ROM side, perhaps in perfd. Might be worth trying other governors.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] defconoi:
Good point with perfd, we may need to take a look at that.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dkirbyechs:
Sept Oreo, 2.01 Update

Having trouble getting this one to take. I've updated a few times, still says 2.0. I have not tried flashing boot.img before the kernel update, though. Where could I find this?

UPDATE: Disregard. Used FlashFire to install the update, automatically restored a boot.img backup beforehand. Looks good to go.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nick80835:
Undervolting does almost nothing on these chips by the way, just making sure you know. :p
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nil253259:
Just flashed EX.. been using stock since Oreo came..EX is wayy smoother, but I noticed that battery is terrible..with only 1 hour of SOT, remaining battery is already 75%. I saw that the both the cores are using a lot of high frequencies, for the bigger core duration with highest freq is even higher than that of lowest freq

I typically get 5 hours SOT with stock and i already made sure that there is no rogue app with odd wakelocks. In fact everything is same except I changed the Kernel
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
I change absolutely nothing about the CPU behavior. There should be no difference in smoothness or battery, it's the exact same code.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Tak3r07:
So you say on stock you have 80% after 1h SOT and on EX you have 75% after 1h SOT, which obviously is "terrible". I assume you have made sure that your observations were under the same conditions, running the same apps for the same time in this 1 hour. And for sure you have repeated this test at least ten times for both kernels and took the average so you can say that these differences are significant. Then you are free to blame the evil dev.

Jokes aside, this 5% difference is nothing near significant. It may just come from different usages of your phone in this short interval.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nil253259:
Apologies if my earlier post sounds rude.

I usually follow a charge cycle of 100% - 20% which makes the battery consumption 16%/h. 25%/h with EX is on the higher side. Since the release of Oreo I think I have repeated the cycle more than 10 times, and with EX, I tested for 3 cycles (agree it's less than 10 :silly:), but thought it showed me a pattern of using higher frequencies more frequently than stock. My usage pattern is more or less similar, using similar apps over similar wifi/data ratio.

But even considering all these factors if I'm the only person who's getting worse battery than stock, I'll investigate from my end. Something is wrong for sure. :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sh0X31:
Do EX Kernel v2.0.1 support init.d?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
Why are you asking about ancient init.d? It is unreliable and should not be used. Please place your scripts in the folders provided by SuperSU or Magisk (whichever you use). You can do this very easily with the script manager in EX Kernel Manager.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sh0X31:
I want to test the scrip by Freak07
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
Just place it in the appropriate folder for whichever root solution you use. Use the script manager in EX Kernel Manager if you are unsure, it does it automatically for you.

init.d needs to die, there are better solutions that ensure the script run at the right time with the right privileges.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
Can someone give me some pointers or advice on. What settings your using in the ex app? I installed the kernel last night, didn't mess with Amy setting in ex manager. Woke up this morning and in an hour and forty-five mins I'm down to 82% battery with 2 Facebook videos and one TWRP install of updated busy box and 10 mins of XDA reading. I believe it's in the kernel setting but I'm not familiar enough to know what to change.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kingkong0821:
Just let it be default, and try for a few more battery cycles

Maybe some apps are draining the battery
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
Will do. Thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
Update!!

You will need to do the same procedure as before: flash stock boot.img, flash ElementalX, flash SuperSU (still haven't had a chance to try with Magisk)

Android 8.0.0 (Oreo)

ElementalX-P-2.02

Changes:

-October security patches
[Google Pixel ROMs, Kernels, Recoveries, & Other De] clothednblack:
Dang it, I just got twrp to stick, I should have clicked here 1st lol.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] adma84:
if we want TWRP to stick, would it be, flash stock boot, flash twrp, reboot twrp, flash elemental, flash supersu ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
Your problem was never a kernel issue. Color is exactly the same on Franco's kernel. It works fine on both.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] xxnirvana69xx:
Must have been a bad download or flash because reflashing a kernel was the fix.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
There's no such thing as a bad flash. If the download is corrupt, the kernel would not boot. I don't know what the issue was, but changing the kernel was not what fixed it. Rebooting probably fixed it. There could be some interaction between night mode and color adjustment. If there is, it will be present on all kernels.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] xxnirvana69xx:
✔. Was just letting you know my experience.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] RedBeardT:
Pixel 32g NDE63L. Boot slot a.

Flashed P-05 Kernel on phone previously rooted /w SuperSU 2.78 SR3 and then ran autoroot to gain root again.

Wasn't paying all that close attention when it happened but I caught a glimpse of a colorful circular graphic at boot that said "Erasing" and found that my phone had been factory reset upon boot. It booted clean the first time but then crashed during the app install portion of restore.

Afterwards the phone was in bootloop but I was able to boot successfully once long enough to verify kernel install but it crashed soon after too. Phone is now back up after resetting by flashing the factory image.

I don't know what's going on but based on there being similar reports I'd say there's something.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shinesthru:
You "ran auto root"? I believe you should use fastboot to attain root at this point. Maybe that is a contributing factor.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] RedBeardT:
Poor phrasing on my part. I did in fact run Chainfire's root as :: fastboot boot boot-to-root.img
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JohnnyMcG:
What do you guys use for kernel managing? I usually use kernel auditor but I have had problems in the past with changing CPU frequency.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piccit:
EX Kernel Manager
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JohnnyMcG:
LMAO idk why I even asked that question on a elemental kernel post lol umm what did I think the answer would be lol
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
Update!!

Version 0.07

Sound control is updated to add earpiece, mic and speaker controls and to fix problems with gain resetting. Hopefully I covered every scenario. Thanks to [MENTION=2760454]chdloc[/MENTION] for guidance.

I need to update EXKM for full sound control. It will have gain control for main speaker, earpiece speaker, mic, analog and digital headphone gain, plus a toggle for stereo mode if you are using [MENTION=2760454]chdloc[/MENTION] dual speaker mod. Eventually I will also be redesigning the sound controls to make them easier to use, but that won't be in the next update.

Also includes November security update
[Google Pixel ROMs, Kernels, Recoveries, & Other De] qwer777:
Question related to your High Brightness Mode, but would it be possible with a kernel edit to lower the minimum brightness? I wish the minimum brightness in manual mode was the actual minimum that you get in a lightless room on adaptive brightness. Preferably lower actually.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nic2112:
Thank you for putting together a kernel. I don't have the guts yet to root by Pixel (although restoring to factory is so easy, flash-all.bat and done) but I'm sure I will soon.

DT2W is a feature I always appreciate.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Quadman:
I'm on slot b so install it on that partition? Also do I have to have root for the kernel? Thx and sorry if these are dumb questions.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tempguest:
Is there anyway to update my kernel without factory resetting my phone? While it does root my phone, every time I use the "fastboot boot boot-to-root.img" command - typically after flashing a new kernel - it factory resets my phone. This doesn't seem to be the case with anyone else.

Am I doing something wrong
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Quadman:
Do I have to have root to benefit from the kernel? How do I enable dt2w as it's a must have for me.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piccit:
Yeah that's not supposed to happen.

Maybe try rebooting into system in between flashing kernel and rooting?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
For now, yes you need root.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ihierbal:
I've flashed multiple kernals, then boot to root image directly after and have not had the phone fully wipe on me. Sorry don't know what the issue is.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kenjoma:
Can someone please tell me where the settings are located for doubletap2lock. I am not seeing any settings for it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] clothednblack:
Twrp sticks without flashing a kernel, it did for me.

I did fast boot boot img

Fastboot twrp

Used twrp to install permanent twrp

Rebooted to twrp and flashed su and suhide.

Twrp stuck as it should without a custom kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] henk-jan:
That's how I did and it works
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ss11602:
How would i Flash this kernel on oreo running NiKernel?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Flash stock boot.img then flash ElementalX
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ss11602:
you know where i can get the stock boot.img
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Factory image from Google.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ss11602:
Thanks a bunch i fund it and got it running. great kernel
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I'd love to see mac address randomization added to this kernel. It would give users some anonymity, like iOS implements. Really this should be a standard feature for android...

You would only need to pickup a couple of patches to support it;

https://github.com/CopperheadOS/kernel_google_marlin/commit/a665b3e20cdbabce3eb8613338e09eba347490f0

https://github.com/CopperheadOS/kernel_google_marlin/commit/c4ba8c73cca490c30d65d7539be2292695a8bdc0

then it's just a matter of providing a way to enable or disable it, via sysctl;

/proc/sys/dev/cnss/randomize_mac

dev.cnss.randomize_mac

I've build an ex kernel with this support, however, I'm still looking for a way to pack up the kernel (Image.lz4-dtb) properly into a boot.img for the pixel (no AOSP sources on my box)

EDIT: I sorted it out and have ex kernel with mac randomization + verified it works too :) ... I used AIK (replaced the kernel in stock, repacked. flashed boot.img with twrp, then flashed magisk, which got around an 'dtb not found' error I was getting trying to flash it with fastboot).

anyhoo, I thought I would point it out, in case it was something of interest.... Would be a great feature to have for other people.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Getting absolutely awful battery life. Any ideas? Here are a couple screenshots. Any advice is greatly appreciated.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
These are features that help make the kernel & the overall Android eco system move forward. Thank you for pointing it out
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
no problem. I had been using Mac randomization for a couple of years with my old device / modded cm-13/14.x roms, but just got it working with the pixel stock ROM today. (the pixel random Mac patch is much different than the old patch; which I had to port from the galaxy s4 to my old s5 device)...

anyway, props go to copperheados, google and Qualcomm - as copperhead has been doing Mac randomization fir a long time and IIRC google and Qualcomm had something to do with the new patch...

so more props to them? than me...lol.

lastly, not sure if ex kernel manager supports 'custom controls' like kernel adiutor does? ... *** but this feature should have an ON/OFF switch... there are situations (like a home or office network), where it may be undesirable to have your Mac addressed randomized...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
For known networks, it could send a fixed Mac address and for the rest, randomized. This might require ROM support to do the right thing.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I think we start talking about needing a custom ROM fir a single feature / sysctl provided in the kernel, an idea should be reevaluated, discussed....

in your scenario; that complicates things. one should be able to flash the kernel and be able to use the feature, without too much fuss. IMHO... having it automated is nice, but if I wanted to do that; I could use an auotmation app such as tasker, on any ROM including stock...

the other problem would be this feature only supports the pixel (or rather the pixels hardware/driver), so it's not very portable code (for other devices), I'm guessing it likely wouldn't be a good candidate for inclusion by any xyz maintainer/ROM Dev..
[Google Pixel ROMs, Kernels, Recoveries, & Other De] yoshi-7:
Unfortunately, I have two problems.

1. If I change the vibration intensity in EX Kernel Manager, it has no effect on the actual vibration. Not even after a restart

2. I've activated sweep2wake. Now the problem is that every few days when i am trying to wake up the device with the gesture, the device is not longer responsive and restarts on his own.

Any idea?

Google Pixel 5" (Sailfish)

EX Kernel 2.02

EX Kernel Manager 3.36

SuperSU v2.82-SR5
[Google Pixel ROMs, Kernels, Recoveries, & Other De] flar2:
I know about the vibration issue.

For sweep2wake, I always have it enabled and still use this as my daily phone. I've never had a problem with restarts or non-response. I suspect that problem is related to something else.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] roirraW "edor" ehT:
+1 no problems with S2W on Oreo for the last couple of months. I'm on the latest Oreo (October), ElementalX (2.02), and SuperSU (2.82 SR5). For reference, I didn't install TWRP, only booted it to install what was necessary, but I'm sure that wouldn't be the culprit.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] haibane:
so is elementalx meant to pass safetynet or is that not something being targeted? seems like it is the only thing that triggers safetynet on my system.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] unhappybirthday:
ElementalX will hide an unlocked bootloader from safetynet. If you are using root then you need to hide it with the proper tool for the root you are using (magisk, supersu).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] yoshi-7:
Thank you for your answers!

The problem with the restarts also occurs with the stock kernel. The device is now being replaced.

Will the vibration problem be fixed in the upcoming release?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kazemitsui:
Is magisk or SuperSU the preferred way to root on the pixel or is it preference? [MENTION=4684315]flar2[/MENTION] what do you use if I may ask

Thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
I've used both with no issues. Currently running Magisk as I don't like what CF did with SuperSU, but it is still an option.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] billiepreks:
[MENTION=4684315]flar2[/MENTION]

Hi, thanks for your kernel I use it since I've my Google Pixel ?

Question : I totaly don't know if it's complicated to do, but if it's possible and not too hard can you adding "binfmt_misc" support to your kernel ?

Thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
Hey guys! I just tried installing the kernel and I’ve run into an issue. I flashed the stock boot.img from August 8.0 release, then flashed the kernel, then performed a reboot. The issues is it gets past the boot animation (dancing dots) but it freezes on the G logo with the moving progress bar beneath it. It’s been frozen like that for about 10 minutes now. [IMG="Freeze"]https://i.imgur.com/h7AzvRn.jpg[/IMG] Any help would be appreciated. Thanks!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
just some advice; you should really consider staying up to date.... like whenever the November update / OTA shows up, get yourself on the latest release...

maybe your bootloop has to do with the fact that most kernel devs pull in the latest fixes and security updates every month.... your issue could stem from that.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
I tried updating from FlashFire but it refused to work, and I thought Magisk allowed for OTA updates so I wasn't sure what to do.

If I download the OTA or factory image of that version, can I remove the -w tick, and install the kernel with all of my data still intact?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I've never used flashfire, so I can't help you there.

Magisk does allow OTA updating, but it requiring some manual steps. the gist is that u need to patch the boot.IMG in the its / slot_b after updating, but before rebooting...there is documentation / articles kicking around on the subject.

this what I do;

1. I download the latest firmware image

2. unzip it and edit the flash-all script, removing the -w flag (so it doesn't wipe my data)...

3. I run the script (from in it's folder).

4. when it reboots, I hold volume down + power (bootloader)

4. then fastboot into twrp (fastboot boot.img),

5. flash my kernel zip and magisk.... reboot.

I do it this way because it's easy, all of the needed files are on my PC anyway AND my pixel is frequently connected to my linux bbox anyway, for app / kernel development...

---------- Post added at 06:48 AM ---------- Previous post was at 06:46 AM ----------

yes, as my above answer describes... u edited, while I was typing on my phone! ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
Haha! Sorry for the impatience, I'm new to the kernel side of things. After flashing the update is it okay to boot into Android before the bootloader again? I just like to make sure things are working properly.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
yes, reboot for sure, if u want.

I just added that in, since I don't like having to constantly reboot... I already do enough off that testing out / dogfooding my own kernels...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
Awesome! I assume rebooting after installing the kernel is a good idea too. I want to keep TWRP and Magisk permanently installed.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Well, after flashing the factory image, you do need to flash magisk and twrp (the factory image's boot.img will toast both of them), but there is no harm in rebooting to make sure that the upgrade went ok, if that's what you meant?

I just don't reboot and go straight back into the bootloader so that I can flash my kernel and magisk (I don't install TWRP, I have no real reason to).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] udahy.manna:
It supports 8.1?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
That is exactly what I meant. Thanks a ton! About to test the kernel again now on the October update.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] yl1504:
Someone tried November update with the latest kernel? Does it work? Or should we wait?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] henk-jan:
And what about 8.1?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
if u look on flat2/elementals github, flag2 has merged in Nov patches from aosp. not sure if he's updated...no idea

I would think the Oct 2 build would run fine on Nov firmware my kernel did).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] roirraW "edor" ehT:
2.02 works with the November image for me.

I used FlashFire to flash the entire November image, including all the "dangerous" partitions to flash and enabling to flash the bootloader partitions in Settings. I said Yes to FlashFire's offer to split the flashing into two parts - the non-dangerous and the dangerous ones. I told FlashFire not to EverRoot since it has an "old" SR4 of SuperSU and I wanted to flash this kernel again for S2S. I told FlashFire to reboot into Bootloader at the end of the flashing, then I fastboot boot'ed TWRP, made a TWRP backup of my boot.img, flashed Ex v2.02 and then SuperSU 2.82 SR5, and all's good.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] yl1504:
Thanks for the feedback!

2.02 works fine for me with November update and not rooted!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sh0X31:
DO someone try 2.02 on November Update?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I did briefly... It seemed to work fine - just lacking all of the patches for Nov....

flar2's github has them all merged - and bumped to 2.03 - not sure if the link is updated on his site or not (never checked)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sh0X31:
Can't find a 2.03 on this Androidhostfile Account :( :P
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Well, I guess you will just have to wait for an update.... Maybe flar2 is just busy or working on something, no idea.

not the end of the world.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] eddi0:
I just got an OG Pixel and have it rooted with Magisk 14.3, coming from a Nexus 5X. I just installed EX and there are no kernel profiles installed like there were with the N5X. Am I missing something? Where do I get the Pixel EXKernel profiles that are out there? Or do I just need to change the stock kernel to interactive.? Or?

Confused (obviously).

Much thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Sched is already very well tuned for pixel using EAS. Governor profiles weren't ever really created because of it.