yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Freak07:
It´s both of those and even more (sensor near the modem, gpu etc ) depending on the scenario and temps the phone might throttle a bit.

Limits/thresholds could be changed, but there's also a reason why google put different thresholds/limits there. Overall pixel 6 pro has thermals done excellently. At least for me from my point of view.

Interesting, thanks for reporting back. No touch (as described on GitHub) also sounded like an issue with vendor_dlkm as the touch driver sits there. Also interesting the phone did boot though with completely broken vendor_dlkm. :)

Nice teamwork there from you guys :) great to see this in here.

Indeed I'm not running proton myself, and I'm also not sure what it's actually based on exactly. Seems to be a mix of some qpr beta parts and stable parts, that's why I assumed the zip you guys quoted would work.

Thanks for the feedback. I'm sure it helps others as well. (y)

Safetynet/banking apps aren't related to the kernel as @Jerreth correctly assumed. Since safetynet hardware attestation has become a thing in the past it's decoupled from the kernel.

Had it happening last month too. Safetynet broke out of the blue for a few hours, gpay detected root and sent me a notification device was modified and it will no longer work. After an hour it was fixed by itself.

Sounds like an issue with accessibility service maybe. Or another app that has access to Lockscreen to alter its functions.

Maybe a mod that's installed, Xposed/lsposed etc.

Seems like a typical framework related issue.

I can't reproduce the issue at my end at all and have never seen it.
[Google Pixel 6 Pro] Israafil:
Anyone having same issue with camera perfomance after root, the issue turned out to be the selinux pernissive magisk module. Camera app don't like this module with it enabled, camera app perfomance issue coming up, disable module and everything is smooth again. I know not directly kernel related but just posting for someone having the same issue.
[Google Pixel 6 Pro] DRatJr:
Okay I'll look into it a bit more. The only mods I have in magisk are AK3 helper and Systemless hosts.
[Google Pixel 6 Pro] DRatJr:
So I just reverted back to stock kernel and the issue appears to be gone. Hasn't happened once since in about an hour or so. Gonna reflash again to see if it's something maybe I did. Either way thanks for the help.
[Google Pixel 6 Pro] Face_Plant:
Does anyone have the channel URL for Magisk 2403? I had to wipe my device, and when setting up Magisk again I noticed that the stable channel now installs 2406, resulting in a bootloop when I install Kirisakura.
[Google Pixel 6 Pro] bush911:
Maybe you can try this?
[Google Pixel 6 Pro] a63548:
So I did a complete new install today from factory using Magisk-v24.3.apk from https://github.com/topjohnwu/Magisk/releases/tag/v24.3, in which I installed Kirisakura with no issues. The version installed was 24.3 (24300).
[Google Pixel 6 Pro] a g bell:
Hi could anybody tell if there is a specific build for QPR BETA 2 nothing on op just wanted to be sure 👍
[Google Pixel 6 Pro] Freak07:
https://xdaforums.com/t/kernel-05-0...pixel-6-pro-aka-raviole.4358435/post-86707797
[Google Pixel 6 Pro] DRatJr:
@Freak07 I reflashed the kernel after going back to stock and it's doing the same thing. Not sure what's causing it as I don't have any modules installed. Just figured I'd like you know. (not telling you to fix it or anything just wanted to give you the info.)
[Google Pixel 6 Pro] XMAN365:
I'm having issues booting my device. I cant get it into recovery or rescue mode now, and ADB does not recognize the device

edit: i got it to work after fastboot boot command
[Google Pixel 6 Pro] Israafil:
Is there realy no way to stop the kernel from overwriting schedulers in exkm?? It would be fantastic if it would be possible to manualy cut frequencies.
[Google Pixel 6 Pro] Paz9:
@Freak07

What are your thoughts on disabling zram/swap seeing as we have 12GB of ram is this really needed? Could we save some cpu overhead by disabling?
[Google Pixel 6 Pro] Freak07:
do you maybe use outdated cleanslate apps that cause a conflict? check the cleanslate threads for the most recents ones.

any other kernel tweaks in exkm/fkm?

