yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] DanielF50:
Hmm, interesting...

I'm in the UK & my build number is SQ1D.211205.016.A4, the only real differences should be radio related, but I wonder if this could make any difference.

edit: forgot to say, yes I did download the raven file. I might try a full wipe soon to see if I can fix this.
[Google Pixel 6 Pro] swieder711:
Downloaded 1.4 to my rooted P6P on the Dec release. Installed via FKM. No errors. Rebooted. No problems. Retained Root.

Well Done Freak!

QQ: I am now running the 1.4 Kernel and just updated the Magisk App to 23016. Now Magisk is telling me to update Magisk, currently reported as 23015. Do I need to reflash the stock kernel, apply the Magisk patch and flash the 1.6 package again?

Nevermind - I just updated Magisk via Direct install to 23016.
[Google Pixel 6 Pro] Utini:
Uhm for some reason I can't download the files?

The link goes to an overview of all folders but I can't click on any folder?

Edit:

Is this the correct one? Found via "most downloads by freak07":

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

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

androidfilehost.com
[Google Pixel 6 Pro] Lughnasadh:
Thank you so much for the early Christmas present 😀🎄🎅

Gotta say, this phone is snappy as all heck on this kernel update. Loving it! Kudos to you👍
[Google Pixel 6 Pro] Nekromantik:
@Freak07 So you dont recommend blocking the 2 wlan wakelocks?
[Google Pixel 6 Pro] joshnichols189:
Also unable to boot after flashing via FKM and have to end up doing a full dirty flash of the december update.
[Google Pixel 6 Pro] DanielF50:
Weird. I'm just about to do a factory reset to see if it helps, will update you on the flip-side 😅
[Google Pixel 6 Pro] joshnichols189:
I went from unlocked US build to "US Carriers" build just now and tried to flash again through FKM with no dice. LMK if factory resetting works, I've dirty flashed like 3 times at this point and will hold off before doing it again lol
[Google Pixel 6 Pro] DanielF50:
It's so odd, maybe it's because I went from .037 to the EMEA build.

I can normally figure out what's wrong or what's causing an issue, but there no way to debug this because it just bootloops before you can even get use ADB, or boot into safe mode.
[Google Pixel 6 Pro] Ghisy:
I did the same. The kernel flashed successfully with EXKM. Something else must be wrong.
[Google Pixel 6 Pro] DanielF50:
Oh right, idk what it is then as it even doesn't work when everything is set to stock just finishing my backup so I can wipe, as above, will advise if this works.
[Google Pixel 6 Pro] manueltimz:
google pixel 6 pro here, was using 1.3 and was working well, however after dec update facing the following issues. i have magisk and lsposed

i flashed the kernel via fkm and after reboot my p6pro goes straight to bootloader. doesn't even want to go to recovery mode.

edit 2: flashed this time with exkm, after reboot, device goes to fastboot mode.

what could be the issue @Freak07
[Google Pixel 6 Pro] MArtyChubbs:
Flashed with EXKM and all is well. Great work @Freak07

Please donate to help with his efforts!
[Google Pixel 6 Pro] MrGimpGrumble:
Flashed latest version and everything went well but I'm not getting audio through Bluetooth and Android auto isn't working... Flashed stock boot back and everything works... Any ideas?!
[Google Pixel 6 Pro] manueltimz:
I have the same issue. my 6pro goes to fastboot mode.
[Google Pixel 6 Pro] DanielF50:
Ok, so conclusion:

1. Wiped, installed December update (without disabling verity/verification), skipped through all the setup, installed Magisk Canary 92546e8a, rebooted, installed EXKM, everything working as expected, installed Kirisakura 1.4.0: straight to bootloader w/ reason: boot failure - can't even use recovery/rescue mode.

2. flashing vbmeta.img with --disable-verity --disable-verification flags forced a wipe (obviously), but also allowed it to boot with the kernel installed.

3. wiped completely again, disabled verity/verification, flashed magisk/kernel again, booted perfectly.

It's weird that I had this issue in the first place as --disable-verity --disable-verification flags were used as soon as I received my P6P and every update has been run with both commands inside flash-all.bat. I'm pretty sure you can't re-enable verity/verification again without wiping either, so they would still have been disabled.

The only explaination I can think of is that I installed this topjohnwu's artifact build yesterday & somehow that reverted my vbmeta flags to enabled?? I literally have no other explaination.

