yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Freak07:
Google did not yet push the source for november firmware as of now. Usually I have all of the non device specific updates months ahead, by regularly merging kernel/common and linux-stable.

However sometimes there device specific changes that depend on a combination of kernel driver/ firmware related changes.

If one of those changes doesn´t work without the other part, flashing a kernel not updated with the latest source may introduce issues, if the new firmware can´t work without the kernel counterpart change.

It´s "usually" fine as long as you not jump between between major android versions or QPR versions.

But if you want to be on the safe side, it´s better to wait for me to inspect sources and push out an updated build or give green light in case there are no changes done to the source, as @djo_5296 and @AlDollaz pointed out. :)

Since Google didn´t push the source yet, I went ahead and flashed the older build on november firmware, it booted up fine and so far no issues. So it should be fine.

But if you want to be on the safe side, wait for Google and me. :)

No, that´s not related to the kernel. The framework decides how the framerate is handled. The kernel just provides the endpoints the frameworks decides when to switch from and has nothing to say about this.

I remember back when I set up the Pixel 6 Pro, I restored data from my Pixel 4 Pro via google backup and it messed up the Pixel 6 Pro badly, as it wouldn´t allow the phone to go to 120hz, unless via forcing in dev options.

I tried everything I can think of, but in the end only wiping and starting fresh without setting my data up helped.

I don´t know if it´s an app or service, or maybe some mod that you have installed that´s causing the issue on your end. I´d remove all mods and dirty flash back to stock (without wiping, don´t forget about your vbmeta flags if you disabled them previously, flashing a firmware will default them to enabled) and start troubleshooting from there if it still happens.
[Google Pixel 6 Pro] Freak07:
It was just coincidence the bug hit you after that reboot, there´s really nothing to look into.

One thing that comes to my mind is you could check if you use an app that somehow utilizes the proximity sensor and is for some reason auto-started and stuck in the background.

As soon as the prox sensor is activated on that phone refresh rate drops to 60hz.

Maybe that will prevent the wipe on your end. Don´t know which app it could be though, I guess all messengers (whatsapp, telegram etc) , third party caller apps, devcheck has an option to test prox sensor...

The display driver in the kernel is exactly stock and the refresh rate switching is not handled by the kernel, but the framework. The kernel just provides the endpoints the framework is using.
[Google Pixel 6 Pro] Utini:
I am still on stock kernel and sometimes have the same problem.

Also videocalls in Telegram seem to block the proximity sensor sometimes.

Additionally I have a bug where location is constantly being used (at least according to the statusbar icon) while no app is listed in recent location permission usage.

So all of that is not caused by the kirisakura kernel... but maybe the kernel could fix issues ;-P
[Google Pixel 6 Pro] Texan1:
What app(s) are you using to check refresh rate?
[Google Pixel 6 Pro] ansh1996:
LMAO you are spot on. I found the problem i think. I turned on something in CleanSlate not sure what it was going to do but sounded interesting haha. I'm guessing it was keeping the proximity sensor on since the problem seems to have gone after i turned it off and rebot. Please see the screenshot. Its the first toggle.
[Google Pixel 6 Pro] Freak07:
nice catch. :)

yeah by default it should be off on the pixel 6 pro.

I´ll talk to @tbalden , maybe there should be a warning for p6pro.

glad you don´t need to wipe now. every prevented wipe is a good one.

either floating monitors of devcheck app or the inbuilt option from developer options to show refresh rate.
[Google Pixel 6 Pro] Texan1:
Thanks. I used this method and appears to be working fine - when I scroll it shows 120 and when I stop it shows 60.
[Google Pixel 6 Pro] Lughnasadh:
As Magisk Canary v. 23015 has been released, just a reminder for people to patch the boot image provided by this kernel and not the factory boot image. As it was very early in the morning and I still had only 1 eye open, I forgot to do this and patched the stock boot image rather than this kernel's boot image and got into a bootloop (oops 🤭). After patching the kernel's boot image with the new Magisk version and flashing that everything was fine.
[Google Pixel 6 Pro] s3axel:
I saw the update notification within the Magisk app, what I did from within the app is: 1. update the app and 2. update Magisk from within the (restarted) Magisk app by selecting "Direct install" - reboot, done.....
[Google Pixel 6 Pro] Lughnasadh:
Yeah, I usually always just patch the image b/c I've seen people in the past sometimes have problems when doing a direct install. Plus, habit 🙂

