yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Freak07:
See my last reply:

no, min cpufreqs are dynamically changed by the powerhal, the thermal hal and other mechanisms in the framework and will just overwrite other values.

It's intentional minfreqs are changed dynamically and I'm not going to implement a function to overwrite this behaviour.

It would be detrimental to performance.

E.g.:

Minfreqs are boosted during interaction, app launch, fingerprint unlock etc.

When no interaction is happening, minfreqs are set to lowest value.

That's part of the code to restrict max cpufreqs and "overrule" power-hal, thermal-hal and framework boosts. Those are the three levels you can choose from.

See the second part of my last reply:

you can restrict maxfreqs via cleanslate battery saver accessible via the cleanslate config app.

Maxfreqs can be capped, because that makes sense.
[Google Pixel 6 Pro] Panchajanya1999:
Hi @Freak07 ,

Can you confirm whether disabling vbmeta is necessary for flashing kernel on pixel 6 series now? I cam across guys who are reporting that flashing kernel (both fastboot/d and magisk) is resulting is soft brick with stock vbmeta.

Can you kindly shed some light on it since its not so practical to disable verity in vbmeta.
[Google Pixel 6 Pro] Freak07:
You don't flash the kernel in magisk that's not working. You don't flash this kernel via fastboot/d, because that's not following the instructions either.

If you follow the instructions and requirements flashing this kernel works fine on pixel 6 series with vbmeta flags enabled as the hashes get patched during the process of flashing the kernel.zip.

If you flash the images via fastboot/d that will never happen and you'll not be able to boot due to avb protection.
[Google Pixel 6 Pro] Panchajanya1999:
by magisk i meant using FKM/EXKM, sorry a little mishap. Thank you anyway.
[Google Pixel 6 Pro] Freak07:
All good, just wanted to be precise so nobody else gets confused. :)

Those should work fine as well 👍 or use the excellent kernel flasher app from @capntrips , it's open source and available here on XDA.

Let's you easily backup all relevant partitions.
[Google Pixel 6 Pro] Freak07:
Thanks for the log, something is changing your ZRAM size from 3 to 4 GB.

Or rather it sets the size from 3GB to 0GB, then from 0GB to 4GB.

Do you use any mods, tweaks, optimizers or set that yourself in EXKM? (just because I see a selinux denial from exkm, just before the ZRAM stuff happens)

Please try without changing ZRAM size. The problem is EXKM does that very very late during boot, which might cause the issue you experienced.

I came across several devices that experience crashes when ZRAM size is changed that way after ZRAM was set up initially by the system and pages were swapped out already. It shouldn´t be done that way really.
[Google Pixel 6 Pro] Freak07:
okay, I checked all the logs previously shared.

All of those that crash right after boot since I said the trace of the crash changed with this issue have ZRAM size changed. the other logs don´t reach that far back, but I´m suspecting something similar.

Shame I didn´t catch that previously. 😁

So to everyone, please do not use anything that changes ZRAM size or alters ZRAM behaviour (kernel managers, magic kernel tweak scripts, other mods, mystic kernel improve apps etc), flash the latest test shared here and post the relevant logs mentioned in case of a crash:

https://xdaforums.com/t/kernel-21-0...pixel-6-pro-aka-raviole.4358435/post-88557817
[Google Pixel 6 Pro] michaely123:
I just put the ZRAM to stock. I guess I set that up a long time ago with EXKM, but I still ended up crashing. Thanks again @Freak07
[Google Pixel 6 Pro] digger16309:
I always flash with EXKM, but then disable it to prevent its old settings getting applied. But I think I haven't re-booted after that in the past. The ZRAM is set at 3GB but it could be something else in EX that has triggered it.
[Google Pixel 6 Pro] Justarandomguy:
I don't want to talk too soon but with last update phone did not crash a single time, usually it crashed at least once a day, or after a reboot it was almost 50/50 chance it will crash in a minute, using it since updated, rebooted few times (low battery, going to sleep and so, nothing kernel related) and 0 crashes still. Didn't update or change anything, so it's all kernel related, as always, thanks for your amazing job, you made this device way more battery efficient and so smooooooth :)
[Google Pixel 6 Pro] falsehhhhh:
No reboot
[Google Pixel 6 Pro] Freak07:
thanks again for the log! :) please check the next post.
[Google Pixel 6 Pro] Freak07:
Test Release 1.0.5_3

Hey everyone,

