yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] newkydawg:
Stock ROM for me. Still on Magisk 24.3 stable. I don't think 25 is "stable" yet. Attached is a screenshot of the Magisk GitHub page.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] crisis_trustee:
Thank you for update kernel!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Carmine8:
You are right, it was still in beta!

Actual stable magisk 25.1 has been released - did anyone try to update on latest krisakura?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] snowrelyt:
I'm using Pixel Experience June patch. Even with a completely stock PE boot image (no magisk), flashing 5.1.1_S causes the bootloop immediately.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Unfortunately I don't know what can be the cause, but it seems something is not right when flashing on source built custom Roms.

The reports started when magisk 25 dropped though even with zips that previously worked. So it might not be the kernel, but rather down to magisk and/or something the custom roms changed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nldxda:
Working for me with the stock ROM
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
I'm on blueline, 5.1.1_S, LineageOS 19.1 (June 14), Magisk 24.3. No issues to report.

I haven't tried updating Magisk yet.

Might be time to start a spreadsheet of what's working and not.

Would logs help?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
You need to be rooted to flash kirisakura
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] CRCinAU:
Also, boot into recovery and disable your Magisk modules. Check to see what is causing the bootloop - because it likely isn't the kernel or Magisk...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
Are you sure? Can't you flash it from TWRP?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] mgp53:
Always, to flash a custom kernel!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
I flashed through twrp and caught myself in bootloop
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
Interesting. And it did work ok when you were rooted first?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
I flashed using ex kernel manager and everything works grt
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
I've had successful flashes both ways /shrug

I really should try the latest Magisk - I haven't bootlooped in a while ;-)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
Try out 24.3 V as 25 is not stable yet
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
I'm already on 24.3. 25.1 is listed as the current stable
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
Okay I'm still on 24.3 bcoz of unstable 25 v
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] agraceful:
Have you gotten freak any logs? As far as boot looping, it started back with an alpha when John made a commit for legacy devices. Or it could possibly something similar to what those are experiencing on the p6pro.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] newkydawg:
Magisk 25.1 is stable. Stock ROM, Kiri 5.1.1 and Magisk 25.1 here and running great!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
LineageOS 19.1, Kiri 5.1.1 and Magisk 25.1 here and also running great!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
Ohh okay then I guess I will finally update magisk... Thanks👍
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dcarvil:
Do you have module "Magisk Bootloop Protector" version 1.8 installed? I ask because I went straight to bootloader mode when I updated Magisk to 25.1. I was on LineageOS 19.1 June update, and Kiri 5.1.1. The new version of Magisk Bootloop Protector repacks boot.img, so maybe there are just too many apps changing boot.img.

The only way I was able to recover was flash the stock LineageOS boot.img, remove the Magisk 25.1 apk, then reroot with Magisk 24.3.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
Nope. I don't use Magisk Bootloop Protector. (Sounds like the module description might be inaccurate.)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
@Freak07 Hey Lineage OS found the fix for microphone sound gain.

Here's the link for that.

ASoC: ops: Fix the bounds checking in snd_soc_put_volsw_sx and snd_so… · LineageOS/android_kernel_google_msm-4.9@f2afdeb

…c_put_xr_sx The $val in both functions has a range between 0 and an arbitrary limit whereas the range specified with the $min and $max can start from a negative number. To do the out of bound che...

github.com

May I ask you to add this fix in next update please?

Using kernel adiuter app consumes more RAM.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] newkydawg:
FYI, I updated to the June "VoLTE Roaming" factory image this morning with Magisk 25.1 and Kiri 5.1.1. Running great! Thanks @Freak07 !
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nubru:
I have this problem too. The only way to use Kirisakura is to downgrade to 24.3 or lower. Magisk 25.1 works with a patched LineageOS bootloader but as soon as Kirisakura (or ElementalX) is flashed it gets stuck at fastboot and requires the patched LineageOS bootloader to boot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] agraceful:
Where's the log for freak? Can't solve this issue without being able to reproduce, or seeing the cause
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nubru:
how would I get the relevant logs from a bootloop? I grabbed logcat after reflashing the LineageOS bootimage but from what I can tell there's no logs addressing the Kirisakura kernel seeing as it refuses to boot. Looking in the ExKernel Manager app saving the Previous Kernel Log (pstore) resulted in an empty file. adb doesn't work in fastboot so I can't physically grab a logcat from a bootloop, unless you know a way? twrp doesn't work on Android 12.

