Database Develop

[KERNEL] [OOS] Omega Kernel OOS11 [April 19, 2021] - OnePlus 8 Pro ROMs, Kernels, Recoveries, & Other

Introduction
Hello everyone, this is my personal kernel for the OnePlus 8 Pro, will use it as my daily driver as soon as I get the device! (hopefully very early next week)
My philosophy on the kernel is pretty simple, intended to replace the stock kernel, but with a lot of under-the-hood tweaks.
Hopefully you will all enjoy!
Important thread information!
I refuse to acknowledge/respond to bug reports that do not include clear steps to reproduce, a logcat, and a console ramoops (if random rebooting) or a dmesg (any other issues). Follow this guide to do this.
Keep things civil, no flaming in the forums!
Features
Up to date with OxygenOS 11 source
Compiled with Google's Clang toolchain for maximum stability, with all warnings and errors fixed
Compiled with Clang's cortex-a55 optimizations
Many tweaks under the hood for smoother UX, lower battery drain, etc.
Westwood as the default congestion algorithm
Includes WireGuard
Includes KCAL support
Available to flash with AnyKernel3
Latest kernel release on GitHub
LINK
Source
Omega GitHub: https://github.com/kristofpetho/kernel_oneplus_sm8250
Omega originally sourced from: OnePlusOSS
Thanks where it's due
Nathan Chance for his guidance and patience with general kernel dev questions
Kerneltoast for his extreme patience and guidance
freak07 for his dtb advice
tbalden for figuring out the 8 Pro boot issues
zoman7663 for testing
osm0sis (for AnyKernel3)

Releases
April 19 - download HERE
- Fixed bootloop issue
April 16 - download HERE
- Updated Clang to Google's latest
- Disable coresight clocks when not used (better battery drain)
- Pulled back the two fixes for network driver that previously fixed random reboots (apologies, don't know how I didn't have those in latest...)
March 23 - download HERE
- Cleaned out older commits (stability)
- Updated Google's Clang toolchain to 12.0.4 (latest)
- Fixed a GPU bug where the UI might jitter a bit (smoothness)
March 16 - download HERE
- Enabled a new set of Clang compilation diagnostics, and fixed them with the help of CAF, who started fixing them in their 5.4.y kernels (7 coding errors)
- Fixed a similar issue in the qseecom driver that didn't show up in diagnostics
- Fixed a potential resourcing error in the mhi bus driver
March 13 - download HERE
- Reverted all CAF patches to fix hiccups observed in UI
- Kept 1 USB driver patch to fix faulty transfer of big files
- Kept 2 network driver patches to address random reboots previously observed
March 10 - download HERE
- Reverted all CAF patches from the kernel
- Added back only critical fixes that (hopefully) do apply to our use case (not did add back any "nice-to-have" patches)
March 4 - download HERE
- Pulled in some critical bugfixes from CAF:
- 3 UFS file system fixes
- 1 F2FS fix
- 1 memory allocation fix
- 3 wireless driver fixes
- 1 more USB transfer fix
- 4 GPU/video driver fixes
- Updated Anykernel3 to latest version
- Built with Google's Clang 12.0.3 (I save ~1 minute every time I do a build, which adds up)
February 26 - download HERE
- Switched back to LLVM's Clang 11.1.0 branch for stability reasons
- Updated Wireguard to latest version
- Potential fix for some random reboots a few users were seeing (reverted two smoothness commits)
- Fixed a major code error in OnePlus's source code
- Potential fix for CPU's min frequencies sticking in some situations
February 22 - download HERE
- Updated Wireguard to latest v1.0.20210219
- Removed more debugging from GPU driver for smoothness
- Updated compiler to Google's Clang 12.0.3
February 14 - download from HERE
- Reverted "Removed 3 performance loggers/debuggers from the kernel" to fix media playback issue
February 11 - download from HERE
- Heavy kernel cleanup, removed a lot of commits that either did nothing, or even reduced performance
- Reverted to using userspace, Oneplus-supplied WiFi driver (improved battery life)
- Fixed some previous ugly code fixes I had in the kernel
- Enabled Clang's detection of code formatting errors, and fixed all of them
- Removed 3 performance loggers/debuggers from the kernel
January 25 - download from HERE
- Switched back to Google's Clang 12.0.2 for compiling (much faster to compile)
- Updated WireGuard to latest version
- Fixed some coding errors caught by Clang after turning on some additional diagnostics
January 20 - download from HERE
- Switched from Google's Clang 12 compiler to stable LLVM Clang 11.0.1 (custom built)
- Removed all debugging from the camera driver (it will not kill the battery if you use the camera a lot)
- Removed some overbearing debugging from the video/media driver
- Removed debugging from the Oneplus priximity driver
- Fixed coding errors found by a run of GCC compiler (there were 2-3 major errors in the code that Clang didn't catch)
- Added WLAN driver to the kernel (using the same 5.2.022.3E driver that Oneplus is using)
- Removed a ton of debugging from the WLAN driver, and fixed some code errors
- Added RMNET driver to the kernel (version parity with the WLAN driver)
- Removed external module support from the kernel, since all modules now reside in the kernel
January 14 - download from HERE
- Adjusted kernel configuration to reflect the addition of a new Oneplus kernel module in OOS 11.0.3.3
- Added back a debugger that is needed by Oneplus's userspace
- Removed some harmless kernel loggers
- Further code fixes in the kernel
- Updated to Google's new Clang 12.0.1 compiler to compile the kernel
December 22
- Back to using binutils (from LLVM tools) - I experienced nav bar graphical glitches with LLVM tools
- Pulled in a few tweaks from Sultan's new redbull kernel - optimized graphics driver, optimized power usage, optimized smoothness
- Updated Wireguard to latest version
- Updated Anykernel3 to latest version
December 13
- Reverted all CAF patches... let's assume Oneplus actually knows what they are doing
- Compiled with advanced LLVM tools
- Reverted a commit that is not needed for LLVM, but was needed for latest binutils (which we are now not using)
December 4
- Added a few fixes from CAF upstream
- Cleaned up unneeded commits
- Removed bad commits
- Removed more logging (that are safe to remove)
November 24
- Refactored some commits for easier later patching
- Finally using UFS 3.0 driver that's meant for the OnePlus 8 Pro
November 20
- Fixed battery drain issue that was on previous release (apologies for that)
November 16
- General stability improvements
- Slightly improved active as well as idle battery drain
- Updated WireGuard to latest version
November 6
- Removed a major debug from the kernel that is also missing on stock kernel (sources were not updated by Oneplus...)
- Reverted to using O2 optimization level from O3, for stability reasons
- Reverted modified CPUsets, the overall experience is much smoother this way, with no discernible effect on battery life
October 23
- Reverted the two Google commits since those seemed to increase active drain just a bit
- Pulled in latest Oneplus kernel source for OOS 11.0.1.1
October 19
- Reverted the CAF upstream - Oneplus does extensive testing on the CAF base they are using and it also resulted in significantly higher active as well as idle drain upon further testing
- Using stock (userspace) WLAN and RMNET drivers
- Pulled in two commits from Google's 4.19.y kernel tree for increased smoothness (scheduling, write delay)
- Fixed a additional code error found through Clang
October 10
First release for Android 11-based OOS11.
Changelog vs stock kernel:
- Compiled with latest Google Clang 11.0.5
- All the tweaks pulled in from Omega OOS10 kernel
- Added in KCAL color control
- Upstreamed the entire kernel to CAF release LA.UM.9.12.r1-08300-SMxx50.0
- Included both WLAN and RMNET drivers with CAF release LA.UM.9.12.r1-08300-SMxx50.0

Philosophy
- The kernel will always be up-to-date with OnePlusOSS sources
- No additional functionality, only stock
- Only code fixes, code optimizations, and minor tweaks to keep it 100% stable
- Only logging and debugging will be removed

I can flash this with EX kernel manager?
Sent from my OnePlus 8 Pro using XDA Labs

Gordietm said:
I can flash this with EX kernel manager?
Sent from my OnePlus 8 Pro using XDA Labs
Click to expand...
Click to collapse
See post 2. And yes, EXKM is also my kernel flasher of choice.

Happy to see you here, used your kernel on the 6T also Flashed and all seems to be good!

Welcome buddy
One of the most popular kernels for the OP6T...
Also for the 8pro ..

Nice to see here! Kudo's

Will I lose root when I flash it?
Sent from my OnePlus 8 Pro using XDA Labs

kristofpetho said:
May 9 - First release
- It boots! YAY
- Built with Clang 10.0.0 stable, polly and cortex-a55 optimization
- Few initial tweaks, some minor debugging removed
Click to expand...
Click to collapse
Any possible way you could try to compile a clang 11 build by chance?

Is it possible to add some kinda touch input boost? Screen sometimes feel sluggish..slow..typing is difficult.

Burt Squirtz said:
Any possible way you could try to compile a clang 11 build by chance?
Click to expand...
Click to collapse
My preference is stable Clang, unless you give me a good reason to use Clang 11.
OPOmaniac said:
Is it possible to add some kinda touch input boost? Screen sometimes feel sluggish..slow..typing is difficult.
Click to expand...
Click to collapse
No. See post #3. BUT -> when I finish the tweaks, it will be much smoother than stock.

Gordietm said:
Will I lose root when I flash it?
Sent from my OnePlus 8 Pro using XDA Labs
Click to expand...
Click to collapse
No you will not, AnyKernel3 will preserve root.

kristofpetho said:
No you will not, AnyKernel3 will preserve root.
Click to expand...
Click to collapse
Will this kernel be able to use normal update of the original Oneplus firmware through the system? Download with oxygen updater and flashing through local update.

golf60 said:
Will this kernel be able to use normal update of the original Oneplus firmware through the system? Download with oxygen updater and flashing through local update.
Click to expand...
Click to collapse
Sure, but you will need to reflash kernel again after the update

marko94 said:
Sure, but you will need to reflash kernel again after the update
Click to expand...
Click to collapse
That's great.

So flashed the kernel with EX Kernel Manager. Everything works great and still rooted.
Thanks for your work!
Do you recommend to keep Ram Boost still enabled?
Sent from my OnePlus 8 Pro using XDA Labs

Gordietm said:
So flashed the kernel with EX Kernel Manager. Everything works great and still rooted.
Thanks for your work!
Do you recommend to keep Ram Boost still enabled?
Sent from my OnePlus 8 Pro using XDA Labs
Click to expand...
Click to collapse
Up to you. I personally have it turned off on my 6T currently.

Flashed! Lets see what is the hype about )) Cant wait for more updates!
EDIT. ok man, im after reboot and my phone feels MUCH faster! Like, scrolling is major improved. I did not expected.

