yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] slickrasta:
Has anyone confirmed if safetynet fix and shamiko work with A14 and Kirisakura 2.0?
[Google Pixel 6 Pro] TheColin21:
I am not using Shamiko but I am passing SafetyNet with USNF, Zygisk and enforced denial list.
[Google Pixel 6 Pro] sharkie405:
I had issues with landscape and various apps, most notably YouTube. In my case the repainter app was the cause. It doesn't work with 14 properly. Once I uninstalled repainter, I haven't had any further landscape issues.
[Google Pixel 6 Pro] Suavie103:
I flash backed to stock as well. No issues so far.
[Google Pixel 6 Pro] awarman:
Seems like my only issue on stock is with the fingerprint censor not accepting the first time. That is it.
[Google Pixel 6 Pro] Admiral2145:
I'm also having lag issues on the p6... Camera... Apps... Scrolling in general.

switching the clusters to conservative gov helps a lot
[Google Pixel 6 Pro] Roll3r:
Ah hah! Think I tried everything besides that - I have the notification hidden so forgot it was running. Thanks!
[Google Pixel 6 Pro] majorfigjam:
Yes, they work.
[Google Pixel 6 Pro] TheColin21:
I am also having havy issues like this. Especially with the camera. This does not seem to be related to the kernel. It also happened with A14 and stock kernel. I tried setting the governors to conservative which seems to slightly improve but not solve the problem. I will try this further.
[Google Pixel 6 Pro] TheColin21:
Also @Freak07 did you by any chance forget to change the thread's title?🤔
[Google Pixel 6 Pro] ada12:
conservative governor is very bad idea ever for tensor processor its kill all google scheduler and will introduce massive issue
[Google Pixel 6 Pro] Gytole:
Have you used it? I have been using it for about 5 months now with great results...
[Google Pixel 6 Pro] ada12:
Every developers will tell you that ... you're phone just survive by libperfmgr but it's no mean it's nice
[Google Pixel 6 Pro] Gytole:
Do you use it?
[Google Pixel 6 Pro] ada12:
Offcourse No - totally nosense
[Google Pixel 6 Pro] ada12:
You get corruption after flashing kirisakura and returning in stock boot because it's no monolithic for pixel 6 - freak07 maintain 2 phone so I understand he missed from pixel 7 to update Changelog for pixel 6

Don't miss to re-flash stock Vbmeta for resolve your issue { If you see in zip vendor_boot.img & vendor_dlkm.img it's no monolithic for the tips }
[Google Pixel 6 Pro] Rachid.Ala:
I have no issues using the kernel. No camera lag no rotation lag ...

I think the people having issues should try a factory reset. That's what I would have done if I had such issues.

For the person using conservative governor, that's a very bad idea and may introduce bugs and poor battery life, you should instead keep the default scheduler and use conservative mode in cleaslate config app if you want.

Oh and Thank you freak07 for the update.
[Google Pixel 6 Pro] awarman:
Confirmed it was repainter that was causing the issues.

Update: Spoke too soon. Once again lagging and locking up on Kirisakura. I'll just go back to stock again.

But hey... P8P tomorrow!
[Google Pixel 6 Pro] AlDollaz:
Screen rotation lag was definitely Repainter for me. Everything else is good now.
[Google Pixel 6 Pro] Psfanboy88:
The titel of this thread needs an update. I didnt notices that there already were a version vor Android 14...
[Google Pixel 6 Pro] uns0undl0gic:
I did a fresh wipe with A14 and installed the latest version of the kernel. No issues at all so far, I am also unable to reproduce any of the lag or camera issues that have been reported so far.
[Google Pixel 6 Pro] Maverick Jester:
Definitely think Repainter is the cause of the lag, as disabling it immediately sorted out the lag and choppiness.

EDIT: no, looks like that was a temporary solution. The lag is particularly horrible when unlocking from sleep and opening the camera.
[Google Pixel 6 Pro] TheColin21:
As many people seem to have expected: conservative scheduler did not improve the lags. (It did not worsen anything either though.).

I am not using repainter, screen rotation works fine, I just have a lot of camera lag and sometimes lag in general that I did not experience before A14 but did experience before using Kirisakura on A14.
[Google Pixel 6 Pro] Admiral2145:
I'm going to flash the other side with sept a13 ota and run that til google fixes it...

