Development [Kernel][07.01.2023][Android 13.0.0 Stable]Kirisakura 1.2.3 for Pixel 7/Pro aka "Pantah"

[Freak07]

You mean this is an issue or bug in the kernel?

I don't have this issue. Tested this couple of times in a call. I am not seeing in delay for screen wakeup nor screen off during calls.
Wondering why its all good for me when you mentioned you found the issue.

Thanks for the report.
Problem is @tbalden and me both don't own a pixel 7 regular.

Seems to be only affecting regular pixel 7. No issues on pixel 7 pro. So if you're on P7 pro, you'd be not affected.

If you're on P7 regular and you don't use any cleanslate features that depend on screen state, you might be unaffected too.

If you're on regular P7 and you use those cleanslate features and don't face any issues, the issue might also be related to another mod.
We can't say for certain, but @tbalden might have already found a fix as it's caused by a lock, that could be blocking the touch driver.

I'll merge this fix in the next update, but since I don't have P7 regular, testing needs to be done by someone else and that makes the process slower.

edit: ninjaed by @tbalden

 

[Texan1]

My banking app has stopped working since flashing the latest version of Kiri. Click on icon and won't open. Have cleared storage and cache, no difference. Works fine on stock and Despair kernel. P7 Pro.

 

[Abdu55799]

You need to use the aosp kernel build environment to build my kernel as well, just as described here. Replace the relevant repos in the environment with the ones you find on my github.



Copy paste from the first post:

Requirements

- vbmeta flags for verity/verification disabled (this requires a wipe if you´re coming from stock with those flags enabled), check the FAQ for information on how to do this
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment so you can flash back to stock in case something goes wrong
- working magisk environment (a device rooted with latest magisk stable in case you want to be absolutely safe)
- IMPORTANT: Unrelated to the kernel, but update both slots of your phone to A13 before you flash anything to your device!
- read the first and second post, there's a lot of valuable information



How to flash the Kernel:
1a. Make sure you tick all the requirements above
1. Download the kernel.zip (unified for both devices) and the correct powerhint module depending on your device (Pixel 7 = panther || Pixel 7 Pro = cheetah)
2. Flash the powerhint module via magisk manager as you would any other magisk module! Make sure to flash the latest one. It will be mentioned in the release post if there´s an update.
3. Flash the kernel.zip via EXKM, FKM or kernel flasher. Root will be preserved.
4. Reboot and profit.


Search the forum for guides or check the FAQ as the question is already answered there.
Flashing any full firmware will just replace all modified partitions and you´ll end up on the new firmware.

thanks for reply. so I have to root the phone and flash the kernel again after every monthly security update. sorry for bad english

 

[HipKat]

No uninstalling old powerhint module first?
I tried uninstalling the old module first and rebooting before installing the new one, and for a bit there magisk was complaining that it had lost root.
But after reinstalling the app it was all good again.
Had no issues installing the new kernel with Kernel Flasher though.

That's what I did - uninstalled the old module, rebooted, flashed the new one, rebooted, then Kernel with another reboot

 

[Freak07]

thanks for reply. so I have to root the phone and flash the kernel again after every monthly security update. sorry for bad english

Yes.

Nice! Will we see these improvements also on your series 6 kernel?

Yes, for the most part.

My banking app has stopped working since flashing the latest version of Kiri. Click on icon and won't open. Have cleared storage and cache, no difference. Works fine on stock and Despair kernel. P7 Pro.

If you tell me the name of the app and provide logs as described in the FAQ I can at least look into it.

 

[xiangyou]

You need to use the aosp kernel build environment to build my kernel as well, just as described here. Replace the relevant repos in the environment with the ones you find on my github.



Copy paste from the first post:

Requirements

- vbmeta flags for verity/verification disabled (this requires a wipe if you´re coming from stock with those flags enabled), check the FAQ for information on how to do this
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment so you can flash back to stock in case something goes wrong
- working magisk environment (a device rooted with latest magisk stable in case you want to be absolutely safe)
- IMPORTANT: Unrelated to the kernel, but update both slots of your phone to A13 before you flash anything to your device!
- read the first and second post, there's a lot of valuable information



How to flash the Kernel:
1a. Make sure you tick all the requirements above
1. Download the kernel.zip (unified for both devices) and the correct powerhint module depending on your device (Pixel 7 = panther || Pixel 7 Pro = cheetah)
2. Flash the powerhint module via magisk manager as you would any other magisk module! Make sure to flash the latest one. It will be mentioned in the release post if there´s an update.
3. Flash the kernel.zip via EXKM, FKM or kernel flasher. Root will be preserved.
4. Reboot and profit.


Search the forum for guides or check the FAQ as the question is already answered there.
Flashing any full firmware will just replace all modified partitions and you´ll end up on the new firmware.

And another question, I am learning to build AOSP of android 13, and my device is Pixel7. I download the 7's AOSP repo from source.android.com and build successfully, and "fastboot flashall -w" -------- just follow the steps as source.android.com said, but, after all this done, everything seems OK， except the device will never boot up ...

 

[Schroeder09]

Does this kernel make it so greenify and aggressive doze magisk modules aren't needed?

 

