Development [Kernel][23.03.2023][Android 13.0.0 Stable]Kirisakura_Raviantah 1.0.1 for Pixel 7/Pro aka "Pantah"

[MarcoReckless]

I'm not sure if this is Kernel or another issue but the last few days I've been having random freezing of the entire phone forcing a reboot. No specific app or action that causes it that I can tell.

I'm probably going to wait for the January Firmware and Kernel update, unless theses get more frequent. Just curious if anyone else is seeing this on their phones?

I've been getting this exact same issue but I'm on the QPR2 beta 1!
Do you have magisk modules installed?
Are you on the december build or the december beta?
I didn't have this issue at first when I was on the december stable but I'm trying to figure out what it is, oh and I'm not using Kirisakura yet so it's certainly not kernel related.


EDIT: I checked github and a few other topics and tried a few fixes, so far I updated Play Services manually via APKMirror and I also forced LTE only (issue on Pixel 5a) using an external app.

EDIT 2: Seems to have rebooted again when I switched from wifi to mobile data, so it's probably related to that, but using LTE only doesn't fix it.

 

[rudolph37]

error: modpost: "pcie_sysmmu_set_use_iocc" [drivers/pci/controller/dwc/pcie-exynos-core.ko] undefined!

Any updates here?? Trying to build pixel7 branch `android-gs-pantah-5.10-android13-qpr1` with default configuration AOSP `build/build.sh` seems to be fcking broken.
Same problem with modpost.

 

[HipKat]

I've been getting this exact same issue but I'm on the QPR2 beta 1!
Do you have magisk modules installed?
Are you on the december build or the december beta?
I didn't have this issue at first when I was on the december stable but I'm trying to figure out what it is, oh and I'm not using Kirisakura yet so it's certainly not kernel related.


EDIT: I checked github and a few other topics and tried a few fixes, so far I updated Play Services manually via APKMirror and I also forced LTE only (issue on Pixel 5a) using an external app, no reboot so far.

I keep mine on LTE all the time because there’s no real solid 5G here and I am on the stable December and not on the beta. The only modules I’m using are the safety net and systemless hosts and James DSP, which I don’t even have enabled actually now that I look

 

[krkhaha]

You were never able to adjust the freqs from kernel manager.
Users shouldn´t play with setting max freqs as they are handled by framework (thermal hal, perf hal, etc) dynamically and all values you´re going to set in kernel managers will get overwritten anyway.
The only way to limit CPU freqs is the battery saver feature from CleanSlate.

Always I did it and always everything was working great. Sorry but this is my pixel and I will decide these things. You should not impose your settings. I used that on lower frequency and was really great. So how can I change CPU freq? I can't see that in kernel manager.

 

[Freak07]

Always I did it and always everything was working great. Sorry but this is my pixel and I will decide these things. You should not impose your settings. I used that on lower frequency and was really great. So how can I change CPU freq? I can't see that in kernel manager.

It doesn´t matter if you´re running completely stock or this kernel. You are and were not able to restrict maxiumum cpufreqs with kernel managers as the settings get overwritten by the framework after a while.
If you choose a lower max frequency in a kernel manager (e.g. exkm or fkm) it seems to stick and once the first app is launched, the powerhal overwrites the maximum you previously set by the kernel manager to the highest one possible. That´s just one of many examples that will overwrite your settings.
If you think you were able to do this, it was just the UI of the kernel manager tricking you.

You can only hard limit CPU Freqs with the CleanSlate battery saver feature. You can access that via the CleanSlate config app (you can find that in the CleanSlate thread). It was already covered in great detail here few days ago.

 

[Ivixmax]

It doesn´t matter if you´re running completely stock or this kernel. You are and were not able to restrict maxiumum cpufreqs with kernel managers as the settings get overwritten by the framework after a while.
If you choose a lower max frequency in a kernel manager (e.g. exkm or fkm) it seems to stick and once the first app is launched, the powerhal overwrites the maximum you previously set by the kernel manager to the highest one possible. That´s just one of many examples that will overwrite your settings.
If you think you were able to do this, it was just the UI of the kernel manager tricking you.

You can only hard limit CPU Freqs with the CleanSlate battery saver feature. You can access that via the CleanSlate config app (you can find that in the CleanSlate thread). It was already covered in great detail here few days ago.