so it seems the probability of the crash is greatly reduced and since the last test the trace changed again, which is good, because it means I´m on the right track.

Additionally to that it seems most users that were affected by the crash changed their ZRAM size via EXKM or any other kernel app. I think this was probably the main cause for the issue to get triggered in the first place.

Thanks to @michaely123 ´s log that shed some further light onto it, here´s the next test build.

Thanks to everyone for flashing all those tests, keeping up with me, providing logs and feedback! all of that is valuable to me, since I still can´t reproduce the crash on my end.

So I´d like to ask, just like the last time:

I´d appreciate if as much users as possible could flash and run this. (especially @michaely123 :) )

I´d appreciate if those that suffered regular crashes before could flash as well.

In case you get a random reboot please zip up and share the contents of sys/fs/pstore once you phone booted up again just like so many did before, which is great for me to see!

Thanks to everyone flashing those tests and providing logs in case of a crash, you guys absolutely rock!
[Google Pixel 6 Pro] falsehhhhh:
1.0.5.1 Need to upgrade to 1.0.5.3 ？
[Google Pixel 6 Pro] Freak07:
Probably better yeah :)
[Google Pixel 6 Pro] michaely123:
Running 1.0.5_3. I'm not sure if this log will help, as the phone rebooted 3 hours ago.

*Update*: Second file just happened right now.
[Google Pixel 6 Pro] digger16309:
No reboots on the last two test releases and mine always occurred within the first 10 minutes of the first boot and none thereafter. I'm convinced mine were an issue with EXKM settings applied at boot that caused a crash.
[Google Pixel 6 Pro] cyberbbc:
my phone heats up all the time and loses charge pretty quickly, unlike the stock core. I don't quite understand why, it was much better on the early version of the kernel.

such a temperature while I was typing ....
[Google Pixel 6 Pro] Freak07:
It´s not related to the kernel.

It´s probably an app or a service always running in background.

You can check for this via top command in terminal. Please search the thread, you´ll find the instructions.

Or your ambient temperature is 10°C higher, because it might be summer where you live now.
[Google Pixel 6 Pro] Rachid.Ala:
Some app might be preventing your phone to deep sleep.

Check the wakelocks with betterbatterystats app or similar. You'll find detailed instructions if you search betterbatterystats thread
[Google Pixel 6 Pro] Freak07:
This is complete nonsense.

The steps to go back to stock are described on the FAQ.

Changing the CPU governor to any other than the default will introduce a lot of breakage in the framework and essentially cripple the phone.
[Google Pixel 6 Pro] ada12:
using conservative governor is very bad idea ! its kill literally Energy Aware Scheduling and you introduce many issue ...

also change to schedutil is even no recommanded google have improved scheduler , governor is called "sched_pixel" in settings see https://github.com/freak07/Kirisaku...1ab44e8336/drivers/soc/google/vh/kernel/sched
[Google Pixel 6 Pro] digger16309:
Do you even have this device or use this kernel?

Thousands of us have no heat issues with this kernel for over 18 months. If we did, the thread would be flooded with such complaints. Of course it's a non-kernel user issue.
[Google Pixel 6 Pro] ada12:
No conservative gov sets the CPU frequency depending on the current usage.

schedutil (* pixel_sched ) is lot more adapted for multi socs like Tensor .

If you have issue don't spam dev please...
[Google Pixel 6 Pro] majorfigjam:
I respectfully suggest that if it is so important to you, that you should do it yourself!

The rest of us here just appreciate Freak07 for the amazing results we get from using this kernel, seemingly without the overheating issues you face.
[Google Pixel 6 Pro] Rachid.Ala:
At least the powerhal and the scheduler assume that pixel_sched is used as a governor.

You should check what app/service is hogging your CPU if temps are very high to your liking.

If you want to prevent your device from using the highest frequencies, you can try using CleanSlate battery saver instead.
[Google Pixel 6 Pro] ada12:
no he have not to get Spammed its great dev. you want compile your kernel ? okey do it. Im friendly guy I sent you in pm guide for compile yourself but no spam here or me in pm if you get problems in compiling / bootlop / bug ...
[Google Pixel 6 Pro] Utini:
Is there anything in the Kernel or configuration/companion app that speeds up the "deep sleep" state?

I have only 60% deep sleep which is caused by very long activation times to get into deep sleep after the screen is off. I do not know yet how to trouble shoot what is preventing my phone from going into deep sleep faster but I was hoping that the kernel or companion/configuration can enforce a faster deep sleep state?

