yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] djo_5296:
wow, ive been getting crashes so frequently. will update to 5_6, the logs attached are for 5_3 just now
[Google Pixel 6 Pro] Freak07:
Hmm, might be a though one.

The Bluetooth driver on my kernel is exactly stock. Most stuff is happening elsewhere in the Bluetooth firmware though, just like radio.

Does this issue happen on stock kernel too?

I'd try to use better battery stats, maybe you'll see something more detailed than the kernel keeping the phone awake, maybe a specific kernel wakelock or a partial wakelock contributing to power manager etc. :)

Because if anything asks to keep the phone awake it will be always shown as the kernel does this, even when it's a service or an app. (in this case Bluetooth Hal/service most probably)

Framework/Hal/service asks for resources because it wants to do something so it thinks it can work properly and the kernel grants it. (the kernel can't know what's happening in userspace/framework)
[Google Pixel 6 Pro] Prakash Chandra Mishra:
Galaxy S10 Lite SM-G770F 5G Comfortablety.
[Google Pixel 6 Pro] Flyview:
Thanks! I'm not sure if it's a problem on the stock kernel, I've been running your kernel since I bought the phone 7 months ago! 😁

BetterBatteryStats is showing 2 kernel wakelocks that do not show up at all when BT is off:

odm:btbcm (100% of the time over a few min test)

bthal_wakelock (98% of the time over a few minutes test)

The wakelock times drop to 10-15% when BT is on but not connected to the problematic device.

I can block odm:btbcm with EX Kernel Manager's wakelocks blocker tool, but bthal_wakelock doesn't show up there! How can I try blocking it manually?

I've actually been blocking odm:btbcm for a few days now and although it's now able to sleep, it only sleeps about 60% of the time. If not connected to the problematic device I see sleep of 90-96%. I'm including this just as an aside as I shouldn't have to be manually blocking BT wakelocks! Hopefully we can figure out what triggers this or how to fix it permanently.

UPDATE: I left the phone connected overnight with odd:btbcm blocked and bthal_wakelock kept the phone awake 36% of the time. I have seen no downside to blocking odd:btbcm so far. Everything works like before.
[Google Pixel 6 Pro] Rachid.Ala:
I'm not sure if this gonna help, but did you try updating your headunit to the latest version ?

You can check these links :

Alpine - Headunits

www.alpine-electronics.co.za

Alpine - Bluetooth Compatibility Charts

www.alpine-electronics.co.za
[Google Pixel 6 Pro] Flyview:
Thanks for the suggestion. It's already been updated to the latest version (1.5).
[Google Pixel 6 Pro] boxemall:
Ok, here i am.

Back again and trying to figure how to flash kiri kernel. Been debating for months, but now that ProtonAOSP is finally dead i went back to Stock.

Just flashed latest A13 tq2a (stable) extracted 'boot.img', uploaded it to the phone and patched it using magisk.

I put the patched img back on my computer and used 'fastboot boot boot.img', but i can't get temp root so that i can flash it using an app, since manual doesn't seem to be a thing anymore.

Output goes like

.\fastboot devices
18211FDF60020H fastboot

.\fastboot boot boot.img
Sending 'boot.img' (65536 KB) OKAY [ 1.449s]
Booting FAILED (remote: 'Unrecognized command boot')

It just won't accept the boot.img. I heard about fastboot/adb changes incoming, so is this it?

after all i need root (at least temp) to be even able to flash it in the 1st place. kinda feel like what was there first,... the egg or the hen?

i must've missed something and granted, it's been a while so plz bear with me and help me out on this one.

regards
[Google Pixel 6 Pro] Rachid.Ala:
Are you in fastboot mode or fastbootd mode ?

To be sure do this :

adb reboot fastboot
[Google Pixel 6 Pro] phaino00:
You have to patch the boot image in magisk first and then flash the magisk patched image in fastboot to gain root.
[Google Pixel 6 Pro] majorfigjam:
The command is "fastboot FLASH boot xxx.img" , where xxx is your patched image - something like magisk_patched-26101_AAAAA.img.