Either way, I have wiped again and not disabled those flags as Magisk now works without those commands - hopefully Freak can update the kernel to work with the flag enabled, as once this becomes more widespread knowledge it might become more of an issue.

@manueltimz - dirty flash full december update over the current install (having removed -w and adding --disable-verity --disable-verification to your flash-all.bat), then you will get "recovery" back, but wont boot, then download & sideload the december update via the ADB sideload update option in "recovery", then you will be able to boot back to Android. You will need to flash Magisk again after sideloading, if you flash the kernel again though you'll be back to square one, so either backup, wipe, disable flags, and then install kernel, or just stay with your current setup.
[Google Pixel 6 Pro] KHANrad_SIN:
is the power hint module still compatible with version 1.4.0 of the kernel?

EDIT: Whoops nvm should have read.
[Google Pixel 6 Pro] manueltimz:
Thanks, it worked. for sure the issue is with disable verity.

downside is that I had to wipe my device. No biggie though due to having backup @Freak07 maybe you can assist users with this. Thanks
[Google Pixel 6 Pro] Lughnasadh:
I believe you have spotted the problem. I'm pretty sure (but not 100% certain) that that build of John's you used had the fstab load to system/etc commit in it to help with the problems on the December update, but not the vbmeta commit, so that's why you couldn't boot the kernel.
[Google Pixel 6 Pro] DanielF50:
Great to know!

Awesome, thanks for the explaination, my brains a bit fried today 😅

In regards to the kernel, I'll just have to wait until it is advised that it works with both enabled/disabled flags to reflash 👍
[Google Pixel 6 Pro] joshnichols189:
I had thought it might be verity related as I updated using the thread here and when flashing the update the thread used to say have verity and verification disabled, but now it says to not. I thought it weird that I could boot a patched magisk tho. Anyways, thanks for the efforts! I'll give it a whirl in a little
[Google Pixel 6 Pro] Attinderkahlon:
New update is pretty solid, but it doesn't go to deep sleep when I'm playing YouTube music in background screen off. Idles gets bad....3.50 to 4.10 per hour idle
[Google Pixel 6 Pro] i42o:
" new vendor_dlkm image larger than vendor_dlmk partition.aborting "....
[Google Pixel 6 Pro] NippleSauce:
Accidental post. My apologies
[Google Pixel 6 Pro] Vio281:
flashed oriole version, likely wont install the app as I dont care for modifying it, but everything running well so far. the standby mode is plaguing these phone though
[Google Pixel 6 Pro] Freak07:
- still thinking about how to provide the necessary things without causing too much confusion, but I guess I´ll upload them today :)

Proton AOSP is still on november patch?

those are a bit of a different story (the wlan driver has a lot of wakelocks at its disposal to wake the device and those two aren´t needed necessarily) and are still removed completely from the drivers source on this kernel. so you can´t block them with the wakelock blocker anyway.

if the kernel would go to deep sleep while music is playing, music playback would stop. 3-4% /h for music playback seems fine.

deep sleep over night is fine as well. If your device doesn´t go to deep sleep at all it´s caused by an app/service or other process stuck in background.

I´m not sure what happened to you. I used the automated magisk build that got created upon the fstab commit, which allowed rooting on december too.

Yesterday I updated to the latest magisk canary that´s "officially" released on magisk github and was able to flash the kernel.zip just fine. I also flashed back the rooted stock image along with the three other images, that boot.img was patched with the artifact build, installed the official canary apk from yesterday, updated magisk via the new app, rebooted and flashed my zip afterwards.

I also tried flashing via exkm and fkm, with restoring stock images in between and both apps worked fine for me.

I disabled verity and verification when flashing the december factory image to my device (went from 037 to emea), as it´s also mentioned in the requirements in the OP.

If the flashing fails on your device you might either want to restore the four stock images this kernel modifies from the matching factory image in case you ran another kernel or dirty flash the factory image (with -w removed to not wipe, but issue the vbmeta flags again, as you should every time you flash new vbmeta)
[Google Pixel 6 Pro] KedarWolf:
Call me dumb, but no option in EK Kernel Manager to actually install the kernel. :(

Can someone show how?
[Google Pixel 6 Pro] KedarWolf:
Just saw it in the Dashboard, my logic told me to look in Tools. :/

I dirty flashed the December update using this guide.

https://xdaforums.com/t/method-to-u...thout-wiping-data-and-retaining-root.4356065/

Made sure I used the December update Magisk from here, flashed the kernel, all my apps retained and everything is okay. :)