During a night: 98% deep sleep with like 2% battery loss

During a work day: 50-60% deep sleep
[Google Pixel 6 Pro] Freak07:
as a short answer: no and you probably don´t want that.

a longer answer: the kernel can´t know what´s happening on your phone or what you´re doing with it.

If there´s nothing to be done from any app/service or other processes the system/framework "asks" the kernel to go to sleep and it will do so, eventually entering deep doze (where the system/framework also limits network traffic and wakeups etc). that´s what´s happening during night and it works fine for you.

during the day if you actually use your phone the system/framework requests the phone to wake up/wakelocks. depending on your location you might have bad mobile reception, switch network often, bluetooth devices connected, wlan connected, you receive notifications, listen to music/podcasts, make calls, have a bluetooth watch connected etc....

If you listen to music/podcasts or call someone while screen is off during the day, the phone can´t deep sleep during that. If you receive notifications the phone won´t deep sleep. If you receive notifications while on bad network the phone will stay awake for longer. If you´re constantly switching networks the phone won´t sleep as much as when it´s stationary overnight and enters deep doze if you don´t touch it for 20 minutes.

Then there can be apps that keep the phone awake for longer as necessary when it should be sleeping (there can be many reasons, sloppy coding, "spying", collecting information, making sure you really receive notifications), but again the kernel can´t know that. To get back to the beginning, you wouldn´t want the kernel to always force deep sleep as your phone would not function properly then.

Depending on what you´re doing 60% deep sleep can mean, let´s say your day spans 15 hours from 7-22. That means your phone sleeps for a bit less than 10 hours of that entire 15 hours. If you have 3 1/2h of SOT, that leaves your phone awake for 1 1/2 hours - 2 hours. If you make some calls, get notifications, switch screen on/off regularly (as opposed to never during the night) that´s plausible if one of the factors above apply (bad network, switching networks, lots of apps syncing, bt devices connected)

It all depends on your personal usage patterns and the factors I described above. If the phone is used for extended periods of time and then just kept idle for extended periods of time it´ll end up with more "deep sleep", as opposed to checking it every few minutes for a minute reply to texts etc.
[Google Pixel 6 Pro] Utini:
Uh thanks for the detailed response.

I am definitely prone to bad phone signal on my office location but I am also always connected to good WiFi signal.

So deep sleep does limit network traffic meaning telegram/whatsapp/signal/fairmail/etc will all not work as expected anymore? And if I have them "not optimized" they will keep working but prevent the system from going into deep sleep?

I know this is not kernel and topic related but:

Would "Naptime" or "Greenify" help with putting the system into deep sleep when using any "spying" or bad coded apps? Or would there be any "reasonable" way to figure out if I have any of such apps?
[Google Pixel 6 Pro] xflowy:
guys. i just saw in gsam app, that my phone does only go in light doze and not deep doze. is this app related (and just does not work properly with the 6 pro) or is sth wrong here?
[Google Pixel 6 Pro] Freak07:
if your device deep sleeps it does deep sleep. if an app or a service wants to work it needs to request a wakelock, waking the device. that´s the simple explanation.

You´ll see it as an alarm, a wakeup , a partial wakelock or a kernel wakelock in bbs, similar apps or battery historian.

Some of those wakelocks belong together, if you´re device is sleeping while connected to wlan, an app or the system wakes up and needs wifi connection, you´ll see a bunch of wakelocks. wifi, activity manager, a wakelock for the app, a wakelock to wake up the ril.

If you really want to figure out what´s happening you need to invest a lot of time, now that BBS is not fully functional. You can try to tackle it from different fronts. Disable mobile network entirely while you´re in the office and solely rely on wlan. you can try to uninstall apps one by one and see if that makes a difference.

You can try to change your usage pattern. Let your phone sleep at the office without touching it for 3 hours there and check deep sleep then.

I don´t know anything else besides BBS or battery historian. I generally don´t like to use apps such as GSAM or those other monitors, but I did when I got the pixel 6 pro as BBS wasn´t working properly. I also don´t use monitors for active and idle drain such as in FKM or EXKM.

But again, it doesn´t sound that bad, if your usage is similar to what I described above.

But this derails this thread further and further. It´s unrelated to the kernel.

I personally don´t use apps like naptime or greenify. I gladly trade a few less % of deep sleep over day, so that I don´t get delayed or missed notifications.

let´s please move this discussion out of this thread. It´s getting more and more unrelated to this kernel and the subject of this thread.