Then reboot, let magisk update everything, then reboot and flash this kernel.
[Google Pixel 6 Pro] ada12:
you use updated fastboot tools in computer ? here from fastboot & fastbootd command fastboot boot boot.img work
[Google Pixel 6 Pro] kpirnie:
what version of magisk? what version of sdk tooks?
[Google Pixel 6 Pro] boxemall:
tx to everyone that took the time to reply to my post. actually i can only think of me doing the wrong things (what else). i just took a chance and flashed the patched bootloader and i had root. What'S life without taking risks,eh? :)

And after that i flashed kranul (kernel i know). all seeme to be working so far. now i need a few days to see how it feels (smoothness, battery etc). so far i can't say anything negative.

regards
[Google Pixel 6 Pro] dark2099:
Edit: Deleted
[Google Pixel 6 Pro] Flyview:
Hey guys, I really need your help. My Pixel 6 Pro just started freezing up after booting. I think it's probably unrelated to this kernel so I started another thread. Please have a look:

https://xdaforums.com/t/help-pixel-6-pro-freezing-shortly-after-booting.4593677/
[Google Pixel 6 Pro] Freak07:
Test Release 1.0.6_3

Hey everyone,

so it seems the last test finally got rid of the issue. No more crashes reported.

This release adds some of the stuff back I removed in order to being able to better understand the crash. If I´m correct those pieces of code which are added back now should not be responsible for the crashes.

So please everyone: Flash, test and report back. Especially those that suffered from the crashes in the past.

Thanks to everyone for flashing all those tests, keeping up with me, providing logs and feedback!

Without all the logs and users willing to flash and help I´d have never been able to debug this.

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 :) )

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] digger16309:
No issues for me at all on 1.0.6.3 but I also stopped having reboots 2-3 updates ago after resetting EXKM and freezing it after flashing the kernel.
[Google Pixel 6 Pro] Admiral2145:
Anyone tried this on June update yet?
[Google Pixel 6 Pro] AlDollaz:
Nope, but I'm positive @Freak07 will update soon.
[Google Pixel 6 Pro] minhgi:
np updating to June firmware
[Google Pixel 6 Pro] Admiral2145:
With the 6-11 kernel?
[Google Pixel 6 Pro] minhgi:
Correct... Just did like 5 mins ago
[Google Pixel 6 Pro] Freak07:
Since this is a QPR bump it's better to wait until I update the kernel with the updated source for the June QPR/feature drop release if you don't want to face any issues.

If your comfortable flashing back to stock conditions and feel adventurous feel free to try. :)

Seemingly still works checking back the last few posts.

Source for June stable has not been pushed yet. It's getting late here. They'll either push source later during my night or tomorrow.

I'll try to update the kernel as soon as possible, but since life is crazy busy at the moment I'll try to do it tomorrow evening.

Wish everybody a nice day/evening :)
[Google Pixel 6 Pro] ykjae:
So not sure what's causing this but seems to be the module helper. Bootloop occurs and bootloop protector kicks in to disable the module. With the module disabled I still have the bootloop. Flash back to stock kernel problem fixed.
[Google Pixel 6 Pro] falsehhhhh:
Waiting for June update
[Google Pixel 6 Pro] Lughnasadh:
He literally told everyone when he will try to push an update two posts above.
[Google Pixel 6 Pro] Psfanboy88:
Can't find the powerhint module. Where do I get it?
[Google Pixel 6 Pro] Freak07:
Copy paste error from pixel 7, adjusted the release post.

The powerhint module gets flashed automatically during flashing the kernel.zip on p6 series. :)

Thanks for spotting 👍
[Google Pixel 6 Pro] Joseahfer:
I think that's only for Pixel 7, so just flash the kernel as always.
[Google Pixel 6 Pro] mlekomann:
Hello. Please help. I have decided to roll back to the standard kernel. I used kernel flasher to flash it. With it I just restored the default boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img, the backup I made before installing the kernel and rebooted. During the boot I got the message "device is corrupted". I clicked next and the google logo came up and that was it. The phone doesn't boot anymore and I can't even turn it off by holding down the power button for a long time. How can I get my phone back to work, or better yet back to its previous working state?
[Google Pixel 6 Pro] phaino00:
You could try to reflash the factory image editing the flash all script by removing -w. This assumes you can get to bootloader of course.
[Google Pixel 6 Pro] mlekomann:
I now only see the Google logo, I can't even turn my phone off. I've been holding the power button for a minute, but it won't turn off.

