yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
I disagree that a fresh start is required after flashing stock updates in place. I did do a full reset when moving from 10 to 11 though and still had the freeze issues on November update. I will also be doing a full reset again as I currently am on 10 and while it shouldn't be required I do prefer to do a full between major revisions.

I never once had an issue on monthly updates doing in place (without wipe) from stock image monthly releases....or at least never an issue that wasn't of my own making :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
Was wondering if you have tried fastboot without "-w" flag? I've been doing that every month, and never have any issue. I know it is time-consuming, but the benefit of restoring any file corruption outweighs 20 minutes (maybe less if you have a faster Internet bandwidth) of my time.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ssdd28561:
Franko Kernel Manager 6.1.1 update fixed their problem with flashing kernels on android 11, so that's nice
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] stifmaster81:
quéhow about this kernel for android 11 stock? improves battery?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] People11:
Maybe remove unnecessary CPUFREQ like Sultan does?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zalazdev:
Man, IT WAS FASTER THAN I THOUGHT!

Also, I did not have ANY PROBLEM.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
Jan patch is out. I am going to test it.

------

edited: I installed Jan patch, root it with magisk then apply r3.0.3 and things are so far so good. without the kernel, magisk will cause phone to freeze up.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 3.0.4_R

Hey guys and girls,

I wish everybody a Happy New Year! Let´s make the best of this year!

The OP was restored after talking to the XDA admins, so it seems we´re back in order. This update contains the January Security Update as well as Linux-Stable Upstream.

Make sure to be on January Firmware for this release.

Other changes please check the changelog and/or github.

I wish everybody a great day.

Enjoy the device and the kernel, because I certainly do

Just in case:

If you face issues or bugs when running the kernel, please return to a stock environment, only your rom plus magisk root, without any modules, scripts, tweaks or mods and see if you can reproduce the issue.

Tell me the exact steps needed to reproduce.

Then send me a dmesg and a logcat (if the kernel crashes not) or a ramoops (in case the device reboots). Take a look at the second post for a guide on how to obtain these.

My kernel.zip flashes both boot.img and dtbo.img. So if you want to return to stock, you need to extract both from factory image and flash them via fastboot if on stock rom.

If you’re on a custom rom you will need to dirty flash your custom rom or learn how to extract both images from a payload.bin

Special thanks to @jcmm11 and @melgar for testing and keeping up with me!

I wish everybody a nice day/evening! :)

Enjoy the device and the kernel, because I certainly do

Changelog:

- Merge January Security Patch

- Linux Upstream to 4.9.249

- bump wireguard

- other changes look at github

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?

Download is below :)

Download:

Kirisakura_Bluecross_R_3.0.4.zip | by Freak07 for Generic Device/Other

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

or following the link in the op to the correction version

How to flash the Kernel:

1. Make sure you are rooted, are using the latest magisk suited for your OS version and a kernel manager capable of flashing a zip is installed. If available you'll can use TWRP as well. Download the kernel.zip to your device.

2. Flash kernel zip in via your favorite method. Kernel Managers and Recoveries need to be updated to work with a specific Android Version. It's your job to ensure compatibility! :) Root will be preserved! (Make sure to be on the latest firmware the kernel is made for)

3. Reboot and profit! Before reporting any issues make sure to read the first three posts of this thread!

Instructions can be found in the OP 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/green tea: http://paypal.me/freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
@Freak07

Happy New Year, my friend! You are one of many awesome reasons that I am still with my dear phone.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] pahlerc1:
Thanks for the January 2021 Security Patch Update! Appreciate the work! I still believe the 3XL is the best Pixel phone still to date! Not like the ole Nexus days, but still nice to be pure Android! I believe this will be our last year of monthly updates from Google
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] billyt1:
Yeah i used the flash tool for Jan update. Without a wipe. Running just fine.

Fresh Start means manually flashing yourself with flash-all.bat

All im saying is if you took a update without wiping data in the process and your having issues.

Step One is the device powered on.

Step Two is fastboot -w or a Fresh Flash.

Because have you ever talked to google support.

Even if its a bigger issue like none of your sensors working.

All I can say bout them issues you know.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] billyt1:
Yea Lineage or Dirty starting to look pretty decent to me.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] stifmaster81:
Why can you never set the minimum frequency? I choose 300mhz and stays at 600mgz anyway
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Admiral2145:
I'm currently on Nov 2020 stock with magisk 21.2...can I flash this kernel... Does it help stock roms? I've only had my p3xl for barley 2 months.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
As the Op said in his post, You had to be in the Jan 2021 stock to use the 3.0.4_R, find the right version for your current rom.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Admiral2145:
Are there any thing I should change after flash... Or is the default flash ok?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 5.1:
Hi,

