yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 2.0.12

Hey guys and girls,

4.9.161 dropped yesterday. Here´s the updated kernel that has it merged.

Also include a patch from kernel/common to speed up read time of /proc/uid_time_in_state file.

Here´s the commit: https://github.com/freak07/Kirisakura_bluecross/commit/7415032875e6c68efe663393ba8cb6ded969cca2

Changelog:

- Linux Stable release 4.9.161

- kernel/common cpufreq_times improvement

Important :)

All flashing errors are now fixed. If you experience the ramdisk error please take a look at the FAQ.

Have fun flashing and enjoy your device with latest linux-stable :)

Why is linux-stable important?

I wish you all a nice day/evening!

Download is below :)

Download:

https://www.androidfilehost.com/?fid=1395089523397903441

or following the link in the op to the correction version

Instructions can be found in the OP!

But look at this post too :)

Have fun, enjoy the kernel and your phone.

If you like my work please consider a donation.

Donations are not mandatory but very welcome.

If you like my work and want to buy me a coffee: http://paypal.me/freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
Thank you

Very informative and detailed :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I fear, I´m not exactly getting what you mean by recency? In the changelog section of the OP you can find a link to the changelog/release-post of every single release. The most recent release being always at the bottom.

Do you maybe want me to put the date of each release into the OP additionally? But than can be found when just viewing the release post I guess.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Hung0702:
I meant putting the most recent at the top. That way, the top link is always the current release.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] exile1ck:
Is anxiety still the prefered I/o scheduler?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Semtronix:
It's too much effort to click a link to read the changelog so he wants you to have a post that just has all the changelogs listed as you make them.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
The default I/O Scheduler (CFQ) was and still is the preferred one. It’s patched up and works really well. I never stated otherwise.

All other are for people who like to experiment and have choices :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
You still running fiops? (That's what I'm running at the moment. Used to run deadline - I ran cfq on spinning disks. I don't think it really matters too much on our phones)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I´m running CFQ currently :)

You´re right it doesn´t make much of a difference. Our storage is already blazingly fast. It´s extremely use case dependant and CFQ is very good all around and a very good choice for the default option :)

However deadline doesn´t work to well on newer (EAS) devices. See this discussion with arter97 too:

https://twitter.com/arter97/status/1004143489171353600

Google tried it and reverted it shortly after.

Okay now I understand. I like growing the chronological order to the bottom in the OP as it is now :)

Thanks for your suggestion though! I hope you can cope with my way of doing it and still visit the OP from time to time when a release drops. ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] OGTempestfqg:
Comparing with normal kernel , did you get a lot more SOT or just a little? Im thinking should i stay in stock or flash this because i need more battery life . Thanks for replying
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
It depends on your usage. Just backup your current boot.img via twrp, flash my kernel and see if it works out for you. You can easily restore your previous kernel by restoring the backed up boot.img.

I’d flash it alone for having more control over my phone like sweep to wake, sweep to sleep, vibration control etc.

This kernel is way more up to date than the stock one in more than one way! Just try it out it doesn’t hurt ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
I can confirm it didn't hurt when I flashed this kernel on stock rom. Good luck!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
Work just fine flashing through ex over proton
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] OGTempestfqg:
I'm just curious and scared because im new to this
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Fair enough. Some things to know and consider.

1) it's almost impossible to hard brick these phones. You have to work really hard and do something really stupid to do that. I've been told it's possible, although I'm not sure how myself.

2) make sure you have a backup of the stock boot image on your computer.

3) make sure you're familiar with at least the basics of adb and fastboot.

Since you're only talking about kernels at this stage even if something goes very wrong you should be able to restore things by flashing the boot image to both slots and rebooting the phone.

I recommend you not try to flash TWRP and just boot the image using fastboot. That eliminates one point of possible failure.

Good luck, take your time, have fun!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Bryanx86:
Root stock and lock your bootloader, then you got a brick. Or put a custom rom on, and lock it. It seems like the only way to turn your phone into a permabrick is to lock it after modifying it, so just don't do that. BUT I've read that there is now a way to fix this if able to get to bootloader. So good thing they are hard to brick. Great kernel, donating today. Thanks@freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
? I did mention doing something really stupid! I think that qualifies.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] scloutkst:
2.0.12 flashed just fine on March update. No security bulletin posted for update yet. So we don't yet know what Google fixed or broke.

Edit security bulletin posted

A-122471935 Camera Improves Startup and responsiveness of Camera app Pixel 3, Pixel 3 XL

A-112046316 A-118317435 A-120212581 Performance Improves recovery in the instance of OTA update failure Pixel 3, Pixel 3XL

