yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] lottarake:
Thanks for adding the FHD option. I've set it to 1080p with 400 DPI and the object scaling is nearly identical to my 1440p setup. Curious to see how this affects battery life.
[Google Pixel 6 Pro] RogerF81:
How can I set the custom DPI?
[Google Pixel 6 Pro] lottarake:
Go to Developer Options and scroll down to the Drawing section and you can enter a value as the minimum DPI width.
[Google Pixel 6 Pro] scloutkst:
Hot damn. After months of being in the beta and doing my best to contribute bug reports, it's great to be back!!

Much love for you my friend with your amazing work and speedy releases!!
[Google Pixel 6 Pro] triggerhappy_:
Does it somehow affect the image quality? Downscaling is not a good thing, at least on the monitor. I'm tryna figure out myself, seems the picture is more blurry in FHD (420 DPI), but I dunno..
[Google Pixel 6 Pro] scloutkst:
It absolutely effects image quality. Rendering at a lower resolution is absolutely going to be fuzzy and look worse.
[Google Pixel 6 Pro] cultofluna:
Τhanks for the update..

Only small issue is that 1080p setup ,is not surviving a reboot...( After restarting it turns on 1440p)
[Google Pixel 6 Pro] Freak07:
Enjoy the ride and happy tinkering/testing :) :cowboy:

unfortunately no.

https://xdaforums.com/t/kernel-16-0...pixel-6-pro-aka-raviole.4358435/post-85976045

And the other feature is something google needs to implement to the framework/nanohub rather than kernel. So you already answered that yourself...

Should work on latest beta just fine too. :)

No, ideally i want everybody to read the release post and check the thread here. :)

Should work fine with flags left enabled :) thanks @roirraW "edor" ehT for confirmation!

I guess it doesn't have a big impact on battery life, but maybe a rather slight one.

However it might be interesting during gaming or similar usage.

You're absolutely correct. Rendering on/using lower resolution will produce a less sharp output on the panel.

Some people will notice it more than others, just like some people notice the difference between 60, 90 and 120hz on the panel more than others. As usual it's also due to usage. If you're looking at a lot of text, use a rather low DPI setting you're probably more likely to notice a difference.

It's not just "rendering" at a lower resolution on 1080p setting though. It's possible to use wm size command in terminal to render on 1080p resolution while keeping the panel itself running on the 1440p setting.

While the setting available by flashing the kernel does both, screen content is rendered at 1080p and panel itself runs on 1080p too.

You're correct. I noticed that too during testing, but forgot to mention it. It's how google implemented the feature in the framework at the moment. Can't change this behaviour via the kernel.

Don't consider it a bug at the moment, but rather a safety measure. If you manage to somehow autostart an app (hypothetical scenario), that crashes the phone on boot while using the 1080p setting you can get out of the loop without a PC. :)

Like I said earlier, in my eyes the feature itself is not finalized yet, so I'm curious if that will really ship on launch on pixel 7 pro.
[Google Pixel 6 Pro] Nightf0x_007:
Hello, is there anything special while updating from a12 to a13 ? Or can i use the same procedure im always doing while flashing every month update ?

My way of updating --> disable any magisk system ui mods, unhide magisk, patch boot image, dirty flash factory image with dm-verity & verification disabled, boot magisk patched boot image, direct install magisk rooted image from magisk app, rehide magisk, re-enable the mods, reflash kiri kernel

Is it ok to update to a13 this way or no? Thanks
[Google Pixel 6 Pro] bleez99:
Wow, that's a lot of prepping.

Just flash it. You no longer need to disable verity either. This literally took me 10 minutes.

I grab the update, pull out boot.Img, push it on the device, patch and pull magisk_patched. Flash with --skip-reboot on the update command line. Flash the whole shebang, then flash magisk_patched. Reboot. Done.

I think it took me longer to write this reply.

All of that verity nonsense was from, if I recall correctly, end of last year with corruption issues.

When the phone comes up, flash Kiri. Doing it this way will guarantee that the possibility of losing a certified device is gone and no need to wipe play store and fiddle around with that stuff.

Hope that simplifies things.

Do what you're comfortable with if I'm freaking you out.
[Google Pixel 6 Pro] Divine Bicycle:
Do you know if adaptive charging still works when you use AccA?
[Google Pixel 6 Pro] nick491:
It works on my end, haven't used A13 yet..
[Google Pixel 6 Pro] roirraW "edor" ehT:
I haven't particularly noticed one way or the other, actually.
[Google Pixel 6 Pro] murphyjasonc:
I pass everything on Integrity checker except meets strong integrity.
[Google Pixel 6 Pro] cbomb1337:
The battery life using this is worse then stick kernal. Pixel 6 android 13. It's higher with sot and sleeping
[Google Pixel 6 Pro] Nekromantik:
anyone else getting failed flashing error on EX Kernel Manager on A13 when trying to flash latest?
[Google Pixel 6 Pro] scloutkst:
Concerning the anti rollback implemented with the android 13 update on pixel 6 phones...