any other apps that use root permissions/accessibility to change something?

I can´t do much with the info if I can´t reproduce the issue. You seem to be the only one facing this particular issue and at the moment I don´t know what could be causing it.

You can try to reproduce the issue a few times, then go to exkm -> tools section -> take a logcat and a dmesg after reproducing the issue. Maybe logs will show something.

don´t change the schedulers. it´ll cause a lot of breakage. there´s no benefit in using anything else than the scheduler that´s already set.

CleanSlate battery saver is the only option to restrict the freqs at the moment, otherwise the powerhal will overwrite your changes eventually.

You can´t set the freqs freely, but choose from 3 pre-defined levels:

// saver 1

#define LVL1_LITTLE 1704000

#define LVL1_BIG 2130000

#define LVL1_PRIME 2401000

// saver 2

#define LVL2_LITTLE 1598000

#define LVL2_BIG 1836000

#define LVL2_PRIME 2188000

// saver 3

#define LVL3_LITTLE 1401000

#define LVL3_BIG 1491000

#define LVL3_PRIME 1745000

no, there´s no benefit. you´re free to disable it yourself via kernel managers or scripts if you want to disable it. :)

SoCs have become increasingly efficient over the last few years. There´s a hw accelerator for that coming with tensor too.

parts of the firmware expect zram to be present.

- userspace low memory killer expects zram to be present and is designed with that in mind

- on boot fstab creates a zram backing device (that´s something else than just having zram) for ZRAM writeback

please note, I don´t know if disabling ZRAM will break something, so if anyone changes kernel stuff like this, please don´t report issues here afterwards.
[Google Pixel 6 Pro] Paz9:
thanks for the explanation - ive tested it on and off and found no major differences

since system may rely on zram i will leave it on
[Google Pixel 6 Pro] Nightf0x_007:
Is there can be a version of the kernel without the need of disabling dm-verity ? As always when i install the kernel my phone bootloops, it needs to completely wipe my phone and disable dm-verity
[Google Pixel 6 Pro] Paz9:
My Verity is enabled and working fine... Follow instructions

@Freak07 not sure if it's been reported

I noticed app launch and loading taking longer than stock

It's smoother than stock but stock loads faster I've flashed stock again to confirm, I may try 2.0.1 is it save to flash over 2.1?
[Google Pixel 6 Pro] Nightf0x_007:
Whenever i flash the kernel my phone bootloops, im on stock kernel now but battery before was better with this kernel
[Google Pixel 6 Pro] Paz9:
Yeah battery seems better with Kiri Kernel, make sure you patch the boot.img with magsik app then flash it then flash the kernel in exkn
[Google Pixel 6 Pro] Nightf0x_007:
Yeah thats what i did but i think the problem is that i wiped my phone with disabling verity but next month i updated it without disabling verity so i think thats the main problem, i dont want to backup and wipe my phone its a major headache
[Google Pixel 6 Pro] Paz9:
i havent disabled verity on my phone

i used latest magisk 24.3 patched boot.img of april factory image.

unlocked BL - fastboot flashed boot img to the phone via adb

start phone and confirmed magisk working

then flashed 2.1.0 via EXKM and rebooted and confirmed kiri is working.
[Google Pixel 6 Pro] john-aurelio:
I install it for several days, I feel that it tends to rise in temperature until it is not used, it is mild.
[Google Pixel 6 Pro] Poesini:
Is someone having severe battery drain issues?

I'm on Proton 12.3.0 with Kirisakura 2.1.0 and I'm having severe battery drain issues that I think I have found to be Cluster 1 sticking to 1803 MHz and "Temperature 26 and Temperature 27" going for 90-95C (reading error?)... It is very weird

All of this is noted with EXKM and Magisk 24300 stable... Phone overheats a lot
[Google Pixel 6 Pro] Freak07:
an app or service is constantly requesting resources for whatever reason. maybe it´s stuck in background, broken or something else is going on in background.

You can check via top command what´s happening. I explained that already here:

https://xdaforums.com/t/kernel-05-0...pixel-6-pro-aka-raviole.4358435/post-86549289
[Google Pixel 6 Pro] Poesini:
Holy crap!