https://xdaforums.com/t/root-users-read-this-before-updating.4356231/page-9#post-86094245
[Google Pixel 6 Pro] Freak07:
If anybody flashed december update without disabling verity and verification, but rooted with the latest official canary magisk (the one that presumably doesn´t require passing vbmeta disable verity/verification flag) please report back, maybe I have a zip that allows flashing the kernel without disabling verity and verification too. I don´t have the time to wipe my phone at the moment.
[Google Pixel 6 Pro] Tomatot-:
Yes, actually you're right I think it's the issue. I'll try again in a few days when December update is released.
[Google Pixel 6 Pro] nguyenson91hp:
Report from Australia. Yesterday, I flashes 1.4.0 successfully using FKM after fresh install Dec update A1, with root. I used FKM backup, thinking foolishly backing up the stock kernel. Today I attempted to restore that backup, ran into a bootloop. So I flashed back to A1 stock successfully with data and root intact. So pls not use that backup feature.

Also, I tried successfully after that to change to A5 (AU carriers) and installed 1.4.0 kernel using FKM without problem, data and root intact.
[Google Pixel 6 Pro] xflowy:
@Freak07 thanks for the update man! tho, new version kinda feels not as snappy and smooth as the previous one (and stock kernel) for me. any thouthts on that? :)
[Google Pixel 6 Pro] bjevers:
Second reboot. Both times I wasn't using the phone. Just noticed it rebooting.
[Google Pixel 6 Pro] allenjthomsen:
same issue its only when the phone is idle that it reboots from what i noticed
[Google Pixel 6 Pro] allenjthomsen:
forgot to grab pstore before i flash stock files back
[Google Pixel 6 Pro] Burt Squirtz:
I haven't had any random reboots yet but my eye is definitely open and ready.
[Google Pixel 6 Pro] joban727:
I have unlocked bootloader but I don't have root because I would have to wipe again. Can I still try flashing this kernel?
[Google Pixel 6 Pro] Freak07:
thanks for the kind words :) I appreciate it.

thanks for confirmation. I hoped it would boot fine, but now I´m relieved.

it should be included in the kernel. go to settings in the app and choose to use the kernel backend option.

thanks for the reports and the logs. I had the same issue during the night.

I suspect it´s something in linux-stable upstream that doesn´t play nicely. Generally so far the gki kernel seems very finicky with linux-stable. The first revision 5.10.44 screwed up the scheduler/pelt.

I´ll look into it and post an update once I know what´s up.
[Google Pixel 6 Pro] Freak07:
hey, thanks for the detailed feedback.

I guess 1) is probably related to EDIT 3. However this should be solved in the next build. FPS returns now back to 60fps.

Google hasn´t fully enabled LTPO yet anyway, otherwise the display should run at even lower FPS.

I´ll check if 2) happens on my end as well and try to debug :)

KCAL uses qcom drivers to tap into the display driver. I haven´t used a non qcom based android device prior for a long time. The drivers for KCAL aren´t used on the Pixel 6 pro as it's not QCOM based.

Right now my priority is to get the base kernel stable, but afterwards I can take a look at it and I´m sure there are other devs that might chime in by then.

However I also have to say that I don´t have any problems with any tint on my pixel 6 pro.

I´d recommend you to take a look at the app released in this post though:

https://xdaforums.com/t/app-5-0-2020-12-22-cf-lumen-v3-74.2711912/post-84459151

It allows you to set custom RGB values, define rules for it and according to chainfire it´s at least on par with KCAL:

https://xdaforums.com/t/app-5-0-2020-12-22-cf-lumen-v3-74.2711912/post-84156987

Edit 2: my charging speed seems to be the same on google charger so far.
[Google Pixel 6 Pro] cultofluna:
Yes you can ...you don't need root
[Google Pixel 6 Pro] Freak07:
1.0.2 Test

if anybody wants to test.

this is the previous release, but only 5.10.44 merged.

all previous features are intact

LRNG is included now: https://www.phoronix.com/scan.php?page=news_item&px=LRNG-Random-2021-v41

So far no more random reboots for me.

I checked charging and the device charges same as on stock kernel.

smooth display is fixed and correctly fall back to 60fps now.

Download: https://www.androidfilehost.com/?w=files&flid=329484

Please follow the procedure in the OP to flash the provided images for 1.0.2.

Restore stock vendor_boot.img, which you can extract from the factory image and flash it the same way as provided in the instructions. This is critical otherwise developer options will crash due to a selinux denial.

