Development [Kernel][04.01.2023][Android 13.0.0]Kirisakura 4.4.1 for Pixel 6/Pro aka "RAVIOLE"

[djo_5296]

Anyone try 4.2.0 on Nov update yet?

there's usually a new Kirisakura version when Pixel monthly update arrives so im waiting for that before I update to Nov

 

[AlDollaz]

there's usually a new Kirisakura version when Pixel monthly update arrives so im waiting for that before I update to Nov

This is the way.

 

[Freak07]

Anyone try 4.2.0 on Nov update yet?

there's usually a new Kirisakura version when Pixel monthly update arrives so im waiting for that before I update to Nov

This is the way.

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.

Stuck at 120 all them time is it related to the kernel ?
So far the kernel is awesome great work hope you will port the faceunlock feature from pixel 7 pro
(I don't have force peak refresh enabled)

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.

 

[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

 

[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

 

[ctfTijG]

Thank you!
Just did the update/flash. Running kernel v4.3.0 smoothly on the Nov 2022 release.

 

[Houssem9506]

Thank you!
Just did the update/flash. Running kernel v4.3.0 smoothly on the Nov 2022 release.

Going to do the same

 

[AlDollaz]

Thank you!
Just did the update/flash. Running kernel v4.3.0 smoothly on the Nov 2022 release.

Same here. Buttery.

 

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

 

[Freak07]

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.

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?

 

[Suavie103]

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.

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.

 

[majorfigjam]

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?

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.

 

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

 

[Freak07]

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.

I´ll follow up via PM.

 

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

 

[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

 

[phaino00]

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

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

 

[dizzota]

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

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

 

[phaino00]

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


View attachment 5756801

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.

 

[Freak07]

Thank you!
Just did the update/flash. Running kernel v4.3.0 smoothly on the Nov 2022 release.

Same here. Buttery.

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.

Thanks for the kind words and I´m glad it´s working fine for you. Enjoy the ride!

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.

Appreciate the kind words
I stopped doing beta testing for big tech companies a while ago 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 )

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


View attachment 5756801

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.

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!