OPOmaniac said:
Flashed! Lets see what is the hype about )) Cant wait for more updates!
EDIT. ok man, im after reboot and my phone feels MUCH faster! Like, scrolling is major improved. I did not expected.
Click to expand...
Click to collapse
That's always after reboot. I have the same problems with screen responsiveness as you. Seems like the phone needs some time to **** it up after rebooting ?
But who knows, let's hope I'm wrong!

Related

Welcome to the N0G33K edition Kernel ​
This kernel is built on the idea of having optimized battery life and performance. A well made balance between these two is what you get.
Read this first
Please do not post requests, because this is my personal kernel and I won't add any stuff I do not want myself (i.e D2W, S2W, AOD, sound control etc). Also I won't add any other support for other devices. Last but not least: I don't reply to questions like: "which governor/scheduler is the best" etc. The choice is all yours.
PS: You need to root yourself (Magisk or SuperSU)
Features
Based on the latest G920FXXU5DPL4 kernel source
Added Linux 3.10.105
Tons of Governors and schedulers added
Compiled with Sabermod 7.0 GCC
Deep sleep and Google Play Services Fix
Enabled Permissive mode
Disabled Knox
Synapse Control
Entropy optimization
Scheduler Improvements
Binder Improvements
Idle Improvements
Other misc optimizations
Download:
V4 https://mega.nz/#!I05xUDLD!7T86PGq2VtTc15VrfFoXhhKth3FIpI4O0gxpTA8vd2s
Changelog:
V1
- Reworked whole kernel
- Optimized battery and performance
V1.1
- Reverted some stuff to test 3
- Fixed Fading LED
V1.5
- Tweaked LMK
- Optimized Workqueue
- Added battery efficiency patches
- AES put to x4 for more speed
- Readahead tweaked
- Vnswap to fast device
- HMP adjusted for more smoothness / battery efficiency
V1.8
- Reverted LMK and Workqueue edits.
- Enabled powereffici�nt Workqueue
- Tweaked Interactive governor
- Added Powersuspend
- Added more Binder changes for UI smoothness
- HMP and Cpuidle improvements.
- LZ4 Compressed
1.9
- Went back to UBERTC 5.3 because N0G33K V1.8 had kernel panics.
- Removed wlan wakelock control and reduced it myself.
- Some other edits and reverts
V2.0
- Reverted ALOT of changes I made in previous versions.
- Updated Kernel source to the latest DPJ2 source
- Compiled with Sabermod 7.0 Toolchain with CCache (should be stable now)
- Updated Linux to 3.10.104
- Backport latest Linux 4.8 random driver (= like super Seeder)
- Backport latest crypto algorithm Chacha20
- Added new battery efficiency patches
- Tweaked interactive governor for better performance/battery.
- Added new governors: Yankactive, Smartmax and Smartmax_eps
- Updated BFQ I/O
- Added dual sim support
- Fixed Invisible CPUset (should actually work now)
- Screen on hotplug disabled (Dynamic hotplug wasnt good enough)
- Added wakelock controls again.
- Updated Synapse
- Patched "Dirty Cow" (CVE-2016-5195) exploit
- Zswap improvements
- Disabled big cores on screen off
- Improved CPUIdle
- Powersuspend hooks added
- and more
V3
Reworked the whole kernel:
- Based on U5DPL4 source
- Powersuspend is out, State Notifier is in.
- Replaced Linux 4.8 random driver with Frandom
- Interactive governor: merged Galaxy S7 Interactive changes (android N changes wont boot, so kept it MM)
- Merged S7 zswap/zpool and zsmalloc android N changes
- Added Impulse governor
- Tweaked I/O Schedulers for our SSD + Zen V2 update
- Xbox control support added and updated to latest upstream (can be enabled in Synapse)
- Noatime as default for better performance
- SafetyNet patched (soon there probably will be a workaround for it...so enjoy as long it lasts)
- More wakelocks toggles added
- Sync on suspend disabled
- Improved Idle drain
- Android OS drain should be better now.
- Removed some other stuff that caused yank like invisible cpusets
V4
- Updated Linux kernel to 3.10.105
- Updated Safetynet patch
- Binder updated to latest Linux 4.6 (smoother UI)
- Backported Linux 4.1.38 random driver and removed Frandom
- DVFS decision mode in Synapse added
- DVFS: scale to 1k instead of 1.2k GHz
- Backported latest CPUidle driver from Linux 4.7 (should give better idle experience throughout the day)
- Other misc optimizations
Credits:
- The Sickness - For his guidance and support
- CODEG33K - He knows why
- Aria.A97 - Intensive daily testing
- Everyone else I cherry-picked from.
Source Code: https://github.com/Noxxxious/Zero
Want to use this in your rom?: PM me first. Disclaimer: I am not responsible for all the damages followed by or to your phone after flashing this kernel. If it bricks, wipes, explodes and you will hold me responsible I will only laugh
XDA:DevDB Information
N0G33K Kernel, Kernel for the Samsung Galaxy S6 Edge
Contributors
Quintz
Source Code: https://github.com/Noxxxious/Zero
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: V4
Stable Release Date: February 2017
Created 2016-11-13
Last Updated 2017-02-22

