[Kernel][05.01.2023][Android 12] Kirisakura 1.0.1_S for Asus Zenfone 7/Pro aka Tequila - ASUS ZenFone 7 / 7 Pro ROMs, Kernels, Recoveries,

[Kernel][05.01.2023][Android 12] Kirisakura 1.0.1_S for Asus Zenfone 7/Pro aka Tequila - ASUS ZenFone 7 / 7 Pro ROMs, Kernels, Recoveries,

Kirisakura-Kernel for the Asus Zenfone 7/Pro
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Asus Zenfone 7/Pro aka Tequila. The Zenfone line- up internal codenames are derived from alcoholic drinks, last year the Zenfone 6 bore the title Kirin.
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. Instead there is an option called battery saver in the options of your phone.
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.
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.
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 different SKUs of the Zenfone 7/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 the other features to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
A big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from Asus for Android 12 and intended for use on the latest Asus Stock-Firmware
- compiled with Clang 13.0.1 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 4.19.2240
- CAF base for the Snapdragon 865/+ (SD865/+) updated to upstream CAF
- Kernel Control-Flow-Integration (CFI) andLink-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 5/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 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!
- Flashable via EXKM, FKM or TWRP on a rooted system!
- Anykernel zip is based on the Anykernel3 release from @osm0sis
- 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)
- display tweaks to reduce power consumption on statically rendered images
- option to limit max cpu frequency (3 levels) also to cpu boosting during input, without enabling powersaver mode that restricts background data sometimes killing notifications
EAS related features:
- EAS implementation patched up to latest CAF state
- disable autogroups and use cgroups for more efficient task placement!
- updates from kernel/common
- scheduler updates from Googles Pixel kernel
- tune scheduler for improved jitter and less jank frames
- scheduler updates for RT tasks
- scheduler updates from sd888/ 5.4 kernel
- mainline scheduler updates for better load balancing on sched_idle cpus
CPU related features:
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to user power efficient workingqueues. This compliments EAS
- improvements to cpufreq/times/stats
- improve memory allocations in binder driver
- vdso32 patches as found on Google Pixel devices (brief documentation here)
- arm64: lse: Prefetch operands to speed up atomic operations, thanks @kdrag0n
- implement fast refcount checking
- remove RTB logging to reduce overhead
- remove event debug logging
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
- 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:
- 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
- default IO scheduler to CFQ and readahead to 128
- improve GC as to not interfere while user interaction is happening and prevent possible jitter or latency spikes
UI/UX/Usability:
- Backlight Dimmer (reduce minimal brightness on a solid white background from 2,3 lux to 1,6 lux)
- sweep to sleep
- touch sampling override option (set stock touchsampling rate from 120hz to 200hz for reduced touch latency)
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 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
- Backport to enable CONFIG_HAVE_MOVE_PMD (see here) , thanks @arter97
- Backport to enable CONFIG_HAVE_MOVE_PUD (commit here) , thanks @arter97
- allow max swappiness over 100, to favor swapping instead of dropping the cache
- free more RAM by removing unused reserved memory regions
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 5 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
- Backport mainline Selinux commits for improved performance in the selinux subsystem, thanks @arter97 (you must be on magisk 21.0 or higher, otherwise the kernel won´t boot)
Misc Features:
TCP Congestion Algorithms:
- advanced algorithms enabled, enable them with your favorite kernel manager
- use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
- 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
- implement ramoops functionality to be able to easily debug kernel panics
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
Flashing Guide, Download and Changelog
Requirements:
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root (magisk 22.0 or higher), usually magisk stable works best
- a backup of stock boot.img and dtbo.img so you can go back to stock conditions (simplest way is TWRP)
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 7/Pro receives an 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, make sure you have a backup ready!
2. Flash the kernel.zip via latest TWRP, EXKM or FKM app and do a full reboot.
3. 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.
www.androidfilehost.com
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.1.3 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-85018787
1.2.0 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-85369449
1.2.1 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-85432205
1.2.5 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-85797313
1.2.6 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-86238683
Android 12
1.0.0 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-87106135
1.0.1 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-87949953
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_TEQUILA_Zenfone_7

FAQ
F.A.Q:
Question: Why does the kernel version show as "unavailable" in settings after flashing it.
Answer: Asus does not allow for custom kernel names in their settings. Use a kernel manager to check the kernel version.
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 as well as dtbo.img from matching firmware you are on and flash the extracted boot.img and dtbo.img via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom.
Question: Why is having Magisk installed mandatory for this kernel?
Answer: Android 10s changes to partitions, doesn´t allow files in system/ and vendor/ to be replaced. This kernel is very far from the stock kernel. To account for this I can´t force load the stock kernel-modules for certain drivers as it happens on kernels that are closer to stock.
Instead we use Magisks function to overlay certain files during boot. Without a working Magisk environment the kernel cannot function.
Question: I have a phone that is converted from CN to WW and now there´s a warning from hardwarestub. Can I hide it?
Answer: Yes, I created a Magisk Module for those that want to hide the notification, so nobody needs to rely on paid apps.
The Magisk module can be found attached to this post.
Please note that refresh rate can´t be changed when the module is flashed. To able to change refresh rate or to remove the module, simple remove it in Magisk Manager and do a full reboot. I´ll attach it to the third post on this thread. There will be no support for this module from my side and no other support for converted devices.
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 one too

and the final one, because one never knows.

In case anyone asks, make sure to update to the firmware that dropped today.
[210421] ZenFone 7 Pro / 7 _WW_30.41.69.51
【Version】 30.41.69.51 【Model Name】 ZenFone 7 Pro (ZS671KS) ZenFone 7 (ZS670KS) 【Release Date】 2021/04/29 Since the server pushes update notice to different serial numbers by batches, it may take some days for you to receive the FOTA notice. Thanks for your patience. You may tap “System...
zentalk.asus.com
Download link for full firmware is here:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS670KS/UL-I002D-WW-30.41.69.51-user.zip

Thank you for this! The phone is much faster, but also warmer in daily use. DeepSleep is perfect.

Seosam said:
Thank you for this! The phone is much faster, but also warmer in daily use. DeepSleep is perfect.
Click to expand...
Click to collapse
My phone runs on the same temperature compared to stock kernel.
Whats your ambient temperature? Maybe it's related to that.
Or it's coincidence and an app is stuck in background or got recently an update. Give it a reboot or maybe a few days.

Freak07 said:
My phone runs on the same temperature compared to stock kernel.
Whats your ambient temperature? Maybe it's related to that.
Or it's coincidence and an app is stuck in background or got recently an update. Give it a reboot or maybe a few days.
Click to expand...
Click to collapse
I think this is due to the higher boost from the kernel compared to stock. There is also only a 4-5 degree Celsius difference. And only when using apps. You can feel it a little in your hand.
Reboot was carried out, of course. As I said, I think it's simply due to the higher frequencies overall and is completely within the limits.

Seosam said:
I think this is due to the higher boost from the kernel compared to stock. There is also only a 4-5 degree Celsius difference. And only when using apps. You can feel it a little in your hand.
Reboot was carried out, of course. As I said, I think it's simply due to the higher frequencies overall and is completely within the limits.
Click to expand...
Click to collapse
The kernel doesn´t boost anything higher than stock. The powerhal and all boosts on input are unchanged compared to stock. Improved UI performance isn´t due to higher boosting.
Might be that some of the scheduler changes, paired with your unique usage lead to overall higher used freqs and the mild temperature increase.
Interesting that it seems to be the case for you.
Temps are basically the same on my end also during benchmarks, because I monitored temps while verifying the improved UI performance.
Thanks for the report! There is still more to come (also for the scheduler)

Thanks for your work, but I noticed than the consumption of the battery was high.
How can I flash the original kernel, I'm always on the stock a11 rom but I will flash soon the omnirom.

gui3gui said:
Thanks for your work, but I noticed than the consumption of the battery was high.
How can I flash the original kernel, I'm always on the stock a11 rom but I will flash soon the omnirom.
Click to expand...
Click to collapse
See post #2

Ok but perhaps, can you provide this file ?

gui3gui said:
Ok but perhaps, can you provide this file ?
Click to expand...
Click to collapse
No, it's best if you extract them yourself.
If you followed the instructions in the OP you should have a backup from boot.img and dtbo.img made via TWRP.
If you don't have them download the full firmware and extract them via payload extractor. You will be able to find that on XDA.
Edit: to flash Omni you need to have stock rom on both slots anyway. So just flash stock rom twice (that will restore original boot.img and dtbo.img anyway) and follow the Omni instructions!

Feature Documentation:
Here´s a brief documentation about some of the features included in the kernel that can be changed as the user desires.
They can be accessed via either terminal, scripts or for example EXKM manager ( tools -> user settings).
CPU-Frequency Limiting
Another option is CPU-Freq Limiting. You can now limit the CPU frequency to a few different levels with a sysfs interface. Original implementation is from @tbalden, I only changed it to be accessible via traditional root methods.
Main Switch:
sys/module/cpufreq/parameters/batterysaver
Set this option to "1" to enable the feature
Max-Frequency Selection (Input boosts, such as scrolling boost or app launching boosts will still apply, if touch boost restriction is not set to 1)
sys/module/cpufreq/parameters/batterysaver_level
Set this to "1" to restrict the max CPU-Freqs to 1,7GHZ/2,1GHZ/2,49GHZ (Little Cluster/Big Cluster/Prime Core)
Set this to "2" to restrict the max CPU-Freqs to 1,6GHZ/1,7GHZ/2,0GHZ (Little Cluster/Big Cluster/Prime Core)
Set this to "3" to restrict the max CPU-Freqs to 1,49GHZ/1,4GHZ/1,6GHZ (Little Cluster/Big Cluster/Prime Core)
Touch-Boost Restriction
sys/module/cpufreq/parameters/batterysaver_touch limiting
Set this to "1" to restrict the powerhal from boosting over the limit defined in batterysaver_level
Set this to "0" to allow the powerhal to boost above the values defined in batterysaver_level, but only during interaction with the Phone!
Screenshots:
{
"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"
}
This is for example very useful during gaming to prevent additional heat, if not the highest performance from the CPU is required. Check if the game is running fine on level 1 or 2, and you´ll notice much less heat. Powerdraw will be reduced as well.
Another very useful trick while doing video calls or long extended navigation sessions with google maps to preserve battery or keep the phone from heating. Especially during summer if the ambient temperatures are high.
This is a very easy way to preserve battery or reduce heat without toggling the battery save mode in settings as that restricts background data usage, which can lead to delayed notifications.

