Develop Bugs

[KERNEL] [ROOT] [SM-G928P] Exynos 7420 | SkyHigh Kernel

[KERNEL] [ROOT] [SM-G928P] Exynos 7420 | SkyHigh Kernel [ v6.8.0-EOL ] | Synapse | Aroma | F2FS | UBERTC 6.2.1 20161012
The BEST & FULLY FEATURED EXYNOS 7420 KERNEL IS REBORN . . . . .
Many select patches for better security, performance and efficiency (not all listed). THERE IS "NO NEED" to tweak anything -- Just FLASH it !! But, if you desire, can further tweak many settings and available features with Synapse to suit your own habits and device capability. That is for you to find out
SUPPORTED DEVICES:
SM-G928P​
RAMDISK BASE:
G928P : G928PVPS3BPJ2 ​
FEATURES:
Modified from the LATEST device specific official Samsung source(s): Samsung OSRC
AUTO-ROOT SYSTEM-LESS SR3-SuperSU-v2.78 (on flash)
KNOX WARRANTY VOID: 1
SELinux PERMISSIVE (default) or ENFORCING
DEEP SLEEP FIX
UX ROM (BOOT support only)
AROMA Installer (set your own defaults)
Auto-Install busybox v1.24.1-Dorimanx & Sqlite3 to /system/xbin (on flash)
Compiled with UBERTC 6.2.1 20161012 + Graphite optimizations
Linux 3.10.104
init.d script support (drop in script & set permissions to 755 or 777 and reboot)
adb insecure
stock dt.img
Secure storage = false (should prevent WIFI settings & passwords wiping on reboots)
Reduced logging
F2FS experimental support (Much faster I/O - write speeds).
exFAT FS support
NTFS R/W support with app
CIFS support (not tested)
ISO 9660 CDROM & UDF FS support
Frandom
mount all partitions NOATIME (better performance & efficiency)
mount EXT4 /data & /cache partitions LAZYTIME (better performance & efficiency)
A53 LITTLE cores increased boot frequency (faster boot)
LZO ramdisk de/compression algorithm (faster boot)
CLEANCACHE & ZCACHE
Microsoft X-BOX gamepad controller module (updated)
Slub tweaked
Invisible CPUSETs (better efficiency)
A tonne of select patches for features, better performance & efficiency
Synapse app support for many kernel configurations + much much more !!
SYNAPSE FEATURES:
Too many too list . . . Have a look through Synapse yourself. If you don't know, then read and research or leave it DEFAULT !!
About
A57 CPU frequency scaling
A57 voltage control
A53 CPU frequency scaling
A53 voltage control
CPU governor
A57 governor tunables
A53 governor tunables
Multicore
CPU stats
Boost
GPU frequency scaling
GPU voltage control
Thermal
BUS
IO
Memory
Advanced
Power Suspend
Doze
Wakelocks
Audio
Battery
LED
Screen
Network
Security
FS (file system)
CortexBrain
Crontab
USB mode
Modules
Backup & Restore profiles + EFS (auto on boot to /sdcard/SkyHigh/EFS)
Logs
Reboot
Info
CREDITS:
My family !!
Chainfire - root & SuperSU app
AndreiLux - years of support for Exynos development and his various kernel features + Synapse app and UCI code
halaszk88 - patches and some Synapse code I adapted to many of my kernels
dorimanx - BusyBox and various ramdisk tweaks/ideas
apb_axel - I adapted and used many of the Synapse controls to suit my kernels
arter97 - various source fixes/patches
ktoonsez - ktoonservative hotplug governor
YashdSaraf - BusyBox-Cleaner script
Android File Host
Linus Torvalds & Linux Foundation
Google & Samsung OSRC
and many others!
All those in my select private group that have provided constructive feedback, help, and support.
IF I'VE FORGOTTEN ANYONE, PLEASE DON'T BE SHY AND SPEAK UP, THANKS
XDA:DevDB Information
SkyHigh Kernel for G928P devices, Kernel for the Sprint Samsung Galaxy S6 Edge+
Contributors
UpInTheAir
Source Code: https://www.androidfilehost.com/?w=files&flid=125583
Kernel Special Features: Aroma - Synapse ++ almost everything !!
Version Information
Status: Stable
Current Stable Version: 6.8.0-EOL
Stable Release Date: 2016-11-19
Created 2016-08-15
Last Updated 2016-11-19

License - requirements - installation - download - source
DON'T POST LAME QUESTIONS THAT YOU CAN FIND THE ANSWER TO BY A LITTLE SEARCHING.
I AM NOT GOOGLE & NEVER PRETEND TO KNOW EVERYTHING, SO A LITTLE HELP FROM YOURSELF WILL GO A LONG WAY. . .
THANKS & ENJOY !!
** LICENSE & DISCLAIMER **
/*
© Copyright (c) 2015-2016 UpInTheAir <[email protected]>
All rights reserved. The alterations from OEM, associated script files and coding packed within this ramdisk & installation package (the "Software"), may not be reproduced, displayed, modified or distributed without the express prior written permission of the copyright holder. For permission, contact [email protected].
The above copyright notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF , FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
*/
In plain language
DO NOT STEAL MY SH*T !!
UpInTheAir is NOT responsible, the person you see in the mirror is !!
REQUIREMENTS:
Supported variant only !!
Touch Wiz Android M 6.0.1 ROM or UX leaked firmware (beta support)
Appropriate custom recovery (i.e..TWRP for your variant)
INSTALLATION & UPDATE:
If you have Synapse installed = = you must clear Synapse app data before flash !!
Device Settings: Enable Developer Options > OEM UNLOCK is ENABLED
Boot into custom recovery (volume UP + home + power)
DO NOTHING but flash SkyHigh kernel.zip (ALWAYS flash again AFTER any custom ROM installation, system or data wipe)
After flash == DO NOTHING but REBOOT IMMEDIATELY from TWRP or you will have to re-flash !!
CONVERT EXT4 TO F2FS FS:
If not already, install the latest TWRP for your device variant (ie. 3.0.2-2). This must support F2FS.
Boot into TWRP.
Insert USB-OTG
** ALL DATA WILL BE WIPED FROM INTERNAL STORAGE (restored later)
Backup (copy) all important files (incl. your NANDROID) off device (ie. from internal storage > USB STORAGE). This can take a while. Advanced > File Manager > .....
Home > Backup > Select Storage > USB Storage > OK > "Swipe to Backup" (Only need DATA, but recommend to backup all partitions).
Install > Select Storage > USB Storage > OK.
Select f2fs.zip > "Swipe to confirm flash" (This will WIPE ALL DATA !! & convert DATA & CACHE to F2FS. System is not supported by kernel).
Check the box to remember setting and “Swipe to allow Modifications”.
If you do not have Step #8, then Data was not converted to F2FS.
Mounts > unchecked both Cache & Data. Repeat Step #7 & 8.
Restore > Select Storage > USB Storage > OK > Select TWRP Backup folder > DATA ONLY !! > "Swipe to Restore" (ignore warning about EXT4).
Home > Install > Select Skyhigh_kernel.zip > "Swipe to confirm Flash".
Home > Mount > USB STORAGE > uncheck/unmount (then remove USB-OTG).
Home > Reboot > SYSTEM.
Wait ~2-5 mins for boot.
Once booted, let stabilize for ~5 mins.
You can check Data & Cache F2FS FS status in either /proc/mounts or Synapse app (FS section).
Use a root type explorer (su permission) & navigate to /sdcard, and delete the "0" folder.
Move (copy) your backed up files from Step #4 to internal storage (/sdcard). This can take a while. Maybe one folder at a time is better?
ISSUES ?
If using TWRP MTP mode, deleting some folders/files may crash TWRP and cause corruption. Instead, use a root type file explorer to delete from device.
If you need to wipe data, then use the ext4 or f2fs.zip, otherwise this is not possible with this TWRP !!
Not tested any method with customized ROMs. The ROM installer script may re-format partitions back to EXT4 or not mount correctly causing TWRP crash or corruption. I can only suggest to Flash ROM with EXT4 FS > make a NANDROID on USB-OTG and then follow the F2FS steps above.
CONVERT F2FS TO EXT4 FS:
The Same steps as above, but use the ext4.zip !!
OPTIONAL SYNAPSE INSTALLATION:
After boot:
Wait at least 120 secs to stabilize
Install Synapse app from Google Play and rate it ☆☆☆☆☆ !!
Open Synapse
Tap "Understood"
So changes stick every time you start Synapse == Make any change & 'apply'.
Recommend: Disable KNOX with Synapse
DOWNLOADS:
Mod Edit: Link removed.
BUGS:
Aroma Installer: 10% of installation will encounter Aroma installer "freeze". It's only the display that freeze, the script still execute in the background. Just wait a minute, then press slightly to the top right 'home' key / top left of the 'back' key . . .
UX BETA firmware - blue light filter
UX BETA firmware - torch light (some ROMs)
HD voice ? - Speakerphone: other party cannot hear voice
SOURCE - ALL SkyHigh VARIANT:
Available upon request..
v6.6.1 AFH
v6.8.0 uploaded soon. . . . .
.