Known issues:
- Probably Synapse "backup profile" doesnt work.
F.A.Q. - Frequently Asked Questions
Q: Synapse says no UCI detected
A: Install Busybox to system/xbin
Q: I had a reboot
A: Only report it here if you didn't undervolt and do it with a log.
A2: If you had random reboot without undervolting, then make a proper log please. Which means I need a last_kmsg from right after the reboot.
You create the log by using this command in adb shell or a terminal or use any 3rd party app like Syslog.
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt

Does this one work for G925F and will it be rooted?

I wish ppl would support w8. I'd be willing to donate for a good kernel

Will this work on the 925T

Link not work

+1
franci79 said:
Link not work
Click to expand...
Click to collapse
Sent from my SM-N930F using XDA-Developers mobile app

hadkeren said:
+1
Sent from my SM-N930F using XDA-Developers mobile app
Click to expand...
Click to collapse
franci79 said:
Link not work
Click to expand...
Click to collapse
Works fine

Testing now [emoji2]

The kernel is absolutely brilliant. I have approx 2 hours youtube and lost only 22 percent of battery 🔋
Gesendet von meinem SM-G925F mit Tapatalk

mydonose said:
The kernel is absolutely brilliant. I have approx 2 hours youtube and lost only 22 percent of battery 🔋
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Stock settings ?

Love this kernel......great work

thank you for sharing your great kernel on the S6 community. Really loving your kernel for my S6 Edge. Running smooth. Keep it going great Kernel developer.

Inverted Sceen
I just flashed the kernel with flashify apk and after the reboot all the icons works in the opposite way. If I push the icon on the left side open the apk of the right side. It happens the same with the TWRP recovery. I tried to recover with the copy before the flash and nothing resolves. I have reinstalled the rom totally clean and nothing changes. G920F
Could you help me?

edzamber said:
Stock settings ?
Click to expand...
Click to collapse
Yes, nothing changed
Gesendet von meinem SM-G925F mit Tapatalk

kurdiakis said:
I just flashed the kernel with flashify apk and after the reboot all the icons works in the opposite way. If I push the icon on the left side open the apk of the right side. It happens the same with the TWRP recovery. I tried to recover with the copy before the flash and nothing resolves. I have reinstalled the rom totally clean and nothing changes. G920F
Could you help me?
Click to expand...
Click to collapse
U installed kernel for 925f on 920f thats why. There is a way to fix it search....... and use this next time.
http://forum.xda-developers.com/gal...ernel-el-generalissimo-v3-01-10-2016-t3472477

Does anyone know how I can use N0G33K with Magisk hide module? Arter Kernel works for me with Magisk and Im able to use Pokemon go. But with N0G33K Kernel I cant play anymore. Any help? Im using a S6 Edge 925F.

will this work on tmobile s6 edge ith alexis rom ?

lilmikey201 said:
will this work on tmobile s6 edge ith alexis rom ?
Click to expand...
Click to collapse
There is thread for t-mobile users as well, but not this kernel......

Harregukalerik said:
There is thread for t-mobile users as well, but not this kernel......
Click to expand...
Click to collapse
So then the answer is no......
Sent from my SM-G925T using Tapatalk

Introducing 4th iteration of F1XY Kernel.​REQUIREMENTS
ROM compatible with msm-4.4, if it runs fine - you are good to go.
Clear mind.
Steardy hands.
Features
Using msm-4.4 kernel source, originally intended for SD660/835. Pie CAF release.
Lots of security improvements.
Kernel improvements from our lord and savior.
Scheduler improvements for better battery life.
Improved CPU freq control.
Faster wakeup.
A bit relaxed CPU throttling.
Improved charging driver for smoother battery charge/discharge.
Boeffla's wakelock blocker.
Latest F2FS + CFQ updates.
NET improvements + Wireguard.
Built with Clang 9.
Contributors
Kenny
Davide
Cooler Davide
Everyone in source: (will takes ages to load)
Subscribe to PewDiePie
Download
1.14: AFH - version for /factory -|- AFH- version for /vendor
1.13: AFH - version for /factory -|- AFH - version for /vendor
1.11: AFH
1.10: AFH
1.09: AFH
1.08: AFH
1.07 - skipped
1.06: AFH
1.05: AFH
1.04 - skipped due to long testing cycle.
1.03: AFH
1.02: AFH
Donations:
Sadly, due to PayPal's restrictions in my country I can't receive direct donations, however, I have a good friend in Russia, who's PayPal is not restricted and who will forward your donations to my debit card.
https://www.paypal.me/xeondead - add note "to Yaro"
XDA:DevDB Information
F1XY-4.4, Kernel for the Lenovo ZUK Z2 (Plus)
Contributors
Star_king12
Source Code: GitHub
Kernel Special Features:
Version Information
Status: Stable
Created 2018-11-13
Last Updated 2018-11-13

