Development [Kernel][21.03.2023][Android 13.0.0]Kirisakura 1.0.0_Raviantah for Pixel 6/Pro aka "RAVIOLE"
- Thread starter Freak07
- Start date
I just loaded this kernel on a brand new Pro (Raven). I ran the stock kernel for about a day before flashing it. I figure with 100+ pages that others are very happy and based on my initial experience, I am as well.
I will be making a donation.
One question, and I'm unsure if this is kernel-related or not. As Android Authority documented, the rapid charging at 30W never takes place and drops to 18W and less the more the battery is charged, even with adaptive charging turned off. I'm sure this isn't news to most of the followers of this thread but it was a surprise to me.
Can this be overcome at all in the kernel or some other mod?
I will be making a donation.
One question, and I'm unsure if this is kernel-related or not. As Android Authority documented, the rapid charging at 30W never takes place and drops to 18W and less the more the battery is charged, even with adaptive charging turned off. I'm sure this isn't news to most of the followers of this thread but it was a surprise to me.
Can this be overcome at all in the kernel or some other mod?
Hey everyone, it might be an extremely dumb question, but I thought it'd be better to ask it rather than face the consequences of ignorance.
When the next security update drops, what should I do? If I update, will I go back to stock kernel, or the device will stop booting and I should revert back to stock before updating?
Thanks and again, excuse my stupidity
When the next security update drops, what should I do? If I update, will I go back to stock kernel, or the device will stop booting and I should revert back to stock before updating?
Thanks and again, excuse my stupidity
Probably not, as I don´t own the device and this kernel has diverged pretty far from stock so i don't think it would be compatible as is.
Hey,
thank you very much for the donation. It´s really appreciated and the kind words mean a lot.
There´s actually more to come with the next release, that should improve things further. But lets see how all the testing goes.
As for the question with charging. I guess it´s theoretically possible to somehow force the phone to charge at 30W, no matter if kernel mod or some other way, but this is where my comfort zone ends. I wouldn't advise anyone to play with this, if you´re not prepared to accept damage to any components inside. Google has the means to do long term testing.
I know most other brands offer way faster charging, but I'm actually happy some brands stick with slower charging.
For my needs the phone charges fast enough. And if it stays cooler every single charge cycle than other phones that charge at slightly higher rates, that's an advantage for me. But I also understand the opposite argument very well, that it charges comparably slower than competitors, which is a disadvantage for other users.
The main problem was that google insinuated (let's just call it like this) the phone would charge at 30W, when only the charger provides this, while the phone doesn't actually.
Just flash either a factory image, a full OTA.zip or use the web tool to update your device like you usually would following any of the guides here.Hey everyone, it might be an extremely dumb question, but I thought it'd be better to ask it rather than face the consequences of ignorance.
When the next security update drops, what should I do? If I update, will I go back to stock kernel, or the device will stop booting and I should revert back to stock before updating?
Thanks and again, excuse my stupidity
This will just update your device to the new stock firmware.
You only need to revert back to stock in case you want to take an incremental OTA, as the incremental OTA needs to stock partitions for a successful update.
Then wait for me to update the kernel to include changes for the next firmware and flash again. Or in case there are no changes, I´ll post it here.
Thanks for the reply. I understand the discomfort and not wanting to fry devices. The fact that it doesn't actually charge at 30W (and other devices do or even higher wattage) is poor marketing.
What I've found to be troubling is that it can handle 18W consistently without overheating but Google throttles the power lower than that threshold continuously the more charged the battery is. I'm sure there are reasons for it.
that doesn't answer my question, the documentation you linked in the original post doesn't state how to build non-official gki kernelsCheck here:
[Kernel][09.02.2023][Android 13.0.0]Kirisakura 4.4.2 for Pixel 6/Pro aka "RAVIOLE"
Kirisakura-Kernel for the Pixel 6/Pro Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Google Pixel 6 Pro aka Raven and the Pixel 6 aka Oriole, together Raviole. I would appreciate if everybody that flashes the kernel...forum.xda-developers.com
For the command you already found:
can you please advise how to build it? · Issue #1 · freak07/Kirisakura_Raviole
I'm trying to learn about this new GKI and trying to build it within google env, but I guess that I'm doing it wrong since that compile fail (I'm running "BUILD_KERNEL=1 ./build_sl...github.com
The kernel is built in the environment just like the stock kernel.
the documentation doesn't tell you how to setup an environment, only how to copy the google one
Follow the documentation and you'll end up with the kernel build environment.
If you don't understand how everything works there, try to build a stock kernel first.
You found my kernel tree on GitHub already. Once you have a grasp how the environment works it shouldn't be a problem, to put everything where it needs to be.
The tweak i think you´re referring to is used for mmc devices.
There are no mmc devices used on the pixel 6 series, so applying the change will have no effect anyway.
You can check yourself under /dev/ on your phone following the documentation I linked.
Last edited:
why can't you just tell me the commands? i already know how to build a stock kernel, the instructions were in the link you sent
[Kernel][09.02.2023][Android 13.0.0]Kirisakura 4.4.2 for Pixel 6/Pro aka "RAVIOLE"
Kirisakura-Kernel for the Pixel 6/Pro Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Google Pixel 6 Pro aka Raven and the Pixel 6 aka Oriole, together Raviole. I would appreciate if everybody that flashes the kernel...
forum.xda-developers.com
I already told you the command.
The script is part of the build environment.
Last edited:
tell me, in your own words, exactly how you setup the build environment, from scratch[Kernel][09.02.2023][Android 13.0.0]Kirisakura 4.4.2 for Pixel 6/Pro aka "RAVIOLE"
Kirisakura-Kernel for the Pixel 6/Pro Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Google Pixel 6 Pro aka Raven and the Pixel 6 aka Oriole, together Raviole. I would appreciate if everybody that flashes the kernel...
I already told you the command.
The script is part of the build environment.
When I update the stock ROM monthly, I disable all Magisk modules, then uninstall Magisk (restore images) so that it's back to an unpatched boot.img prior to flashing the update.
There is a warning not to disable or uninstall the AK3 Helper module.
What should I do instead?
Flash the patched root image in the bootloader?
Will that restore me back to stock kernel?
Seeking to avoid bootloops and data wipes.
There is a warning not to disable or uninstall the AK3 Helper module.
What should I do instead?
Flash the patched root image in the bootloader?
Will that restore me back to stock kernel?
Seeking to avoid bootloops and data wipes.
https://source.android.com/docs/setup/build/building-kernels?hl=en#downloading here you go
In my own words...
mkdir android-kernel && cd android-kernel
repo init -u https://android.googlesource.com/kernel/manifest -b BRANCH
repo sync
i can't use repo because kirisakura kernel doesn't have a repo manifest file (default.xml)
I followed the directions and used the kernel flasher that was listed to "attempt" to flash this. Now it bounces to the fastboot mode after the google logo. How do I recover from this without wiping everything?
Top Liked Posts
-
1
What kernel manager?@Freak07 - Updated to latest Lineage (which i believe contains the latest March 23 update) on my Pixel 6:-
LineageOS Downloads
download.lineageos.org
But receive the following error when flashing (im flashing for the first time and currently have stock LineageOS Kernal installed which is pre rooted using Magisk 'delta':-
Kernel Flasher just exits when i attempt to begin flashing this Kernel -
32Update to Raviantha 1.0.0
Hey guys and girls,
So here´s the next release for stable March firmware, which is now QPR2 based. This results in quite a lot of changes and improvements in the vendor specific drivers!
Aside from that as already hinted at in the Pixel 7/Pro release for March google kind of unified the main kernel tree for the Pixel 6 and Pixel 7 series. That means I´m now able to compile the release for Pixel 6 and Pixel 7 from the same main kernel tree after some modifications to my own changes! This saves me a bit of time and means all not vendor/firmware/hardware specific improvements added to the kernel are now shared automatically, without me constantly merging them back and forth.
Hence the name change and starting from 1.0.0 again. Pixel 6 Oriole/Pixel 6 Pro Raven combined are Raviole, Pixel 7 Panther/Pixel 7 Pro Cheetah combined are Pantah, so Raviantha is the combination of both Raviole and Pantah.
Please note there are still separate zips due to the powerhal being different and the ramdisk in vendor_boot not being exactly identical.
As part of this development all improvements from the linked pixel 7 release found its way into this release plus a few more. So this time you guys are the first.
Short explanation follows below.
Please note that this release is not for the QPR Beta firmware, but the stable android 13 march firmware!
Please make sure to not use magisk canary 25210. It breaks module loading and causes a lot of issues! Please use either stable canary or canary 25206.
Latest platform tools have issues flashing super.img, please use platform tools 33.0.3!
Maple Tree / Per VMA-locks via Maple Tree in RCU-Mode
Updated this patchset to a new refined version that´s currently been tested.
Bit of a graph that shows app launch times with and without this patchset:
Link to the graph can be found here.
Explanation of the patchset in hide tags below!
Linux 6.1 finally merged the Maple Tree patchset. I had my eyes on that patchset for quite a while now. I backported it a few months ago (back in november iirc) but at that time I still ran into a few problems with it so it never made it into a release on XDA.
However after discovering work done on per vma-locks, which builds directly on the benefits that maple-tree provides interest was sparked again. Decided to pull it in again and fix the remaining issues.
If you´re interested in details read the linked topics.
Basically those patches reduce app launch time as well as lock contention. Additionally per vma-locks directly utilizes lazy-rcu, which was backported in 1.1.0. Usually I´m very hesitant when it comes to kernel changes actually translating to real world power consumption improvements, but lazy-rcu is one of the few patchsets that translate to a small improvement for everyone regardless of the usage.
So the new per VMA-lock patchset directly benefits from the previous backport of lazy-rcu.
Improve Uclamp
Improve uclamp patchset and detect capacity inversion. This greatly reduces the few missed frames we had.
Camera Launch Speed
Speed Up Camera launch by quite a bit. Also improve animations around camera compared to stock kernel.
There are other small improvements as well. Please check my github for those.
The kernel is made for stable A13 firmware, not beta.
I wish everyone a nice day.
Changelog:
- Linux-Stable bumped to 5.10.175 containing tons of stability and security fixes
- kernel is now built with latest clang 17.0.0 prebuilt from google
- Update Per VMA-locks patchset from previous release (this benefits greatly from lazy rcu!)
- improvements to MGLRU
- bump f2fs to latest f2f2 stable state
- improvements to the scheduler
- improvements to uclamp, prevent capacity inversion (reduce missed frames)
- greatly speed up camera launch time!
- ported improvements from QPR3 beta
- fixes/improvements to to memory management
- security fixes/ improvements from kernel/common
- optimize code around nr_cpus from latest linux
- other fixes please check github
- fixes/improvements to to memory management
- security fixes/ improvements from kernel/common
- other fixes please check github
Download:
Attached to release post as AFH is currently down.
Make sure to not delete and keep the powerhint ak3 module installed via Magisk Manager after flashing!
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing or simply dirty flash. Thank you.
Make sure to meet the requirements and read the OP as well as the FAQ before flashing.
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/freak077
thanks, I missed that before.
I can see the problem. Should be adressed in the next release.6
Custom roms are hit and miss, because some seem to do some weird stuff that´s deviating from the stock firmware. That's why there's no support from my side, as I simply don´t have the time to flash custom roms just to test that out. If there´s interest somebody else has to jump in and fix whatever issue is occurring. If the fix is simple enough and doesn´t impact compatability with the existing kernel.zip for the stock firmware I´m glad to accept any proposal or fix.
In this case it seems super partition has none or too less space left so it can be resized to flash vendor_dlkm on the fly while the device is booted.
You can try to repack the custom roms´s boot.img with the zImage found in my kernel.zip, flash the other images (dtbo and vendor_boot) manually in fastboot (vendor_dlkm in fastbootd, there super should get resized properly).
Afterwards you can try to flash the kernel.zip via app and see if the flash went through.
I think some others also shared steps previously, so if you want to search the thread, feel free to do so.
You can also ask the rom maintainer to look into it, but I can understand if they don´t like to add support for 3rd party kernels either.
correct, only stable stock firmware. no time and motivation from my side to support beta firmware.Hey @Freak07, great stuff as usual
Am I correct to assume that the QPR betas are not supported and we're on our own if we decide to use the kernel on them?4
not really
Were you using Youtube vanced and a corresponding magisk module? I suppose the hot reboot might kill the overlay somehow.
But as stated here, it’s not really kernel related so I guess we won’t be able to fix it anyway if its some firmware/framework related issue.
For losing the app, if it’s indeed vanced you’re using a logcat in that thread or on github might be the best way. -
119Kirisakura-Kernel for the Pixel 6/Pro
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Google Pixel 6 Pro aka Raven and the Pixel 6 aka Oriole, together Raviole.
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
The kernel aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security, stability and performance!
This includes Linux-Stable, F2FS-Stable and kernel/common!
If that got you curious, have a read about linux-stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
A big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Features:
Main Features:
- Based on latest A13 kernel sources from Google, Kernel is made for Android 13
- Linux-Stable-Upstream included to 5.10.170
- Compiled with prebuilt Google clang 17.0.0
- Backport entire RCU subsystem to Linux 6.0
- Lazy RCU which should result in power-savings while the device is lightly-loaded or idling, more information here
- Backport Maple tree from Linux 6.1
- Per VMA-locks in conjunction with Maple Tree RCU-Mode (improve app launch time, this feature in general benefits greatly from lazy rcu!)
- FHD Support for Pixel 6 Pro (display is able to run at 1080p), more info here and here
- merged kernel/common (improvements to android-common-kernel straight from google)
- MM subsystem reworked (more info and some patchsets linked in this post)
- Multi-gen LRU backported/reworked and enabled (more info here, here as well and here) to improve mm and reduce cpu cycles, latest V15 state
- improvements to uclamp, prevent capacity inversion (reduce missed frames)
- greatly speed up camera launch time!
- Utilize an additional kswapd thread to increase throughput for memory reclaim
- pelt multiplier tied into powerhal to speed up scheduler during interaction (more info here)
- prevent frequency spikes caused by small transient tasks when the device is idle(more info here)
- tie mechanism to prevent frequency spikes caused by small tasks also into powerhal
- scheduler improvements for RT (realtime) tasks
- introduce and setup PMU limiter (prevents CPU from spiking to max when it isn´t needed, based on PMU reads, more information here)
- improve camera performance by tuning the powerhal during recording
- bias tasks of rt, sf and ta groups to prefer high capacity cpus during app launches, interactions
- improve app launches via powerhal
- improve trusty driver performance which connects to fingerprintscanner-hal by using high perf wq during fp unlock
- restrict maximum CPU-Freqs during screen off/ idle to 1.1GHZ for all clusters to save power
- introduce unfair f2fs rwsems to prevent writer starvation and improve IO perf under heavy load
- fuse: give wakeup hints to scheduler to speed up compress/decompress in internal storage (details)
- enable RCU_BOOST (details here), also fix RCU_BOOST behaviour
- F2FS-Stable updated
- merge and enable f2fs block_age-based extent cache (improve the accuracy for data temperature classification, reduce the garbage collection overhead after long-term data updates)
- TCP backports from mainline
- SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
- Scheduler updates from linux-main
- use improved energy model for exynos cpu cooling/thermal control
- allow GPU to scale down to 150mhz, but boost to higher value in case of interaction via powerhal
- affine IRQS to CPU 7 during camera usage for improved performance as it tends to overload the little cores
- use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
- include bbrv2 from google, more info here
- Enable support for TTL spoofing
- Include LRNG, see here and here for more info, bump to v45 with 3.0.0
- important patches from kernel/common for 5.10 (here are more details)
- CleanSlate Features from @tbalden, big applause here! (s2s, notification booster, battery saver, flashlight notifications. Please note: cleanslate features that work otherwise with rooted devices like kadaway (adblocking) are not implemented on this kernel since I´m running rooted)
- dirty pipe exploit fixed
- supports direct usb access for hi-res playback over USB-C DACs
- improve ZRAM usage
- flashing the kernel will preserve root
Various Optimizations:
- update several drivers to use power efficient workingqueues (for example wlan driver)
- kernfs: use buffer from the stack space
- printk: use buffer from the stack space
- kthread: use buffer from the stack space
- bpf: avoid dynamic memory allocation for small value buffers
- binder: Reserve caches for small, high-frequency memory allocations
- kernfs: use kmem_cache pool for struct kernfs_open_node/file
- cgroup: use kmem_cache pool for struct cgrp_cset_link
- f2fs: reduce timeout for uncongestion
- f2fs: Demote GC thread to idle scheduler class
- f2fs: set ioprio of GC kthread to idle
- mm: vmstat: use power efficient workingqueues
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
AK3 Helper Module:
- restrict little cluster to 1,19ghz mid cluster to 1,19ghz and big cluster to 1,1ghz during screen off, to reduce battery usage for example during music playback
- only use little cores during screen off/device suspend
- tie pelt multiplier into the powerhal (more info here)
- prevent frequency spikes caused by small transient tasks during idle operation (more info here)
- boost scheduler using the pelt multiplier during fingerprint unlock operation
- setup and control PMU limiter via powerhal (more info here)
- dynamically adjust target load for memory interface during interaction
- boost memory interface controller during interaction (decreased missed frames, improved soc efficiency according to google docs)
DOWNLOAD:
Download is always located in this folder:
4.2.0, 4.3.0, 4.4.0, 4.4.1, 4.4.2 are attached to the release posts linked below as AFH is wonky at the moment.
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...www.androidfilehost.com
Changelog:
Android 12.0.0
1.0.0 Initial Release
1.0.2 https://forum.xda-developers.com/t/...r-pixel-6-pro-aka-raven.4358435/post-85910621
1.0.5 https://forum.xda-developers.com/t/...r-pixel-6-pro-aka-raven.4358435/post-85924419
1.3.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-85976139
1.4.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86109665
1.5.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86259863
1.7.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86390563
1.8.4 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86541727
Android 12.1.0 Stable (March feature drop and more recent)
2.0.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86617873
2.0.1 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86637233
2.1.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86695911
2.3.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86821331
2.4.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86834981
Android 12.1.0 Stable (June feature drop and more recent)
3.0.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86992705
3.0.1 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86996237
3.0.17 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87127695
Android 13.0.0 Stable (not QPR beta!)
4.1.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87290247
4.1.6 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87399635
4.2.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87524609
4.3.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87697425
4.4.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87823333
4.4.1 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87944879
4.4.2 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-88118201
Raviantha 1.0.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-88316223
Android 12L QPR Beta - Deprecated
Build for Android 12 QPR Beta: https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86857033
Requirements
- the kernel is made for the stock firmware provided by Google, pay attention to flash a kernel release matching the firmware (flashing on custom roms might work, but you may need workarounds!)
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment so you can flash back to stock in case something goes wrong
- working magisk environment (a device rooted with latest magisk stable in case you want to be absolutely safe)
- IMPORTANT: Unrelated to the kernel, but update both slots of your phone to A13! (take a look here)
How to flash the Kernel:
1a. Make sure you tick all the requirements above
1. Download the correct kernel.zip depending on your device (Pixel 6 = oriole || Pixel 6 Pro = raven)
2. Flash the correct kernel.zip via EXKM, FKM or kernel flasher. Root will be preserved. The AK3 magisk helper module will be automatically installed during flashing the kernel.zip and be present on next reboot.
Do not remove or disable the AK3 Magisk Helper Module otherwise the device will bootloop.
3. Reboot and profit.
Manual installation is no longer supported starting with release 3.0.0, as there´s a free open-source option to flash kernel.zips now.
Instead use the free kernel flasher, which can be found here.
Manual installation without relying on paid apps like fkm/exkm:
Please have a look at the linked post.
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea/beer
If you like my work: http://paypal.me/freak07
Credits:
@osm0sis for all his work on AK3.
@tbalden for being the best HTC, Pixel, OnePlus and Asus wingman!
@capntrips for all his work on the pixel 6!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help and advices!
@topjohnwu for magisk and his entire work!
Source Code: https://github.com/freak0744Update 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:
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:
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...
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/freak0743Update to 4.2.0
Hey guys and girls,
I hope everyone started well in the new week. Here´s the next release and it´s a rather big one with lots of under the hood improvements.
We already had all the changes in from the October security patch release released, due to merging linux-stable stable and kernel/common in advance.
The kernel is now at 5.10.146 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. Additionally to that the security patches are about 3 months behind the discovery of those vulnerabilities.
Amongst linux-stable upstream there are a few other not minor updates in this kernel.
Clang
The kernel is now compiled with the latest prebuilt Clang from Google. This was quite a journey as this is a pretty big update to clang. This is quite experimental to be on googles side of a "bleeding" edge compiler, but after fixing several issues that originated from the new compiler it ran stable for over 2 weeks.
There´s a potential for CFI failures that originates from that new Clang rather than a "real attack", due to the changes in clang.
Short reminder what CFI actually does: Control flow integrity (CFI) is a security mechanism that disallows changes to the original control flow graph of a compiled binary, making it significantly harder to perform such attacks.
A typical crash (that´s not wanted and originates from compiler changes rather than an actual attack, which is already resolved of course ) would look like the following: Open camera app, due to compiler changes CFI is accidentally tripped every time this code is executed.
I think we catched all of these newly CFI failures and everything is nice and stable. In case you discover such a behaviour please send me the contents of sys/fs/pstore, once the phone booted back up.
There´s always the possibility of a "real" attack in which CFI will crash the phone, before the attacker can compromise the phone. That´s why keeping subsystems updated is important.
Powerhal
The powerhal was retuned due to changes to the scheduler introduced. It should work even better now, regarding efficiency and performance. Of course I try to tune it also to my personal needs, while trying to keep it working for all workloads. The changes are not drastic, so please don´t post after several hours you see drastic differences.
Other improvements
Several other improvements from kernel/common (for higher branches than 5.10) and linux-main were backported to this branch so we can benefit from those improvements. For details please check my git.
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.146
- kernel is compiled with latest prebuilt google clang 15.0.2
- improvements from linux-mainline
- locking subsystem
- memory management
- more details please check github
- updates from kernel/common to several subsystems
- tweak powerhal for improved performance/efficiency
Download:
Attached to release post as AFH is currently down.
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...
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/freak0737Update to 1.8.4
Hey guys and girls,
So here´s the next update. It´s kind of an off schedule update, as I planned to update the kernel with the next security update/feature drop.
But in the light of recent events regarding the new exploit called "Dirty Pipe" (more info here), which is similar to the "Dirty Cow" exploit from a while ago, but easier to exploit this time, I decided to release an update ahead of schedule.
This exploit was fixed in linux-stable 5.10.102, as opposed to a single commit in AKC (android kernel common, commit here). This shows once more why merging linux-stable is beneficial as explained in detail in the OP.
Since one of the key aspects of this kernel is security and staying on par with upstream (which often fixes exploits way ahead of android security bulletin updates, even before an exploit is even known or fixed via a patch on the security bulletin) I decided to release this update as quickly as possible, so this exploit is fixed on devices running this kernel.
Several other notable improvements and changes in this release:
Bring in scheduler updates from Android 13 Developer Preview, which aim at improving task placement. (adjust powerhal accordingly)
BFQ IO-Sched is now on par with linux-mainline.
Several fixes to mm subsystem, f2fs and others.
Several other improvements are included as well. More details in the changelog.
Download is below.
Updated instructions in the OP!
Changelog:
- linux-stable 5.10.103
- contains fix for the dirty pipe exploit
- built with clang 14.0.2 prebuilt by google
- improvments from kernel/common
- fix memory leaks
- security related patches
- mm improvments
- f2fs fixes
- scheduler fixes
- for details please check github
- built with improvements from A13 Dev Preview to display driver
- other changes please look at my 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...
Instructions can be found in the OP! Please follow the instructions to avoid any issues.
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.37Update to 1.7.0
Hey guys and girls,
So here´s the next update. It includes the february security update. Most of the changes brought by the February kernel source drop, were already included in this kernel by merging kernel/common and linux-stable.
Several other notable improvements and changes in this release:
Improve f2fs performance by merging a patchset to prevent writer starvation for the checkpoint thread. This was discussed this month in the f2fs mailing list and is already merged to the kernel/common tree. It´ll improve performance under heavy I/O utilization.
You can find more information following the discussion here.
Necessary backports were brought to the kernel and the platform specific f2fs-implementation was also adjusted.
Latest f2fs-stable was also merged to the kernel.
Update the patchset to prevent frequency spikes caused by small tasks as well. Tie those new changes into the powerhal. (That means users not flashing the kernel.zip, but instead use the manual installation method, which are only a handful from the download count, need to flash the updated magisk helper module. Users that flash the kernel.zip via FKM/EXKM have to just flash and forget)
Several other improvements are included as well. More details in the changelog.
Download is below.
Updated instructions in the OP!
Changelog:
- February Security update merged
- linux-stable 5.10.96
- include latest f2fs-stable
- improvments from kernel/common
- fix memory leaks
- security related patches
- mm improvments
- for details please check github
- introduce unfair f2fs rwsems to prevent writer starvation and improve IO perf
- update patchset to prevent freq spikes caused by small transient tasks (also tie this into powerhal)
- give pelt multiplier power hint for scheduler performance boost during fingerprint unlock
- fuse: give wakeup hints to scheduler to speed up compress/decompress in internal storage (details)
- enable RCU_BOOST (details here), also fix RCU_BOOST behaviour
- update LRNG implementation (thanks to arter97 )
- improvements/fixes for CleanSlate features
- other changes please look at my 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...
Instructions can be found in the OP! Please follow the instructions to avoid any issues.
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.