Cleanslate app works with default kernel of january to use battery saver mods?or we have to wait for your kernel realese? Thanks in advance

 

[Freak07]

No kernel source for january out yet.

I went ahead and flashed the current release on January firmware, it booted fine with no issues so far.
Powerhint module also needs no update.

Should be fine to flash. If you're not in a hurry I'll try to update the kernel tomorrow if the source is released.

 

[Freak07]

Cleanslate app works with default kernel of january to use battery saver mods?or we have to wait for your kernel realese? Thanks in advance

No, it does not work with the default kernel as the CleanSlate features rely on kernel changes.

Check one post above this as well.

 

[Ivixmax]

Thanks for the info master.Apreciate it

 

[krkhaha]

It doesn´t matter if you´re running completely stock or this kernel. You are and were not able to restrict maxiumum cpufreqs with kernel managers as the settings get overwritten by the framework after a while.
If you choose a lower max frequency in a kernel manager (e.g. exkm or fkm) it seems to stick and once the first app is launched, the powerhal overwrites the maximum you previously set by the kernel manager to the highest one possible. That´s just one of many examples that will overwrite your settings.
If you think you were able to do this, it was just the UI of the kernel manager tricking you.

You can only hard limit CPU Freqs with the CleanSlate battery saver feature. You can access that via the CleanSlate config app (you can find that in the CleanSlate thread). It was already covered in great detail here few days ago.

I tried that app and all the time when I setup is for GPU after some time everything was going back to normal. I mean don't keep that settings.

 

[Freak07]

Update to 1.2.2

Hey guys and girls,

So here´s the next release. January source drop did not contain anything new for this project except a small kvm patch.

@HipKat and a few others reported random freezes. While I haven´t faced them at all and I´m not 100% sure what´s causing them, I reverted some of the patches from QPR2 Beta, which I merged in the previous update as a precautionary measure.
It´s very unusual for kernel issues to surface after the kernel ran fine for a few weeks and all reports coming at roughly about the same time for only very few users. So either it was something in the December update that´s triggering very rarely for some and the timing is coincidence, a server side update from google/play services update or similar or it´s caused by some of the kernel changes I pulled in from QPR2 beta in the previous update.
I reverted those changes a few days ago as a pre-caution, and it seems QPR2 might have the same issues running stock kernel as well. Unfortunately this doesn´t rule out anything as it still could be all of the three possibilities above. Additional to that, browsing XDA or reddit and it seems freezes can happen on completely stock firmware too.

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

The kernel is made for stable A13 firmware, not beta.

I wish everyone a nice day.


Changelog:

- Linux-Stable bumped to 5.10.161
- improvements to MGLRU
- bump f2fs to latest f2f2 stable state
- improve GC from f2fs
- fixes/improvements to to memory management
- other fixes please check github



Download:
Attached to release post as AFH is currently down.
I´ll push to AFH once it´s back up.

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

Make sure to update or keep the powerhint module installed via Magisk Manager!


If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_kernel_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

 

[rage302]

...flashed V1.2.2 over January Firmware (Cheetah) via KernelFlasher ...All good so far.
THX @Freak07

 

[binoysankar]

Hello @Freak07, I too had random freeze on the previous version of your kernel couple of times. I remember one time how it happened was opened youtube > switched to full screen mode > zoomed to fit screen > took a screenshot and tried to edit that screenshot and when editing i tried to zoom in to crop the pic and the phone freezed. I waited for almost 5 min and it didn't recovered. Need to force restart the device. As i wanted to report this behaviour next time the same steps worked fine. So its very very rare case freezing happened to me.

 

[Not_Purgatory]

@Freak07

Do you know if Google have added anything that's similar to the ULPS stuff for the Pixel 7 / 7 Pro screen panels that was possible to enable and utilize on devices like the Pixel 3 (XL) and Pixel 4 (XL) in the past?

 

[creezalird]

only had 1 time complete freeze while browsing FB lite, but it could be because I set the battery saver to 3 in cleanslate. Afther changed to 2, so far no freeze at all

 

[HipKat]

@Freak07