I'll have my p8 pro sat also.
[Google Pixel 6 Pro] estapagu:
Screen rotation lag (using repainter) and a lot of camera lags ON STOCK KERNEL here (updated from A13). So I'm uninstalling repainter right now and flashing

Kirisakura kernel.​
[Google Pixel 6 Pro] bradical711:
Can confirm lagging on my pixel 6 A14 with kirisakura 2.0.0 was caused by the app Repainter, as turning off the setting within the app and rebooting solves all lag throughout the phone. However, the first time I open the camera or another app that accesses the camera after reboot, will cause extreme lag for about 30 seconds before stabilizing. The camera will also lag again after closing and reopening the app too. It should be said that I am rooted with magisk 26.3 and use zygisk/LSPosed 1.9.2. Not sure if that would also cause lag in camera but just wanted to share the observations on my end. No other random crashes or reboots with 2.0.0 though so great work and thank you !
[Google Pixel 6 Pro] xpdragon:
I haven't seen any lagging issue with my P6P since updating it to A14 with the latest version of this kernel. I don't use the Repainter app though. I use Project Themer app instead, also Magisk 26.3, Zygisk/LSPosed 1.9.2, AOSP Mods, AccA, Tasker, etc.
[Google Pixel 6 Pro] pentium0:
Netflix still works for me. On raven pixel 6pro, updated to A14 from A13 with pixelflasher, rooted with magisk. Running universal safetynetfix
[Google Pixel 6 Pro] bradical711:
Reinstalled the A14 update using the flash all script without wiping and no more lagging on my P6. Maybe the lag is caused by a bad OTA ? Either way, I just wanted to report back and say that reinstalling the update fixed the lag ! I kept the same setup etc minus Repainter until the app gets an update.
[Google Pixel 6 Pro] ppog:
Just for all of you attributing lag to repatinter, I had awful lag on 14 factory image flashed with Pixel flasher, and this kernel, and I don't use that repainter app. The lag was on swiping home screen/app drawer, browsing instagram feed where it would chug seriously when reels autoplayed, and likewise with youtube feed. I went back to stock, no lags. So I don't think that an app was the cause, or at least the main cause.

EDIT: Also I forgot to say camera lagged terribly too, both opening app and using in WhatsApp. Not so with stock
[Google Pixel 6 Pro] rbanaco:
Same experience as @ppog
[Google Pixel 6 Pro] BarackMitzvah:
Unfortunately same here. Much of the lag seems to occur when the camera is activated but also will happen intermittently, completely locking the phone up

