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

Search This thread

Admiral2145

Senior Member
Sep 28, 2010
2,097
379
Xiaomi Poco F3
Google Pixel 6
I have a weird issue... I can root and flash both slots however, when I try to flash the kernel on slot b it locks/bootloops however, on slot a I can flash kernel and have no issue... Has anyone have this happen or know what's wrong on my slot b to cause this?
 

roirraW "edor" ehT

Forum Moderator
Staff member
I have a weird issue... I can root and flash both slots however, when I try to flash the kernel on slot b it locks/bootloops however, on slot a I can flash kernel and have no issue... Has anyone have this happen or know what's wrong on my slot b to cause this?
We'd have to know what you do have on Slot B right now. If you start fresh on Slot B with a factory image with no wipe (so remove -w), then flash this kernel, then what happens? I've definitely shifted from slot to slot (manually) over the past year with no issue while using this kernel, so regardless it's probably not a problem related to this kernel.
 
  • Like
Reactions: Admiral2145

Admiral2145

Senior Member
Sep 28, 2010
2,097
379
Xiaomi Poco F3
Google Pixel 6
We'd have to know what you do have on Slot B right now. If you start fresh on Slot B with a factory image with no wipe (so remove -w), then flash this kernel, then what happens? I've definitely shifted from slot to slot (manually) over the past year with no issue while using this kernel, so regardless it's probably not a problem related to this kernel.
I'll try that... Flash fresh A13 Sept (slot b) and see how it goes
 
  • Like
Reactions: roirraW "edor" ehT

exile1ck

Senior Member
Dec 8, 2018
64
8
Just wanna ask what does everyone's idle battery drain looks like? Just woke up and noticed my average was -475mA(-1.9%/hr). Can anyone confirm this is normal?
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,017
20,732
Just wanna ask what does everyone's idle battery drain looks like? Just woke up and noticed my average was -475mA(-1.9%/hr). Can anyone confirm this is normal?
Nobody can tell you without more information, because nobody uses their phone like you do.

For context:
I'm losing about 2-3% over 7-8 hours overnight, while i don't touch my phone. So 0.3-0-4%/h.

If I'm listing to music during the day with screen off my idle drain is about 2-3%/h.

Generally comparing battery stats is difficult as usage per day varies a lot for most of us and everyone's usage is different.
Try to compare your own results to get an overview.
 

NCVol

Member
Jul 15, 2022
19
11
My Play System update is stuck on July. It will try to update but on reboot I'm still on the same one. I was told to check if it's the kennel. Is there any chance the kernel is part of that issue?
 
  • Haha
Reactions: Mrcactuseater

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,017
20,732
@Freak07 are there any settings in the kernel that change the behaviour for going into deep idle (not deep sleep)?

Also, can you maybe check and share how much your device is usually in deep idle during the last 24h?
What is deep idle you're referring to and how do you check this on your end? I'm not sure I understand. :)
 
  • Like
Reactions: roirraW "edor" ehT
What is deep idle you're referring to and how do you check this on your end? I'm not sure I understand. :)

Okay I am happy that I am not the only one not fully understanding it lol.

Using the app Temefi:

Then inside the app:
Currently Running>Doze>Doze Cycle graph>*

The green bar shows how much the device is in deep idle. According to the app author deep sleep is just a CPU state but deep idle is what we want the device to be/to go for battery savings.

There are different doze profiles one can load from within that app. Those will change setting into more aggressive deep idle settings.

Edit:
To see current doze settings:
Currently Running>Doze>DumpsysDevice Idle History


To load more aggressive doze profile:
Currently Running>Doze>Set or compare doze profile
 
  • Like
Reactions: Freak07

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,017
20,732
Okay I am happy that I am not the only one not fully understanding it lol.

Using the app Temefi:

Then inside the app:
Currently Running>Doze>Doze Cycle graph>*

The green bar shows how much the device is in deep idle. According to the app author deep sleep is just a CPU state but deep idle is what we want the device to be/to go for battery savings.

There are different doze profiles one can load from within that app. Those will change setting into more aggressive deep idle settings.

Edit:
To see current doze settings:
Currently Running>Doze>DumpsysDevice Idle History


To load more aggressive doze profile:
Currently Running>Doze>Set or compare doze profile
I suspected you were talking about doze. That's unrelated to the kernel.

Here's a bit of information:

From that documentation: "If a user leaves a device unplugged and stationary for a period of time, with the screen off, the device enters Doze mode."
I know there are more conditions to it, but usually tweaking things like this ends in a lot of trouble.
There's a reason why the device enters the so called deep idle/doze only after a while if completely left alone. You won't receive notifications during that time.
I know it sounds tempting to play with this to make it kick in more aggressively, but usually it does more harm than good.

I'm not screwing around with doze or making it more aggressive, because I like to get my notifications during the day. :)
 
I suspected you were talking about doze. That's unrelated to the kernel.

Here's a bit of information:

From that documentation: "If a user leaves a device unplugged and stationary for a period of time, with the screen off, the device enters Doze mode."
I know there are more conditions to it, but usually tweaking things like this ends in a lot of trouble.
There's a reason why the device enters the so called deep idle/doze only after a while if completely left alone. You won't receive notifications during that time.
I know it sounds tempting to play with this to make it kick in more aggressively, but usually it does more harm than good.

I'm not screwing around with doze or making it more aggressive, because I like to get my notifications during the day. :)

