yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Freak07:
Thanks for the donation. I really appreciate it! :)

Thanks to everyone for the kind words and the reports. I´m glad it works out well for you. :)

All good on my end.

Without logs there´s nothing I can do. If you get a random reboot get me the contents of sys/fs/pstore after the device boots back up as described in the FAQ.

Please make sure to not install any other mods, tweaks to ease any debugging on my end. I don´t have the time and motivation to do any debugging on xposed mods or other modifications that can crash the system. :)
[Google Pixel 6 Pro] digger16309:
I just had my first random reboot since updating to the latest. I do run other mods, including LSPosed. But I've also been fussing with USNF versions today.
[Google Pixel 6 Pro] direwolf1:
I've had a couple of reboots as well. Tried to grab a log...
[Google Pixel 6 Pro] w_tapper:
using lsposed with aospmods on this kernel, no reboots yet
[Google Pixel 6 Pro] dannejanne:
I also got a first random reboot just now on P6P after flashing the latest kernel update yesterday. Latest Crdroid (January's security update), only magisk no modules at all and clean flash from just yesterday.
[Google Pixel 6 Pro] Rachid.Ala:
I don't knowif it's just a placebo, but battery life improved for me with this last build.

Thanks again 👍👍👍
[Google Pixel 6 Pro] djo_5296:
If anyone accidentally flashed my P6 Pro with v34 of platform-tools, and even after flashing (Feb) update properly with say v33 or smth and device ended up having "corrupt, cannot be trusted" message on boot, I just continued with the normal update and root process. So flash the magisk patched boot, then i opened FKM and flashed Kirisakura kernel 4.4.2 and the corrupt message disappeared. Didn't have to wipe my phone, thankfully
[Google Pixel 6 Pro] Jerreth:
just got another reboot this one was right after a power up.
[Google Pixel 6 Pro] Freak07:
thanks for the log, that might prove helpful.

A couple of questions:

Do you use any magisk modules, xposed (lsposed) or modules there?

Do you use any apps, tweaks or scripts that alter kernel settings? Like disabling ZRAM, playing with memory settings etc?

edit: I also found something else that might interest you in your log, not related to the reboot.

The app called air.com.vudu.air.DownloaderTablet causes a lot of selinux denials. The apps tries to access a lot of internal stuff that´s selinux restricted.

To me it also seems the app tries to read (maybe change) the selinux state of your device, which is worrying.

[ 96.269929][ T478] type=1400 audit(1676388606.969:1933): avc: denied { read } for comm="LE-2" name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app_30:s0:c11,c257,c512,c768 tcontext=u:object_r:selinuxfs:s0 tclass=file permissive=0 app=air.com.vudu.air.DownloaderTablet

Another example:

[ 102.306015][ T478] type=1400 audit(1676388613.005:1938): avc: denied { read } for comm="pool-27-thread-" name="u:object_r:serialno_prop:s0" dev="tmpfs" ino=282 scontext=u:r:untrusted_app_30:s0:c11,c257,c512,c768 tcontext=u:object_r:serialno_prop:s0 tclass=file permissive=0 app=air.com.vudu.air.DownloaderTablet
[ 102.306937][ T478] type=1400 audit(1676388613.005:1939): avc: denied { read } for comm="pool-27-thread-" name="u:object_r:serialno_prop:s0" dev="tmpfs" ino=282 scontext=u:r:untrusted_app_30:s0:c11,c257,c512,c768 tcontext=u:object_r:serialno_prop:s0 tclass=file permissive=0 app=air.com.vudu.air.DownloaderTablet
[ 102.307282][ T478] type=1400 audit(1676388613.005:1940): avc: denied { read } for comm="pool-27-thread-" name="u:object_r:firstboot_prop:s0" dev="tmpfs" ino=202 scontext=u:r:untrusted_app_30:s0:c11,c257,c512,c768 tcontext=u:object_r:firstboot_prop:s0 tclass=file permissive=0 app=air.com.vudu.air.DownloaderTablet
[Google Pixel 6 Pro] Jerreth:
so thats the Vudu app for purchasing and viewing movies and such other than that its stock OS no mods except for your kernel. if the Vudu app is doing all that ill drop it but ive never heard of it doing that before now.
[Google Pixel 6 Pro] Freak07:
No I can see the reboot and the kernel panicking in the log. It´s a memory allocation failure, but googles ZRAM eh implementation is involved during that.

That´s why I asked if you run anything that could modify this, as I can´t reproduce that issue on my end.

I´ll look into this though. I might already have an idea.

If you run into another reboot, please don´t hesitate to share the logs, it might help me. :)