I don´t mind occasional off-topic or explaining certain things (even multiple times), but this isn´t the right place for it.

I answered basically the same thing to @Utini in the thread that was created here:

https://xdaforums.com/t/gsam-batter...ting-me-from-deep-sleep.4368947/post-86026807
[Google Pixel 6 Pro] Texan1:
Hey there @Freak07 , will you wait for the December update next week before releasing a new kernel? Cheers mate.
[Google Pixel 6 Pro] Nezorflame:
I can confirm that after updating the Companion app to the version 3.3.3 (162), flag Enable Proximity Sensor Screen on is now visible. After setting it to off and rebooting, it's not locked to 60Hz anymore.

Thanks again!
[Google Pixel 6 Pro] Freak07:
yeah I guess next update will drop alongside whenever december source code drops. :)

as of right now I´m just enjoying the device and the kernel in its current form.

thanks for reporting back, glad it´s working fine now.

hats off and thanks to @tbalden for the quick fix! :)
[Google Pixel 6 Pro] milestoneman:
Is this kernel beneficial for battery life?

I've not used a kernel for years but feel the 6 Pro needs some tweaking

Will my gpay still work or do I need to do anything extra?

Cheers
[Google Pixel 6 Pro] Freak07:
every user has their unique usage patterns, so nobody will be able to definitely answer the question for you.

The only two things that definitely will improve drain:

take a look at the first post. If your usage includes listening to music/podcasts with screen off during the day, the provided magisk module, which tunes the powerhal will improve battery drain a bit.

in the CleanSlate config app, you´ll find a batterysaver that restricts max cpufreqs at 3 chooseable levels, which will improve battery drain as well. (if you´re willing to restrict max cpufreqs during regular usage.)

Battery life on this phone is pretty stellar to me though, so I have nothing to complain. :)

edit: gpay will stop working as soon as you unlock your bootloader. that´s unrelated to the kernel.

safetynet can be fixed, via other means though so you can get it working after unlocking, which is a requirement to flash the kernel! :)
[Google Pixel 6 Pro] Texan1:
What we do know is that we are lucky to have the great man @Freak07 developing a kernel for our devices... he knows his stuff! 👑
[Google Pixel 6 Pro] milestoneman:
Thanks, I do listen to lots of podcasts so this is appealing
[Google Pixel 6 Pro] Nekromantik:
If you want to use GPay on unlocked phone then you need to root and use magisk and saftynetfix to make gpay work. there are threads on this already on forum.
[Google Pixel 6 Pro] rafik25:
Hello a noob question after installing this kernel, i lost root (magisk) any ideas plz ?
[Google Pixel 6 Pro] DanielF50:
Of course you did - you flashed a boot.img that doesn't have Magisk installed?

Looks like you missed the above step in the OP. Patch the kernel's boot.img in the Magisk app and flash it again to recover root.
[Google Pixel 6 Pro] rafik25:
Ok i missed patching kernel's boot.img to to keep root. thx a lot bro ;)
[Google Pixel 6 Pro] vlubosh:
will this kernel work on Proton early acces rom? or it could be problem with DTBO and Vendor? thank you.
[Google Pixel 6 Pro] Prey521:
Water isn't wet lol
[Google Pixel 6 Pro] phaino00:
And technically, the sky is transparent (insert bad joke laugh).
[Google Pixel 6 Pro] Lughnasadh:
And just to add a bit related to my own experience, blocking those 2 WLAN-related wakelocks seems to help a bit with my idle drain (maybe a decrease of .1% compared to stock?) as well as adding roughly 9% to my deep sleep percentage.
[Google Pixel 6 Pro] majorfigjam:
If it helps:

https://source.android.com/docs/setup/build/building-kernels

I'm sure we all look forward to seeing your efforts shared here
[Google Pixel 6 Pro] enerGy:
And this is why you have a reaction score of 73 compared to his 21k, geez even I have more and I know **** all :ROFLMAO: Enuff said really. Guess I know who they will take advice from :unsure:
[Google Pixel 6 Pro] ada12:
"Suggest ssg merge " have you read feature kirisakura kernel in page 1 ?
[Google Pixel 6 Pro] chml17l:
Crash/reboot when using camera. /storage/emulated/0/Download/Kirisakura_Raviantah_Raven-1.0.5_3_A13_stable.zip
[Google Pixel 6 Pro] Justarandomguy:
No crash for me since the two last releases, working great
[Google Pixel 6 Pro] falsehhhhh:
《If you disabled verity/verification on your device 》