edit: I tried an alpha build of twrp from that thread, booted it with the Lineage kernel and grabbed the logs fine. Flashed Kirisakura, rebooted into twrp and tried to get logs but no such luck: adb wouldn't connect presumably because the kernel won't load.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] pbcsd:
Can't seem to find instructions on restoring my Pixel 3XL to stock image? Looking to sell the phone shortly and want to remove TWRP, Magisk, etc.

Hmmm...maybe all I need to do is relock the bootloader. But Fastboot Flashing Lock command returns a failed to validate boot images error?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dcarvil:
See https://developers.google.com/android/images
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jlokos:
Are you running stock rom?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c0dac0da:
I tried it last time with relocking bootloader on pixel 3 & got a no os found message, soft bricked but was able to get the device get back to bootloader & reflash.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
hey :)

attached build includes the fix you linked in your post. Please give it a try and report back.

Wireguard is bumped as well.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] _Axios_:
Works great as far as I can see. Also, the low mic volume issue seems to be fixed. Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] krutx:
+1

The same problem with PixelExpirience. Original PE kernel works well with latest Magisk, but with this kernel I stuck at fastboot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
Oh yeah sure I'll give it a shot
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
Just installed on my XL after upgrading from last 11 version to the latest 12 release (June).

Installed via EXKM and all seems fine.

Thanks again for keeping up-to-date on this!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] entux:
I'm running lineage-19.1 but it keeps overwriting any custom kernel with each ota update. When I want to flash it back I'm running into the issue with a non-responsive touch screen with TWRP. So I can neither flash any custom kernel nor magisk to root the device so I can use a custom kernel flasher (which requires a rooted devices).

Any ideas?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
The kernel does get overwritten but Magisk should be retained.

Are you saying your TWRP is retained but not Magisk? Are you using the TWRP Magisk module? (Hint: don't).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] entux:
No. I haven't installed Magisk so far because I didn't need root. But I EITHER need root for a kernel flashing app or a working TWRP install for kernel flashing or Magisk installation.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
Flashing this kernel needs root either through twrp or from custom kernel flasher... Just read info on 1st page...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] entux:
I had TWRP up an running and could install the kernel just fine when I was running stock. But after installing lineage TWRP introduced the non-touch screen issue. I was hoping someone had experienced something similar and found a solution that could help me.

UPDATE: I've used the lineage recovery to sideload kirisakura kernel and twrp. I can now use the touch screen inside twrp.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Mattski:
Got the same issue as well on my PixelExperience, does installing this test build fix it?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] _Axios_:
I can't say certainly about the fixing on the PixelEperience ROM, because I have LOS installed. But it seems to me that due to the fact that this issue is kernel related, the test build should help on any ROM.

Still using it and have no problems at all.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Slim2none4u:
Every time i try to install this kernel it reboots to the bootloader. Clean install of PE.

I have wiped and factory reset and flashed several times with the same outcome. Any idea what may be wrong with my setup? It can't be the kernel but i am a a loss.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dcarvil:
A few people, including me, with Magisk 25.1 have had that problem. One workaround is to revert to Magisk 24.3. No one has been able to get logs to indentify the problem. Most people with 25.1 do not have the problem.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
@Freak07 Hey bro the build is awesome... Everything 's running smooth... Mic issue is solved... But I still think that earpiece volume is a bit on the lower side... I'm still using kernel adiuter app for sound bump for earpiece as I need to connect ear buds for hearing other people's voice... Other than that... It's great work mate... Applause 🥂
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] entux:
Hi,

I've recently updated my Lineage-19.1 installation via OTA-Update and reflashed the S_5.1.1 version. Since the reflash other people can barely hear me. I have to almost scream into the microphone. Any idea why that might be? Shouldn't exactly this problem be fixed with this version?

Is there any way to change the recording volume of the microphone?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
glad to hear it´s working fine. There shouldn´t be a difference to how it is on stock.

Could there be some dust/dirt in the earpiece? The pixel 3 devices have quite an age now, so that could be a factor.

That´s the wrong build. 5.1.2 has the fix for the volume:

Check this post:

https://xdaforums.com/t/kernel-10-0...ixel-3-xl-aka-bluecross.3864563/post-87114567
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] entux:
Ah... thanks. I thought I would find the latest version on androidfilehost.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
You're correct, usually it's on afh if i do a release with a release post and all that, but i put this just out as a test until I find to update the thread properly since I wanted to get that hotfix out as fast as possible for everyone :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
@Freak07

Maybe... But I don't think that's the possibility bcoz

1. My phone is just 3 months old...

