Development [Kernel][03.05.2022][Android 12.1.0][Android 12.1.0 QPR Beta 2] Kirisakura 2.4.0 for Pixel 6/Pro aka "RAVIOLE"

[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

 

[Freak07]

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

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.

 

[Utini]

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.

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?

 

[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?

 

[Freak07]

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?

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.

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?

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:

GSAM Battery Monitor - How to find wakelocks? What is preventing me from deep sleep?

Hello everyone, initially I had great battery life on my P6P. I then later started to root, add a 2nd SIM card and installed more and more apps (the same ones I already had on my P4 XL). I can't really say when deep sleep stopped working, but it...

forum.xda-developers.com

 

[Texan1]

Hey there @Freak07 , will you wait for the December update next week before releasing a new kernel? Cheers mate.

 

[Nezorflame]

Good find, thank you for the report! It's related to a bug in the pixel6 detection in the app I didn't notice yet... rolling out an update to the play store with a fix. As soon as google approves it, should be available.

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!

 

[Freak07]

Hey there @Freak07 , will you wait for the December update next week before releasing a new kernel? Cheers mate.

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.

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!

thanks for reporting back, glad it´s working fine now.
hats off and thanks to @tbalden for the quick fix!

 

[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

 

[Freak07]

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

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!

 

[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!

 

[milestoneman]

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.

Thanks, I do listen to lots of podcasts so this is appealing

 

[Nekromantik]

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

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.

 

[rafik25]

Hello a noob question after installing this kernel, i lost root (magisk) any ideas plz ?

 

[DanielF50]

Hello a noob question after installing this kernel, i lost root (magisk) any ideas plz ?

Of course you did - you flashed a boot.img that doesn't have Magisk installed?

2a. If you want to stay rooted patch the provided boot.img in magisk manager prior to flashing it via fastboot. Of course you need to adjust your command to flash like you did when rooting the device.

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.

 

[rafik25]

Ok i missed patching kernel's boot.img to to keep root. thx a lot bro

 

[vlubosh]

will this kernel work on Proton early acces rom? or it could be problem with DTBO and Vendor? thank you.

 

[Prey521]

Erm. In other news, water is wet and the sky is blue....

Water isn't wet lol

 

[phaino00]

Water isn't wet lol

And technically, the sky is transparent (insert bad joke laugh).

 

[Lughnasadh]

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.

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.