[KERNEL] Jesse's Kernel for Galaxy S8 and S8+ (Exynos) - Samsung Galaxy S8 & S8+ Cross Device Development

Jesse's Kernel (I am not good at naming sth.)
for Galaxy S8 and S8+ (Exynos)
(G950F/FD/X/N) and (G955F/FD/X/N)
This kernel is designed to be SIMPLE and STABLE with improved performance and battery life.
Just flash and enjoy your phone. No additional setting required.
This kernel has 3 series,
Early-Testing: Contains latest changes, experimental features. This build will be released to testers only.
Stable: Changes, features in early-testing build will be picked into stable once they are confirmed to be stable.
Semi-Stock: For those who want maximum stability or ROM developers who want to integrate with their ROMs. This build is very similar to stock but it will have some useful changes like SELinux permissive, disabled security features, etc. This build will be released to public in low update frequency(usuallly based on stock kernel changes).
LICENSE:
Kernel sources:
GPL 2.0: https://www.gnu.org/licenses/gpl-2.0.html
Kernel binaries, patches to system, ramdisk modifications, etc.:
Code:
You can use, mirror, modify and/or integrate it/them with your own works, WITHOUT inform me, subject to the following conditions:
1. Credit MUST be given. (a possible form: thanks *** for ***)
2. Warranty is NOT provided. I am not responsible for any possible losses.
3. Authorization may be TERMINATED for selected person without prior notice under certain conditions (subject to my sole discretion).
4. Above conditions must be preserved. (You have the responsibilities to inform your users about these conditions. A possible way is to add "LICENSE: (link to this post)" to "thanks *** for ***")
Features:
STABLE: (Mainline)
Toolchain: Linaro GCC 7
Linux 4.4.79 (updated from 4.4.13)
Always SELinux Permissive (with fake SELinux Enforcing status.)
Kernel Security Features, Root Restrictions are DISABLED
Linux mainline random generator driver backported
Max frequency of big cores set to 2.5GHz
Other optimizations, backports for best performance and power efficiency
BFQ I/O scheduler
Versioning: VERSION x.x
Release Frequency: Regularly
SEMI-STOCK:
Toolchain: Linaro GCC 7
Linux 4.4.79 (updated from 4.4.13)
Always SELinux Permissive (with fake SELinux Enforcing status.)
Kernel Security Features, Root Restrictions are DISABLED
Versioning: RELEASE x
Release Frequency: Rare (only stock kernel updates and bug fixes)
NOTE: As of VERSION 0.3 and SEMI-STOCK RELEASE 6, AQG5 or newer bootloader is required.
Download:
STABLE:
VERSION 0.3: (Source Tag)
https://www.androidfilehost.com/?fid=673368273298975229
SEMI-STOCK:
RELEASE 6: (Source Tag)
https://www.androidfilehost.com/?fid=889764386195919462
NOTE:
1. Existing Bluetooth Pairs, Wi-Fi Passwords will be forgot when you flash this kernel for the first time.
2. You need to flash root package (Magisk or SuperSU) AFTER flash kernel if you want root access.
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
Get informed about news and updates:
Join Official Telegram Channel
AND/OR
Follow this project on XDA
XDA:DevDB Information
Jesse's Kernel for Galaxy S8 and S8+, Kernel for the Samsung Galaxy S8+
Contributors
jesec
Source Code: https://github.com/jesec/android_kernel_samsung_universal8895
Kernel Special Features:
Version Information
Status: Stable
Created 2017-05-08
Last Updated 2017-07-30

Changelog:
STABLE:
VERSION 0.3, July 29th:
Merge AQG5 kernel updates from Samsung
Merge Linux 4.4.79
Merge BFQ-v8r12
Backport latest F2FS
Switch to latest Linaro GCC 7 toolchain with processor specific tunes.
Use -Ofast optimization.
VERSION 0.2.2, June 26th:
Merge AQF7 kernel updates from Samsung
Merge Linux 4.4.74
VERSION 0.2.1, May 27th:
Merge AQE5 kernel updates from Samsung
Merge Linux 4.4.69
Update system patches
VERSION 0.2, May 19th:
Updated to Linux 4.4.68
Full F2FS file system support (with latest driver backported from Linux 4.12) is added.
Possible kernel panic (random reboots) addressed.
Possible battery life improvements for CPU frequency boosts.
BFQ is added and set as the default I/O scheduler.
VoLTE & VoWiFi problem fixed. (verified by testers)
NOTE: VoLTE logo may not be an accurate indicator of VoLTE support.
VERSION 0.1, May 11th:
Initial Release.
SEMI-STOCK:
RELEASE 6, July 29th:
Merge AQG5 kernel updates from Samsung
Merge Linux 4.4.79
Backport latest F2FS
Switch to latest Linaro GCC 7 toolchain with processor specific tunes.
Use -Ofast optimization.
RELEASE 5, June 26th:
Merge AQF7 kernel updates from Samsung
Merge Linux 4.4.74
RELEASE 4, May 27th:
Merge AQE5 kernel updates from Samsung
Merge Linux 4.4.69
Update system patches
RELEASE 3, May 19th:
Updated to Linux 4.4.68
Switched to GCC 8.X
Full F2FS file system support (with latest driver backported from Linux 4.12) is added.
Possible kernel panic (random reboots) addressed.
VoLTE & VoWiFi problem fixed. (verified by testers)
NOTE: VoLTE logo may not be an accurate indicator of VoLTE support.
RELEASE 2, May 11th:
Storage and CPU performance problems fixed.