For anyone who has an unlocked bootloader and has manually flashed android 13. Please take the time to make sure both your A and B partitions are updated to android 13. I assume this will mean most everyone here.

DO NOT ATTEMPT TO BOOT TO THE OS AFTER SWITCHING BOOT PARTITIONS BEFORE FLASHING ANDROID 13 YOU WILL HAVE A PAPERWEIGHT ON YOUR HANDS IF YOU DO SO

It appears a major security vulnerability has been patched alongside the new bootloader with android 13 ( I mean what else would it have been anyway)

From what I have read if for any reason a failed boot occurs before android 13 is present on both A and B slots, attempting to boot Android 12 due to an automatic switching of slots you are in for a bad time.

For all of us here tinkering with kernels and mods this seems like a definite non zero possibility.

Most of the useful information I have gleaned is from the Twitter thread from topjohnwu

Pixel 6 series can't go back to Android 12 after updating to Android 13 due to security vulnerability [U]

Google has confirmed that Android 13 for Pixel 6, Pixel 6 Pro, and Pixel 6a is an upgrade that can't be reverted back to Android 12.

9to5google.com

https://twitter.com/i/web/status/1559786740050644992
[Google Pixel 6 Pro] Psfanboy88:
How can i flash both? I used the following Method for the Android 13 Update coming from 12.:

Use the latest Magisk Stable (in my case, I keep the app "hidden" / renamed)

Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)

Extracted the new boot.img

Copied new boot.img to the phone

Patched the new boot.img with Magisk Stable

Renamed Magisk'd boot.img so I know what version of firmware it's for

Copied the Magisk'd boot.img back to the computer

Disabled all my Magisk Modules

Removed the "-w " from the flash-all.bat

Re-edited the flash-all.bat to verify I saved it with the "-w " taken out

Open a Command Prompt, navigated to S:\platform-tools

adb reboot bootloader

flash-all.bat

Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)

adb reboot bootloader