com.facebook.katana (Dang Zuckerberg) was eating 99%...

Can't test if this is causing the battery drain yet though... Will report later

But, temp 25 and 27 are still showing 95-96C
[Google Pixel 6 Pro] Freak07:
yeah that was what caused your issue probably.

I assume temp 25 and temp 27 are from exkm app?

some temp sensors in exkm/devcheck and other apps report constant high temps. they do the same on stock kernel.

you can get some good temp readings for the respective cores by running the command via a rooted shell:

while true; do cat /dev/thermal/tz-by-name/MID/temp ; done

for example.

that´ll print temps in millidegree celsius for MID cores to the console.

You can replace MID, with BIG or LITTLE. :)

you can check also for other sensors in /dev/thermal/tz-by-name

If you play around with your phone and do some expensive operations you see how quick temps for the BIG cores ramp up under load.
[Google Pixel 6 Pro] Poesini:
You're right... Seems to be an issue of EXKM since the command shows 38000 - 37000 - 39000 while idle...

Thank you very much!

Will report if more battery drain is happening
[Google Pixel 6 Pro] Freak07:
another point, which I feel I should add at this point as it fits perfectly, is that sometimes issues like you described in your previous post happen because of very unsuspicious things like for example adblocking.

I once ran into a very similar issue that was triggered, because an app couldn´t access some files it needed to download to properly function. all of this happened silently in background, which also requested cpu cycles over and over. Used top command to hunt the app, force closed the app, everything fine, after a while the app woke itself in background and it all started again. Then I checked logcat and saw the app throwing errors, which made me realize it was adaway list being updated with an host address that app critically needed to work properly.

Another thing that likes to trigger similar bugs is disabling services or parts of apps via some root apps that allow to do so.

Same goes for magisk modules or mods that claim to restrict background usage by restricting google play services or other apps.

Any of these create scenarios that those apps/services are most probably never tested against and can create random issues like this.

An app or services is trying to access something endlessly which it can´t access as it´s restricted in some way.

I hope this helps some others in the future to avoid or maybe quickly detect such issues and be aware of this possibility.
[Google Pixel 6 Pro] Poesini:
I'm using Greenify (Probably because I have been using it since Android 4.0.3 days)... Can it be a problem? Although top seems to show nothing weird so far and battery seems fine also

Also, I use ADAway but haven't seen this issue but will investigate some more
[Google Pixel 6 Pro] Freak07:
I don´t know to be fair. It could be, it could be not. Could be a weird one off issue that´s just entirely facebook related. If you run into it again it might be worth trying without greenify.

My previous post was more talking in general about this kind of issue.

I stopped using apps like greenify quite a while ago and I never had problems like this. On the other hand I also don´t use facebook. :)

edit: @Poesini I´m also using adaway. It´s not that using adaway is bound to cause such issues, it´s just a possibility.
[Google Pixel 6 Pro] Freak07:
Hey everyone :)

I´d like a favor to ask from all of you. I´m trying to create some graphs/mapping about the binnings of different tensor chips so the differences in voltages used for the CPU freq steps can be evaluated.

I´m not after trying to undervolt the CPU or similar I just want to see the differences in voltages for the binnings so we can get an idea for the range that inevitably exists there.

If you want to help me, all you need to do is to reboot the phone and immediately after boot is finished take a dmesg and upload it here so I can check.

The easiest way to take the dmesg is to just open exkm if you have the app installed, go to tools -> save logs -> current kernel log (dmesg).

Other apps can do this as well or via terminal. Instructions for terminal/adb shell can be found here.

The most important thing is to take the dmesg as fast as you can after boot finished!

I´ll collect all the data and create a spreadsheet for everyone to check.

I´d be really happy if as many as possible could share a kernel log here, the more data of different devices I can gather the better the picture we will see later will be.

Thanks for your help and I wish everyone a great day.
[Google Pixel 6 Pro] Lycidias:
Here you go ☺️

File-Upload.net - Datei nicht gefunden

Leider konnte Ihre hochgeladene Datei nicht gefunden werden. Laden Sie die Datei neu hoch.