Guides:
HOW-TO FLASH THIS KERNEL:
1. Make sure TWRP is installed. (https://forum.xda-developers.com/showpost.php?p=72004368&postcount=3)
2. Download the flashable zip from download section in OP.
3. Transfer the zip to your phone.
4. Go to "Install" menu of TWRP and flash the zip.
(for devs) HOW-TO PROPERLY INTEGRATE THIS KERNEL TO YOUR ROM:
1. Download the flashable zip from download section in OP.
2. Rename the downloaded zip to "jesse-kernel.zip".
3. Delete original boot.img of your ROM.
4. Place the zip to kernel (create if not exists) folder of your ROM.
Example Structure:
->META-INF
->->com
->->...
->system
->->app
->->priv-app
->->...
->kernel
->->jesse-kernel.zip
->...
5. Delete original kernel flashing lines from installation script (META-INF/com/google/android/updater-script) of your ROM.
tip: usually start with package_extract_file("boot.img" after "ui_print("Extracting boot image...");".
6. Add these lines to the installation script of your ROM:
Code:
ui_print("Installing Jesse's Kernel...");
package_extract_dir("kernel", "/tmp/kernel");
run_program("/sbin/busybox", "unzip", "/tmp/kernel/jesse-kernel.zip", "META-INF/com/google/android/*", "-d", "/tmp/kernel");
set_perm(0, 1000, 0755, "/tmp/kernel/META-INF/com/google/android/update-binary");
run_program("/tmp/kernel/META-INF/com/google/android/update-binary", "3", "1", "/tmp/kernel/jesse-kernel.zip");
ui_print("Jesse's Kernel Installed");
(for devs) Tips about kernel compile: (Note: NO technical support for such things. Inquires will be ignored.)
1. There is a kernel build script in my kernel. (build_kernel.sh)
2. Two variables must be specified before you can run it.
export $KERNEL_TOOLCHAIN=/path/to/your-toolchain/bin/toolchain-prefix-
export $KERNEL_DTBTOOL=/path/to/dtbtool/dtbhtoolExynos
3. If you are building for Galaxy S8 (dreamlte), run it with "bash build_kernel.sh dreamlte".
If you are building for Galaxy S8+ (dream2lte), run it with "bash build_kernel.sh dream2lte".
4. Default output dir is "../kernel_out". "dt.img" and "Image" will be generated.

That's what I'm talking about! Thank you!!

Thanks @jesec for this and twrp. Without u development would be so far behind
sent from the R.I.C.E powered V8+

Great work mate :fingers-crossed:

State-wide provider blackout the very second i flashed. No worries!

Thanks for your hard work. Great job as always.
Sent from my SM-G955F using Tapatalk

what is the difference between stock and semi stock?

GreyFox777 said:
what is the difference between stock and semi stock?
Click to expand...
Click to collapse
Got the same question.. I've installed it, but it doesn't seem to have any advanced governors, etc on board.
But still very nice to have the first kernel on!!!!!
Jesec, you're just great
Btw: does the name Jesse's kernel was chosen on purpose or just a mistake?

GreyFox777 said:
what is the difference between stock and semi stock?
Click to expand...
Click to collapse
This kernel look like a basic kernel update from 4.4.13 to 4.4.66

@jesec
Awesome, thanks a lot bro!

Thank you for the first custom kernel
Can we expect a permissive kernel for this device soon?

tiho5 said:
Thank you for the first custom kernel
Can we expect a permissive kernel for this device soon?
Click to expand...
Click to collapse
Per github commit, the big news here is that this kernel is permissive!
@jessec, you are totaly awesome:good:
Thank you for being here!
Update; appear kernel selinux is still enforcing

It is SELinux permissive. That enforcing is fake actually. (just let userspace think status change is successful)
Changelog: (May. 9th)
I fixed a bug of script. Now new build (May. 9th) should work fine on non-plus variants.

finally i can use ARISE completely. thx a lot

Great one. Many thanks. I will try and report.
Sent from my SM-G955F using Tapatalk

Feels good to see development here, used to love ur work on GS7.
One question, where can I get the Magisk Flashable? I got it when flashed the ROM but I cant flash the ROM over the kernel or I will lose the kernel

jesec said:
It is SELinux permissive. That enforcing is fake actually. (just let userspace think status change is successful)
Changelog: (May. 9th)
I fixed a bug of script. Now new build (May. 9th) should work fine on non-plus variants.
Click to expand...
Click to collapse
Great.
Thanks. That's what I've been waiting for.

metuskale said:
Feels good to see development here, used to love ur work on GS7.
One question, where can I get the Magisk Flashable? I got it when flashed the ROM but I cant flash the ROM over the kernel or I will lose the kernel
Click to expand...
Click to collapse
here it is:

Related

[64-bit][KERNEL][UBER-TC][15 Oct]Spirit.Kernel r3 [CAF]

[64-bit][KERNEL][UBER-TC][15 Oct]Spirit.Kernel r3 [CAF]
Spirit Kernel
This kernel works on all the latest roms available which require new kernel source.
Statutory Warning: This kernel is not a feature bloated kernel like other kernels available, if you like tons of govs/io and hotplugs all in one and if you like to blow up your device, then you are at the wrong spot. This kernel will be minimal and only necessary features will be added.
A while back my users requested me to make a kernel which supports new ROMs(as few of them fail to). So I have decided to make a kernel which contains essential features along with stability and smoothness.
I will update this regularly as I have time and will add new features and fixes as well.
If you have any feature requests, don't hesitate to post it here!! I will consider if I like it​
PLEASE READ
How to report a bug?
Include the following in your bug report:
The ROM you are currently using + a link to the ROM's thread
A log, preferably dmesgs or kmsgs (use Google to find out how to pull these from your device)
The version of SpiritKernel you use (=rx, e.g.r3)
Bug reports not meeting these requirements will be ignored.
NO BUG REPORTS ON EXPERIMENTAL BUILDS!​
Features
This Hybrid kernel contains features from great kernel devs with like faux,franco etc, optimized for tomato to make it work.Initially there are less features but I will add much more soon
[*]Based on the Latest CyanogenMod sources
[*]CAF Patches by Abhinav
[*]Governors: stock for now
[*]Hotplug: ThunderPlug 2.5
[*]KCAL Driver by savoca
[*]Powersuspend by faux123
[*]FRandom module
[*]Adreno Idler by arter97
[*]Advanced TCP Congestion
[*]Built using UBER TC
[*]LMK Optimizations
[*]Graphite flags
[*]ANY Kernel zip
[*]And other opts
[*]TCP: HTCP/HSTCP/HYBLA/VEGAS/SCALABLE/LP/VENO/YEAH/ILLINOIS/WESTWOOD
TO-Do List
New Govs and I/Os
GPU OC and UC
* Recommended app for tweaking the kernel: FauxControl,Kernel Auditor or TricksterMod
How DO I flash this?
Reboot to recovery.
Install zip from SD Card.
Choose the Spirit.Kernel-rx-tomato.zip
Install and Reboot.
Changelog:
Click Me
Downloads:
Basketbuild
Source:
Github(branch:cm-12.1-amss-1.0.2)
Wiki containing changelogs,settings and more
Credits goes to these SUPERHUMAN for Inspiration and support (In no specific order)
Varun Chitre
Abhinav Jhanwar
arter97
faux123
yank55lu
savoca
cyanogen
And my supporters
And more
XDA:DevDB Information
Spirit.Kernel for YU Yureka, Kernel for the YU Yureka
Contributors
DC07
Source Code: https://github.com/DC07/spirit_msm8916
Kernel Special Features: CAF,KCAL,ThunderPlug,Adreno Idler and much more
Version Information
Status: Stable
Created 2015-10-10
Last Updated 2015-10-15
Does it support miui
DC07 said:
and if you like to blow up your device
Last Updated 2015-10-10
Click to expand...
Click to collapse
What do you mean ?
Does a bloated kernel 'blows up' device ?
baratheon16 said:
What do you mean ?
Does a bloated kernel 'blows up' device ?
Click to expand...
Click to collapse
adding unnecessary features and modifying codes without knowing anything does.
for eg. adding 4-5 hotplugs (enabled by default) and all working at once does.
Regards
Update is live.
Changelog
Dynamic FSync
ThunderCharge Control from Varun Chitre
Added Darkness governor
-OFast flags for more opt
Arch Power
vegas tcp tweak
Removed wlan.ko which was accidentally added
For more check github.
Enjoy.
Update is live
======r3=====
What's new?:
* F2FS and NTFS Support
* SWAP Support
* Enable all CPU cores while boot for quick boot
* kill some logspam
Changelog:
a47e11c spirit: use all cores on-boot for faster bootup
184bd1a moar changes
addc11d spirit: rework build script and bump to r3
9d5f29e spirit: add changelog.sh
52fcf5b spirit: Add NTFS Support
031757e Revert "dts : use all cores on-boot for faster bootup"
19b2c34 spirit: enable swap
701bcef mm: page_io.c: remove write error messages for swap devices
db6f10b mm/zswap: NUMA aware allocation for zswap_dstmem
122a852 mm/zswap.c: remove unnecessary parentheses
a37407a mm/zswap: support multiple swap devices
fa8792d mm/zswap.c: update zsmalloc in comment to zbud
58374d9 mm/zswap.c: fix trivial typo and arrange indentation
b1a1ec6 mm/zswap.c: change params from hidden to ro
2d81f29 mm/zswap: refactor the get/put routines
a664710 vnswap: integrate vnswap from Samsung
0a12121 mm/zswap: bugfix: memory leak when invalidate and reclaim occur concurrently
431421d mm/zswap: avoid unnecessary page scanning
4eeb42b mm/zswap: bugfix: memory leak when re-swapon
9a8de22 mm/zswap: use postorder iteration when destroying rbtree
65a7d5a mm/zswap.c: get swapper address_space by using macro
8af692f dts : use all cores on-boot for faster bootup
10b0414 spirit: updates to build.sh
699223a tomato: Enable f2fs
7986854 arm64: Kill logspam
Download: https://basketbuild.com/filedl/devs?dev=DC07&dl=DC07/Spirit/tomato/Spirit.Kernel-r3-20151015.zip
=====r3=====
Enjoy.
can we flash this on stock yureka rom! cm 12.1??
rishivg said:
can we flash this on stock yureka rom! cm 12.1??
Click to expand...
Click to collapse
It won't work on stock COS.
It works on AOSP and CM based roms
does it work for yureka plus?
does it work in blisspop rom
adamnp2000 said:
does it work in blisspop rom
Click to expand...
Click to collapse
Yea... It does... I am using it right now with blisspop
kdhupar0 said:
does it work for yureka plus?
Click to expand...
Click to collapse
yes, it does
Can you give us a daily usage setting for the kernel, please?
fanatic75 said:
Can you give us a daily usage setting for the kernel, please?
Click to expand...
Click to collapse
Check op
Work with cm13 ?
Any update @DC07?
Sent from my AO5510 using Tapatalk
This kernel is good but yureka plus is too damn slow on darkness governer.. Have to keep it on performance.. Any settings for a balanced usage without lags and good battery backup??
Thanks for the kernel.. ??
Does it supports MIUI 7?
Pls add 2.0ghz oc
DC07 said:
It won't work on stock COS.
It works on AOSP and CM based roms
Click to expand...
Click to collapse
So not compatible with Stock CM12.1 rom
Correct

[XTREME-UX- KERNEL]- V4 -[UBERTC 6.2 - GCC 6.2.1] - N920 C/G/I/L/S/K-CD - GraceUX

About Xtreme Kernel for Samsung Galaxy Note 5
The main goal of this kernel is to target a niche group of people looking for a daily drive kernel for their devices,a solid stable kernel with extended battery life without sacrifying performances, a reliable kernel with the best smoother user experience possible and optimum power efficiency managment.
With those guidelines in mind,i am not going to re-invent the wheel,as samsung and linux devs already did a really great job on android linux kernel, but more a fine tuning on differents kernel's sections that has direct impact on battery life and performances,without affecting their dependencies and inter-dependencies wich may lead to unexpected behaviour (no blind cherry-picking or patch merging,but more reading linux documentation for better understanding)
The challenge was to match the best balanced profil design for performances/battery life with solid stability to bring a different user experience than stock one, wich is not battery friendly,especially on ux firmware, as most of users know its battery drain 'issue'.
Agrressive improvments has been done on this kernel, tracking every bit that can take up precious resources on your phone when you aren’t using it, and improved this even further by making more wise power serving while in use, resulting in a longer battery life wich can last more with extra time.
This kernel doesn't have bells and wisthles other kernels have,if you are looking for playing with voltage, frequencies and synapse so this kernel may not fit your needs and suits your habits,you still are completly free to use it or no,it's up to you.
Xtreme Kernel has been tested and working fine so far,so be more precise when reporting if you encounter any issue to pinpoint the problem for better diagnosis.(FYI kernel has been reported bug free from all testers).
I hope you will enjoy your experience with this kernel,it will get more improvments in futur regarding your feedbacks.
Enjoy !
Important Note:
- Call waiting issue is a known bug on official ux korean firmware,it's not kernel related so ask rom devs for fix or look for it on xda.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
- DISCLAIMER
I AM NOT RESPONSIBLE,NOR XDA, FOR ANY BRICK OR HARM THAT MAY OCCUR ON YOUR DEVICE,YOU ARE THE ONLY RESPONSIBLE OF USING ANY FLASHABLE FILES ON YOUR PHONE,BY FLASHING THIS KERNEL, I ASSUME THAT YOU AGREED TO THIS TERM AND YOU ARE DOING IT AT YOUR OWN RISK ! THINK TWICE BEFORE ENGAGING YOUR OWN RESPONSABILTY !
BUT SO FAR, THE KERNEL IS WORKING FINE ON MY SAMSUNG GALAXY NOTE 5 SM-N920C ,AND ALL BETA TESTERS ARE CONFIRMING VIA REPORTED FEEDBACKS THAT THIS KERNEL IS WORKING FINE TOO ON THEIR SAME DEVICE.RE-THINK AGAIN BEFORE FLASHING.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
- Xtreme-UX-KERNEL V4
* Kernel Features:
- Compiled with latest new optimzed UBERTC Toolchain 6.2 with Latest featured GCC 6.2.1
- Based on latest available AOSP kernel official korean open source code N920KKKU2CPJ4 (link below)
- Patched to Linux 3.10.104
- Note 7 Stock patched ramdisk based on N930FXXU1APGI (tweak and patch applied)
- Mount partition with noatime option.(reading accesses will no longer cause the atime information.Performance gains)
- SELinux set to Permissive
- Auto-Root included and updated to latest SU 2.79 (credits and thanks @Chainfire)
- Graphite enabled for high level memory optimizations
- Optimized Row I/O scheduler
- Deepsleep optimized with lot of improvments
- Tweaks for ram swappiness
- Westwood default algorithme as a Tcp congestion control strategie for better internet speed
- Optimized Interactive governor
- GPU enhancement for smooth experience and better rendering
- Better stability and reliability
- Improved Battery life
- BUG FREE (no random reboots,reboots,freeze,hangs,crashs,black screen at wakeup..etc)
++ more to come..
====================================================================================================
++Credits:
- Samsung and Linux for the Kernel Open Source Code
--- Samsung open source code link : http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=n920s
--- Linux kernel open source code link : https://www.kernel.org/
++Credits and Thanks for Elite Devs for their inspirationnal,heads up and for cherry-picking some of their commits on various git reposAndreiLux @halaszk @franciscofranco @Imoseyon @faux123 @dorimanx @djvoleur @googyanas @Chainfire for SuperUser @craigacgomez.......
++Credits to All Group friends/testers.( Special thanks to @carlitobahsoun @SoumyasishD )
If i unintentionnaly forgot someone,i'll be honored to add him ,just pm.
========================================================================================================================================================================================================
- Steps for flashing kernel:
I assume that you are already on a rooted device with TWRP 3.0.x.x installed,if not,useful posts on how to root and install twrp can be found on Xda,just do a search.
1 - enter recovery mode via twrp
2 - Wipe cache and Dalvick/ART cache ( important step or junk files will lead to internal conflicts like freeze lags or random reboots)
3 - Flash kernel and reboot,(it will bootloop once,just don't touch it and don't panic)
4 - After complete reboot,don't use the phone and let the kernel settle for 5 minutes for better hardware and firmware integration,if u use it while rebuilting cache and integrating,you may experience lags or freeze,so let it install comfortably before starting usage.
5 - after step 4 , you can use the kernel. A second reboot is advicable but not obligatory,it's up to you.
6- Enjoy Xtreme Kernel !
========================================================================================================================================================================================================
- Download
Link for Xtreme UX Kernel V4
XDA:DevDB Information
[XTREME-UX- KERNEL] - [UBERTC 6 - GCC 6] - NOTE 5 - SM-N920 C/G/I/L/S/K - GRACE-UX, Kernel for the Samsung Galaxy Note 5
Contributors
SpiritualWarrior
Source Code: https://www.androidfilehost.com/?fid=457095661767129755
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 4.0
Stable Release Date: 2017-01-15
Beta Release Date: 2017-01-15
Created 2016-06-11
Last Updated 2017-01-15
Changelog Xtreme Kernel V2
- Changelog:
- New Kernel Based on latest available open source code N920CXXS2BPE4 (link below)
- New Ramdisk merged and based on Samsung BPE4 source (stock patched)
- Compiled with latest new optimzed UBERTC Toolchain 6 with Latest featured GCC 6.x.x :good::good:
- Patched to latest Linux 3.10.102
- Auto-Root included and updated to latest SU 2.76 (credits and thanks @Chainfire)
- Mount partition with noatime option.(reading accesses will no longer cause the atime information.Performance gains)
- SELinux set to Enforcing ( see post 1 if you want to change to permissive)
- Graphite enabled for high level memory optimizations
- Optimized I/O schedulers for better tasks queue managment
- Deepsleep fixed and working fine - optimized triggers
- Various tweaks for ram swappiness
- Westwood default algorithme as a Tcp congestion control strategie for more internet speed
- Optimized Interactive governor for better clock speed scalling
- Optimized cpu freq scalling for better battery and responsivness
- Extended battery life
- Improved stability
- +++ More features to come
- BUG: Absolutely Bug free ( no freeze,no random reboots,no black screen,audio call on speaker working and both parts hearing..etc..)
- Version: V2
- Status: Very stable
- Tested and Working on N920 variants C/G/I ( for other variants please report if it works to be added to list )
-- Samsung source code (Credits: Samsung and Linux) : http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=n920c
++Credits for the respectable and talented elite real great devs for learning purpose, and for cherry-picking commits : @AndreiLux @arter97 @googy_anas @dorimanx @Chainfire for SuperUser @craigacgomez @djvoleur @Imoseyon @faux123
++Credits to All Group friends/testers.
If i unintentionnaly forgot someone,i'll be honored to add him ,just pm.
-- Source code @ Git repo: https://bitbucket.org/mus1711/xtreme-kernel-note-5-n920c-mm-tw-n920cxxs2bpe4
- DOWNLOAD LINK Xtreme Kernel V2 for MM-TW
Xtreme Kernel V2
Xtreme UX Kernel V3
- Xtreme-UX-KERNEL V3
* Kernel Features:
- Compiled with latest new optimzed UBERTC Toolchain 6 with Latest featured GCC 6.x.x
- Based on latest available AOSP kernel open source code A810SKSU1APJ1 (link below)
- Patched to Linux 3.10.103
- Note 7 Stock patched ramdisk based on N930FXXU1APGI (tweak and patch applied)
- Mount partition with noatime option.(reading accesses will no longer cause the atime information.Performance gains)
- SELinux set to Enforcing (steps bellow to change to permissive)
- Auto-Root included and updated to latest SU 2.78 (credits and thanks @Chainfire)
- Graphite enabled for high level memory optimizations
- Optimized I/O schedulers for better tasks queue managment
- Deepsleep working fine - optimized triggers
- Tweaks for ram swappiness
- Westwood default algorithme as a Tcp congestion control strategie for better internet speed
- Optimized Interactive governor for better clock speed scalling
- GPU enhancement for smooth experience and better rendering
- Optimized cpu freq scalling for better battery and responsivness
- No uci support ( i'm not a synapse fan,a battery saver profil can be a bit good for battery saving but catastrophic for playing games with hard cpus loads and vice versa ,better to let kernel manage everything,just sit back in the car like a boss to enjoy ride and let the driver manage driving hassles )
- Best Balanced profil optimized for best perfs/battery life
And much more...too long technicals features to be listed.
===================================================================================================
++Credits:
- Samsung and Linux for the Kernel Open Source Code
--- Samsung open source code link : http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=n920
--- Linux kernel open source code link : https://www.kernel.org/
++Credits for the respectable and talented elite real great devs for learning purpose and for cherry-picking commits especially @AndreiLux @arter97 @googy_anas @dorimanx @Chainfire for SuperUser @craigacgomez @djvoleur @Imoseyon...
++Credits to All Group friends/testers.
If i unintentionnaly forgot someone,i'll be honored to add him ,just pm.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
- Steps for flashing kernel:
I assume that you are already on a rooted device with TWRP 3.0.0.0 installed,if not,useful posts on how to root and install twrp can be found on Xda,just do a search.
1 - enter recovery mode via twrp
2 - Wipe cache and Dalvick/ART cache ( important step or junk files will lead to internal conflicts like freeze lags or random reboots)
3 - Flash kernel and reboot,(it will bootloop once,just don't touch it and don't panic)
4 - After complete reboot,don't use the phone and let the kernel settle for 5 minutes for better hardware and firmware integration,if u use it while rebuilting cache and integrating,you may experience lags or freeze,so let it install comfortably before starting usage.
5 - after step 4 , you can use the kernel. A second reboot is advicable but not obligatory,it's up to you.
6- Enjoy Xtreme Kernel !
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
- Permissive Mode
- How to set SE linux to Permissive permanently for Xtreme Kernel with SELinux Enforcing mode ?
1- You need to have 2 tools:
--- A root files explorer like Fx Explorer with root addon OR Root explorer ( I am using Fx explorer ,personal preference)
--- Universal init.d (to enable support), Download it from PlayStore
2- Once installed,enable it by switching to ON
3- With root access, Go to system/etc/init.d directory
4- Create a file and name it 08setperm
5- Open new created file and write these 2 lines:
#!/system/sh
setenforce 0
6- Save and close
7- Give full permissions (read,write,execute) to the file " 08setperm " like this "rwxrwxrwx" (use Fx Explorer or Root explorer to edit and change permissions)
8- Open Universal init.d and switch to ON and click on "08setperm" then click 'execute' on top (the play buttom).
9- Now Reboot your phone
10- Done! your SELinux mode is set to permissive permanetly.
To revert back to Enforcing, just switch to OFF Universal init.d enabler and reboot .
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
- Download Link :
++ Link for Xtreme-UX-Kernel V3 for Samsung Galaxy Note 5 SM-N920 C/G/I/S/L/K - GraceUX
- Xtreme-UX-Kernel_V3
-------------------------------------------------------------------------------------------------------------------------------------------------------------
XDA:DevDB Information
[XTREME-UX- KERNEL] - [UBERTC 6 - GCC 6] - NOTE 5 - SM-N920 C/G/I/L/S/K - GRACE-UX, Kernel for the Samsung Galaxy Note 5
Contributors
SpiritualWarrior, diegonnc, haifish9999
Source Code: https://drive.google.com/open?id=0ByEZRlb688olZWV2ak53a01yZW8
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.0
Stable Release Date: 2016-10-27
Beta Release Date: 2016-10-27
Created 2016-06-11
Last Updated 2016-11-13
Reserved
Nice one man , just here to officially welcome you , keep it up
Nice work .. I think the link doesn't work
Sent from my SM-N920C using XDA-Developers mobile app
samehfarahat said:
Nice work .. I think the link doesn't work
Sent from my SM-N920C using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks !
Link working fine
Edited : Downloaded .. thanks
NOW, this is really the best KERNEL of the PLANET !!! XTREME KERNEL ! Great and Welcome to XDA
Welcome and i love your kernel
congratulation
N920c/64g/tl68 v9 /googy kernel v1.4 /xposed greenify+amplify+powernap
is it ok if i flash this kernel over googy max ?? my devise is 920c dual sim
truenitos said:
NOW, this is really the best KERNEL of the PLANET !!! XTREME KERNEL ! Great and Welcome to XDA
Click to expand...
Click to collapse
Thanks mate !
themoto said:
Welcome and i love your kernel
Click to expand...
Click to collapse
Nice to see you here thank you
3mmar3d said:
is it ok if i flash this kernel over googy max ?? my devise is 920c dual sim
Click to expand...
Click to collapse
No..just follow flashing steps
Btw googymax is an excellent kernel from a talented dev
carlitobahsoun said:
congratulation
N920c/64g/tl68 v9 /googy kernel v1.4 /xposed greenify+amplify+powernap
Click to expand...
Click to collapse
Thanks dude
Links doesn't works. Any mirror?
rvlnic said:
Links doesn't works. Any mirror?
Click to expand...
Click to collapse
open link from web not from here tapatalk
Sent from my SM-T715 using Tapatalk
good to see you here
I just installed it. It's snappy and stable. Will report back later. Thank you for sharing your work.

[KERNEL] [OOS] SimpleGX v6.4 (August 13)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING :
This kernel is for Oneplus 5T (dumpling)
Code:
You will NOT void your warranty after flashing this kernel.
Be sure to make all necessary backups first before processing to installation.
I'am not responsible of any damage caused to your device or data lost after flashing this kernel.
Of course, these are only basic warnings ! but generally you'll not get any problem :)[/COLOR][/FONT]
Some reading..
Welcome to SimpleGX kernel ! a kernel that aims for simplicity, stability, better performance, smoothness and battery life over a pure stock kernel.
This kernel is designed for people who are (like me) bored to flash kernels which integrate tons of unneeded things.
Main goals of it is to stay MUCH closer to stock than every kernels shared here and almost not to be a “custom kernel” on its own. So beware, no exotic stuffs here !
No need for any third app or whatever to control this kernel. Just "flash-n-joy" ! this is how I always liked thing.
Keep in mind that this kernel has been designed for my daily use first.
As always, I'm enjoying sharing my contribution here on XDA for free, which taking me a lot of (my free) time to test before releasing. So, if you can offer me a little beer, it will be really appreciated!
This kernel must be only flashed over an official Oneplus 5T OxygenOS (OOS) ROM !
Feel free to include my kernel to your ROMs / threads but please don't forget to inform/ask first via PM and credit me properly in your original thread. It's always appreciated.
​
★ WHAT TO EXPECT ★ :​
(over a pure stock kernel) :
Slightly better battery life
Slightly better performance
Include only efficient (but definitely not experimental) tweaks
Stay as close as possible from pure stock source
★ FEATURES (up-to-date) ★ :​
Base :
Always directly based from latest available "android_kernel_oneplus_msm8998" Android Nougat/Oreo/Pie source from Oneplus5T OxygenOS (for clean work)
Compiled with stock Google (4.9.x / aarch64-linux-android) toolchain (for best stability)
Featuring AnyKernel3 (for all ramdisk compatibility)
Stock Linux
Main :
Kernel logger disabled
Very few fixes/optimizations patches for stock interactive governor
Completely optimized stock 'cfq' I/O scheduler
All TCP congestion control modules activated with Westwood currently as default
mmc/core: disabled CRC check
Disabled CC_OPTIMIZE_FOR_SIZE
tcp_output: set initial TCP window size to 64K
fs: default to noatime
Decrease BCL low battery threshold to 5%
WireGuard support (thanks to @zx2c4)
Xbox controller (and other USB pads) support
Dash Charge support
Removed verify and forced encryption + patched SafetyNet flags to pass CTS
Disabled suspicious OnePlus services and logging
Some miscellaneous tweaks, fixes, patches and security patches
Various tweaks :
Full changes to be discovered directly in my Github source below
Features that will NEVER be included in this kernel :
adding any other governor/IO schedulers than those stock
root/busybox auto-installation
CPU/GPU overclocking/undervolting
KCAL
adreno idler
state_notifier
any upstream of Linux kernel
dual-boot
etc
★ PREREQUISITE ★ :​
An unlocked Bootloader
An Android Nougat/Oreo/Pie firmware (based on OxygenOS)
A custom recovery (TWRP recommanded), to flash the kernel
Optional : to control some kernel tweaks, you can install Kernel Adiutor)
★ SOURCE (up-to-date) ★ :​
SimpleGX (normal version)
SimpleGX (ALS version)
★ INSTALLATION PROCEDURE ★ :​
Backup everything you need (internal & external)
Unlock your bootloader
Flash your favorite TWRP recovery
Reboot to TWRP
Wipe both cache & dalvik partitions
Flash your full usual ROM/firmware (optional if you did not flashed any other custom kernel)
Flash SimpleGX kernel
Flash root (Magisk recommended but should work with SuperSU also)
Reboot and enjoy !
★ Frequently Asked Questions (FAQ) ★ :​
How can I update my SimpleGX kernel version ?
- Nougat: Just make a dirty flash over it. If there is a special thing to do, then it will be precised directly into the announce.
- Oreo/Pie: flash kernel and root right after (otherwise your device won't boot).
How can I go back to stock kernel ?
Just flash back your full usual rom/firmware back (flashing stock kernel is not enough since it does not brings stock modules back to the rom/firmware).
Is there a LineageOS (LOS) version of you kernel ?
No, and there won’t be any this time on OP5T.
Is your Oreo/Pie version compatible with custom ROM's (8.1.x) ?
No, only official OOS Oreo/Pie.
My battery is draining like hell, what's wrong ?
As @nathanchance perfectly said for his kernel: "The kernel doesn't drain any battery, use an app like BetterBatteryStats to figure out what app is screwing with your phone".
Also, generally, I remarked that wiping cache+dalvik between updates may drain a lot for the percentage left and the first cycle. Anyway, be sure to make at least two full cycles (from 100% to 0%) before judging battery life for any kernel.
How to recover excellent battery life ?
Check my personal tips HERE.
★ for OnePlus 5T ★
/!\ PLEASE DO NOT MIRROR MY DOWNLOADS /!\​
Need supports ? all kind of questions must be posted on this thread directly. Be sure to read at least completely this first post before asking any question.
If you enjoy this kernel, don't forget to rate this thread
stars, and clicking the 'thanks' button (right below). It's always appreciated to keep this thread maintained ​
LIKE MY WORK ?
OFFER ME A
:good::highfive::good:​​
CHANGELOG
★ CHANGELOG ★ :​
13.08.2019 : v6.4 released.
Synchronize codes for OxygenOS 9.0.8 (Android Pie / 9)
26.07.2019 : v6.3 released.
Synchronize codes for OxygenOS 9.0.7 (Android Pie / 9)
Updated Anykernel3 to latest version
Updated WireGuard to latest version (20190702)
11.06.2019 : v6.2 released.
Synchronize codes for OxygenOS 9.0.6 (Android Pie / 9)
Upgrade from AnyKernel2 to AnyKernel3
Updated WireGuard to latest version (20190601)
22.05.2019 : v6.1 released.
Synchronize codes for OxygenOS 9.0.5 (Android Pie / 9)
Updated Anykernel2 to latest version
Updated WireGuard to latest version (20190406)
(slightly ) updated Google GCC 4.9 toolchain
06.01.2019 : v6.0 released.
Synchronize codes for OxygenOS 9.0.1 (Android Pie / 9)
Updated Google GCC 4.9 toolchain
Updated Anykernel2 to latest version
Updated WireGuard to latest version (20181218)
Reverted to built-in proprietary wifi module instead of opensource OOS drivers (not shared to public for now)
All modules are now internal (instead of external) (smaller kernel size)
Kernel logger is now disabled forever
25.10.2018 : v5.6 released.
Synchronize codes for OxygenOS 5.1.6
Updated WireGuard to latest version (20181018)
Updated Anykernel2 to latest version
Compiled with latest updated Google GCC 4.9 toolchain
23.08.2018 : v5.5 released.
Synchronize codes for OxygenOS 5.1.5
Updated WireGuard to latest version (20180809)
Updated Anykernel2 to latest version
28.07.2018 : v5.4 released.
Synchronize codes for OxygenOS 5.1.4
Updated WireGuard to latest version (20180718)
Updated Anykernel2 to latest version
ak2: add a warning to not forget to flash Magisk right after flashing kernel (in order to boot)
27.05.2018 : v5.3 released.
Synchronize codes for OxygenOS 5.1.2
Updated WireGuard to latest version (20180524)
Updated Anykernel2 to latest version
17.05.2018 : v5.2 released.
WiFi: migrated from OOS proprietary module to OOS opensource
Fixed (again) delayed notifications issue
Updated WireGuard to latest version (20180514)
Updated Anykernel2 to latest version
Compiled with latest updated Google GCC 4.9 toolchain
26.04.2018 : v5.1 released.
Synchronize codes for OxygenOS 5.1.1
Updated WiFi proprietary module from OOS 5.1.1
Updated WireGuard to latest version (20180420)
Important note: due to added wifi proprietary module, it is highly recommanded to be flashed only on OOS 5.1.1 (please do not complain if wifi is not working if you are on any another OOS version from this). It is also recommanded to flash full stock OOS firmware before flashing kernel and finish by Magisk (otherwise you may face infinite boot at oneplus logo).
19.04.2018 : v5.0 released.
Directly based from latest available 5.1.0 Oreo (8.1) OOS kernel source from OnePlus
Updated WiFi proprietary module from OOS 5.1.0
Updated simplegx_defconfig to match latest 5.1.0 OOS needs
Updated WireGuard to latest version (20180413)
Removed fixed notifications delay tips from joshuous (useless on 8.1)
Important note: due to added wifi proprietary module, it is highly recommanded to be flashed only on OOS 5.1.0 (please do not complain if wifi is not working if you are on any another OOS version from this). It is also recommanded to flash full stock OOS firmware before flashing kernel and finish by Magisk (otherwise you may face infinite boot at oneplus logo).
Previous releases changelog...
08.04.2018 : v4.2 (ALS) updated.
Linux-stable updated to 4.4.127
Updated Anykernel2 to latest version
Compiled with latest updated Google GCC 4.9 toolchain
04.03.2018 : v4.2 (ALS) updated.
Linux-stable updated to 4.4.120
02.03.2018 : v4.2 (ALS) released.
Introducing ALS (Android Linux Stable) version (same as original v4.2 with linux-stable merged in) - big thanks to @nathanchance
Linux-stable updated to 4.4.119
28.02.2018 : v4.2 released.
Synchronize codes for OxygenOS 5.0.4
Update WiFi proprietary module from OOS 5.0.4
Updated WireGuard to latest version (20180218)
Updated Anykernel2 to latest version
13.02.2018 : v4.1 released.
Fixed notifications delay (credits @joshuous)
Disabled suspicious OnePlus services and logging (credits @joshuous)
07.02.2018 : v4.0 released.
Directly based from latest available 5.0.3 Oreo OOS kernel source from OnePlus.
Compiled with latest updated Google GCC 4.9 toolchain
Updated Anykernel2 to match latest version available
Exact same features from Nougat version excepted the following:
- Updated WiFi proprietary module from OOS 5.0.3
- Stock Oreo defconfig merged with SimpleGX needs
My github will now feat 2 branchs for both respective Nougat and Oreo versions.
Nougat versions will always now be 3.xx and Oreo 4.xx.
Important note: due to added wifi proprietary module, it is highly recommanded to be flashed only on OOS 5.0.3 (please do not complain if wifi is not working if you are on any another OOS version from this). It is also recommanded to flash full stock OOS firmware before flashing kernel and finish by Magisk (otherwise you may face infinite boot at oneplus logo).
19.01.2018 : v3.2 released.
Fixed a little mistake from myself from v3.1 about trying to update WireGuard (thanks to @nathanchance & @zx2c4 for their precious helps)
Updated Anykernel2 to match latest version available
18.01.2018 : v3.1 released.
Updated WireGuard to match latest version available
Updated Anykernel2 to match latest version available
Update build script
16.01.2018 : v3.0 released.
Updated Anykernel2 to match latest version available
Kernel completely rebuilded from zero (again)
Removed all added arm64, cpuidle, etc commits. This version is now even more close from stock than ever (check github for changes or first post for actual features)
Also removed the following:
- Wakelocks control support
- MAPLE I/O scheduler added (and set as default)
- Very few compilation optimizations
10.01.2018 : v2.4 released.
Added some new arm64 patches
Updated Anykernel2 to match latest version available
04.01.2018 : v2.3 released.
Enable back stock Adaptive LowMemoryKiller
03.01.2018 : v2.2 released.
Add some new optimizations/fixes interesting commits (check github for changes)
01.01.2018 : v2.1 released.
Add WireGuard support
31.12.2017 : v2.0 released.
Kernel completely rebuilded from scratch (cleaner github separate commits also)
Completely thinked and reworked from zero (many commits removed, to keep only efficient ones and be more close to stock than ever)
Add some new optimizations/fixes interesting commits (arm64, cpuidle, etc)
Synchronize codes for OxygenOS 4.7.6
Updated Anykernel2 to match latest version available
Removed franciscofranco wakelocks implementation to move up to Boeffla one (only safe wakelocks are now blocked by default)
Removed old github wifi OP5 OOS implementation to now include stock proprietary OOS OP5T wifi module, and load it correctly
Switch back to stock 'O2' optimizations (instead of 'Ofast')
13.12.2017 : v1.7 released.
Revert "sched: Disable gentle fair sleepers"
DTS: Decrease BCL low battery threshold to 5%
11.12.2017 : v1.6 released.
Makefile: enable 'Ofast' optimizations
sched: Disable gentle fair sleepers
Updated Anykernel2 to match latest version available
Compiled with latest updated Google GCC 4.9 toolchain
08.12.2017 : v1.5 released.
Synchronize codes for OxygenOS 4.7.4
01.12.2017 : v1.4 released.
defconfig: Disable SEEMP support
Revert "Correctly unregister usb_psy"
Revert "kgsl: convert some workqueues to use kthreads"
Revert "kgsl: Increase priority of RT thread"
29.11.2017 : v1.3 released.
Correctly unregister usb_psy
Updated Anykernel2 to match latest version available
Revert "cpufreq: interactive: fix to come out of hysteresis mode"
Remove (broken) USB Fast Charge implenetation, for now
27.11.2017 : v1.2 released.
kgsl: Increase priority of RT thread
kgsl: convert some workqueues to use kthreads
cpufreq: interactive: fix to come out of hysteresis mode (ported from OP5 to OP5T by me)
power: qpnp-fg-gen3: queue work on system_power_efficient_wq (ported from OP5 to OP5T by me)
kernel version: add android codename version (as a future Oreo build will be made, it will be easier to discern kernel versions in infos)
25.11.2017 : v1.1 released.
Fixed brightness problem which wasn't really going to 100% (but was stuck at 30% approx).
Removed backlight dimmer useless option
25.11.2017 : v1.0 released.
Initial release (check actual features)
Thanks & greetings
★ THANKS & GREETINGS ★ :​
(by alphabetic order)
Lord Boeffla
osm0sis
. . . and of course to all talented devs credited in my commits!
DONATIONS
★ DONATIONS ★ :​
Many thanks @morback :good:
Many thanks Henry P. :good:
Many thanks @marko94 :good:
Many thanks @kgs1992 :good:
Many thanks @MrPepperino :good:
Many thanks @xrelic7 :good:
Many thanks @Robustuck :good:
Thank you to support my work ! :highfive:
RESERVED
Reserved.
Thanks will try it once the phone arrives. Love to see development starting
Thanks for this, I always prefer the near-stock experience with some much-needed tweaks. Flashed it on 4.7.2, boots fine, looks very smooth for now!
Keep up the good work!
Welcome to the party sir..! Look forward to your subtle and simple kernels builds..!
Welcome :highfive: i am happy to say that the most stable kernel was yours (op5) and great battery life thanx
Nice to see a new Kernel.
Thanks for your hard work!
Did you include any additional wake-up gestures?
Bug so far: Wifi disabled
Fixed
Not sure if I'm the only one or not, but it seems that I'm no longer able to adjust the brightness after installing your kernel. Other then that, everything else looks to be running pretty good.
xocomaox said:
Did you include any additional wake-up gestures?
Click to expand...
Click to collapse
Nope, sorry. I would like to stay as stock as possible, I prefer to let this kind of functions to real custom kernels
DocRambone said:
Bug so far: Wifi disabled
Click to expand...
Click to collapse
Strange, no problem of WiFi here, just tried to turn ON and connect to my home wifi and connected with success, internet test = OK :good:
Do you directly comes from another kernel ? (I would say blu_spark since we are only 2 for now on OP5T). I recommand you to revert back to stock kernel before flashing mine, and then re-test.
thephoenixvampire said:
Not sure if I'm the only one or not, but it seems that I'm no longer able to adjust the brightness after installing your kernel. Other then that, everything else looks to be running pretty good.
Click to expand...
Click to collapse
No problem also, just tried to slide from min to max and all is fine (progressive), tried with automatic brightness ON and OFF. Same as above, can you try to flash stock kernel/firmware back and then flash my kernel ? :highfive:
AndroidGX said:
Strange, no problem of WiFi here, just tried to turn ON and connect to my home wifi and connected with success, internet test = OK :good:
Do you directly comes from another kernel ? (I would say blu_spark since we are only 2 for now on OP5T). I recommand you to revert back to stock kernel before flashing mine, and then re-test.
Click to expand...
Click to collapse
Yes, restored stock kernel and installed yours after an reboot fixed the bug
Tried to flash this kernel over oos and freedom room and keep getting error 1. What am I doing wrong?
NickMidd91 said:
Tried to flash this kernel over oos and freedom room and keep getting error 1. What am I doing wrong?
Click to expand...
Click to collapse
Probably a bad download, check MD5 to be sure that it corresponds before flashing :good:
AndroidGX said:
Nope, sorry. I would like to stay as stock as possible, I prefer to let this kind of functions to real custom kernels
Strange, no problem of WiFi here, just tried to turn ON and connect to my home wifi and connected with success, internet test = OK :good:
Do you directly comes from another kernel ? (I would say blu_spark since we are only 2 for now on OP5T). I recommand you to revert back to stock kernel before flashing mine, and then re-test.
No problem also, just tried to slide from min to max and all is fine (progressive), tried with automatic brightness ON and OFF. Same as above, can you try to flash stock kernel/firmware back and then flash my kernel ? :highfive:
Click to expand...
Click to collapse
Your kernel was installed within 20 minutes of pulling my op5t out of the box, unlocking, and installing TWRP. I'll go ahead and do another full wipe/data format, see how that goes.
AndroidGX said:
Probably a bad download, check MD5 to be sure that it corresponds before flashing :good:
Click to expand...
Click to collapse
I tried it twice man and I'm flashing it on twrp like I would have on the op5 but only on the op5t. I even downloaded it twice.
Up and running smoothly. Great work!
Edit: No Wifi issues, but I have noticed that the brightness is the same from 25-100% and does not change.

[NOV 15][Kernel] HTML5 Kernel

HTML5 KERNEL​
"Low overhead, light and the way of the future" - sultanxda
(he wasn't referring to this but whatever)​
This Kernel aims to be as simple as possible with only useful added features, you may request for features and we will consider them.
Features:
Compiled with GCC (cuz clang sucks)
Removed unnecessary bloat
Reduced power consumption
Improved zRAM and memory management
Upstreamed to the latest Linux 4.9 stable (based off ALS)
First kernel with touchscreen in TWRP fixed
Some cool patches
A lot of less cool patches
Magisk support
Westwood+ is now the default tcp algorithm
Brickported Backported patches from Sony, CAF and others
refer to the source for the rest I am lazy
TLDR:
It's better than stock and the best custom kernel out there (arguable)
Links:
Downloads
Telegram group
note: the zip is a flashable anykernel zip.
XDA:DevDB Information
HTML5 Kernel, Kernel for the Google Pixel 3
Contributors
ab123321, _LLJY
Source Code: https://github.com/bluecross-dev/kernel_msm-4.9
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 210
Stable Release Date: 2019-11-15
Created 2019-05-17
Last Updated 2019-11-15
HTML5 kernel v137
TL;DR: Download
Join our Telegram group if you want more frequent kernel updates
Yet another stable update! (that I did not even test)
This build is the final release supporting Android 9.0 Pie, next versions are going to support Android Q exclusively.
Brief changelog:
Merged Q beta 4 tag (also supposedly fixes rare live photo crash)
Updated to Linux 4.9.181
Various scheduler and cpuidle updates
Further vmalloc enhancements
Other minor changes
does this work on the Q beta?
Agree, this is the best kennel
Still no luck in running this kernel on stock Android 10 (blueline-qp1a.191005.007-factory-c36610c6). Version HTML5_137 brings bootloop (fastboot tells "error boot prepare" message).
NEW MAJOR UPDATE: v210
Now, with Android 10 support! A lot of work has been done since the last update, ehehh... yes, we still exist
I suck at coming up with huge placebo changelogs, so just believe me at that statement
Follow the link and flash dis new build right away (if you still haven't lost your patience): Download
Will this work on havoc os 3.0?
crankiro97 said:
Will this work on havoc os 3.0?
Click to expand...
Click to collapse
It should if it is Android 10
ab123321 said:
It should if it is Android 10
Click to expand...
Click to collapse
Ok, since TWRP is not working in A10, how do you install it?
crankiro97 said:
Ok, since TWRP is not working in A10, how do you install it?
Click to expand...
Click to collapse
Flash through FKM or EXKM.
xFirefly93 said:
Flash through FKM or EXKM.
Click to expand...
Click to collapse
Thanks, that worked. Flashed it with FKM.

Development [Kernel][01.06.2023][Android 13] Kirisakura 2.0.24_T for Asus Zenfone 9 aka "DaVinci"

Kirisakura-Kernel for the Asus Zenfone 9
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Asus Zenfone 9 aka DaVinci. The Zenfone line-up internal codenames were traditionally derived from alcoholic drinks. Two years ago the Zenfone 6 bore the title "Kirin". The Zenfone 7 was codenamed "Tequila", while the Zenfone 8 bore the title "Sake".
This year seems to make a change however. The Zenfone 9´s internal codename is "DaVinci".
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
As far as we, @tbalden and me, are aware and as far as we know this project, alongside CleanSlate kernel for the Zenfone 9, marks the first release of a source compiled custom QGKI 2.0 kernel as a standalone flashable zip and project here on XDA.
The introduction of GKI and QCOMs adaptation QGKI means unfortunately that building a monolithic kernel becomes harder and harder. This results in the "kernel" itself no longer just sitting in one partition or the zImage, but it´s spread across different partitions (no longer being monolithic) now. Since there´s no requirment to keep monolithic builds working as in the past, it´s no longer possible to compile the source as is (without applying major rewrites, tricks or hacks) in the monolithic fashion on 5.10 kernels. The same was true for the Pixel 6/Pro.
That means the "kernel" project you´re seeing here needs to be compiled in a build environment to achieve the GKI/QGKI way. Since only Google releases the full build environment alongside the kernel sources itself in a proper fashion with git history, it became very complicated and seemingly impossible to do this on the Zenfone 9 at first glance. A big thanks at this place to Asus. From all the sources of SD8 Gen 1 QGKI devices published, the Asus Source is the most complete. A big thanks to Asus for publishing the sources on time and complete! Also for listening to us if the source is not complete and something is missing.
With excellent teamwork and a lot of hardwork, @tbalden and me managed to compile the Zenfone 9 kernel in QGKI 2.0 fashion after a lot of failed attempts and misery. It´s been a pleasure to work with him over the years here on XDA.
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. Starting with 5.4 kernel ( SD 888 ) CFI and SCS were 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 QCOM-Upstream. CLO-git is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 8+ Gen1 that´s built into the different SKUs of the Zenfone 9.
The kernel-bases available on QCOMs git, 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 16.0.2 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 5.10.181
- upstreamed QCOM base for the Snapdragon SD8+ Gen1 (qcoms internal codename "cape")
- Lazy RCU which should result in power-savings while the device is lightly-loaded or idling, more information here
- include important fixes/improvements from kernel/common
- SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
- implement ramoops for easier logs in case of kernel panics
- implement LRNG (see arter kernel OP for more info )
- Flashing the kernel will keep root!
- Flashable via EXKM, FKM or Kernel Flasher (free open source solution, get it here)
- 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
CPU related features:
- Power saving workingqueues enabled by default
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to use power efficient workingqueues. This compliments EAS in general
- vdso32 patches as found on Google Pixel devices (brief documentation here) (CAF 5.10 default, keep for documentation)
- improve suspend/resume from audio driver (caf-upstream for audio-kernel)
- enable suspend_skip_sync to save power during suspend/resume
- speed up face unlock
- reduce camera launch time
GPU related features:
- GPU driver updated to latest CAF-State
File System related features:
- f2fs improvements
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 9 Forums on XDA. Please consider buying the premium versions if you enjoy using the CleanSlate features, to give a little something back to @tbalden.
- add option to force 240hz touch sample rate
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
- Enable support for TTL spoofing
Memory related features:
- Speculative Page Faults left enabled (1. 2) (CAF 5.4 default, keep for documentation)
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)
Other features:
- clean up asus drivers and fix a few warnings in kernel log
- 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, vendor_dlkm.img and dtbo.img so you can go back to stock conditions (simplest way is TWRP or to extract from stock firmware via payload extractor)
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 9 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 in your favorite kernel app (I personally use Kernel Flasher by @capntrips as it´s free OSS) or TWRP once available.
3. Reboot and profit.
DOWNLOAD:
Download is located always in this folder:
AFH is currently down. Please check release posts for attached files.
https://www.androidfilehost.com/?w=files&flid=335947
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 12
1.0.0 Initial Release
1.1.0 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-87544785
1.1.0 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-87641829
1.1.3 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-87761015
Android 13
2.0.0
[Kernel][09.12.2022][Android 13] Kirisakura 2.0.0_T for Asus Zenfone 9 aka "DaVinci"
Kirisakura-Kernel for the Asus Zenfone 9 Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Asus Zenfone 9 aka DaVinci. The Zenfone line-up internal codenames were traditionally derived from alcoholic drinks. Two years ago...
forum.xda-developers.com
2.0.6 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-87945357
2.0.12 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88194923
2.0.18 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88332217
2.0.19 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88360955
2.0.21 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88384057
2.0.24 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88600875
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! This device is absolutely stunning!
@osm0sis for all his work, including the ak3 installer!
@capntrips for his relentless work on several projects, including kernel flasher!
@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_DaVinci_AI2202/
For necessary changes to other repos, besides the main kernel tree please check tbaldens github, we did the bringup together:
tbalden - Repositories
engineer. Started github with kernel for HTCDoubleshot, migrating version in 2011. kernel follows kernel, patching intuitive new features into CleanSlate line. - tbalden
github.com
F.A.Q:
Question: How do I return back to stock?
Answer: Extract boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img from the matching factory image provided on googles download page.
If you want to stay rooted make sure to flash a boot.img that has been patched with magisk.
Flash those images via fastboot/fastbootd and you will be back on stock kernel.
boot.img, dtbo.img and vendor_boot.img are to be flashed in regular fastboot.
vendor_dlkm.img is to be flashed in fastbootd (you can get to this with "fastboot reboot fastboot" when you´re in regular fastboot)
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?
Please make sure to meet the points described above, provide logs as detailed in the link above, otherwise debugging is a lot more time consuming and harder. If these requirements aren´t met and I don´t find time to either reproduce the issue myself or I´m not able to reproduce the issue myself reports might just be ignored. 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.
Question: What about unlocking, rooting, passing safetynet, apps detecting root/modifications and other topics that are vaguely related, but not really subject of this thread?
Answer: If you want to modify your phone via root/magisk in any way you need to unlock the bootloader. Unlocking will result in safetynet not passing. This has nothing to do with the kernel. At the moment of writing this, safetynet not passing can be worked around with a magisk module called "Universal SafetyNet Fix".
Not passing safetynet is unrelated to the kernel since hardware attestation is enforced on nearly all newly released devices now.
If you´re not passing safetynet banking apps might for example be detecting root. There are various tricks to hide root/modifications to the phone from banking apps or others but that´s not really subject of this thread.
taken from pixel 6 soon to be adjusted
AOSP Build Environment and Standalone Kernel builds (monolithic builds)
I´m sure some of you followed the movement towards the Generic Kernel Image (GKI) and Qcoms adaption to it called QGKI.
You can find more information about GKI following this link.
What does that mean for custom kernels and this custom kernel?
The last few years the kernel on android devices was more or less compiled as a monolith. That means the kernel is in the zImage with all (most) drivers compiled inline.
However with GKI this changed. There´s the base kernel image while vendor/device specific drivers are compiled as dynamically loadable kernel modules.
On last years devices like the Pixel 5 (using a 4.19 kernel) and this years devices with SD888 on a 5.4 kernel base, there was the possibility to change the QGKI kernel back into a monolithic kernel image. (building the drivers that are on stock kernel external modules back into the zImage to end with a monolithic kernel)
On the Pixel 6 I wasn´t able to achieve this yet. But during my tries I also wondered if maybe finally the time has come to follow suit, instead of trying to enforce old ways, when there´s a new way going forward.
What does that mean. This means that at this point the kernel is shipped as images that are to be flashed via fastboot. At a later stage I´m sure we can modify anykernel3 to allow flashing zips again, but at this early stage fastboot flashable images will be provided.
Those images can be flashed the same way the device is rooted, therefore I think everybody should be able to flash it easily since the device can´t be rooted any other way.
The kernel was compiled using the aosp kernel build environment. Information about it can be found on the documentation page from google.
this one too
and this one as well
Woohoo! Rock'n'roll! ^__^
Update to 1.1.0
Hey guys and girls,
Here´s the next update. It includes quite a few changes.
It also includes the few kernel changes from the latest firmware 32.2040.2040.23.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- Linux-Stable upstream bumped to 5.10.146
- merge latest CAF-Upstream
- bump clang to prebuilt 14.0.7 from google
- fixed clang warnings in the process
- other improvements and tweaks please check github
Download:
AFH is currently not working properly. Please check this post for the download. Kernel.zip is attached.
https://www.androidfilehost.com/?w=files&flid=335947
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.0
Hey guys and girls,
Here´s the next update. It includes quite a few changes.
It also includes the few kernel changes from the latest firmware 32.2040.2040.23.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- Linux-Stable upstream bumped to 5.10.146
- merge latest CAF-Upstream
- bump clang to prebuilt 14.0.7 from google
- fixed clang warnings in the process
- other improvements and tweaks please check github
Download:
AFH is currently not working properly. Please check this post for the download. Kernel.zip is attached.
https://www.androidfilehost.com/?w=files&flid=335947
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 sir,
How do you compile the original Kernel? Is any of vendor_boot or vendor_dlkm images the same as original stock or both are different? What about DTBO? I'm trying to build kernel for ROG Phone 6 but I thought kernal was still a monolithic file, so I flashed one only and failed to boot. ROG Phone 6 includes a script that apparently compiles everything but I don't which one is DTBO, vendor boot and vendor dlkm. Where and how you compile this kernel and where does the output go? For example I see kernel-platform/msm-kernel as the one you modified? That one is the vendor_boot?
Thank you for your help
And by the way, any plan for Kirisakura for ROG Phone 6?
Update to 1.1.1
Hey guys and girls,
Here´s the next update. It includes quite a few changes.
It also includes the few kernel changes from the latest firmware 32.2050.2050.29.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- included few changes from firmware 32.2050.2050.29
- other improvements and tweaks please check github
Download:
https://www.androidfilehost.com/?w=files&flid=335947
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
Lossani said:
Hello sir,
How do you compile the original Kernel? Is any of vendor_boot or vendor_dlkm images the same as original stock or both are different? What about DTBO? I'm trying to build kernel for ROG Phone 6 but I thought kernal was still a monolithic file, so I flashed one only and failed to boot. ROG Phone 6 includes a script that apparently compiles everything but I don't which one is DTBO, vendor boot and vendor dlkm. Where and how you compile this kernel and where does the output go? For example I see kernel-platform/msm-kernel as the one you modified? That one is the vendor_boot?
Thank you for your help
And by the way, any plan for Kirisakura for ROG Phone 6?
Click to expand...
Click to collapse
boot.img contains the zImage, vendor_boot contains first stage kernel modules, vendor_dlkm contains second stage kernel modules.
Kernel is no longer monolithic by default. I´m using the build environment to get the relevant images for GKI.
Freak07 said:
boot.img contains the zImage, vendor_boot contains first stage kernel modules, vendor_dlkm contains second stage kernel modules.
Kernel is no longer monolithic by default. I´m using the build environment to get the relevant images for GKI.
Click to expand...
Click to collapse
Do you have any kind of tutorial to follow to pack the kernel like you do in AnyKernel zip?
Thank you
Lossani said:
Do you have any kind of tutorial to follow to pack the kernel like you do in AnyKernel zip?
Thank you
Click to expand...
Click to collapse
I´m sorry but a step by step tutorial I don´t have the time to type that all down.
Please check tbaldens github for ZF9. We did the "bringup" of the ZF9 GKI environment together.
That here contains the scripts/methods we basically use both.
GitHub - tbalden/android_kernel_asus_zf9_build_env
Contribute to tbalden/android_kernel_asus_zf9_build_env development by creating an account on GitHub.
github.com
Check all the other zf9 repos as well.
We took basically the asus build script inside the ROG 6 source, readjusted it for the ZF9 source, as the build environment for the ROG 6 was more complete than ZF9.
You either need to remove avb from fstab (that lands in vendor_boot) or disable vbmeta flags for verity/verfication before you can flash any modified vendor_dlkm.
Be aware, disabling the flags triggers an inevitable wipe.
Otherwise check the scripts and work yourself through all the repos.
Unfortunately with GKI kernels you need to adjust the ABI. Now it gets complicated. The gki kernel, the zImage is usually compiled, from the common repo, while the qcom specific drivers are built in the msm repo. Since I don´t care about preserving googles abi for the GKI kernel, I compile the zImage from the updated msm repo, as well as the qcom modules.
That means in my build environment common repo is a symlink of msm repo, while I compile with the same script found in ROG 6 source. I think once you start working through the build environment you´ll understand. Tbalden doesn´t need to do that, as his kernel is close to stock with only a few mild changes, so easier to keep abi in check.
Unfortunately at the moment there´s no easy way to compile it.
Freak07 said:
I´m sorry but a step by step tutorial I don´t have the time to type that all down.
Please check tbaldens github for ZF9. We did the "bringup" of the ZF9 GKI environment together.
That here contains the scripts we basically use both.
GitHub - tbalden/android_kernel_asus_zf9_build_env
Contribute to tbalden/android_kernel_asus_zf9_build_env development by creating an account on GitHub.
github.com
Check all the other zf9 repos as well.
We took basically the asus build script inside the ROG 6 source, readjusted it for the ZF9 source, as the build environment for the ROG 6 was more complete than ZF9.
You either need to remove avb from fstab (that lands in vendor_boot) or disable vbmeta flags for verity/verfication before you can modify vendor_dlkm.
Otherwise check the scripts and work yourself through all the repos.
Unfortunately with GKI kernels you need to adjust the ABI. Now it gets complicated. The gki kernel, the zImage is usually compiled, from the common repo, while the qcom specific drivers are built in the msm repo. Since I don´t care about preserving googles abi for the GKI kernel, I compile the zImage from the updated msm repo, as well as the qcom modules.
That means in my build environment common repo is a symlink of msm repo, while I compile with the same script found in ROG 6 source. I think once you start working through the build environment you´ll understand. Tbalden doesn´t need to do that, as his kernel is close to stock with only a few mild changes, so easier to keep abi in check.
Unfortunately at the moment there´s no easy way to compile it.
Click to expand...
Click to collapse
Thank you for your reply. I succeded to compile using ROG 6 script but I end up with a vendor_dlkm.img in out/target/platform/taro and in gki folder "dist" outputs Image, vendor_boot.img and another vendor_dlkm.img + dtbo.img but doesn't seem to be the correct size, I guess there's another step missing to compile or I don't know which one of the dlkm is the correct one or if I need another step to make the Image file and vendor_boot.img.
Thank you anyways
Lossani said:
Thank you for your reply. I succeded to compile using ROG 6 script but I end up with a vendor_dlkm.img in out/target/platform/taro and in gki folder "dist" outputs Image, vendor_boot.img and another vendor_dlkm.img + dtbo.img but doesn't seem to be the correct size, I guess there's another step missing to compile or I don't know which one of the dlkm is the correct one or if I need another step to make the Image file and vendor_boot.img.
Thank you anyways
Click to expand...
Click to collapse
check the scripts I just sent you. the vendor_dlkm and vendor_boot from the environment don´t work on the device.
The thing is, asus just uses the kernel environment to precompile zImage,all the modules, dtb and dtbo, then transfer those to their complete build environment and those get includes into the images that end up in the firmware. The zImage they´re using on the device is actually not the one compiled in the build environment, but the GKI kernel uploaded by google. That´s why abi is so important. You´re not supposed to flash the ones produced by the build environment.
Check the scripts how repacking both of those works. If everything is right, that will get you to boot.
the zImage you can get from ASUS_AI2202-32.2030.2030.26-kernel-src/kernel_platform/out/msm-waipio-waipio-gki/dist
Update to 1.1.3
Hey guys and girls,
Here´s the next update. Linux-Stable up to 5.10.149, which also fixed the CVEs discussed here and here.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- included few changes from firmware 32.2050.2050.34
- merge latest kernel/common
- linux-stable to 5.10.149
- includes a few fixed CVEs
- other improvements and tweaks please check github
Download:
Attached to release post, AFH is currently broken
https://www.androidfilehost.com/?w=files&flid=335947
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
Update to 2.0.0
Hey guys and girls,
Here´s the next update with source for A13 stable merged. (not much changes, hence the fast release)
Update to A13 stable before flashing this.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- included few changes from firmware 33.0804.2060.65
- merge latest kernel/common
- linux-stable to 5.10.157
- other improvements and tweaks please check github
Download:
Attached to release post, AFH is currently broken
https://www.androidfilehost.com/?w=files&flid=335947
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
Update to 2.0.6
Hey guys and girls,
Here´s the next update. That´s a bigger one. I´ll explain a few things below in more detail.
The link to the latest firmware can be found following this link.
Monolithic kernel build
Thanks to @arter97 it´s now possible to build the 5.10 qcom kernel now as a monolithic kernel, not needing to build as a GKI style kernel.
To explain it simple: The problem is QCOM/Google are no longer required to test if drivers are loading in the correct order and or test compilation of a monolithic kernel at all.
The gki style kernel has 100s of drivers build as external kernel modules, instead of directly into the zImage.
Having a monolithic build eases development a bit, but won´t directly make an impact to the user.
If you´re interested check my github, it contains the commits. and be sure to drop @arter97 a few thanks somewhere!
Introduction of Lazy RCU
Usually I´m not stating remarks about a change improving battery life notably. But this is one of the few kernel changes that really does make a noticeable difference.
This kernel has the entire(!) RCU subsystem updated to latest linux 6.0 kernel state. This also allowed for Lazy RCU to be merged into the kernel, which should result in power-savings while the device is lightly-loaded or idling (which is basically the case all the time a smartphone isn´t being interacted with (nothing touching the screen and no other workload such as video editing is done).
If you´re interested in details check the slides, which are also linked in the article mentioned/linked above.
A very simplified explanation: RCU functionality can be called 1000s of times a second, batching RCU calls can save power by not calling as often.
Please keep in mind, those are kernel changes and battery life will not be improved magically by huge amounts, but there´s definitely an improvments.
Sony Scheduler Improvements
Import some scheduler changes around Walt from Sony Xperia 1 IV. This improves jitter by a significant amount.
More changes in the changelog below:
Changelog:
- merge latest kernel/common lts branch
- linux-stable to 5.10.160
- merge latest qcom upstream to main branch
- bump clang to latest prebuilt from google 16.0.2
- lazy rcu backported
- scheduler improvements from Sony Xperia 1 IV
- remove wlan rx wakelock as it´s unnecssary
- other improvements and tweaks please check github
Download:
Attached to release post, AFH is currently broken
https://www.androidfilehost.com/?w=files&flid=335947
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
is there any possibility you could try to make such a kernel for rog 6 ? if you had a tester
luki2411 said:
is there any possibility you could try to make such a kernel for rog 6 ? if you had a tester
Click to expand...
Click to collapse
hi everybody. this is a very voluminous work, but still, if you decide, I am ready to take an active part in testing.
Hi Freak Will you port this kernel to ROG Phone 6 ?

Categories

Resources