You can use ExKernel Manager or Franco Kernel manager to customize stuff. Check it out 👍

Cheers...

Sébastien.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Admiral2145:
Is there a post that shows recommended settings is what im asking.. Looking on the 1st few pages I saw nothing.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
all the default setting is already setup after you flashed the kernel. Not much to change.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] newkydawg:
You might want to increase Swappiness to 150 or 175 (max I believe) under ZRAM/Memory settings and under Gestures, enable/disable these to your liking. You will need a kernel manager like EXKM or FKM to make these changes
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Admiral2145:
Thx I flashed it with ex kernel manager
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] stifmaster81:
[QUOTE = "stifmaster81, publicación: 84246483, miembro: 5147237"]

¿Por qué nunca puede establecer la frecuencia mínima? Elijo 300 mhz y me quedo en 600 mgz de todos modos

[/CITAR]

unany solution ? does anyone listen to me?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Slim2none4u:
English please
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] stifmaster81:
147237 "] Why can you never set the minimum frequency? I choose 300mhz and stay at 600mgz anyway
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
the powerhal changes this tunable each time you touch the screen. that means it boosts this tunable to 1,1ghz when you touch the screen and sets it to 600mhz once the timer expired. it will just overwrite your setting, like you noticed.

there´s no benefit in setting the frequency lower than 600mhz on modern qcom socs.just leave frequencies as they are.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] godzulu:
Deleted
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Admiral2145:
I'm new to the p3xl... I'm on Nov 2020 stock rooted fw with this kernel... Is there a way to update to Jan 2021 and keep root and not have to flash via adb ect?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] trabadura:
Reboot several times with the last update from January with Kirisakura_R 3.0.4+ Tue Dec 8.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 2Wires:
I installed 3.0.4 on my Pixel 3 XL with January patch and systemless hosts from Magisk. It froze after a few days. I thought it has the f2fs patch?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jlokos:
I installed 3.04 on my wife's phone with systemless hosts, and she has had no issues. It maybe something else.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] trabadura:
Today again restarted several times on an incoming call.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Please take a look at post #2 and #3 for how to report bugs. Remove all mods, magisk modules and provide logs.

It seems nobody else is facing it, so without logs it could be anything.

You're free to check the changelogs and GitHub to see for yourself. :)

Yes it's included so you're probably facing another issue.

Please take a look at post #2 and #3 for how to report bugs. Remove all mods, magisk modules and provide logs.

My pixel 3 XL is running without a single reboot since I flashed the January release of my kernel. magisk and systemless hosts are in use as well.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] trabadura:
After uninstalling the module that I installed from Magisk today I do not have a single freeze or restart. Thanks to Freak07.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
so far the Jan update with using 3.0.4 is very good for me, in fact I think the battery is extremely good, my uptime in between charge is like almost two day now. Very good. Thanks for the very nice kernel.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
@Freak07 here is a coffee for you. Transaction ID: 20495231959261856
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
Just want to update that I upgraded clean to 11 January release about a week ago. Ran fine with just Magisk root for about 2 days. Installed ACC module and continued to run fine another day. Enabled System-less Hosts and within 3 days had at least 3 lock-ups. After the third I went ahead and updated to the latest Kiri kernel and have been running without issue for 4 days.

Battery life seems worse than 10 on both stock and kiri kernel. Everything else is copasetic.

Thanks again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Xeust:
Hi. I have recently experienced a rather weird problem. I couldn't turn off zram, change zram size or zram compression. With that I attach the logcat and dmseg I pulled from ex kernel app in case necessary for your inspection.

I can't seem to upload directly for some reason so I uploaded them to mediafire. I recreated the error somewhere in between 23:12:00 until 23:14:00.

Pixel 3 on the latest build and latest Kirisakura_R 3.0.4

logcat : https://www.mediafire.com/file/ybx4a80ou1ub8h2/logcat.txt/file

dmseg: https://www.mediafire.com/file/hmayq3b5xik3fhr/dmesg.txt/file

Edit: Problem persist even after a full wipe. I assume its related to thermal throttling?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
Hey @Freak07 - I just noticed that john closed https://github.com/topjohnwu/Magisk/issues/3171 as wontfix.

Do you have any insight there? I mean technically the issue is not with Magisk, but with module - is that correct?