About the app I was mentioning. Selinux is like the last barrier and arguably androids strongest defence against attacks. If an app or something else tries to access parts of the system that are completely blocked, like selinux status itself, reading serial number, grant themselves higher privileges those selinux denials will get printed in the log.

I just wanted to make you aware that this behaviour of the app is a bit suspicious as it shouldn´t have any reason to do this.
[Google Pixel 6 Pro] Jerreth:
i agree with that statement about that app having no business doing this. and i really appreciate all your hard work :) if i get another reboot ill post for sure.
[Google Pixel 6 Pro] snake218:
I had 3 random reboots with latest kernel, if I'm not wrong, happened when launching/changing to chrome browser.
[Google Pixel 6 Pro] -Happy Feet-:
Can i flash this Kernel on Bliss ROM, which ist AOSP based?
[Google Pixel 6 Pro] w_tapper:
I can do it in derpfest, which is made by the same person
[Google Pixel 6 Pro] -Happy Feet-:
Have you flash it with Fastboot or Kernelmanager?
[Google Pixel 6 Pro] w_tapper:
I used EXKM
[Google Pixel 6 Pro] -Happy Feet-:
I try it. Thanks.
[Google Pixel 6 Pro] -Happy Feet-:
Got an Error
[Google Pixel 6 Pro] w_tapper:
weird, it worked fine for me on derpfest, idk tbh
[Google Pixel 6 Pro] -Happy Feet-:
Maybe because of the active Slot.
[Google Pixel 6 Pro] w_tapper:
ehh idk, maybe use kernel flasher but some good news is that the kernel works on evo x
[Google Pixel 6 Pro] chewy74:
Did you flash stebomurkn420 derpfest?
[Google Pixel 6 Pro] w_tapper:
yeah
[Google Pixel 6 Pro] -Happy Feet-:
Is this ROM also AOSP based?
[Google Pixel 6 Pro] Prince_of_Hell:
im haivng a issue, flashed the kernel on evolution x and now it constantly reboots to fastboot mode.
[Google Pixel 6 Pro] -Happy Feet-:
I would restore the Evolution boot.img
[Google Pixel 6 Pro] Prince_of_Hell:
i just did that i think, the vendor_boot and now it just boots to the google screen over and over and i cant access recovery now about the only thing i can access is fastboot
[Google Pixel 6 Pro] jlokos:
I had the same issue. I had to start over with a clean install.
[Google Pixel 6 Pro] -Happy Feet-:
Maybe dirty flash of this ROM. Without wipe data?
[Google Pixel 6 Pro] Prince_of_Hell:
i was able to fix it by using google android flash tool, im gonna see if i can flash evo and then flex the kernel again using the way somebody just used
[Google Pixel 6 Pro] w_tapper:
same issue, me getting this kernel working on evo x was a fluke
[Google Pixel 6 Pro] Nezorflame:
Hey @Freak07, great stuff as usual 💪

Am I correct to assume that the QPR betas are not supported and we're on our own if we decide to use the kernel on them?
[Google Pixel 6 Pro] Freak07:
Custom roms are hit and miss, because some seem to do some weird stuff that´s deviating from the stock firmware. That's why there's no support from my side, as I simply don´t have the time to flash custom roms just to test that out. If there´s interest somebody else has to jump in and fix whatever issue is occurring. If the fix is simple enough and doesn´t impact compatability with the existing kernel.zip for the stock firmware I´m glad to accept any proposal or fix. :)

In this case it seems super partition has none or too less space left so it can be resized to flash vendor_dlkm on the fly while the device is booted.

You can try to repack the custom roms´s boot.img with the zImage found in my kernel.zip, flash the other images (dtbo and vendor_boot) manually in fastboot (vendor_dlkm in fastbootd, there super should get resized properly).