Download:
[Google Pixel 6 Pro] Nekromantik:
is SE Linux enforced on this?
[Google Pixel 6 Pro] Freak07:
Yes.
[Google Pixel 6 Pro] Utini:
Wohooooo!!! :) Thanks! Now I need to find a good guide on how to root atm :D
[Google Pixel 6 Pro] RogerF81:
Ohh yes I was hoping for this to come! :)
[Google Pixel 6 Pro] Krasendo:
Gonna check it out ^^!
[Google Pixel 6 Pro] Ariac Konrel:
The random reboots stopped on 1.0.2.

Everything has been running smoothly all morning.

Will update this post if any issues come up.
[Google Pixel 6 Pro] Freak07:
Update to 1.0.2

Hey guys and girls,

Sorry for any inconvenience caused by the semi-stable first release yesterday. The random reboots should now be solved since I got several last night on 1.0.0, but none during the day running 1.0.2 and several testers confirmed it. Let´s keep the fingers crossed.

For now I reverted linux-stable back to 5.10.44, the one revision I merged and tested extensively after identifying some scheduler breakage.

All previous features mentioned in the OP are still included.

LRNG is included in 1.0.2. More information can be found here.

During the day I discovered that my compiled vendor_boot.img is a userdebug build. That´s the reason developer settings crashed on 1.0.0, due to a selinux-denial that happens because of userdebug.

Since we don´t modify anything yet that ends up in vendor_boot.img please flash back the original one from the factory image you´re device is running on.

Boot to bootloader and execute the following command:

fastboot flash vendor_boot vendor_boot.img

Then proceed to flash the other images as described in the guide in the OP!

Changelog:

- revert linux-stable back to 5.10.44 to solve random reboots

- keep all previous features intact

- introduce LRNG (thanks for @arter97 for the inital backport on his op9 kernel), more info here

Download:

Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

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

www.androidfilehost.com

Instructions can be found in the OP!

Don´t forgot to restore the stock vendor_boot.img found in the factory image if you flashed 1.0.0!
[Google Pixel 6 Pro] scott.hart.bti:
Sweet! Was wondering who would be the first to drop a tasty treat for our p6p. Now I have motivation to unlock and root. Can't wait to try this out. Thanks for your hard work.
[Google Pixel 6 Pro] flar2:
I don't know if the same stuff applies on this device, but I made something like kcal for an earlier exynos soc, maybe it will be of use:

mdnie: override RGB · flar2/starlte@c30dc4f

Samsung Galaxy S9 Exynos. Contribute to flar2/starlte development by creating an account on GitHub.

github.com

BTW, I don't think I will make a kernel for this phone, I bought one but will be returning it because I find it underwhelming, it was very expensive, the source is a clusterf*ck and very few people use my kernels anymore. I'll just update EXKM to work with all the newer exynos stuff before I send it back. I'm also working on a new "flash center" in EXKM that will make it easier to flash and extract all the different images.
[Google Pixel 6 Pro] Burt Squirtz:
Freak can I just say something? You are one of the most level engaging, friendly and confident developers I have ever been in communication with.

I won't name any other developers but some others would have maybe taken offense to my post or gotten defensive. But you instantly realizedI was just trying to give feedback and help the Kernel get better. I'm incredibly impressed! 👍🌟.

I was just wondering if there's any way you could build the kernel with clang 13? Believe it or not I do notice a performance difference on other kernels, when they changed from 12 to 13. I realize clang 13 isn't fully "stable", but every 13 other kernel build I've tried has had zero issues. The noticeable improvement in smoothness and reduced latency makes a massive difference in my opinion^.
[Google Pixel 6 Pro] yujinloh:
p6p(december update, verification and verity flags not disabled) goes into bootloader mode with reason:boot failure after reboot {fkm shows no errors when installing).

In the requirements part it said verification and verity flags needs to be disabled while the link to root the phone just beside it says its not neccessary to disable them anymore).

so is it actually needed to disable verification and verity flags?

I'm in the process of redoing everything again with verification and verity flags disabled :)

Edit : you will need to disable verification and verity flags for things to work, unless OP releases a fix for it.
[Google Pixel 6 Pro] Freak07:
If you have a few minutes to spare I can send you a test zip that maybe boots with the vbmeta flags not disabled.
[Google Pixel 6 Pro] Freak07:
fkm only backs up boot.img (which was sufficient on older devices), however flashing the zip boot, dtbo, vendor_boot and vendor_dlkm get modified. so to get back to stock you need to restore all 4 images like mentioned in the faq.

