Development [Kernel][07.05.2022][Android 12] Kirisakura 2.0.0_S for Asus Zenfone 8 aka "Sake"

Search This thread

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,537
18,352
Thanks man! :)
Could you please let us know if defconfig is stable or it's better to configure something (like cpu/gpu freq's) on the device ?
Does it support both 8GB and 16GB RAM devices?
Just flash the kernel and reboot like described in the instructions :) no need to change anything, all setting are applied during bootup. (y)

Except for installing @tbalden's CleanSlate config and companion apps to control those excellent features as they are included in my kernel too.
If you're interested I'd recommend to check out the CleanSlate thread for details :)
 
  • Like
Reactions: Sam6536

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,537
18,352
Thanks for reply! :)

Do you have plans to release Permissive version of your kernel?
why would you want to do that, just curious?
if there´s need, you can patch sepolicy with magisk during bootup to allow specific things, instead of making the device completely selinux permissive.
look in the magisk documentation for more info.


Alternatively you can use terminal or a script to set the kernel permissive.

su

setenforce 0

there might be also magisk modules to set the kernel permissive, although not really recommended.
 

dron39

Senior Member
Sep 20, 2009
710
108
Idk at the moment. )
Just used it on previous Samsung (Note 20 Ultra) to have some Viper and other things which could not be possible if kernel is Enforced.
Please also check pm when you have time.
 

dron39

Senior Member
Sep 20, 2009
710
108
Thanks, I saw it already but no full firmware zip and no source code has been uploaded yet. Probably beginning of next week (y)

  1. Optimized system stability
  2. Improved power consumption
  3. Improved thermal for some 3rd party APP video call of rear camera.
  4. Improved the image quality of ASUS Camera, Instagram and Snapchat
  5. Updated Android security patch to 2021-07-05
Waiting promptly for your update :)))
 

dron39

Senior Member
Sep 20, 2009
710
108
I thnik not only me would also like to see instructions more detailed in FAQ. Especially about how to revert to stock kernel, could you please share fastboot partitions or complete command to where we need to flash stock 3 files.
Thank you in advance! :)
Just for people who came from other brands (like Samsung) where other software like Odin did all the things for users automatically. =)
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,537
18,352
thanks :)

And sourcecode:

I have some problems with openng zip with WinRar (corrupted archive), but with 7-zip it looks like it's OK.
Looks like this one is broken (maybe) kernel\msm-5.4\drivers\md\dm-linear.c
So please check it.
it´s not fully uploaded yet. or the upload was faulty.
usual size is around 600mb, this is just 245mb, so broken for now.

I thnik not only me would also like to see instructions more detailed in FAQ. Especially about how to revert to stock kernel, could you please share fastboot partitions or complete command to where we need to flash stock 3 files.
Thank you in advance! :)
Just for people who came from other brands (like Samsung) where other software like Odin did all the things for users automatically. =)
use any tool which can extract payloads ( example, but there are plenty more when googling ) to get the 3 imgs mentioned in the FAQ from the full firmware zip.

then connect your phone via fastboot and flash the 3 imgs.

fastboot flash dtbo dtbo.img
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img


alternatively flash the magisk_patched boot.img to stay rooted during this process.
 
  • Like
Reactions: dron39

dron39

Senior Member
Sep 20, 2009
710
108
alternatively flash the magisk_patched boot.img to stay rooted during this process.
So if I understand you correctly, it is enough to flash magisk_patched boot.img if I want to root std kernel. And If I want to go back to stock kernel from your or CleanSlate I need to flash these three dtbo, boot, vendor_boot. And if I ant to preserve root then dtbo, magisk_patched boot, vendor_boot.
Correct?
Sorry if too many questions here and in pm. :)
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,537
18,352
So if I understand you correctly, it is enough to flash magisk_patched boot.img if I want to root std kernel. And If I want to go back to stock kernel from your or CleanSlate I need to flash these three dtbo, boot, vendor_boot. And if I ant to preserve root then dtbo, magisk_patched boot, vendor_boot.
Correct?
Sorry if too many questions here and in pm. :)
correct, magisk_patched boot.img is enough to root on stock firmware.

