Buffcore oreo kernelSamsung Galaxy S4 i9505 (jfltexx)Release 02 - 11th June 2018
Code:
#include
/*
* Your warranty is now void.
* And other random stuff no-one reads.
*/
Intro
I had never intended releasing this as a stand alone, but had always been aware that it would work.
With BB and Side both being busy and AOSP and OptLos stalling for a bit, the kernel from RR-oreo should I think help a bit to alleviate users battery issues.
What is it?
Buffcore 2.04 - this is a fork of BB's AOSP 8.1 kernel with added fastcharge and battery saving features.
It is the kernel supplied with RR-o release 2, so isn't needed for RR users.
Code:
renamed to buffcore;
sdfat enabled;
fastcharge implemented for faster charging (up to 1900 ac / 1000 usb);
bcmhd wakelocks for rx and tx halved;
libmemcopy and libstring sped up;
io readahead to 1024k;
lower min cpu governor frequency (270);
power efficient work queues;
voltage tweaking user interface;
faster vmstat;
autosmp hotplugging replacement;
mmc crc disabled;
allow for lower cpu voltage;
reduce swapiness;
optimise divide / multiply by power of 2;
added tcp optimisation options,;
set westwood default;
force doze screen off helper;
optimise cbfillrect function;
reduce wifi wakelock times;
nohz: reduce overhead under high-freq idling patterns.
What rom is it for?
BB's AOSP oreo
Side's OptLos 15.1
Installation
Dirty (use with current rom flash)
Extract the boot.img file from the zip (It is not a flashable zip!).
Reboot rom into twrp.
Perform a nandroid backup to be safe, incase you need to go back.
Go into Install, then select Install Image for Buffcore kernel.
Reinstall your prefered root solution (Magisk, etc).
Do not wipe caches.
Reboot.
Clean (flash as part of clean install)
Extract the boot.img file from the zip (It is not a flashable zip!).
Reboot rom into twrp.
Perform a nandroid backup to be safe, incase you need to go back.
Perform clean recomended in your rom thread.
Install rom.
Go into Install, then select Install Image for Buffcore kernel.
Reinstall your prefered root solution (Magisk, etc)
Install Gapps.
Do not wipe caches.
Reboot.
Usage
Some features will need to be forced on (IF desired) and set to apply on boot with an app like Kernel Aduitor, EXKM etc. (Fastcharge, Min cpu frquency used, Power efficient work queues, Voltage tweaking, AutoSMP hotplugging).
This kernel should / will not be compatible with stweaks.
There will essentially be no support with this, if it works then it works, or doesn't.
If it helps you then it helps you, if it doesn't tough, don't moan about it.
It has had a little testing with the roms it is intended, boots fine and seems to provide some benefit.
This may not get updated either - see it as a stop gap for the moment.
Thanks
Thanks due to Drrossum, Kesaras, CR4IGY_BOY for testing for me.
BB for original kernel and Side and TsvietOK for picks.
Download
Download from AFH here BUFFcore-o-2.04-release02-20180611.zip
md5sum - d2293a1e623ddcc68946dbea7ea12869
XDA:DevDB Information
BUFFcore-o, Kernel for the Samsung Galaxy S4
Contributors
Buff99, side
Source Code: https://github.com/Buff99/platform_kernel_samsung_jf/tree/aosp-8.1
Kernel Special Features: Fastcharge, battery saving features
Version Information
Status: No Longer Updated
Created 2018-06-18
Last Updated 2018-09-13
Reserved
might as well have one, won't be writing much tho....
Very well done, master!
Perfect. I guess it's my new optlos main kernel
side said:
Perfect. I guess it's my new optlos main kernel
Click to expand...
Click to collapse
Of course, we work better and smarter together.
Since Kernels are/should be backward compatible, any reason why this shouldn't work with RR Marshmallow?
Thx!
<CuriousCat> said:
Since Kernels are/should be backward compatible, any reason why this shouldn't work with RR Marshmallow?
Thx!
Click to expand...
Click to collapse
Backwards compatibility with kernels? Not guaranteed that I know of.
When Oreo kernels use 64 bit binder, it locks out use with ROMs that don't have 64 bit binder defined.
You'd be better trying a sidecore kernel for nougat as an intermediate, if it works then try this. A kernel flash that doesn't work should be easy to recover from if have you stock one on hand ready to reflash. Remember that any mod / root that patches the kernel will need reflash.
SideCore kernel is a no go. A stock RR Nougat kernel also. Do you think some repacking with the boot.img of the RR Marshmallow would help?
<CuriousCat> said:
SideCore kernel is a no go. A stock RR Nougat kernel also. Do you think some repacking with the boot.img of the RR Marshmallow would help?
Click to expand...
Click to collapse
if they don't work, then this is a definite no-go.
I think RR marshmallow used the stock CM13.1 kernel, nothing was changed. Your viable choice would be anything cm13 compatible.
Syzrgy & Alucard spring to mind from back in the day.
Buff99 said:
if they don't work, then this is a definite no-go.
I think RR marshmallow used the stock CM13.1 kernel, nothing was changed. Your viable choice would be anything cm13 compatible.
Syzrgy & Alucard spring to mind from back in the day.
Click to expand...
Click to collapse
Alucard can't be found for MM and Synergy is very old (and not sure how stable).
Is there a way to take the (your/lineage) source and compile it to work with MM?
<CuriousCat> said:
Alucard can't be found for MM and Synergy is very old (and not sure how stable).
Is there a way to take the (your/lineage) source and compile it to work with MM?
Click to expand...
Click to collapse
just change the ramdisk using an image kitchen
side said:
just change the ramdisk using an image kitchen
Click to expand...
Click to collapse
I was thinking the same. Let me try.
Once repacked it boots but it's unstable. After running AnTuTu a few times it restarted every time. Not a good sign.
I flashed it several times on I9505 running the LOS15.1 and everytime I reboot after flash it shows the boot up screen with the phone model and then goes to Download mode. The fix for this non booting condition is to reflash the ROM.
Pecata01 said:
I flashed it several times on I9505 running the LOS15.1 and everytime I reboot after flash it shows the boot up screen with the phone model and then goes to Download mode. The fix for this non booting condition is to reflash the ROM.
Click to expand...
Click to collapse
Where is los15.1? Which rom u mean
I meant the Optimized Lineage OS 15.1 builds Version1 on which I tried to install BUFFcore-o rel02 kernel and it didn't work. But i flashed the Lineage OS 15.1 Version2 and it's all working. Good job
Is it possible to change the max frequency? Before compiling? Or manually with an root Explorer?
Just for fun
M4verick44 said:
Is it possible to change the max frequency? Before compiling? Or manually with an root Explorer?
Just for fun
Click to expand...
Click to collapse
aka overclock.
yes its possible.not suggested though.this thing is really advanced and i dont think that u will have nice results.wont be 'fun' at all
Can you add Boeffla Wakelock Blocker to this kernel? The Wi-Fi wakelocks are still annoying.
side said:
aka overclock.
yes its possible.not suggested though.this thing is really advanced and i dont think that u will have nice results.wont be 'fun' at all
Click to expand...
Click to collapse
Will you add over clocking to this kernel anytime soon? @side @Buff99?, maybe @ripee
---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------
side said:
aka overclock.
yes its possible.not suggested though.this thing is really advanced and i dont think that u will have nice results.wont be 'fun' at all
Click to expand...
Click to collapse
Will you add over clocking to this kernel anytime soon? @side @Buff99?, maybe @ripee
Related
AOSP RIN Kernel for D851
Close to stock with some sugar added ... delicous!
Hey guys and girls,
here is my attempt to build up on the cm source for an modified AOSP kernel, hope you like it, have fun
First of, DISCLAIMER, I'm not responsible for bricked devices, dead unicorns, rainbows with missing colors, world war, nose bleed, void warranty (you know that already, don't you? your warranty is void now and it's your fault ) or any other harm happening to your device, you or people around you!
What does it serve? (Features)
AnyKernel
Kexec Hardboot patch
FauxSound support
OC to 2.7GHz and UC support
Voltage control
Intelliplug
Cpu limiter
GPU Overclocking to 675Mhz
Simple GPU Algorithm
Simple_ondemand GPU Governor fixed
fsync on/off support (on by default)
Power efficient workqueues
Dynamic management of dirty page writebacks
Dynamic Read Ahead
IO Schedulers
CFQ
DEADLINE
FIFO
FIOPS
NOOP
ROW (default)
SIO
TRIPNDROID
VR
ZEN
Governors
Adaptive
Conservative
DanceDance
Intelliminmax
Interactive (default)
Lagfree
Lionheart
OnDemand
Performance
Powersave
SmartassV2
Userspace
Wheatley
Smartmax
TCP Congestion Algorithms
BIC
Westwood+
Vegas
Veno
Yeah
HTCP
Cubic (default)
Reno
LiveSharpening
2-Way Call Recording support
exFat support
DriveDroid support
KSM
android logger sysfs toggle (disabled by default)
Many under the hood fixes
Stability
More to come
How to apply it? (Installation)
IMPORTANT: Read through all the requirements, steps and warnings before you do anything, if any requirement doesn't match or you don't know what one or more of the steps below mean or do, ask before you do any of them, if you don't know how all the steps can be done, let it be, I warned you, if you don't do and something bad happens, I'll just laugh at you!!
Requirements? Yes!
D851
Custom Recovery
AOSP based lollipop ROM (Mainly cm12 based)
How to flash the kernel?
BEWARE to be on the default kernel of the given ROM (NO custom, except at updates of this one!!) when flashing this kernel, the ramdisk is taken from the currently flashed kernel!!!
Download zip
Place on internal or external SD
Reboot to recovery
Choose install zip
Search for the downloaded zip
Confirm flashing
Wipe cache
Reboot
Have fun
Changes? (Changelog)
14.01.2015/1.6.5
FauxSound support added
Dynamic read ahead
13.01.2015/1.6
Initial AOSP release
Full list of commits can be found here
Where to get it from? (Download)
google drive | AndroidFileHost | dev host
Let me test!! (Beta Testing Community)
Google+ LG G3 Beta Testing Community
Show me the so(u)rce(ry)! (Source Code)
https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-cm-12.0
Donators (huge thanks, you're simply great )
@Toneman07
@Helloworld294
@shaarky
@Dreamxtreme
@guyd
@mosincredible
@tobitege
@AndroidUzer
Credits
XDA for the great community
Google for their great operating system
LG for the great device
CyanogenMod for the base this is built up from
@invisiblek for his marvelous job on the bring up of the device and the many patches
@HolyAngel for some commits I used
@faux123 for his great work with intelli* and beyond
@KAsp3rd for some commits I used
@myfluxi for some commits I used
@trialsrider1 for some commits I used
@Skin1980 for his breakthroughs at our device, his support and for being such a nice guy
@Lord Boeffla for some commits I used
@GuneetAtwal for some commits I used
@DooMLoRD for some commits I used
@Fechinator for some commits I used
@savoca for AnyKernel, Livesharpening and some other stuff
@Christopher83 for his implementation of Dynamic management of dirty page writebacks and some additional stuff
If you like my work, please show your appreciation by pressing the thanks button, if you want to do more, i've nothing against a little donation, but I'm as happy when you just thank me by pressing the button
XDA:DevDB Information
Rin Kernel AOSP, Kernel for the T-Mobile LG G3
Contributors
Tectas
Source Code: https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-cm-12.0
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 1.6.5
Beta Release Date: 2015-01-14
Created 2015-01-14
Last Updated 2015-01-14
Reserved
Awesome thanks. Heard good things about your STK LG kernel. Downloading
razrlover said:
Awesome thanks. Heard good things about your STK LG kernel. Downloading
Click to expand...
Click to collapse
Super addition to the D851 arsenal.
Thanks
P.S: Can't seem to find it in the downloads!
arifqur said:
Super addition to the D851 arsenal.
Thanks
P.S: Can't seem to find it in the downloads!
Click to expand...
Click to collapse
Sorry, link fixed.
Tectas said:
Sorry, link fixed.
Click to expand...
Click to collapse
Thanks for the link and especially thanks for being the first Dev to include kexec hard boot patch for D851 in his kernel
Heh, I managed to screw up my MultiROM setup.
Fusion LP was a tertiary ROM. I decided to flash this kernel against it. Almost 10 minutes and it never finished flashing. TWRP was also frozen.
On restart none of the ROMs would boot. Trying to reselect Fusion in MultiROM would fail and freeze/lock TWRP. Seems the partition with Fusion got corrupted.
Got tired of pulling the battery so wound up restoring primary ROM and will start over with MultiROM.
Just one of those things probably unrelated to the kernel itself.
I should have at least backed up the secondary ROM. Oh well. ?
Small update to 1.6.5:
14.01.2015/1.6.5
FauxSound support added
Dynamic read ahead
Download within the OP, have fun
Tectas said:
Small update to 1.6.5:
14.01.2015/1.6.5
FauxSound support added
Dynamic read ahead
Download within the OP, have fun
Click to expand...
Click to collapse
Thanks
Working well so far, thanks :good:
marcdw said:
Heh, I managed to screw up my MultiROM setup.
Fusion LP was a tertiary ROM. I decided to flash this kernel against it. Almost 10 minutes and it never finished flashing. TWRP was also frozen.
On restart none of the ROMs would boot. Trying to reselect Fusion in MultiROM would fail and freeze/lock TWRP. Seems the partition with Fusion got corrupted.
Got tired of pulling the battery so wound up restoring primary ROM and will start over with MultiROM.
Just one of those things probably unrelated to the kernel itself.
I should have at least backed up the secondary ROM. Oh well. ?
Click to expand...
Click to collapse
I'm using it with Fusion as primary ROM with no problems. But flashing fusion itself takes close to ten minutes to flash, and the progress bar shows nothing until it's done. I was already on fusion, then flashed RIN and Multirom.
Never mind.
Working well with Euphoria.
Thanks for a great AOSP kernel
joshuajones said:
I'm using it with Fusion as primary ROM with no problems. But flashing fusion itself takes close to ten minutes to flash, and the progress bar shows nothing until it's done. I was already on fusion, then flashed RIN and Multirom.
Click to expand...
Click to collapse
I changed my primary SkyDragon ROM then reflashed kexec kernel and multirom. Discovered my CM11 was still there (cool) then reflashed Fusion.
Flashed RIN kernel but this time I waited. It took much longer than the ROM install.
But all is good. Fusion seems to be running great with RIN.
Thanks.
Sent from my LG-D851 using Tapatalk
Kernel is working great
I've used this Kernel on about 3 different LP ROM's (clean flash) and on each of them, the pull down menu appears and freezes after ending calls whether its being made or receiving them. If you are able to get out of the menu, the pull down no longer works. You must reboot for everything to return to normal...
Nothing says great batterylife except when it tells me 1 day 19 hours and hasnt been on a charger since 8 am
Nice kernel exelent battery and no complains for now ?
Been off charger all day with light use and its still going strong
scribbles92 said:
I've used this Kernel on about 3 different LP ROM's (clean flash) and on each of them, the pull down menu appears and freezes after ending calls whether its being made or receiving them. If you are able to get out of the menu, the pull down no longer works. You must reboot for everything to return to normal...
Click to expand...
Click to collapse
Done a few clean flashes since I started using this kernel but I'm not having this problem...
To God be the glory, It is finally here: Android N kernels!
@malacore had a good suggestion for me to get started on my AKLU kernels while I wait for more ram for my computer to make my own N builds. I started with JDCTeams's CM14, and hope to branch out to AOSP and others soon.
Feel free to comment if you have tried them on another rom, successful or not, or to leave feedback on these kernels as well. These can be flashed on any JF variant of phone, but I have only personally tested them on JFLTETMO.
Post #2: N kernels
Source: https://github.com/alaskalinuxuser/
Kernel Version 3.4.112
Post created: 11/02/16
Last updated: 9/5/17
Nougat kernels!
For AOKP 7:
(AOKP is now based on LineageOS)
https://www.mediafire.com/folder/h3p473al6xstx/kernels
For SlimRoms 7:
http://www.mediafire.com/file/s3v49439d9k5k1e/AKLU-SLIM-N-JFLTE-intelliplug-20170117.zip
For LineageOS 14.1:
http://www.mediafire.com/file/305w1rnap7qj2he/AKLU-LINEAGEOS-N-JFLTE-intelliplug-20160112.zip
For RR 5.8.0:
(RR is now based on LineageOS)
http://www.mediafire.com/file/0nq9p5qq5mx9q8u/AKLU-RR580-N-JFLTE-UPDATE-20170126.zip
For CM14 by the JDCTeam:
http://www.mediafire.com/file/9z097f1aox8pguu/AKLU-CM14-N-JFLTE-iosched-20161110.zip
Change Log:
20170619
-Added Faux Sound! Thanks @faux123
-Added fast charge!
20170524
-Added GPU and CPU voltage controls!
--> Control the CPU through Kernel Adiutor
--> Control the GPU with my GPU Voltage Control App.
https://forum.xda-developers.com/ga...gpu-voltage-control-app-aklu-kernels-t3506985
20170425
-Updated for 7.1.2 compatibility.
20170315
-Update for Substratum compatibility.
20170126
-Fixed WiFi hot-spot issue for AOKP and RR.
20170115
-Updated RR and AOKP kernel with LineageOS base, as they transitioned away from CM.
20161222
+ Added Intelliplug, an alternative hotplugging option made by @faux123.
20161220
+ No feature changes, just cleaning up a few things to help with RR 5.8.0
20161110
+ Added I/O Schedulers:
-->FIOPS
-->SIO
-->VR
20161102
+ Overclocked CPU to 1998 MHz.
+ Overclocked GPU to 487 MHz.
+ Added Governors:
-->SmartMax
-->Wheatley
-->LionHeart
Old Kernels:
http://www.mediafire.com/file/rzt412chq67b3av/AKLU-JFLTE-AOKP-N-20170425.zip
Screenshots!
Some screenshots of Kernel Aduitor with these kernels.
Awesome gonna give it a go and see but I'm sure will run/perform just fine
sent from my SGH-M919 BadAss TinkerToy
---------- Post added at 04:26 PM ---------- Previous post was at 04:09 PM ----------
have u tested with systemless root does it play nice the marshmallow dev worked great just wondering since supersu patches boot.img but I'll test it incase and let u know
sent from my SGH-M919 BadAss TinkerToy
Kernel seems to run fine I noticed no fauxsound or fast charge. Also didn't have all the same governors as other kernels u have. Web apps ran laggy but I think that's something with that rom. Also noticed on boot unlike ur marshmallow dev kernel it show not selinux enforcing. currently back on marshmallow it says only about kernel. Why is that on marshmallow it says permissive when full booted under about phone. I wonder if it's some flag or something supersu patches on marshmallow dev that it can't or isn't patching on the nought kernel. Because both ur rom and cm14.1 are both showing permissive fully booted under about phone with me changing nothing. Even ran getenforce to make sure.
sent from my SGH-M919 BadAss TinkerToy
dtriguero said:
Kernel seems to run fine I noticed no fauxsound or fast charge. Also didn't have all the same governors as other kernels u have. Web apps ran laggy but I think that's something with that rom. Also noticed on boot unlike ur marshmallow dev kernel it show not selinux enforcing. currently back on marshmallow it says only about kernel. Why is that on marshmallow it says permissive when full booted under about phone. I wonder if it's some flag or something supersu patches on marshmallow dev that it can't or isn't patching on the nought kernel. Because both ur rom and cm14.1 are both showing permissive fully booted under about phone with me changing nothing. Even ran getenforce to make sure.
sent from my SGH-M919 BadAss TinkerToy
Click to expand...
Click to collapse
Yes, I am still adding features, so fast charge, fauxsound, etc., are not added yet. Also it is not set to permissive when I made it for their ROM, because their default was enforcing. I can make it default permissive if needed when I make more adjustments. It is somewhat difficult working within their ROM to make my own kernel, so it will take some time to get all of the features put in.
that's funny cause the nought one boots with two errors on sammy logo not seandroid enforcing I think and kernel warranty bit as if is permissive but when boot mm dev kernel only shows kernel warranty bit on sammy screen as if enforcing during boot but permissive when finished boot. Also N shows permissive but did flash supersu before booting maybe it changed it. Steps was
Full wide-after backup of course
flash cm14.1
flash 7.1 micro gapps
flash ur N kernel
flash supersu 2.78 sr3- there rom flash 2.78 sr1
sent from my SGH-M919 BadAss TinkerToy
For now I am satisfied with Alucard kernel in OotCM14 but I'll be keeping an eye on this thread to see how things developed.
I do have one question, is your kernel based on stock cm kernel or Alucard?
Sent from my SGH-M919 using Tapatalk
Xplorer4x4 said:
For now I am satisfied with Alucard kernel in OotCM14 but I'll be keeping an eye on this thread to see how things developed.
I do have one question, is your kernel based on stock cm kernel or Alucard?
Click to expand...
Click to collapse
No worries!
Yes, my kernel is based on stock CM kernel. Alucard kernels are great, I have a lot of respect for Alucard kernels.
AlaskaLinuxUser said:
For CM14 by the JDCTeam:
http://www.mediafire.com/file/9z097f1aox8pguu/AKLU-CM14-N-JFLTE-iosched-20161110.zip
For AOKP 7:
http://www.mediafire.com/file/znzpjieflvb7q9r/AKLU-AOKP-N-JFLTE-iosched-20161110.zip
Change Log:
20161110
+ Added I/O Schedulers:
-->FIOPS
-->SIO
-->VR
Click to expand...
Click to collapse
To God be the glory, another successful addition to the N kernel! Just added a few I/O schedulers.
i see you are making kernels for aokp 7. i am wondering is there even an aokp 7 for us yet and if so where can i test it
gizm0luvsu said:
i see you are making kernels for aokp 7. i am wondering is there even an aokp 7 for us yet and if so where can i test it
Click to expand...
Click to collapse
I am guessing it was a typo and he meant aosp not aosp. No aokp rom yet that I know of.
Sent from my Pixel using Tapatalk
gizm0luvsu said:
i see you are making kernels for aokp 7. i am wondering is there even an aokp 7 for us yet and if so where can i test it
Click to expand...
Click to collapse
Xplorer4x4 said:
I am guessing it was a typo and he meant aosp not aosp. No aokp rom yet that I know of.
Click to expand...
Click to collapse
Actually, there is an AOKP 7.0 teaser download in the AOKP MM thread. No working calls yet.
AlaskaLinuxUser said:
Actually, there is an AOKP 7.0 teaser download in the AOKP MM thread. No working calls yet.
Click to expand...
Click to collapse
ahhh ok
Will u be adding all the goodies u had in ur MM Dev kernel to ur aokp N kernel
dtriguero said:
Will u be adding all the goodies u had in ur MM Dev kernel to ur aokp N kernel
Click to expand...
Click to collapse
Great question!
Yes, I plan to do that eventually, it may take me a while. There are some other pressing phone items that I need to fix first.
For some reason I tried flashing your aokp kernel on your new build and boot indefinitely. Could be me
smartt699 said:
For some reason I tried flashing your aokp kernel on your new build and boot indefinitely. Could be me
Click to expand...
Click to collapse
Hmmm... It did test good here. However, I let AOKP N boot fully, then went back to recovery and flashed this kernel.
However, I have updated it, so try the new one in the OP, if you would. It also tests good here. When flashing, it gave me an error, but still flashes just fine. The error is about the syntax of the META-INF file, not a kernel problem.
Let me know how if you have any more problems. I did not have GAPPS installed when I tested this, just for reference.
Praise God, new kernel is up!
Hey guys, just wanted to let you know that the OP is updated with the new kernel, including intelliplug, an alternative to mpdecision for hotplugging. This controls how many cores are used at once. You have to use Kernel Adiutor or some similar app to control it. Intelliplug has several options that show up in the Kernel Adiutor as well. Let me know what you think!
hi there is a procedure to install this kernel on RR ( like wipe cache), because i tried an get a bootloop
Due to the @MSFJarvis and @nathanchance being the unbeatable dynamic duo, I've decided to discontinue this kernel. At this point, our kernels are extremely similar, save ElectroUtil and a few misc commits. Rather than put time into a modified Flash kernel, I recommend y'all just try Flash (warning: its pretty good). ElectroUtil and my other changes will live on in the CarbonROM kernel, and will simply be added on top of flash kernel. Thanks for supporting this project while it was alive.
For those of you who have used my angler and (unreleased) ether kernels, then you already know how this works. Feel free to skip to the Instructions.
Electron kernel has a few goals that make it different from other kernels. These goals are to:
Be as light weight as possible
Improve battery while performing at least as well as stock
Be a flash-and-go kernel (recommended settings are defaults)
That being said, This is a flash and go kernel (If you install the Magisk Module), please do not tweak options unless you are an advanced user.
Electron does NOT have spectrum support yet, and I don't plan on adding it until twrp is semi stable.
Current Features:
Upstreamed to 4.4.108
Updated EAS
ElectroUtil governor (renamed schedutil for compatibility)
Maple I/O scheduler
Adreno Idler
GPU Display state awareness
KCAL Support
Wake Gesture support
State Notifier
Disabled FSync
Power-Efficient Workqueues
Wakelock blocker
Devfeq wake boosting
FP Scanner speedups
CAF CPUIdle Updates
GPU+CPU Undervolted
Zen Interactive Tunings
Optimized string routines
Many warnings fixed
Optimized strlen use
Compiled with DragonTC 4.0
Polly optimizations
Installation:
Download the Electron boot image
OPTIONAL: Patch with Magisk
Run "adb reboot bootloader"
Run "fastboot flash boot /path/to/Electron-boot.img"
RECOMMENDED: Download Electron Defaults zip
Install as a Magisk module by pressing the "+" in the modules menu
Reporting Bugs:
Please follow this guide by @The Flash . If reporting a crash/reboot, provide both a dmesg and ramoops. Otherwise, provide a logcat and dmesg. CLICK HERE
Download:
Boot Image
Magisk Module
I would like to thank all of the great people whose support and help that I've received and whose work I've referenced to make this kernel a reality: nathanchance(TheFlash), boeffla(andi-p), FranciscoFranco, RenderBroken, flar2, xanaxdroid, R3V3NT3CH, arter97, DespairFactor, neobuddy89, ZeroInfinity, and anyone I missed!
XDA:DevDB Information
Electron Kernel for Taimen, Kernel for the Google Pixel 2 XL
Contributors
frap129
Source Code: https://github.com/frap129/taimen
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v4
Stable Release Date: 2017-12-26
Created 2017-11-15
Last Updated 2018-02-08
In this post, I will add descriptions of my original kernel features for users and developers to reference.
ElectroUtil Governor:
ElectroUtil is a schedutil based CPU Frequency governor, taking some queues from pwrutilx by ZeroInfinity, but with an overall different frequency selection algorithm.
ElectroUtil is a hexacore-biased governor, meaning that all 4 Silver and the first 2 Gold cores are preferentially granted higher frequencies at lower utilizations than the last 2 Gold cores to prevent excess use of more Gold cores than necessary. ElectroUtil is also device state aware, forcing lower frequencies when the device is suspended. This is handled via 2 different mechanisms. The primary mechanism is the 'suspend_capacity_factor' tunable, which is used such that
max = capacity * (suspend_capacity_factor + 1) / suspend_capacity_factor
where 'max' is the divisor of the frequency calulation
algorithm. For example, a value of 10 for the capacity factor result in a frequency that is 1/10th lower when the device is suspended. The second mechanism is a hard limit, set by the tuneables {gold/silver}_suspend_max_freq. If the requested frequency is higher than than the respective suspend max, the max will not be exceded. For the last 2 Gold cores, this max is always the minimum frequency.
Maple I/O Scheduler:
Maple is based on the Zen and Simple I/O schedulers. It uses Zens first-come-first-serve style algorithm with separate read/write requests and improved former/latter request handling from SIO. Maple is biased towards handling asynchronous requests before synchronous, and read requests before write. While this can have negative aspects on write intensive tasks like file copying, it slightly improves UI responsiveness. Like chill, maple also has power saving features. When the device is asleep, maple increases the expiry time of requests so that it can handle them more slowly, causing less overhead.
More to come...
Reserved
Errors out when I try to install module, but the kernel itself runs smooth
crossen0 said:
Errors out when I try to install module, but the kernel itself runs smooth
Click to expand...
Click to collapse
Thats weird, it installed for me. Will look into it asap.
Here's what the error said:
Ah yes, feed my flashing hunger muhahahaha!!! Install of kernel and module went without issues. I have noticed the following repeated in logcat but I had to run out for a few so only posting the error until I return home. Every 10-15 lines in logcat contains the below at least once.
11-14 20:57:26.139 811 811 E [email protected]: Governor not supported by powerHAL, skipping
crossen0 said:
Here's what the error said:
Click to expand...
Click to collapse
That's the same exact error ive been getting with no matter what module i try to flash with magisk. just started after i unistalled viper4android and tried reinstalling it. Can't find a workaround with it just yet either
crossen0 said:
Here's what the error said:
Click to expand...
Click to collapse
Thats a device issue. Try rebooting and/ redownloading
123SIT said:
Ah yes, feed my flashing hunger muhahahaha!!! Install of kernel and module went without issues. I have noticed the following repeated in logcat but I had to run out for a few so only posting the error until I return home. Every 10-15 lines in logcat contains the below at least once.
11-14 20:57:26.139 811 811 E [email protected]: Governor not supported by powerHAL, skipping
Click to expand...
Click to collapse
I forgot that the governor is powerHAL dependant for EAS devices. I'll look for a workaround until twrp works (requires installing a custom powerHAL), but for now, performance and battery don't seem to be affected much
Do I need to rename the .zip?
Maybe I'm missing something here? I have rebooted several times redownloaded the zip.
crossen0 said:
Do I need to rename the .zip?
Maybe I'm missing something here? I have rebooted several times redownloaded the zip.
Click to expand...
Click to collapse
Did you make sure that the Kernel flashed correctly? First time I flashed it I was still on the previous FLash kernel. Had to do it one more time and it finally showed Electron kernel under sett/about. Then I installed the Magisk Module w/the defaults successfully by using + once in Modules menu.
https://drive.google.com/file/d/1lPda5zNtK0FUXswmIIDEvPAGry4wZqss/view?usp=sharing
an21281 said:
Did you make sure that the Kernel flashed correctly? First time I flashed it I was still on the previous FLash kernel. Had to do it one more time and it finally showed Electron kernel under sett/about. Then I installed the Magisk Module w/the defaults successfully.
Click to expand...
Click to collapse
I am on Electron v1
crossen0 said:
I am on Electron v1
Click to expand...
Click to collapse
Hmm, the only other thing I did was copy the Electron-defaults.zip to the MagiskManager folder before installing as a mudule...
an21281 said:
Hmm, the only other thing I did was copy the Electron-defaults.zip to the MagiskManager folder before installing as a mudule...
Click to expand...
Click to collapse
I tried moving it over to MagiskManager folder but it still fails.
Made a quick workaround for the powerHAL issue, will include in v2 (Should only be a couple days)
crossen0 said:
Do I need to rename the .zip?
Maybe I'm missing something here? I have rebooted several times redownloaded the zip.
Click to expand...
Click to collapse
Sounds like a magisk issue. Try completely remove magisk and manager.
Going to dive in!! But, ugh! I have to go back to 8.0? THE HORROR!!! LoL.. Onward!
Up and running fine!!! Just a quick question..maybe OT? Maybe not.. But would this script have any issues with the kernel being installed from here?
https://forum.xda-developers.com/pixel-2-xl/development/mod-pks-tuning-script-t3702834
Is this kernel compatible with the pixel 2?
JayTheNinja said:
Is this kernel compatible with the pixel 2?
Click to expand...
Click to collapse
Really?? Look 5 posts above yours!
Badger50 said:
Really?? Look 5 posts above yours!
Click to expand...
Click to collapse
No, this is XL only! If it was Pixel 2 compatible, it would be in the Pixel 2 forum.
JayTheNinja said:
Is this kernel compatible with the pixel 2?
Click to expand...
Click to collapse
But... its not
No idea why there's such a large number of pixel 2 users that hang out in the xl forum
I present you Unicornblood Kernel as flashable standalone zip.
I built it straight from DU source with AnyKernel script.
This kernel only works with OmniRom, DU and Reaper!
Source Date: 2017-07-13
Features :
To know what's included you have to look at GitHub. I'm just to lazy to make a neat list.
DOWNLOAD:
https://drive.google.com/file/d/1krznYjanLUkwzw-1twPPddW6qfr9s8LX/view?usp=drivesdk
XDA:DevDB Information
Unicornblood Kernel, Kernel for the Nextbit Robin
Contributors
DirtyUnicorns
Source Code: https://github.com/DirtyUnicorns/android_kernel_nextbit_msm8992
Version Information
Status: Stable
Created 2018-01-21
Last Updated 2018-01-21
Thanks a lot to @L3R0N. @L3R0N tested it with CrDroid. Unfortunately, it does not work with LOS-based ROMs.
We have unfortunately bad luck. It is then on the device tree. DU and Omni use essentially the same device tree, but LOS is different. This kernel works only with AOSP-based ROMs. AnyKernel will only make the kernel adapt to the Ramdisk of the ROM, if I get it right.
But hey, I have now learned how to compile a kernel. :laugh:
I'm currently testing out your kernel on omni and it's running pretty nice. Running Hawktail 1.2 governor with greenify and naptime. I've been out most of the day, mostly using data, bluetooth's been on for the past 4 hours with spotify playing for about half of that, 3 hours SOT and I still have about 25% battery left.
demeez said:
I'm currently testing out your kernel on omni and it's running pretty nice. Running Hawktail 1.2 governor with greenify and naptime. I've been out most of the day, mostly using data, bluetooth's been on for the past 4 hours with spotify playing for about half of that, 3 hours SOT and I still have about 25% battery left.
Click to expand...
Click to collapse
That's really nice to hear. Thanks for your feedback.
Any Idea if it would work on CarbonROM? New to this kernel thing but really interested to try out just don't wanna break anything on the first try
[email protected] said:
Any Idea if it would work on CarbonROM? New to this kernel thing but really interested to try out just don't wanna break anything on the first try
Click to expand...
Click to collapse
No sorry, the kernel is not compatible with CarbonRom.
NurKeinNeid said:
No sorry, the kernel is not compatible with CarbonRom.
Click to expand...
Click to collapse
sorry for sounding like a complete noob here, but isn't the kernel supposed to work on AOSP ROMs and I checked on CarbonROM's page and it said that it was based on AOSP. If you could educate on what I'm missing that'd be really appreciated. Thanks
[email protected] said:
sorry for sounding like a complete noob here, but isn't the kernel supposed to work on AOSP ROMs and I checked on CarbonROM's page and it said that it was based on AOSP. If you could educate on what I'm missing that'd be really appreciated. Thanks
Click to expand...
Click to collapse
I tried flashing it on Carbon and it bootlooped so I wouldn't advise it. I guess the kernel will only run on Omni.
[email protected] said:
sorry for sounding like a complete noob here, but isn't the kernel supposed to work on AOSP ROMs and I checked on CarbonROM's page and it said that it was based on AOSP. If you could educate on what I'm missing that'd be really appreciated. Thanks
Click to expand...
Click to collapse
These are more or less semantic details. Strictly speaking, LOS is also AOSP-based. But in this case, CarbonRom's device tree is based on that of LOS. And this kernel only works with device trees that are based on Omnis device trees, for example, DU. I'm just as noob as you are and start to understand everything. This kernel was a kind of proof of concept for me. I am trying a lot to understand things better. Since last week I am testing the new interesting device related changes of LOS and have also now tested overclocking and underclocking.
NurKeinNeid said:
These are more or less semantic details. Strictly speaking, LOS is also AOSP-based. But in this case, CarbonRom's device tree is based on that of LOS. And this kernel only works with device trees that are based on Omnis device trees, for example, DU. I'm just as noob as you are and start to understand everything. This kernel was a kind of proof of concept for me. I am trying a lot to understand things better. Since last week I am testing the new interesting device related changes of LOS and have also now tested overclocking and underclocking.
Click to expand...
Click to collapse
please dont kill me but i have an off topic question:
can you make a kernel based on PA sources with this features:
lastest upstream linux update, lastest upstream cfq i/o scheduler, lastest interactive CAF gov, boeffla wakelock driver, simple thermal driver by sultanxda, power efficient workqueues patches by franciscofranco, westwood as default tpc/ip scheduler, kcal driver and dynamic cpu boost driver by sultanxda?
i can help you with the commits.
DiePirate said:
please dont kill me but i have an off topic question:
can you make a kernel based on PA sources with this features:
lastest upstream linux update, lastest upstream cfq i/o scheduler, lastest interactive CAF gov, boeffla wakelock driver, simple thermal driver by sultanxda, power efficient workqueues patches by franciscofranco, westwood as default tpc/ip scheduler, kcal driver and dynamic cpu boost driver by sultanxda?
i can help you with the commits.
Click to expand...
Click to collapse
No, I do not kill anyone lol. I'm not very experienced in kernel development. I could try it but why you dont share your wishes with @linckandrea? He recently asked for suggestions in his thread.
https://forum.xda-developers.com/nextbit-robin/development/kernel-pop-kernel-t3706069/page5
So I am on Omni. Can I can simply flash this via TWRP and then use Hawktail governor via EXKM?
/root said:
So I am on Omni. Can I can simply flash this via TWRP and then use Hawktail governor via EXKM?
Click to expand...
Click to collapse
Yes.
bootloop!
Hi there,
I tried running this kernel with Omnirom on a Robin/Ether.
Really happy with it, NFC is working and cpu governor is pretty solid.
Today I got a bootloop for a second time in a month.
The first time I haven't had time to look at it and thus recovered from a TWRP backup. This time I try to fix it manually.
Is there a roadmap or any guidelines in doing so?
Anyone else managed to revert it withought the use of restore process?
Why is it happening? Do you have any clues?
Regards,
mod
modestos said:
Hi there,
I tried running this kernel with Omnirom on a Robin/Ether.
Really happy with it, NFC is working and cpu governor is pretty solid.
Today I got a bootloop for a second time in a month.
The first time I haven't had time to look at it and thus recovered from a TWRP backup. This time I try to fix it manually.
Is there a roadmap or any guidelines in doing so?
Anyone else managed to revert it withought the use of restore process?
Why is it happening? Do you have any clues?
Regards,
mod
Click to expand...
Click to collapse
I think there are some things enabled on kernel side which is not present in omni device tree. Like Zram or ksm for example.
[HELP]
Is this kernel compatible with Resurrection Remox or Oxygen OS based ROMs?
Thank you
anuroop_nandi said:
Is this kernel compatible with Resurrection Remox or Oxygen OS based ROMs?
Thank you
Click to expand...
Click to collapse
No.
demeez said:
I'm currently testing out your kernel on omni and it's running pretty nice. Running Hawktail 1.2 governor with greenify and naptime. I've been out most of the day, mostly using data, bluetooth's been on for the past 4 hours with spotify playing for about half of that, 3 hours SOT and I still have about 25% battery left.
Click to expand...
Click to collapse
Hey everyone, thanks for this
I just wanted to find out do you flash the kernel after installing the ROM or before. i have tried flashing it afterwards but it just restarts
I'm running Omni ROM 8.1 for ether
dr_vaice said:
Hey everyone, thanks for this
I just wanted to find out do you flash the kernel after installing the ROM or before. i have tried flashing it afterwards but it just restarts
I'm running Omni ROM 8.1 for ether
Click to expand...
Click to collapse
A. After.
B. This is for Omni 7.1 not Oreo.
Hello,
I flashed this kernel, but I am facing some issues.
So firstly I don't have any backup, I flashed this kernel and then accidentally wiped system storage and data. Then tried to connect it to my laptop to transfer ROM files ( which connects as MTP device usually ), but the laptop is not able to detect the phone ( Unknown device ). I tried to use almost all the drivers available online, only to face failure. Tried using USB-OTG, even that isn't getting detected ( expected ).
Now I am stuck at TWRP Recovery, neither able to flash a ROM, nor flash the stock kernel.
Please help me out, I have no clue how to proceed further.
Thanks
A noob trying to learn.
What is LightningZap! kernel?
It is a lightweight, yet heavily tweaked and optimized kernel geared towards balancing performance and battery life.
Please read this ENTIRE post before downloading and flashing LightningZap! kernel.
Disclaimer: As with all custom kernels, you flash at your own risk. Always make a backup! I nor the associates of LightningZap! kernel, Teamfahq, or the testers group cannot and will not take responsibility for YOUR actions. I cannot always control what works and doesn't work with ROMs other than my own. If there is a bug, feel free to report it with logs, but note that the problem may be due to a conflict with coding int the ROM. If said condition exists, please discuss the concern with said ROM developer. If a bug condition does exist within the kernel and there is a known fix for said bug, please don't hesistate to link me to that fix. Make sure to give credit, thanks, and maybe even a cup of coffee to your developers. If you have a feature request, please feel free to share it as well.
Features:
Based off ElementalX kernel by flar
blue_schedul governor from blue_spark kernel thanks to eng.st
Ondemand gov Optimized for better performance while maintaining battery life
FIOPS ioscheduler by default (suggest leavving it that way)
My insane readahead tweak **** In HDK-Mod kernel manager, it reports "Not in range." This is normal DO NOT adjust. My tweaks optimizes readahead per demand usage.****
LZ4 compression
O3 Optimizations
zram
lz-sysctl tweaks
Sound control (speaker, earpiece and mic)
Backlight min setting
Adjust or disable vibration
Advanced Color Control and K-Lapse
Block wakelocks
NTFS r/w, CIFS and NFS support
WireGuard support
Option to disable fsync
Pass SafetyNet
LightningZap! kernel will work on oneplus 6 and oneplus 6T on stock OOs and most custom roms. There are 2 versions, PIE and NDP.
Diferences
PIE was built for custom roms
STOCK was modified for stock OOS (Does not include commits to fix fps that custom roms need)
NDP was slightly modified for SkyDragonOs by removing wake gestures. Wake gestures are natviely written into SkyDragonOs (and maybe more roms).
I have not tested all roms to see what works and what doesn't. So, I would suggest trying PIE first. If wake gestures (like dt2w) do not work, try NDP. Feel free to report what rom and LightningZap! kernel version you are using.
Bug reporting is HIGHLY encouraged, but please accompany your reports with logs. I cannot do much to fix things without them. Pruning of the logs is deeply appreciated as well.
I feel that if you are here, you already know how to flash a custom kernel. If not, close this page and do some research about it first. This will not erase recovery or root when flashing. But, I would like to quote @eng.stk
Warning: If you come from other kernel or have any issues, you should dirty flash your ROM before flashing LightningZap! zip to avoid problems.
Reflash ROM -> if you want root flash SuperSU or Magisk (default, no plugins/modules) -> flash LightningZap!.
If you are already rooted or upgrading between LightningZap! versions, just flash the kernel zip. Also uninstall or clean data of any kernel control app you're using.
Click to expand...
Click to collapse
Download links:
LightningZap! kernel PIE- Updated 10-07-2019
LightningZap! kernel NDP
LightningZap!-kernel-STOCK
Changelog
XDAevDB Information
LightningZap! kernel for OnePlus 6/6T
Special thanks to:
flar, eng.stk, HolyAngel Kernel Source: OnePlus6T-LZ
Version Information
Status: Stable
Current Stable Version: 2.3
Stable Release Date: 10-05-2019
ROM tracker
Here I will post what version of LightningZap! kernel works with what ROMs. As well as any noted bugs with said rom.
PIE
Most custom roms
NDP
SkyDragonOs
Stock
Stock OOS
It sounds very interesting! But a doubt that not before the SkyDragon rom was running the HolyDragon kernel? This would be the evolution of that kernel?
It sounds very promising! As soon as possible I will try it!
Thank you man!!
thomas.raines said:
Here I will post what version of LightningZap! kernel works with what ROMs. As well as any noted bugs with said rom.
PIE
Stock OOS
NDP
SkyDragonOs
Click to expand...
Click to collapse
Thank you so much. Do you recommend sticking with schedutil, which is default I believe, or do you prefer Onedemand or Blu instead? Thanks again for the kernel, I'm checking it out now.
---------- Post added at 04:18 PM ---------- Previous post was at 04:14 PM ----------
Everything seems great so far except one thing. Has anyone else noticed that their fingerprint sensor stopped working on OOS stable? Or could this just be a coincidence for me?
Ryano89 said:
Thank you so much. Do you recommend sticking with schedutil, which is default I believe, or do you prefer Onedemand or Blu instead? Thanks again for the kernel, I'm checking it out now.
---------- Post added at 04:18 PM ---------- Previous post was at 04:14 PM ----------
Everything seems great so far except one thing. Has anyone else noticed that their fingerprint sensor stopped working on OOS stable? Or could this just be a coincidence for me?
Click to expand...
Click to collapse
Isnt working for me either
fosgate24360 said:
Isnt working for me either
Click to expand...
Click to collapse
Yeah, I tried to reregister my FP but it won't let me.
Ryano89 said:
Yeah, I tried to reregister my FP but it won't let me.
Click to expand...
Click to collapse
It's not going to work on OOS as he's got the FOD hacks required for functional fingerprint on custom ROMs. Doing this breaks fingerprint on OOS, and removing them will break it on custom ROMs. The only way to accommodate both currently is with two separate kernel variants.
Great work Thomas
Riddle5 said:
It sounds very interesting! But a doubt that not before the SkyDragon rom was running the HolyDragon kernel? This would be the evolution of that kernel?
Click to expand...
Click to collapse
Completely different kernel from HolyDragons.
Ryano89 said:
Thank you so much. Do you recommend sticking with schedutil, which is default I believe, or do you prefer Onedemand or Blu instead? Thanks again for the kernel, I'm checking it out now.
---------- Post added at 04:18 PM ---------- Previous post was at 04:14 PM ----------
Everything seems great so far except one thing. Has anyone else noticed that their fingerprint sensor stopped working on OOS stable? Or could this just be a coincidence for me?
Click to expand...
Click to collapse
For governor, use whatever fits your needs the most. I recommend trying all 3 to see which on egives you the most performance and battery life.
return.of.octobot said:
It's not going to work on OOS as he's got the FOD hacks required for functional fingerprint on custom ROMs. Doing this breaks fingerprint on OOS, and removing them will break it on custom ROMs. The only way to accommodate both currently is with two separate kernel variants.
Click to expand...
Click to collapse
Yep... Accidentally merged those commits to the PIE branch. Running new build now. oops...
PIE branch updated. Fingerprint should be fixed now.
The New Update Is Buttery Smooth Bro Great Work Fp Works Better Than Stock Oos the only thing is the gaming performance has came down can experiencing shutter lags, and fps drops any fixes over that rest is just amazing bro .
Dhairya said:
The New Update Is Buttery Smooth Bro Great Work Fp Works Better Than Stock Oos the only thing is the gaming performance has came down can experiencing shutter lags, and fps drops any fixes over that rest is just amazing bro .
Click to expand...
Click to collapse
With your favorite kernel manager app, try using ondemand governor and lowering the up_threshold value adjust the sampling rate.
Using 3D benchmark app with Sling Shot Exteme setting up_threshold at 70 (default value) OpenGL ES 3.1 scored 4632 and Vulkan came in at 4272
Dropping it to 15 (lowest possible value)
OpenGL ES 3.1 scored 4857 and Vulkan came in at 4456
Setting it to 90
OpenGL ES 3.1 scored 4337 and Vulkan came in at 4068
These are overall scores and only an example. Results may very per device.
You can also try raising the sampling_rate as well. But I think the default value is best.
Be aware when adjusting these values, your perfomance vs battery life is effected.
lower up_threshuold will increase performance and decrease battery life whereas higher up_threshold decreases performance but raises battery life. Adjusting these values too high/low can cause the device to become unstable or overheat. Make your adjustments in small increments and if you notice a significant lag or your device is starting to get too hot, you can change them back and avoid complete device failure.
And by battery life, I mean the discharge rate, not the length of time until your battery takes a poop and you have to replace it or your phone.
New download link for pie branch. New branch added STOCK.
So, as pointed out by return.of.octobot , the PIE branch fp worked but became broken after reverting the commit for fp on custom roms. So, I made a new branch for OOS only and the PIE branch is for custom ROMs.
Tried flashing this stock version kernel on OOS 9.0.17 via FK manager app and got the abort message with error as unsupported device. Please see attached screenshot and let me know if there is something I need to change.
deepu458 said:
Tried flashing this stock version kernel on OOS 9.0.17 via FK manager app and got the abort message with error as unsupported device. Please see attached screenshot and let me know if there is something I need to change.
Click to expand...
Click to collapse
Flash in recovery. Since this is not a franko kernel, the franko kernel app won't work...
thomas.raines said:
Flash in recovery. Since this is not a franko kernel, the franko kernel app won't work...
Click to expand...
Click to collapse
Hello dear dev, is it working on 10.3.0 OOS for OP 6?cause the latest build is from October 2019...
James Blode said:
Hello dear dev, is it working on 10.3.0 OOS for OP 6?cause the latest build is from October 2019...
Click to expand...
Click to collapse
The thread title says it all...OOS9/ Pie.
James Blode said:
Hello dear dev, is it working on 10.3.0 OOS for OP 6?cause the latest build is from October 2019...
Click to expand...
Click to collapse
The current released and stable version is for android 9.0/pie.
Thre android 10 version is still in testing.
thomas.raines said:
The current released and stable version is for android 9.0/pie.
Thre android 10 version is still in testing.
Click to expand...
Click to collapse
Thanks for letting me know...ill wait for this great kernel...