Good to know the direct install method worked 👍
[Google Pixel 6 Pro] Texan1:
Does updating Magisk like this affect the kernel at all?
[Google Pixel 6 Pro] s3axel:
Well, it patches the boot.img directly on the device.... If you are asking whether it interferes with kernel functions: I don't think so.....
[Google Pixel 6 Pro] TotallyAnxious:
You can update magisk directly via app or update by patching kernel and flashing kernel via instructions in OP.
[Google Pixel 6 Pro] old_fart:
How does the changes to Magisk Canary v. 23015 effect our updating & rooting methods ? Not at all ?
[Google Pixel 6 Pro] Lughnasadh:
Doesn't seem to affect the updating and rooting methods at all. Both patching the kernel's boot image or direct installing have been reported to work.
[Google Pixel 6 Pro] ansh1996:
A warning would definitely help. I cant seem to think of a reason why proximity sensor would need the the screen refresh rate to be set to 60Hz haha.

I was really not looking forward to reinstalling all my apps. Thanks for your insight! :)
[Google Pixel 6 Pro] Gytole:
So yes, for those who are wondering or are confused, IF YOU ARE ROOTED, just update the magisk APP first, then update MAGISK. DIRECT INSTALL WORKS ON THE PIXEL 6 PRO. Update, reboot. Done. I decided to try it and it worked flawlessly for me. Glad I didn't have to fastboot anything again hahaha.

Some screeny's for helpskies
[Google Pixel 6 Pro] rogosteve:
Does the newest update with clean slate work on the regular 6? Or only on the pro?
[Google Pixel 6 Pro] Freak07:
It might be that 120hz somehow "confuses" the proximity sensor due to some frequency thing interfering.

As soon as the prox sensor is used by an app, the phone drops to 60hz.

For example calling somebody, makes the phone also drop to 60hz.

The newest release you can find in the OP works fine on the regular Pixel 6, but the CleanSlate features won´t work.

If you want to use those features on a regular Pixel 6 use the attached images. It´s the same as 1.3.0, just added CleanSlate feature support for the regular Pixel 6, thanks to @tbalden for implementing and @TotallyAnxious for testing.

I don´t have time to update the thread, so I´ll do it this way until the next official release.

Follow the instructions in the OP.
[Google Pixel 6 Pro] xflowy:
hey! a question to all the pros here: i just went to unlock and root the new pixel 6 pro of a buddy and missed that the phone was only updated to the 036 nov build (and not the 037 one). however, for the rooting process i went with the factory image of the latest nov build (the 037 one) and thus flashed vbmeta and a patched boot img from that build on the 036 one, that was installed. is this mismatch somewhat harmful to the device? thanks guys!
[Google Pixel 6 Pro] roirraW "edor" ehT:
A couple of us have answered in your stand-alone thread about the problem.
[Google Pixel 6 Pro] Freak07:
Google pushed the source now, but I have to leave for work.

I´ll update the kernel probably in the evening if I find time.

Stay tuned :)
[Google Pixel 6 Pro] Freak07:
Update to 4.3.0

Hey guys and girls,

I hope everyone started well in the new week. Here´s the next release and it´s again a rather big one with lots of under the hood improvements.

We already had all the changes in from the November security patch release released, due to merging linux-stable stable, some code of the QPR Beta and kernel/common in advance.

I added the following part about linux-stable in the last release too, but to further emphasize it with a bit of context.

5.10.148 and 5.10.149 fixed the CVEs discussed here and here. Those were fixed on kernel common on November 2nd. It might take a few months until they trickly down into any officially shipped android kernel.

The kernel is now at 5.10.152 way ahead of the stock kernel. To further emphasize the importance of this. About 90% of kernel security issues are solved in linux stable. While I didn´t check the actual number myself, I´d have estimated about the same (80-90%) before actually reading the slides from @arter97 presentation.

What also needs to be kept in mind is that a big part of those security issues are resolved in linux-stable sometimes months ago before those patches end up in a monthly security patch. (as pointed out above)

Amongst linux-stable upstream there are a few other updates in this kernel.

I´d like to write all of this with more detail, but at the moment I lack the time to do so.

Kernel is compiled for stable A13, not A13 QPR Beta!

I wish everyone a nice day.

If you´re one of the unfortunate ones that suffer from the device is corrupt bug on pixel 6 series please take a look at the FAQ at the beginning of this thread it contains a solution. The issue is probably caused by a bug that affects pixel 6 devices and has nothing to do with magisk or a kernel, it just happens to get triggered when using any of those.

Changelog:

- Linux-Stable bumped to 5.10.152

- kernel is compiled with latest prebuilt google clang 15.0.3

- f2f2 bumped to latest f2fs stable

- some patches from pixel 7 source

- updates from kernel/common to several subsystems