I think for cleanslate kernel, dtbo and vendor_boot might not be needed (as cleanslate doesn´t change anything there, it´s closer to stock), but you´re on the safe side if you just flash all three all the time.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Update to 2.0.0

    Hey guys and girls,


    Alright so here´s the next update. Big bump to 2.0.0.
    It´s based on firmware 31.1010.0410.61.

    As already mentioned .43 updated bumped the CAF-Base the kernel is based on. That is on one hand nice to see and a novelty this year for me on the other hand it means a lot more work for me since the source from Asus is pushed without git history. That means it´s impossible to merge an update like this to my existing kernel as there are just to many conflicts to fix manually. While starting from scratch takes also a lot of time, it takes less time than manually trying to fix all the conflicts.
    Usually I only had to do that for major android updates (going from A11 to A12) as that was the only occasion OEMs would start to base the kernel on a more recent QCOM base.

    Anyway here´s the update for the latest firmware, all previous features should remain intact.
    Updated in the changelog below.

    The link to the latest firmware can be found following this link.


    More changes in the Changelog below:


    Changelog:
    - Rebase entire kernel on 31.1010.0410.61
    - Linux-Stable upstream bumped to 5.4.191
    - use prebuilt clang 14.0.7
    - CAF-Upstream to latest
    - MGLRU added (info here and here)
    - update f2fs fsck spoof
    - update ak3 zip
    - other improvements and tweaks please check github


    Download:



    Instructions can be found in the OP!
    But look at this post too :)

    Have fun, enjoy the kernel and your phone.

    Donations are not mandatory but very welcome.
    If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
    3
    Yes, already downloaded the newer one.
    One question: I've noticed that, after flashing it through FKM and rebooting, the ak3 module doesn't appear in magisk. Is this a problem?
    Figured so, flashed it too without issue so far.
    Just like @Rokcy98, no new magisk module installed. Flashed it with EXKM, so that might be the reason ?
    my bad, there´s no ak3 module on A12 needed yet :)

    copy paste error, thanks for catching!
    2
    Thanks for this kernel. I am running 31.1010.0410.61 and I just installed the 2.0.0 version of the kernel.

    I guess I need to use it for a while to see if it really makes a difference in battery life/performance. I do like the inclusion of Wireguard into the kernel, that's nice.

    Anyway, using Accubattery I think the phone is in deep sleep less than it was on the stock kernel. Is this something I need to configure in FKM or something? Is this not an issue at all? Maybe it is in deep sleep and I just need to stop checking it so often?

    Maybe I need to just leave the phone be and use the kernel for more than a day and see what it does.
    It´s not something you need to configure in FKM. The kernel allows the phone to go to deepsleep if nothing requests the phone to be awake, for example, apps, services or wifi etc.
    If something requests a wakelock to do whatever needs to be done to receive a notification the kernel will allow the phone to quickly leave deepsleep and re-enter it.
    If an app abuses this, deepsleep might get worse.

    A big portion of this is controlled by framework now outside the kernel. Asus uses something of their own additionally called background app management acccessible via battery section in settings.
    Alternatively you can control even more background behaviour in app info settings of each respective app. There´s something else called doze at play, which puts the phone to a "deeper" deepsleep state if no motion etc is detected for some time (e.g. overnight). If you constantly check the phone, this mode is likely never be entered.
    1
    Hi there, kinda new ZF owner. Any chance 2.0.0 version might work with latest 0410.61 version or isn't it worth even testing ?

    Edit: posted this kinda... exactly at the same time as OP confirming the release compatibility. Disregard my comment, and thanks :)
  • 20
    Kirisakura-Kernel for the Asus Zenfone 8

    Hello everyone,

    To keep it short: Here is Kirisakura - Kernel for the Asus Zenfone 8 aka Sake. The Zenfone line-up internal codenames are traditionally derived from alcoholic drinks. Two years ago the Zenfone 6 bore the title "Kirin". The Zenfone 7 was codenamed "Tequila".
    I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.

    Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
    If you expect a custom kernel to magically improve your devices battery life manifold and this is your only priority then this might not be the right place for you.
    However the kernel is built to keep battery life close to the same as you would experience the on stock kernel while being tuned to perform better in various UI related benchmarks. The same benches are used by google to verify and ensure UI smoothness on the Pixel devices. The scheduler is tuned to yield lower jitter and reduce jank frames.
    If that got your curious, I welcome you to continue reading if you´re still interested!


    This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.


    A very positive development. Google pushed for CFI and SCS to be enabled by default in the android-common kernel. In this years generation ( 5.4 linux kernel base/ SD 888 ) CFI and SCS are enabled by default. It was a lot of work to get these features working nicely on the kernel I did the years back. So it´s nice to see this is now there by default in everybody can profit from it.
    I put the explanations and links in hide tags here.

    Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features.
    The recently released Kirisakura-Kernel for the OnePlus 8 Pro was featured on the XDA-Portal due to the inclusion of CFI. The featured article explains CFI in great details, is easy to understand and definitely worth to read.
    If possible the latest Kirisakura-Kernel releases for various devices aim to include CFI in enforcing mode so users can benefit from this security features.

    Another security feature is Shadow Call Stack (SCS).
    SCS is another security patchset that is aimed at preventing attacks via return oriented programming (ROP).
    ROP is a technique where the attacker gains control of the kernel stack to overwrite function return addresses and redirect execution to carefully selected parts of existing kernel code.
    If you´re interested here are a few good links:
    Google Security Blog explaining SCS.
    LLVM doc about SCS
    Android DOCs documenting SCS

    If reading about upstream in the paragraph above 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.
    Read more about the Release-Model following this link.
    This conversation on the LKML mailing list also shows the power of Linux-Stable and why it´s very beneficial to not just say it´s not worth and a potentiol source for bugs:
    Starting with the Initial Message , the following reply and a good summarizing statement.



    Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 888 that´s built into the different SKUs of the Zenfone 8.
    The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
    The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
    This kernel focuses amongst the other features to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.

    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!


    Main Features:
    - Based on latest kernel sources from Asus for Android 12 and intended to be used on the latest Asus Stock-Firmware
    - compiled with Clang 14.0.7 and built with -O3 speed optimizations
    - Linux-Stable-Upstream included to 5.4.191
    - upstreamed CAF base for the Snapdragon 888 (qcoms internal codename "lahaina")
    - include important fixes/improvements from kernel/common
    - tune scheduler for improved jitter and less jank frames
    - reduce power consumption during deep sleep
    - remove logging while device is suspended
    - remove sleep debugging from Asus for release build
    - disable various debugging mechanisms for drivers which are not needed on a perf build (for example touchscreen, fingerprint reader, display, binder)
    - disable various debugging configs, that are not needed in a perf kernel build according to google.
    - disable selinux auditing (we don´t have to adress selinux denials running a stock rom)
    - display tweaks to reduce power consumption on statically rendered images
    - disable unnecessary CPU errata for our specific SoC
    - disable per cgroup pressure tracking to reduce overhead
    - free up RAM by removing reserved mem regions used only for debugging
    - implement LRNG (thanks @arter97, see arter kernel OP for more info )
    - Flashing the kernel will keep root!
    - Flashable via EXKM, FKM or TWRP (if available) on a rooted system!
    - Anykernel zip is based on the Anykernel3 release from @osm0sis


    EAS related features:
    - Implement dynamic WALT-Window size depending on current FPS, collecting information about CPU-Load to provide more precise information for the scheduler
    - EAS implementation patched up to latest CAF state
    - updates from kernel/common
    - scheduler updates from sd888/ 5.4 kernel
    - scheduler update from sony xperia 1 III kernel aiming to improve WALT

    CPU related features:
    - Power saving workingqueues enabled by default (toggleable in EXKM)
    - Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to use power efficient workingqueues. This compliments EAS in general
    - improvements to cpufreq/times/stats
    - vdso32 patches as found on Google Pixel devices (brief documentation here) (CAF 5.4 default, keep for documentation)
    - remove event debug logging
    - disable broken irq detection, disable debugmon
    - improve suspend/resume from audio driver (caf-upstream for audio-kernel)
    - cpuidle: wake only cpus for which qos has changed (this allows cores to keep idle states better)
    - disable debugging during sleep states as per qcom recommendation
    - remove RTB logging to reduce overhead
    - disable trace_printk as it shouldn´t be used on production/perf kernel builds
    - enable suspend_skip_sync to save power during suspend/resume
    - disable edac and coresight (following google on the pixel kernels)
    - disable jtagv8 debugging as recommended by qcom for perf builds to avoid potential power, performance and memory penalty
    - disable s2idle in favor of deep idle state -> improves deep sleep drain (google initially used 2idle for improved suspend/resume latency on pixel 3 and pixel 4, but disabled it on pixel 5. qcom followed suit for sd 888, but apparently didn´t see google reverting it on pixel 5. Other OEMs such as Xiaomi or OnePlus already disabled s2idle on their SD888 devices in favor of deep- read more about s2idle vs deep here)

    GPU related features:
    - GPU driver updated to latest CAF-State
    - gpu/kgsl improvements from pixel 4/pixel 5 kernel
    - add low_prio_worker thread for gpu driver (Improves performance when tearing down processes (eg, via LMK) and not blocking currently running UI from submitting work to the GPU

    File System related features:
    - upstream BFQ-MQ to latest state in linux-mainline and default to 128KB readahead
    - improve memory allocations in kernfs
    - ufs improvements from pixel 4/ pixel 5 kernel
    - improve GC as to not interfere while user interaction is happening and prevent possible jitter or latency spikes

    UI/UX/Usability related features from CleanSlate:
    - CleanSlate features made by @tbalden
    - Disclaimer: All CleanSlate features can be controlled via the free companion and config app found on CleanSlate thread here on the Zenfone 8 Forums on XDA. Please consider buying the premium versions if you enjoy using the CleanSlate features, to give a little something back to @tbalden.

    Network related features:
    - Wireguard Support (Details)
    - advanced TCP algorithms enabled
    - use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
    - includes new bbr
    - improved networking drivers from caf-upstream (especially wifi)
    - remove unnecessary wakelock from WLAN driver to reduce thousands of very short wakeups during a 7 hour deep sleep period
    - improved bluetooth performance (¹, ²)
    - Enable support for TTL spoofing

    Memory related features:
    - Speculative Page Faults left enabled (1. 2) (CAF 5.4 default, keep for documentation)
    - Fix various memory leaks in different subsystems
    - improved mm with patches from mainline
    - patches from kernel/common
    - improve memory allocations in various subsystems, video encode/decode, kernfs, cgroup
    - Backport to enable CONFIG_HAVE_MOVE_PMD (see here) , thanks @arter97
    - Backport to enable CONFIG_HAVE_MOVE_PUD (commit here) , thanks @arter97
    - free more RAM by removing unused reserved memory regions
    - mm: Micro-optimize PID map reads for arm64 (improves game performance, especially unity based games such as genshin impact)
    - MGLRU added (info here and here

    Security related features:
    - Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) (CAF 5.4 default, keep for documentation)
    - Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO (CAF 5.4 default, keep for documentation)
    - Shadow Call Stack (SCS) Security-Feature ( 5.4 default, keep for documentation)
    - enable init_on_alloc for even more security, more information can be found in the commit message (CAF 5.4 default, keep for documentation)


    Misc Features:

    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
    - blocking a kernel wakelock should only be done in case of firmware incompatabilities (WiFi network at work (can´t be changed) causes deep sleep to not work on the phone.) That´s the only use case I see for this feature. The kernel does not features this to improve battery life!

    Other features:
    - clean up asus drivers and fix a few warnings in kernel log
    - disable logging and debugging to make the kernel more lightweight in various places (includes binder, mm, vma, gpu, ipa etc)
    - fix several coding issues detected by newer Clang-Toolchains
    - enlarge dmesg size to ease debugging


    Flashing Guide, Download and Changelog

    Requirements:
    - unlocked Bootloader (this will void warranty and kill future OTA updates on all asus phones at the moment)
    - USB-Debugging in developer options enabled
    - latest adb and fastboot binaries
    - working adb and fastboot environment
    - magisk root
    - a backup of stock boot.img, vendor_boot.img and dtbo.img so you can go back to stock conditions (simplest way is TWRP or to extract from stock firmware)

    How to flash the Kernel:
    1. Download the latest kernel.zip and make sure you have properly updated to the latest matching Asus Stock-Firmware. When the Zenfone 8 receives an OTA update it takes Asus a while to release the source code for the new OS and me a while to build a new kernel. If you don´t want to face any issues, wait until I either release an updated kernel or give green light because there were no kernel changes.
    Always make sure to run the firmware the kernel is built for!
    If you feel adventurous and try in advance, make sure you have a backup ready!

    2. Flash the kernel.zip via latest TWRP (if available), EXKM or FKM app and do a full reboot.

    3. Reboot and profit.


    DOWNLOAD:
    Download is located always in this folder:

    Important: Read after Download
    Please take a look at the second post after flashing the kernel!

    Changelog:
    Android 11

    1.0.0 Initial Release
    1.0.3 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85230887
    1.1.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85369421
    1.3.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85471991
    1.4.7 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85580815
    1.5.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85708459
    1.7.5 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85845707
    1.7.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85845707
    1.7.9 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86004361

    Android 12
    1.0.0 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86200913
    1.0.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86219239
    1.0.2 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86221081
    1.0.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86546997


    Donations:
    Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea :)
    If you like my work: http://paypal.me/freak07

    Credits:
    Asus for the development device, giving me the opportunity to create this project!
    @osm0sis for all his work, including the ak3 installer!
    @tbalden for being the best HTC, Pixel, OnePlus and now Asus wingman!
    @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!


    Source Code: https://github.com/freak07/Kirisakura_SAKE_Zenfone_8
    9
    Update to 1.7.5

    Hey guys and girls,


    I hope everyone is having a good day or starting into one. Here´s the next update.
    The kernel is updated for the latest firmware:
    30.12.112.36. Make sure to update to the latest firmware before flashing the kernel to have no compatibility issues.

    The link to the firmware can be found here:


    More changes in the Changelog below:


    Changelog:
    - Import zenfone8_zs590ks.MR1-30.12.112.36 source code
    - Linux-Stable Upstream to 5.4.155
    - Merge CAF (QCOM) upstream
    - remove logging while device is suspended
    - improvements to deep sleep power consumption (ufs driver, auto hibernate)
    - reduce auto suspend delay in various other drivers
    - improvements on various subsystem like memory management, bluetooth, display, gpu etc
    - implement LRNG (thanks @arter97, see arter kernel OP for more info )
    - updates from kernel common for several subsystems
    - updated ak3 zip, thanks to @osm0sis


    Download:



    Instructions can be found in the OP!
    But look at this post too :)

    Have fun, enjoy the kernel and your phone.

    Donations are not mandatory but very welcome.
    If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
    8
    Update to 1.0.8

    Hey guys and girls,


    Alright so here´s the next update. The asus source for the new updates didn´t contain anything that we didn´t already have by merging CAF and linux-stable upstream.

    However it was time for an update.

    After flashing the kernel.zip there will be a magisk module in magisk manager called AK3 Helper Module. Do not delete it.

    The link to the latest firmware can be found here:
    [/URL]


    More changes in the Changelog below:


    Changelog:
    - Linux-Stable upstream bumped to 5.4.182
    - use prebuilt clang 14.0.2
    - CAF-Upstream
    - wifi driver updated with caf-upstream
    - update f2fs fsck spoof


    Download:



    Instructions can be found in the OP!
    But look at this post too :)

    Have fun, enjoy the kernel and your phone.

    Donations are not mandatory but very welcome.
    If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
    7
    Update to 1.0.0

    Hey guys and girls,


    I hope everyone got smoothly into the new year. A bit late, but Happy New Year to everybody.
    The Android 12 update arrived.

    Kernel was rebased from scratch as Android 12 uses a different qcom base than Android 11. This was a lot of work, but it went more smoothly than I expected.

    All previous features and changes should still be intact. Android APIs changed on Android 12, so some kernel changes for CleanSlate apps were necessary. Please update the CleanSlate apps according to the instructions on the CleanSlate thread here and here.

    After flashing the kernel.zip there will be a magisk module in magisk manager called AK3 Helper Module. Do not delete it.

    The link to the firmware can be found here:


    More changes in the Changelog below:


    Changelog:
    - Rebase the complete kernel on Android 12 source for Zenfone 8; zenfone8_zs590ks.MR2-31.1004.0404.73
    - latest linux-stable merged
    - latest qcom upstream merged, including the wifi driver (this contains a ton of improvements)
    - all previous features are kept intact
    - update CleanSlate config and companion app according to instructions on the CleanSlate thread here and here


    Download:



    Instructions can be found in the OP!
    But look at this post too :)

    Have fun, enjoy the kernel and your phone.

    Donations are not mandatory but very welcome.
    If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
    7
    Freak07,
    Hi,
    Will you update your kernel for current firmware (.43) ?
    Thanks!

    When I find time. They bumped the CAF-Base, but my kernel is still ahead.

    This creates a lot of conflicts during merging. Either I need to start from scratch again or check in detail how much work merging and fixing all the conflicts will be.