FAQ & HELP
TROUBLESHOOTING GUIDE:
I might not have your device variant and or able to reproduce your "issue".
Please provide as much information as possible.
Without resetting your device to a stable unmodified baseline, any potential troubleshooting or logs could be meaningless.
So please follow the guidelines set out below. Users can't "read minds".
Without providing important information, we are unable to help YOU.
Search thread, XDA and Google before posting
Provide as much information as possible.
- Device model
- Firmware version
- ROM name / version
- Kernel version
- Modem version
- Bootloader version
- Synapse settings (try default)
- Installed tweaks and apps etc (Xposed ?)
- The exact steps you've taken to try resolve the issue yourself.​
Exact steps to reproduce the issue. Provide screenshots if able.
Does it work with older / other versions etc
Reset your device to a stable baseline (ie. stock) with only custom TWRP recovery and kernel (FULL WIPE: system, cache, dalvik-ART)
Possible logs
FAQ & HELP:
CAN I BUILD A KERNEL FOR YOUR __XX DEVICE ?
Sorry. I don't have the spare time for any more variant support.
Additionally, I do not build for any device that I can not compile using SAME source, personally test method or debug. Some device variants can compile with same source.
CAN I INCLUDE SkyHigh KERNEL IN MY ROM
NO == My ramdisk modifications are COPYRIGHT (refer LICENSE in Post #2), and distribution without MY (UpInTheAir) prior written consent is not only in a breach of that license, but also XDA Rule #12)
Although I do appreciate your contribution, if you could please do not include my kernel in any ROM package etc. This policy goes for anyone.
Having my kernel distributed outside my development thread just removes a lot of credit and more importantly, constructive user feedback that could be helpful to my development or user issue.
ALWAYS on DISPLAY (AoD)
I have spent some time to attempt port S7 display drivers to our kernel, but haven't had success as yet with too many errors.
TBH, it's a lot of work for something I'm not really interested in or would use. . . so I don't wish to spend any more of my own time on it, sorry. If someone else does it, GREAT
DO I "NEED" SYNAPSE
THERE IS NO "NEED" !!
It is "recommended", which is OPTIONAL, and not "needed".
It is for ADVANCED or adventurous users who wish more control of their device or use various features I've added.
Using any other optional tweaking or control app may conflict & many features and options won't be available.
WHY WAIT 120 SECS
The kernel and Synapse scripts need time to boot up properly and allow SU permission.
There are scripts / code that have a deliberate delay and must run after Synapse. These are not user optional.
Synapse has a stability check on boot. You may get "synapse boot cancelled".
Thermal throttling will be trying to limit many things, let the device settle
OTHER PARTY CAN NOT HEAR VOICE ON SPEAKER PHONE
It could be a conflict in the system/etc/mixer_*.xml. I don't know for sure, but if I exclude the sound mod, then this "fixes" the problem.
As I cannot reproduce the issue (and the majority), then the audio mod stays.
Unfortunately, making it optional would require to build kernels without and create much more work for many device I don't actually use.
Either live with it, or use another kernel. Sorry.
"NO UCI SUPPORT"
It's a ROM busybox compatibility issue !!
Re-flash kernel as per Installation Instructions. (kernel install zip flashes proven busybox binary to /system/xbin)
BACKUP / RESTORE ISSUES
It's a ROM busybox or sqlite3 compatibility issue !!
Re-flash kernel as per Installation Instructions. (kernel install zip flashes proven busybox binary to /system/xbin)
BACKUP & RESTORE
DO NOT restore profiles from different kernel version
Refer to THIS post for "how-to" screen-shots
Refer to THIS post for a "how-to" video
LOADABLE MODULES AREN'T WORKING
Check your /system/lib/modules directory. Are any ____.ko present?
Did you flash a ROM or wipe the system partition at any point? Doing this will remove them !
Re-flash the kernel will install the modules.
If modules aren't installed after flash, then re-flash and manually mount system in recovery first.
You can check running modules in terminal with:
​lsmod
KTOONSERVATIVE GOVERNOR
Some info from the author HERE
DT2W & COLOUR CONTROL
No, I cannot make it work properly with single source for all supported variants
CPU POWER CONSUMPTION
The Samsung Exynos 7420 Deep Dive - Inside A Modern 14nm SoC (by ANANDTECH - Andrei)
F2FS SUPPORT
It's not needed. You wouldn't see any difference or measure much, if anything. Not worth the potential trade-off. This is not eMMC anymore
Storage Benchmarks
STUCK ON SAMSUNG BOOT LOGO AFTER FLASH
Ensure you flashed the correct kernel for your device model
Ensure your download is not corrupted. Check MD5 hash or re-download
Your current base firmware (ROM, boot-loader version etc.) may be incompatible - UPDATE to latest with Odin and try again.
CM SUPPORT
Read THIS
BATTERY TIPS (require updating !! )
Try some (or combination) of the CPU MULTICORE features in Synapse:
HMP profile = Default (values are battery orientated)
Power Aware Scheduling (slight performance cost) = Enabled
HMP LITTLE Packing (slight performance cost) = Enabled
PEWQ (power-efficient workqueue) (slight performance cost) = Enabled
Set A57 & A53 Interactive governor profile = Battery
Set Input-Booster for key/touchkey profile = Battery
Multi-tasking: enable UKSM & "low" or "quiet" profile (slight performance/battery cost)
PERFORMANCE TIPS (requires updating !! )
Set A57 & A53 Interactive governor profile = Performance
Set A57 & A53 Interactive governor = Turbo Mode (battery cost)
Set HMP threshold profiles = Stock or Performance
Once in a while:
Optimize Databases
FSTrim​
RANDOM REBOOT
Don't UV or UC CPU or GPU
Use SkyHigh defaults
Use a stock UNMODIFIED ROM for your device variant
No tweaks, Xposed or other CPU control apps installed
Follow the TROUBLESHOOTING GUIDE
ASV_GROUP (ALL DEVICES ARE NOT CREATED EQUAL)
THIS is an example from my Exynos5420 source. Similar idea for Exynos4
DOWNLOAD LINK NOT WORKING
I want to keep this project all in one place - ☆☆ NO MIRRORS ☆☆
Please try again in a few minutes
POOR CPU/GPU BENCHMARK or GRAPHICS PERFORMANCE
Disable any CPU MULTICORE options in Synapse
Disable any Battery profiles in Synapse. Set to default or Performance.
Allow the device to cool. Repetitive testing will heat the device hardware and invoke thermal throttling and lead to decreased benchmark.
HIGH CPU/GPU OC == excessive heat == thermal throttling == reduced clock frequency == DECREASE PERFORMANCE
DYNAMIC MANAGEMENT OF DIRTY PAGE WRITEBACKS
by Christopher83
This feature allows to have two different intervals for dirty page writebacks and to dynamically manage them when the system has been resumed (it's active) or when has been suspended.
Three new procfs parameters are exposed inside /proc/sys/vm path:
dynamic_dirty_writeback is the activation status of this feature, set 1 to enable it, set 0 to disable it and use the standard behaviour
dirty_writeback_active_centisecs is the interval for the dirty page writebacks when the system is active (screen on)
dirty_writeback_suspend_centisecs is the interval for the dirty page writebacks when the system is suspended (screen off)
This feature is in part inspired on Francisco Franco's PATCH
TCP/IP NETWORK SECURITY
Thanks to zeppelinrox & V6SuperCharger
Hardening the TCP/IP stack to SYN attack
Bump up tw_buckets in case we get DoS'd
Ignore pings
Don't cache connection metrics from previous connection
Don't pass traffic between networks or act as a router
Enable spoofing protection (turn on reverse packet filtering)
Don't accept source routing
Don't accept redirects
Further reading:
http://www.cyberciti.biz/faq/linux-kernel-etcsysctl-conf-security-hardening
http://www.symantec.com/connect/articles/hardening-tcpip-stack-syn-attacks
CHROMECAST - STREAMING PROBLEMS
Lock screen MUST be enabled (simple screen lock swipe) I don't know why but it breaks the chromecast app's ability to resume smoothly if switched off
Synapse > Network > DTIM (both screen ON & OFF) = 1
Synapse > Network > WIFI Power Mode (screen OFF) = FAST

v5.8 released
SkyHigh KERNEL REBORN - v5.8 released !!
Hi fellow members.
Please find my latest release for SkyHigh kernel. There are many many changes, both visually (more / improved features) and a upgraded engine (better performance & efficiency) since I last publicly released. Far too many to talk about. . . .
Please note that although I have taken as much care in building and testing by my friends and I, the kernel may still not perform as hoped for you. Could be due to various factors including (but limited to):
hardware quality
firmware installed (incompatibility)
user habit (how you use the device)
apps & mods installed, customization's (conflicts)
user kernel settings (read them carefully - if in doubt == defaults)
As noted in Post #3, I may not have your device variant and not be always able to help either. In the end, sometimes SkyHigh is just not meant for you . . . .
If you have issues = = READ & FOLLOW ALL Posts #1-3
READ & FOLLOW THE INSTALLATION INSTALLATIONS EXACTLY (or else device will not boot)
Also please note (as per OP) the support for UX based ROMS is still in beta. I have personally tested very briefly, and also some of my friends (not all variant). I don't believe this kernel will fix the no call audio issue for those UX ROMs. It is ROM related !!
Enjoy
UITA
.

Thanks the "Ps" appreciate your time and efforts.

I know I do appreciate your time. Thank you
Sent from my SM-G928P using Tapatalk

Thank you, Sir. This is wondrous news! Much appreciation.

v5.8.1
v5.8.1 Minor update for all supported Galaxy S6 Edge Plus variants.
Enjoy

Heavy usage all day yesterday
Better battery
No lag what so ever
1 random reboot in the middle of the night while charging and not using

MonkeyAround said:
Heavy usage all day yesterday
Better battery
No lag what so ever
1 random reboot in the middle of the night while charging and not using
Click to expand...
Click to collapse
I suppose it occurred at the time battery was either full or 100% ? I've 2 of those on my N920C whilst on data and standard mains AC charging since v5.6. Battery was either full and or indicating 100%. Only happened (for me) since later kernel source merges. I thought I fixed it 5.6 - 5.8, but maybe not entirely. Could be firmware variant inconsistencies and or stock dt.img.
Unfortunately it's rare (meaning difficult to reproduce the bug so a solution can be found), and I just don't have time to look into things for a long time.
UN-recognized Developer of my SkyHigh Kernel v5.8.x powered SM-N920C

This might be a newby question, but, would a Rooted Stock be able to use this Kernel? I'm guessing you must have a Rom?

SprintBama said:
This might be a newby question, but, would a Rooted Stock be able to use this Kernel? I'm guessing you must have a Rom?
Click to expand...
Click to collapse
If your device meets the requirements in Post #2
UN-recognized Developer of my SkyHigh Kernel v5.8.x powered SM-N920C

Is something wrong with Android File Host? Cannot download...

N920P Tester needed
If you are capable and willing to test G928P SkyHigh kernel pre-release on full stock firmware G928PVPU2BPG1 ??
Just require ONE (THE FIRST TO REPLY) that can work around flashing and recovery WITHOUT anyone holding your hand.
Without proper testing and decent informed feedback, there will be no official release for you. I've spent a lot of time on this for just a few users here. There aren't many appreciative, since I don't even have device.....
Cheers
UITA
UN-recognized Developer of my SkyHigh Kernel v6.x.x powered SM-N920C

I'll do it. I'm always appreciative for any work to our device.
Sent from my SM-G928P using Tapatalk

nowerlater said:
I'll do it. I'm always appreciative for any work to our device.
Sent from my SM-G928P using Tapatalk
Click to expand...
Click to collapse
Okay.
All I require to finish this test build is the stock G928PVPU2BPG1 boot.img. If you don't have it, then it can be extracted from the full firmware package http://www.sammobile.com/firmwares/download/84809/G928PVPU2BPG1_G928PSPT2BPG1_SPR/ . I need it unmodified.
I can't guarantee much on this, full fresh build on top of your device specific source. A few changes along the way, which could affect stability or boot. etc. No idea.

I'll get it to you ASAP
Sent from my SM-G928P using Tapatalk

UpInTheAir said:
Okay.
All I require to finish this test build is the stock G928PVPU2BPG1 boot.img. If you don't have it, then it can be extracted from the full firmware package http://www.sammobile.com/firmwares/download/84809/G928PVPU2BPG1_G928PSPT2BPG1_SPR/ . I need it unmodified.
I can't guarantee much on this, full fresh build on top of your device specific source. A few changes along the way, which could affect stability or boot. etc. No idea.
Click to expand...
Click to collapse
https://www.dropbox.com/s/qts6z1f89sqv6e9/boot.img?dl=0
Sent from my SM-G928P using Tapatalk

nowerlater said:
https://www.dropbox.com/s/qts6z1f89sqv6e9/boot.img?dl=0
Sent from my SM-G928P using Tapatalk
Click to expand...
Click to collapse
I'm out getting the car brakes repaired. Will build as send to you for test later. Please make sure your device is prepared with full stock (Same as boot.img) and TWRP. NO other mods, tweaks, xposed or crap. We need to test the "kernel" [emoji3]
UN-recognized Developer of my SkyHigh Kernel v6.x.x powered SM-N920C

I can also test if you need me to, I'm currently running G928PVPU2BPG1 with the kernel from the OP with otherwise stock firmware and all is working fine.

[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 ??*

[ROM][EXYNOS] LineageOS 18.1 for S10e|S10|S10+ - v2.2 (UPDATE: 2021-07-23)

- - - - - -
This project provides LineageOS with SELinux for the Samsung Galaxy S10e (SM-G970F, beyond0lte), S10 (SM-G973F, beyond1lte) and S10+ (SM-G975F, beyond2lte).
- - - - - -
{
"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"
}
FEATURES
We provide a secure and up to date ROM, check the Lineage Trust status of your phone!
Secure ROM
Fine-grained SELinux policy
Latest 4.14 Linux Kernel release
Improved performance
Wireguard support
USB restrictions
AES-256-XTS File Based Encryption (FBE)
Signed with developer keys
Nice features
FDroid and AuroraStore preinstalled
Bluetooth phone calls
KNOWN ISSUES
Don't be scared by the "BETA" label. Our ROMs are always rock solid.
Some audio effects are missing
Miracast not working
Wideband SCO
IMS not working (No AOSP solution yet)
Some minor issues are described in the FAQ below.
DOWNLOAD
You can download the latest version under the following links:
S10e
S10
S10+
INSTALLATION
Put the zip file of the ROM on your external SD card boot into recovery. If you use our TWRP recovery, you should use that one to flash the ROM.
Make sure you select: Zip signature verification.
This will verify that the signature of the ROM will match the one in TWRP recovery. A more detailed step by step description is in the FAQ below.
SECURITY ADVICE
Don't flash Magisk modules or anything else which sets SELinux to permissive or you open your device for malware!
Do not flash Multi Disabler on this ROM!
What a Wurst!
This ROM is developed by derf elot, linux4 and modpunk
Contributors
modpunk, derf elot, linux4
Source Code: https://github.com/whatawurst
ROM OS Version: Android 11
ROM Kernel: Linux 4.14.236
ROM Firmware Required: XXSBFUF3
Based On: LineageOS

REQUIRED FIRMWARE: XXSBFUF3
CHANGELOG
2021-07-23 | 2.2
Update to Linux 4.14.239
2021-06-23 | 2.1
Update to Linux 4.14.236
Fixed GPS
Improved autobrightness (Thanks to linux4)
2021-06-07 | 2.0
Added support to disable fast charging
Kernel fix to disable the touchscreen during handheld phone calls
Improved auto-brightness
2020-12-17 | 1.4
Add support for glove mode
2020-10-26 | 1.3
Update to Linux 4.14.206
2020-10-26 | 1.2
Update to Linux 4.14.202
Added Seedvault (Video)
Fixed bluetooth regression
Fixed NFC service registration (SELinux denials)
Fixed camera issues
Fixed LineageOS recovery
2020-09-11 | 1.1
Update to Linux 4.14.196
Added Kernel changes from CTG4 (fixes usb audio issues)
Improved DT2W support (thanks linux4)
Fixed camera access to some sensors
2020-08-08 | 1.0
Update to Linux 4.14.192
Performance improvements
New thermal HAL for better overheating protection
Fixed light sensor auto-brightness
Fixed extended-length NFC (required for ePerso App)
2020-07-13 | RC2
Update to Linux 4.14.188
Fixed reboot issue with new Power HAL
Fixed crash issue with power HAL
Update to latest Security release
Removed su for adb root
2020-07-06 | RC1
Update to Linux 4.14.187
Performance improvements (new power HAL)
2020-06-17 | BETA3
Update to Linux 4.14.184
Update to Wireguard 1.0.20200520
Fixed HDR support
Upstreamed vibrator service implementations
2020-05-20 | BETA2
Update to Linux 4.14.177
Added Wireguard support
Added support for L1 widevine security level (Netflix etc.)
Added in-screen fingerprint support for S10(+)
Added "Wireless Powershare" support
Get the full list of sensors working, including tilt, rotation_vector, game_rotation_vector and pick_up_gesture
Fixed USB tethering
Fixed wifi hotspot
Fixed proximity sensor
Fixed phone calls over bluetooth
Fixed phone off charger with nice animation now
2020-04-14 | BETA1
Update to Linux 4.14.175
Added magisk building support
Added USB Trust HAL
Added "Always On Display" quick setting tile (merged upstream)
Fixed performance issues
Fixed video calls (e.g. in Signal)
Fixed proximity sensor
Fixed significant motion sensor
2020-04-05 | BETA0.1
Fixed Play Store
Fixed permission list
Added missing vendor properties
Fixed product definitions
2020-04-03 | BETA0
Initial release
OUR UPSTREAM EFFORTS
Common SELinux policy for Samsung devices
AOD Quick Setting Tile
In-screen fingerprint HAL for LineageOS
Powershare support for LineageOS
Common timed_out vibrator service for Samsung devices

Features + Known Bugs Summary:
This ROM does already support most features of the hardware. If you need specific features, please check the list below. Each feature was manually tested, so it is possible that it does not match your experience with the ROM. In this case please tell us, see the "Getting Help" section at the end of this post.
Ratings Description
++ perfect (in depth tested, performs like stock or better)
+ good (lighly tested only or has minor flaws but is good enough for normal use)
o ok (can be used with some limitations)
- broken (doesn't work at all)
x not supported (unlikely to be implemented, relies on samsungs closed source code)
? can't test, please give feedback
Performance
++ geekbench 5 score: 2267 (gsmarena stock: 2141)
++ antutu v8.4.1 score: 403909 (gsmarena stock: 389694)
Speed (values in MB/s, sr =seq. read, sw = seq. write, rr = random read, rw = random write)
++ internal SD 128GB
AndroBench5: sr 815.0, sw 193.1, rr 138.7, rw 24.7 (= notebookcheck stock)
CPDT 1GB: sr 735.3, sw 139.2, rr 19.2, rw 4.52
++ external SD, 128GB Samsung Evo Plus
Androbench5: sr 68.2, sw 34.5, rr 5.75, rw 2.56
CPDT 1GB: sr: 75.2, sw: 29.5, rr: 4.08, rw: 1.71
++ USB 3.0 MTP, sw 105MB/s (PC CrystalDiskMark -> mtpdrive -> internal SD)
++ USB 3.0 OTG, sw 105MB/s (Sandisk Extreme 64GB -> internal SD, 10.8GB file, 102s)
+ bluetooth file transfer, 0.1MB/s (29MB; from other phone 4m42s, from PC 5m24s) (theoretical max. is 0.3 for BLE4.0, 0.8 for BLE4.2 and 1.4 for BLE5.0)
Connectivity
++ phone calls, 3G, LTE; also with dual sim
++ wifi (delivers 50Mb/s, the maximum my provider supports)
++ bluetooth (file transfer to phone & pc; headphons incl. mic; speakers; keyboard incl. special keys)
++ NFC (only card read tested)
x VoLTE
Screen
+ 10 finger multitouch, "high touch sensitivity" mode not available
++ full brighness range available
++ double tap to wake
+ AOD works, but might be dimmer than stock and brightness cant be changed. While active the proximity sensor is used an its LED blinks dimly next to the camera
Sound
++ dual laudspeaker for media, quality as expected, high volume selectable
+ earpiece (no in depth test)
+ headphones (3.5mm jack) have clean audio, high volume selectable, limited to 16bit/48kHz (instead of 24bit/192kHz) possibly by ROM
+ build-in mic, limited to 16bit/48kHz (instead of 24bit/192kHz), volume should be normal (test)
+ headphone mic, limited to 16bit/48kHz (instead of 24bit/192kHz)
+ some external DACs supported, limited to 24bit/48kHz; (reported by @El Dun)
Camera (with opencamera + camera API v2)
++ wide, ultrawide, front, front-crop
++ PDAF autofocus, face tracking optional (main + front camera, ultrawide is always fixed focus)
++ manual setting for exposure/ ISO/ shutter/ focus
++ raw files option (main camera)
++ optional HDR
+ dual apperature (main camera), only manual switch (default f1.5)
+ video up to 2160p/30fps, 1080p/30fps (all cameras should support 60fps, but OpenCamera only produces 30fps files)
+ 1080p/240fps (main)/ 1080p/120fps (front) high speed/ slow-mo works in stock cam + GCam
x no 720p/960fps super slo-mo
x no supersteady
- S10, S10+: no telephoto camera (details + help wanted)
x S10+: no front depth camera
Sensors
++ gps, quick fix with A-GPS data
+ fingerprint (all variants), can glitch during setup (see bug list)
++ accelerometer, gyroscope, magnetometer, pressure, light (front) (all values are within tolerance)
+ light sensor, but only the front/ under-screen sensor, not the rear sensor
++ IR/RGB sensor outputs values for IR/Red/Green/Blue/Clear (test) (COM.SAMSUNG.SENSOR.LIGHT_IR)
++ grip sensor
+ front proximity (makes only one measurement per second, if you put it quickly to your ear it may touch the screen before it's turned off; reported by @Lav64)
++ software sensors: step counter, rotation vector, gravity, linear acceleration, compass
++ S10/S10+ heart rate/ SpO2 (confirmed by @Ned)
o several software sensors don't produce data, but don't do it on stock either. Affected are the IDs: PICK_UP_GESTURE, COM.SAMSUNG.SENSOR.PROXIMITY_POCKET, COM.SAMSUNG.SENSOR.HALLIC, COM.SAMSUNG.SENSOR.BIO_IR (proof thanks @Brembo109, more info from modpunk)
Charging & Battery
++ 15W quick charge
++ 4.75W reverse charge (with USB OTG adapter)
+ 7.5W+ qi-wireless charge (limited by my charger)
+ 2.5W+ reverse qi-wireless charge (limited by the receiver IC BQ51013)
+ low 40mW idle power consumption (details)
+ ACCA (advance charging controller app) works with limited settings
Misc
++ all buttons, bixby can be reprogrammed (workaround for other functions)
++ wired headphone buttons (pause/play, vol+, vol-)
+ flashlight has only one brighness option (instead of 5 on stock)
- S10e: no fingerprint swipe up/down geture, not even with 3rd party app "Quick Fingerprint Geture"
Known bugs:
when phone is shut down, it reboots instead (fixed in RC2)
reboot to recovery boots directly into system (fixed in RC2)
reboot takes long, about 30s (fixed in RC2, now it only takes a few seconds)
double tap to wake not always working (should be fixed in RC2)
holding fingerprint too long during setup can cause problems details
in full screen apps there may be a black bar to hide the camera cutout which can not be disabled (details, workaround)
high sensitivity touch screen / "glove mode" not available (details)
bixby-button hold-shortcut does not work (details)
google backup does not work with 4x4 or 5x5 pattern. This is an LineageOS issue, but important enough to deserve a note here. (details (thanks @Ivo_Todorov)
Installation:
How do I install this ROM on my phone for the first time?
Below you find a brief checklist of the required installation steps. Installation is more complicated than other ROMs because we take device security very seriously. If you are unfamiliar with installing custom roms , please click the links and read the additional details there.
Confirm the firmware version
Check the top of the ChangeLog which firmware version is required for the ROM release to work well
Go to settings/software-update and update only if the new version matches the requirement!
Alternative: flash with odin/heimdall (details see below)
Unlock your device
Backup all data, unlocking will factory reset your phone
Enable developer mode to and enable the OEM-unlock switch there
Turn off device and boot to bootloader (hold VolumeDown + Bixby, then connect USB cable)
Follow instructions on-screen
Finish the initial setup after unlock. You must connect to WiFi, but can skip everything else. Do not specify a pin/pattern during setup afterwards, otherwise TWRP may cause the "try again after 86400 seconds" issue (see below)
Confirm in the settings that the bootloader is actually unlocked. (greyed out, telling you its unlocked)
Install our TWRP (official thread) | more details (thanks @AndrOdin)
Download our TWRP recovery and the vbmeta-disabled.img file
Unpack the .xz file with 7zip
Check integrity of TWRP (optional, but important for security)
Rename files to recovery.img and vbmeta.img; then pack both files together in a .tar archive with 7zip
Install Samsung USB drivers and odin, (direct link)
Start odin as admin, disable "Auto Reboot" and click "AP "to select the .tar archive
Turn off device, boot to bootloader and, once odin detects it, click "Start"
When the screen turns off, immediately hold (and keep holding) VolumeUp + Bixby + Power to enter recovery mode
When the secondary warning appears, release everything but VolumeUp
Swipe slider to allow for modification
Install LinageOS
copy the ROM ZIP file an external SD card
Boot into the recovery
Wipe cache + dalvik (wipe->advanced and select cache + dalvik)
Format data (wipe->format data, use the dedicated button, wipe->advanced does not work)
Flash the ROM (install -> select storage -> micro SD card and select the .zip file)
Optional: Flash GAPPS (e.g. OpenGAPPS)
Reboot to system
How do I update LineageOS?
Updating LinageOS is a lot less work and you can keep all user data. The process is similar to the last part of the installation:
Backup all important files optional, but very helpful if something goes wrong)
Remove any pin/password/pattern to prevent "retry after 86400 seconds"
Copy the ROM ZIP file an external SD card or internal storage; download the new firmware files to PC (if needed)
Boot into the recovery, do not reboot until you've installed the new ROM and firmware
Flash the ROM (install -> select storage -> micro SD card and select the .zip file)
(Optional: Update GAPPS to the latest version)
Wipe dalvik and cache
Reboot to download
Flash new firmware with instructions below
(Optional: if you use Magisk, flash the new BOOT file. You can also do this in previous step instead of using Stef4n82's "BL.tar" file.)
Reboot to system
How do I update the firmware?
On the stock ROM you can update from the settings menu. You can't do this on lineageOS (yet), so ypu need to use use Odin or Heimdall instead.
How do I update the firmware manually?
Thanks to @Stef4n82's new instructions and repacked firmware files installation is easier than ever. Below you find a copy of his post:
If you use Heimdall:
Download the latest firmwarepackge for your device: "G97?F_Firmwareupdate_Heimdall_????.tar.gz"
Extract the package
Flash the firmware files with this command:
Code:
heimdall flash \
--BOOTLOADER sboot.bin \
--PARAM param.bin \
--UP_PARAM up_param.bin \
--CM cm.bin \
--KEYSTORAGE keystorage.bin \
--UH uh.bin \
--DTB dt.img \
--RADIO modem.bin \
--CP_DEBUG modem_debug.bin
If you use Odin:
Download the latest firmwarepackge for your device: "G97?F_Firmwareupdate_Odin_????.zip"
Extract the package and you will get an AP.tar, a BL.tar and a CP...tar.md5
Flash the 3 files with Odin (tested with latest Odin 3.14.x)
You can download the repacked firmware from the links below.
S10
S10e
S10+
If you don't want this repacked firmware packages and want to download the whole firmware by your own. Make sure if you flash it via Odin that you use this files:
From AP_G97?FXX*.tar.md5 take the dt.img and create a new AP.tar
CP_G97?FXX*.tar.md5
Extract BL_G97?FXX*.tar.md5 and create a new BL.tar without the vbmeta.img.lz4
Try again after 86400 seconds?
With newer version of the Samsung blobs, if you unlock the storage (/data) with TWRP (ie. you enter your pin/password/pattern in TWRP), the trustzone thinks it is a failed attempt and will lock the storage unlocking for 1 day (86400 seconds). To prevent this do not enter your pin (press cancel) and you can still flash an update. If you tripped the trustzone you can either wayt for 1 day to unlock your device (do not power it off) or try rebooting the phone a few times (thanks @Stef4n82), or this slightly more detailed guide (thanks @Exilion90)
You can prevent this completely by removing any pin/password/pattern before entering recovery. This does remove all stored fingerprints, so you'll have to set the up again after the update.
3rd Party Software:
How do I install Google apps?
You can download and install the Google Apps from Open Gapps Project. You need ARM64 and 10.x. We suggest to always use the pico package. If you need additional apps you find them in the Play Store.
Put the Open Gapps ZIP file on your SD card and flash it directly after you flashed LineageOS and before the first boot!
Can I use GPay? What about other banking apps
GPay as well as some other banking apps check if the device passes safetynet and will not start if it doesn't. Safetynet fails when the bootloader is unlocked and therefore this ROM will not run GPay and other applications that need it. This official LineageOS statement explains why safetynett will never by bypassed (by default).
Safetynet used to be easy to bypass with Magisk, but since an Update eralier this year Google uses the TPM module and that can't be circumvented easily. However there might be a workaround with "MagiskHide Props Config", please check out this post and this one. (thanks @Stef4n82) Please note that this has not yet been tested and we can not provide any support. If you got it working on your device, please share how you've done it so we can add it here!
How do I get MicroG with this ROM?
MicroG is an open source alternative to GAPPS. , but unfortunately not recently updated and therefore not recommended.
If you want to install it anyway, read this guide by @JoeRifle and this post (appendum) by @ned14 . Update: It has been reported that the new MicroG version works without issues. (thanks @ichmyselfandi)
Does this ROM have root?
Not by default. If you need root (eg. for AFWall) you can get it through Magisk.
How do I install Magisk?
Important security Advice: Don't flash Magisk modules or anything else which sets SELinux to permissive or you open your device for malware!
Option 1 (recommended):
Download the boot image for Magisk: S10e -- S10 -- S10+
Verify the integrity of the file -> See INTEGRITY
Unzip the boot image using xz or p7zip
(Needed for Odin) Rename the file to boot.img and use 7zip to pack it into a .tar file
Flash the boot image to the BOOT partition using Odin, Heimdall or TWRP
Install https://******************/
Option 2:
Patch TWRP
Which camera app do you suggest?
OpenCamera:
Great open source app that supports a lot of the camera's features with the camera API v2 (select this option in the settings):
All cameras supported (except telephoto, this is a issue with the ROM)
Manual change of exposure, aperture, shutter speed, ISO
The (main) developer uses an S10e himself so you can expect good HW support
You can get it from F-Droid or Play Store
GCam Variants:
There is no "official" GCam for this ROM, but there are some that work. Please read this excelent post by @ned14 for more details. The current recommendation is "GCam_5.1.018.177470874.41362666_IDan_N6_3.5_fix.apk" from (IDan). You need GAPPS, microG (post) or the Google Service Framework(post).
In comparison to OpenCamera it sacrifices manual controls + extra lenses for:
simpler user interface
better single-shot HDR
better panoramas + photospheres
SlowMo video (1080p @120/240fps)
I've also written a more detailed comparison. You can have both camera apps installed at the same time, so you can always choose the better one depending on the scenario.
Getting Help:
General:
Before you post, please check this FAQ, use the search function and skim the few last pages of this thread. We want LinageOS to work on your device, that's the whole point of this thread, but this way you can get the fastest help. If you did not find an answer, feel free to ask here We do this in out free time and it may take us some time to answer, so please be patient.
How to report a bug?
To fix any bug we first have to be able to reproduce it. Please include all relevant information:
device (S10e/S10/S10+)
ROM version
is gapps/ microg/ magisk installed?
steps to reproduce the issue
When in doubt it's better to include to 0much information than too little. A good example is @Sheffield Steve's bug report. Check out Simon's "How to Report Bugs Effectively" to write even better reports (and thus get better help).
How to create a logfile?
To get an even better insight into your issue, a logfile can help us a lot. On Android this is called "logcat". Short logcats are best. They contain less fluff which makes finding the issue easier. Here are the steps how to create a log with adb:
install adb drivers
open cmd and navigate to the adb file eg. cd C:\Users\<user>\Desktop\platform-tools
Connect your phone via USB
Select "Allow USB Debugging" on the popup on the phone (see below how to activate it)
Clear the log using: adb logcat -c
Start loggingwith: adb logcat | tee beyond.log
Reproduce the issue
Stop logging by pressing CTRL+c
Send us the log (in a PM)
How do I enable USB Debugging?
To enable USB Debugging you need to do the following steps:
Go to Settings -> About Phone
Look for Build number
Tap on Build Number several times till you get the message that Developer Options have been enabled
Go to Settings -> System -> Advanced -> Developer Options
Enable USB Debugging
About this FAQ:
This FAQ is originally written by modpunk and partly maintained by me (ctrej) to reduce modpunk's workload. We try to keep the FAQ as up-to-date as possible, but it may lag a few days behind. Please read the last posts in this thread for latest information.
Changelog:
20200813 (v1.0)
update: this changelog, now with ROM version at time of posting and a hide section for older changelogs
update: firmware update section (thanks @Stef4n82!)
update: ROM update section
update: getting help section, rewritten for clarity
update: proximity sensor, slow sample rate (thanks @Lav64)
update: audio section with my test and @El Dun's report
add: gpay/safetynet explanation
change: link formating to stay under the 30k character limit
20200809 (RC2)
update: audio output with limited frequency range, limited DAC support (thanks @El Dun)
update: double tap to wake works well, used it for a few weeks now without issues
update: "86400 seconds" section (thanks @Exilion90)
add: links to each version of this FAQ, just click one of the datecodes
add: ACCA to feature list
add: ADO works kinda
add: dual sim to feature list (thanks @Exilion90)
20200802 (RC2)
update: microG section (thanks @ichmyselfandi)
update: unlock instructions, setup with wifi required (thanks @Lunat1c)
update: "86400 seconds" section (thanks @Lunat1c & @Stef4n82)
add: gapps/ microg/ google framework requirement for the GCAM (thanks @KanyT & @ned14)
add: bug google backup pattern with 4x4 or 5x5 pattern (thanks @Ivo_Todorov)
fix: twrp "more details" link (thanks @Lunat1c)
20200719 (RC2)
update: rgb light sensor, all channels working
update: software sensors don't output values on stock either (thanks @Brembo109)
add: gcam information (thanks @ned14)
add: grip sensor
add: microg appendum (thanks @ned14)
add: workaround for black status bar in fullscreen
add: bug no glove mode (thanks @raggatip)
add: bug bixby button hold shortcut (thanks @Lav64)
20200713
update: feature/ bug list (previously called working/ not working) with fixed from RC2
update: instructions for microG (thanks @ned14)
update: magisk install instructions
update: wireless power share works fine, the phone just didn't like the synthetic load I used for testing
add: black bar on camera cutout in fullscreen apps (thanks @Sradgads)
20200707 (RC1)
update: section "get help" with copy & paste template
update: font for cmd to Courier New
confirm: removing pin/password/pattern solves the 86400 second wait delay (thanks @fishnetfancy)
add: working/not working section
add: this changelog
add: telephoto lens not working (thanks @Ned)
add: several RC1 issues (thanks @angela5246)
add: vbmeta_disabled note to firmware instructions (thanks @okloloi)
add: reminder to update Magisk alongside lineage (thanks @fishnetfancy)
20200705 (Beta3)
first FAQ update by me (ctrej)
change: order to the "natural" installation flow
change: install section into a more detailed checklist (thanks @AndrOdin)
add: sub-sections (install/ 3rd party/ support)

What is difference between this and Ivan's lineage os?

BratoMo225 said:
What is difference between this and Ivan's lineage os?
Click to expand...
Click to collapse
The most obvious one is that we provide SELinux enforcing and care about security and privacy. For the rest I can't give you an answer as Ivan doesn't want to release the source of his device tree. It would be great if Ivan would join our effort and contribute.

Great news, thanks a lot. Your work is much appreciated.
I run LOS from 31.03. from Ivan now. Can I easily flash yours now? As I see Ivan includes vendor files in his release. Is this something I need to consider before flashing your version? And last but not least - I would like to build from your sources. Mainly because I dont want to have Aurora and Fdroid included. Is there a recipe ready for building from scratch?
Again, thank you very much for your effort.

angela5246 said:
Great news, thanks a lot. Your work is much appreciated.
I run LOS from 31.03. from Ivan now. Can I easily flash yours now? As I see Ivan includes vendor files in his release. Is this something I need to consider before flashing your version? And last but not least - I would like to build from your sources. Mainly because I dont want to have Aurora and Fdroid included. Is there a recipe ready for building from scratch?
Again, thank you very much for your effort.
Click to expand...
Click to collapse
If you switch, you have to format /data I'm sorry. We decided to go with AES-256-XTS encryption for this ROM and also the code is signed with my developer keys! There are package signature checks in place for apps which would prevent you to use the ROM.
If you want to build it yourself, instructions are in the beyond0lte README.
However you can just go to Settings -> Apps and disable FDroid and AuroraStore.
Also I've added and AOD (Always On Display) Quicksetting Tile, but this hasn't been merged upstream yet. You might want to pick those changes.

I cant flash it. Im using latest twrp 103

BratoMo225 said:
I cant flash it. Im using latest twrp 103
Click to expand...
Click to collapse
Which TWRP are you using? Do you use the one we built?

No. The one i downloaded from ianmcd thread.
---------- Post added at 09:26 AM ---------- Previous post was at 09:06 AM ----------
Well now after flashing your twrp, and restarting into recovery mode, my phone wont turn on. It says Could not do normal boot invalid kernel length. When i connect my phone to pc, it just loop restarts. now what

can i flash magisk via twrp or are there any extra steps i need to do before it will work?

BratoMo225 said:
No. The one i downloaded from ianmcd thread.
---------- Post added at 09:26 AM ---------- Previous post was at 09:06 AM ----------
Well now after flashing your twrp, and restarting into recovery mode, my phone wont turn on. It says Could not do normal boot invalid kernel length. When i connect my phone to pc, it just loop restarts. now what
Click to expand...
Click to collapse
Did you also flash a vbmeta image which disables vbmeta checking?

catormeme said:
can i flash magisk via twrp or are there any extra steps i need to do before it will work?
Click to expand...
Click to collapse
I'll upload a boot.img which is pre-patched for Magisk 20.4. You can flash this via twrp and Magisk should work, just need to install the Magisk Manager.
edit: Here it is https://www.androidfilehost.com/?fid=4349826312261761185 Unzip the file. If you wish, you can verify it using gpg, then flash the boot.img via TWRP.

modpunk said:
Did you also flash a vbmeta image which disables vbmeta checking?
Click to expand...
Click to collapse
nope. nothing. I will fix my phone with odin right now and then ill try those steps

BratoMo225 said:
nope. nothing. I will fix my phone with odin right now and then ill try those steps
Click to expand...
Click to collapse
I've flashed twrp + vbmeta-disalbed img, then put the zip and gapps on the sdcard and flashed them, formated data and wiped cache and dalvik.

modpunk said:
I've flashed twrp + vbmeta-disalbed img, then put the zip and gapps on the sdcard and flashed them, formated data and wiped cache and dalvik.
Click to expand...
Click to collapse
Your img is "twrp-3.3.1-0-android-10.0-beyond0lte-3.img.xz" ending at .xz sir. I should rename it and only keep .img at ending ?

BratoMo225 said:
Your img is "twrp-3.3.1-0-android-10.0-beyond0lte-3.img.xz" ending at .xz sir. I should rename it and only keep .img at ending ?
Click to expand...
Click to collapse
You need to unpack it.

What about Live display settings in this build? Does it have different color profiles (sRGB for example as it was on S9 series LOS 15.1/16/17.1) or not? Ivan's ROM has only standard "vivid" gamma and white balance correction....

vomad said:
What about Live display settings in this build? Does it have different color profiles (sRGB for example as it was on S9 series LOS 15.1/16/17.1) or not? Ivan's ROM has only standard "vivid" gamma and white balance correction....
Click to expand...
Click to collapse
Live display is fully working. derf elot fixed the last bit yesterday iirc. The manifest entry was wrong for one part of livedisplay.

modpunk said:
Live display is fully working. derf elot fixed the last bit yesterday iirc. The manifest entry was wrong for one part of livedisplay.
Click to expand...
Click to collapse
"Good news everyone!" So I'll be waiting for the S10/S10+ release and immediatly will flash this rom (and magisk boot image I hope)

[Kernel][05.01.2023][Android 12] Kirisakura 1.0.1_S for Asus Zenfone 7/Pro aka Tequila

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

[KERNEL][STOCK] N0Kernel [Android Q][G7/V35/V40]

DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR PHONE BRICKS! YOU ARE FLASHING THIS KERNEL AND ITS YOUR CHOICE TO DO IT OR NOT TO DO IT AND YOU'RE THE ONE DOING IT. I JUST WANT TO HELP OTHERS OUT.
REQUIREMENTS: UNLOCKED BOOTLOADER AND ROOT.
IMPORTANT: THIS KERNEL IS MEANT TO WORK ONLY ON STOCK ROM, IT WONT WORK ON CUSTOM ROMS, CUSTOM ROMS ALREADY PROVIDE WITH THE ROM CUSTOM KERNEL AS ALMOST ALL CUSTOM ROMS ALREADY USE MY KERNEL, THIS IS A MODIFIED VERSION OF THE CUSTOM ROM KERNEL AVAILABLE IN DOTOS BUT FOR STOCK ROM. IT CAN WORK ON ANY LG G7 THINQ MODEL.
How to flash:
1. Download Smartpack Kernel Manager (free) from playstore or any other kernel manager that supports flashing zips such as Franco kernel manager, Ex kernel manager etc;
2. Go to Flash section in the kernel manager, in smartpack press on the 3 lines in the top left corner, scroll down and tap on SmartPack;
3. Press on the button that looks like a lightning, select the zip and wait for it to flash;
4. Reboot;
5. Enjoy.
Features:
- Compiled with Proton Clang 13.0;
- Upstreamed ZRAM compression and decompression algorithms, now ZRAM should be almost as fast as RAM;
- Sultan's Custom Input Boost;
- Sultan's Devfreq Boost;
- F2FS support.
- Rapid GC for F2FS thanks to Arter97;
- Modified CpuSets;
- Quad dac driver backported from LG V50 ThinQ;
- Simple lmk from sultan;
- 4.9.235.
- LA.UM.8.3.r1-08100-sdm845.0 CAF Tag, Why 8100 only and not newer ? Because it performs the best, i've tested even Android 11 tags, it performs worse, this tag is more efficient for battery life while maintaining same performance if not better;
- RCU backported from 4.14 kernel;
- Binder backported from 5.4 kernel;
- Srandom driver by josenk;
- Cpu idle, lmp levels and pm qos improvements, should reduce idle drain.
- Sultan's Pid Map improvements. (Helps a lot in gaming performance, especially in genshin impact);
- A lot of KGSL improvements thanks to Sultan. (KGSL - GPU driver in the kernel);
- Cache improvements;
- Scheduler Improvements;
- CONFIG_HZ = 250;
- 128kb Readahead. Why ? Because thats the default value in linux and pixels as well;
- Updated Energy Model from freqbench result , this will lead to less power consumption;
- Removed inefficient frequencies;
- Added efficient frequencies in schedutil;
- Improvements in schedutil;
- Added support for steam & nintendo swich controllers;
- Many other improvements.
Download Link: Google Drive
Kernel Source: https://github.com/EmanuelCN/android_kernel_lge_sdm845/tree/stock
Useful Guides:
How to unlock bootloader
How to root:
Firstly you have to unlock bootloader.
1. Install magisk manager
2. Boot into 9008 mode
3. Backup your boot_a image using Qfil (Read data)
4. Copy it to your phone
5. Rename it to boot_a.img
6. Go in magisk manager —-> install —-> Select and patch an image —-> select the image.
7. Copy the patched boot image file to your PC (its located in downloads folder in your phone)
8. Flash it with fastboot/qfil ( fastboot flash boot_a < drag and drop over the cmd the image > // select boot_a and load image in qfil)
NOTE: IF IT TELLS YOU THAT YOU ARE NOT ROOTED THEN DO THE SAME PROCESS BUT WITH BOOT_B.
Special Thanks:
- SGCMarkus;
- J0sh1x;
- Thenotonly;
- LlamaMonster;
- ErickG233;
- Sultan (kernel toast);
- Arter97;
- Many other great developers.

reserved