Ah okay... I was already suspecting that deep idle (or deep doze or whatever) is causing troubles such as no notifications. I was just worried because my phone pretty much never enters that state. But I guess that is fine then.
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,017
20,732
Ah okay... I was already suspecting that deep idle (or deep doze or whatever) is causing troubles such as no notifications. I was just worried because my phone pretty much never enters that state. But I guess that is fine then.
It should enter that state during the night while you leave the phone stationary without touching it.
But if you use your phone regularly during the day/carry it in your pocket, that's expected.

But it gets a bit off topic now :)
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,017
20,732
Is this kernel okay on the qpr beta? I searched the thread and didn't see anything
No, it's for A13 stable.

 

ChongoDroid

Senior Member
Jul 29, 2010
6,292
2,959
Vancouver
Google Pixel 4
Google Pixel 4 XL
No, it's for A13 stable.

Gotcha I was wondering if it'd work on 13 beta but maybe there's kernel differences
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,017
20,732
what are the commands you used to build the kernel? i can't figure it out
Check here:


For the command you already found:
 
  • Like
Reactions: roirraW "edor" ehT

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Fantastic Work Sir! @Freak07 I do believe you've supplied every pixel and even the OP7TProNR McLaren I recently owned. I ditched Google for another year+ because my OGP1 Marlin suffered hardware failure and then my 4XL splder to lifted from battery plug and scattered solder like missiles lol.

    ANYWAYS For anyone On the January Bliss 6.3 from yet another fine Dev who I completely ignore at times (sorry doode) @stebomurkn420 . This kernel will not flash as OP states. However instead of using the Bliss January ASB boot.img use the TQ1A.230105.001.A2 boot.img patched with Magisk. You can then flash this Mona-Lisa-Linux kernel and keep root.

    That is all. GoodDay & Happy 2023! 🌿〽️🥳🍷🌿🍺🎊 🌿🚬😎
    🚬🪬
    5
    Off topic: pixel 6 here, i installed a gms doze magisk modules & uninstalled it, sometimes i receive notifications as a bulk at once when i switch from mobile data to wifi & vice versa, now on since yesterday im only receiving whatsapp notifications, i dirty flashed jan. Firmware image but nothing changed, cleared gms & google apps data but also nothing (sometimes after clearing google app data notifications arrive then stops again)

    Im sorry i know its off topic but if anyone have any tip on how to fix this, thanks
    If you know this is completely off topic why not open a new thread with a question tag and just describe your problem there?
    Or post in the XDA thread of that module. Maybe it's something that happens regularly.
    I'm pretty sure if somebody is aware of that problem, you'll find better help there.
    (I don't have any suggestion on how to help you other than staying away from all mods that alter background behaviour, doze behaviour, notification, etc etc. as problems like this are usually what's going to occur.)


    This just clutters up the thread here and may confuse (inexperienced) users reading or searching through the thread. This thread is really not the place to start a discussion about that topic.
    Thanks for your understanding!
    4
    Installed & uninstalled the modules & still no notifications, ran (dumpsys deviceidle disable) still also no notifications

    umm, youve been warned twice now to please post in the applicable thread. I even tried to give you a direct link to where that would be along with some troubleshooting steps (the one you quoted wasnt even the one related to what you reported, you only needed to read a bit further down), and even an alternative, not to mention the direct warning that even with the best Doze module some people will still have issues....if youre still having issues, backup (something like Migrate (v4) and the way ive used it forever might help shorten the procedure)) and factory reset, and restore, problem solved, plenty of people before you (me included) have had to do it...you'll often spend more time trying to find some obscure workaround than you will fixing it the 100% way...i dont like to enable this behaviour, so this will be the last reply from me on the subject, here or elsewhere...

    Please take another friendly hint....and dont post OT here again :)
    2
    Is it possible to force enable DP Alt Mode using this for the Pixel 6 Pro? Trying to find a way to achieve this, this seems like the most promising thing so far.

    Update: Read through the thread, someone asked this before, for those googling: No, this doesn't fix DP Alt Mode as apparently there are hard links to display firmware and other BS (thanks Google). Damn.
    2
    Is there any way to manually flash? I want to try it on latest beta cause I want full magisk. Rn I'm with p7 boot workaround for root. So I have root and magisk modules enabled for the already installed apps that need root but since magisk can't recognize root can't give root permission to new apps or flash modules. The thing is that I can't install this kernel as well since I can't grant root to kernel flashers. Funny thing I uninstalled kernel flashers done days ago cause I hadn't use it for long and it already had root.... Any way to flash this kernel? I don't even know if it will boot. Thanks
    the kernel is made for stable firmware, not qpr betas.

    manual process won´t work for the current kernel releases. flashing the kernel won´t work properly without being rooted as described in the requirements in the OP.
  • 118
    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, 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.161
    - Compiled with prebuilt Google clang 16.0.2
    - 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
    - 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
    - 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
    - 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
    - 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

    DOWNLOAD:
    Download is always located in this folder:
    4.2.0, 4.3.0 and 4.4.0 are attached to the release posts linked below as AFH is wonky at the moment.


    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



    Android 12L QPR Beta - Deprecated

    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/freak07
    44
    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:
    Screenshot_20220816-083147.png
    Screenshot_20220816-083204.png

    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:


    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
    43
    Update 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
    - patches to f2fs
    - 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.



    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
    37
    Update 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:


    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.
    37
    Update 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:


    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.