Hey everybody,
I was a bit busy. Regarding new firmware update:
all changes from the 30.41.69.66 were already present in my kernel by merging CAF-Upstream.
So just flash away on the new firmware, link is here:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS670KS/UL-I002D-WW-30.41.69.66-user.zip

Freak07 said:
Hey everybody,
I was a bit busy. Regarding new firmware update:
all changes from the 30.41.69.66 were already present in my kernel by merging CAF-Upstream.
So just flash away on the new firmware, link is here:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS670KS/UL-I002D-WW-30.41.69.66-user.zip
Click to expand...
Click to collapse
Hi,
I'm considering to get a zenfone 7 Pro but I would like to know do your kernel support permissive mode with fully /system write?

TheEndHK said:
你好，
我正在考慮購買 zenfone 7 Pro，但我想知道您的內核是否支持完全 /system 寫入的許可模式？
Click to expand...
Click to collapse
no

TheEndHK said:
Hi,
I'm considering to get a zenfone 7 Pro but I would like to know do your kernel support permissive mode with fully /system write?
Click to expand...
Click to collapse
That's not related to the kernel any longer.
Permissive selinux can be set via terminal or a script.
Read/write is difficult on devices with dynamic partitions. Magisk modules are the easiest solution for this. They allow to systemlessly replace files during bootup.
However there are solutions like this:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
I'd be very cautious of stuff like this, it has the potential to mess up the device completely, so it can be only restored by wiping everything including all data on the device.

Any new updates? On the actual 78 firmware, the cores don't reduce the frequences on my phone.
Thank you

Double post

Related

[Kernel][All Quark]BHB27-Kernel android [5.1.1] to [10.x]. For Custom and Stock ROM's

{
"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"
}
I have start this project to bring a more features and updates to Quark Kernel, and put the user on the control of the Kernel configuration
ROM Support:
This will work on any CM/LOS Custom ROM that is up to date to CM/LOS Repo or my custom ROM repo (in doubt check with the ROM developer) And latest Motorola Stock Marshmallow ROM for all devices (for the stock ROM use Kernel V3.5 and up only)
TWRP will display what is flashing during installation if the TWRP screen show something odd print the screen and post on the thread
SuperSu support on Stock ROM:
Link for BETA-SuperSU-v2.62-3-20151211162651_3
If you never flash SU on Stock ROM first Flash that version reboot then go back to recovery and Update using the latest from SU thread
This Kernel has safetynet verification Support on unlocked bootloader of course without ROOT, if you wanna ROOT checks latest hide root support threads use XDA search for that
Main features:
I will bring any featuring and improves that is possible to Quark, but the main point is provide the better experience balance battery vs performance, keep a update kernel and full user control.
Kernel is a slow process to improve I will take my time and will make updates when I can, every update will be tested before release, any bug found please let me know.
Some of the below features can only be see on the app when using this thread Kernel, the below are just some of many featuring of this app/kernel...
CPU and GPU - Over and under clock;
Linux Kernel always update to the latest version;
Many custom CPU GOV optimized for Krait 450;
CPU optimizations;
CPU Per core control;
CPU Per core Frequency control;
CPU Per core Governor control;
CPU Schedule workqueues;
CPU Boost ;
CPU Wakeup Boost and Hotplug Boost;
CPU voltage control;
Custom CPU Hotplug;
Custom Thermal control;
Ram control;
GPU optimizations;
GPU idling algorithm;
Wake gestures Doubletap2wake and Sweep2wake ;
KCAL - Advanced color control;
Sound control module;
Power and suspend Improves;
I/O Scheduler optimizations;
Many custom I/O;
Wake Locks controler;
KSM kernel same-page merging;
Virtual Memory;
Zram;
Network optimizations;
Many custom TCP Cong algorithm;
Custom Kernel Adiutor app with special features just for Quark (to better support my kernel I make my on Kernel adiutor check Downloads)
Check Changelog L, Changelog M, Changelog M and N, Changelog O, Changelog P and Mod Kernel adiutor changelog for full list of features.
Installation instruction Kernel:
Download the latest version
Take a TWRP backup (system, boot and data)
Flash the zip using latest TWRP recovery (wipes are't necessary)
Reboot
Enjoy!
On Oreo, will take two tries to finished the boot process after the update, first is slow and reboot at the end second is fast and after all must work OK
Installation instruction app:
Just Install the apk like anormal app on any ROM it need's ROOT access to work.
Installation Files
Download Kernel Oreo, Nougat and Marshmallow (Marshmallow only version 3.5 and up, Oreo 9.5 and up):
Main:
Gdriver Mirror Click Here (This contains current and previously version)
Secondary:
AFH Mirror Click Here (This contains all old versions)
Download Kernel Lollipop click here
Download App Mod Kernel adiutor for Quark:
XDA Labs Click Here or use XDA Labs app to install update and received updates warning (search for KA27)
AFH Mirror Click Here (This contains all old versions)
TWRP For Quark click here
To go back to Stock ROM kernel:
Oreo:
Is possible in Oreo to just restore or reflash the Stock ROM boot.img, if you did not made a backup of the boot partition, you can extract the boot.img from the ROM zip and install it over TWRP the process is the same as any .zip flash but you must chose "images (is in the bottom right of the install screen) after select the image and image type "boot"
Older than Oreo OS::
As quark kernel is not just a boot.img before Oreo, it has some modules that are on the system partition, to restore is need to re-flash yours ROM zip (a dirty flash) it will re-flash the stock kernel + all the modules of that ROM, but will erase any modification that you made to system like xposed or gapp so is need to re-flash any zip that changes the system partition. Make a TWRP backup first just in case, the dirt flash may bootloop, in that case clean install.
Thanks:
@Skrilax_CZ for his hard work on CyanogenMod for this device.
Big thanks:
A big thank for those that donating to thanks for my work on this kernel
Developer donation link:
To donate via paypal click here
No other donation option is available.
XDA:DevDB Information
BHB27-Kernel, Kernel for the Motorola XT1225, XT1250 and XT1254 -- Moto Maxx, Moto Turbo and DROID TURBO.
Contributors
baybutcher27
Source Code:
Kernel: fgl27/BHB27Kernel/tree/N_c
Toolchain: UBER from matthewdalex/arm-eabi-4.9
How to Build: how_to_build_this.sh
Mod Kernel Adiutor app: fgl27/KA27
Kernel Special Features: Check Changelog L, Changelog M,Changelog M/N Unified, Changelog O, Changelog P/Q
Version Information
Linux: 3.10.x
Status: Stable
Created: 2015-09-21
Last Updated: Check Changelog L, Changelog M,Changelog M/N Unified, Changelog O, Changelog P/Q

Below is some help for the most know problems.
Random Power off or reboots?
To identify if the device random reboot or simply power it self off there is two ways.
1) If after the device goes black you can't power it up again without plunging the charger, then is because the battery is dead, even if yours battery had good % left before it shutdown yours battery is probably damage doesn't matter if the device/battery is new a battery can go bad simply by charging the device wrong, a wrong way to do it is let the device constantly go bellow 20% as low you let it get worse yours battery will be with time.
2)Check the boot reason prop "ro.boot.bootreason" if it is like the example bellow set to power_key_press the device didn't reboot it sled power off.
Code:
[ro.boot.bootreason]: [power_key_press]
Check the prop using :
Kernel Audiutor app > logs section > search in a log > mark getprop > search key word "reason".
If the Random power off are related to battery, BCL can help mitigate the problem.
BCL can be controlled via BHB27 kernel adiutor Power and battery section.
Lowering the BCL Max frequency or Making the number of hot unplugged core higher will help to mitigate the CPU power.
But if the problem persist is necessary to change the BCL low and high voltage threshold to higher values to make BCL to start sooner, the recommendation is to set they to 3700mV (Low) and 4000mV(High) and if the problem is resolved after that, the device stops randomly power it self off, lower the values 100mv it until you find a perfect value, or if the problem persist make the values 100mV higher.
Is also recommended to set the battery "Automatic power saver" from default 15% to a higher value, with is today max at 25%
If the device did just reboot just share a log as recommended on next post.
There is a help like this on the ROM's I share it may help as some problem are ROM related and not kernel so they are not here, so try to check there for more .

This kernel is tested and is fully working.
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand and can't be reproduced, I can't fix.
Always start a post with a bug report with @fgl27 and always attached a log .zip
fgl27 Kernel Adiutor > Logs > One click all Logs to a ZIP
If is a Reboot/Power off related bug make the log as soon the device finishes boot up
Bugs without logs, without @fgl27 will probably not be read, there is too much posts on the thread sometimes and I don't have time to read it all, anyone can post as much as is need of course as long is a things related to this thread
Feature request are welcome too, but understand not all feature that exist is possible to bring to quark.

What's difference between this and kernel of NX?
----
Moto Maxx - XT1225
Xposed NXRom 5.1.1

Flashed, looking forward to seeing if it makes a difference during class and such tomorrow, thanks!

RSDamasceno said:
What's difference between this and kernel of NX?
----
Moto Maxx - XT1225
Xposed NXRom 5.1.1
Click to expand...
Click to collapse
Never used, can find source dev does not seem to publish, can look.
Will ask him for the source.

baybutcher27 said:
This kernel is tested and is fully working.
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that i can't understand can't reproduce I can't fix.
Feature request are welcome too, but understand not all feature that exist is possible to bring to quark.
Click to expand...
Click to collapse
One request, if possible? "Westwood Plus" TCP congestion control. I know "Cubic" is the Android default, but many tests show Westwood Plus (also written Westwood+) is better under lossy conditions. (Not to be confused with the original "Westwood", Westwood + is a newer version. ) Many custom ROMs include it in their kernels, and some custom kernel devs make it the default over Cubic.
Yes, there is debate over which one is better -- Cubic or Westwood Plus. But isn't choice a good thing?
http://androidmodguide.blogspot.com/p/tcp-algorithms.html
Westwood/Westwood+:
A newer version of Reno, and another commonly used one. It controls parameters better, helping out streaming and overall quality of browsing the internet. One of the most 'fair' algorithms out there, and is one of the most efficient algorithms to date.
Click to expand...
Click to collapse
If it's not possible to include it, I can live with Cubic. Just a request. :good:

ChazzMatt said:
One request, if possible? "Westwood Plus" TCP congestion control. I know "Cubic" is the Android default, but many tests show Westwood Plus (also written Westwood+) is better under lossy conditions. (Not to be confused with the original "Westwood", Westwood + is a newer version. ) Many custom ROMs include it in their kernels, and some custom kernel devs make it the default over Cubic.
Yes, there is debate over which one is better -- Cubic or Westwood Plus. But isn't choice a good thing?
http://androidmodguide.blogspot.com/p/tcp-algorithms.html
If it's not possible to include it, I can live with Cubic. Just a request. :good:
Click to expand...
Click to collapse
Yes The + i did not find because did not know about, i will search, I have included some already in the test version that i'm using, check the pic.
I know how to make things work for quark Kernel, but i don't now all the things that exist, so keep me inform, i will search and if is possible to port to quark i will.
will try to release a new version later today 6 to 8 hours from now, test is very good.

@ChazzMatt the Westwood in the next build is already the Westwood+
check the C file in here
The file is name just westwood but you can read in the file description that is the +... Test kernel is really stable, will released today, let all test and see what is the best for it use...

baybutcher27 said:
Never used, can find source dev does not seem to publish, can look.
Will ask him for the source.
Click to expand...
Click to collapse
You want some screenshots of Kernel Adiutor?
----
Moto Maxx - XT1225
Xposed NXRom 5.1.1

Kernel update! BHB27-Kernel-V1.0.2
Download-Kernel
Changelog-Kernel
Change:
====================
09-22-2015
====================
* V.1.0.2
* Implemented KSM
* Add TCP-CONG Westwood, bic, Highspeed, Hybla, Htcp
* Implemented CPU otimizations Flags to the Kernel (more otimizations to come in next build)
Test and let me know...
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that i can't understand can't reproduce I can't fix.

BTW try to implemented DT2W and S2W but quark doesn't accepted it (the config is ok but noting happen ), maybe i future update. Can be a conflict with moto screen wave and pick i disable it but not work...
Will try if success will release a separated version with DT2W because it can be a wakealock.

Removed the last update something is wrong on my device will check.

baybutcher27 said:
Removed the last update something is wrong on my device will check.
Click to expand...
Click to collapse
Working fine here

goalando said:
Working fine here
Click to expand...
Click to collapse
I tested it over 24h, It may work well but from noting it start to produce bugs. maybe a none kernel related i looking
Making a new build remove a wrong entry to see if help.

Kernel update! BHB27-Kernel-V1.0.3
Before install it, uninstall or clean data of any kernel control app you're using.
Download-Kernel
Changelog-Kernel
Change:
====================
09-22-2015
====================
* V.1.0.3
* Remove incompatibility (CPU optimizations flags and Remove per-cpu workqueue) To find a bug will add improves latter.
Test and let me know... I test this, i remove some improves that may cause bugs, is more to stock as possible, but still have, CPU gov, KSM and TCP govs.
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that i can't understand can't reproduce I can't fix.

Gpu governor > simple ondemand = freeze and reboot. In v.1.0.3
Edit for requests:
1) add mako hotplug
2) GPU frequency minimum to 27MHz
3) volume and microfone gain
----
Moto Maxx - XT1225
Xposed NXRom 5.1.1

Thanks for all your hard work man

RSDamasceno said:
Gpu governor > simple ondemand = freeze and reboot. In v.1.0.3
Edit for requests:
1) add mako hotplug
2) GPU frequency minimum to 27Hz
3) volume and microfone gain
----
Moto Maxx - XT1225
Xposed NXRom 5.1.1
Click to expand...
Click to collapse
Yes it does, did not have time to go over gpu_gov, I recommend to leave as default msn-adreno-tz. Will remove or fix simple ondemand. :good:

Implemented, now I'm testing new features that user's ask... No new hotplug, mako is not ported right now to MAXX, will try to port other improved hot plug or improve msm
Voltage, sound, FS and screen control. FS can only be change with some kernel app (like trickster mod ).
All is good bu twill test longer to make shore.

[KERNEL][TW][SM-G930F/FD/W8/S/L/K] Primal Kernel v2.3.4 [DQH8][S7 + Ports]

{
"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"
}
Welcome to the official thread for Primal Kernel project for the Exynos Galaxy S7 (SM-G930F/FD/W8/S/L/K) running TouchWiz based ROMs (Nougat only currently).
The aim of this project is to provide a rock solid, ready to use tweaked kernel, without useless features.
Introduction:
Primal Kernel, formerly known as The Outsider Kernel, is the first S7 kernel for TouchWiz based ROMs sporting the AnyKernel2 installation approach.
The most widespread method consists of flashing a complete prebuilt boot image (this means that it will be flashed straight away without any modification).
This is the most practical method for providing a working kernel, but it has disadvantages too:
1) the installation package will be bigger.
2) the developer must keep the ramdisk updated with the newest from stock kernels. This requires rebasing the patches and keeping up with the newest firmwares sometimes with frequent releases.
3) it makes the compatibility with older ROMs a little more complicated as a newer ramdisk could add modifications not supported by the older ROM.
4) for the ported ROMs the developer has to manually patch the ramdisk with the required changes from the ported device's one. So you have to create a different boot.img for every ported device for every S7 variant.
But we have an alternative...
AnyKernel2 is a different approach to the installation of the kernel: the package only contains the prebuilt zImage (the actual kernel), the dtb (basic hardware instructions like reserved memory and so on) and the patches for the stock ramdisk. AnyKernel while installing unpacks the previous kernel and replaces zImage, dtb and, after patching it, the new ramdisk.
This implies various benefits:
1) smaller installation package.
2) you can always have the most updated ramdisk without the need of waiting an update from the developer.
3) better compatibility as you can flash it on top of any stock (or close to) boot image.
4) it makes life a lot easier for the developer with many ready to use patching functions.
5) with some efforts from me, the package can adapt the stock S7 ramdisk to work on any S8 or Note FE ported ROM, making it even more adaptable.
All this sounds great (and it is great) but introduces a problem: you can't flash it on top of another custom kernel. This because custom kernels almost always have scripts and other modifications to the ramdisk, which might not be compatible with my kernel.
Installation instructions:
If you correctly follow these instructions you'll be able to run Primal on any ROM (as above).
If it doesn't work, read twice and try installing again before asking for help.
● Instructions for BatMan ROM (S8 port) users:
1) install the ROM (you can dirty flash if you already have it installed) make sure to choose stock kernel (so it doesn't install the new GPU libs, which aren't supported by Primal).
3) after the ROM flashing process has been completed flash the Primal kernel zip for your device.
4) flash your preferred root method.
5) reboot and be patient as first boot might take a little more time.
● Instructions for any other ROM (any other S8 and Note FE ported ROM and, obviously, any S7 ROM) running a custom kernel:
1) make sure you have the stock S7 kernel zip (or any stock boot.img from any S7 Odin package or ROM zip containing the stock kernel) and Primal Kernel zip.
2) if you have a boot.img flash it to the boot partition using Flashify or TWRP itself.
3) if you have the flashable stock kernel zip and Primal Kernel zip reboot to recovery and flash in this order: stock kernel zip, Primal Kernel zip and then your preferred root method.
● Instructions for any S7 ROM running stock kernel:
1) reboot to recovery and flash in this order Primal Kernel and your root method of choice.
If you get into a bootloop...
● if you're running a port make sure it says dream2lte (if an S8 port) or gracerlte (if a Note FE port) in the build.prop; if there isn't any add a line at the bottom, "primal=dream2lte" for S8 or "primal=gracerlte" for Note FE.
● make sure your ROM doesn't come with the new GPU libs installed, if it does restore the old libs somehow (flashable zip coming soon!).
Thanks and Credits:
● Samsung OSRC for the kernel source code
● @Tkkg1994 and @jesec for their clear and vast source code and scripts
● @flar2, @UpInTheAir, @franciscofranco, @eng.stk, @osm0sis, @andip71 and others for their great contributions to the community and Android
Features:
● based on the latest Samsung kernel source code G935FXXU1DQH8 merged with G935SKSU1DQG1
● always have the latest ramdisk for your specific model and variant, thanks to AnyKernel2
● ported ROMs are supported (like S8 and Note FE based ROMs)
● compiled with custom built Uber Toolchain 6.4.1 (20170826) and optimization flags
● custom scripts with tweaks applied at boot, optimizations and wakelock fixes
● init.d support
● added a few tested and updated CPU governors (blu_active, conservative, ondemand, powersave, interactive, performance).
default: interactive
● added a few tested and updated I/O schedulers (noop, deadline, row, cfq, bfq, zen)
default: cfq with custom parameters
● added a few TCP congestion algorithms (westwood, reno, bic, cubic, htcp, lia, olia, wvegas)
default: westwood
● full f2fs support from jaegeuk's f2fs-stable plus OnePlus improvements
● fstab mount tweaks for both ext4 and f2fs
● fixed various bugs in the Linux code like improved cyptography algorithms, filesystems, network...
● architecture specific fixes
● cpuidle improvements
● random (entropy) generation improvements
● power managemnet, schedulers, governor and memory management improvements
● unlocked lower CPU frequencies with correct voltages and set recommended defaults (312MHz big - 338MHz LITTLE)
● schedule workqueues on awake CPUs enabled
● improved hotplug and idle with interactive governor
● added 112MHz minimum GPU frequency and clock control
● voltage control for GPU
● LED control with fading option
● voltage control for big and LITTLE clusters
● preset I/O scheduler tunables
● disabled SWAP and ZSWAP for best performance
● preset VM tunables
● SELinux permissive
● Knox 0x0, Samsung security checks and SafetyNet spoofed to pass
● Fsync switch added
● Software CRC control switch added
● and many other changes (too many to be listed here)...
Notes:
● If you want root, you need to flash the root zip after flashing this kernel (Magisk is recommended to pass SafetyNet).
● If you want to access the advanced kernel controls MTweaks by @morogoku is the only app which supports all the features (download it here).
Everything has always been stable, and almost bug free, so no notes on that side at the moment :laugh:
Latest stable version is 2.3.4.
If you want to flash an older version see Archive in the download links below.
Source > GitHub
Commits (kind of a changelog) > GitHub
Download:
herolte (S7 SM-G930) > Android File Host
Support:
If you want to receive support, find and share settings, report bugs and try Beta versions, join our Telegram group:
TouchWiz Projects by kylothow | Official Group
You're welcome
XDA:DevDB Information
Primal Kernel, Kernel for the Samsung Galaxy S7
Contributors
kylothow
Source Code: https://github.com/kylothow/universal8890-NN-G935
Kernel Special Features: Stable f2fs porting, tweaked with recommended settings, a few but working governors, schedulers and patches are just some of the awesome features.
Version Information
Status: Stable
Current Stable Version: 2.3.4
Stable Release Date: 2017-09-13
Created 2017-04-26
Last Updated 2017-09-14