A-120920537 Performance Improves storage performance on Pixel 3 devices Pixel 3, Pixel3 XL

A-119776006 Bluetooth Improves bluetooth reliability on Pixel 3 devices Pixel 3, Pixel3 XL

A-111260263 A-116848259 Media Improves playback of encrypted media on some video apps Pixel 3, Pixel3 XL

Looks like they fixed the problem our main man here already took care of for the filesystem performance.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
No kernel source published yet. As I know google they post it just when I’m asleep :laugh:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] scloutkst:
I wasn't complaining in the slightest. I am absolutely blown away by the quality, quantity, and speed at which you drop updates. I was simply posting to let people know their were seemingly no issues running the latest kernel release on March update.

Thanks again for the hard work.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Didn’t take it as complaining from your side at all :highfive:

Thanks for confirming it’s still save to flash the latest release even on march release now. Enjoy the kernel and thanks for the nice words!

Hopefully this month’s release will improve our device even further. :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
I am on March patch with 2.0.12 seems to be working fine.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Always does
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
what if we use noatime, nodiratime with nolazytime

does that mean ctime atime mtime don't get updated at all?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
No, it doesn't. Just stop already.

If you use noatime (which is the default) you don't need nodiratime since it's already implied by noatime

ctime and mtime will always get updated. The only question is when that update is applied to the physical inode.

noatime means that atime will never get updated.

nolazytime will provide no tangible benefit in terms of performance. That said, in conjunction with noatime, it also won't hurt your performance very much since atime was the most significant impact on performance. But it will hurt it somewhat.

Anything beyond this - Google is your friend.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
sorry if it's annoying, I just get curious
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 2.0.13

Hey guys and girls,

The source for the new security update dropped this night while I was asleep. I merged it this morning and wanted to run it for a few hours to make sure everything is alright!

I think that´s beneficial for everyone, taking a bit time, just make sure there are no issues introduced.

Most of the patches, which google pushed, were already in my tree :)

The commit causing severe regression to file system performance, introduced by google in the february security update, which I decided to revert in 2.08, got now officially reverted by google and fixed in this commit.

KLAPSE is now built into the kernel, for those who already heard about it or want to use it! Description can be found in the commit description here.

Or at the developers (thanks to [MENTION=5913332]tanish2k09[/MENTION]) Github-Site.

Feature can be set with latest release of EXKM!

Kernel is now built with Clang 8.0.9.

Changelog:

- March Security Update

- Kernel built with Clang 8.0.9

- KLAPSE included

Important :)

All flashing errors are now fixed. If you experience the ramdisk error please take a look at the FAQ.

Have fun flashing and enjoy your device with latest linux-stable :)

Why is linux-stable important?

I wish you all a nice day/evening!

Download is below :)

Download:

https://www.androidfilehost.com/?fid=1395089523397907490

or following the link in the op to the correction version

Instructions can be found in the OP!

But look at this post too :)

Have fun, enjoy the kernel and your phone.

If you like my work please consider a donation.

Donations are not mandatory but very welcome.

If you like my work and want to buy me a coffee: http://paypal.me/freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
[MENTION=3428502]Freak07[/MENTION] Does Klapse interfere with adaptive brightness?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] scloutkst:
Saw something interesting on reddit. User. Mentioned March update allowed high performance cores to hit full clocks at 2800 Mhz. Has this always been the case? Or were they limited to 2500 Mhz. Never really paid attention. They definitely hit 2800 Mhz now, but I thought that was the case before as well.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
It should not interfere as adaptive brightness is Rom related and KLAPSE is kernel based. They should work alongside each other, but might also effect each other!

The big cluster of bluecross devices always scaled to 2,8GHZ since the release of this phone. A few sites spread misinformation, that Google supposedly downclocked the performance cluster, but that was always false information.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] scloutkst:
That's kind of what I thought. Thank you!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] peikojose:
Will this work with February roms?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I don´t really know where this misinformation originated, but it´s definitely wrong.

You´re very welcome.

It most probably should work with February Roms. I ran it this morning for a few minutes, but upgraded then. ;)

Doesn´t hurt to backup your boot.img before flashing. That way you can quickly return in case it´s not working, but I´m quite sure you don´t have too :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] scloutkst:
Well that misinformation has definitely stuck with people. I had to have this thread pulled by the moderators over at reddit.

https://www.reddit.com/r/GooglePixel/comments/axkyop/starting_with_the_march_update_the_pixel_3_runs