sorry you ran into troubles, but I can´t account and document all of these little things here.

no such problems on my end. make sure you´re not using any other magisk modules or other mods.

might be an app/process constantly requesting CPU cycles, which could cause such issues.

use top command and check if there´s anything hogging the CPU.
[Google Pixel 6 Pro] yujinloh:
Ah i saw this too late lol, i no longer need it as i redid everything with verification and verity flags disabled and everything works fine.

Still very grateful for what you do for this device though.

But maybe edit the post to indicate whether verification and verity flags needs to be disabled or not?

I think the 1.4.0 zip is currently broken with verification and verity flags enabled,
[Google Pixel 6 Pro] Freak07:
it says it in the requirements in the OP. vbmeta flashed with flags disabled...
[Google Pixel 6 Pro] Freak07:
well if anybody wants to try I attached the test.zips to the quoted post.
[Google Pixel 6 Pro] yujinloh:
Yep, but the how to root the phone here link you attached indicates that disabling verity/verification is no longer necessary.
[Google Pixel 6 Pro] Freak07:
i see where the confusion came from. I removed the link and just left the vbmeta warning for now.

Let´s see if somebody flashed the test zips and whether that solves the issue, or we still need to disable it.
[Google Pixel 6 Pro] Krasendo:
Everything works fine, thank you for the kernel uwu

I installed 1.4.0 by FKM
[Google Pixel 6 Pro] yujinloh:
Since magisk does not require verification and verity flags to be disabled now, will the kernel also follow suit in the future?
[Google Pixel 6 Pro] DanielF50:
Thanks for the reply - me either, sounds like a random issue unrelated to anything from this thread - it's completely confused me.

I was running 1.3.0 on Nov build perfectly, then updated to Dec EMEA with disable verity/verification flags in the flash-all.bat, so not sure why it seems to have reverted back - I was even using the disable flag when dirty flashing, in an attempt to fix my phone.

Awesome, I'll give this a go & report back! 😎

Edit: flashed and booted perfect, first time, thanks @Freak07!

There's a test build on the previous page, I quoted above :)
[Google Pixel 6 Pro] yujinloh:
Interesting , will take a look at it
[Google Pixel 6 Pro] nguyenson91hp:
Totally understand that, mate. Just comment so newbies like me could avoid any inconveniences.
[Google Pixel 6 Pro] Freak07:
So just to confirm, the attached zip with 23016 as appendix flashed fine on a device rooted with magisk 23016 and vbmeta flags for verity and verification enabled?
[Google Pixel 6 Pro] DanielF50:
Yes indeed - I didn't disable verity or verification when I did a full reset last night. The kernel zip flashed fine & is working as expected with 23016.
[Google Pixel 6 Pro] Freak07:
Perfect, thanks
[Google Pixel 6 Pro] yujinloh:
Another confirmation that this works with disabling verity/verification.

Edit : Root is lost if i try to rename/hide magisk 23016, not sure why
[Google Pixel 6 Pro] Freak07:
With disabling? You mean without issueing the disable vbmeta verity verification command?

Because it always worked fine when those were disabled.

Hiding not working should not be related to this kernel. It's a magisk issue if that's the case.
[Google Pixel 6 Pro] yujinloh:
Yes, the Kirisakura_Raven-1.4.0_23016.zip kernel works without disabling verity/verification.Bootloader mode error with reason : boot failure is no more.
[Google Pixel 6 Pro] Lughnasadh:
Just out of curiosity, will the new test zip (once it is finalized) that works with verity/verification enabled also work if verity/verification is disabled? I know disabling verity/verification is not needed anymore, but anticipate some who may still have it disabled so was just curios about that.
[Google Pixel 6 Pro] neekless:
Will there continue to be imgs that are flashable in fastboot without relying on proprietary apps?
[Google Pixel 6 Pro] DanielF50:
I assume a simple solution would be to have one universal zip which runs a script upon flashing to check your verity/verification status & proceeds to install the correct files for your system.
[Google Pixel 6 Pro] Lughnasadh:
Yep. Was basically just asking if he was going to do that because I can foresee some who may still have verity/verification disabled (for whatever reason) in the future.
[Google Pixel 6 Pro] xflowy:
thanks for the reply. so no changes on your end that could interfere with such performance things?

and: whats top command? :/
[Google Pixel 6 Pro] neekless:
Type 'top' without quotes into a terminal emulator