- include bbrv2 from google, more info here

- match 1080p display timings to pixel 7 source

Download:

Attached to release post as AFH does not allow me to upload files at the moment.

I´ll push to AFH once it´s back up.

Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.

I wish everybody a great day/evening!

Have fun, enjoy the kernel and your phone.

If you like my work please consider a donation.

Donations are not mandatory but very welcome.

If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak07
[Google Pixel 6 Pro] ctfTijG:
Thank you!

Just did the update/flash. Running kernel v4.3.0 smoothly on the Nov 2022 release.
[Google Pixel 6 Pro] AlDollaz:
Same here. Buttery.
[Google Pixel 6 Pro] majorfigjam:
Thanks for the new kernel. Unfortunately it still doesn't play nicely with Musicolet in conjunction with a combined USB-C power / 3.5mm audio adapter. The issue seemed to start only with 4.2,.0, as I had previously been using your kernel without problems since I first bought the 6Pro.

I have no problems with the stock kernel, but with 4.3.0 Musicolet crashes pretty much as soon as the screen times out. I've attached a logcat file from boot up onwards, so hopefully you might be able to see where the problem lies.
[Google Pixel 6 Pro] Freak07:
I have 4 different usb c to 3.5mm adapters at home and can´t reproduce the issue. :(

11-09 19:33:46.984 860 7994 E audio_hw_output_stream: out_pcm_write: fail: -5 cannot read/write stream data: I/O error
11-09 19:33:46.985 860 7994 D audio_hw: shutdown: deep-buffer-playback
11-09 19:33:46.986 860 7994 D audio_hw_aoc_route: deep-buffer-playbackP usb-headphone 0
11-09 19:33:46.986 860 7994 D audio_hw_aoc: aoc_get_hw_intf_ctrl : HW_INTF : 10
11-09 19:33:46.986 860 7994 D audio_hw_usb: release_setting: card 1 dev 0x4000000 (tx active 0, rx active 1)
11-09 19:33:46.986 860 7994 D audio_hw_usb: send_cmd_to_monitor_thread: sending command 2 to monitor thread.
11-09 19:33:46.991 860 1376 D audio_hw_usb: read_cmd_from_pipe: reading command 2 from main thread.
11-09 19:33:46.991 860 1376 D audio_hw_usb: cmd_to_thread_monitoring_mask: Disabling monitoring USB Rx.
11-09 19:33:46.991 860 1376 D audio_hw_usb: read_cmd_from_pipe: current monitoring mask is 0
11-09 19:33:46.991 1135 1135 D AOC : F1:MSG: controller.cc, 273: AudioOutCtrl: cmd ID: 0x00c9, tag: 0x50 [cntr = 94]
11-09 19:33:46.991 1135 1135 D AOC : F1:MSG: controller.cc, 811: AudioOutCtrl: ipc: audio_output_co, cmd ID: 0x00c9, tag: 0x50, rc: 0
11-09 19:33:46.991 1135 1135 D AOC : F1:MSG: controller.cc, 273: AudioOutCtrl: cmd ID: 0x010f, tag: 0x51 [cntr = 95]
11-09 19:33:46.991 1135 1135 D AOC : F1:Unregistered Source 5 from Sink 3
11-09 19:33:46.992 1135 1135 D AOC : F1:AT Map:0 (LL:0), 0 EPs active, Power: Yes, Config: No
11-09 19:33:46.992 1135 1135 D AOC : F1:Mixer 3 configuration changed: (0)
11-09 19:33:46.992 1135 1135 D AOC : F1:Sink 3 Configuration changed: ULL (disabled)
11-09 19:33:46.992 1135 1135 D AOC : F1:MSG: usb.cc, 501: Stop playback, TX enabled = 1, RX enabled = 0
11-09 19:33:46.992 1135 1135 D AOC : F1:MSG: usb.cc, 1837: Release system memory access
11-09 19:33:46.992 1135 1135 D AOC : F1:MSG: controller.cc, 811: AudioOutCtrl: ipc: audio_output_co, cmd ID: 0x010f, tag: 0x51, rc: 0
11-09 19:33:46.992 1135 1135 D AOC : H0:Mixer AMixUSB: 480 samples (0000/0000) (OFF SC)
11-09 19:33:46.992 1135 1135 D AOC : H0:Mixer configuration updated

The first line is the problem. Something is interrupting playback and afterwards the driver shuts down cleanly as expected. The first line is not kernel space however, but rom side of things.

11-09 19:33:46.789 1135 1135 D AOC : F1:[USB] ISR ms min: 0.985351 max: 1.014403 avg: 0.999991

as you can see above 150ms before that error, everything is fine with no error in between.

I´m not sure I´ll be able to debug that, since another user told me he faces the exact same issue on stock pixel 6 kernel. The log looks exactly the same.

Since you said screen times out, does it also happen if you shut down the screen via power button?

Can you next time get me a dmesg as well? Also when plugging in your dongle?

Does it happen every single time? Is it reproducible 100%?

So 4.2.0 had the issue, while 4.1.6 did not?
[Google Pixel 6 Pro] Suavie103:
I use a Moshi USB-C power / 3.5mm dac, I've been experiencing the same cut outs once my screen times out. No issues with Bluetooth. Just wired audio.
[Google Pixel 6 Pro] majorfigjam:
Sorry, will have to reload tomorrow to get dmesg. But yes, it is 100% reproducable with 4.2 or 4.3, but not at all with 4.1.6. If I recall, turning the screen off doen't kill audio, but it dies a minute of two later.
[Google Pixel 6 Pro] digger16309:
Thank you for the kernel update and for getting far ahead of the actual patches. Restore to stock instructions worked as expected. V4.3 working beautifully on Nov update.
[Google Pixel 6 Pro] Freak07:
I´ll follow up via PM. :)
[Google Pixel 6 Pro] scott.hart.bti:
Looks like I'm switching back from the beta to stable... I knew I'd end up doing this.. can't help but to run your kernel! Thanks for the new update as always sir.
[Google Pixel 6 Pro] dizzota:
i tried flashing 4.3.0 using KF on my pixel 6 (after updating to November 2022), but once i rebooted, it refused to boot android and simply kicked me back into the bootloader each time :(

am i doing something wrong here? i'm suspecting that the module didn't install properly
[Google Pixel 6 Pro] phaino00:
What were your steps? I flashed this with KF yesterday with no issues. Pixel 6 here too. Are you using the most recent KF (alpha 12)?
[Google Pixel 6 Pro] dizzota:
i uninstalled 4.2.0 while i was on October 2022 and updated to November 2022, i updated KF to alpha 12 first, then i installed 4.3.0

i rebooted my pixel, and after roughly 5 seconds when it displays "Google," it cuts to black, then boots into "Fastboot Mode" instead

enter reason states "reboot bootloader" (and no visible errors, weirdly enough)

i got out of the bootloop by just dirty flashing the factory image, but the other boot slot is still unbootable if i try to switch to it

i've attached the ak3 log from when i was installing 4.3.0, though i doubt it'll be of any help since i've legitimately never had this happen to me before with custom kernels...? it's bizarre
[Google Pixel 6 Pro] phaino00:
That is bizarre. There are many possible causes. You may want to ensure you flash the factory image to both slots and wipe data to get back to square one to eliminate the issue with the unbootable slot a.
[Google Pixel 6 Pro] Freak07:
Thanks for the kind words and I´m glad it´s working fine for you. Enjoy the ride!

Appreciate the kind words :)