Last night, shortly after I flashed the newest firmware update, I assume that overrides the kernel with the stock kernel, my phone froze up and did a forced reboot so I’m assuming the kernel doesn’t have anything to do with it. I have the clean slate apps and EXKM installed, but I’ve never set any settings on any of those apps so they’re just at their defaults.

I’ll see how this goes during the day today, those random freezing episodes, have absolutely no rhyme or reason to them and they’re not that often. The one last night was the first one I’ve had in probably two days.

When I get home from work, and I have more time, I’m going to do a pack up, and then a factory reset and re-flash the newest firmware, restore my apps, and flash the updated kernel and see what happens

 

[Freak07]

@Freak07

Last night, shortly after I flashed the newest firmware update, I assume that overrides the kernel with the stock kernel, my phone froze up and did a forced reboot so I’m assuming the kernel doesn’t have anything to do with it. I have the clean slate apps and EXKM installed, but I’ve never set any settings on any of those apps so they’re just at their defaults.

I’ll see how this goes during the day today, those random freezing episodes, have absolutely no rhyme or reason to them and they’re not that often. The one last night was the first one I’ve had in probably two days.

When I get home from work, and I have more time, I’m going to do a pack up, and then a factory reset and re-flash the newest firmware, restore my apps, and flash the updated kernel and see what happens

Thanks for the report!
Yes flashing new firmware will indeed overwrite everything and you're ending up on the stock kernel.
Seems more and more like it's just some odd bug google introduced in the December release, that also affects the QPR2 firmware. (If those are all the same issues)

@Freak07

Do you know if Google have added anything that's similar to the ULPS stuff for the Pixel 7 / 7 Pro screen panels that was possible to enable and utilize on devices like the Pixel 3 (XL) and Pixel 4 (XL) in the past?

The displaY driver is completely different as P6 and P7 devices are no longer QCOM based.
But there's kind of an equivalent in the source there too. The Samsung driver from P6 and P7 in general is probably better than the QCOM one, especially for Samsung displays.

 

[JakeDHS07]

Is the module meant to be the same? The January post is linking the v4 from December

 

[TotallyAnxious]

Is the module meant to be the same? The January post is linking the v4 from December

The module doesn't always get updated.

 

[i5lee8bit]

@Freak07

Last night, shortly after I flashed the newest firmware update, I assume that overrides the kernel with the stock kernel, my phone froze up and did a forced reboot so I’m assuming the kernel doesn’t have anything to do with it. I have the clean slate apps and EXKM installed, but I’ve never set any settings on any of those apps so they’re just at their defaults.

I’ll see how this goes during the day today, those random freezing episodes, have absolutely no rhyme or reason to them and they’re not that often. The one last night was the first one I’ve had in probably two days.

When I get home from work, and I have more time, I’m going to do a pack up, and then a factory reset and re-flash the newest firmware, restore my apps, and flash the updated kernel and see what happens

Curious, shortly after rebooting, can you go to settings and try to open Tips and support? It's all the way at the bottom, right below About Phone. See if it opens or immediately crashes / kicks right back to settings.

Or open Google Photos and open a pic that has geotagging. Does it show the location on map or just say "Google Play services are updating"? This also goes for any app that uses the maps API (e.g. Ecobee in the geofencing option). Maybe also Chrome mysteriously isn't sync'ed anymore after every reboot. GPay also wouldn't fully load while in this state, and several Pixel Buds options would be missing.

It's a super long shot, but I had a weird problem since day 1 that would cause all sorts of weird issues (spanned several factory resets, even after exchanging the whole device with Google, more factory resets, not restoring from any backup i.e. setting up as new device entirely, etc), and I only bring this up because I remember someone mentioning GMS as a possible culprit for this weird recent freezing episode people are having lately. Curious if you happen to have stumbled onto the same problem, in which case the above would happen. The biggest annoyance was that Chrome would lose sync after every reboot. If I was lucky, my phone would return to a normal state randomly after 24-72 hours (as if Google Play services finally "settled" or something) - if it didn't lock up or I had to reboot before then.

I did get it fixed finally about 3 weeks ago and it hasn't come back. Could be placebo, but random lock ups have also gone away since then (although it didn't happen nearly as often as people are describing). But I won't clutter this thread more unless someone else confirms they're having this exact, strange problem that seemed to only affect me somehow for the longest time.