yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Nightf0x_007:
How is protonaosp? Compared to stock, as i will only wipe my phone if im going to flash proton otherwise no

I think also what happened with me is due to dm verity as i tried manually flashing the update but couldnt boot or flash magisk boot image so i reinstalled the update via android flash tool and ticked dm verity/verification disable then again couldnt boot or flash magisk pqtched boot image so again i reflashed the jan. Image manually and then patched a new boot image and flashed it all went ok but then when i flashed kirisakura device bootlooped and the corrupt warning started appearing, now im rooted on stock jan. Image without kirisakura

If anybody know a way to get rid of this corrupt warning and flash kirisakura without wiping would be great, backing up and wiping is major headache for me

edit: is it safe to do the following flashing vbmeta then reflashing magisk then reflash the kernel

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

fastboot flash boot magisk_patched.img

or this puts my device on risk of wiping my data ?
[Google Pixel 6 Pro] danw_oz:
It was buried in posts because after my previous flashing issues, I went through and was reading pages after pages about the patching because I did not want the issue again.

I might have miss-understood Texan1's comment and your reply in post #544, there were others mentioning it was required early on but can't remember where they are now.

Edit found it. Was previously unsure what requirements where for using kernel managers for flashing so I looked at the manual one. It was following OP manual instructions Spoiler in post #4

The addition of the flashing for Kernel managers is very helpful, thanks for that, because prior I was unsure what the overlap was between this method and manual
[Google Pixel 6 Pro] ChongoDroid:
Wow scrolling is much improved. I was happy with the improvements from January update but this kernel smoothes out micro stutters even more so.

Thanks for this!
[Google Pixel 6 Pro] bouchigo:
It was a good rom, snappier than stock and a little bit better battery life, but not as customizable as I had hoped it was. Also, I had a glitch to where if I would try to check an email it would not load on the first try, I would have to back out and then re-open the email to have it load properly. Other than that, it was pretty solid.

Hopefully crDroid comes out soon for this phone for more customization.
[Google Pixel 6 Pro] Gordietm:
@Freak07 I finally got the Kirisakura kernal flashed and working properly 🙂

First I did a complete uninstall of Magisk, then I use the Android Flash Tool to force flash the January update, updated the partitions and then disabled verity and verification (just to make sure the kernel flashed properly, I know you don't need to do this anymore, but no harm). When the phone rebooted, the error I was getting previously (your phone might be corrupted, press enter to continue) is now gone.

Flashed the patched boot image and your kernel flashed properly with EXKM. 👍

p.s. I used the new kernel zip you provided with the ak3 update.

Thanks for all your help.
[Google Pixel 6 Pro] chill145:
First, thanks for the kernel but I had a quick question. I read through the first few pages and other kernel threads discussing patching boot img before flashing.

However, I but don't see that in the instructions so do I just need to flash the correct kernel.zip via EXKM or FKM and root will still be there or an I missing something?
[Google Pixel 6 Pro] Freak07:
Correct. If you're already rooted, flashing the kernel.zip via exkm for fkm will preserve root.

Follow the instructions in the first post. (y)
[Google Pixel 6 Pro] Utini:
Working fine on January update :)
[Google Pixel 6 Pro] dabrownie:
I like it, just like you said, it smoothes out even more the micro stutters.

This is my first flash as I was not comfortable doing the whole "flash this then flash that" stuff.

I'm so glad I waited until it was a simple download and flash and go!

So I wanna say,

Thank you Freak07!

Been flashing your kernel on my oneplus 7pro this whole time and I love it and now one Pixel 6pro!
[Google Pixel 6 Pro] bush911:
Thank you very much for the kernel, I have been using your kernel on my Pixel 3.

What I was wondering is whether this Kernel supports battery idle mode. I know this concept from Acc document which says by battery idle the phone consumes external power instead of battery. the stock pixel 6 kernel does not support this feature.
[Google Pixel 6 Pro] simonk206:
This fixed my issue finally! Just reflashed Jan Firmware with disabled verity and v1.5.0 kernel works now
[Google Pixel 6 Pro] Freak07:
Adjusted the features detailed in the OP a bit and improved the instructions to clear up some steps regarding keeping root, the ak3 helper zip etc.

Next release is already under testing.
[Google Pixel 6 Pro] felek73:
Anyone has any problem with screen cast on this kernel? It worked before I flashed this kernel now it does nothing.
[Google Pixel 6 Pro] MartinN6:
@Freak07

Thank you very much for your excellent work!