I hate when people spread bad information because they are uninformed. And the op was still trying to argue against this after multiple people confirmed he was wrong. Smh.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Maybe it started on gsmarena. I don’t know.

https://m.gsmarena.com/google_pixel_3_and_pixel_3_xl_hands_on-review-1833p3.php

It was already reported to them, but they didn’t bother to correct their article at all.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] scloutkst:
Yeah Idk. Sorry for going off topic and cluttering the thread. Thanks again for the good info.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I already answered you a few posts back ;) just look above.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
I just install the kernel and now stucked in the google screen.

I have to re-flash the original boot.img into both slot then went into twrp and flash the kernel and magisk, it's all fine now
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] peikojose:
Sorry connection problem sent the question two times
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yung40oz84:
Just a few general questions.

1. Is the adaptive low memory killer as it sounds? It just adapts based on the usage? Any battery drain from this or minimal?

2. For the gestures the vibrate on wake doesn't work. Is this normal? Lol Also, when u enable double tap it doesn't work, when u disable it, then it works. Just wanted to tell ya.

3. What's the recommended read ahead for a 128GB device such as mine?

4. Is there a good read on tweaking the schedtune settings and adjusting EAS, or is it recommended to keep those settings untouched on this kernel?

I think that's it for now, lol. I've been in the dev community for a very long time, but just got the Pixel 3XL after experimenting with other devices ? just wanted to get up to date on some things.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
welcome to the pixel 3 xl forums then :)

1. Has nothing to do with your usage, but rather the vmpressure. However leave that setting as it is (disabled), the oom_reaper mechanism is enabled, which takes care of freeing up RAM. If you would have searched this question was already answered a few months ago :P

https://xdaforums.com/pixel-3-xl/de...ra-1-0-0-pixel-3-xl-aka-t3864563/post78364541

Stuff to further read up about this topic: Take a look at this about the OOM_REAPER as well as the commit description itself

2. Vibrate on wake works fine here when using sweep to wake (all set via EXKM). For double tap to wake you have to disable native double tap to wake in the ROM settings. Then activate the kernel solution in your favorite kernel manager.

Keep in mind double tap to wake on the pixel 3 xl, is not a double tap but rather a "double smear" to wake. Smear your finger while tapping and it will work reliably. This is a quirk in the touchscreen driver from samsung.

3. This was also asked a few weeks ago. Leave it at 128 KB and CFQ.

More info: https://xdaforums.com/showpost.php?p=78890223&postcount=975

4. Just leave everything as it is. Documentation about EAS is linked at the beginning of the OP!

Everything I want tweaked in the kernel is already tweaked in the source and set at compile time. Features like KCAL, KLAPSE, Wake Gestures, Speaker/Mic Gain can be set as desired :)

Generally it´s just flash and forget. If you want to experiment the kernel open all kind of possible tweaks :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] SCYTHERBLAKE:
[MENTION=3428502]Freak07[/MENTION] is it possible to add volume rocker music playback control to the kernel itself because i love the stock rom and i love your kernel. So just a suggestion for future update.

Thank you for the update and love to see this thing possible to the kernel
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
[MENTION=3428502]Freak07[/MENTION]

Hi boss! Thanks as always for your work, but I have one question. After the latest update I can't flash your kernel, I've tried flash trough EXKM app, it gives me repacking error after it detect magisk. What I should do? I'm asking before I make a mess ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
had the same issue. thru twrp works fine.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Are you on canary builds? If not which magisk version are you on?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
I use unofficial [MENTION=3306843]kantjer[/MENTION] version of Magisk.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
Latest official build 18.1 sir
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
I also couldn't flash with ex kernel manager. Had to use twrp. I'm on magisk canary build.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
Sorry for the double post, forgot to attach the screenshot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Jiggs82:
I wonder would the new kernel work on rom with feb patch? lol
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
https://xdaforums.com/pixel-3-xl/de...ra-1-0-0-pixel-3-xl-aka-t3864563/post79044551
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Jiggs82:
Flashed 2.0.13 kernel and magisk (just to be safe) via twrp and it works fine ;) thanks.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] tanish2k09:
Klapse doesn't interfere with brightness. However, the brightness_factor (or Dimmer as in EXKM) emulates a lower brightness by reducing the RGB multipliers in KCAL.

By design I made klapse only "read" the actual brightness for mode 2 (brightness-dependent mode). It can't write to it.

I wonder where these points originate... RGB ≠ brightness

I should probably make a little FAQ section in my thread.