www.file-upload.net
[Google Pixel 6 Pro] krystiano:
If helps :

Log - Google Drive

drive.google.com
[Google Pixel 6 Pro] bush911:
@Freak07 I am currently using other kernel, does my dmesg still make sense？
[Google Pixel 6 Pro] Freak07:
thank you very much for taking the time!

yes, doesn´t matter which kernel as long as the kernel doesn´t undervolt (but I think no kernel available on xda does that). stock is working too.
[Google Pixel 6 Pro] Freak07:
Hey everyone :)

I´ll bump this up so it doesn´t get lost on the previous page.

I´d like a favor to ask from all of you. I´m trying to create some graphs/mapping about the binnings of different tensor chips so the differences in voltages used for the CPU freq steps can be evaluated.

I´m not after trying to undervolt the CPU or similar I just want to see the differences in voltages for the binnings so we can get an idea for the range that inevitably exists there.

If you want to help me, all you need to do is to reboot the phone and immediately after boot is finished take a dmesg and upload it here so I can check.

The easiest way to take the dmesg is to just open exkm if you have the app installed, go to tools -> save logs -> current kernel log (dmesg).

Other apps can do this as well or via terminal. Instructions for terminal/adb shell can be found here.

The most important thing is to take the dmesg as fast as you can after boot finished!

I´ll collect all the data and create a spreadsheet for everyone to check.

I´d be really happy if as many as possible could share a kernel log here, the more data of different devices I can gather the better the picture we will see later will be.

Thanks for your help and I wish everyone a great day.
[Google Pixel 6 Pro] bush911:
Here we go
[Google Pixel 6 Pro] michaely123:
Uploaded
[Google Pixel 6 Pro] phaino00:
Pixel 6

April factory image

Radioactive kernel
[Google Pixel 6 Pro] DIXZ06:
edit:
[Google Pixel 6 Pro] bjevers:
See attached
[Google Pixel 6 Pro] MrGimpGrumble:
Sorry just saw this... Attached!
[Google Pixel 6 Pro] Jerreth:
Well i would like to attach the dmesg but for some reason it will not allow me to attach to the thread it self so here's a dropbox link to it.

Dropbox - File Deleted - Simplify your life

www.dropbox.com
[Google Pixel 6 Pro] capntrips:
see attached
[Google Pixel 6 Pro] djclark25:
Mine didn't want to attach either so here is a link to my Google drive

dmesg.txt

drive.google.com
[Google Pixel 6 Pro] a63548:
Anything for @Freak07! :)

dmesg.txt
[Google Pixel 6 Pro] Poesini:
My 2c

https://zerobin.net/?e5f52b2291346768#D6r80srRNLGG3pUZg9MrTf6o/JB/VSKi2FFiBnjivX8=
[Google Pixel 6 Pro] spr33:
Here's mine 😊

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com
[Google Pixel 6 Pro] jericho246:
Here you go mate.