There is just a tiny little thing I want to ask. I try to activate the s2s-gesture with the EXKM but it doesn't work at my device. Guess I do somthing worg, but dont no what.
[Google Pixel 6 Pro] Freak07:
Hm I guess I should remove the sysfs node that exkm picks up, as it doesn't do anything with the current s2s implementation.

Use the CleanSlate config app to set s2s to your desired configuration.

Here's my config. It's meant to be used with navigation gestures and it will turn the screen off when swiping from left or right bottom corner inwards (you'll have haptic feedback when successfully triggered) and lifting the finger up.

Keeping the corner pressed will pull down notification bar (make sure to install and set up the Cleanslate companion app as well).

Double tapping corner will shut down screen too.

2 new items by freak 07

photos.app.goo.gl

Connection to my Chromecast works just fine.
[Google Pixel 6 Pro] woundman:
Hi Freak07. I'm having an issue when I restart my phone. Sometimes it randomly has a loading bar like it's trying to update the phone. Seems to do it every other reboot? Let me know if I'm doing something wrong. Thank you!
[Google Pixel 6 Pro] felek73:
I'm not talking about Chromecast it's work fine, just sending phone screen to TV without Chromecast doesn't work
[Google Pixel 6 Pro] Freak07:
No you're not doing anything wrong. That happens if the phone takes a bit longer than usual to boot and the regular boot animation is not "long" enough.

Can have various reasons:

Happens if you update the kernel and the f2fs fsck check runs to update the kernel version, some apex update in the background going on, after a firmware update is flashed and art cache is being optimized, using a few magisk modules prolonging the boot process.

Which TV do you try to cast your screen to?
[Google Pixel 6 Pro] felek73:
Lg65oled. It worked fine before but truly speaking it was on Dec software.
[Google Pixel 6 Pro] Freak07:
Pixels don't support Miracast. You need to either use Google cast or a Chromecast with pixels.

I don't know why it would have worked on December firmware.
[Google Pixel 6 Pro] felek73:
Hm..maybe I'm wrong but what is "Screen cast" tile in QS for? Should I install aby additional app to connect to my tv?
[Google Pixel 6 Pro] rbanaco:
Hey there! Has anyone tested the video in cinematic panning from Google camera? I'm on January update with root and this kernel and it stutters a bit. Has anyone experienced anything similar?
[Google Pixel 6 Pro] dd805bb:
That cast your screen QS uses the Chromecast logo...
[Google Pixel 6 Pro] Freak07:
Screen casting via Google Cast/Chromecast.

I don't know about your TV, but any screen mirroring function on a TV that's Miracast based won't work on pixels.

I just tried 4 or 5 cinematic pans and all of them turned out smooth without any stutters.

Maybe your device is thermally throttled or something is hogging resources in the background?
[Google Pixel 6 Pro] edmondt:
Following the previous bricked Nov flash l got a new Pixel 6 Pro and just flashed the version 1.5.

Fingers crossed, everything seem to be good so far, except I feel that the device is warmer and drains a bit.

Is there some settings or any other thing I need to do? I see the AK3 Helper Module in Magisk enabled.
[Google Pixel 6 Pro] rbanaco:
Thanks for the feedback, I will revert to stock just to try it, the device is sleeping ok and cold. I've tried a couple times.
[Google Pixel 6 Pro] JrSmilez:
Hope this is an ok post, I haven't done any of this stuff for years... Since SuperSU. I decided to give rooting a shot and was having a few issues so I thought before I went back to stock, I'd give a kernel a try. There was another one I was looking at, but it has no instructions at all. I followed these instructions and other than feeling like it took forever to reboot, I've been really happy with trying it out. Thank you for the hard work. It's appreciated 👍👍
[Google Pixel 6 Pro] rbanaco:
So, I've tested the stock kernel and the stutter of recorded videos by camera is gone... My device is the oriole, don't know if that helps in some way.
[Google Pixel 6 Pro] Nekromantik:
mod delete above post please its spam
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
@Freak07 @Az Biker @Lughnasadh @roirraW "edor" ehT @Pekempy

I hadn't used a rooted phone since my S9+ in 2018. I can't thank you all enough for your posts which have made it so much easy to get to a rooted phone with a custom kernel. No issues from start to finish. Thank you again, love lurking around just reading and re-reading posts, lol. Next steps - I have to learn how to update whatever I have (OTA updates, kernel updates, magisk updates, magisk module updates etc.) when newer versions are available, lol, one step at a time.

Happy Weekend!
[Google Pixel 6 Pro] manueltimz:
I updated to Jan build on 6pro. I have used all the previous kernels for 6pr since October when the phone was released. However in this January build i have an issue where the screen freezes when scrolling or typing. Does anyone else have this issue?
[Google Pixel 6 Pro] JrSmilez:
Mine was doing it before I installed this kernel. I don't notice it nearly as much now
[Google Pixel 6 Pro] manueltimz:
Was that on stock?
[Google Pixel 6 Pro] XSLdesire:
can we flash this kernel without disable the dm verity? like the latest magisk?
[Google Pixel 6 Pro] JrSmilez:
Sorry, yes, completely stock. I actually replaced one 6 pro thinking it was caused by a bigger problem.
[Google Pixel 6 Pro] woundman:
Thanks for the quick reply. I've tested it multiple times, even on fresh install. It's been stuck on this loading screen for roughly 5 minutes now. Seems to do it after you restart multiple times back-to-back. I'm going to see if I can replicate it consistently. I'm curious if other users are experiencing the same thing?
[Google Pixel 6 Pro] Freak07:
Yes, it should work just fine. Use either the latest kernel.zip or if you follow the manual route make sure to patch the provided boot.img with latest magisk canary.

However there seem to be quite a few users running into issues with verity on this forum and device. Not only when flashing kernels, but also in the guide threads. If you´re a bit unsure I´d only flash it if you have a PC nearby to flash a factory image to be able to recover and have a backup of your data ready.

If it´s stuck for 5 minutes something else is wrong and it´s not due to the factors I mentioned earlier. I haven´t run into this issue at all, so something else might be screwed up if that happens regularly.

Just tried 6 consecutive reboots and everything is working just fine.
[Google Pixel 6 Pro] woundman:
I've factory reset and so far I've only seen it once now. I'll post again if it continues to do it. However, I think it's working well now. Thanks again.
[Google Pixel 6 Pro] XSLdesire:
thanks for the reply. I have tried it and got the same issue mentioned here, that's weird
[Google Pixel 6 Pro] felek73:
Is it possible to implement dt2w feature at kernel side? I don't think that single tap to wake, which is default on Pixel, is right solution.
[Google Pixel 6 Pro] Freak07:
https://xdaforums.com/t/kernel-15-0...pixel-6-pro-aka-raviole.4358435/post-85976045
[Google Pixel 6 Pro] felek73:
Sorry for missing this and thanks for pointing this out👍😀
[Google Pixel 6 Pro] Gordietm:
This kernel is working really well for me. Battery life is excellent, the phone is responsive and runs smooth.

I'm looking forward to the next release.

Thanks @Freak07 for all your work. It's appreciated
[Google Pixel 6 Pro] Texan1:
So got some camera/video freezes today for the first time since getting my 6 Pro several months ago. On latest Jan build and updated Google Camera app a couple days ago from the Play Store. Have seen a few others reporting this, has it become more common?
[Google Pixel 6 Pro] Izy:
Food for thought any idea about the charging limiting

The pixel could do a 1hour charge if the limit didn't kick in halfway
[Google Pixel 6 Pro] ayobarme:
Hi does the kernel work on the January update?
[Google Pixel 6 Pro] Gordietm:
Yes
[Google Pixel 6 Pro] danw_oz:
Yes, to fix for me on standard firmware was to disable Adaptive battery under battery settings, never saw the issue again after this. definitely haven't seen it with this Kernel even with that enabled.
[Google Pixel 6 Pro] Burt Squirtz:
What made you leave proton to come back on Pixel release? Bro? Isn't proton technically better performance and battery life?
[Google Pixel 6 Pro] bouchigo:
I never had issues with stock, and still don't.

I just wanted to try ProtonAOSP out. It was a little quicker at opening apps, but not enough built in customization for me, plus I had an email bug with it that caused me to have to open emails twice to read them.

I'll wait for crDroid instead.
[Google Pixel 6 Pro] zetsumeikuro:
Are you guys having complete loss of touch until you turn the screen off and back on and touch is restored?
[Google Pixel 6 Pro] Zach Alt:
Nope. Never experienced that.
[Google Pixel 6 Pro] manueltimz:
No its just freezing screen for like 3 seconds and then the screen responds. Happens when scrolling or typing. I went back to stock after January update because that's when the issue started on kiri 1.5
[Google Pixel 6 Pro] zetsumeikuro:
That sounds more like the Accessibility Services bug that some are having. Touch input freezes for 2-3 seconds and everything catches up. That's a Google issue and not because of the kernel. Google has finally addressed the issue and it will be released in a future patch.
[Google Pixel 6 Pro] KyriaZ:
Yeap same here but its not kernel related for sure cause i am having the same when i was completely stock. It will fixed on Febs update as they announced.
[Google Pixel 6 Pro] roirraW "edor" ehT:
This issue? Pixel 6/6 Pro randomly freezing all touch inputs for 1-2 seconds bug - temporary fix inside along with this update in that same thread regarding it (TL;DR Google solved it and will release it in a "future" update).
[Google Pixel 6 Pro] Burt Squirtz:
Bro, I've got a 55 oled. Gaming on those things is nothing short of pure Bliss. I bought a 'TCL 55 quantum TV' thinking you could get somewhat close to the same quality. What a joke in comparison. Those perfect contrast and nice deep inky blacks, wonderful poppy color. Nothing can match an OLED tv - even Samsung Neo Qled.
[Google Pixel 6 Pro] blaze909090:
Anyone else having problems installing the kernel on Proton AOSP (new January built)?

Device says it's corrupt and doesnt boot.
[Google Pixel 6 Pro] rav101:
This kernel is designed to work on stock PixelOS rather than custom ROMs like ProtonAOSP. That's why it's likely not working.
[Google Pixel 6 Pro] Freak07:
Can't really comment on this as I'm not familiar with the internals of Proton AOSP. From my thread i know people used my kernel on it in the past and as far as I'm aware does Proton use the stock kernel.

If you're willing to wipe, you could try to disable verity and see if that changes anything as the error you encountered sounds a bit like it.
[Google Pixel 6 Pro] bush911:
@Freak07 boss, any intention of adding battery idle mode supporting? As far as I know, there is no Pixel 6 Kernel which supports battery idle mode.
[Google Pixel 6 Pro] jbarcus81:
Any tweak recommendations for the Pixel 6 Pro? I decided to root and do all this fun stuff again and see what the rooting world has to offer these days and I really missed tinkering around! I skimmed through all the posts and didn't really see much so if I missed it, sorry! But so far I'm just leaving it as is after installing the kernel and love it so far! Amazing as always OP!!
[Google Pixel 6 Pro] Tomatot-:
I can confirm latest build works fine, but indeed I think you need to make sure vbmeta/verification are disabled when flashing/updating proton.
[Google Pixel 6 Pro] BarackMitzvah:
Thanks for sharing your work. My P6 Pro runs so smoothly on your kernel
[Google Pixel 6 Pro] Lughnasadh:
In my opinion, tweaking is unnecessary. Kernel runs great as is. I miss tinkering around too 🙂
[Google Pixel 6 Pro] wanttotree:
Forgive me if i miss it, does fpr on this kernel disabled during aod? It works fine once the screen is on. But not at all while on aod.

Update: turns out its the new magisk 24. Back to canary build now.
[Google Pixel 6 Pro] Freak07:
No i don't have any intentions to modify the charging driver at all, sorry. I leave my fingers from this.

It's up to google to add this. I don't have the necessary means to do broad and thorough field testing. Battery is not easily swappable.

Besides the CleanSlate features there's not much to set. The magisk helper module does most of this by adjusting the powerhal so settings are changed dynamically depending on the type of input scenario. :)

Works just fine for me.

Oh I just saw the edit, I'm still on the canary. Thanks for checking. (y)
[Google Pixel 6 Pro] Utini:
This, your detailed changelogs and the great support is why I love this kernel :)
[Google Pixel 6 Pro] roirraW "edor" ehT:
We have at least one user for who the fingerprint reader works fine on AOD with Magisk 24, and some other evidence that it shouldn't affect it. I haven't updated yet.