So either we have to be running a custom kernel which has fixed the issue (like yours), or the module maker needs to design their module better?

Which I don't totally understand because SH is built into MM.

Or is he saying it can't be fixed by Magisk at all and has to be built into the kernel because the issue is actually with the original code base?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
No the issue is in the f2fs driver in the stock kernel now. During the A11 update a commit from f2fs stable upstream got merged that doesn’t work well with magisk and causes a deadlock.

It’s not something that’s fixable on magisks side.

The issue can happen as soon as magisk is installed. Using a module makes it more likely to trigger the issue. The more modules you use the more likely the deadlock will get triggered.

So yes. For the time being you have to use a kernel that has the problematic commit/s reverted.

Arter and me are working on getting a fix merged to f2fs stable source and we hope to the pixel kernels.

This needs to be reviewed first of course. It’s difficult and takes time.

But we’re already in contact with the f2fs lead developer.

We hope we can get it fixed. No promises and it will take time.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
Got it. Thanks. Yeah I'm fine being patient since I'm totally happy just running your kernel and probably will continue to once it is fixed. I was just curious as to why it was closed without further comment - makes sense.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
There’s a comment at the top of the issue thread from topjohnwu as to why it’s closed :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
heh...yeah I saw that. But, I was pretty sure that this was said weeks ago - so I was more curious why it was closed now as opposed to then. But, no matter...thanks again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Anyoe:
same here, happened after flashing magisk v21.3.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Xeust:
I see. I'll try n downgrade the magisk version to reconfirm whether magisk is the cause.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
seems like a magisk issue indeed. It should be fixed in the next canary, just debugged it with topjohnwu :)

edit: update to canary 21304, this should have the issue fixed :)

aside from that I wouldn´t disable ZRAM since the userspace lmk somewhat expects it to be present.

you´ll probably save next to no battery by just disabling it on modern android devices in general (socs have become way more efficient than a few years ago), and probably do more harm than good by disabling it on pixels with userspace lmk.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Xeust:
Oh no I wasn't trying to disable the zram. I wanted to change the size and compression but it didn't seem to work so I thought I'd disable it first to see if it'll work. But thank you very much for the insight. I've updated magisk and it is all working now 👍🏼
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
It seems I misunderstood :)

Nice, to hear it’s back to working for you. Yes it was a problem with

su -c

that’s fixed now.

Revert to old `su -c` behavior · topjohnwu/Magisk@1f4c595

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

It was an issue that affected probably many root dependant apps.

I read your post yesterday evening and noticed another problem on my own this morning caused by this issue, so I had an idea what might be happening. so thanks for the post, also to @Anyoe and the hint to new magisk canary. I’m happy that it could be debugged so quickly :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
So I had a lock up today. To re-iterate - I was having lock-ups a couple month ago before the kernel magisk fix that caused me to revert back to 10. These lockup were more total lock-ups where the device because wholly unresponsive. Although they varied a bit, they usually happened directly after boot or directly after turning the screen on. In any event, I also experienced these error on 11 last week once I installed Magisk. As I mentioned in a previous post I was running fine for a few days, then had 3 lockups within 3 days of Magisk until I installed the latest Kiri kernel. I have been running fine for about a week with that.