fastboot flash boot kernel.img (renamed Magisk'd boot.img)

fastboot reboot

Unlock, check everything's working

Re-enabled the most basic Magisk Modules which I was sure wouldn't cause a critical issue

Reboot, unlock, made sure everything's working

Does the flash-all.bat flash both Slots A and B?
[Google Pixel 6 Pro] scloutkst:
The flash-all.bat does not flash both slots.

I used the fastboot command to manually switch the slot. Then ran the flash-all.bat again to flash everything.

This method worked well for me. It's not elegant or streamlined, but it works. I'm suspect the flash-all.bat could be edited to flash both partitions but I'm not sure how.

The command to switch slots is one of the following depending on which slot you are currently on. The bootloader recovery screen will tell you what slot is currently active.

fastboot --set-active=a or fastboot --set-active=b
[Google Pixel 6 Pro] roirraW "edor" ehT:
No. On the Fastboot screen, change to the opposite slot with either:

fastboot --set-active=a

(If you're on slot b)

or

fastboot --set-active=b

(If you're on slot a)

Then flash-all.bat again (remembering to still use the one with the -w removed so it doesn't wipe).

Then you'll have to re-root the newly updated slot.
[Google Pixel 6 Pro] Ghisy:
I used the kernel flasher app mentioned in the OP and it worked fine.

Note that EX Kernel Manager has been updated for Android 13 only 2 days ago. Make sure you have the latest version.
[Google Pixel 6 Pro] Ghisy:
Am I safe if I flashed the new bootloader to both slots before updating to 13?
[Google Pixel 6 Pro] Psfanboy88:
Do i have to do all the steps again after switching the Slot? Which also means to patch the boot file in magisk?
[Google Pixel 6 Pro] scloutkst:
If you only flashed the bootloader I am not entirely sure, but I suspect the answer is a big fat NO.

The problem occurs when trying to boot Android 12 with the new bootloader. If android 13 has been successfully booted even once on the phone it burns the anti rollback fuse. And anti rollback will be tripped when attempting to boot Android 12 with the new bootloader.

So if you only flashed the bootloader to both slots , and not android 13 in its entirety I would say, you are not safe.
[Google Pixel 6 Pro] Nekromantik:
Ah i didnt see update of app

Thanks
[Google Pixel 6 Pro] scloutkst:
Whatever you did after flashing android 13 initially the first time on the other slot will need to be done again. Including rerooting by flashing the modded boot file from magisk, along with re-flashing the kernel once booted into the os after rooting.
[Google Pixel 6 Pro] roirraW "edor" ehT:
These really have nothing to do with this kernel.

Yes.

You have to switch slots, flash-all.bat, reflash the boot.img you've already Magisk'd (unless you deleted it - in that case, yes, re-Magisk the boot.img and flash it), then to use this custom kernel, flash it using Kernel Flasher.
[Google Pixel 6 Pro] scloutkst:
Unless I misunderstood the way anti rollback is causing bricks, I don't know if he is safe unless android 13 in its entirety is on both partitions. Please correct me if I am wrong.
[Google Pixel 6 Pro] scloutkst:
@roirraW "edor" ehT @Freak07

I apologize for the "off topic" post here and de-railing the thread. However I felt this was absolutely something people flashing this kernel should be aware of, considering the inherent risk associated with flashing kernels/mods and finding yourself in a no boot situation.
[Google Pixel 6 Pro] Ghisy:
Thanks, just saw something about it in another thread!

Sorry for the OT btw. Back to Kirisakura now! :P
[Google Pixel 6 Pro] roirraW "edor" ehT:
Taking the update conversation to another thread.
[Google Pixel 6 Pro] Nekromantik:
hmm installed kernel flasher and when I open it it says invalid boot img

i booted the patched stock img instead of flashing. is this reason? used to work like this on A12
[Google Pixel 6 Pro] Ghisy:
Wait, what? Kernel flashed is for flashing a kernel using a ZIP file, not a boot.img. What are you trying to do?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I always boot completely stock unrooted after updating, then I boot back to Fastboot, flash the Magisk'd stock boot.img, boot with it, then use Kernel Flasher to flash the custom kernel. Worked for me with no issues on Android 13 Stable.
[Google Pixel 6 Pro] flar2:
The flashing stuff didn't change and shouldn't need to change for Android 13. All versions of the flasher should work.

However, one user I spoke to had permission issues when the app's directory was set to /sdcard/ElementalX. Everything worked fine for him using a directory under /sdcard/Documents/

I couldn't reproduce that issue, it works fine for me using /sdcard/ElementalX on Android 13

Since Android 13 was released I've had complaints about all my apps not working, none of which I can reproduce (I've been using 13 since the previews were released).

IMHO, Google has ruined Android with too much complexity and inconsistency. They are on track to become the next Microsoft
[Google Pixel 6 Pro] Nekromantik:
i did as per normal but some reason booting the patched stock img did not let me flash kernel.

I went back and flashed it instead and now on the latest version fine
[Google Pixel 6 Pro] ttle54:
Update on my Android 13 Kirisakura 4.1 Kernel:

1. Much better battery life, I'm looking at 19 hrs for 80% of battery.

2. Butter smooth, no crashes so far, knock on wood.

3. The resolution change from 1440p to 1080p is great. However, running the phone at 1080p won't make much difference to battery life.

Notes: I'm running NapTime, Servicely, and disable auto-sync in FKM app. A bunch of other apps are not allowed to run in background by using Servicely.
[Google Pixel 6 Pro] DespairFactor:
I turn my phone off and get 2 months battery
[Google Pixel 6 Pro] ChongoDroid:
Phone is crazy smooth on 13 but with this kernel, the gsm wakelock disabled and the resolution at 1080p it's unreal how good it is.

Phone stays stone cold under medium usage now
[Google Pixel 6 Pro] radiohead7778580:
Is anyone having a fingerprint issue whenever you're using a bank app or some other app that requires a fingerprint verification? It only happens when using 1080p (FHD). The fingerprint still works. It just doesn't come up. It's just a blank screen where the fingerprint icon should be.
[Google Pixel 6 Pro] CertifiedBlyndGuy:
Probably not the right thread but AppDash and EXKM are working perfectly. Love your work and I whole heartedly agree with you

The same goes for this kernel too. It's been working perfectly since I got my Pixel in April and I appreciate the work that has been put into it

Keep it up guys
[Google Pixel 6 Pro] DespairFactor:
like Steve Austin?
[Google Pixel 6 Pro] antiochasylum:
And that's the bottom line.....cause...
[Google Pixel 6 Pro] roirraW "edor" ehT:
The same problem happens sometimes when changing the DPI of the screen. Probably a common issue with force changing the resolution.
[Google Pixel 6 Pro] Lughnasadh:
Damn, must be "getting" old (ok, gotten old)...not a Six Million Dollar Man reference I thought I spotted.. 🏃‍♂️

Sorry for the OT 😬
[Google Pixel 6 Pro] jcp2:
I thought 'Six Million Dollar Man' the first time I read it as well! :)
[Google Pixel 6 Pro] Utini:
Updated from A12 to A13 fine and flashed kernel without problems.

Thanks as always @Freak07
[Google Pixel 6 Pro] triggerhappy_:
Battery drainage is freaking rapid on the latest updates.

A13 raven + latest Kirisakura.

I had like.. 3 days battery life with 7-8h SOT, now I barely have 20 hours with SOT 3-4 hours. Not to mention all stuff remained the same. 😮‍💨☹️
[Google Pixel 6 Pro] hanschke:
thank you for replay for my json wish. I thougt that there is not the problem because changelog is shown inside the app und a link to the threat too. I thougt it is much easier to get information for a new update but thank you for your work
[Google Pixel 6 Pro] kickassdave:
Something weird going on for me as well. Barely doing anything and my phone is alarmingly hot to touch.

Think I might flash stock kernel back before I break something :/
[Google Pixel 6 Pro] Utini:
Your current battery drain is what I always had so far lol.

Download better battery stats and check if your device is in deep sleep.
[Google Pixel 6 Pro] Suavie103:
Updated ex kernel to 5.90 for Android 13. App keep force closing. I had to flash the kernel in the Franco kernel app. Any help for elementx kernel app?
[Google Pixel 6 Pro] CertifiedBlyndGuy:
The only way I ever got 7-8 hours of SOT was over on ProtonAOSP with this kernel and on a friend's project that has yet to be officially released. On stock I get 3.5-5 unfortunately and always have, sometimes nearly 5.5 with this kernel
[Google Pixel 6 Pro] CertifiedBlyndGuy:
Unless the device is alarmingly hot all the time, give things two or so days to settle. Happens to me every time I flash stock. There's an adjustment period
[Google Pixel 6 Pro] triggerhappy_:
Where can I find powerhint magisk module for P6P? Going to back to stock for a while. Following steps from

Spoiler content hidden.

Or is there any way to do it easier?
[Google Pixel 6 Pro] DespairFactor:
you don't need to do this
[Google Pixel 6 Pro] Lughnasadh:
There isn't a separate module anymore since he includes it in the kernel. That quote is from old instructions.

Ninja'd 🤪
[Google Pixel 6 Pro] triggerhappy_:
So, is it enough to Update and Root Factory Image? Or better skip 1a and flash boot, dtbo, vendor_boot, vendor_dlkm.img like in #4 instruction?
[Google Pixel 6 Pro] Lughnasadh:
Again, you are reading from old instructions. Manual installation of the kernel is no longer supported.
[Google Pixel 6 Pro] triggerhappy_:
So, how can I safely go back to stock then? Sorry for my ignorance, I'm tryna do my best :)
[Google Pixel 6 Pro] Lughnasadh:
Oh, you are going back to stock. Misunderstood. Yes, flash those stock images. Thought you were trying to flash the kernel because of that quote mentioning the Powerhint Mod.
[Google Pixel 6 Pro] Freak07:
Second post, first question in the FAQ. :)
[Google Pixel 6 Pro] Freak07:
Use top command to check for any rogue app or service pinning the CPU.

Please search the thread, I posted a few times how to do this :)