Apologies for the OT. @wanttotree if you have any other information about this, feel free to respond in the thread the below two quotes are from (click the back arrow beside the user name).
[Google Pixel 6 Pro] bush911:
Have you ever managed to fix this issue without wiping the phone?

I happen to encounter this isuuse while flashing different kernel over each other or restording to stock root kerenl.

I was so stupid when I first saw the corrupt message, I thouth the phone is soft bricked I must re flash the stock firmare.

After I flashed the stock firmware and rooted, it turned out the corrupt message was still there and coul be got rid of by pressing power button.
[Google Pixel 6 Pro] awarman:
What is this module? I don't remember installing it. Does it get installed with this Kernel? I disabled it because I wasn't sure for now.
[Google Pixel 6 Pro] a63548:
Yes, keep it enabled. In the first post it clearly mentions it gets installed automatically when flashing the kernel zip. I am however completely baffled why you have the OnePlus 7 Pro Companion Module installed???
[Google Pixel 6 Pro] bush911:
Hasn't your phone been fully wipped. I am going to try to get rid of this annoying message to.
[Google Pixel 6 Pro] Gordietm:
Yes, I resolved the problem. I explained what I had to do in post #694.
[Google Pixel 6 Pro] Gordietm:
Yes, I had to wipe the phone.
[Google Pixel 6 Pro] bush911:
Thank you. It seems that wiping the phone is a must to get rid of this corruption message.