To be fair as well, I did not try A14 without the kernel as well, so there's a pretty good chance it's unrelated (sorry freak, we're a pain in the butt 😅)

I'd be willing to take logs or provide any feedback necessary to actually determine root cause

Edit: Reflashing the A14 build without the kernel seems to have removed the stutters. Let me know if I can assist in anyway

As always thanks for your work freak!
[Google Pixel 6 Pro] felek73:
Just fyi: now I flashed back stock A14 on Kiri kernel. I love Kiri but on stock kernel scrolling in app is much more smoother. Browser, fb and others are more fluid without any doubt.
[Google Pixel 6 Pro] prokiller1199:
yeah same
[Google Pixel 6 Pro] Rachid.Ala:
I just had a random reboot.

Context : An app was being updated in the background (from play store) and I was about to open another app.
[Google Pixel 6 Pro] ykjae:
I didn't back up the stock kernel on a14 (raven) does anybody have it available?

Sent from Pixel 6 Pro using ReLabs
[Google Pixel 6 Pro] BarackMitzvah:
Just reflash the update
[Google Pixel 6 Pro] ykjae:
That's easy. But someone might just have the stock kernel backup

Sent from Pixel 6 Pro using ReLabs
[Google Pixel 6 Pro] AlDollaz:
Download A14 stock image (https://developers.google.com/android/images#raven) > extract boot.img from zip inside zip.
[Google Pixel 6 Pro] Freak07:
thanks for the logs. :)

unrelated to the kernel.

something in the framework so terribly that the phone decided the only way forward is to start a reboot.

Reboot reason: 0xcafe - User Reboot(S/W Reboot)
[Google Pixel 6 Pro] spr33:
Re: latest kernel + A14 lag.

I too saw lag mostly when loading the camera on A14 with Kiri kernel. Wasn't always there but 90% of the time it was.

I noticed other were using the repainter app so I swiftly uninstalled it to see if it would fix it but it didn't.

I have subsequently flashed stock again and the lag is gone. I will re-flash Kiri to see if it comes back at some point this week and report back.
[Google Pixel 6 Pro] Psfanboy88:
Can confirm: back to stock and lag is gone.
[Google Pixel 6 Pro] Freak07:
I'm still not able to reproduce the issue on my own end.

Judging from the posts here not all are affected. So it might be that something conflicts with the kernel, which some seem to use.

Make sure to not use any mods, magisk module, kernel tweaks, kernel scripts, kernel manager apps, change any kernel settings or other magic stuff etc.

Make sure to not delete the helper module after flashing the kernel.

Then share a logcat and a dmesg when you experience the stutter.

Just reflashing boot.img is not enough to return back to stock.

Instructions on how to return to stock can be found in the first few posts.
[Google Pixel 6 Pro] ho0o0o11111:
A14, clean flash, with magisk (and many modules). 24 hrs passed, no problem here, especially camera. Very smooth. Perhaps it sounds crazy but I feel my P6P is even smoother than my P7P (dirty flash though).

Thanks for the development.
[Google Pixel 6 Pro] ppog:
Only modules [EDIT: apart from helper module] I have are systemless hosts for adaway and universal safetynet fix mod
[Google Pixel 6 Pro] iwearthebelt:
Sounds like you're having a good experience with the kernel on A14. Keep the updates coming as I've been staying with the stock kernel until I hear more reviews without issues. I really like the kernel and @Freak07 work. I'm not that experienced playing around with kernels so I've been going easy until the little bugs are cleared up. I'm patiently waiting until it gets better.
[Google Pixel 6 Pro] ykjae:
It seems the lag issues I had, which were really bad - keyboard would even lag causing my words to be spelled wrong..

I now don't notice any lag. I didn't flash back or anything.

Sent from Pixel 6 Pro using ReLabs
[Google Pixel 6 Pro] DougMG:
Google has done a stealth drop of platform tools 34.0.5. No change log but if you hit download the version is 34.0.5.
[Google Pixel 6 Pro] DougMG:
Just completed a factory install using flash-all with a wipe and it completed as expected.
[Google Pixel 6 Pro] DougMG:
Also there is a new canary version of Magisk.
[Google Pixel 6 Pro] spr33:
Update to my earlier post.

I just flashed Kiri after the (dirty) re-flash of A14 and there is no lag in the camera.
[Google Pixel 6 Pro] Roll3r:
This kernel doesn't respond to Tasker trying to collapse the notification shade. Previous versions did, and stock still does.

edit: also want to add that, with only the helper module and safety net fix enabled, I can immediately see the difference between stock and this kernel - stock is a lot less laggy. I've switched back & forth at least 3 times and the difference is immediately apparent.
[Google Pixel 6 Pro] Freak07:
I don´t think that issues is kernel related. notification panel is framework related. the kernel doesn´t interfere there.

I also flashed back to stock, there´s no regression that´s obvious to me in different apps when scrolling etc. Some apps like twitter are just laggy by default, but that´s the app rather than anything else and the same between stock kernel and this one.

google switched to a new boosting method recently, maybe I need to make some adjustments there, but so far I can´t find a way to reproduce some of the reports here.
[Google Pixel 6 Pro] panic.exe:
Same Setup (modules etc) here. The lag would get so bad sometimes it would lock up the phone. Mostly it would occur when anything accessed the camera it seemed like. I did dirty flash from android 13 to 14 with pixel flasher i don't if it had something to do with that or not. I haven't tried flashing it since doing a clean factory install.
[Google Pixel 6 Pro] Maverick Jester:
So an update on the lag issues.

After flashing back to stock last week, I flashed the kernel again yesterday, and have had absolutely no lag since, even when using Repainter. No changes to the mods used other than the usual updates to Shamiko and Pixel Xpert.

Dunno what the cause of this was initially, but happy that it's gone.

EDIT: Murphy's Law strikes. I experienced really bad lagging in the camera app, and there are a few times a day where I'll wake it from sleep and it's a bit jittery and laggy, but it goes away fairly quickly.

However, it's really bad when quickly swapping between apps using the gesture, to the point that it actually seems to restart the SystemUI.

I'll probably do a clean flash of Android 14 and set everything up again to see if this solves the problem. I don't think a dirty flash after opting out of Android 14 QPR beta was the best upgrade route.
[Google Pixel 6 Pro] Teemas:
Hello!

I don't know what topic to post this message in. But maybe you can help me...

My Pixel 6 Pro's multi-touch only supports 2 touch points after replacing the screen. Unfortunately, I have now moved to another country far from the service center and cannot go there. Otherwise, the screen works very well - the fingerprint works correctly and quickly, the screen refresh rate is 120Hz, high resolution and high-quality color rendition. So I think the screen is original and just needs calibration. Even the cheap $20 not original display of my Xiaomi after replacement even supports 10 touch points. Can I do the calibration myself and what is required for this? Please help me solve this problem😪 🙏🏻🙏🏻🙏🏻

Spoiler content hidden.
[Google Pixel 6 Pro] TheColin21:
I just reflashed my raven with the current A14 stable OTA and did not flash Kirisakura afterwards.

I also had a lot of laggy behaviour before, especially when using the camera (often it was basically unusable).

The device is running much smoother now, although I still think, that A13 with Kirisakura was even smoother.

With this flash I also updated modded USNF from 1.2 to Update 1.3 (not 2.0 as @roirraW "edor" ehT said, that 2.0 would not work completely) and I used the new fastboot 34.0.5 instead of 33. I don't think that either of these changes should impact performance in any way (especially fastboot) but I wanted to mention them.

I never used repainter (which many thought was responsible for the lags) either.

I am looking forward to the first monthly A14 update and hopefully an updated Kirisakura kernel which resolves these performance issues (if they are really caused by it).
[Google Pixel 6 Pro] Rachid.Ala:
Today I experienced the lags, it makes the phone unusable and camera will make the phone completely hang.

How to reproduce it :

1 - Switch to a secondary profile

2 - Switch back to the main profile.

I'm not sure if this happens on stock too, I don't have time right now to go back to stock and test.

When I'll have some free time, I'll test on stock too and give my feedback here.
[Google Pixel 6 Pro] panic.exe:
Try calibrating https://pixelrepair.withgoogle.com/udfps
[Google Pixel 6 Pro] Teemas:
Thanks for the answer, but this is suitable for fingerprint calibration. Or do you mean doing a full reset and software update? Will this cause my phone to become bricked?
[Google Pixel 6 Pro] panic.exe:
run that tool and see if it fixes your issue
[Google Pixel 6 Pro] Freak07:
Nice catch!

There´s an issue with profiles on A14, I never use a secondary profile so it makes sense I never run into it.

Google is investigating Android 14’s multiple profile update bug

The Android 14 update has wreaked havoc on some phones.

www.theverge.com
[Google Pixel 6 Pro] Teemas:
Unfortunately, this did not solve the issue. How accurate is the information displayed by Device Info HW? Is my display original? And how can I check this without disassembling the phone?

Perhaps I need to install a touchscreen driver? Or change the configuration file?

Spoiler content hidden.
[Google Pixel 6 Pro] Freak07:
Update to Raviantha 2.0.2

Hey guys and girls,

So here´s the next update. It´s for stable Android 14 and includes the November Security updates.

Important:

Please note that this release is not for the QPR Beta firmware or dev preview, but the stable android 14 firmware!

Please make use magisk stable if you don´t know your way around bugs and don´t want to actively help debugging magisk development.

You should download magisk stable only from official magisk release site!

There are other small improvements as well. Please check my github for those.

I wish everyone a nice day.

Changelog:

- Update kernel to Android 14 November Security patches

- more changes please look at my github

Download:

Link to Github as XDA attachements are currently down:

https://github.com/freak07/Kirisakura_Raviole/releases/download/Kirisakura_Raviantah_2.0.2/Kirisakura_Raviantah_Oriole-2.0.2_A14_stable.zip

https://github.com/freak07/Kirisakura_Raviole/releases/download/Kirisakura_Raviantah_2.0.2/Kirisakura_Raviantah_Raven-2.0.2_A14_stable.zip

Make sure to keep the ak3 helper module installed in Magisk Manager and do not delete it!

If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.

Make sure to meet the requirements and read the OP as well as the FAQ before flashing.

I wish everybody a great day/evening!

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 6 Pro] AlDollaz:
On Nov update, working great!
[Google Pixel 6 Pro] Rachid.Ala:
Thank you, gonna flash it tonight.
[Google Pixel 6 Pro] TheColin21:
I just flashed it and immediately noticed my camera performance getting worse again :/ I really hoped the update would solve these issues but it seems it didn't.

