Develop Bugs

[KERNEL][L][STOCK][5.1.1][One G1]intersectRaven's Kernel - 20151105_11XX

Development Goals:
- stability
- energy savings due to more efficient ARM algorithms
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
- all improvements should require MINIMAL user interaction (e.g. you don't need to do anything except flash the kernel or at the very least use SetCPU or the like to set fixed options)
- stability
*note: FAQ is at the 3rd post
20151105_11XX:
- updated to MRA58Y
- huge number of changes (see GitHub)
20151018_20XX:
- enabled KSM and ZRAM for increased memory flexibility
20151015_11XX:
- huge number of improvements (see GitHub)
- updated ramdisk to LUZ59Q
20151012_17XX:
- initial release
- compiled using own GCC 5.2 compiler
*not yet in recovery flashable zip format so for advanced users for now
Disclaimer:
Flash at your own risk.
You can find my other kernels at:
GitHub is at:
XDA:DevDB Information
intersectRaven's One G1 Kernel, Kernel for the OEM Cross Device Development
Contributors
intersectRaven
Kernel Special Features:
Version Information
Status: Testing
Created 2015-10-12
Last Updated 2015-10-12

Reserved 1

Reserved 2

Reserved 3

intersectRaven said:
Development Goals:
- stability
- energy savings due to more efficient ARM algorithms
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
- all improvements should require MINIMAL user interaction (e.g. you don't need to do anything except flash the kernel or at the very least use SetCPU or the like to set fixed options)
- stability
*note: FAQ is at the 3rd post
Latest Kernel Here
20151012_17XX:
- initial release
- compiled using own GCC 5.2 compiler
*not yet in recovery flashable zip format so for advanced users for now
Disclaimer:
Flash at your own risk.
You can find my other kernels at:
http://intersectraven.net/kernels
GitHub is at:
intersectRaven's GitHub
XDA:DevDB Information
intersectRaven's One G1 Kernel, Kernel for the OEM Cross Device Development
Contributors
intersectRaven
Kernel Special Features:
Version Information
Status: Testing
Created 2015-10-12
Last Updated 2015-10-12
Click to expand...
Click to collapse
Reserved 4

intersectRaven said:
Development Goals:
- stability
- energy savings due to more efficient ARM algorithms
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
- all improvements should require MINIMAL user interaction (e.g. you don't need to do anything except flash the kernel or at the very least use SetCPU or the like to set fixed options)
- stability
*note: FAQ is at the 3rd post
Latest Kernel Here
20151012_17XX:
- initial release
- compiled using own GCC 5.2 compiler
*not yet in recovery flashable zip format so for advanced users for now
Disclaimer:
Flash at your own risk.
You can find my other kernels at:
http://intersectraven.net/kernels
GitHub is at:
intersectRaven's GitHub
XDA:DevDB Information
intersectRaven's One G1 Kernel, Kernel for the OEM Cross Device Development
Contributors
intersectRaven
Kernel Special Features:
Version Information
Status: Testing
Created 2015-10-12
Last Updated 2015-10-12
Click to expand...
Click to collapse
:fingers-crossed::fingers-crossed: thank you very much!.. but can we have quick charge 2.0 for this device? just a wishful thinking but i would be so happy if it were to be included because i bought a quick charger to think that Quick charging in G1 was not enabled same as the xzperia z2...

One question: Will I be able to receive OTA updates if I flash this kernel?

rho57 said:
One question: Will I be able to receive OTA updates if I flash this kernel?
Click to expand...
Click to collapse
No , don't install the update files. Give an eror.
Wileyfox Swift cihazımdan Tapatalk kullanılarak gönderildi

Can I use this on Wileyfox Swift CyanogenOS?
intersectRaven said:
Development Goals:
- stability
- energy savings due to more efficient ARM algorithms
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
- all improvements should require MINIMAL user interaction (e.g. you don't need to do anything except flash the kernel or at the very least use SetCPU or the like to set fixed options)
- stability
*note: FAQ is at the 3rd post
Latest Kernel Here
20151018_20XX:
- enabled KSM and ZRAM for increased memory flexibility
20151015_11XX:
- huge number of improvements (see GitHub)
- updated ramdisk to LUZ59Q
20151012_17XX:
- initial release
- compiled using own GCC 5.2 compiler
*not yet in recovery flashable zip format so for advanced users for now
Disclaimer:
Flash at your own risk.
You can find my other kernels at:
http://intersectraven.net/kernels
GitHub is at:
intersectRaven's GitHub
XDA:DevDB Information
intersectRaven's One G1 Kernel, Kernel for the OEM Cross Device Development
Contributors
intersectRaven
Kernel Special Features:
Version Information
Status: Testing
Created 2015-10-12
Last Updated 2015-10-12
Click to expand...
Click to collapse
Can I use this on Wileyfox Swift CyanogenOS?

is this kernel, will works on infinix hot 2 X510 indonesia?

Hi. Thanks for this and it's really a great work.
Mind if you answer some newbie questions?
How do I enter to fastboot? I have already installed all the required drivers and I know how to run the commands.
It is just that I cant figure out how to enter to fastboot.
When I run fastboot via cmd "adb reboot bootloader" , the device just reboot and nothing happens(will reboot but stuck on CherryMobile logo). Btw, I'm also using One G1 on stock 5.1.1. I just want try your kernel.
I have also tried some key combinations like volume up + power button( android logo appears with a text saying no command). When I use voume down + power, nothing also happens, same with volume up + volume down + power button. This device is really tricky.
Edit: I have finally got it working already. SuperThankss!

un-droid said:
Hi. Thanks for this and it's really a great work.
Mind if you answer some newbie questions?
How do I enter to fastboot? I have already installed all the required drivers and I know how to run the commands.
It is just that I cant figure out how to enter to fastboot.
When I run fastboot via cmd "adb reboot bootloader" , the device just reboot and nothing happens(will reboot but stuck on CherryMobile logo). Btw, I'm also using One G1 on stock 5.1.1. I just want try your kernel.
I have also tried some key combinations like volume up + power button( android logo appears with a text saying no command). When I use voume down + power, nothing also happens, same with volume up + volume down + power button. This device is really tricky.
Edit: I have finally got it working already. SuperThankss!
Click to expand...
Click to collapse
Once you initiate "adb reboot bootloader", the Cherry Mobile logo itself will be the fastboot mode.
intersectRaven said:
Latest Kernel Here
20151105_11XX:
- updated to MRA58Y
- huge number of changes (see GitHub)
Click to expand...
Click to collapse
Marshmallow SuperSU 2.52 BETA support?

zrlan7710 said:
Once you initiate "adb reboot bootloader", the Cherry Mobile logo itself will be the fastboot mode.
Marshmallow SuperSU 2.52 BETA support?
Click to expand...
Click to collapse
would like to confirm this too

Will you port to 6.0.1 @intersectRaven ?

nhmanas said:
Will you port to 6.0.1 @intersectRaven ?
Click to expand...
Click to collapse
Once I get the OTA.

intersectRaven said:
Once I get the OTA.
Click to expand...
Click to collapse
Don't wait ota flash stock 6.0.1 man I'm excited :fingerscrossed:
Tengri biz menen.

Thread closed due to me not wanting to comply with development council's command. Will be maintaining my kernels from my own site from now on. :fingers-crossed:

gpl | abyss kernel 1.20 | cm-14.x

Hi oneplus2 people!
This is my modified kernel with some kernel optimizations and some compiler optimizations.
The goal of abyss is to achieve improved performance/battery without the cost of stability.
I will not be overhauling this project with changes that are not logical to add.
This kernel should work on the latest 7.x.x roms like CyanogenMod.
It might work on other roms, but there will be little support for them.
How does one achieve this?
- build kernel with an optimized toolchain
- use compiler optimization flags (experimental)
- remove redundant code
- improve existing code with more efficient code
- etc. (most are not so easy to explain)
This kernel is built with mdalexca's latest UBER GCC 4.9.
Is there actually a performance improvement?
With all the changes added up, there should be. Whether or not one notices the difference is another thing.
For those interested in how the kernel optimizations will benefit/work, please look at my github source and read the commit messages.
For those interested in how the compiler optimizations/hacks will benefit/work, please look at this article.
Downloads:
Latest release
BasketBuild
Source:
GitHub
This was made by request from dsst22 who also tested this bad boi like crazy.
XDA:DevDB Information
abyss kernel for the OnePlus 2, Kernel for the OnePlus 2
Contributors
kwoktopus, dsst22, OnePlus, grarak, The Flash, arter97, Lord Boeffla, frap129, Linux, Google, CAF, a bunch of other major OEMs
Source Code: https://github.com/abyss-kernels/oneplus2
Kernel Special Features:
Version Information
Status: Nightly
Current Stable Version: 1.20
Stable Release Date: 2016-12-05
Created 2016-12-05
Last Updated 2016-12-13

Key Changes:
- upstream interactive governor (with Flash 1.0 profile by The Flash) (Google and CAF)
- upstream cpufreq driver (Google and CAF)
- upstream cpu-boost driver (Google and CAF)
- upstream random driver from Linux 4.1.31 (performance..!)
- slub/slab/slob/vmalloc patches
- flar2's slightly modified thermal driver
- using Linaro's power efficient workqueues throughout kernel
- using Adreno idler by arter97 to reduce frequency scaling without performance cost
- using power efficient "relaxed" macros throughout kernel (assembler)
- KCAL Control Driver by Savoca
- Android-Keyboard patch, use your device as an external keyboard!
- too many to list here, check out my source
How to install:
Place zip in to your internal storage
Place current ROM zip on to your storage
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
Flash kernel zip
Reboot

Don't like the defaults?
Use Kernel Adiutor to change the settings!
Frequently Asked Questions:
Is this a custom kernel?
I was asked this question once, and it posed as a real good question. I do not consider abyss to be a "custom kernel" per se, but more so as a modified kernel. The patches and features that go into this kernel do not make it customizable. What they do is improve what has already been implemented. It is like swapping a car's engine for a better one rather than just adding LED flooring lights and fancy car mats.
Can you add [this] and [that] feature?
Something I pride myself with this kernel is that it does not have a bunch of random, useless features or patches mashed into it. Everything put into this kernel is thought out and tested. I see a lot of works being made popular because it has [this] and [that] feature when really, it's nothing revolutionary. As a matter of fact, most things added to any kernel will not make it 5x better than any other kernel. Most of the time, simple is better; and in this case it definitely is!

For me

Thanks! I'll give it a go.

Giving it a go

Yess! Been waiting for this ever since i saw your OP2 repo!

Does this kernel install on a f2fs formatted system?

suraj.das said:
Yess! Been waiting for this ever since i saw your OP2 repo!
Click to expand...
Click to collapse
You can thank @dsst22 for helping with testing, or else you would have waited a very long time :silly:
socialdistortion said:
Does this kernel install on a f2fs formatted system?
Click to expand...
Click to collapse
I have not made any file system changes to the kernel. If the stock CM kernel supports, then this one will too.

Is kcal support present..??

chl1810 said:
Is kcal support present..??
Click to expand...
Click to collapse
unfortunately no.

good to see new kernel for our device, thanks and good luck

suraj.das said:
unfortunately no.
Click to expand...
Click to collapse
I wish it had

chl1810 said:
I wish it had
Click to expand...
Click to collapse
I can remember the YoshiShaPow falcon kernel

chl1810 said:
I wish it had
Click to expand...
Click to collapse
In the future
PeterImmel said:
I can remember the YoshiShaPow falcon kernel
Click to expand...
Click to collapse
You can probably see how much I've grown as a developer since then too :angel:

Works on a f2fs filesystem based rom. Testing it now...
Edit: No obvious bugs at the moment. Is it possible to implement some sort of charging control. The USB charging speed is super slow (on both this kernel and stock CM kernel).

kwoktopus said:
In the future
Click to expand...
Click to collapse
Nice!! thank you!!

Pretty smooth haven't found any bugs. Love the simplicity.
I can't imagine what it would be like with a little over clock.

adame09 said:
Pretty smooth haven't found any bugs. Love the simplicity.
I can't imagine what it would be like with a little over clock.
Click to expand...
Click to collapse
I trust the engineers that designed the chip to choose a safe maximum clock speed. Here's a pretty good article on the risks vs benefits, which outline some strong points.
But, if I were to add it, I would set the max value at boot to stay as stock values; so I'll leave it up to @dsst22 to decide.

I'll try this out for you dude. Impressive what you've done.

[KERNEL][Stock#1/AOSP#5][V30*][Oreo|Pie] Lunar-Kernels for LG V30

initial thread here, further clarifications in recently added posts below OP/1st post
Lunar-Kernels
tl;dr - too long didn't read / first things first
Stock ROM kernels are attached in posts #1-4 or link to Google Drive
AOSP/LineageOS kernels are attached in post #5 or folder
simply dropping the folder with kernels here (Stock ROM):
https://drive.google.com/open?id=1xL5gEiG-fjzTuSGM_kUDsrOKy-jTtGr1
Description: 3 sub-folders (thus kernels) available:
"old" shouldn't really be used, this is a very bare to LG stock source kernel and (probably) using outdated ramdisks which prevent FM Radio, Mirrorlink, etc. from working
"stable" stable has gotten more testing (or more recent fixes) and is deemed fit for daily driver usage
"bleeding edge" is newest branch, very experimental changes/fixes or just the very latest kernel (if those don't end up in "stable" already)
Stable and bleeding edge are the
Further notes for "eas":
From the tests so far - it has turned out that power consumption ALWAYS was higher compared to HMP and/or the default shipped LG kernel (tweaked HMP)
So the best results up until now was to underclock CPU, underclock GPU (or keep at lowest 1-2 levels) and add tweaks to shut phy power source off for display, this is similar results like anandtech with Exynos EAS/HMP tests: https://www.anandtech.com/show/12620/improving-the-exynos-9810-galaxy-s9-part-2/3
Meaning: NO EAS kernels until further notice - only HMP kernels will be developed/provided right now
Usage case: [outdated]
"old": should work pretty reliable, everything is built conservatively & close to stock one of the first kernels
"stable": probably great daily driver material - FM Radio & MirrorLink, etc. still broken
"bleeding edge": just the latest and greatest from upstream, security, tuning, etc. - features might break in the process
eas [attached here]: daily driver, long running for lots of reading, lots of watching videos, high SOT demand ; suitability for gaming has yet to be evaluated
NOT working and probably will NOT in the near future (or at all): [outdated]
- FM Radio (broken with "old", "stable" kernels - those use v300 ramdisk)
- MobiCore - thus MirrorLink, etc. (broken with "old", "stable" kernels - those use v300 ramdisk)
- FM Radio & MirrorLink currently works with bleeding edge kernels
Notes (Kernel):
This kernel is built first and foremost FOR ME and shared with the community to benefit from that work,
you don't owe me anything and I don't owe you anything
like with Sony (yeah, even Sony !) and other vendors with their modified, proprietary non-AOSP ROMs - kernel development is extremely bothersome, each few commits kernel doesn't boot or compilation fails, so don't expect e.g. 4.4.137 kernel or catchup with latest codeaurora changes since that takes simply too much time and work (time, effort, nerves, etc.)
tested on H930 (Europe) V30 ONLY, test at your own risk on H930DS (dual SIM) or other devices; ramdisks and device configs WILL differ (global defconfig used - so compatiblity should be higher, limitations/compatibility issues with US, Korea and other models possible)
You need to have knowledge how this device behaves in case of flashing broken kernels, filesystem corruption and other worst-case scenarios
You must:
stay calm all of the time while flashing and must NOT do anything rash or chaotic
know how to get into bootloader/fastboot mode via USB-cable (when device is off) OR via adb command from a running system
know how to force the device to turn off (it will turn on again but that might help in certain cases) - this way you easily can get into fastboot/bootloader again
know and/or have a basic understanding that the device will settle most issues on its own
have your device charged to a battery level AT LEAST to 50-60% in case boot loops take longer (it is caught in boot loop) and you can't quickly turn the device off anymore
know/expect that flashing Magisk and other mods most certainly will lead the device too boot several times ("artificial bootloop") and might get you uneasy or confused, we need to figure out how to speed up the process that it finally boots into the ROM
potential issues & potential remedies/fixes: [up-to-date]
might have high load unless rctd disabler is flashed (root detection tool) => flash rctd
might not boot unless no-verity is flashed, custom ROM => flash no-verity
might not boot or work with encrypted phone or encrypted anything => should be self-explanatory, don't use LG encryption on custom ROMs/mods
some security functionality might not work => TEE/qseecom/lgecrypto_module might not work, encryption safe, folder encryption, etc. might be broken (if applicable)
might not boot or bootloop microSD with exfat is cause of LOT of trouble => in doubt remove microSD before flashing custom Kernels or ROM mods to avoid having additional trouble-maker to troubleshoot
phone boot-"loops" several times => seems to be default bootloader behavior for LG V30 (and/or other LG phone)
phone boot-"loops" several times => might need a few times to "settle" to boot the ROM up
booting up takes long => might actually rebuild dalvik cache or do some filesystem checking
SIM PIN isn't request and WiFi is dead as well => several reboots might fix it;
SIM PIN isn't request and WiFi is dead as well => permission corruption might have occurred, (need root) try to fix via: https://stackoverflow.com/questions...acct-uid-10064-read-only-file-system-in-emula
after flashing (custom) Kernel or (custom) ROM phone (re)boots into fastboot => "no OS" , Kernel might not actually be bootable , kernel issue, system partition issue
after flashing (custom) Kernel or (custom) ROM phone (re)boots into fastboot => might have incompatible ramdisk, no-verity was not flashed
after flashing (custom) Kernel or (custom) ROM phone (re)boots into fastboot => Kernel might be broken (totally not work or be compiled with non-compatible features)
after flashing (custom) Kernel or (custom) ROM phone (re)boots into fastboot => OS/Android might be broken (filesystem corrupted, etc.)
Flashing rctd & no-verity/verity-disabler is only necessary for LG Stock-based ROMs !
Not necessary for AOSP, LineageOS, etc. !
prepare kernel for flashing : [up-to-date]
rename the zip-file to 7z (file size limit)
extract the 7z (needs 7z that support PPMd compression)
rename it into boot.img
suggested flash : [up-to-date]
Get into fastboot mode (turn off => connect cable end to phone => hold VOL down => connect PC end of cable)
fastboot flash boot boot.img
fastboot boot TWRP.img (keep USB cable connected ALL of the time)
flash rctd disabler
flash no-verity
(optional) flash Magisk
disconnect USB cable
(optional) wipe /cache
(optional) dalvik cache
reboot system
Help:
Forcing the device to reset usually is done via Power + VOL DOWN - keep both pressed for several seconds, then the screen should turn off
the device is set up to (re)boot again - so have the USB cable, a PC/phone [on the go] with fastboot ready to connect the cable immediately when it was off
.
If you plan on using the microSD more extensively and are on non-Stock (e.g. AOSP, LineageOS, dot os, etc.) - [backup your data !] then format the microSD to ext4 in TWRP, that should give you 2x the write performance of exfat and also somewhat faster read performance
As a bonus of using ext4 on the microSD - access to your files should be available when flashing/trying out the GSIs (Project Treble)
Kernel boot test (DEVs):
[Kernel testing or if you want to try] I usually do a fastboot boot boot.img first to see if the bootanimation is successful (boots into bootanimation [non-Stock] or it boots into the ROM itself with reduced functionality [Stock ROM])
After that I do a real flash of the kernel via fastboot flash boot boot.img
Quirks (V30* phones compared to others & bootloader/boot(loop) behavior):
After first flashing - the kernel might fail at 1st boot, then reboot device and properly boot into the ROM
with Magisk it can be more reboots (I counted at least 3-4).
.
.
If the bootlooping is much longer - force reset the device (Power + VOL DOWN), that should usually allow the device to recover after 1-3 (re)boots
.
If that still doesn't help - remove the microSD - until you've successfully booted the kernel up, the exfat driver is known to cause trouble and make things much less predictable and irritating
To make things more predictable (and exclusively using AOSP/LineageOS-based ROMs) - you can format the microSD to ext4, that might help a bit with the amount of (re)boots during flashing)
FIXME:
additional notes, warnings, guides, etc.
(theory) while the device seems to bootloop after flashing Magisk or other "bigger" modifications - occasionally press the volume down button while you see the LG V30 ThinQ logo (boot splash/image) to speed up booting (input = boosting = quicker everything ?)
Kernel Source:
android_kernel_lge_msm8998/branches
lunar-kernel_II_WIP5_boot-work [current "bleeding edge"]
other/older kernels are earlier states of latest bleeding edge branch
Kudos:
Linus Torvalds, Linux Kernel devs
Greg Kroah-Hartman our favorite upstream Kernel LTS maintainer <3
Google kernel & other Android devs
codeaurora, linaro & all other devs working on qualcomm goodies
LG kernel & other devs
nathanchance for his kernel, toolchain and other reference work
sonyxperiadev & devs
sultanxda
freak07
franciscofranco
andip71
frap129
GreyLeshy
SGCMarkus
the XDA , 4PDA and all other android communities
all other devs & folks to be mentioned
last edited:
28.06.2018, add attachment: specifically built kernel for ls998, US sprint V30 model (US firmware, US998)
28.06.2018, add attachment: uploaded II_EAS_I_stable , EAS kernel on early ported EAS state, should be pretty efficient, deemed stable material, read notes: at its announcement post
06.07.2018: updated text for bleeding-edge added link to it https://forum.xda-developers.com/showpost.php?p=76996622&postcount=88
12.07.2018: attached latest HMP kernel to OP (1st post), removed EAS kernels since those had a bug with frequency being stuck at max frequency
26.10.2018: removed older attached HMP kernels, newer ones are in posts below

#1
"old", barebones kernel with absolute minimum changes (from LG) will be here

#2
"stable", only minimum additional functionality & fixes will be here
if not mentioned otherwise these are ONLY for LG Stock-based ROMs (Boombox, A.I.S., Stock, debloated Stock, etc.)
Checksums (md5sum):
d0c4572563a389ec495f1c661332c185 boot_oreo_I_6_WIP4_stock__H932_spr_US__tmo_US_20K.img
f29fc429d32de4fd79d3117642d39137 boot_oreo_I_6_WIP4_stock__H932_spr_US__tmo_US_20K_PPMd_7z.zip
6307cd6d40e97404a3c66bf78d20437f boot_oreo_I_6_WIP4_stock__US998init_spr_US_20D.img
f181f7589ecb3426006fa0d15c1e161d boot_oreo_I_6_WIP4_stock__US998init_spr_US_20D_PPMd_7z.zip
f31791fcd8b57db7e3b91ba5e4755bf3 boot_H930_21A_oreo_I_6_WIP4_LG_stock.img
d77c0504c9119f2d86880dd74d8fc0cd boot_H930_21A_oreo_I_6_WIP4_LG_stock_PPMd_7z.zip
Source:
https://github.com/zachariasmaladro...mmits/oreo_I_6_WIP4_stock__H932__US998_spr_US

#3
"bleeding edge", current development branch & WIP (work-in-progress) drops
Stability troubleshooting:
disable zram
set lowest CPU frequency and max CPU frequency to default
lower GPU max frequency
...
change each setting separately and see if that improves stability then please report your results
oreo_I_6_WIP7_3_stock
Branch:
https://github.com/zachariasmaladroit/android_kernel_lge_msm8998/commits/oreo_I_6_WIP7_3_stock
Changes:
rolled back kernel to earlier state (October 1st), troubleshooting stability
re-added sdcardfs aosp msm upstream changes, mostly "Drop dentry cache to prevent unknown file status" change in behavior (data integrity)
sdcardfs fixes
ext4, f2fs, ecryptfs and fscrypt updates and changes close to latest upstream
lockdep improvements
further oom, oom_reaper, fork-handling fixes and improvements
force 16b ECC for pstore
scheduler fixes (hmp.c; ...)
updated simple_lmk (not used in this branch)
[eval] reverting to basic optimizations for armv8-a
[eval] reverting to Google's 4.9 Toolchain (best compatibility, stability, etc.)
devfreq fixes and improvements
PCIe wake improvement for msm8998
configure i2c for bit-banging bus recovery
[eval] revert several previous changes
several other changes
Click to expand...
Click to collapse
md5sum checksums:
91273b50c1126bf44e2fa9b7d3eb00bb boot_oreo_I_6_WIP7_3_stock__H932_spr_US__tmo_US_20K.img
859fa1eb9948f19821110da85d2d996a boot_oreo_I_6_WIP7_3_stock__H932_spr_US__tmo_US_20K_PPMd_7z.zip
e20bb8036273960e99316cb7bac57c78 boot_H930_21A_oreo_I_6_WIP7_3_stock.img
0a360f4dd4cedf6cf95ded2dbd78fa1d boot_H930_21A_oreo_I_6_WIP7_3_stock_PPMd_7z.zip
0b7fc9259836f9a79c2e1715ba7bd79a boot_oreo_I_6_WIP7_3_stock__US998init_spr_US_20D.img
9c1d1f917f7cd9ba50c2464a2b8b4bb0 boot_oreo_I_6_WIP7_3_stock__US998init_spr_US_20D_PPMd_7z.zip
Click to expand...
Click to collapse
oreo_I_6_WIP8_stock
Branch:
https://github.com/zachariasmaladroit/android_kernel_lge_msm8998/commits/oreo_I_6_WIP8_stock
Changes:
faster initialization of kgsl/3d adreno graphics driver (quicker boot)
removed (for now): DTS Eagle - caused more noticeable humming/buzzing/whirring of sound at lower volume levels with aqstic (internal) DAC
timers: fix for lock contention and failing
CIFS/SMB: security fixes up-to-date [driver not used right now]
qcacld-3.0: updated WiFi driver & firmware to latest revision for Android 8.1
removed: LiveDisplay driver (only used in LineageOS; RR, etc. ?)
[eval] switched to 300Hz tickrate from 1000Hz tickrate which tends to be quite unstable on LG Stock ROMs
wcd934x: (internal DAC) a few fixes & improvements
removed/reverted: change that caused horizontal line of AOD display
several other changes
Click to expand...
Click to collapse
Known issues:
inverted color on AOD display [needs investigation] - e.g. red equals to turquoise for whatever reason
md5sum checksums:
8acd26556f1f6afe1659cff54fe61efc boot_H930_21A_oreo_I_6_WIP8_stock.img
32b8e679cdb8c066cdb945785334822c boot_H930_21A_oreo_I_6_WIP8_stock_PPMd_7z.zip
a29bda002d9c70f617180f3a955cb066 boot_oreo_I_6_WIP8_stock__H932_spr_US__tmo_US_20K.img
b06ddaba4f4c0124448b81ff78f479ba boot_oreo_I_6_WIP8_stock__H932_spr_US__tmo_US_20K_PPMd_7z.zip
3c46f82d1bb45e2fe3dfe5fc55f8b815 boot_oreo_I_6_WIP8_stock__US998init_spr_US_20E.img
e7d42505842abcb08e3ec0c90c26924d boot_oreo_I_6_WIP8_stock__US998init_spr_US_20E_PPMd_7z.zip
Click to expand...
Click to collapse
oreo_I_6_WIP9_7_5_2_stock
Leaving this here for a bit (from the Telegram Group https://t.me/LGEV30 ):
New experimental/WIP kernel for Stock LG ROMs [regression fix, headset detection might stop working after a while]
internet max throughput should be 25-30% higher than before, ZZMoove governor is onboard along with other custom ones (cultivation, impulse, blu_active), MPTCP got updated, additional fixes & improvements to cut down latency & raise stability, ppp subsystem has been updated and enhanced (potentially fixing VPN connection issue), peripheral-loader, slimbus, glink subsystem updated; camera actuator updated - uses boost to make zooming smoother, several other subsystems updated, cpu_input_boost used - screen output smoothing/boosting, oom handling fixed/improved, HSWAP (swap + lmk + page_alloc LG in-house variant) disabled in favor of upstream lmk, binder fixes and improvements, regulator fixes & improvements, mempolicy got updated, eliminated a few battery drainers (idle drain should be lower)
H930/H930DS, 21A:
https://drive.google.com/open?id=1iyX8yY8QuX1ZJv8VcUn9CEpx4bOtaU98
US998, 20E:
https://drive.google.com/open?id=1ne06IAK4AJ7k22OYiD91yicjkp0nGtZ-
H932, 20K:
https://drive.google.com/open?id=1s6y8YSEdh5QXheqPrEaqdSiiYdc6QsO-
open towards suggestions on how to reduce battery consumption of WiFi usage further
Click to expand...
Click to collapse
Kernel source branch:
oreo_I_6_WIP9_7_stock__H932__US998_spr_US
Click to expand...
Click to collapse
Note:
Attached file is a 7zip (PPMd compression) renamed to zip due to filesize limitation
rename to .7z and extract - some archiver can handle the file without renaming ...

#4
due to attachment size limitations - the file was packed with 7z PPMd (max) compression, then renamed to .zip, so: rename to .7z and unpack
afterwards flash the boot.img either
via fastboot flash boot boot
via TWRP
oreo_I_6_WIP7_3 (almost identical to current LG Stock ROM kernel)
Branch:
pie_I_6_WIP7_3
Changes:
rolled back kernel to earlier state (October 1st), troubleshooting stability
re-added sdcardfs aosp msm upstream changes, mostly "Drop dentry cache to prevent unknown file status" change in behavior (data integrity)
sdcardfs fixes
ext4, f2fs, ecryptfs and fscrypt updates and changes close to latest upstream
lockdep improvements
further oom, oom_reaper, fork-handling fixes and improvements
force 16b ECC for pstore
scheduler fixes (hmp.c; ...)
updated simple_lmk (not used in this branch)
[eval] reverting to basic optimizations for armv8-a
[eval] reverting to Google's 4.9 Toolchain (best compatibility, stability, etc.)
devfreq fixes and improvements
PCIe wake improvement for msm8998
configure i2c for bit-banging bus recovery
[eval] revert several previous changes
several other changes
Click to expand...
Click to collapse
md5sum checksums:
0639cd649bd4d8aa27bf2db5ed065761 boot_oreo_I_6_WIP7_3_H930_AOSiP-8.1-Derp_29.08.2018.img
3807e6991580b96ec796836c8c1f1bb7 boot_oreo_I_6_WIP7_3_H930_AOSiP-8.1-Derp_29.08.2018_PPMd_7z.zip
9ecaafd28851c2471c4c4de0dbd8e6be boot_oreo_I_6_WIP7_3_H930_lOS-15.1_27.09.2018.img
f148bd763cbb606508ac332b45ef15a7 boot_oreo_I_6_WIP7_3_H930_lOS-15.1_27.09.2018_PPMd_7z.zip
d9ead2f72bd19d02d50a9bf12bb85a79 boot_oreo_I_6_WIP7_3_H930_RR-O-6.1.0_29.08.2018.img
59aee22119d981b8aa91c1c846a5075e boot_oreo_I_6_WIP7_3_H930_RR-O-6.1.0_29.08.2018_PPMd_7z.zip
2a60f4130b4005736fdba05981cff408 boot_oreo_I_6_WIP7_3_H930_dotOS_2.5_27.09.2018.img
f7643c6f30c61755f7e066b4ff4d5fae boot_oreo_I_6_WIP7_3_H930_dotOS_2.5_27.09.2018_PPMd_7z.zip
Click to expand...
Click to collapse
these 4 different Kernel releases are needed because the ramdisk/init content is fundamentally different preventing the phone/ROM from booting if it doesn't match
Dirty Unicorns 9.0-based Kernels (06.10.2018 build):
see attachment
Checksums (md5sum) :
be498bf45017a28d7ead8ccada514868 boot_pie_I_6_WIP3__DU_9.0__06.10.2018.img
30c34e1566fece2ac8721868fa89b88c boot_pie_I_6_WIP3__DU_9.0__06.10.2018_PPMd_7z.zip
a4425bb19177033622d402c3b6795a4d boot_pie_I_6_WIP4__DU_9.0__06.10.2018.img
f89adcd02831700eed629195639497c7 boot_pie_I_6_WIP4__DU_9.0__06.10.2018_PPMd_7z.zip
please also take a look at the "experimental" folder if there are newer ones there (currently: 26.10.2018 - there are none newer ones)
edit (01.09.2018):
removed the attached kernel since 3 different kernels, depending on ROM, are needed to avoid confusion
edit (26.10.2018):
added updated kernels for recent AOSiP, lineageOS 15.1, Resurrection Remix Oreo 6.1.0, dotOS 2.5 builds (all Android Oreo, 8.1)

Interested in checking this out. Would I be able to get past bootloops on an already loaded rom full of Magisk mods or would this need to be done solely through clean rom flashes?

XCaliburX said:
Interested in checking this out. Would I be able to get past bootloops on an already loaded rom full of Magisk mods or would this need to be done solely through clean rom flashes?
Click to expand...
Click to collapse
Not sure what you mean with "solely through clean rom flashes"
Just do a TWRP backup of each partition separately: /boot, /system, /data
then get into fastboot:
boot into bootloader (adb reboot bootloader)
turn phone OFF, connect USB cable to phone, hold volume down - connect other end to PC
First test-run to see if it boots for you:
Code:
fastboot boot boot.img
then
Code:
fastboot flash boot boot.img
after that boot into TWRP and flash Magisk.
I've had Magisk installed before and after each kernel flash you, of course, need to install Magisk again (Magisk Mods probably, too - that at least was the case I tried NanoMod/microG via Magisk).
tl;dr
bootloops or longer booting would/could still happen no matter ROM state - ideally you should be able to flash or fastboot boot the new kernel without issues
Magisk always needs to be re-installed after new kernel (boot.img) flash, same applies to Magisk modules
Thanks

Nvm.

Thanks for your work. Is it possible to flash your kernel, as img, in twrp as usual ? Whithout using adb code ?
Envoyé de mon LG-H930 en utilisant Tapatalk

XCaliburX said:
Nvm.
Click to expand...
Click to collapse
Thanks for your comment (before replacing it )
You ran into any issues ?
The stable kernel/branch is more suitable to gain battery savings since it has the phy-off change included that allows the phy power supply to be turned off during idle state and the scheduler change (the "old" one doesn't - it constitutes the absolute bare minimum).
The scheduler change effectively reduces battery consumption during usage by approx. by half (confirmed with e.g. music playback with PowerAMP).
The flashing is actually quite straight-forward, the notes in OP / first post matches with the previous (incomplete) understanding I had how the device behaves and needs to be amended once I further understand how to most efficiently
do all the steps ...
The device (or bootloader) seems it's set up that way to bootloop (when a broken kernel/boot.img is flashed) - returning to the warning screen that the bootloader is unlocked - and once the phone was turned off (via Power button), it'll immediately boot successfully via the existing kernel on the boot partition to the ROM.
So with the boot.img files I offer actually non of the bootlooping should happen (after flashing Magisk, it'll reboot once but should boot into ROM afterwards).
There are additional power savings possible e.g. sending the GPU off to nap once it's idle but that needs careful tuning to reduce lag/non-smoothness - which I currently don't have time to do,
also we're limited to using the enhanced HMP kernel for now - EAS is off limits, so that should prevent further power savings and enhanced smoothness with high efficiency.
guigui33 said:
Thanks for your work. Is it possible to flash your kernel, as img, in twrp as usual ? Whithout using adb code ?
Envoyé de mon LG-H930 en utilisant Tapatalk
Click to expand...
Click to collapse
I haven't tried doing that yet,
but if that possibility is there it most probably should work - please give it a try
Merci

No problem flashing .img via TWRP. flashed the "stable" Kernel 2h after OP posted the links. Running fine for now w/o problems. Smooth as butter und more battery friendly than stock
Great work i have to say.
Cheers

Just a question. I replaced the kernel boot.img of a rom inside the zip with the "old" kernel. After coming across some problems, I decided to wipe partitions and restore a previous save. When I tried this, the restore would send me to the bootloader screen instead of rebooting. Is there something wrong with the save or does this mean there's some conflict with the kernel the phone's currently on and the saved restore's kernel? I'm only able to boot if I fresh reinstall the rom with the original kernel intact. Phone is a US998R.
Will try the "stable" kernel and report back if I come across anything.

XCaliburX said:
Just a question. I replaced the kernel boot.img of a rom inside the zip with the "old" kernel. After coming across some problems, I decided to wipe partitions and restore a previous save. When I tried this, the restore would send me to the bootloader screen instead of rebooting. Is there something wrong with the save or does this mean there's some conflict with the kernel the phone's currently on and the saved restore's kernel? I'm only able to boot if I fresh reinstall the rom with the original kernel intact. Phone is a US998R.
Will try the "stable" kernel and report back if I come across anything.
Click to expand...
Click to collapse
Both "old" and "stable" kernels use the "stock" modified ramdisk from SGCMarkus which was working fine while flashing his debloated (Korean origin) Stock ROM,
it could be that the device nevertheless is reacting allergic to modifications/deviations from a kernel which is very close to stock.
Can't really tell what could be the reason for it to react up - HOWEVER nothing in "old" kernel looks suspicious to can cause that.
tl;dr:
no idea
in case of doubt use completely stock kernel
don't forget to use rctd-disabler & no-verity/forced-encrypt disabler
once you have a working base, go from there

As someone with one of the"Franken-phones" ( h931 flashed to us 998 nougat and updated to Oreo via LGUP) would it be worth trying to flash this kernal? Currently these devices have issues with the Aosp roms and therefore require a rom that is closer to stock in order to avoid bootlooping. In settings my lgv30 displays as a H930 unit, so theoretically it could work.. would be nice to get a customized kernal. Any input would be appreciated. Thanks

MetaMaverick said:
As someone with one of the"Franken-phones" ( h931 flashed to us 998 nougat and updated to Oreo via LGUP) would it be worth trying to flash this kernal? Currently these devices have issues with the Aosp roms and therefore require a rom that is closer to stock in order to avoid bootlooping. In settings my lgv30 displays as a H930 unit, so theoretically it could work.. would be nice to get a customized kernal. Any input would be appreciated. Thanks
Click to expand...
Click to collapse
That's an AT&T/Time Warner model, right ?
it uses a different mode of operation/has changes in ecryptfs
runs in FIPS mode
has an in-built VpnClient security module which supports an "interceptor" netfilter module
doesn't seem to have multi-path (MPTCP) vs. the global model (or at least kernel config)
it comes with an enhanced TrustZone/qseecom driver "to enable Periodic Kernel Monitoring driver for LG IMA" (PKM)
adds support for "ccaudit logging using additional fifth buffer" (which doesn nothing ?)
haven't seen the ramdisk yet (boot.img ?)
but I guess there might be interference as soon as the kernel strays too much from stock since qseecom/TZ is involved which pretty quickly can lead to a non-booting kernel on Stock ROM (had it happen on Z5).
There might very well be additional changes from the global (H930) model - I've only looked at the main files so far ...

I have flashed the bleeding version, and it seems to be hard to boot with and to make a battery drain.
I'm on the stock twrp rom.
I flash then the stable kernel, and lt's better, the boot is fast and it seems to have no battery drain.
In case of problem, can you join the stock kernel in the topic to be flashable as image or zip via twrp ?
Good work !
Envoyé de mon LG-H930 en utilisant Tapatalk

Using the stable on ls998 stock and boots nicely...no issues so far...hopefuly be able to squeeze a bit of extra battery life out with it...thank you and great work...on another note i flashed as an image through twrp without issues

Reboots a few seconds after unlocking screen. Kmesg from twrp. Ls998 (converted from Verizon). Pretty sure twrp grabs the correct kmesg
Happens on stable and old.

TotallyAnxious said:
Reboots a few seconds after unlocking screen. Kmesg from twrp. Ls998 (converted from Verizon). Pretty sure twrp grabs the correct kmesg
Happens on stable and old.
Click to expand...
Click to collapse
Thanks for the feedback,
nope though:
Linux version 4.4.78-perf+ ([email protected]) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #11 SMP PREEMPT Sat Mar 24 22:16:32 CET 2018
Click to expand...
Click to collapse
that one's from SGCMarkus.
Can you post more info how your system is set up ?

zacharias.maladroit said:
Thanks for the feedback,
nope though:
that one's from SGCMarkus
Click to expand...
Click to collapse
I'm having trouble figuring out a way to get a kernel log then. The phone reboots too soon for adb. Any ideas? Google has only shown me ways when the phone is working normally and reboots.
---------- Post added at 02:01 AM ---------- Previous post was at 01:57 AM ----------
zacharias.maladroit said:
Can you post more info how your system is set up ?
Click to expand...
Click to collapse
Debloated from latest kdz Oreo. Magisk 16.4. I flash the img, flash magisk 16.4 then reboot. I've tried keeping wifi off (didn't change anything). I've tried with and without my personal magisk mod. All that's left is magisk mods like BusyBox and other utilities.

[Kernel] [All ROMs] [ALL VARIANTS] Glassrom kernel

This is the stock kernel that ships with glassrom (or will ship with it)
5g variants are not yet supported
It is based off kirisakura kernel with additional hardening from my side.
You get this:
All the features from kirisakura kernel
Removed qualcomm's rmnet drivers
COMPAT_VDSO is disabled to enable full vDSO ASLR
KSPP patches have been applied
Clang control flow integrity (https://source.android.com/devices/tech/debug/cfi)
Backward edged control flow integrity:
Strong protections enforced by shadowcallstack (https://source.android.com/devices/tech/debug/shadow-call-stack)
Weak protections enforced by adding stack canaries to everything and ensuring ASLR is of a decent enough quality
Compiled with -O3 and Polly for maximum performance
Wireguard driver has been removed
AVB depends on the ROM. Flashing it on glassrom/oxygenos will definitely cause it to boot with enforcing AVB. On other ROMs this shouldn't happen
Selinux forced enforcing patch from Samsung
Yama is enabled and set to SCOPE_NO_ATTACH
Uses sdfat driver to provide vfat and exfat drivers
Todo:
Port Linux-hardened patch
fix fingerprint on oos
Notes:
Flashing it on oxygenos will break dt2w
Flashing the kernel regardless of ROM or device combination will break twrp ramdisk boot. The only way to boot twrp is using fastboot boot, installing it to the ramdisk will always lead to a kernel panic. This is not a bug and will not be fixed
Download: see release post https://forum.xda-developers.com/showpost.php?p=81105101&postcount=8
Source:
https://github.com/GlassROM-devices/android_kernel_oneplus_sm8150
Donations:
Most of the hard work was done by @Freak07 so check out his thread and buy him a coffee

anupritaisno1 said:
This is the stock kernel that ships with glassrom (or will ship with it)
5g variants are not yet supported
It is based off kirisakura kernel with additional hardening from my side.
You get this:
All the features from kirisakura kernel
Removed qualcomm's rmnet drivers
COMPAT_VDSO is disabled to enable full vDSO ASLR
KSPP patches have been applied
Clang control flow integrity (https://source.android.com/devices/tech/debug/cfi)
Backward edged control flow integrity:
Strong protections enforced by shadowcallstack (https://source.android.com/devices/tech/debug/shadow-call-stack)
Weak protections enforced by adding stack canaries to everything and ensuring ASLR is of a decent enough quality
Compiled with -O3 and Polly for maximum performance
Wireguard driver has been removed
AVB depends on the ROM. Flashing it on glassrom/oxygenos will definitely cause it to boot with enforcing AVB. On other ROMs this shouldn't happen
Selinux forced enforcing patch from Samsung
Yama is enabled (does nothing significant for now)
Todo:
Set Yama to level 3 (breaks magisk)
Port Linux-hardened patch
Notes:
Flashing it on oxygenos will break dt2w
Flashing the kernel regardless of ROM or device combination will break twrp ramdisk boot. The only way to boot twrp is using fastboot boot, installing it to the ramdisk will always lead to a kernel panic. This is not a bug and will not be fixed
Download:
https://mirror.apexcdn.net/files/glassrom/unsigned.zip
Source:
https://github.com/GlassROM-devices/android_kernel_oneplus_sm8150
Click to expand...
Click to collapse
Fingerprint is broken on oos

Kaz205 said:
Fingerprint is broken on oos
Click to expand...
Click to collapse
Yeah sorry about that. I'll make a version for oos soon
I did test it for a short while on oos but did not test it enough

Merged in the latest kernel from kirisakura git and also merged in 4.14.156
It boots fine but I don't have a good internet connection to be able to upload it
Will do so soon

anupritaisno1 said:
Merged in the latest kernel from kirisakura git and also merged in 4.14.156
It boots fine but I don't have a good internet connection to be able to upload it
Will do so soon
Click to expand...
Click to collapse
Thanks! Does this one work with OOS?

MrGimpGrumble said:
Thanks! Does this one work with OOS?
Click to expand...
Click to collapse
I eventually plan to stop supporting oos
OOS is proprietary for one and such a system is almost never secure. And if you don't believe me just look at their past vulnerability announcements. Almost all oxygenos vulnerabilities come from the fact that oneplus finds loopholes around Google's CTS. Who knows what other holes they've opened up that Google forgot to add checks for
Further, oos has many "memory optimisation" drivers that directly try to access ram and break most of the security features I'm implementing. Most custom ROMs do not have these and the drivers can be safely disabled
I will also add that this kernel is almost functionally identical with kirisakura kernel. Yes I might merge upstream slightly faster but other than that there is no difference that you would notice. The only difference is that I'm enabling all the security features that must be enabled - especially CFI and shadowcallstack which come standard on any Google pixel device
As for wireguard I just think running a VPN in kernel space is a very bad idea. Not to mention I have confirmed that on Android the tunnel leaks ipv6 traffic if you're not careful and no, disabling ipv6 is not the solution. The userspace go implementation is much safer and I mean it. The userspace implementation almost never leaks ipv6 traffic. Not to mention Go is a much safer language than C

okay new update is in the attachments
changes: linux 4.14.156
upstreamed to oos open beta 6 (doesn't mean fixed fingerprint yet)
upstreamed wifi driver and audio driver to latest caf tag (LA.UM.8.1.r1-12200-sm8150.0)
yama is now at level 3
all upstream changes from kirisakura. except for wake gestures as lineagehw seems to already have those
oos users should disable smart boost from settings

okay new build is here
changelog:
linux 4.14.157
upstreamed sdfat driver
fixed a weird kernel panic that happened on anything other than oxygenos when the device was fast charging from a very low battery

anupritaisno1 said:
okay new build is here
changelog:
linux 4.14.157
upstreamed sdfat driver
fixed a weird kernel panic that happened on anything other than oxygenos when the device was fast charging from a very low battery
Click to expand...
Click to collapse
work on pa?

ryshd296 said:
work on pa?
Click to expand...
Click to collapse
Please test it and let me know
It should boot on any ROM that can enforce selinux

anupritaisno1 said:
Please test it and let me know
It should boot on any ROM that can enforce selinux
Click to expand...
Click to collapse
This sent me into an immediate Qualcomm crash dump upon booting on both stock OOS and Omni for OnePlus 7t global variant.
Previous releases as well, not just the newer release.

scott.hart.bti said:
This sent me into an immediate Qualcomm crash dump upon booting on both stock OOS and Omni for OnePlus 7t global variant.
Previous releases as well, not just the newer release.
Click to expand...
Click to collapse
Please duplicate the crashdump message exactly
Especially send the "PC at" line and the error message if present
If the error message is blank please mention that it is
If you get a PC at __cfi_check_fail message please mention this

@scott.hart.bti still waiting for your response
Please send the crash log if possible

Do i need ma
gisk companion for this?

psychemisha said:
Do i need ma
gisk companion for this?
Click to expand...
Click to collapse
No you don't
However somewhere around ob4 maintaining compatibility with oxygenos became next to impossible without breaking custom ROMs
I think most users are still on OOS. If not I can just release builds for custom ROMs

Costum plz

is the development stopped?

[KERNEL] [Android 11/12] Dora kernel for OP7 series

Introduction
Dora kernel is a successor of popular nem0 kernel for A10/A11 ROMs.
Dora Kernel is CAF based kernel aiming to provide great stability and performance while maxing out battery life!
Code:
// Your warranty is now void.
//
// I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
// Please do some research if you have any concerns about features included in this Kernel before flashing it!
// YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Main Features:
- Unified for OOS 11 and Android 11 Custom ROMs (Check with your maintainer if they have R blobs merged in)
- Based and upstreamed to latest CAF tags for the SD855
- Upstreamed to latest Linux-Stable
- Upstreamed to latest F2FS stable
- Compiled with Clang 13 and -O3 speed optimizations flags
- Compiled with Clang Polyhedral Loop Optimizations (Polly)
- Simple LMK driver from kerneltoast
- BBR2 TCP congestion algorithm
- 675 MHz GPU step
- Custom energy-freq scheduling model for maximizing performance and battery life
- Custom frequencies setup (dropping to CAF default minimums during idle)
- S2idle suspend mechanism with patches from Google P4/P5 kernels
- PELT scheduling mechanism
- Many scheduler backports from mainline and/or 4.19 Google kernel
- Zip made using latest AnyKernel3 release, retains root on flash (Stable Magisk 21.4 or higher reccommended)
- Zip flashable through EXKM/FKM/Smartpack/TWRP
- Integrated OTA updates in Franco's Kernel Manager *(link for the json: JSON)
- Many more features I don't remember right now, check source if you're interested or contact me on Telegram!
Bug reports:
- If you want to report a bug, please provide some sort of logs (logcat, dmesg)
Flashing instructions:
- Just flash it through TWRP or EX or Franco's Kernel Manager apps
- No sorts of configs needed, flash and be happy out of the box
-There are 2 versions per release: one with SDCARD_FS disabled (default) and one with it enabled. Motivation behind this is recent updates to AOSP 11 ROMs (Yaap, Derp, etc.) that have disabled the support for it. And even though that builds with SDCARD_FS could still work, it's not recommended.
So, in layman terms, if you are running OOS or any custom ROM that still hasn't followed the path of those custom ROMs, please use the sdcard-fs zip or update through OTA.
Downloads
Stable and Test builds: Google Drive
Kernel being actively tested in this group: Telegram
Donations
If you would like to keep this project going with more improvements, feel free to support it: PayPal
Thank you to:
@osm0sis for AnyKernel
@nathanchance for help with upstreams
@topjohnwu for Magisk
@idkwhoiam322, @KuranKaname for being good friends
@BobAzzon, @npv12, @Gabyrx7, @Reechings and rest of my dear friends that tested the kernel (really, wouldn't be possible without you guys <3)
Contributors
nem0 aka AnnoyingZlatan
Source Code: GitHub
Version Information
Status: Stable
Created 2021-05-01
Last Updated 2021-07-20

Reserved

Reserved #2

really pru kernel, I like it
my sot tripled
jk, best kernel on here!

Best kernel ever since Nemo,,now Dora,,congrat bro,,awesome kernel,,work perfect with new official PE rom,,,

Best for A11 on OOS11 blobs and OOS11 !!!!

Ex-nem0 Kernel user here, thank you so much @AnnoyingZlatan for this one
I've just installed 1.0 with adb sideload on latest PixelExperience, all good

Love ur kernel looking forward to help u testing hehe

Toutatis_ said:
Ex-nem0 Kernel user here, thank you so much @AnnoyingZlatan for this one
I've just installed 1.0 with adb sideload on latest PixelExperience, all good
Click to expand...
Click to collapse
I'd like to try it on YAAP, but I didn't know how to go back to stock kernel. I read somebody says to restore boot.img & dtbo but not sure how to do it

Zhuang zhuang said:
I'd like to try it on YAAP, but I didn't know how to go back to stock kernel. I read somebody says to restore boot.img & dtbo but not sure how to do it
Click to expand...
Click to collapse
In Franko kernel manager you can make a backup of your current kernel. Then flash this, then restore kernel if you want it back.
Of fastbootd flash boot img from yaap, same as you most likely did when you originally installed it if you used that method. (Ps, make sure it's matching your ROM though, so you're not updated to the latest but flashing a boot image from a previous version..)

Currently using your Nemo kernel. I flashed this kernel via Franco's kernel manager but I get kicked back to my recovery..any ideas? Tia your kernels are awesome

This kernel is awesome. With Dora Freq i've the best UI performance with AOSP like LOS/CrDroid , another world compared to OOS. Thanks Dev.

bushninja07 said:
Currently using your Nemo kernel. I flashed this kernel via Franco's kernel manager but I get kicked back to my recovery..any ideas? Tia your kernels are awesome
Click to expand...
Click to collapse
Yes, this is meant for OOS 11 and A11 ROMs that switched to R blobs, as it's stated in the OP. It won't be compatible with the builds you've run Nemo on

Amazing experience out of the box, super thanks !
tested with OP7 on oos 11.0.0.2
super smooth and really impressive battery

I flashed via FKM on YAAP. Everything started good but just few minutes ago, when the screen turned off, it didn't turn on again & auto reboot. I had it 2 times in just a couple of minutes

Zhuang zhuang said:
I flashed via FKM on YAAP. Everything started good but just few minutes ago, when the screen turned off, it didn't turn on again & auto reboot. I had it 2 times in just a couple of minutes
Click to expand...
Click to collapse
Yaap has a built in logcat, perhaps check to see if there's any traces of the error. It might help Zlatan if you post that..

I have OOS 11 and and currently using a custom kernel. Should I flash OOS 11 again before your kernel? Thanks in advance.

Zhuang zhuang said:
I flashed via FKM on YAAP. Everything started good but just few minutes ago, when the screen turned off, it didn't turn on again & auto reboot. I had it 2 times in just a couple of minutes
Click to expand...
Click to collapse
I am aware of the issue. Will be fixed in next update, just a bit busy atm.

Teso79 said:
I have OOS 11 and and currently using a custom kernel. Should I flash OOS 11 again before your kernel? Thanks in advance.
Click to expand...
Click to collapse
Nope, just flashing a kernel is enough.

I have tried this version of the kernel and it feels very good! But the memory of my phone is too small, I hope there will be swap space in the future. Does the developer have plans to add zram or zswap in the future?