[feligoni]

Any chance of updating with latest Clean slate fixes for p7?

 

[Freak07]

Any chance of updating with latest Clean slate fixes for p7?

Do those fixes in the latest CleanSlate update resolve the issue with touch not registering after proximity sensor was used for you on regular P7?

 

[Not_Purgatory]

Does this kernel make it so greenify and aggressive doze magisk modules aren't needed?

 

[Schroeder09]

A simple "yes" or "no" would haveb actually been helpful and taken the same amount of time

 

[Not_Purgatory]

A simple "yes" or "no" would haveb actually been helpful and taken the same amount of time

Greenify haven't been needed since the 9.0 days and it's the same about the aggressive Doze stuff tbh.

 

[fuadhdmini]

anyone succeeded installing the new update with the qpr1 beta3.1?

i tried flashing normally when i did with stable stock ended uo with bootloop

 

[Schroeder09]

Greenify haven't been needed since the 9.0 days and it's the same about the aggressive Doze stuff tbh.

What about this? Google gms and Instagram are keeping my phone awake according to BBS.

[MODULE] Universal GMS Doze

Universal GMS Doze Overview: - Optimized and adjusted Google Play services. - Support API 23 or later. - Support Magisk Live or Custom Recovery installations. Contents: - Base extensions module: 1.8.4 (0830) code: 184 Credits: - @topjohnwu /...

forum.xda-developers.com

 

[fuadhdmini]

anyone succeeded installing the new update with the qpr1 beta3.1?

i tried flashing normally when i did with stable stock ended uo with bootloop

Ok. Now I noticed this

"Kernel is compiled for stable A13, not A13 QPR Beta!"

 

[thefinger]

What about this? Google gms and Instagram are keeping my phone awake according to BBS.

[MODULE] Universal GMS Doze

Universal GMS Doze Overview: - Optimized and adjusted Google Play services. - Support API 23 or later. - Support Magisk Live or Custom Recovery installations. Contents: - Base extensions module: 1.8.4 (0830) code: 184 Credits: - @topjohnwu /...

forum.xda-developers.com

Did you go through the usual force stop, clean cache and data and restart phone? Are you on a beta on any of those 2? What other magisk modules do you have going on?

 

[Lughnasadh]

What about this? Google gms and Instagram are keeping my phone awake according to BBS.

[MODULE] Universal GMS Doze

Universal GMS Doze Overview: - Optimized and adjusted Google Play services. - Support API 23 or later. - Support Magisk Live or Custom Recovery installations. Contents: - Base extensions module: 1.8.4 (0830) code: 184 Credits: - @topjohnwu /...

forum.xda-developers.com

Try restricting battery for Instagram. Google gms could be anything as lots of apps use this. Honestly, none of these doze enforcing/hibernating/battery restricting apps are needed on Pixels and can do more "harm" than good at times. Maybe post your BBS idle dump in the BBS thread to get a better handle on what is keeping your phone awake as we're starting to veer off topic here since this really isn't kernel related.

 

[Lughnasadh]

@Freak07 Do you know if this issue was ever fixed (or the commit reverted) in the stock kernel for this device or the Pixel 6 series?

 

[Freak07]

@Freak07 Do you know if this issue was ever fixed (or the commit reverted) in the stock kernel for this device or the Pixel 6 series?

If I recall correctly that bug never triggered on 5.4 kernels and higher. So it might not exist there, due to the f2fs implementation being a bit different /more recent.

But I don´t know a 100% if it was fixed by changes done to magisk or f2fs.
Since requests for Pixel 3a and 4a (which I never supported but users asked from time to time if I could compile a kernel with said commit reverted )ceased slowly over time, it might be that magisk doesn´t trigger the bug any longer since the big rewrite and it´s fixed on 5.4 and upwards in f2fs as well.

Either way I don´t think it´s a problem on pixel 6 or pixel 7. I haven´t run into this issue at least.
Why do you ask?

 

[Lughnasadh]

If I recall correctly that bug never triggered on 5.4 kernels and higher. So it might not exist there, due to the f2fs implementation being a bit different /more recent.

But I don´t know a 100% if it was fixed by changes done to magisk or f2fs.
Since requests for Pixel 3a and 4a (which I never supported but users asked from time to time if I could compile a kernel with said commit reverted )ceased slowly over time, it might be that magisk doesn´t trigger the bug any longer since the big rewrite and it´s fixed on 5.4 and upwards in f2fs as well.

Either way I don´t think it´s a problem on pixel 6 or pixel 7. I haven´t run into this issue at least.
Why do you ask?

Some people are reporting (near the end of that thread and I guess on Reddit as well, for what it's worth) that they are having system freezes on the Pixel 7 series and they believe it may be due to having Systemless Hosts mod enabled and this bug. I haven't experienced this bug since, oh I don't know, my Pixel 2 XL or 4 XL days maybe?, but used your kernel that had that commit reverted.

I've had the Systemless Hosts mod enabled on my Pixel 6 Pro and on this device and have never experienced a system freeze.

Just thought you might know off the top of your head if this bug may still be an issue. Thanks for the reply.