The computer detects the phone as an unrecognized usb.
[Google Pixel 6 Pro] phaino00:
Try hold power and vol down to get to the bootloader.
[Google Pixel 6 Pro] mlekomann:
I must have panicked a little. It did help to turn it off by holding down "volume up + on" for a long time.

I was able to enter fastboot. Can you tell me what I should do now?

Switch from slot "a" to slot "b"? Or restore boot.img, dtbo.img, vendor_boot.img, vbmeta.img and vendor_dlkm.img again in manual mode from the firmware I had?

I feel stupid, I read the instructions several times and I thought I was doing everything right. Sorry for cluttering up this thread.
[Google Pixel 6 Pro] phaino00:
The straightforward thing to do is reboot from fastboot to bootloader and install factory image.
[Google Pixel 6 Pro] Flyview:
Get into bootloader then:

./fastboot update image-raven-tq3a.230605.010.zip

"image-raven-tq3a.230605.010.zip" in my example is the zip inside the zip you download. Make sure to NOT add "-w" to the update command or your device will be wiped.

You can get the June factory image from here:

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 6 Pro] Utini:
Coming from April build + kernel I did:

Update to May build

Update to June build

Flashed June kernel

Worked fine so far :)
[Google Pixel 6 Pro] panic.exe:
Do I need to use cleanslate config to enable flashlight notifications or is there another way I'm not seeing?
[Google Pixel 6 Pro] Freak07:
Glad to hear :)

Enjoy the ride!

Iirc correctly you need the companion app. :)

Maybe @tbalden wants to confirm?

The kernel doesn't know what happens in userspace, e.g. notifications arriving.

So companion app serves as a bridge there.
[Google Pixel 6 Pro] mlekomann:
Thank you, it's working now and everything is fine. I just panicked a little, I didn't expect that.

Perhaps the failure itself was caused by not restoring what I think vbmeta.

I didn't turn off verity when rooting, and now I don't want to erase my phone and it's too late to do that.
[Google Pixel 6 Pro] Freak07:
You're deduction is correct.

As mentioned in the FAQ if you don't disable flags for verity/verification you want to restore the four partitions you mentioned including stock vbmeta.img to return back to stock conditions.

Factory image flashes back stock vbmeta, so dirty flashing factory image fixed the problem you were facing.

Vbmeta basically contains the hashes from the partitions that are checked. So if the expected hashes are changed during the kernel flash (so flashing the kernel works with vbmeta being enabled) you want to restore those hashes back to stock as well when going back to stock. :)
[Google Pixel 6 Pro] rolarocka:
This Kernel is awesome 👍😍
[Google Pixel 6 Pro] FerJavi:
I guess roms based on may builds are not going to work with the new release?? Im on a bootloop.
[Google Pixel 6 Pro] spr33:
I didn't think you needed to update each month? I believe you can just go straight to the latest firmware. Please correct me if I'm wrong.
[Google Pixel 6 Pro] AlDollaz:
Correct. If you're a few months behind, just install the latest. Installing each previous month is just a time waste.
[Google Pixel 6 Pro] Nightf0x_007:
Hello p6 here do i need to have dm verity & verification disabled ? As i already have them disabled and i keep them disabled every month while updating but this time while upgrading from may to june update phone got the error cant load android system ..., To get the phone to work without wiping my data i reflashed the update without disabling the dm options so is it safe to flash the kernel or will i get bootlooped, thanks
[Google Pixel 6 Pro] idark11:
If I have installed 5.10.183-Kirisakura_Raviantah_1.0.6_3 Can be installed dirty on top?
[Google Pixel 6 Pro] Flyview:
I think so. That's what I did.

@Freak07 @tbalden Is there a way to keep the battery saver CPU frequencies even while the camera is used? I noticed that when the camera is in use, the phone is allowed to use all frequencies. Could this please be made an option? Is there anything other than camera for which an exception is made?
[Google Pixel 6 Pro] ada12:
Or Its exist another solution but it's more technical, it's to generate your own vbmeta.img ! you need create a script avb for sign every img you flash ...
[Google Pixel 6 Pro] Freak07:
yes pixel 6 series can flash kernel with the flags enabled at the moment, as the kernel.zip patches vbmeta for the expected hashes.

Note that to flash back to stock you also want to flash vbmeta.img additionally to the other images.

yes, you can always flash on top unless I mentioned otherwise if you´re already on my kernel.