Edit: check the post and quoted post for example

Post in thread '[Kernel][16.08.2022][Android 13.0.0]Kirisakura 4.1.0 for Pixel 6/Pro aka "RAVIOLE"' https://xdaforums.com/t/kernel-16-0...pixel-6-pro-aka-raviole.4358435/post-86772869
[Google Pixel 6 Pro] triggerhappy_:
Exactly what I was doing until I stumbled upon 1a from post #4 and trying to find this powerhint module for p6p :p

Anyway, gotta skip this and just flash the images. Thanks all!
[Google Pixel 6 Pro] triggerhappy_:
I did all precise steps and flashed images and now I got the message "your device is corrupt", I proceeded and here is just Google logo in boot. Am I screwed?
[Google Pixel 6 Pro] Freak07:
I adjusted the FAQ to make it more clear that it's just a help if you don't know the fastboot commands.

Just dirty flash the factory image of your current firmware version again, like you did when you updated. That should get you back on track.

Sounds like something was not done correctly or went wrong but impossible to say now.
[Google Pixel 6 Pro] triggerhappy_:
How can I reboot to bootloader or something? It's stuck on Google.
[Google Pixel 6 Pro] Freak07:
Long press power and volume down.
[Google Pixel 6 Pro] triggerhappy_:
Thanks for support mate. It works. I almost lost my mind.
[Google Pixel 6 Pro] bgboii:
I agree there has been a ton of drainage on my phone.
[Google Pixel 6 Pro] triggerhappy_:
I presume the reason is Android 13 itself. Being on the latest firmware and stock Kernel the drainage is still humongous. Dunno, probably will stick with 12+3.0.17
[Google Pixel 6 Pro] Divine Bicycle:
I've just installed AccA, do you mind sharing your settings?
[Google Pixel 6 Pro] Freak07:
There´s not much difference on battery life on my end when I went from A12L to A13. I could post screenshots of my battery life, but that wouldn´t help anyone as this is entirely due to my usage and no usage is like any other.