Also, thank you [MENTION=3428502]Freak07[/MENTION] for using my module :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] exile1ck:
Anyone getting this issue when flashing the new kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Jiggs82:
Flash it via twrp instead
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rohmbd:
I did with Ex... switched to the Franco app and it flashed fine.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rspkt:
I can confirm everything is working flawlessly on March update with 2.0.13 flashed via TWRP. Thank you again [MENTION=3428502]Freak07[/MENTION]!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jstoik:
I too ran into trouble trying to flash this kernel with EXKM after the March update and Magisk v18.1 (18100) — same version I was using before — but trying to install the kernel via TWRP 3.2.3-4 had also failed me at first.

I ended up having to reflash a clean boot.img to both slots with fastboot; use Magisk Manager to generate a patched boot image; flash that image to both boot slots with fastboot; reboot to system once to make sure root was installed and behaving; then finally boot twrp-3.2.3-4-crosshatch.img and install the Kirisakura 2.0.13 release from recovery.

But everything's A-OK now! ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey [MENTION=7914014]SCYTHERBLAKE[/MENTION]

Unfortunately this is not possible at kernel level. But I see you already got a reply from flar2 in his thread!

Hello,

It seems the version 4.04 of EXKM introduced this error, as I was able to reproduce it yesterday. However the latest update to EXKM 4.05 allows me to flash via the app again.

I did no changes to my installer so it was most likely caused by some change in 4.04 EXKM. I´m going to release a new kernel soon anyway, it would be great if all of you can make sure to update EXKM to 4.05 and flash the kernel via the app as usual. Please report back if the issues are solved with the EXKM update.

In case you still get an error you might want to restore your stock boot.img and reroot but I don´t think this is necessary. Thanks everyone!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
New release with 4.9.162 included will drop soon!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] newkydawg:
I can confirm that EXKM 4.05 correctly flashes Kirisakura 2.0.13 on Feb. rom. I tried earlier with EXKM 4.04 but it failed.

Thanks again [MENTION=3428502]Freak07[/MENTION]!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 2.0.14

Hey guys and girls,

4.9.162 got released yesterday evening. Here´s the next kernel with linux-stable bumped up to 4.9.162.

Sorry about the fast releases :P

The flashing issues with EXKM should be solved with EXKM update 4.05. Make sure to update to this latest version of EXKM, before attempting to flash it via the app!

Changelog:

- 4.9.162 included!

Important :)

All flashing errors are now fixed. If you experience the ramdisk error please take a look at the FAQ.

Have fun flashing and enjoy your device with latest linux-stable :)

Why is linux-stable important?

I wish you all a nice day/evening!

Download is below :)

Download:

https://www.androidfilehost.com/?fid=1395089523397908208

or following the link in the op to the correction version

Instructions can be found in the OP!

But look at this post too :)

Have fun, enjoy the kernel and your phone.

If you like my work please consider a donation.

Donations are not mandatory but very welcome.

If you like my work and want to buy me a coffee: http://paypal.me/freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
Flashed the latest kernel with updated ex kernel manager and all worked perfectly.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jstoik:
The latest EXKM flashed the latest kernel without any issues. Thanks [MENTION=3428502]Freak07[/MENTION]!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] qualitymove13:
I appreciate the quick updates! One question going back to the old days. Is letting a kernel "settle" still a thing?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
Sorry if it is a noob question but is there any compatibility or performance problem with installing Magisk Face Unlock module and this kernel?

(I have had interaction between Face Unlock and Custom Kernel on another device)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] i42o:
Try flashing like a always flash and this is the first time I get something like this
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
Did you update exkm to 1.05. It was discussed earlier
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
It never was for me really.

However after setting up a device or a silent play service upgrade your device may behave different because it’s setting stuff up in the background.

I test each and every single kernel release and to be honest I don’t feel much of a difference after flashing it. But my battery life on this phone was pretty good from the beginning. So if it would have gotten worse I’d probably notice it quickly.

The pixel 3 xl doesn’t have native face unlock as far as I’m aware. There may be tricks to somehow get trusted faces back but I don’t know how it would fare with the kernel so I have no direct answer.

But I wouldn’t use a magisk module to get a security “feature” I guess.

Yes as [MENTION=3961342]gvsukids[/MENTION] mentioned make sure you update your exkm app to latest 4.05 version. That piece of information you literally quoted when quoting my release post... :rolleyes: ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
:( I am so used of the quickness of face unlock.

But I will follow your advice and hope it will be integrated to the Pixel 3 xl in the future.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] scloutkst:
It will never be brought back to the pixel 3/xl. It was removed as it was insecure. It didn't have the hardware like the new iPhone do that makes it more secure. Do not expect face unlock to come back.