Afterwards you can try to flash the kernel.zip via app and see if the flash went through.

I think some others also shared steps previously, so if you want to search the thread, feel free to do so.

You can also ask the rom maintainer to look into it, but I can understand if they don´t like to add support for 3rd party kernels either.

correct, only stable stock firmware. no time and motivation from my side to support beta firmware.
[Google Pixel 6 Pro] Freak07:
so it seems there were no further reports about crashes after I asked for logs, without any modifications (magisk modules, root tweaks, lsposed, lsposed mods etc) added to the phone. I suspect that either nobody wants to run without modifications or no crashes happened without mods, except the one I already saw a log for.

I still haven´t experienced a single crash on my side yet, so I´d appreciate more logs so I´m at least able to work on potential issues.
[Google Pixel 6 Pro] Freak07:
thanks, I missed that before.

I can see the problem. Should be adressed in the next release.
[Google Pixel 6 Pro] kpirnie:
I have to be doing something wrong. I have 1080 set for the display resolution, but every time I reboot it reverts back to 1440

I have 1 module in Magisk, the A3 module from installing the kernel, I'm also on stock February (raven)... is there something else I'm missing to presist the screen resolution?

Maybe there's something in build.prop (or system.prop) I could toss in a magisk module to keep it there... anything...
[Google Pixel 6 Pro] Rachid.Ala:
6 pro with kirisakura kernel is affected by this weird bug

https://www.reddit.com/r/GooglePixel/comments/11byf50
[Google Pixel 6 Pro] w_tapper:
lmao I came across that same post today, my 6 pro with kirisakura and lineage 20 is affected by this too

my youtube revanced app even got deleted
[Google Pixel 6 Pro] Freak07:
I saw it too. Seems it’s fixed on the qpr beta though. So it might be fixed in a few days when march update drops. :)

I’m not sure it’s related to kernel anyway. It’s also not a hard but a soft reboot.
[Google Pixel 6 Pro] w_tapper:
do you have any idea as to why my YouTube app may have also been deleted?
[Google Pixel 6 Pro] Rachid.Ala:
Maybe a logcat would help but it would be a huge off-topic. The most appropriate place for this would be the revanced thread.
[Google Pixel 6 Pro] Freak07:
not really :)

Were you using Youtube vanced and a corresponding magisk module? I suppose the hot reboot might kill the overlay somehow.

But as stated here, it’s not really kernel related so I guess we won’t be able to fix it anyway if its some firmware/framework related issue. :)

For losing the app, if it’s indeed vanced you’re using a logcat in that thread or on github might be the best way. :)
[Google Pixel 6 Pro] w_tapper:
Yeah I was using revanced which might have something to do with it
[Google Pixel 6 Pro] fillwithjoy1:
Dumb question but which file do I use to install it onto? My Pixel 6 Pro also doesn't enable 50 megapixel full photos and 8k30fps recording
[Google Pixel 6 Pro] w_tapper:
Use a kernel flasher such as the kernel flasher app on GitHub
[Google Pixel 6 Pro] 24ky:
@Freak07 any plans to add support for 6a ( bluejay ) ? Is it possible to merge bluejay into your kernel source? If so I'm willing to full on test it before you do make it official. Can pull kernel logs , crash logs etc.
[Google Pixel 6 Pro] Flyview:
Is there any way to manually tune thermal-hal and power-hal? Like back in the good old days where there was a thermal_engine.conf file? How is the CleanSlate config app controlling frequencies? I'd really like to play with the thermal thresholds if possible.
[Google Pixel 6 Pro] Freak07:
The power-hal is already tuned for this kernel. It's part of the magisk module that gets installed while flashing.

I recommend leaving the power-hal unchanged while running my kernel, otherwise a lot of things can break.

The freq limits from Cleanslate power saver are built in at compile time, that's why they can work as hard limits if set via Cleanslate config app. The Cleanslate app itself does nothing, it just switches on the feature that's already built into the kernel, when I compile it.

The default interface of max cpufreq nodes that regular kernel managers access (which is part of "every" kernel) just get overwritten.