Changelogs:
From version 2.3.3 to 2.3.4:
Code:
● added fstrim on boot
● added Knox and other security check props spoofing inside the kernel
● added Google Play services drains fix
● added custom init.rc with tweaks (cfq with tunables preset, read ahead 128 and 256 for external, rised base CPU frequency a little (you can lower it if you want)
● recent patch to cpufreq added
● updated AnyKernel2 with the latest goodies from osm0sis
While searching the Internet you might also find versions which aren't listed here: these are Beta versions and their changelog isn't available (but included in the one of the next stable version, so you don't miss anything).
All the changes I made are listed on GitHub.
Old changelogs (for The Outsider):
Version 2.2.1
Code:
- added cleaning scripts at boot (automatic trim, sqlite optimization, cache and leftovers cleaning
- updated ramdisk and mcregistry to DQE7
- updated with latest Samsung changes (DQE7/DQEF)
- disabled swap and zsmalloc
- added row I/O scheduler
- increased default maximum frequency to 2.6GHz
- updated to Linux 3.18.55
- switched to custom built Uber Toolchain 6.3.1 (20170528)
- switched to a whole new overclock/voltage management method based on ASV
- changed frequency policy especially regarding touch boost (for better battery)
- allow to enable Exynos swap
- add unstable power detection and charging/battery controls
- added notifiers for the future addition of CPU governors and removed old/broken implementations
- a few f2fs and other minor fixes to defconfig, schedulers, cpufreq
Version 2.1.6
Code:
- switched to GCC 6.3.1
- various build flags to optimize building
- enabled a few compression algorithms (GZIP, LZ4, LZMA...)
- enabled cryptographic drivers optimized for 64 bits
- defconfig tunings to reduce debug logging
- updated mcRegistry and ramdisk to DQD9 (for S8Port only the init file)
- drastically changed kernel default tweks/settings
Version 2.1.5
Code:
- fixes regarding stability and speed
- ext4 and fuse fixes
- crypto and drivers built uncompressed
- random numbers generation changes
Version 2.1.4
Code:
- the kernel has been redone from scratch; the features are in pair/more than the previous 1.x.x versions, and gives you an overall way better experience.
Version 1.4.1
Code:
- various bug fixes
- performance/reliability improvements for network, ext4, f2fs and cryptography
- enabled a few kernel modules for ipv6 and a few other optimizations
- trying out higher kernel timings
- set default governor to blu_active
Version 1.4.0
Code:
- first release for xda

How to set up your phone with f2fs:
1) First you have to install a compatible recovery. Recent TWRP releases can format and mount f2fs, but they don't handle a few installation scripts correcty. I recommend TWRP 3.1.1.0 by @lyapota which has the correct patches. You can find it here.
2) Then you have to backup all your data (internal storage will be wiped too, so make sure to copy ALL your files in the INTERNAL storage). So, any TWRP backup should be taken on external SD card.
3) After this, reboot into TWRP. From Wipe / Advanced Wipe check only /data, then select Change Filesystem and check f2fs. Do the same for /cache. At the moment I don't think there are ROMs that support f2fs on /system too (All the TouchWiz based ROMs force ext4 and format despite settings).
4) Reboot into recovery once again, so we're sure that it can mount everything.
5) At this point you're done. Flash your ROM of choice, this kernel and whatever you want.
Reboot and profit!
ROMs supporting f2fs formatted /system will be listed here when available.

Dishonored reference?
Sent from my Galaxy S7 using XDA Labs

XDevOS said:
Dishonored reference?
Sent from my Galaxy S7 using XDA Labs
Click to expand...
Click to collapse
Definitely [emoji6]
Sent from my SM-G935F using Tapatalk

kylothow said:
Definitely [emoji6]
Click to expand...
Click to collapse
Love that game :good: Will stay with this kernel as long as I can xD <3
Sent from my Galaxy S7 using XDA Labs

busy man
thanx boss
testing. ..
hotplug?
what Rom you running @kylothow

Calvin.manneson said:
busy man
thanx boss
testing. ..
hotplug?
what Rom you running @kylothow
Click to expand...
Click to collapse
At the moment only the stock hotplug. Further developments will need a specific app like Synapse or maybe a custom Kernel Adiutor -- which is the next step in the development.
I'm running latest Helios, the only thing that is preventing me to do my own custom ROM (basically it perfectly fits my needs).

Default settings are the best even for you?
I wanna try your work but don't have enough time for playing games with custom settings.
Thx a lot for you anyway

ig_df said:
Default settings are the best even for you?
I wanna try your work but don't have enough time for playing games with custom settings.
Thx a lot for you anyway
Click to expand...
Click to collapse
The point of this is to provide a great experience out of the box -- there is a few others helping me to decide which are the best settings, and I update them quite often because it's a continue pursuit of the best everyday settings profile.
The script applies at boot before anything else so you can change them in case you don't like.
The inexperienced user can update the kernel and enjoy always updated settings without even installing a kernel control app or rooting.
Sent from my SM-G935F using Tapatalk

+good kernal antutu 15xxxx
https://www.mx7.com/i/140/F2Pnl9.png
-battery unstable
rom s.....

Calvin.manneson said:
busy man
thanx boss
testing. ..
hotplug?
what Rom you running @kylothow
Click to expand...
Click to collapse
Those scores are with OC ? GPU and CPU?

Seems smooth even with PowerSaving mode(1.4.1)
Update: Battery is unstable <=60-50%

nalas said:
Those scores are with OC ? GPU and CPU?
Click to expand...
Click to collapse
yup,speed up everything for high score
New base D2/3 all score high.
with stock kernel and default settings score 140k.

May give it a try out at some point ATM I'm on superman ROM but curious as if it will break superman control app as I know a version of super kernel broken that app
Sent from my SM-G930F using Tapatalk

king118 said:
Seems smooth even with PowerSaving mode(1.4.1)
Update: Battery is unstable <=60-50%
Click to expand...
Click to collapse
hi
what is battery unstable you mean? it's less time than other kernel? please guide

tranphungan said:
hi
what is battery unstable you mean? it's less time than other kernel? please guide
Click to expand...
Click to collapse
The old 1.x.x version can have every problem imaginable (the only confirmed one is stutters for some users) but no one ever complained about battery.
Users just say things without proof, stats or logs, they don't even mention the settings they're using or which ROM are they on... Definitely not useful.
Sent from my SM-G935F using Tapatalk

kylothow said:
The old 1.x.x version can have every problem imaginable (the only confirmed one is stutters for some users) but no one ever complained about battery.
Users just say things without proof, stats or logs, they don't even mention the settings they're using or which ROM are they on... Definitely not useful.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thank you.
In my opinion. I can see this kernel make my rom Super Man is smoother than superstock or tgpkernel or superkernel. Absolutely smoothly and not effect to battery much (still not recognize..). I push up all cpu frequency to max. Hehe