Also it seems my idea to create a kernel backup with FKM before flashing the kernel and restoring it to go back to stock kernel wasn't a good one.

I am able to boot the device to fastboot mode but when Pixel Flasher tries to boot it into sideload to flash the OTA it hangs at the google logo (just like trying to boot it into recovery or system) where it hangs for a minute (rough guess) and then reboots.

EDIT: I was not able to fix the phone using the OTA. I tried switching the boot slot to get a working flashing environment but it still did not get past the Google logo.

I was able to get the phone working again using a factory image, as this could be flashed using the bootloader and a then working (after the flashes in bootloader) fastbootd.
[Google Pixel 6 Pro] BarackMitzvah:
Unfortunately I experienced the same this month and last

Not sure what we're doing that makes our devices behave similarly

Overall as compared to stock, the phone often felt to have almost microlags very often, intermittently anything that triggered the camera would significantly slow the phone down or outright lock the phone up becoming completely unresponsive for many seconds

Might have to sit this month out too
[Google Pixel 6 Pro] TheColin21:
Sadly exactly my experience...
[Google Pixel 6 Pro] enerGy:
Sorry to see some users having issues. I have been fortunate enough to have the opposite experience. Some micro lags which I felt on stock is gone also browser scrolling etc feels much more fluid. My camera opens up and works fine without any sluggishness. Not bragging that mine works over some users here but just more so how weird this is considering same device etc. I clean flash all my updates and only use safetynet fix plus the youtube module
[Google Pixel 6 Pro] BarackMitzvah:
It only began with this and the previous update (I think the 2.x versions?)