I am going to disable that socalled verify and verification next time while fastboot flashing the stock firmware.

Can I get this done once and for all?

I mean this time I disabled, will I lose data while disabling again next time?

Thank you, this flashing procedure is getting more and more complicated
[Google Pixel 6 Pro] Freak07:
no, you have to wipe only when disabling the flags for the first time. Just don´t forget to issue the command to disable the vbmeta flags everytime you flash a firmware which contains a vbmeta.img before rebooting the device. (everytime you flash a factory image or a full OTA.zip.)
[Google Pixel 6 Pro] awarman:
That's what I mean. I know the AK3 module is needed and installed per the notes. Companion module is weird to me. I've removed it.
[Google Pixel 6 Pro] Freak07:
Sounds to me like you accidentally downloaded and flashed the wrong file on my androidfilehost at any point in time. The file you downloaded is on the most popular files of my androidfilehost account. But yeah you can remove that safely. :)

When flashing the most recent kernel.zip from the first post, there will only be the AK3 Helper Module in Magisk Manager module list, which you should not touch as you stated.
[Google Pixel 6 Pro] Gordietm:
I thought it's not necessary to disable verity anymore with the new canary magisk builds?
[Google Pixel 6 Pro] bush911:
I had thought too.

But it seems that to disable verify will do the good, in case that just like I flash Kernel over each other
[Google Pixel 6 Pro] awarman:
It sure seems that way... Although I don't remember doing it. I'm sure it wasn't in the raviole version. Not questioning that.
[Google Pixel 6 Pro] Freak07:
Didn´t you have to do this yourself to get rid of the device is corrupted warning? Unless I misunderstood your previous post?