Check here:

cpufreq: add cleanslate battery optimizer feature · freak07/Kirisakura_Raviole@5cb2233

(cherry picked from commit dcd935c40c0dcdddd73ff0d4176ae3d21ad91468) (cherry picked from commit f192bb2c928f653baf75a5152dc0be60cef6f4e3)

github.com

The limits from Cleanslate battery saver are specifically tuned for this kernel, so they work in combination with how i set up the pmu limiting feature in the power-hal. Check here.

If you change anything in the power-hal you might break a lot of stuff, that's why I recommend leaving it alone.

You also won't be able to change max frequencies directly in the power-hal, as there are different actions based on scenarios that constantly overwrite the values.

Same goes for thermal hal, but different reasons. It's possible to change thermal thresholds. But this can damage the device and I'm pretty sure it will over time.

Relaxing the thresholds can damage the battery, the camera sensors, the panel and other internal components as well.

Google uses a pretty "advanced" system of combining several virtual sensors, that are combinations of actual sensors into different virtual temp categories (e.g. skin, CPU skin, charging etc) and use different mechanisms of throttling.
[Google Pixel 6 Pro] jamescable:
It would be nice to be able to force under locking again tho to keep temps down, sometimes phone feels so hot can't use it
[Google Pixel 6 Pro] Freak07:
That's precisely what the Cleanslate battery saver does.

It allows you to restrict cpufreqs to three different predefined levels/freqs for each respective cluster.

Switch to enabled in the app, set the level you want and hit the save button.
[Google Pixel 6 Pro] jamescable:
Is this the app? Will it work with your kernel?
[Google Pixel 6 Pro] Freak07:
Yes, you can also find free version to try in the Cleanslate thread here on XDA. (ad supported)
[Google Pixel 6 Pro] Flyview:
Yes, I understand. I have been using the CleanSlate battery saver to keep temps down myself. I was just curious where all the logic is for the thermal throttling that is based on the various sensors. I'd love to take a look at it myself. I'm not necessarily looking to just increase the limits. I want to understand it more.

As a side note, I find that a lot of heat is actually produced from the modem (even on LTE) as I'm often on the road and don't have WiFi. If you start transferring large files the phone quickly heats up.
[Google Pixel 6 Pro] fillwithjoy1:
Which file do I download? The multi_touch one or the magisk.zip? (Have Magisk and FKM)

