Development [Kernel][21.03.2023][Android 13.0.0]Kirisakura 1.0.0_Raviantah for Pixel 6/Pro aka "RAVIOLE"

[Ghisy]

I flashed the newest EMEA July update (SQ3A.220705.001.B2) and it seems like the kernel is working fine! Don't know if Google made any changes kernel-wise, probably not.

 

[triggerhappy_]

How could I safely flash the new 12.1.0 (SQ3A.220705.004, Jul 2022) firmware being on the latest Kirisakura Kernel? Never done an update before, just curious. Appreciate.

 

[Freak07]

I flashed the newest EMEA July update (SQ3A.220705.001.B2) and it seems like the kernel is working fine! Don't know if Google made any changes kernel-wise, probably not.

No changes have been pushed, so I'm pretty sure by now there are none.

How could I safely flash the new 12.1.0 (SQ3A.220705.004, Jul 2022) firmware being on the latest Kirisakura Kernel? Never done an update before, just curious. Appreciate.

Either use factory image or full OTA zip to update. That's probably the easiest route. Both will just flash the updated stock firmware, so you're device will end up being on the new stock firmware.

Search the forums, there are guides on how to update.


Afterwards just follow the instructions to flash the kernel again if you desire to do so.

 

[triggerhappy_]

If you update via either factory image or full OTA zip, you don´t need to restore original partitions.

So, afais, all I need to do is flashing the latest stock factory image.

 

[Utini]

Any chance to make the phone less fragile to hot summer days?

E.g. by throttling more/sooner at a certain temp limit?

15mins on the lake (30C Temperature) of browsing in the sun and it will shut off connectivvity due to temperatures.

 

[jericho246]

Any chance to make the phone less fragile to hot summer days?

E.g. by throttling more/sooner at a certain temp limit?

15mins on the lake (30C Temperature) of browsing in the sun and it will shut off connectivvity due to temperatures.

I feel your pain man.

This kernel has CleanSlate kernel features such as Battery saver which can be used to reduce heat. In my experience the difference was minimal, but maybe it'll be different with your usage. Worth a try I guess.

[KERNEL] CleanSlate T2.4.4/S1.4.4 |S2S|AdBlock|VIB|BatterySvr [Dec 7]

tbalden's CleanSlate kernel for Google Pixel 6 Pro The User Experience Kernel leaning towards Stock Stability plus UX features. Rock stable stock approach, performance smooth and issue free "No-Root is a State of Mind" As always tbalden is...

forum.xda-developers.com

You gotta install Clean Slate Companion app + the configuration app. Grant necessary permissions and then choose a Battery Saver level from 1 to 3, with 3 being the most aggressive.

 

[Freak07]

Any chance to make the phone less fragile to hot summer days?

E.g. by throttling more/sooner at a certain temp limit?

15mins on the lake (30C Temperature) of browsing in the sun and it will shut off connectivvity due to temperatures.

Use CleanSlate battery saver during those conditions.
Edit: i was ninja'ed.

That limits only cpufreq though. Might not make the biggest difference, but still useful.
Running display at highest brightness, while being in direct sunlight, high ambient temp, mobile signal etc, it's just a matter of time until it gets hot.

Apart from that thermal throttling is not directly controlled by the kernel, but the thermal hal. That part is not open source afaik and I don't want to touch it either way.

 

[Utini]

Thanks. I also just changed from "always dark mode" to "light mode during hot hours".

I hoped that the light theme heats up slower than the dark theme :S but more battery usage then I guess.

 

[shizonic]

Is it safe to flash over the august update?

 

[roirraW "edor" ehT]

Is it safe to flash over the august update?

Probably not since @Freak07 was supporting the Stable Android version only, and not Android 13 Beta. Now that 13 is Final, I'd just wait.

But perhaps someone who enjoys risk more than me these days will test the theory!

 

[shizonic]

Probably not since @Freak07 was supporting the Stable Android version only, and not Android 13 Beta. Now that 13 is Final, I'd just wait.

But perhaps someone who enjoys risk more than me these days will test the theory!

I see. Thanks.

Maybe I gonna be the one who risk it by tomorrow...

 

[Freak07]

Is it safe to flash over the august update?

Probably not since @Freak07 was supporting the Stable Android version only, and not Android 13 Beta. Now that 13 is Final, I'd just wait.

But perhaps someone who enjoys risk more than me these days will test the theory!

if you want to know if it´s safe to flash the A13 stable factory image over A12 firmware with this kernel installed, yes it is since it replaces everything.

if you want to know if the A12 kernel runs on A13, it won´t.

 

[shizonic]

if you want to know if it´s safe to flash the A13 stable factory image over A12 firmware with this kernel installed, yes it is since it replaces everything.

if you want to know if the A12 kernel runs on A13, it won´t.

Thanks for clarifying.

Are you planning an A13 version of your kernel?

 

[TheLoonyRebel]

Thanks for clarifying.

Are you planning an A13 version of your kernel?

I believe it was stated a few pages back that once A13 is final the kernel would migrate over to A13 as well.

 

[shizonic]

I believe it was stated a few pages back that once A13 is final the kernel would migrate over to A13 as well.

Glad to here that. Thanks.

 

[Freak07]