I just answered the question whether or not a wipe is required on consecutive firmware flashes with vbmeta flags disabled and keeping them disabled.

Disabling the flags should not be needed any longer if everything goes according to plan, with the new magisk canaries that´s also correct. One of my testers runs with vbmeta flags not disabled and has no issues.

But given all the issues some people run into, when they end up with the device is corrupted message (seems also to happen when flashing/updating just factory images without the involvement of anything else, at least what I saw in the guide threads) there still seems to be something wonky.

I didn´t find any clue what exactly is happening, so unfortunately I can´t comment any more on this.
[Google Pixel 6 Pro] Rodimus8402:
Has anyone else been experiencing issues where the P6P's screen is slow to wake?

I think it has something to do with deep sleep, and occurs whether tapping on the screen, or lifting to wake the device, it just seems to be stuck for a few seconds and then the screen comes on. I've been trying to isolate if an app or setting etc is causing it, but I haven't found the root cause yet.

If I don't change any settings via a kernel manager app (EXKM) then it doesn't occur either, which makes me think that it's related to the kernel in some way.

I've only noticed it after updating to January.

P6P, Rooted, Kirisakura.

Thanks!
[Google Pixel 6 Pro] Freak07:
No i haven't faced that myself at all.

Did you change any settings in exkm? You shouldn't have much more settings available stock kernel compared to my kernel.

Did you maybe disable any wakelocks in exkm?

Edit: just checked the thread you created. seems like people get this on stock too.
[Google Pixel 6 Pro] Rodimus8402:
The only setting I change is the "Readahead kb" from 128 t0 256, and toggle "On" all of the other settings.

Could that cause any issue?

I'll try just loading the stock values without changing anything and see if this still occurs
[Google Pixel 6 Pro] Freak07:
the readahead setting shouldn´t cause it.
[Google Pixel 6 Pro] Rodimus8402:
I think I found what's causing it, seems to be using Zygisk in the latest version of Magisk.

If I have that disabled, I'm able to use EXKM to change any and all kernel options.

I'll report this in the correct thread, thanks!
[Google Pixel 6 Pro] jlokos:
I'm using FKM and the latest zygist Magisk. I have no issues changing kernel settings.
[Google Pixel 6 Pro] Rodimus8402:
Interesting, any idea how I'd determine what's causing the issue? How I could figure it out by using Logcat?
[Google Pixel 6 Pro] jlokos:
You might see if anyone else on the thread is having the same issues with EXKM. Sometimes the kernel and the kernel managers don't play together well.