New update is available for download. It has been tested and reported to be stable and worth the upgrade from the great 2.1.6.
Here's the changelog:
Version 2.2.1
Code:
- added cleaning scripts at boot (automatic trim, sqlite optimization, cache and leftovers cleaning
- updated ramdisk and mcregistry to DQE7
- updated with latest Samsung changes (DQE7/DQEF)
- disabled swap and zsmalloc
- added row I/O scheduler
- increased default maximum frequency to 2.6GHz
- updated to Linux 3.18.55
- switched to custom built Uber Toolchain 6.3.1 (20170528)
- switched to a whole new overclock/voltage management method based on ASV
- changed frequency policy especially regarding touch boost (for better battery)
- allow to enable Exynos swap
- add unstable power detection and charging/battery controls
- added notifiers for the future addition of CPU governors and removed old/broken implementations
- a few f2fs and other minor fixes to defconfig, schedulers, cpufreq
> https://www.androidfilehost.com/?w=files&flid=171297

thanx for updating dev.
definitely the fastest custom kernel for me...
anyone know why ux score is 'red' in antutu?

[KERNEL] [N] [OxygenOS] SimpleGX v1.18 (2nd Nov)

★ WHAT TO EXPECT ★ :
(over a pure stock kernel) :
Better battery life
Overall better performance
Trying to include only efficient (but definitely no 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 7.1.1 source from OxygenOS / OnePlus 5 (for clean work)
Compiled with stock Google (4.9.x / aarch64-linux-android) toolchain (for best stability)
Featuring Anykenel2 (for all ramdisk compatibility)
Stock Linux 4.4.21
Main :
USB fast charge support (disabled by default)
Kernel logger disabled
Disabled adaptive LowMemoryKiller
Minimum backlight level control support (stock value by default)
Wakelocks control support (all wakelocks disabled by default)
Several fixes/optimizations patches for stock cpufreq_interactive governor
MAPLE I/O scheduler added (and set as default)
Completely optimized stock 'cfq' I/O scheduler
Xbox controller (and other USB pads) support
All TCP congestion control modules activated with Westwood currently as default
Removed verify and forced encryption + patched SafetyNet flags to pass CTS
Wlan module from official OOS source
Some miscellaneous tweaks, fix, patches and security patches to improve overall smoothness and battery life experience
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 (than those stock)
root/busybox auto-installation
CPU/GPU overclocking/undervolting
KCAL
adreno idler
state_notifier
any upgrade of Linux kernel
dual-boot
etc
★ PREREQUISITE ★ :
An unlocked Bootloader
An Android Nougat 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) ★ :
Github >> SimpleGX.
★ INSTALLATION PROCEDURE ★ :
Backup everything you need (internal & external)
Unlock your bootloader
Flash your favorite TWRP recovery (official or unofficial)
Reboot to TWRP
Wipe system/cache/dalvik partitions
Flash your full usual ROM/firmware
Flash SimpleGX kernel
Flash root (Magisk or SuperSU)
Reboot and enjoy !
★ FAQ ★ :
How can I update my SimpleGX kernel version ?
Follow THESE steps.
How can I go back to stock kernel ?
Just flash back your full usual rom back.
Is there a LineageOS (LOS) version of you kernel ?
There was, but it has been discontinued. HERE is the old thread.
How to recover excellent battery life ?
Check my personal tips HERE.
★ LATEST VERSION ★
★ ARCHIVES ★
/!\ CHECK MD5 BEFORE FLASHING IS ALWAYS HIGHLY RECOMMENDED /!\
/!\ 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 ★ :
02.11.2017 : v1.18 released.
Synchronize codes for OxygenOS 4.5.14
23.10.2017 : v1.17 released.
Removes Spectrum support
Anykernel2: updated to latest version
19.10.2017 : v1.16 released.
Add Spectrum support (please read post #5 for all informations you need to know).
17.10.2017 : v1.15 released.
Re-included all queue work on power efficient wq patches (for overall better deep sleep).
Brings back minimum backlight to stock value (user may still set its favorite value).
09.10.2017 : v1.14 released.
Re-include (CVE-2017-1000251) security patch for Bluetooth BlueBorne attack (thx @nathanchance for the advice)
09.10.2017 : v1.13 released.
Synchronize codes for OxygenOS 4.5.12
Revert (CVE-2017-1000251) now useless security patch for Bluetooth (already included from OxygenOS 4.5.12 security patch)
03.10.2017 : v1.12 released.
Synchronize codes for OxygenOS 4.5.11
21.09.2017 : v1.11 released.
init.simplegx.rc: add (and disable) missing "wcnss_filter_lock" wakelock
21.09.2017 : v1.10 released.
Add (CVE-2017-1000251) security patch for Bluetooth BlueBorne attack
20.09.2017 : v1.09 released.
Added two cpufreq_conservative (fixes/optimizations) patches
Added wakelocks control back and disable them by default (for better battery life)
18.09.2017 : v1.08 released.
Anykernel2: updated to latest version
07.09.2017 : v1.07 released.
Removed all queue work on power efficient wq patches from franciscofranco. (Less experimental, more close to stock now).
Added OnePlus5 minimum backlight fix (current value has been set to 8 for now).
03.09.2017 : v1.06 released.
Added two minor (and safe) patches about performance and battery.
29.08.2017 : v1.05 released.
Synchronize codes for OxygenOS 4.5.10
23.08.2017 : v1.04 released.
USB fast charge support (disabled by default, use Kernel Adiutor to enable it if you need)
block: add MAPLE I/O scheduler and set it as default
cpufreq: interactive: Remove the jump_to_max hack
cpufreq_interactive: remove boost functionality
Anykernel2: finally fixed all available ramdisk simplegx tweaks
Anykernel2: updated to latest version
Anykernel2: new styling retouch during kernel flashing
18.08.2017 : v1.03 released.
Removed wakelocks control stuff.
I wasn't happy with it (not to say useless) and anyway it needed an app to control this, so...
16.08.2017 : v1.02 released.
Much better deep sleep.
15.08.2017 : v1.01 released.
Completely rebuilded from OP5 source from zero. I decided to now include only few recognized commits (many previous commits has been removed).
Wakelocks control available (ON by default, but may be turned OFF via Kernel Adiutor for exemple).
12.08.2017 : v1.00 released.
Initial release (check actual features).

Thanks & greetings
★ THANKS & GREETINGS ★ :
(by alphabetic order)
Lord Boeffla
osm0sis
ZaneZam
. . . and of course to all talented devs credited in my commits!

Donations
★ DONATIONS ★ :
Many thanks @dr.zook :good:
Many thanks @gillboyzz :good:
Thank you to support my work ! :highfive:

Spectrum explanation
This kernel is now NO MORE compatible with Spectrum app (author: @frap129)
Obsolete details (for reference) :
Since all spectrum profiles are all different between switching from kernels, here is my vision of things : instead of spending time to fine tune interactive gov (etc) in the purposed 4 scenarios offering typically what other kernels may do, I still wanted want to keep simple but efficiency (and not dangerous) settings/tweaks that me be useful for everybody.
Here is all you need to know, what SimpleGX kernel may offer, and the main differences between each profiles.
Full view of the currently integrated Spectrum file (for advanced users) :
Code:
# Balance (default profile)
on property:persist.spectrum.profile=0
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor interactive
write /sys/module/cpu_boost/parameters/input_boost_ms 100
write /sys/class/kgsl/kgsl-3d0/devfreq/governor msm-adreno-tz
write /sys/class/leds/lcd-backlight/max_brightness 255
# Performance
on property:persist.spectrum.profile=1
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor performance
write /sys/module/cpu_boost/parameters/input_boost_ms 1500
write /sys/class/kgsl/kgsl-3d0/devfreq/governor msm-adreno-tz
write /sys/class/leds/lcd-backlight/max_brightness 255
# Battery
on property:persist.spectrum.profile=2
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor conservative
write /sys/module/cpu_boost/parameters/input_boost_ms 100
write /sys/class/kgsl/kgsl-3d0/devfreq/governor powersave
write /sys/class/leds/lcd-backlight/max_brightness 100
# Gaming
on property:persist.spectrum.profile=3
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor performance
write /sys/module/cpu_boost/parameters/input_boost_ms 1500
write /sys/class/kgsl/kgsl-3d0/devfreq/governor performance
write /sys/class/leds/lcd-backlight/max_brightness 255
BALANCE profile :
This is the stock default profile after flashing kernel. It will be applied as default if you don’t want to switch to another profile. Balance profile will benefit from all you guys know already about this kernel for it’s great stock experience and stock values, looking for best of performance and battery life for everyday use.
PERFORMANCE profile :
Performance profile is looking those who only cares about performance at the cost of battery life. Excellent for UI and overall top tier performance during apps use. I definitely not recommended to let this profile 24/7. Please do not report any bad battery experience while using this profile.
BATTERY profile :
Battery profile is probably the most only interesting profile (at my eyes). Extremely useful in some situations, it will provide you best battery life without scarifying too much performance and keep your device usable everyday. Very useful for days at work or when you reach really low percentages, this profile will probably save your day. Note that also, the min screen brightness has been intentionally lowered to 100 (instead of 255), to reduce consummation.
GAMING profile :
This profile is completely based on performance profile, at the exception of GPU governor changed to performance. Only useful for gaining some extra FPS’s during your gaming sessions. I definitely not recommended to let this profile 24/7. Please do not report any bad battery experience while using this profile.

Welcome in the Kernel OP5 family mate, i'm also a french user (Nice)
Thanks

Can't wait to try this one out..Thanks mate.

Already flash this kernel~

Here we go
Enviado desde mi ONEPLUS A5000 mediante Tapatalk

thanks for the new kernel which is a good alternative for all users who just used the stock kernel so far Fortunately, I didn't post an update yet for the rom so I can still implement you kernel to the aroma installer menu.
Good luck!

Pho3nX said:
i'm also a french user (Nice)
Click to expand...
Click to collapse
Welcome to the club ! :highfive::good:
xXx said:
thanks for the new kernel which is a good alternative for all users who just used the stock kernel so far Fortunately, I didn't post an update yet for the rom so I can still implement you kernel to the aroma installer menu.
Good luck!
Click to expand...
Click to collapse
Thank you very much for that, appreciated :good::highfive:
You are my rom base since the beginning of my OP5, so thank you for your hard work! :good:
Cheers'

Just flashed your kernel mate
Thanks for your work so far kernel seems smooth like butter

UPDATE
★ CHANGELOG ★ :
15.08.2017 : v1.01 released.
Completely rebuilded from OP5 source from zero. I decided to now include only few recognized commits (many previous commits has been removed).
Wakelocks control available (ON by default, but may be turned OFF via Kernel Adiutor for exemple).
N-JoYz :good:

Testing... Works fine for now
Few deep sleep: remains awake often
Other things work perfectly, and im testing on Los based

mystique47 said:
Testing... Works fine for now
Few deep sleep: remains awake often
Other things work perfectly, and im testing on Los based
Click to expand...
Click to collapse
Thanks for LOS working confirmation, I didn't know it was compatible :highfive:
I will add it into first post :good:
Concerning deep sleep, it works fine for me, but yeah, there is something to ameliorate a bit (I alrerady have some ideas) but this time I will take time (before releasing next version) to decide which precise things to add :good:

AndroidGX said:
★ CHANGELOG ★ :
15.08.2017 : v1.01 released.
Completely rebuilded from OP5 source from zero. I decided to now include only few recognized commits (many previous commits has been removed).
Wakelocks control available (ON by default, but may be turned OFF via Kernel Adiutor for exemple).
N-JoYz :good:
Click to expand...
Click to collapse
Was having issues with elementalX and battery drain. Switched to this rom and problem solved. Thanks for the awesome kernel!

AndroidGX said:
Thanks for LOS working confirmation, I didn't know it was compatible :highfive:
I will add it into first post :good:
Concerning deep sleep, it works fine for me, but yeah, there is something to ameliorate a bit (I alrerady have some ideas) but this time I will take time (before releasing next version) to decide which precise things to add :good:
Click to expand...
Click to collapse
like all oos kernels on los roms notification slider don't work and hardware buttons are inverted (can change from options obviously). I haven't find other issues for oos kernels on los

We cannot disable touch boost? Why..
Sorry for bad english :good:

ponkz said:
We cannot disable touch boost? Why..
Sorry for bad english :good:
Click to expand...
Click to collapse
Where do you see it cannot be disabled ? I tried to disable via Kernel Adiutor app and it seems to work without any problem :good:
Anyway, I don't advice to disable touch boost since you will face some slight stutters during some activites (gaming, browsing, etc), stock value is better.

UPDATE
★ CHANGELOG ★ :
16.08.2017 : v1.02 released.
Much better deep sleep.
Enjoy ! :good:
(@mystique47, this release is for you :highfive

[KERNEL][TW & AOSP] PRIME-Kernel v2.1.2

List of Supported
Variants
SM-G930S/K/L/F/FD/W8
SM-G935S/K/L/F/FD/W8
ROMs
TouchWiz N base all ROMs (Stock, S8 port ROMs, Note 7/8 port ROMs)
AOSP 7.1.2 & 8.x base all ROMs (Lineage, RR, crDroid & AICP & more...)
Main Features
OSRC's latest Note-FE & S7 source code base.
Using the AnyKernel2(Flashing Tool).
Synapse support.
SELinux Permissive / Enforcing switchable (+ Fake Enforcing Mode).
Linux-stable 3.18.y upstream.
Compile with UBERTC 6.4.1 toolchain.
F2FS support (/data, /cache only).
Optimized for Exynos8890 using the Exynos-M1 flag for compile options.
Gametuner-Mod
Game Booster Mode
intelligent performance enhancement mode in conjunction with Samsung-Gametuner.
Fake KNOX.
chacha20 to random (entropy).
Linaro LSK-v3.18-Energy-Aware Scheduler (EAS) port.
EAS simplifies power and performance management through scheduler-driven tuning to manage more efficiently.
Linux-v3.18 already has EAS installed, but with the LSK-v3.18-EAS, the existing EAS has been further improved and the user can choose between tuning power efficiency and performance.
Linaro v3.18/topic/OPPv2 branch merge.
Lazytime mount options
improved storage performance and longevity.
Similar to DynamicFsync, but operates at the file system level and has no risk of data loss.
CPU/GPU UC & OC.
Limit the maximum overclock range according to the device's ASV value (device yield) to prevent excessive overclocking.
CPU/GPU/BUS voltage control.
GPU Performance Tuning.
Performance/balance/battery separated DVFS user settings.
Thunder Hotplug driver port.
HMP tuning Interface.
Detail charging circuit control allows faster charging.
Added I/O Scheduler 'bfq, fifo, fiops, row, sio, maple, tripndroid, zen'.
Enable Westwood tcp/ip congestion control (not default).
LED FADE control.
PWM Flicker free.
boeffla's generic wakelock blocker driver.
Qualcomm interactive (renamed cafactive) cpu governor porting.
Added battery-friendly 'relaxed' governors, and more.
Provides an add-on that keep kernel settings on unrooted devices.
Synapse: System Tweak add-on available.
Synapse: Provides configuration profile separated by performance/battery/stability.
Many other optimization applications.
How many users are there in this kernel and what is it with custom ROM?
* Go to User Statistics.
With this kernel, the following information is sent once to the developer's server at boot time.
variant, android serial number(not device serial), name of current firmware(ROM), country code, kernel version
* This information is Android apps can see without any special permissions.
* If you suspect other information transfer, open the '/res/synapse/actions/addon' file.
Description for AOSP ROMs
If you are using another developer's custom kernel, or if using ramdisk is corrupted kernel, you may encounter a bootloop or an unknown problem.
If you have a bootloop problem, flash the PRIME kernel after first flashing the builtin kernel in your ROM. (Or flash the ROM again)
This kernel is flashed AnyKernel method, for all kinds of AOSP ROM support.
Download
Latest Version | Older Version
Community
Telegram Group: https://t.me/primekernel
Naver Cafe (for Korean): http://cafe.naver.com/primeusers
How do I enable donation-only add-on features?
Credit (Thanks. to)
@AndreiLux - Perseus8890 kernel.
@tkkg1994 - refer to some Commits.
@arter97 - cafactive & more.
@osm0sis - AnyKernel2.
@jesec - AOSP kernel source.
@Wootever - PWM Flicker Free.
All members of the PRIME-Kernel NaverCafe.
And all of commited in sources & all of xda developers.
XDA:DevDB Information
PRIME-Kernel, Kernel for the Samsung Galaxy S7
Contributors
Hyunwoo AHN
Source Code: https://github.com/dwander/Linaro-base/tree/herolte
Kernel Special Features: Linaro-LSK-3.18-EAS Port, Gametuner-MOD, Intelli-Performance
Version Information
Status: Stable
Current Stable Version: 2.1.2
Stable Release Date: 2017-12-17
Created 2017-09-23
Last Updated 2017-12-17

How do enable donation-only add-on features?
I only receive donations from your heart.
Do not donate if you intend to unlock synapses.
If you are unable to make a donation of 5.0 USD or more due to economic reasons, please do not donate and request me to unlock Synapse. Then you can use all the functions of synapse without donation.
How to request synapse unlock
Please tell [email protected] the following:
- A matter that is difficult for you to donate(eg economically difficult countries, students without money or credit card).
- The first five letters or screenshots of the KeyCode on the Synapse's first screen.

Change Log
v2.1.2
fixed bluetooth issue in AOSP 8.1
Linux upstream to v3.18.88
v2.1.1
Linux upstream to 3.18.87
Add Android O (8.x) support
Add new commit for AOSP support
Changed AOSP build to TouchWiz base (Integrated AOSP and TW kernel source code)
Fixed WiFi-Hotspot issue for N8 porting ROM
Fixed an issue where the charge state switching notification did not work
Note-FE GPU driver (r15p0) build droped
r12p1 GPU driver is built back into the package
Minor bug fixes
v2.0.1
Reuse AutoASV
Over clock limit relaxed
Removing the State Notifier Driver & Using the FB Driver
Fixed a bug where two big cores could not be used (v2.0)
Corrected the overclock value to actually apply when boosting the big core
Synapse: Memory: Z-Swap compression algorithm selection option removed
Synapse: Labs: gms drain patch removed
v2.0.0
base: Re-based on Note-FE source code
linux: upstream to v3.18.83
f2fs: Updated latest from f2fs-stable branch
init: Fixed video playback delay issues reported by some N8 porting users
tcp: Change the TCP congestion control algorithm default to Westwood (stock: bic)
Synapse: Fixed the problem that the Intelli-Performance setting is released after rebooting
GPU: Remove unnecessary ipa update code
exynos: Separate AutoASV in 5 steps
exynos: Changed AutoASV not to participate in overclock value(only used for big Core boosting)
mm: Change Z-Swap compression algorithm default to lzo(stock value)
Synapse: Memory: Added Z-Swap compression algorithm selection option
Synapse: Add Labs tab
Synapse: Storage: Resolve compatibility issues with DualSIM models
installer-zip: Include a RAMdisk for TouchWiz for all supported models in package(no need for stock kernel flashing)
installer-zip: After the kernel flashing is complete, it automatically flashes when Magisk or SuperSU files are found.
v1.9.3
Upstream to Linux 3.18.80
Synapse->Utility: Added Android ID management function
Synapse->Advanced: Added option to switch to Enforcing mode after booting
Synapse Add-on Updated to v6.4.2
selinux, Improved fake Enforcing
Use new random driver functions
Removing Gametuner-MOD from AOSP build
Minor bug fix
v1.9.0
Supported Note 8 Porting ROMs
Backported random(entropy) driver from Linux v4.14.rc7
Updated AnyKernel2 (bug fix)
Updated mptcp(Multipath TCP) driver (0.90.0 → 0.90.3)
installer, Prevent Magisk from being deleted when merging ramdisk
Reduced screen brightness during boot
r12p0/r15p0 GPU driver to separate build, packaged in one
! Please read the 'Attention to the GPU driver' part on the first page.
v1.8.2
Linux upstream to v3.18.78
Merge G935F DQJ1 firmware sources
Merge Note-FE AQI4 firmware sources
Fix SafetyNet bypass issue.
f2fs: fix potential panic during fstrim
selinux: Apply Fake-Enforcing mode
In Enforcing mode, it actually works in Permissive mode.
Thanks to @jesec
Synapse: minor bug fix
v1.8.0
• Linux 3.18.76 upstream.
• fully merged Note-FE AQH3 firmware sources.
- There are very very many improvements(bad sammy!)
- Not applicable for AOSP binaries• Added boeffla's generic wakelock block driver. by @andip71
• Synapse > wakelock: Add generic wakelock.
• Synapse: Some English translation.
v1.7.0
• Linux 3.18.75 upstream
• Added IPA update for cafactive, ironactive, impulse governors.
• Added relaxed CPU governor
- Conservative based battery-friendly governer, with performance degradation.• ironactive, impulse governor removal.
• Synapse: Added EAS-Tune tab.
- Boost support separated by global, top-app, background, and foreground items.
v1.6.0
Linux 3.18.73 upstream.
Selinux: permissive/enforce mode switching support.
Synapse: Improved to work in Enforce mode.
Synapse: Improved the SynapseLoader add-on to work in Enforce mode.
Synapse: Added SELinux Enforce option.
- More complete SafetyNet bypass & KakaoBank compatible.Synapse: Updated addon (v6.4.0)
Install-zip: Prevent Magisk from reverting kernel init files before.
Install-zip: Added init binary hexpatch to support f2fs conversion of cache partition.
v1.5.2
aosp: Reduce the haptic feedback strength default by 50%.
synapse: misc: Added haptic feedback intensity control to AOSP.
v1.5.1
Enable cgroup_schedtune.
- EAS Schedule tuning (energy or performance) automation support options.
- CFS boost setting is removed accordingly.install-zip: Fixed some bugs in the flashing process.
v1.5.0
Linux 3.18.72 upstream.
G935F-DQIC firmware kernel source merged.
Support AOSP 7.1.2 based custom ROMs.
- Tested: LineageOS, crDroid, RRChanged to AnyKernel method.
Updating the f2fs file system on the f2fs-stable branch.
workqueue improvement.
Apply ADJ_RBTREE to LMK.
Using ARM64 logic on SHA256 / 512.
PWM Flicker Free - Thank's to [email protected]
- information: https://forum.xda-developers.com/s7-edge/development/amoled-pwm-s7-edge-t3517739Synapse - Added WakeLock control.
- Some are not supported in MTweaks, I recommend using Synapse.Synapse: Added CPU Voltage margin setting.
There are many more minor changes.
v1.4.0
EAS: Adding a missing commit.
- Fixed temperature rise problem in some high-end games.GPU: DVFS tuning.
Synapse: Correct default settings when selecting maple IO scheduler.
init: cfs_boost Adjust the default value to 0.
zip-installer: Mali-R12P0 & R15P0 Include the GPU driver in the package.
v1.3.2
Linux 3.18.71 upstream.
changed the source code base to G935FXXU1DQH8.
improved crypto.
fs: updated to the latest in the f2fs-stable branch.
f2fs: support for lazytime mounts.
fstab: support f2fs mount (/system not allowed).
ext4: fix fencepost error in lazytime optimization.
ramdisk: unified with G935FXXU1DQHY base without any 'flat/edge/kor/eur'.
v1.3.0
Disable Exynos-Swap, use ZSwap.
- ZSwap's efficiency is better.Enable zswap_writeback.
Changed the toolchain to gcc-6.4.1 (UBERTC 6.4.1).
Remove the 'perfect C-state residency' related commits.
Back to r12p0 gpu driver.
- Battery efficiency issue of r15p0.Fix synaps FC issue.
- In the case of genuine firmware, FC occurs at the first execution.Optimized & bug fixes for old scripts in synapse.
Ramdisk divided build, global model and Korean model.
- Several issues related to global models.
v1.2.0
Updated with DQH8 firmware source code.
Linux 3.18.15 ~ 70 upstream rework.
NIVIDIA CPU Relax Patch removal.
- In some games, FC or loading loop issue.XPAD Joystick driver update (from Google AOSP 3.18 kernel)
ZRAM, KSM off
- ZRAM is duplicates with VNSWAP
KSM is inefficientSynapse: English translation (90%)
Details(Korean): http://enfree.com/prime/?page=changelog&device=G930

New kernel , i'm going to test now

Tried both with my S8 ROM port.
Boots very slow
When devices i booted it takes some seconds till phone freezes and than reboots!

DirkStorck said:
Tried both with my S8 ROM port.
Boots very slow
When devices i booted it takes some seconds till phone freezes and than reboots!
Click to expand...
Click to collapse
Tell me the name of your custom ROM and the name of your device model.

Hyunwoo AHN said:
Tell me the name of your custom ROM and the name of your device model.
Click to expand...
Click to collapse
My device is SM-G930F and I am using BatMan-Rom V1.3.0
After flashing the kernel I have flashed Magsik 13.6
Thanks

DirkStorck said:
My device is SM-G930F and I am using BatMan-Rom V1.3.0
After flashing the kernel I have flashed Magsik 13.6
Thanks
Click to expand...
Click to collapse
Sorry, can you try again with v1.3.0?

Hyunwoo AHN said:
Sorry, can you try again with v1.3.0?
Click to expand...
Click to collapse
Sorry, my fault. MTweaks was still running what interfered.
Flashed v1.4 with stock GPU drivers. running fine so far but boot time is still longer than with other kernels.
Could you add a global slider to under volt CPU and GPU by a certain value?
EDIT:
In Synapse at "Game Tuner MOD" and "Utility" tab the last few settings are not in englisch

DirkStorck said:
Sorry, my fault. MTweaks was still running what interfered.
Flashed v1.4 with stock GPU drivers. running fine so far but boot time is still longer than with other kernels.
Could you add a global slider to under volt CPU and GPU by a certain value?
Will try this kernel now and report back.
EDIT:
In Synapse at "Game Tuner MOD" and "Utility" tab the last few settings are not in englisch
Click to expand...
Click to collapse
The global slider is hard to implement, because of the UI structure of Synapse.
If you are not comfortable with the Voltage setting, you can get the desired result by returning to Synapse after setting in MTweaks. If you do not know what I mean, try it.
What if it takes a long time to boot? If it is a symptom that only takes longer in the first Bootanimation, it will not be a problem from the second since it recreates the dalvik (ART) cache for some reason.
If it takes a long time to boot each time, it may be because used the G935F ramdisk in this kernel. I tried BatmanROM, but I did not have the problem you said.
In the next version, i will separate ramdisks by variant like v1.3.0.
Korean in the Gametuner-MOD and utility tabs are donation-only functions.
I will translate English donors if they say inconveniences.

Hyunwoo AHN said:
The global slider is hard to implement, because of the UI structure of Synapse.
If you are not comfortable with the Voltage setting, you can get the desired result by returning to Synapse after setting in MTweaks. If you do not know what I mean, try it.
What if it takes a long time to boot? If it is a symptom that only takes longer in the first Bootanimation, it will not be a problem from the second since it recreates the dalvik (ART) cache for some reason.
If it takes a long time to boot each time, it may be because used the G935F ramdisk in this kernel. I tried BatmanROM, but I did not have the problem you said.
In the next version, i will separate ramdisks by variant like v1.3.0.
Korean in the Gametuner-MOD and utility tabs are donation-only functions.
I will translate English donors if they say inconveniences.
Click to expand...
Click to collapse
Ok, tried that with MTweaks and noticed that it was already under volted by my previous settings.
Noticed that there is no tab to disable wakelocks. Do you plan to add this?
EDIT: for now I back to my previous kernel...sorry....
Thanks!

DirkStorck said:
Ok, tried that with MTweaks and noticed that it was already under volted by my previous settings.
Noticed that there is no tab to disable wakelocks. Do you plan to add this?
EDIT: for now I back to my previous kernel...sorry....
Thanks!
Click to expand...
Click to collapse
Kernel-level wakelocks work when requested by an Android system or app.
It is not desirable to force such requests to be ignored.
My Note4 kernel has a wakelock tab. However, it was added because of the deep-sleep problem in some variants of Note4.
If there is a deep sleep (wakelock) problem in our S7, I will add a wake-lock tab.
Again briefly, the wakelock control should not be abused. So, if there are no related problems, I will not add them.

update to v1.5.0

Thanks for supporting AOSP! ?

After flashing 1.5.0 I'm still at 1.4.0 :/

MK73DS said:
After flashing 1.5.0 I'm still at 1.4.0 :/
Click to expand...
Click to collapse
If flashing was completed and there were no errors, it is not possible.
If you rooted or unrooted the kernel after flashing, the old kernel would have been restored.
If you do not know, Flash the kernel after rooting.

Hyunwoo AHN said:
If flashing was completed and there were no errors, it is not possible.
If you rooted or unrooted the kernel after flashing, the old kernel would have been restored.
If you do not know, Flash the kernel after rooting.
Click to expand...
Click to collapse
Indeed, I rooted after flashing the kernel, thank you ^-^

you do a fantastic job with all the feature you added in your kernel(thunderplug,eas, pwm flicker free, etc...). v15 is very recommended

Hey man, thanks for this kernel! I tried it on AOSP for RR which boots but I noticed that flashing this kernel, disabled the option to adjust vibrate intensity. The option in Sound is there but Settings Force Closes when clicking on it. The reason I need to adjust it, is the vibration is back to really strong vibration when touching a key. Hope this details helps. On latest Prime 1.5.0

Andrw0830 said:
Hey man, thanks for this kernel! I tried it on AOSP for RR which boots but I noticed that flashing this kernel, disabled the option to adjust vibrate intensity. The option in Sound is there but Settings Force Closes when clicking on it. The reason I need to adjust it, is the vibration is back to really strong vibration when touching a key. Hope this details helps. On latest Prime 1.5.0
Click to expand...
Click to collapse
issue was raised on edge thread.
https://forum.xda-developers.com/s7-edge/development/kernel-prime-kernel-v1-4-0-t3678159/page5

[KERNEL] lunar-kernels for LG V30

[LG][V30][V30s][KERNELs] lunar-kernels for LG V30
There's one main name of the kernel variants: lunar kernels
the variants include:
Kernels for LG Stock Oreo ROM + AOSP Pie ROMs (with LG Stock Oreo drivers) ["Oreo driver generation ROMs"]
-------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------
EAS kernels [LG Stock Oreo, AOSP Pie]:
-------------------------------------------------------------------------------------------
Elisa (EAS on stock base + my/additional stuff)
Orion (EAS on linux-upstream + CAF updates + my/additional stuff)
-------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------
HMP kernels [LG Stock Oreo, AOSP Pie]:
-------------------------------------------------------------------------------------------
Marduk (HMP on linux-upstream + CAF updates + my/additional stuff)
Ceres (HMP on CAF/LG Oreo kernel base + CAF updates + my/additional stuff)
-------------------------------------------------------------------------------------------
Kernels for LG Stock Pie ROM + AOSP Q ROMs (with LG Stock Pie drivers) ["Pie driver generation ROMs"]
-------------------------------------------------------------------------------------------
HMP kernels [LG Stock Pie, AOSP Q / Android 10]:
-------------------------------------------------------------------------------------------
Haumea (HMP on LG Pie stock base + CAF updates + my/additional stuff)
-------------------------------------------------------------------------------------------
Warning:
using Haumea on Oreo LG Stock and older AOSP versions (all Pie AOSP ROMs except Lineageos 16 beta with LG Stock Pie drivers) *CAN* and *WILL* cause trouble on those
no guarantees for device safety (charging heating, battery health, etc.), functionality (camera functionality, Wifi, etc.) and stability !
-------------------------------------------------------------------------------------------
The opposite applies as well:
Warning:
using Elisa, Orion, Marduk, Ceres on Pie LG Stock and newer AOSP versions (Android 10 / Q, lineageos 16 beta with LG Stock Pie drivers) *CAN* and *WILL* cause trouble on those
no guarantees for device safety (charging heating, battery health, etc.), functionality (camera functionality, Wifi, etc.) and stability !
-------------------------------------------------------------------------------------------
*my/additional stuff can include CAF updates, backports from up to 5.x kernels
** in addition to that there's partially features from jollaman999's jolla-kernel for joan (LG V30 family) in some kernels
jolla-kernel specific features include:
- additional ARP spoof protection
- dynamic fsync (only syncing/flush when screen is off, while screen is on no sync) [removed since I ran into data loss issues]
- sovc - screen off volume control / screen gestures
lunar-kernel specific features include ( #fixme )
(Seems like the download link got eliminated for some reason):
main folder for all lunar kernels:
https://drive.google.com/open?id=1xL5gEiG-fjzTuSGM_kUDsrOKy-jTtGr1
main folder for all ceres kernels:
https://drive.google.com/open?id=16ZrJD1IX9f9CkGILWBXtf6NOtes3W9_I
08.2019 ceres kernels folder:
https://drive.google.com/open?id=1Nne8uE1XFhPrVjhM7K74zWd9N5R4JLU1
XDA:DevDB Information
Zach's Kernel Workshop mk3 (V30), Kernel for the LG V30
Contributors
zacharias.maladroit, SGCMarkus, jollaman999
Kernel Special Features:
Version Information
Status: Testing
Created 2019-05-27
Last Updated 2019-08-11

Can I use any of these with h932?

Vuzeultra said:
Can I use any of these with h932?
Click to expand...
Click to collapse
The ones that are anykernel2, try flashing them. They should be compatible

I tried to install the Anykernel zip from TWRP 3.3 but it failed for me. The problem was that the installation script waited for the vol key initialization and got stuck there. Any idea?
Should this kernel work with Liquid Remix 10?

Thanks for the kernels
Stuck at "Starting Vol Key Options" in TWRP with the latest Orion kernel with Havoc.
Perhaps a precis on which kernels work with which roms?

So enlighten me, why should I install this kernel? What advantages are to be gained?

elhennig said:
I tried to install the Anykernel zip from TWRP 3.3 but it failed for me. The problem was that the installation script waited for the vol key initialization and got stuck there. Any idea?
Should this kernel work with Liquid Remix 10?
Click to expand...
Click to collapse
Use 3.2.3-7. 3.3 is experimental and buggy.

Alright, kernel time!
First, thanks for all of the hard work, and for releasing the kernel.
I just flashed AnyKernel2_orion_II_WIP3_4-7_t2_LGstock_AOSP_H on my H932, running the stock debloated 20s from this thread https://forum.xda-developers.com/lg-v30/development/stock-t-mobile-lg-v30-stock-collection-t3917560. I haven't had much chance to test yet, but it booted fine and so far is running good. Only thing is that the SD card is read as corrupted, but I saw that in the old thread, so no surprises there.

Every kernel zip I try to flash in TWRP hangs at Starting Vol Key Options...
TWRP is 3.3.0-00-no_decrypt
Currently running Havoc 2.5, latest build.

joarce said:
Every kernel zip I try to flash in TWRP hangs at Starting Vol Key Options...
TWRP is 3.3.0-00-no_decrypt
Currently running Havoc 2.5, latest build.
Click to expand...
Click to collapse
flash TWRP 3.2.3.
TWRP 3.3.0 is a bit buggy.

joarce said:
Every kernel zip I try to flash in TWRP hangs at Starting Vol Key Options...
TWRP is 3.3.0-00-no_decrypt
Currently running Havoc 2.5, latest build.
Click to expand...
Click to collapse
I had the same problem. It works fine with TWRP 3.2.3-7
Thanks again to @cascabel

itachilinux said:
flash TWRP 3.2.3.
TWRP 3.3.0 is a bit buggy.
Click to expand...
Click to collapse
elhennig said:
I had the same problem. It works fine with TWRP 3.2.3-7
Thanks again to @cascabel
Click to expand...
Click to collapse
Thanks! That did it

orion_II_WIP3_4-8_t3_2 is now available on GDrive,
will follow suite on XDA
Changelog orion_II_WIP3_4-8_t3_2 (from orion_II_WIP3_4-7_t2) said:
- lowered compaction threshold for fragmentation back to default (earlier compaction, better success for allocations/app launches, etc.)
- simple_lmk: updated to latest incarnation of kerneltoast
- q6dspv2: glink priority upgrade for low latency audio (less stutter)
- wcd934x: Increase port disconnect timeout to 1.6sec
- less logspam from msm-pcm*
- [HOTWORD DETECTION] wdsp: reset spi clk user if enable fails [Test: verify hotword/music detection, trigger WDSP crash manually]
- sound system fixes
- Convert few critical drivers to use msecs_to_jiffies insted of HZ
- re-enable TTWU_QUEUE for scheduler
- removed sdFAT - worthless for now, cutting cruft
- re-enable SW AINUR DTS driver (DTS ULTRA support)
- Makefile: add various optimization flags to speed up kernel
- network speed/netsched: switch back to pfifo_fast from cake - higher throughput [regression fix ?]
- silence workqueue
- msm: mdss: Speed up MDP interrupt processing for cmd mode panels
- msm: camera: Undo pm_qos request upon error ["if anything fails, the pm_qos request won't be undone and will waste power"]
- scsi: ufs: Only apply pm_qos to the CPU servicing UFS interrupts
- mm: vmstat: use power efficient workingqueues
- proc: Remove verifiedbootstate flag from /proc/cmdline
- proc: Remove additional SafetyNet flags from /proc/cmdline
- other changes
various backports:
- [4.6] mmc: core: enable mmc host device to suspend/resume asynchronously
- mmc: core: Convert from IDR to IDA for host indexes
- mmc: host: create a specific workqueue for clk gate [deadlock fix]
- mmc: core: Add a facility to "pause" re-tuning
- mmc: card: Service RPMB requests with priority over other
- genirq/affinity: smarter irq spreading
- sched/cputime: Improve scalability by not accounting thread group tasks pending time
- [4.7] ext4: allow readdir()'s of large empty directories to be
- [4.12] ext4: avoid unnecessary transaction stalls during writeback
- compaction: speed ups/fixes
- rcu: Speed up calling of RCU tasks callbacks [from ~ 1s to ~ 0.1s]
- fix potential crash/issues in usb: gadget: f_accessory
- slimbus: slim-msm: Handle system suspend while active slimbus transfers
- msm: kgsl: Remove excessive log in kgsl_snapshot_get_object
- msm: kgsl: Fix NULL pointer dereference
- devfreq: Use busy cycles only for GPU bandwidth decisions
- devfreq: Weight stall cycles more for GPU bus DCVS
tl;dr
- stability improvements
- faster syncing = faster installs, etc.
- quicker
- less power consumption
- higher reliability for HOTWORD detection (?)
- smoother/faster (less overhead)
Click to expand...
Click to collapse
Changelog orion_II_WIP3_4-7_t2 (vs. orion_II_WIP3_4-7): said:
- reverted pinctrl subsystem changes
- [re-apply] disable LB_BIAS by default
- sched/fair: improve big task placement
- Revert "ANDROID: sched/fair: always start with the biggest CPU"
- sched/fair: if sync flag ignored, try to place in same
- Revert "ANDROID: sched/fair: Fix incorrect usage of RCU in CPU select path
- sched/core: Replace sd_busy/nr_busy_cpus with sched_domain_shared
- sched: Per-Sched-domain over utilization [EAS/energy-aware scheduling in over-utilizing scenarios]
- sched/fair: Update overutilized status after migrating tasks
- [BACKFILL] sched: fair: avoid little cpus due to sync, prev_bias
Click to expand...
Click to collapse
Changelog orion_II_WIP3_4-7: said:
- qseecom security updates
- dsboost (dynamic stune boost *only* based boosting mechanism without explicit / fixed boost frequency, scheduler/EAS decides frequency and task placement)
- sched/fair: Skip pulling tasks from cpu marked for active balancing
- disable AINUR_SW (DTS:X Ultra support)
- genirq fixes
- irq: Silence IRQ CPU migration message
- fs/writeback.c: use rcu_barrier() to wait for inflight wb switches going into workqueue when umount (fix NULL pointer dereference)
- mm/vmalloc: up to 67-70% less time (improved performance), thanks to Uladzislau Rezki from sonymobile
- [eval] mm: Compact memory mostly when fragmentation occurs (rather than lack of available memory)
- TCP: disable syncookies (performance)
- TCP: tweakings (internet throughput)
- TCP: disable ping by default
- TCP: disable SACK, FACK, DSACK by default
- use DSBOOST
- add extraversion to kernel (git hash to make it easier identifiable)
Click to expand...
Click to collapse

CC: @privaatcharlie
I would put a finger pointing at the post above but there are no such smilies
that's only a small fraction of the changes and features included in the kernel
if I find some I might add some more changes to that list
joarce said:
Thanks for the kernels
Stuck at "Starting Vol Key Options" in TWRP with the latest Orion kernel with Havoc.
Perhaps a precis on which kernels work with which roms?
Click to expand...
Click to collapse
It should work for all the AOSP ROMs , latest LG Stock ROMs ymmv (your mileage may vary) - there have been issues reported with 22j but that's natural since
the libraries, vndk version, kernel version etc. aren't quite in unison (AOSP is Pie, LG Stock ROM is Oreo).

Is one of the issues with 22j is that magisk keeps getting uninstalled for no reason? Or am I doing something wrong

WindowsPhone8.1User said:
Is one of the issues with 22j is that magisk keeps getting uninstalled for no reason? Or am I doing something wrong
Click to expand...
Click to collapse
It happens once to me every time i flash a new kernel (even stock after being on a custom kernel). Just reboot. Hasn't happened for a few days now.

I'm sorry i can't find the orion_II_WIP3_4-8_t3_2 kernel in the Gdrive folder what am I missing?
plus i had a video recording issue with the orion_II_WIP3_4-7_t2 build. Videos didn't play through any app after recording.
EDIT: Video recording issue fixed in the 4-8_t3 build ??

I've got a few hours in on this update, going good so far. Feels smoother.
Oppoxda said:
I'm sorry i can't find the orion_II_WIP3_4-8_t3_2 kernel in the Gdrive folder what am I missing?
plus i had a video recording issue with the orion_II_WIP3_4-7_t2 build. Videos didn't play through any app after recording.
EDIT: Video recording issue fixed in the 4-8_t3 build
Click to expand...
Click to collapse
What's your device? Twrp version? Just checking, as if you look a few posts up, TWRP past a certain release has some weirdness to it.
If you click the drive link, go to Orion-kernels -> Orion kernels_05.2019 -> kernel_file_here

So one of the Elisa builds says "stock" but also "AOSP". Will that work with Oreo on a VS996(Verizon)? I thought AOSP was more for Pixel-like devices.
EDIT: It's the AnyKernel2_elisa_I_WIP3_6_LGstock_AOSP_H930.zip Kernel

TheCoryGuy said:
So one of the Elisa builds says "stock" but also "AOSP". Will that work with Oreo on a VS996(Verizon)? I thought AOSP was more for Pixel-like devices.
EDIT: It's the AnyKernel2_elisa_I_WIP3_6_LGstock_AOSP_H930.zip Kernel
Click to expand...
Click to collapse
I'm on vs996 ROM and haven't been able to successfully boot with the Elisa kernel. Have had better stability with the stock Orion's. However my device is an unlocked V30S US998 so that might be why ??*

Develop Bugs

welcome