If coming from any other kernel it´s better to restore stock once in between.

that´s the only exception.

battery saver level 2 and 3 will introduce stutters to video recording and generally make camera experience very "hiccupy" as GCAM is extremely resource intensive.

There are already PMU limits during camera usage imposed, so the phone does not scale to the highest freqs.

I can look if those can be restricted, but one stutter can ruin an entire video recording unfortunately. :(

I suppose you want to do this to reduce heat?

yes, that´s also possible.

kernel flasher app offers the possibility to easily backup all relevant stock images. That´s currently the best and easiest solution I think.

on pixel 7 the approach of patching vbmeta with the expected hashes during a kernel flash, as we do currently on pixel 6, does not work and still requires a wipe so the device can boot.

I think this is a very intentional change, so the p6 is at a weird mix in between in that regard.
[Google Pixel 6 Pro] idark11:
Unfortunately, the top update failed on P6pro. The phone went into perpetual download. A previous version was previously installed
[Google Pixel 6 Pro] Freak07:
shouldn´t happen. don´t know what can be causing this, without further information.

Best to follow the steps mentioned in the FAQ to restore your phone to stock.

Make sure to flash the kernel only on the compatible firmware. 1.1.0 requires stable June firmware, 1.0.6_3 was for stable May firmware.
[Google Pixel 6 Pro] Rachid.Ala:
Thank you Freak07 for your contributions, the kernel works flawlessly on my P6P.
[Google Pixel 6 Pro] Flyview:
Yea mainly to reduce extreme heat and battery usage during video calls over data. Camera stuttering doesn't matter much in that scenario. I wanted to play with it and see how much stuttering it would cause in video recording as well. It would be nice to have manual control over this. What do you mean by PMU limits?
[Google Pixel 6 Pro] Freak07:
The main problem there isn´t the CPU, camera module itself and the radio produce a lot of additional heat as well in that scenario.

Did you check the actual freq usage? e.g. taking a trace and not just a CPU overlay app? I don´t think you´ll see much of the higher frequencies used.

I guess there might be a difference depending on the app you´re using for video calls though. Which app do you use?

PMU limits means there are CPU freq restrictions already applied during camera usage when a certain threshold from the PMU (performance monitoring unit) is not crossed.

The problem here is the kernel can't know that you're doing a video call. It just "knows" the camera is started and used.

I can add a manual toggle accessible via sysfs to override the battery saver to also restrict on camera usage.

Or I can tweak the power-hal further trying to do a more strict pmu cpufreq limiting, but like I said I'm not sure limiting the CPU does much.

Power-hal has the ability to differentiate between scenarios like 4k recording, 60fps, 1080p, Front cam, viewfinder preview etc.
[Google Pixel 6 Pro] Flyview:
Thanks for the detailed reply, really means a lot.

No I haven't taken an actual trace, I'm just using a CPU overlay app as you guessed haha. I do most video calls through the Signal app. Where is the exception for the battery saver if the is camera in use actually implemented? In the kernel? I was thinking the best solution would be to add an option for this camera exception in the CleanSlate Config app. That way you can choose whether you want the battery saver CPU freqs to stick during camera use, similar to how we can pick if they stick even while touching the screen.
[Google Pixel 6 Pro] Freak07:
I´ll summon @tbalden to the discussion here as the CleanSlate apps are his area.

Yes @tbalden and me discussed earlier that an exception for the battery saver must be made during camera usage as it introduces stutter, hangs, etc etc.

So the kernel detects camera is being started in the camera driver and suspends the batterysaver as long as the camera is in use.

The problem like I said is the kernel can´t know if you´re using GCAM, taking a video, taking a picture or doing a video call.

That´s what the companion app for CleanSlate is for. It brings userspace events to the kernel side.

So maybe it´s possible to detect that a video call session is started on android and export that via companion app to the kernel @tbalden? I think a per-app list is an endless or hopeless task.

The other solution would be to add an additional toggle to the CleanSlate config app, to disable the override for the battery saver during camera usage for those that do a lot of video calls, maybe with a warning that keeping this override enable can seriously impact camera experience by ruining videos etc.

If possible I´d prefer the first solution. 😇

We also need to weigh the actual CPU impact contributing heat against the impact on general camera experience in the second scenario.

And I probably need to do some traces to check if during a video call, the freqs are actually pushed very high, because I think they won´t really be.
[Google Pixel 6 Pro] danidenial:
Hello p6 here do i need to have dm verity & verification disabled ? As i already have them disabled and i keep them disabled every month while updating but this time while upgrading from may to june update phone got the error cant load android system ..., To get the phone to work without wiping my data i reflashed the update without disabling the dm options so is it safe to flash the kernel or will i get bootlooped, thanks :)
[Google Pixel 6 Pro] phaino00:
On the P6, you do not have to disable DM options when flashing this kernel and most others. I haven't disabled DM options and no bootloops.
[Google Pixel 6 Pro] idark11:
It is possible to fix TTL? My telecom operator has set the modem mode as a paid service :(
[Google Pixel 6 Pro] tbalden:
Trying a little bit in Google chat video call, it isn't really pushing it to high freqs but still it happens time to time when the picture in front of the camera gets a lot of changes, then it time to time bumps to a bit higher, sometimes over 2ghz.

So what I tried is to use the companion app and the possibility to monitor which process is in the top usage at a given moment, thus detecting the app in the foreground. Passing this to battery saver functionality and identifying Google camera process there, it is possible to selectively only disable battery saver when the Google camera app is in the foreground using the camera sensor. An advanced option there to set this. Testing this a bit and later on I'll be releasing new apps and kernel with this feature.
[Google Pixel 6 Pro] Flyview:
Sweet!!! Yes, and I'd like to add that while video calling you can be doing other stuff on the phone, and that can definitely push into the higher frequencies when the battery saver is disabled due to camera use.

Is detecting Google Camera as the top CPU process reliable during camera usage? What if something else spikes during video recording, temporarily making the config app think Google Camera is *not* being used when it really is?

If you're adding this option, why not add an option for no camera exception at all? I prefer manual control, and in this case I wouldn't have to also run the companion app.

Thanks for all of your work either way!
[Google Pixel 6 Pro] tbalden:
Usage is based on how much the UI is being in focus, and it should work regardless of CPU usage of other tasks.

I'll think about an option to simply disable exceptions for camera
[Google Pixel 6 Pro] sylj69:
After flashing version 1.1.0 of lineageos of microg, it stuck on the first screen and could not enter the desktop
[Google Pixel 6 Pro] Freak07:
If you check the OP custom roms are unsupported, for that exact reason.

Most probably lineage isn't yet updated to June vendor, which includes the qpr bump.

Try to flash the previous release found here.

Otherwise you're on your own, because I can't support/test every custom ROM out there.
[Google Pixel 6 Pro] sylj69:
MOD TRANSLATION

"I just tested version 1.0.2 and it goes to the desktop fine. It seems that I can only flash version 1.0.2 first."

*************************************

我刚刚测试了1.0.2版本，它可以正常进入桌面。看来我只能先刷1.0.2版本了。
[Google Pixel 6 Pro] Nayem-Mahfuz:
I need help please! I flashed the kernel using kernel flasher but now it's stuck on the Google logo(Where it loads), I did not disable verity and verification as I did not want to wipe the device( So the problem may lie within it). I am able to get to fastboot but the problem is I do not have a computer at the moment, and while I can use bugjaeger with another device... I am not sure what to do. I downloaded the June factory image but how do I use bugjaeger to flash it? Thanks you in advanced. Usually I have a PC at my disposal and could've have fixed the problem. I know how to use bugjaeger but if someone could run me through I would be very helpful (Considering the fact even it is possible). Sorry for the hindering english.

EDIT: I manually updated the factory image of April (I was on the April build) but now when press start on the bootloader menu it shows the Google logo and come backs to the fastboot mode.
[Google Pixel 6 Pro] slickrasta:
For anyone else who installs 1.1.0 on lower than June and gets stuck in a bootloop on their P6. Hold power+volume down to enter fastboot then connect to PC go to flash.android.com and flash June update with no checks on anything (don't disable verity). Then reroot (I like to use PixelFlasher.exe) then install kernel using KernelFlasher and you're good to go.
[Google Pixel 6 Pro] Justarandomguy:
Is there any way to make kernel use max frequencies? I tried on smart pack kernel manager and max frequencies jumped from higher to lower and so, is there any way to set a max frequency and make it stay there without using performance govnor for benchmarking for example? Been using this kernel for months and loving it ❤️❤️