Thanks, I'll take a look and see what's what, though scripts aren't really my forte and there are a lot of them.

Do I even need the AOSP folder then? Do I even need to build using this method or are you doing it on a more simple, elegant way?

I'm used to just simply building the Image and dropping it into the device folder of a full AOSP build and then make bootimage

It seems I forgot to reply to this.
The kernel is now in more "places" than the boot.img and afaik nobody managed to build a monolithic kernel yet.
Given the kernel build environment I also don´t see a need here.
The parts of the kernel end up in boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img.

The aosp folder contains kernel/common, which is just the GKI kernel. If you just compile the zImage, you probably will need to force load the other device specific drivers which end up in vendor_boot (those that need to load early, plus dtb) and in vendor_dlkm to make them load.

Ideally you want to compile zImage, dtbo.img, vendor_boot and vendor_dlkm. That will give you a "full" kernel build on pixel 6 devices. This is also what the scripts do, you´ll end up with those images in the out/.../dist folder of the environment.
You can invoke the build with the scripts. private/gs-google and private/google-modules is where the kernel repos are.
Since my kernel changes abi as it´s very very far from stock, I need to generate new abi, otherwise build will fail. For example I do so with build/build_abi.sh --update.

 

[Freak07]

I believe it was stated a few pages back that once A13 is final the kernel would migrate over to A13 as well.

Glad to here that. Thanks.

indeed

 

[Freak07]

soon

 

[Freak07]

Update to 4.1.0

Hey guys and girls,

I hope everyone started into a good week. Here´s the next release. It´s for stable Android 13.
Thanks to Google releasing the kernel source for the previews and the betas I´m able to push this update out very quickly. As in the past, the code didn´t change between last beta and stable release.

There are again a lot of changes in this release. I´ll try to keep the release post short as I don´t have that much time lately.


FHD/1080P Support for Pixel 6 Pro

The biggest change is FHD support for the Pixel 6 Pro. If you follow twitter you might have seen this tweet from @MishaalRahman.
Instead of using the display driver that´s supposedly for the Pixel 7 Pro, FHD support was added to the Pixel 6 Pro display driver. There were a few obstacles to make it run properly on the Pixel 6 Pro, but I got it working nicely so far. If anyone has more experience than me regarding panel timings, display drivers etc, feel free to push any improvement as a pull request to my github or point me towards any improvement.

As a result you can now select 1080p resolution from settings after flashing the kernel. Dynamic refresh rate works, brightness scaling works, no tints, colour shifts or contrast issues either. AOD has a 1080p Low-Power timing as well.

You´ll find a few more infos with a short video on my tweet here:

https://twitter.com/i/web/status/1559439100113207296

It´s perfectly usable on a daily basis so far. I ran it for a few days without issues on my end. While the advantage might be debatable (saving battery, less load on GPU, still needing to drive the same amount of pixels in the end even on lower resolution, etc etc) having options is nice and this is why I decided to ship it.

Apps need to redraw after switching resolution, sometimes 1080p on big display size selected in settings the UI looks a bit sketchy. So I think Google is still working on that.

There´s however one bug I found so far that makes me believe this is still very much a WIP from google. If having the "show current refresh rate" option from dev settings enabled while switching resolutions, the display will black out and a restart needs to be forced by keeping the power button pressed or using adb interface to restart the phone. This is not due to the kernel, but display settings in framework getting scrambled as it´s not yet implemented 100% on googles end. So be warned.


MM Subsystem Rework

MM subsystem was completely reworked including many improvements from linux-mainline. During this MGLRU was also reworked a bit and works better now. I´ll include links to a few of the improvements/patchsets in hide-tags below, if you´re interested beyond that please check out my github.
links:

Spoiler

[PATCH v5 0/8] Remove dependency on congestion_wait in mm/

[PATCH 0/9 v6] Introduce a bulk order-0 page allocator with two in-tree users

[PATCH 0/9 v6] Use local_lock for pcp protection and reduce stat overhead

[PATCH 0/6 v2] Calculate pcp->high based on zone sizes and active CPUs

[PATCH v2 0/6] Follow-up on high-order PCP caching

Additionally tie in a few of the MM changes into the powerhal. For example Proactive compaction is more aggressive during screen-off/device suspended operations to improve long term-performance.

Other changes:

Also tune the powerhal and implement all A13 changes, according to the changes that were already present on A12.

Latest changes from f2fs-stable are included, which include several bugfixes and small improvements.
Binder improvments/fixes, scheduler improvements from kernel/common, performance for exfat formatted storage device improved (niche use case, but still nice) and other little improvements.
For other changes and details please take a look at github.


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:

- Rebase kernel fully on A13 trees
- Linux-Stable bumped to 5.10.136
- FHD/1080p support for Pixel 6 Pro
- all previous features and improvements kept intact
- bump f2fs-stable to latest available
- rework mm subsystem (check git for more details)
- scheduler improvements
- binder improvements from kernel/common
- improve exfat performance (if someones uses exfat formatted devices)
- loads of other changes from kernel/common
- update powerhal to account for a13 changes and port existing changes over
- loads of other changes, please check github



Download:

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

 

[Sek0n]

Perfect timing. Just updated to 13 stable a minute ago, and saw the update get posted. Flashed and working so far. Thanks again!