2. The voice after tweaking with kernel adiuter becomes like how it was before...

Maybe it's just me... Lol
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nldxda:
EDIT: I flashed the stock kernel and went riding and lo and behold, even on stock this app "paused" itself less than halfway thru the ride.. so it isn't only on kirisakura kernel this problem occurs.. it's a new problem as of a couple weeks ago and I've been using this app for years, so don't know what the problem is..

Original Post:

I use 4 cycling apps while out riding but using this kernel, one particular app seems to stop working. I suppose it falls out of RAM.

The 4 apps are: Strava, Google fit, mapmyride, and Ride with gps. It's ride with GPS that continuously pauses the ride and it ends up not recording half or more of the ride. This behavior doesn't occur using stock kernel.

Is there a setting I could change using a kernel manager app that could fix this?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] entux:
as a side note... the installer still says 5.1.1.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Maybe try removing it from background optimization?

Thanks 👍
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nldxda:
Ah ha! Just changed the setting, will see how it goes later today next ride.. thanks 👍

EDIT: so after removing battery optimization, it did work today without problem.. hopefully it'll keep working, 👍

EDIT 2: Doh! It paused mid-ride again, even with battery optimization turned off 😐.. don't know what to do now.. I hope I don't have to roll back to Android 11 just for this..
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
@Freak07

I'm not sure you can assist with this issue. As you are aware our Pixel 3XLs will have much more limited use as the next few months roll on due to the necessity of VOLTE and VOLTE roaming. This was the main impetus for Google releasing a new 12 update for the phone last month.

I had not been using 12 prior to this, but because I wanted to ensure call functionality I decided to take the jump to 12. I do not know if you have run into the issue with the Phantom Process Killer killing apps. It is detailed in depth here:

Android Phantom, Cached And Empty Processes

Android Phantom, Cached And Empty Processes. GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

and a public issue on google's tracker here:

Google Issue Tracker

issuetracker.google.com

A more cursory overview is available here:

Android 12's new background app limitations could be a major headache for power users

Android 12's new background app limitations could be a major headache for power users that use apps like Termux and maybe even Tasker.

www.xda-developers.com

I can't say that my knowledge is enough to add anything more or even to fully grasp every detail discussed in the above threads. Suffice it to say Android 12 breaks a lot of functionality that power users were used to. For me that is most definitely Tasker which seems to die randomly - most usually overnight and take manually kickstarting it back into gear.

I am not sure which components of these changes are part of the Kernel in 12 or just part of overlying OS. The best workaround that has been proposed so far is to increase the thread count allowed for the process killer with the following:

adb shell "/system/bin/device_config put activity_manager max_phantom_processes 2147483647"

This isn't an ideal solution because it apparently doesn't help with the OS killing off apps taking (what it feels are) excessive CPU cycles. Apparently this setting can also be reverted by Google's config sync behavior (which I am still trying to fully understand).

What I am wondering is if it currently possible to enter some tuning parameter into your kernel to set this value on boot so that it does not need to be set manually and would not worry about reversion from other system processes to the default 32 value? I have never done any tuning manually to your kernel so don't know if this is something that is already possible using some type of kernel tuning application?

If not, is something like this even possible for you to implement in the kernel? If it is, would you consider it?

Thanks again.

UPDATE: Specifically it seems this is handled by ActivityManager and is specified in the code base here:

services/core/java/com/android/server/am/ActivityManagerConstants.java - platform/frameworks/base - Git at Google

As such, I do not think this is a kernel issue? But not sure if something can be set in the kernel that would override that.

Again, I am asking because this seems to be set at a low enough level that even manually changing it gets overridden in some cases and thought you might have some insight.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Seriousfreedom:
Phone resulted in a bootloop after flashing kernel tried to switch bootslots in recovery and am getting an error boot prepare message....

I'm am running android 12
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
Don't know if it will help you, but I upgraded to A12 finally a couple of weeks ago since they released the summer update.

I had nothing but trouble.

I found that apps closed more often (Maps on long trips), and had a bunch of problems with Tasker.

I think part of it is due to the issue of Phantom Processes being killed on 12. I wrote up some of my Tasker woes here.

In the end, I couldn't get Tasker to not crash and manually need restarting. I was also having a problem with my phone Mic and so as a last resort I did a full reload back to 11 (it worked, Mic is better....though I don't necessarily blame that on 12).

I had a lot of apps (500+) and these phones don't have a lot of working RAM. I think if you have lots of apps running at the same time (which many apps do in the background even if you don't realize) or if you have apps that need to continually run for a long time - you are going to have problems with 12.