I stopped doing beta testing for big tech companies a while ago :D especially since the betas are mostly testing only platform changes and no pixel features in advance. But I know the feeling of excitement and running something bleeding edge still quite well. (that´s why latest google prebuilt clang is used in this project for example ;) )

the log looks fine from a quick glance. I don´t know why it isn´t working for you.

Flashing the factory image will not change slots. The factory image will always flash to the current slot, compared to a full OTA zip, which will flash to the currently inactive slot and switch to the updated previously inactive slot upon successful installation and the next boot.

So @phaino00 ´s advice to make sure to flash to both slots is a good one!
[Google Pixel 6 Pro] hamzih0:
On ricedroid root disappears when flashing tried a few times, how do I get root after using it? I noticed I have a los recovery can I sideload or do I have to patch a boot.img? I can't find the boot file anywhere
[Google Pixel 6 Pro] miqcea3:
Custom kernels not working on custom roms. You can flash rom and magisk again to get root back.
[Google Pixel 6 Pro] hamzih0:
That's what I'm asking do I need to patch boot.img it or can I sideload on Los recovery?
[Google Pixel 6 Pro] Nightf0x_007:
November update's battery not so good so far, also someone here was complaining before from a problem caused while using a usb c to 3.5mm audio it got back here but idk whats causing it actually
[Google Pixel 6 Pro] Freak07:
Battery life difference is not due to kernel.

I tried 4 different USB C to 3.5mm adapters and all work fine here. I can't reproduce any issues. Local Playback of mp3/flac, Spotify, audible and YouTube videos with screen off/timing out.

The log I saw doesn't point towards the kernel.