Prior it worked better than stock, incredible stuff
[Google Pixel 6 Pro] enerGy:
Dam that sucks bud. I would ask if you use any modules that might effect it but since the previous versions had worked ok I guess it wouldn't be them in any case
[Google Pixel 6 Pro] snake218:
Same, since previous updates getting lag occasionally. In Nov update the lag is less often and it appears mostly when using the camera.
[Google Pixel 6 Pro] ho0o0o11111:
Updated to Nov security patch with Kirisakura 2.0.2 today. All good here, no obvious lags here or there. I did a clean install of A14 in Oct and didn't have any problem last month so YMMV.

Thanks for developer's Nov update.
[Google Pixel 6 Pro] sgmkrg:
Good day to all. The last update (2.0.0), for 14A, also caused lags and freezes for me, so I had to flash the native kernel. I see that people are having problems this month too and I don’t even want to try, although in the same way I agree that the custom Kirisakura core was 100% better than the stock one. Here is a list of Magisk modules:
[Google Pixel 6 Pro] XSLdesire:
may i ask if you have plan to move to 8 pro? if not, i won't disable the verity cause that's a pain in the ass
[Google Pixel 6 Pro] Zaxx32:
I'd 'buy u a coffee' if you ever decided to include the P6a in ur project...js ;)
[Google Pixel 6 Pro] Utini:
Two coffees if you decide to include the P8P first! :P
[Google Pixel 6 Pro] Legitsu:
can confirm that kirisakura DOES NOT Work on evox A14

bluespark does likely due to erofs / changes in unified pixel device tree / vendor whatnots

will re-test if dev has time/will to switch to the unfied tree
[Google Pixel 6 Pro] Freak07:
custom roms are not supported. sorry, but this one you have to figure out for yourself.

bluspark is extremely close to stock except for a few changes.

I don´t know how a "unified device tree" is related to this.

My kernel tree is "unified" for pixel 6 and pixel 6 pro, however the ramdisk was different between pixel 6 and pixel 6 pro several times in the past. That´s why there are two zips of this kernel.

Other kernels ignore this fact shipping p6 ramdisk for p6 and pro or vice versa.
[Google Pixel 6 Pro] Legitsu:
just testing man I fully expected it not to work as it hasn't since TQ3A A13.B2

I assume the primary problem is erofs or vendor differences

but i recall something about evox having switched to a unifed base for all pixel devices (some upstream shake up on the google asop side)

I don't understand what they are doing so different to cause breakage because on paper it should 'just-work'

shame because your kernel is leaps and bounds more performant then evox's stock

o well can't have it all sometimes

cheers
[Google Pixel 6 Pro] TeeJae360:
How about Cleanslate kernel. Have you tried testing it on evox A14?