I'm staying back on 11 until VoLTE issues force my hand. Too many things just didn't work for me.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
I have to agree that 4GB isn't enough RAM anymore. For my part, I don't remember whether Android 11 was much better than 12 or if it's just that applications keep getting sloppier with their memory usage.

I was looking forward to the Pixel 6a until I heard they crippled it with 6GB of RAM. I can't see upgrading to less than 8 at this point. The regular Pixel 6 is too big for my hands (and pockets). So I just learn to be patient while my apps reload.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
4GB wasn't enough when the 3XL was released. It really was an insult to sell us a $1K phone with 4GB of RAM.

I won't say that 11 is better than 12, but on the 3XL I think it certainly is (especially with the phantom process issues if you are a power user).

My 2 week experience with 12 was nothing but problem after problem and not a single new "feature" that I cared to have, especially at the sake of what was lost.

My 11 experience was getting a bit bogged down, but I think it was due to the # of apps I have installed and as you say apps getting sloppier. McDonalds or Walgreens has no reason to be doing anything on my phone unless I am actively using it.

I will be reinstalling some of these but keeping them frozen unless needed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
I'm using a kernel manager to up the ZRAM size to 3k and use zstd ZRAM compression. It takes a while to set up after a reboot (it has to disable the zram altogether first) and EXKM seems to lose the settings pretty often, but once it's finally set up it does seem to give me just a little more available RAM and fewer app restarts.

I've also tried SmartPack and Kernel Ardiutor. None of them can make the settings reliably after a reboot. I suspect they get killed themselves in the process of disabling the ZRAM. Any suggestions on how to patch the kernel or maybe an init.d or addon script that might be faster or more reliable?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Dima93:
Man, excuse my bad English, I'm from Colombia and I have a 3 XL. I have a doubt, it happens that my phone has a bad battery optimization, that's why I decided to install or well I want to install a kernel for that purpose. But the only thing I have been able to do is unlock the bootloader and I don't want to leave it as a brick. That is why my question is, having android 12, how can I install a kernel in a simple way?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Nikberchardt06687:
Bro, when are the kernel updates?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] CRCinAU:
I tried Kirisakura_Bluecross_S_5.1.1.zip with the latest Lineage 19.1 build on bluecross, and I can only boot into Fastboot / Recovery now.

Are there any plans for an update that works?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
There's 5.1.2 but I don't know if it'll fix your issue. I'm on a Pixel 3 (not XL) and haven't had that issue.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] CRCinAU:
I screwed up - I'm on blueline aka Pixel 3. Not crosshatch. I did find the 5.1.2 ZIP file - it doesn't look like it ever made it to Android File Host...

I'll have a bit of a play - but I can still get wireless fast charging to work on the Pixel 3 using the Lineage kernel via just increasing the voltage using Tasker - so that's the main feature I want access to...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
@Freak07 Any update on Kirisakura for Android 13 for Crosshatch ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ferdimage911:
Can you please link me to the 5.1.2 blueline kernel, thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] CRCinAU:
https://xdaforums.com/t/kernel-10-0...-aka-bluecross.3864563/page-162#post-87114567
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
@Freak07 Hey bro... Android 13 stable has been released with arrows os 13 for crosshatch... I'm using it bt the freezing persists fue to stock kerner... Really need ur updated kirisakura for 13...😐
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
Did you try editing the version number on the latest version so it'll flash on 13. There should be instructions somewhere in this thread. I did that to use the Android 12 kernel on Android 11. I don't think kernels after very Android version specific.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
Naah I didn't had any idea that we can actually do that😅
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
Is there any xda thread or youtube video that I can follow to change the android version number?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
Is this post enough for you? It's a pretty simple patch. You just need zip and a text editor.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
Actually I got the idea about how it will work... But I don't exactly know what to edit inside that file for flashing on A13... Can u provide some kind of details as what to edit and what to replace in it?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Unzip the kernel.zip, open anykernel.sh, search for this line:

supported.versions=

and put 13 instead of 12 there. Rezip and flash.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ashwin Kale:
Yes I did this same thing yesterday without changing anything else.

When I zipped it again and flashed through ex kernel manager, it gave me an error that the directories does not exist.

I don't exactly remember but I was in a hurry ao I quickly got back to Lineage 19.1 A12.

@Freak07 hey, r u stopping support for pixel 3 xl now?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rubnduardo:
I need this kernel for android 13 haha