13 (TQ1A.230105.002) (I'm sorry if I sound stupid)
[Google Pixel 6 Pro] rayraycarter4:
How exactly did you get this to work with bliss rom I'm on 16.4 bliss and i did what you did and ended up in a fastboot bootloop ... Could you pm me with help
[Google Pixel 6 Pro] Roll3r:
Can someone take a look at the attached logs and see why my phone's been shutting off randomly? It started after installing the Feb update and 4.4.2. I don't necessarily think it's the kernel, but want to rule it out. Thanks!
[Google Pixel 6 Pro] Freak07:
Yes, cpu is only one source of heat.

As you already pointed out modem is another one, just like the camera array itself will produce heat while using it (especially noticeable while taking videos, which presents two issues, if cpu is throttled to much hi-res video might produce stutter, if heat is not kept in check camera sensors might get damaged).

If you want to take a look at the thermal throttling you can find this on the device tree. This one is for p6 pro (raven).

Release for January firmware is attached to the release post for january, you can find those in the OP.

Thanks a lot for taking the time and actually posting logs!

That issue is the same I replied to in this post and will be fixed on the next release.
[Google Pixel 6 Pro] Roll3r:
Fantastic! Thanks
[Google Pixel 6 Pro] fillwithjoy1:
Hey I'm wondering what's the charging switch setting to enable battery idle mode (A13.TQ1A). I know that the Pixel itself natively supports it because after 3 days of continuous charging the phone completely stops charging and enables battery idle mode by itself.
[Google Pixel 6 Pro] zosina:
Install acc v2022.7.30-dev by VR25 and test the switches with acc -t in a terminal app.
[Google Pixel 6 Pro] fillwithjoy1:
Apparently FKM says that the kernel doesn't support high brightness mode
[Google Pixel 6 Pro] w_tapper:
works fine on exkm
[Google Pixel 6 Pro] Roll3r:
The correct one isn't listed in ACC, so you need to enter it manually. Instructions are in my post here:

https://xdaforums.com/t/kernel-09-0...pixel-6-pro-aka-raviole.4358435/post-86404619
[Google Pixel 6 Pro] fillwithjoy1:
Is there a script I can import to enable high brightness mode then?
[Google Pixel 6 Pro] w_tapper:
tbh idk it just works
[Google Pixel 6 Pro] rhetorician:
Yes--this is frustrating, I admit. I really do regret buying FKM app. Let us now if you figure out how to enable.
[Google Pixel 6 Pro] jamescable:
FKM is a couple of years outdated, yes some people say they can still flash kernels with it but no one should be buying it and giving Dev money for a dead app
[Google Pixel 6 Pro] BarackMitzvah:
Anyone confirm if the previous kernel is good to use on the March update?

Edit: I'm an idiot, March update is late apparently
[Google Pixel 6 Pro] Lughnasadh:
The March update hasn't even been released yet.
[Google Pixel 6 Pro] BarackMitzvah:
Haha WOW

I don't usually even look until after this kernel gets updated

My bad! I guess I assumed it came out on its normal schedule 😆
[Google Pixel 6 Pro] Rachid.Ala:
I miss flashing a new version of Kirisakura more than the March google update 😂
[Google Pixel 6 Pro] ctfTijG:
And the March update is here! 😄
[Google Pixel 6 Pro] Jerreth:
did you get it OTA? i am not seeing it listed for anything other than the 7 series pixels
[Google Pixel 6 Pro] Admiral2145:
It seems like they are having some issues again, as a Google Support person has told on the chat that the March 2023 update for the Pixel 6 series devices will come on the 20th of March 2023
[Google Pixel 6 Pro] fillwithjoy1:
Oh c'mon
[Google Pixel 6 Pro] fillwithjoy1:
Yeah... I do wish that I knew earlier about that....
[Google Pixel 6 Pro] Justarandomguy:
Can't wait for an update, I'm really enjoying this kernel, unlocking bootloader, flashing a/b and going back to stable was worth, battery life is better, performance is better, smoothness is better... Will do flashing speedrun when a new release comes <3
[Google Pixel 6 Pro] jamescable:
@Freak07 any chance you can include features from your 7 pro kernel?
[Google Pixel 6 Pro] BarackMitzvah:
Well this is terrifying. Think we will see a fix via security update and/or this kernel?

Multiple Internet to Baseband Remote Code Execution Vulnerabilities in Exynos Modems

Posted by Tim Willis, Project Zero In late 2022 and early 2023, Project Zero reported eighteen 0-day vulnerabilities in Exynos Modems...

googleprojectzero.blogspot.com
[Google Pixel 6 Pro] Admiral2145:
I believe it's fixed in the March update and if you turn off your wifi calling and volts... It won't. work
[Google Pixel 6 Pro] Freak07:
Features like which exactly? Did you read the first post and compared the kernel features? :)

All of those features are included, except some from tensor 2 that rely on updated vendor firmware or hardware.
[Google Pixel 6 Pro] w_tapper:
can you add face unlock via kernel or is that rom based?
[Google Pixel 6 Pro] Freak07:
rom based
[Google Pixel 6 Pro] jamescable:
...oh 😂, silly me lol. Any chance for KCAL or vibration control?
[Google Pixel 6 Pro] Freak07:
Vibration control is available already and accessible via Cleanslate config app.

Kcal is QCOM specific. There's no similar interface to tap into the display on the Samsung/google driver.

Check out the app cf lumen from chainfire. It's available on XDA and is superior to a kernel implementation in a few days, because the kernel can't know location for example. :)

E.g. location or time based switching is possible that way.
[Google Pixel 6 Pro] Rachid.Ala:
March update is finally released.

I'll wait for Kirisakura to be released first before flashing
[Google Pixel 6 Pro] Admiral2145:
I'm on January build with February kernel... Can I just flash the March Ota and go foward?
[Google Pixel 6 Pro] ada12:
I recommand you to use Always kernel of same month stock rom for avoid issues ( and use Always latest stock for security )