Changelogs will live here:
1.02 -> 1.03:
1. Improved GPU frequency control, you should see less lags/stuttering now.
2. Decreased CPU boost.
3. Deleted a few unneeded drivers (sound and touchscreens).
4. Killed IPA_WS wakelock.
5. Fixed some touchscreen regressions after 4.4 update. Wrong coordinates reporting should be fixed
1.03 -> 1.05:
1. EAS.
2. 4.4.165 and CAF updates.
3. Improved fingerprint scanner stability.
4. Zram improvements.
5. Added SimpleLMK (giving it another try).
1.05 -> 1.06:
1. 4.4.166
2. Removed SLMK, no more lockups.
3. Disabled unused I/O schedulers (deadline, test)
1.06 -> 1.08
1. Upstream and CAF updates.
2. Reverted a lot of EAS commits (battery life should improve)
3. Fixed pocket mode.
4. Fixed a few memory leaks.
5. Fixed Hi-Fi sound.
6. HZ set to 1000.
1.08 -> 1.09
1. Some EAS updates.
2. Fixed Wi-Fi that died after 08 for some of the users.
3. Some camera improvemements from OnePlus 5.
1.09 -> 1.10
1. Camera issues should be fixed now.
1.10 -> 1.11
1. Upstream (now with f2fs patches, some bugfixes and stuff)
2. VNDK support.
3. Fixed some memory leaks.
4. Medium overhaul of changes that were done in the past 1-2 months, filtered unused commits and organised everything better.
5. Improved screen wake-up speed slightly.
1.13 is based on 1.10 (and thus 1.09), so changelog is relative to 1.10.
1. As always, EAS updates.
2. Upstream, CAF and kernel/common updates.
3. Fixed some memory leaks.
4. Faster touchsceen wakeup and suspend.
5. Improved performance by decreasing the amount of debug.
6. F2fs updates and improvements.
1.13 - > 1.14
1. Underclocked slightly further (1.4/1.78 GHz are new freqs)
2. Fixed an issue when phone's mic would die when a mic-less headphones were plugged in.
3. Removed an audio improving driver (didn't really improve anything).
4. Some toolchain optimizations enabled.

Reserved

Installed, phone is booting.
Too early for anything else. Thanks ?

Phone booted, but wrote wrong vendor image. Also no sound and no video playback. Didn't test further. :/
Tested on lineage os 15.1

AMDFenics said:
Phone booted, but wrote wrong vendor image. Also no sound and no video playback. Didn't test further. :/
Tested on lineage os 15.1
Click to expand...
Click to collapse
On AEX no problem so far.

On AEX autobrightness doesn't work...
Edit : Sorry its work

AMDFenics said:
Phone booted, but wrote wrong vendor image. Also no sound and no video playback. Didn't test further. :/
Tested on lineage os 15.1
Click to expand...
Click to collapse
Because u need a 4.4 kernel compatible rom which is now only latest aex...

Starchm said:
Because u need a 4.4 kernel compatible rom which is now only latest aex...
Click to expand...
Click to collapse
to bad, but thanks anyway.

First impressions - bit better standby drain than stock aex kernel, smooth, no problem with bt.

It's me or with this kernel OIS is gone again?

so this is good on AEX6 ?

Thanks for update, works great.

I'am on RR 6.2.1 on Zuk 2 pro. Want to move to AEX6. Think I need this kernel. Which is the right way to update?

robert_b said:
I'am on RR 6.2.1 on Zuk 2 pro. Want to move to AEX6. Think I need this kernel. Which is the right way to update?
Click to expand...
Click to collapse
install the rom, according to the instructions posted in the rom's thread.
when rom has installed, you can boot into that rom.
afterwards, if you desire, you can reboot into recovery and flash this kernel.

tried out kernel, wireguard works fine, basic governors been shown instead of schedutil governor, but no zen i/o scheduler
question: is it possible to include the mentioned scheduler back into kernel ? for now i try out the AEX PIE kernel completely before i step into other kernel (Grait Work btw!)

ikram.senguen said:
tried out kernel, wireguard works fine, basic governors been shown instead of schedutil governor, but no zen i/o scheduler
question: is it possible to include the mentioned scheduler back into kernel ? for now i try out the AEX PIE kernel completely before i step into other kernel (Grait Work btw!)
Click to expand...
Click to collapse
1. Schedutil is exclusive for EAS.
2. ZEN is outdated piece of, ugh, code. Use CFQ.
3. They won't be included "back" because they never were here in the first place and they aren't coming.
EAS is coming soon.

New update is live! Check second post for changelog

Thanks, will try asap. Just one curious question - is zRAM necessary since we have 6gigs available?

Oriwen said:
Thanks, will try asap. Just one curious question - is zRAM necessary since we have 6gigs available?
Click to expand...
Click to collapse
Yes, all OEMs ship with zram, even phones with 8gb ram. Android relies on zram for storing some rarely used data.

Kirisakura-Kernel for the Asus Zenfone 6
Hello everyone,
After rising to the most popular Kernel on Pixel 3/XL, here it is for the Asus Zenfone 6!
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!
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.
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. In fact this, alongside Kirisakura-Kernel for the OnePlus 8 Pro, may be (and probably is) the first 4.19 msm kernel with a fully working Kernel-CFI implementation and CFI-Violations fixed on a smartphone.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3, 4 and 5 devices.
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.
Another security feature is Shadow Call Stack (SCS). Similar to CFI, only the Pixel 3, 4 and 5 kernels use this security feature.
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.
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 855/+ that´s built into the different SKUs of the Zenfone 6.
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.
Many of the 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 11
- Upstreamed against latest CAF
- Linux-Stable-Upstream included to latest 4.14.220
- compiled with Clang 11.0.1 prebuilt from Google
- Link-Time-Optimization (LTO)
- Kernel Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common
- Shadow Call Stack (SCS) Security-Feature
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Preview Kernel instead of full LTO for full program visibility (needed by CFI)
- fix CFI-Violations found in various subsystems like Asus/device specific drivers and qualcomm drivers
- Link the kernel with LLD and use RELR-Relocation
- include important fixes/improvements from kernel/common
- Flashing the kernel will keep root!
- Anykernel zip is based on the all new Anykernel3 release from @osm0sis
- include vDSO 32 patches to improve 32-bit performance
- disable various debugging configs, that are not needed in a perf build kernel according to google.
- disable selinux auditing (we don´t have to adress selinux denials running a stock rom)
EAS related features:
- backported scheduler from sd865
- disable autogroups and use cgroups for more efficient task placement!
- disable core_ctl for improved task placement and load balancing
- updates from kernel/common
- scheduler updates from Googles Pixel kernel
CPU related features:
- Power saving workingqueues enabled by default (toggleable in EXKM)
have a read here: https://lwn.net/Articles/731052/
this complements EAS in general
- Change various drivers ( MM, audio) to user power efficient workingqueues. This should work well in conjunction with EAS
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- improve memory allocations in binder driver
- vdso32 patches as found on Google Pixel devices (brief documentation here)
File System related features:
- Set the bio REQ_NOENCRYPT flag (When lower layers such as dm-crypt observe the REQ_NOENCRYPT flag, it helps the I/O stack avoid redundant encryption, improving performance and power utilization. ) (CAF default)
- improve memory allocations in sdcardfs
- improve eventpoll logging to stop indicting timerfd (improves kernel wakelock readability)
- improve memory allocations in kernfs
- writeback: hardcode dirty_expire_centisecs=3000 based on this commit
- ufs improvements from pixel 4/ pixel 5 kernel
GPU related features:
- KCAL to control the display
- KLAPSE integrated
- KCAL/KLAPSE: changes safety measures -> allow completely disabling two RGB values (this was requested to, for example, only have red values on night dimming)
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbrv2
Memory related features:
- Memory Management patches from mainline kernel
- Speculative Page Faults (1. 2)
- Fix various memory leaks in different subsystems
- Reap memory of a task that receives sigkill
- enabled per process reclaim
- allow ZRAM to use higher swappiness values than 100
- possibility to use lzo-rle as default ZRAM compression algorithm (more information here and there )
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO
- Shadow Call Stack (SCS) Security-Feature
- fix various CFI-Violations found in various subsystems like Asus/device specific drivers and qualcomm drivers
- enable init_on_alloc for even more security, more information can be found in the commit message
WLAN Driver
- use CAF wlan driver and compile it inline, the only way to ensure working wlan with this kernel
- the kernel cannot even force load prebuild WLAN module as the kernel base is way to far from stock!
- do no longer rely on the pre compiled wlan driver module
- completely removed qcom_rx wakelock in the wlan driver
- removed debugging from wlan driver
- removed logging from wlan driver
Magisk Companion Module
- set kernel settings like I intend them to be
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:
- disable logging to make the kernel more lightweight in various places
- fix several coding issues detected by newer Clang-Toolchains
- add support for steam controller
- add support for nintendo switch controller
- ufs improvements from pixel 4/ pixel 5 kernel
- gpu/kgsl improvements from pixel 4/pixel 5 kernel
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
How to flash the Kernel:
1. Download the latest kernel.zip
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img, re-root with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
2. Make sure to use latest Magisk stable. (not the latest canary!)
3. Flash the kernel.zip via latest EXKM or FKM app. Alternatively via TWRP.
4. Reboot and profit.
DOWNLOAD:
Download is located always in this folder:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 9/Pie
1.0.0 Initial Release
1.3.0 https://forum.xda-developers.com/showpost.php?p=79852192&postcount=21
1.5.0 https://forum.xda-developers.com/showpost.php?p=79948337&postcount=36
1.6.0 https://forum.xda-developers.com/showpost.php?p=80037776&postcount=46
1.8.1 https://forum.xda-developers.com/showpost.php?p=80275065&postcount=58
3.0.0 https://forum.xda-developers.com/showpost.php?p=80712703&postcount=66
Android 10/Q
1.0.0_Q https://forum.xda-developers.com/showpost.php?p=81368413&postcount=73
1.0.3_Q https://forum.xda-developers.com/showpost.php?p=82387237&postcount=86
1.2.0_Q https://forum.xda-developers.com/showpost.php?p=83920653&postcount=92
Android 11/R
1.0.1_R https://forum.xda-developers.com/t/...sus-zenfone-6-aka-kirin.3940178/post-84526765
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee
If you like my work: http://paypal.me/freak07
Credits:
Asus for the Zenfone 6!
@osm0sis for all his work, including the ak2 installer!
@tbalden for being the best HTC wingman!
@LeeDroid for his awesome roms!
@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
@topjohnwu for magisk!
@osm0sis for anykernel!
XDA:DevDB Information
Kirisakura-Kernel, Kernel for the ASUS ZenFone 6 (2019)
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_Kirin
Version Information
Status: Stable

Mine for FAQ

Too

And too

Flashed it today and no problems so far.
Everything seems to work as intended

Freak07 said:
Mine for FAQ
Click to expand...
Click to collapse
Which RAM version do you have please?
Is the kernel for both?

EMJI79 said:
Which RAM version do you have please?
Is the kernel for both?
Click to expand...
Click to collapse
The 8GB version. RAM variant shouldn´t matter.

1. Does it have to be magisk stable or is canary (dev version) ok? I am asking because i need to use canary so my stupid pay app will not detect root.
2. This might sound stupid but what is magisk companion and where do i get it? I can not find it in the magisk modules repository or on xda and neither google.

2. This might sound stupid but what is magisk companion and where do i get it? I can not find it in the magisk modules repository or on xda and neither google.[/QUOTE]
It's in the downloads folder at the end of the afh link in the OP

isthisadagger said:
1. Does it have to be magisk stable or is canary (dev version) ok? I am asking because i need to use canary so my stupid pay app will not detect root.
2. This might sound stupid but what is magisk companion and where do i get it? I can not find it in the magisk modules repository or on xda and neither google.
Click to expand...
Click to collapse
jeremyet said:
2. This might sound stupid but what is magisk companion and where do i get it? I can not find it in the magisk modules repository or on xda and neither google.
Click to expand...
Click to collapse
It's in the downloads folder at the end of the afh link in the OP[/QUOTE]
1. you can probably use the canaries of magisk too. But keep in mind, they’re canary builds for a reason. If you’re having issues, flash to magisk stable and see if you can reproduce them.
2. Like @jeremyet said, it’s in the download folder in the OP

good job man

@Freak07: Cool, the first costom kernel for the Zenfone 6, thanks
I am still thinking of switching to the Zenfone 6, one feature I currently use a lot, is the "USB fast charge" : it makes a big difference, if I have my Smartphone for file transfer on my Laptop or PC, whether it charges in the background only with 500 mAh or with a little over 900 mAh on my USB 3 ports.
Does your kernel support USB fast charge / if not: will it be supported? (some custom kernels devs don't want to implement it, bacause it is not an official feature and "might" not work perfectly)

Coming from stock kernel, I got stuck at the Zenfone logo during reboot after the first flash with exkm. Volume down+power fixed that and after flashing a second time all seems to be working ? zram is at 684mb for my 6Gb variant.
Thank you a lot.

A quick question about the kernel source: Is there an API/kernel endpoint that can be used to query and manipulate the flip camera's motor? If so, is it something than can be accessed from userland? I was wondering if one might be able to write a shell script that can be used to send commands to it.

Does camera has OIS? I've seen OIS code in DTS

dmd79 said:
Does camera has OIS? I've seen OIS code in DTS
Click to expand...
Click to collapse
It's not the object of this thread.
There's a "ask me anything thread" in the discussions forum.

Flashing via EXKM will NOT work, if you’re on the latest magisk canary! (currently 19305!)
19302 is still working fine with EXKM, as is stable 19.3. Big changes in magisk are coming. we will have to wait for flar2 to find a new way of flashing zips.

Can this be flashed on the latest update or does it require an update from you? If not are there any downsides to it not being based on the most current kernel source code then?
Kind regards

regenwurm16 said:
Can this be flashed on the latest update or does it require an update from you? If not are there any downsides to it not being based on the most current kernel source code then?
Kind regards
Click to expand...
Click to collapse
Wait a bit. I’ll release an update soon. (hopefully later today) This will have latest asus sources merged.
I currently see 2 downloads for my kernel :cyclops: so I thought I can take it slow.
Testing was good so it should be ready for prime time stay tuned!

Thanks for your effort.
If think the two downloads are because of the scarce availability of the phone. I ordered mine on 5th of June on Amazon Germany the 6GB RAM 128GB ROM variant (only model they sell) and it took until 1st of July to get to me
I would have ordered on the Asus eShop but they don't ship to my country/don't have a shop for my country
Just take a look in the UK availability thread it's even worse there

Kirisakura-Kernel for the OnePlus 8 Pro
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the OnePlus 8 Pro aka InstantNoodle.
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!
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.
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. In fact this may be (and probably is) the first 4.19 msm kernel with a fully working Kernel-CFI implementation and CFI-Violations fixed on a smartphone.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3 and Pixel 4 devices.
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.
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 865 that´s built into the OP8 Pro.
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 others 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.
I´d like to mention @tbalden ´s excellent CleanSlate features at this place. They improve usability by a big margin for me personally. The highly customizable sweep to sleep implementation (adjustable to different navigation settings), long tap to bring down status bar (very useful on a big device), backlight dimmer and notification reminder are very useful features that I use personally every day, which can be enabled rootless if one desires to run without root.
Another 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 OnePlus for Android 10 and intended for use on OOS-Stable releases
- compiled with Clang 11.0.3 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 4.19.146
- CAF base for the Snapdragon 865 (SD865) updated to CAF-Tag LA.UM.8.12.r1-12500-sm8250.0
- Kernel Control-Flow-Integration (CFI) andLink-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Shadow Call Stack (SCS) Security-Feature
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Preview Kernel instead of full LTO
- fix various CFI-Violations found in various subsystems like OnePlus drivers and qualcomm drivers
- Link the kernel with LLD and use RELR-Relocation
- include important fixes/improvements from kernel/common
- Flashing the kernel will keep root!
- Cleanslate Features included! See @tbaldens´s CleanSlate Thread for more information
- Flashable via EXKM and FKM on a rooted system!
- Anykernel zip is based on the Anykernel3 release from @osm0sis
EAS related features:
- EAS implementation patched up to latest CAF state
- disable autogroups and use cgroups for more efficient task placement!
- Dynamic Stune Boost to inflate task utilization and not overload cores on interaction (thanks to @RenderBroken, @joshuous and @tbalden for the rootless implementation )
- updates from kernel/common
CPU related features:
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to user power efficient workingqueues. This compliments EAS
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- improve memory allocations in binder driver
GPU related features:
- GPU driver updated to latest CAF-State
- remove POPP functionality from GPU driver to avoid constant fight about downscaling with msm-adreno-tz
- don´t wake the gpu on touch input, instead wake when receiving an ioctl
- don´t copy fence names by default to save a bit of cpu-time (explanation)
- msm: kgsl: Stop slab shrinker when no more pages can be reclaimed
File System related features:
- improve memory allocations in sdcardfs
- improve eventpoll logging to stop indicting timerfd (improves kernel wakelock readability)
- improve memory allocations in kernfs
- writeback: hardcode dirty_expire_centisecs=3000 based on this commit
UI/UX/Usability related features from CleanSlate:
- CleanSlate features made by @tbalden
- Flashlight Notification/Call blinking
- Vibrating Notification Reminder
- Sweep to Sleep touchscreen gesture - highly customizable
- DoubleTap on Sweep2Sleep's area gestures - new way to pull down android Notification Area
- Face down screen off - new gesture
- Backlight Dimmer - possibility to use lower panel brightness (switch DC dimming off in Lab settings!)
- KCAL Color Control (credit to @savoca)
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbr2
Memory related features:
- Speculative Page Faults left enabled (1. 2) (CAF default)
- various fixes for PSI-Monitor, which is used by the userspace lowmemorykiller-daemon
- Fix various memory leaks in different subsystems
- improved mm with patches from mainline
- various other changes from mainline
- included zstd as an option for ZRAM-algorithm (lz4 is probably the best all around, so only change it if you know why and what you are doing)
- improve memory allocations in various subsystems
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO
- fix various CFI-Violations found in various subsystems like OnePlus drivers and qualcomm drivers
- enable init_on_alloc for even more security, more information can be found in the commit message
Misc Features:
TCP Congestion Algorithms:
- advanced algorithms enabled, enable them with your favorite kernel manager
- includes new bbr2
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:
- 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
- add support for steam controller
- add support for nintendo switch controller
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest matching OnePlus firmware. When OOS receives an update it takes OnePlus 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.
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img, re-root with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
2. Make sure to use latest Magisk-stable, if you choose to use Magisk.
3. Flash the kernel.zip via latest EXKM or FKM app, or TWRP (haven´t tested TWRP myself as I don´t need it) and do a full reboot.
4. Reboot and profit.
DOWNLOAD:
Download is located always in this folder:
https://www.androidfilehost.com/?w=files&flid=313864
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 10
1.0.0 Initial Release
1.2.0 https://forum.xda-developers.com/showpost.php?p=83260487&postcount=67
1.2.2 https://forum.xda-developers.com/showpost.php?p=83521551&postcount=119
1.2.4 https://forum.xda-developers.com/showpost.php?p=83539543&postcount=125
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee
If you like my work: http://paypal.me/freak07
Credits:
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC wingman!
@LeeDroid and @mwilky for their awesome roms and work!
@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 too
@topjohnwu for magisk!
XDA:DevDB Information
Kirisakura Kernel, Kernel for the OnePlus 8 Pro
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_OP8PRO_InstantNoodle
Kernel Special Features:
Version Information
Status: Stable
Created 2020-06-19
Last Updated 2020-09-20

FAQ
F.A.Q:
Question: Is root preserved when flashing this kernel?
Answer: Yes, the AnyKernel.zip will detect root and keep it.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img from matching firmware you are on and flash the extracted boot.img via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom.
Question: How to report bugs properly?
Answer: Have a look at post #3 in this thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re not using any mods, magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a ramoops file.
Easiest way is immediately after booting up, with a root explorer navigate to sys/fs/pstore. Copy the contents to your internal storage, zip it up and send it to me.
If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!

Useful Resources
How to report bugs:
It is incredibly useful if bug reports are done in a proper way. That saves everyones time and will ultimately lead to a faster bugfix (hopefully).
The following guide from @nathanchance is a very good guideline on how to properly report a bug!
Please also take a log at the FAQ one post above. It covers some procedural steps as well and serves as a guideline too!
https://github.com/nathanchance/Android-Tools/blob/master/Guides/Proper_Bug_Reporting.txt

Hello everyone
I want to lose a few words about this kernel.
Before anybody asks, it´s made for the OP8 Pro only!
As you may or may not have noticed by reading the OP this kernel is very far from the stock base.
Adding linux-stable upstream and CAF-Upstream causes the commit-count to increase from 805000 to about 840000.
A "higher" commit count does not automatically translater to a better kernel. However upstreaming linux-stable and the CAF-Base to the latest code is an important aspect, that´s often cast aside. (after all the android kernel is based on the linux-kernel and the CAF-Base is the kernel base OnePlus bases the kernel for the OP8 Pro on) . Many developers work constantly on improving the linux-stable branches with commits that are tested, same goes for the qualcomm developers over at the CAF-Forums.
The main goals of this kernel are summarized in the OP. I encourage everyone to at least read once through it.
Here´s a short summary of what I think are the most characteristic and important aspects (also an excerpt from the first post of this thread ):
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security, stability and performance! This includes Linux-Stable, CAF-Upstream and kernel/common.
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. In fact this may be (and probably is) the first 4.19 kernel with a fully working Kernel-CFI implementation and CFI-Violations fixed.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3 and Pixel 4 devices.
If some of 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.
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 865 that´s built into the OP8 Pro.
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 others 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.
I invite everybody to try the kernel
If you face any bugs, I´d appreciate if bug reports are done in the proper way, like it is asked for and explained in the 2nd and 3rd post.
If you read the OP you probably noticed I´m not talking about any improvments (some call it even magic) to performance or battery life. This is not one of the direct goals of this kernel.
If the modifications present in the kernel make you feel a noticable difference in either of these I´m very happy for you. I know that artifical benchmarks are improved and some other things I tested.
If this kernel is not for you you can very easy return to the stock kernel, like it´s described in the FAQ as well!
There might not be updates of this kernel for every single linux-stable upstream revision that is released at kernel.org or every single new commit added to the tree, but rather less updates but bigger ones.
I guess that gives everybody a rough idea of where this project might be going.
I wish everybody a nice day

Loved this for the 7 pro. Welcome ?

Woohoo, welcome!
Congrats on this truly great achievement.
Keep it up.
[emoji106][emoji106][emoji122][emoji122]
Sent from my Pixel 4 XL using Tapatalk

Excellent, welcome!

Hey buddy! Nice to see you here! ?

possible to add option to disable touchboost?

tbalden said:
Woohoo, welcome!
Congrats on this truly great achievement.
Keep it up.
[emoji106][emoji106][emoji122][emoji122]
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Thank you! Glad to have you as a wingman for a very long time across different devices now!
Keep on rocking with all the CleanSlate goodies!
Reuben_skelz92 said:
Loved this for the 7 pro. Welcome
Click to expand...
Click to collapse
kristofpetho said:
Excellent, welcome!
Click to expand...
Click to collapse
TheKnux said:
Hey buddy! Nice to see you here!
Click to expand...
Click to collapse
Thank you
Nekromantik said:
possible to add option to disable touchboost?
Click to expand...
Click to collapse
Yes, since all Cleanslate features are included it´s accessible via CleanSlate config app.
https://forum.xda-developers.com/showpost.php?p=82598221&postcount=192
Gestures and Extras Section - Stock touchboost.

nice to see ya here

Doing a sexy dance right this minute! :victory: Dam glad your covering this device now also buddy Always a great solid kernel that runs smooth and fluid without issue! :good:

Omg the kernel was amazing on the OP7P, can't wait to use this one again on my 8!

Running smooth as butter for me ?

Thank you sir, donation sent.

Nice to see this Kernel here for the 8pro
Gesendet von meinem IN2023 mit Tapatalk

seems it disable lowmemorykiller? i cant check it from FK kernel App and i want change it, **** OS with12g RAM still killng bg app
max its used 65% RAM, can not used more than it.

Lxeon said:
seems it disable lowmemorykiller? i cant check it from FK kernel App and i want change it, **** OS with12g RAM still killng bg app
max its used 65% RAM, can not used more than it.
Click to expand...
Click to collapse
The lowmemorykiller daemon is no longer in the kernel. it’s handled from userspace on the op8 pro on android 10 OOS.
Unfortunately nothing I can do in the kernel to change this.
If apps are getting killed say thank you to OnePlus and OOS. Not related to the kernel.

Lxeon said:
seems it disable lowmemorykiller? i cant check it from FK kernel App and i want change it, **** OS with12g RAM still killng bg app
max its used 65% RAM, can not used more than it.
Click to expand...
Click to collapse
Try to disable zram/swap

cultofluna said:
Try to disable zram/swap
Click to expand...
Click to collapse
still around 65%
---------- Post added at 11:49 AM ---------- Previous post was at 11:49 AM ----------
Freak07 said:
The lowmemorykiller daemon is no longer in the kernel. it’s handled from userspace on the op8 pro on android 10 OOS.
Unfortunately nothing I can do in the kernel to change this.
If apps are getting killed say thank you to OnePlus and OOS. Not related to the kernel.
Click to expand...
Click to collapse
good hardware, suck software

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.
Spoiler: Documentation Control-Flow-Integrity (CFI) / Shadow Call Stacj (SCS)
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 13 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.231
- 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
- SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
- 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:
https://www.androidfilehost.com/?w=files&flid=326387
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
2.0.0 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86856077
2.0.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87005047
2.0.2 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87053951
2.0.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87244107
2.0.10 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87432111
2.0.12 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87641841
2.0.15 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87944971
Android 13
3.0.0 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-88195025
3.0.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-88326835
3.0.2 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-88632657
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

F.A.Q:
Question: Is root preserved when flashing this kernel?
Answer: Yes, the AnyKernel.zip will detect root and keep it.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img, vendor_boot.img as well as dtbo.img from matching firmware you are on and flash them via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom and re-root.
Question: Why is having Magisk installed mandatory for this kernel?
Answer: The kernel uses a ramdisk overlay to apply some settings after boot. If you are not rooted these settings will not get applied and you miss some of the optimizations.
Question: How to report bugs properly?
Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re running on a stock configuration. That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a .zip of /asdf.
Easiest way is immediately after booting up, with a root explorer navigate to /asdf. Copy the contents to your internal storage, zip it up and send it to me.
If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!

and this is mine too

justincase

last one I promise

Woah another kernel for sake ! Might give it a try later !

Update to 1.0.3
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.11.51.67. 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:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/UL-I006D-ASUS-30.11.51.67-1.1.25-user.zip
md5sum: 0f30d5e043f4a675e7db3250d5218125
More changes in the Changelog below:
Changelog:
- Import zenfone8_zs590ks.MR0.4-30.11.51.67 source code
- Linux-Stable Upstream to 5.4.128
- bump clang to latest prebuilt clang by google (12.0.7)
Download:
https://www.androidfilehost.com/?fid=14943124697586354960
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

Freak07 said:
Update to 1.0.3
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.11.51.67. 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:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/UL-I006D-ASUS-30.11.51.67-1.1.25-user.zip
md5sum: 0f30d5e043f4a675e7db3250d5218125
More changes in the Changelog below:
Changelog:
- Import zenfone8_zs590ks.MR0.4-30.11.51.67 source code
- Linux-Stable Upstream to 5.4.128
- bump clang to latest prebuilt clang by google (12.0.7)
Download:
https://www.androidfilehost.com/?fid=14943124697586354960
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
Click to expand...
Click to collapse
Hello. I tried this kernel recently. But now I want to return to the stock core. But when I flash boot.img and dtbo.img, the settings stop working for me. There are also no items in Quick Settings. What am I doing wrong?

a7lanov said:
Hello. I tried this kernel recently. But now I want to return to the stock core. But when I flash boot.img and dtbo.img, the settings stop working for me. There are also no items in Quick Settings. What am I doing wrong?
Click to expand...
Click to collapse
Soory, wrong post

a7lanov said:
Hello. I tried this kernel recently. But now I want to return to the stock core. But when I flash boot.img and dtbo.img, the settings stop working for me. There are also no items in Quick Settings. What am I doing wrong?
Click to expand...
Click to collapse
Hey,
I forgot to mention to restore vendor_boot.img as well.
Sorry for the inconvenience, I adjusted the OP and the FAQ already.
So to get back to stock, extract boot.img, vendor_boot.img and dtbo.img from the matching stock firmware.zip. make sure you extract from the same firmware you're currently running.
Then flash these via fastboot.
If it doesn't work afterwards your problem lies elsewhere.

Freak07 said:
Hey,
I forgot to mention to restore vendor_boot.img as well.
Sorry for the inconvenience, I adjusted the OP and the FAQ already.
So to get back to stock, extract boot.img, vendor_boot.img and dtbo.img from the matching stock firmware.zip. make sure you extract from the same firmware you're currently running.
Then flash these via fastboot.
If it doesn't work afterwards your problem lies elsewhere.
Click to expand...
Click to collapse
Thank you. Today I will also try to flash the vendor_boot.img

no updates?

I know IT clearly says 'Zenfone 8', but is there any chance this Kernel will work on the 'Zenfone 8 Flip', too? (ZS672KS)... Ty!

elchmartin said:
I know IT clearly says 'Zenfone 8', but is there any chance this Kernel will work on the 'Zenfone 8 Flip', too? (ZS672KS)... Ty!
Click to expand...
Click to collapse
unfortunately no. 8 flip uses a separate kernel.

Hi @Freak07 ,
Thanks a lot for your effort and time that you invested into developing this kernel.
However, as is the case with other custom kernels, I would like to know what kind of battery life benefits I can expect from using this kernel on my device?
Unlocking the bootloader on Asus phones right now means a bit more hassle with the updates, also rooting the phone means a bit more hassle with using some apps (safety net etc),so I would really like to know what are the benefits in terms of battery life.

Update to 1.1.8
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.11.51.83. 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:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/zenfone8_zs590ks.MR0.5-30.11.51.83.zip
md5sum: 0f30d5e043f4a675e7db3250d5218125
More changes in the Changelog below:
Changelog:
- Import zenfone8_zs590ks.MR0.5-30.11.51.83 source code
- Linux-Stable Upstream to 5.4.134
- bump clang to latest prebuilt clang by google
- Merge CAF (QCOM) upstream
- enable ddr cooling device
- raise lto inlining limit
- other improvements please take a look at github
Download:
https://www.androidfilehost.com/?fid=14943124697586372325
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

Freak07 said:
Update to 1.1.8
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.11.51.83. 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:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/zenfone8_zs590ks.MR0.5-30.11.51.83.zip
md5sum: 0f30d5e043f4a675e7db3250d5218125
More changes in the Changelog below:
Changelog:
- Import zenfone8_zs590ks.MR0.5-30.11.51.83 source code
- Linux-Stable Upstream to 5.4.134
- bump clang to latest prebuilt clang by google
- Merge CAF (QCOM) upstream
- enable ddr cooling device
- raise lto inlining limit
- other improvements please take a look at github
Download:
https://www.androidfilehost.com/?fid=14943124697586372325
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
Click to expand...
Click to collapse
Hi. Thanks. And I have a question. I noticed through the Kernel Adiutor that big and prime cpu do not sleep when there is no load, they work at low frequency (original kernel). Is this a hotplug problem? Should they not go to Offline? Do they sleep in your kernel?

a7lanov said:
Hi. Thanks. And I have a question. I noticed through the Kernel Adiutor that big and prime cpu do not sleep when there is no load, they work at low frequency (original kernel). Is this a hotplug problem? Should they not go to Offline? Do they sleep in your kernel?
Click to expand...
Click to collapse
That´s expected behaviour on the few last gens of QCOM SoCs. and you´re also fooled by the ui of the app.
if there are no tasks/work the clusters go into idle c-states, but kernel managers/monitors will show you the frequency that you described.
depeding which battery mode you chose in settings, minfreqs for the clusters will be higher or lower.
dynamic should be at 300mhz for little cluster, 710mhz for big cores and and 844mhz for the prime core.

Freak07
Thanks for clarifying

Freak07 said:
Update to 1.1.8
Click to expand...
Click to collapse
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?