Note: I'm on ProtonAOSP (April update) and Kirisakura 2.1.0
[Google Pixel 6 Pro] boxemall:
just asking for your 2 cents since i`m on stock protonaosp kernel atm: Would a dmesg help you or is it only kernel related? i can`t be arsed to flash back n forth now that the kernel has been splitted into several parts. it was so easy back then. just one zip and off you go... dunno why it has to be like this now. is there any benefit to splitting the kernel up like it is now? I`m currently in exam preparations so that i can`t risk a non functioning device lol. i wouldn`t have the time to fix it :)
[Google Pixel 6 Pro] bush911:
Just do it, I mean get the dmesg file as soon as phone finishes booting 😂
[Google Pixel 6 Pro] DirtyPISTOLA:
Here you go.https://drive.google.com/file/d/1-RaA76YIMosHn3XzyrmRK-hkh7eNeYaM/view
[Google Pixel 6 Pro] Lughnasadh:
There you go sir 😃

Pixel 6 Pro

Kirisakura 2.1.0

April build

Canary Magisk 24306

dmesg.txt

drive.google.com
[Google Pixel 6 Pro] dabrownie:
@Freak07 i just wanted to say thank you for doing an amazing job with this phone! The kernel was super smooth when I had and I hope you keep doing a great job. I'll be waiting for when you do a new phone in the future, maybe the Google pixel 7 or another one. But I traded in the pixel for the 22 ultra because no matter what I did I could not get over 6hrs screen on time and always had to charge it before bedtime. Now with the 22 ultra I can literally go 2 days with it with my normal usage. And I say my normal usage as everyone is different of course.

But I just wanted to thank you for doing an amazing job and I will for sure look for you when new phones drop in the future because I'll be getting whatever phone you decided to take on next!
[Google Pixel 6 Pro] arvylas:
Here you go.

Easyupload.io - Upload Files and Share Them Easily

Uplaod files easily and share them with your friends and colleagues. File upload solution for everyone. Upload big files and get a link to share effortlesly.

easyupload.io
[Google Pixel 6 Pro] JagerPL:
Here it is

dmesg-2022-04-23_105421.log

drive.google.com
[Google Pixel 6 Pro] Nezorflame:
Here ya go - taken from oriole, Proton, 2.1.0 version of the kernel.
[Google Pixel 6 Pro] dijia1124:
I notice the scrolling sensitivity is lower than what on stock kernel. I mean, if I use the same way to scroll the screen, on stock kernel it will scroll more. As well as in game touchscreen movement sensitivity. Personally I would prefer the stock scrolling feeling:)
[Google Pixel 6 Pro] Jon8RFC:
You, sir, are one steely-eyed missile man. Thank you.

I flashed the kernel and my device would no longer boot, getting stuck on the "Google" screen, and I also got that corrupt warning. I did a non-wipe flash-all.bat hoping I'd get it all back to normal, but that warning screen remained.

I'm on April 2022, so I downloaded the factory image for March 2022. Flashed that boot.img, failed as expected, then flashed my safe magisk-patched April 2022 boot.img...

I got this terrifying Error screen (not my image), but I did "try again", and it booted normally, thankfully. Thanks again!
[Google Pixel 6 Pro] :
Pixel 6 Pro

Kirisakura 2.1.0

April build

Stable Magisk 24300
[Google Pixel 6 Pro] jayjay1234:
Can someone help on which slot I should flash this in? I'm new to this slot thing and haven't understand how they work exactly. Do I need to flash on both slots of is one for our main system?
[Google Pixel 6 Pro] Lughnasadh:
Don't worry about slots. Just flash it and it will flash to your current slot.
[Google Pixel 6 Pro] CrashTestDroid:
Here's the dmesg from my Raven on kernel 2.1.0
[Google Pixel 6 Pro] neekless:
Hi @Freak07 I tried to run ./build/build_abi.sh --update but I'm getting the following errors from google-modules. Wondering if you have encountered this before.

ERROR: modpost: "bpf_trace_run8" [../google-modules/uwb/kernel/drivers/net/ieee802154/dw3000.ko] undefined!
ERROR: modpost: "trace_print_hex_seq" [../google-modules/uwb/kernel/drivers/net/ieee802154/dw3000.ko] undefined!
ERROR: modpost: "trace_print_symbols_seq" [../google-modules/uwb/kernel/drivers/net/ieee802154/dw3000.ko] undefined!
ERROR: modpost: "kstrtoull_from_user" [../google-modules/uwb/kernel/drivers/net/ieee802154/dw3000.ko] undefined!
ERROR: modpost: "__wake_up_locked" [../google-modules/uwb/kernel/drivers/net/ieee802154/dw3000.ko] undefined!
ERROR: modpost: "cpu_latency_qos_remove_request" [../google-modules/uwb/kernel/drivers/net/ieee802154/dw3000.ko] undefined!
ERROR: modpost: "cpu_latency_qos_add_request" [../google-modules/uwb/kernel/drivers/net/ieee802154/dw3000.ko] undefined!
ERROR: modpost: "perf_event_pause" [../google-modules/uwb/kernel/drivers/net/ieee802154/dw3000.ko] undefined!
ERROR: modpost: "hrtimer_try_to_cancel" [../google-modules/uwb/kernel/drivers/net/ieee802154/dw3000.ko] undefined!
ERROR: modpost: "cpu_latency_qos_update_request" [../google-modules/uwb/kernel/drivers/net/ieee802154/dw3000.ko] undefined!
ERROR: modpost: "kobject_del" [../google-modules/uwb/kernel/drivers/net/ieee802154/dw3000.ko] undefined!
ERROR: modpost: "jiffies_to_usecs" [../google-modules/uwb/kernel/drivers/net/ieee802154/dw3000.ko] undefined!
ERROR: modpost: "devm_regulator_get_optional" [../google-modules/uwb/kernel/drivers/net/ieee802154/dw3000.ko] undefined!
ERROR: modpost: "trace_print_symbols_seq" [../google-modules/uwb/kernel/net/mcps802154/mcps802154_region_nfcc_coex.ko] undefined!
ERROR: modpost: "trace_print_hex_seq" [../google-modules/uwb/kernel/net/mcps802154/mcps802154_region_fira.ko] undefined!
ERROR: modpost: "trace_print_symbols_seq" [../google-modules/uwb/kernel/net/mcps802154/mcps802154_region_fira.ko] undefined!
ERROR: modpost: "crypto_alloc_sync_skcipher" [../google-modules/uwb/kernel/net/mcps802154/mcps802154_region_fira.ko] undefined!
ERROR: modpost: "trace_print_symbols_seq" [../google-modules/uwb/kernel/net/mcps802154/mcps802154.ko] undefined!
ERROR: modpost: "nla_strlcpy" [../google-modules/uwb/kernel/net/mcps802154/mcps802154.ko] undefined!
ERROR: modpost: "ieee802154_unregister_hw" [../google-modules/uwb/kernel/net/mcps802154/mcps802154.ko] undefined!
ERROR: modpost: "ieee802154_register_hw" [../google-modules/uwb/kernel/net/mcps802154/mcps802154.ko] undefined!
ERROR: modpost: "ieee802154_free_hw" [../google-modules/uwb/kernel/net/mcps802154/mcps802154.ko] undefined!
ERROR: modpost: "ieee802154_alloc_hw" [../google-modules/uwb/kernel/net/mcps802154/mcps802154.ko] undefined!
ERROR: modpost: "ieee802154_xmit_complete" [../google-modules/uwb/kernel/net/mcps802154/mcps802154.ko] undefined!
ERROR: modpost: "ieee802154_wake_queue" [../google-modules/uwb/kernel/net/mcps802154/mcps802154.ko] undefined!
ERROR: modpost: "ieee802154_rx_irqsafe" [../google-modules/uwb/kernel/net/mcps802154/mcps802154.ko] undefined!
[Google Pixel 6 Pro] DRatJr:
@Freak07 I'm happy to say I think I finally got this kernel flashed and running as expected.

I believe the lockscreen issue I was having was from Google One restoring my data. As after I flashed the stock kernel I saw it happen again. albeit less frequently.

I also used Magisk 240300 to patch my boot img and I'm having no issues with the device saying it's corrupt.

Thanks for all the help!
[Google Pixel 6 Pro] Utini:
Attached is the log file. I rebooted in airplane mode due to proxyhandler bug. Hope it doesn't matter?
[Google Pixel 6 Pro] jayjay1234:
Hi, For some reason I got a bootloop from the G screen with the loading bar.

I flashed v1.8.4 thru EXKM. I'm on the latest April raven-sp2a.220405.004 firmware with Magisk 24.3 (24300) installed.

Flashed back stock images and booted back up. Any ideals? Will try to do a manual flash later

Probably an obvious question but where can I install android 12.1 from?
[Google Pixel 6 Pro] jericho246:
Reboot into bootloader

And click here (google's page with factory images)

Should be "izi pizi" with the in-browser flash tool.
[Google Pixel 6 Pro] jayjay1234:
I think I might have installed the wrong kernel version. When I went to check my build in settings I thought I was on Android 12.0. Apparently April's tags shows 12.0 instead of 12.1.