You have to keep in mind, there´s constantly a ton going on in the background. So if you just updated and flashed the kernel it may give the impression it must be due to the kernel, when it just isn´t.

Google services updating (it´s not only play services now, there are several other backends, which google constantly pushes updates for either via playstore, play servives, pixel services etc) and app updates is the most prominent example for this.

There´s always the possibility of a service or an app (most of the time introduced by an update) getting stuck in background pinning the CPU/GPU by constantly requesting resources.

The three good advices (not matter if you´re on stock kernel, stock firmware, custom kernel or custom rom) I can give is to:

1. use better battery stats app (you can find latest beta version on xda which also works on a13) which can give you a good overview of what´s happening in the background.

Set a custom reference point, let your phone idle screen off on the table for an hour without using it and check the stats.

If Awake (Screen Off) is more than 10% during this hour of you not interacting with the phone, you either have a ton of apps syncing in the background or something is wrong if the value is even higher.

2. check out battery historian, do a google search. It´s similar to better battery stats but will show you a lot more information, graphs and stats. although it´s more difficult and time consuming to set up and check out the stats.

3. use top command, while the screen is on without you interacting in any way with the phone to check for any stuck service or app constantly requesting resources, which in turn will drain the phone quickly.

check out this post on how to do this and the reply to the post where facebook as identified as the culprit.

I had an issue with a specific version of google photos app a few weeks back. After opening the app once, it would pin the CPU cores to high freqs. The only solution was to downgrade or to force close the app when leaving it. Two days later another update solved that problem.
[Google Pixel 6 Pro] Utini:
@Freak07 just curious, do you use a firewall on your phone? E.g. afwall?

One thing to mentioned regarding screen off (awake):

It seems like sometimes it takes several minutes until the phone gets into deep sleep after leaving it alone. Some if you use it frequently (e.g. like me at work) you will have like 1/3 of screen off (awake) because it takes like 8mins for it to fall into deep sleep and 2mins later I get a phone call.

Here at home I am in deep sleep after 16 seconds though.
[Google Pixel 6 Pro] Freak07:
No I don´t use a firewall.

Yes, that´s why I said leave it an hour without touching it to identify any deep sleep issues. If you see an app keeping phone constantly awake you´ll likely see it there.

After a while it will drop to different "deep sleep states". (a bit simplified) Most of this is no longer controlled by the kernel either. There are different kinds of so called doze states, which are more or less controlled by different triggers depending on how you use the phone. If you google around you will likely find some not very accurate documentation from google about this, but it will give you a general idea.

You´ll always get the best results on your home wifi network, where not much traffic is happening, not much is around.

If you´re on mobile network or in a network with many devices it always looks different.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hi. I've sent a reply to you in the [How To Guide] Limit Charge thread. :)
[Google Pixel 6 Pro] Utini:
I thought I might be able to safe some more battery by not letting all those nasty google apps constantly call home :P

The difference between work and home is huge. About twice as much SoT at home. Also only 1 hour screen off (awake) with 8 hours deep sleep while at work its more like 3-4h screen off (awake) with 8 hours deep sleep.
[Google Pixel 6 Pro] Pipodi93:
Can't seem to find the screen resolution switch, am I missing something here?
[Google Pixel 6 Pro] zetsumeikuro:
FHD/1080P Support for Pixel 6 ProFHD/1080P Support for Pixel 6 Pro. No regular P6.
[Google Pixel 6 Pro] Pipodi93:
Holy. It seems that 3 weeks off work made me forgot how to read. Sorry! :(
[Google Pixel 6 Pro] zetsumeikuro:
No worries dude, we've all been there. We got each other's backs here.
[Google Pixel 6 Pro] bgboii:
Does anyone else feel like their device gets warm easily?