I sent another user a test kernel via pm, but did not hear anything back. If you're interested I can send it to you as well.

If the issue was gone for you in October it likely isn't related to the kernel at all. :)
[Google Pixel 6 Pro] Nightf0x_007:
Yes in october after multiple reboots its gone but it came back with november's update, when screen goes off and background playing is working the issue appears and phone lags, system ui crashes and phone reboots
[Google Pixel 6 Pro] Rachid.Ala:
Thank you for your kernel, everything is flawless and bugless here.

But idle drain at around 1,9%/h is normal ?

I have "Now playing" feature enabled, it could be because of that ? Thanks again
[Google Pixel 6 Pro] Freak07:
It depends on the setup of your device, network quality, usage etc. The kernel doesn´t have much impact there.

You can check if anything is keeping the phone awake during the day with better battery stats.

Yes, well I saw reports about usb c to 3.5mm adapter problems on XDA and reddit as well on stock firmware.

I can´t reproduce any issues and the logs don´t show anything so I can´t do more at the moment.
[Google Pixel 6 Pro] Lughnasadh:
I doubt "Now Playing" has anything to do with it. I have that enabled and am getting excellent idle drain on stock kernel.
[Google Pixel 6 Pro] Freak07:
Neither do I have a problem running my kernel with now playing enabled :)

And generally the kernel has not much to with idle drain. Network coverage, wifi signal, usage patterns, usage and not to speak of apps and services running in the background have far more impact compared to a kernel. :)
[Google Pixel 6 Pro] Lughnasadh:
Absolutely! Many variables go into idle drain and the kernel is usually not one of them.
[Google Pixel 6 Pro] amritpal2489:
Why is A13 QPR not supported?
[Google Pixel 6 Pro] AlDollaz:
No sources.
[Google Pixel 6 Pro] amritpal2489:
Ohhh .. So no kirisakura kernel option available... That's a bummer...

Is there a Telegram group?
[Google Pixel 6 Pro] Freak07:
There are sources for QPR Beta available, that´s not the problem.

Copy paste from another post in this thread where I already answered the question, why I don´t support dev-previews/betas:

No, I have no plans to support A13 beta or any dev-preview or beta firmware. It will be supported once it´s stable. I don´t have the time, desire and motivation to support it.

It all boils down to the fact that I enjoy doing what I´m doing here, I do it in my free time and share what I´m using myself with others so they can enjoy it with me and I want to release something that´s polished, extensively tested and stable.

Since that questions comes up from time to time:

I´m not comfortable releasing something I´m not running/testing extensively myself with loads of changes compared to the stock base.

I never felt the urge to do beta testing for companies just to run more recent software too.

I don´t have time to test, maintain and build that many compilations, let alone switching between Beta Firmware and Stable firmware on my phone for testing. It´s simply not possible, and I don´t want to release something that´s not extensively tested.

I think sometimes people don´t realize how much time goes into this aspect of my kernels projects alone.

Also try to see it that way:

Merging code updates takes time. Be it linux-stable, f2fs-stable, kernel/common, lrng updates, updates directly from Google or a lot of the features that are descrbied in the OP. Sometimes longer, sometimes shorter.

This kernel is now very very far from the stock base (compared to the other kernels available) as is also reflected in the OP. So while merging code updates will take time as there are many conflicts that need to be solved on my kernel. Even if the branches are somewhat similar I still need a lot of additional time to manage this aspect alone, not to speak of testing on my device to make sure nothing is broken.

There´s no longer just the kernel repo itself to manage. With the introduction of GKI, the kernel is split in several sub repos for different device specific drivers, touchscreen, wifi, uwb, nfc, bt, etc etc. Those needs to be managed too, as well as other repos from the build environment as they´re different between stable and beta.

Powerhal changes need to be monitored and adjusted each month too, as there might be differences between stable and beta as well.

Building takes time. Every compilation, for testing or release purposes takes about 15 minutes. Only building, not adjusting the code. Every release here needs 2 different builds for oriole/raven. Yes I can do something else during the compilation, but it´s still time I need to spend.

No there´s no telegram group. Everything you need is here on XDA. All information is in the first few posts. If you use the search function you´ll find even more I guess.
[Google Pixel 6 Pro] dwxvi:
I'll most definitely be hopping back to stock tomorrow and flashing this kernel, @Freak07. Your work here is greatly appreciated, and I can tell you've put a lot into this kernel! I'll be doing my best to report back after I've tested for a few days!
[Google Pixel 6 Pro] ada12:
Thanks for the release as Always )

*I disable vbmeta verification signature and Seem device corrupted message is fixed as expected 😎