If you install march rom wait march kirisakura before flash kernel ...
[Google Pixel 6 Pro] JasDevi:
Damn waiting so eagerly for @Freak07 to update to march!
[Google Pixel 6 Pro] digger16309:
You folks know you can update your devices and run the stock kernel for a few days, right? ;)
[Google Pixel 6 Pro] Freak07:
I’m planning to release the next update later today.

I’ll drop this little screenshot as a hint. Maybe someone can make a guess based on the screenshot regarding one of the bigger changes.

Stay tuned, this will be a very very nice update :)
[Google Pixel 6 Pro] Rachid.Ala:
Sounds like a downgrade to me
[Google Pixel 6 Pro] Utini:
I heard your account on xda will be immediately terminate itself when you run stock for more than 24h.

Raviantah :o
[Google Pixel 6 Pro] Rachid.Ala:
Unified kernel 6 / 6 pro / 7 / 7 pro ? 👏👏
[Google Pixel 6 Pro] StanWiz:
Freak07 - Will the new kernel be the same for both releases (E1 - F1) ?

Thanks
[Google Pixel 6 Pro] JasDevi:
O

Omg omg! It's coming!
[Google Pixel 6 Pro] w_tapper:
uh oh
[Google Pixel 6 Pro] TheColin21:
Just flashed it, great update
[Google Pixel 6 Pro] Rachid.Ala:
Thank you 👏👏👏
[Google Pixel 6 Pro] Freak07:
Yes, only carrier related files are different. Kernel is the same. :)
[Google Pixel 6 Pro] dyval:
Thanks for the update!👌🏻
[Google Pixel 6 Pro] w_tapper:
looks cool, will flash when Evo X gets an update to march
[Google Pixel 6 Pro] Nothex:
I'm curious: Why is your Cid red? I have not seen that guy for nearly 10 years...
[Google Pixel 6 Pro] Nothex:
Ravioli Ravioli give me the Formuoli 🦀🍝🤖
[Google Pixel 6 Pro] dyval:
That's the OG of custom roms man!😉
[Google Pixel 6 Pro] Nothex:
I know! I had hassium as my alarm tone until recently. But why is yours red? He looks evil!
[Google Pixel 6 Pro] digger16309:
Random reboot several hours after update to latest kernel when using Chrome.

Edit - log attached.
[Google Pixel 6 Pro] w_tapper:
my old galaxy note 10.1 was running cm13 until last week... not enough apps work on android 6 to make it practical
[Google Pixel 6 Pro] dyval:
I'm a fan of black and red combo bro.😁
[Google Pixel 6 Pro] Freak07:
Zip it up or upload it to GDrive etc. Alternatively resort to the browser on the phone.

I'd like to take a look at the log.
[Google Pixel 6 Pro] digger16309:
I edited my post to add the log. I think I pulled the right files based on past instructions. And, I know you'd rather not have LSPosed involvement, but it is what it is.
[Google Pixel 6 Pro] Lycidias:
Awesome Update!!! Highly appreciated 🥰
[Google Pixel 6 Pro] AlDollaz:
Smooth as butter. Thanks for the update!
[Google Pixel 6 Pro] spida_singh:
@Freak07 - Updated to latest Lineage (which i believe contains the latest March 23 update) on my Pixel 6:-

LineageOS Downloads

download.lineageos.org

But receive the following error when flashing (im flashing for the first time and currently have stock LineageOS Kernal installed which is pre rooted using Magisk 'delta':-

Releases · HuskyDG/magisk-files

Contribute to HuskyDG/magisk-files development by creating an account on GitHub.

github.com

Kernel Flasher just exits when i attempt to begin flashing this Kernel
[Google Pixel 6 Pro] jamescable:
What kernel manager?
[Google Pixel 6 Pro] BarackMitzvah:
This month's release feel fabulous. As always thank you for your work!
[Google Pixel 6 Pro] DanielF50:
Awesome update!

Spoiler content hidden.
[Google Pixel 6 Pro] Freak07:
I´m having no problems using the sliders on the version of the camera app you´re describing. (8.8.224....)