Just now, I unlocked my phone and it because unresponsive for about a minute. Once it became responsive I was unable to open any apps...they would take 10 seconds or so to launch, but I would just get a white screen and the app never opens. Nova launcher seems responsive. I can open my app menu, pull down the notification shade, toggle between open apps to swipe them closed (thought technically they aren't "open", because they never properly launch). But going into an app or system settings won't work. Phone also appears to unlock properly with my fingerprint. This is the same type of lock-up I was getting last week in-between installing Magisk/SH and updating to the latest Kiri kernel. These lockups feel different than the ones I had a couple of months ago (they aren't as destabilizing, even though I was/am unable to actually use any apps).

I'm attaching a logcat here. I don't know if it can help. At the end (around 3:21pm) I tried to launch Chrome, then a minute later the Phone app, then after that Google Maps. All of them just launch to a white screen and sit there until I swipe out. Not sure even where to begin on this. I actually don't need my phone for a bit...so I am going to hold of restarting in case someone can give me an idea of what else to check/log over the next couple of hours.

thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Can you get me a dmesg? You should be able to get it via exkm in the logs section.

What kind of magisk modules/root apps do you have on your phone? Just magisk and systemless hosts?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
I can't launch any apps. I can get to adb shell, but don't think I can even "su".

I believe the only Magisk apps I currently have enabled are SH and ACC (battery) and Edge Sense Plus.

ESP has only been installed for a few days.

Let me know what I can do (if anything) to try to find culprit.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Do a reboot, after booting back up look in sys/fs/pstore, zip the content up and upload it here.

I'll look at it tomorrow morning :)

I'd remove esp and see if it happens again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
Here you go. I was able to issue a reboot via adb as the phone became even more unresponsive.

Curious re: ESP. Have you heard/seen issues with it? I had run it for over a year on 10 with no issues and had been using it for several days before I saw this lock up. For now, I'm going to keep with it until I see another lock or two. If so, I will go about disabling again for a while (it is partially unsupported now with the Dev handing off monthly updates to another and I have been able to recreate most of my necessary functions in tasker).

Let me know what else I can do to provide any info. Thanks.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
Yeah

Yeah. The device was sleeping...as in it was sitting on my desk I hadn't used it in a while. My daughter brought it over to me and when I turned it on is when the hanging began. It took too long to show the desktop and when I toggled the power button or pressed menu a few times I got back to the launcher, but couldn't launch anything as I mentioned. After a few minutes I brought it over and plugged it into the PC to launch adb and then everything else I mentioned (chrome, maps, etc).

I use quite a few root apps...like MiX Explorer, Backup programs (TiBu, Swift), AdAway, ACCA, AFWall+, EXKM, Termux, And Tasker and some of its associated plugins. Obviously some of those only run when I need them (Termux, Backups, MiX), but others are on all the time. Tasker monitors a bunch of things regarding the system, but right now I mainly have it enabled to issue some warning when low on power and go into battery save mode at my threshholds.

What specifically in those logs you pasted are you finding "suspicious" do you mean an app that looks nefarious? Apart from the tasker logs I'm not seeing much.

All I can say is that I ran with a pretty much identical configuration on 10 for well over a year and I never had any issues like these. I'm not saying it is an issue with your kernel, but maybe there is still something else with 11 that was introduced and might need a work around. As it stands I guess I can't do much but wait for it to happen again. If possible I will get a dmesg next time. If it becomes a regular occurrence I'll start eliminating modules again, but it is hard to tell if it happens only once a week. It is clearly better than it was before and if I need to reboot weekly to keep all the functionality I need, I guess that's the price I need to pay.

Thanks for taking a look.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
wow that´s quite a bit :)

mainly that similar lines to these all related to tasker

W ActivityManager: Foreground service started from background can not have location/camera/microphone access: service com.walmart.shop/com.joaomgcd.taskerm.plugin.ServiceRequestQuery

seem to pop up after you try to launch any app when you seem to have that issue. But maybe that´s just the nature of tasker or the setup you use and is "normal. Like I said rom side or tasker I´m no expert. :(

If you recreated missing functionality via tasker, from the discontinued ESP magisk module and this never happened before, this might be it.

Since there´s no easy way of reproducing the issue or a good definitive clue from the logs options are limited. Especially if the issue happens only once a week.

Could be anything. Could be a tiny change in linux-upstream in the kernel that conflicts with something, the branch the pixel OS is build on, did change in december and again in January on the pixel 3. (november "RP1A", december "RQ1A", January "RQ1D") Not to mention big changes from android 10 to android 11.

I guess there´s not much you can do beside waiting if it happens again, and when it happens try to remove maybe this new tasker/esp part.

the ramoops is fine if you can´t get a dmesg. It´s basically a dmesg that gets saved when you do a reboot to show what happened during the last session the device was up. Usually it just gets saved when the device crashes completely due to a kernel panic, but I changed this so it gets saved on normal user invoked reboots as well (to be able to debug situations like this, if the kernel is at fault :) ).

Sorry I´m not more help to this cause.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
No changes in the kernel source this month. You can flash 3.0.4 just fine on February.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DimyD7:
Hello!

First of all, thank you for the great work. The reviews about this kernel are amazing so I want to give it a try!

Right now I am on stock Android 11 (February security patch), but I do not want to root. Is it possible to install this kernel by flashing the .zip via TWRP.img? I really do not want to have problems with safetynet as I use GPay and banking apps a lot...

Sorry about this newbie question, I had flashed a lot of other smartphones but I am a bit more scared about the Pixel... Hope someone will help me, thank you!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
My safetynet is clear and GPay works. Is your bootloader unlocked? BTW, the OP states:

How to flash the Kernel:

1. Download the kernel.zip to your device. Make sure your device is

rooted properly

, with the magisk version suiting your current firmware version.