May I ask how to know if you have？
[Google Pixel 6 Pro] ada12:
1 ) if you never selected disable dm verity in android flash tools during flash its enabled

2 ) you have never disabled in fastboot : fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

its enabled.
[Google Pixel 6 Pro] Justarandomguy:
*Update* crash when letting phone charge, the only crash I experienced in days

*Update few days later* no crashes, only that one that day, so far so good
[Google Pixel 6 Pro] Freak07:
Basically what @ada12 said.

Alternatively check the first question on the pixel 7 pro FAQ linked here.

There's a magisk module linked and posts with instructions that allow you to check on your phone.
[Google Pixel 6 Pro] digger16309:
I know everyone's use cases are different. But I have found noticeable battery life improvement on the latest test build. Both screen on and screen off it's ~40% improved on my P6P over the weekend. I don't think I've done anything differently. I didn't delete any apps or change their battery profiles. My battery life was already great compared to stock, but this is another level better. I'm not even running the clean slate app.
[Google Pixel 6 Pro] snake218:
So far only 1 crash on 1.0.5_3
[Google Pixel 6 Pro] djo_5296:
rebooted after loading a game, i believe after a previous game was also running in the background

it also did a reboot after i took a picture (and opened instagram) but forgot to create logs then. this specific instance, right after taking a picture then rebooting, has been going one since the first raviantah version. i'll try to grab logs when it happens again
[Google Pixel 6 Pro] Yeedatoy:
FKM is not updated to support our device, I suggest not using it. Things will show up incorrectly or not at all, like the GPU. EXKM works perfectly. I have changed zram size and the compression method with no issues, even experimented with a small swap file. I received a rom update however so I'm not on the kernel anymore, however id suggest maybe checking Anerin Bliss's latest commits as he added his own implementation of the troublesome HBMV Manager, and I've never been able to use my device this long without it even getting warm. I can use it heavily while charging it and it just gets a bit warm but doesn't throttle at all. Just a thought, we all learn from one another. Sometimes it's difficult to figure out the best way to phrase suggestions. We may read them over before writing them and completely overlook something that may be considered disrespectful. Sometimes it's difficult to figure out if suggestions are welcome at the time, or if only feedback that someone is looking for is technical, ie: Bug reports. Let's just do our best to be conscious, considerate and respectful. Woaahh...maybe I smoked too much

Edit: yeah I definitely did, considering I just realized I'm in the pixel 6 threads and not the 7
[Google Pixel 6 Pro] DougMG:
Rebooted while checking recent calls list.
[Google Pixel 6 Pro] djo_5296:
was just about to scroll through FB
[Google Pixel 6 Pro] Flyview:
Hey @Freak07 , I know you're busy so please get to this whenever you have some time.

I'm having an issue with my Pixel 6 Pro not entering deep sleep at all when connected to my Bluetooth headunit (Alpine UTE-73BT) with no audio playing of course. GSam Battery Monitor reports that the kernel is keeping the device awake. As soon as I turn Bluetooth off, or disconnect from this particular BT device, the phone sleeps just fine. It also sleeps just fine connected to my BT headphones, so it's only when it's connected to this BT device that it's a problem!

I've tried playing with all the BT settings I can find and nothing seems to make a difference. What should I check next to investigate this further?
[Google Pixel 6 Pro] Freak07:
Test Release 1.0.5_6

Hey everyone,

so it seems the probability of the crash is greatly reduced again, but it can still happen. The problem is I don´t understand why it crashes exactly yet. I changed a few things again, which I suspect could be connected, but I´m relying on logs from you.

Also thanks to @ada12 who spotted a missing piece for teo util awareness, this should improve performance/efficiency starting with this test release as well.

Thanks to everyone for flashing all those tests, keeping up with me, providing logs and feedback! all of that is valuable to me, since I still can´t reproduce the crash on my end.

So I´d like to ask, just like the last time:

I´d appreciate if as much users as possible could flash and run this. (especially @michaely123 :) )

I´d appreciate if those that suffered regular crashes before could flash as well.

In case you get a random reboot please zip up and share the contents of sys/fs/pstore once you phone booted up again just like so many did before, which is great for me to see!

Thanks to everyone flashing those tests and providing logs in case of a crash, you guys absolutely rock!
[Google Pixel 6 Pro] Justarandomguy:
I'll always love reading that x thing has improved with an update, flashing now