Develop Bugs

[KERNEL][N6P] FrancoKernel ⚡️- r77 - 7th December - Oreo & Pie

Hi all.
Compatibility:
It should work on any rom by following this logic:
Builds from r1 to r23 are Android 6.0.1 Marshmallow only (up until June's security patches)
Builds from r24 are for Android 6.0.1 Marshmallow only from July's security patch up to the r28.
Builds from r29 are for Android 7.0 Nougat.
Builds from r40 up to r49 are for Android 7.1.1 Nougat only.
Builds from r50 up to r55 are for Android 7.1.2 Nougat.
Builds from r56 up to r64 are for Android 8.0.0 Oreo.
Builds from r65 are for Android 8.1.0 Oreo.
Download:
https://francokernel.app
Installation:
Flash the zip in your recovery
or
Auto-flash from Franco Kernel Updater app
Features:
1 - Legendary battery life
2 - Flash & forget
3 - Typical interfaces like display adjustments, sound control, vibration control, and all that boring stuff
4 - Bypasses the verified boot flag for Android Pay compatibility (root still breaks Android Pay but that's your own problem)
5 - Idle power consumption reduced to the absolute minimum (if you have wakelocks from 3rd party apps you're obviously on your own)
6 - Support for FKUpdater's Performance Profiles
7 - Magical support, I'm here every day, checking posts almost hourly, ready to help anytime (well, unless you fail to read the OP, which contains most info you need)
8 - Seemless integration with my app FKUpdater
9 - No crap placebo patches, or "magical" optimizations
10 - Probably more, check my github for all the details - the code speaks for itself
Changelog:
https://francokernel.app
Scroll down, choose your device & select the latest release to see the changelog.
Source:
https://github.com/franciscofranco/angler
Power Profiles
https://forum.xda-developers.com/nexus-6p/general/power-profiles-francokernel-kernel-t3742799
Follow me on the interwebs
Google+
Twitter
Google+ FK community
https://plus.google.com/u/0/communities/117966512071636110546
Kernel Manager for Franco Kernel
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!

Yes it's about time!

FKUpdater users from previous phones: support for this device will be added as soon as realistically possible.
My main focus on r1 release was to improve battery life as much as possible. I'm very happy with it.
If you want a detailed change-log check my git.
I'm sure you're going to love it.

Yayyyy!! Franco is here!

r1 is only for 6.0.1, don't flash if you're not using it. Also you must use the new system-less SuperSu, 2.60 or newer.

YESSSSSSSSSSSSSS. . Been waiting for this..

Great to see your kernel here! Your kernels are always battery sippers!

giant22000 said:
Great to see your kernel here! Your kernels are always battery sippers!
Click to expand...
Click to collapse
I'm sure you'll find the same with this one Just make sure you're on 6.0.1 before flashing.

franciscofranco said:
I'm sure you'll find the same with this one Just make sure you're on 6.0.1 before flashing.
Click to expand...
Click to collapse
10-4
Already on 6.0.1

Thank you so much Franco! I'm sure I speak for the majority when I say WE LOVE YOUR KERNELS! Rock on! +1

xReaper7x said:
Thank you so much Franco! I'm sure I speak for the majority when I say WE LOVE YOUR KERNELS! Rock on! +1
Click to expand...
Click to collapse
You're ****ing welcome

Woohoo, the thread lives. Been testing the kernel for the past couple of days prior to r1 and it's been a pretty good experience in battery and performance.
Definitely recommended

franciscofranco said:
r1 is only for 6.0.1, don't flash if you're not using it. Also you must use the new system-less SuperSu, 2.60 or newer.
Click to expand...
Click to collapse
Why do we have to use the system-less? Will normal system root not play well with the kernel?

Fair enough to assume we should reflash SuperSU 2.61 after the flash of a zip?
Sent from my Nexus 6P using Tapatalk

Thanks Franco your kernels are to notch. Flashed thanks for your work!

Neverendingxsin said:
Why do we have to use the system-less? Will normal system root not play well with the kernel?
Click to expand...
Click to collapse
Yes will traditional root not work with this Kernel
Sent from my Nexus 6P using XDA Free mobile app

Neverendingxsin said:
Why do we have to use the system-less? Will normal system root not play well with the kernel?
Click to expand...
Click to collapse
Because for 2.52 to work it needs a different sepolicy bin, and I can't use the old 6.0 binary from CF's initial Nexuses pre-rooted boot.img. And because system-less SuperSu is the future and it will let you flash OTAs on your device without wiping or extra cleaning.
hajabooja said:
Fair enough to assume we should reflash SuperSU 2.61 after the flash of a zip?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes.

trlash said:
Thanks Franco your kernels are to notch. Flashed thanks for your work!
Click to expand...
Click to collapse
You're ****ing welcome

franciscofranco said:
Because for 2.52 to work it needs a different sepolicy bin, and I can't use the old 6.0 binary from CF's initial Nexuses pre-rooted boot.img. And because system-less SuperSu is the future and it will let you flash OTAs on your device without wiping or extra cleaning.
Click to expand...
Click to collapse
Thanks for the quick response. Where can I find information on how to go from system to systemless root, can't seem to find it on XDA (or i'm completely missing something).

Franco kernels
This is the best development (pun intended) of the day! Thanks Franco!

[KERNEL][OP5] FrancoKernel ?- r49 - 27th Aug · Pie & custom roms

Hi all.
Compatibility:
Builds from r1 up to r12 are for Android 7.1.1 Nougat OxygenOS based roms only.
Builds from r13 are for Android 8.0.0 Oreo OxygenOS based roms only.
Builds starting with r18 work with Android 8.1.0 Custom roms.
Builds starting with r28 up to r32 work with OxygenOS 5.1.0 Android 8.1.0
Builds starting with r33 work with OxygenOS 5.1.5 Android 8.1.0
Builds starting with r40 are for OxygenOS 9.0 Android Pie.
Builds starting with r44 are also available for custom roms such as LineageOS.
Download:
https://francokernel.app
Installation:
Flash the zip in your recovery
or
Auto-flash from FK Kernel Manager app, it's magical
Changelog:
https://francokernel.app
Scroll down, choose your device & select the latest release to see the changelog.
Source:
https://github.com/franciscofranco/OP5-5T-unified
Follow me on socials for updates and interesting tidbits
Twitter[/URL
FK Kernel Manager video
[url]https://www.youtube.com/watch?v=ARdNqh71D0E
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!

Wow nice! For OOS?

As usual there's a large focus on battery life. F2FS is upstreamed to the latest version and I spent a couple days single picking useful commits from Qualcomm's repository with fixes and power consumption improvements.
You should see an improvement in battery life.

Beukhof1 said:
Wow nice! For OOS?
Click to expand...
Click to collapse
Yes.

wowww Franco is here!

25% off sale on FK Manager & Updater for the next 48 hours to celebrate adding One Plus 5 support
https://play.google.com/store/apps/details?id=com.franco.kernel

I'm wait this moment. Thanks FF!

@franciscofranco The king is here!!!!Tnx buddy!!

can it be flash over another custom kernel?

Thank you for supporting Oneplus 5! Using now and it's very smooth.
Just want to report also that the stock screen gestures (double tap to wake, draw O for camera etc) are not working yet

lohaanaa said:
can it be flash over another custom kernel?
Click to expand...
Click to collapse
Nope....first stock kernel...after custom one....

Great work Franco!
After a reboot, the phone boots to default color calibration and it takes like 10-20 seconds to switch to DCI-P3 or SRGB.
PS:Gestures are broken too.

The kernel is systemless?
Sent from ONEPLUS A5000 by Tapatalk

v7 said:
After a reboot, the phone boots to default color calibration and it takes like 10-20 seconds to switch to DCI-P3 or SRGB.
PS:Gestures are broken too.
Click to expand...
Click to collapse
Color calibration did not reset for me. Working fine. But Gestures don't work when screen is off.

I don't see the discount price for the Manager & Updater in the PlayStore.
Edit: price already updated in the store

@franciscofranco
fsync seems to be causing issues for me. With fsync disabled some apps fc after being cleared and some other work fine. After reenableing fsync everything returns to normal.
I´am running the latest stock rom with the only modificatiion being your kernel and magisk.
here is a short vid. of it in action: https://gfycat.com/MemorableMemorableCaecilian
logcat (sorry its quite huge ) https://www.dropbox.com/s/w2rbudldqw3ofvr/log.txt?dl=0

AlfalfaX said:
fsync seems to be causing issues for me. With fsync disabled some apps fc after being cleared and some other work fine. After reenableing fsync everything returns to normal.
I´am running the latest stock rom with the only modificatiion being your kernel and magisk.
here is a short vid. of it in action: https://gfycat.com/MemorableMemorableCaecilian
Click to expand...
Click to collapse
Grab a logcat.

Nice, I missed you (used Franco on my 3T). Already have the app, but nice for new users with discount :highfive:

Nice thanks

lohaanaa said:
can it be flash over another custom kernel?
Click to expand...
Click to collapse
Flash full zip. Let it boot. Boot back too twrp then flash kernel

[KERNEL] Unicornblood Kernel [2018.01.21]

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.

Future Updates (official) or Custom Rom?

Hi everyone!
I have my OP 5t (8/128) since release date and it is still my favourite phone!
I'm thinking about future update policy from OP... Still running OOS 9.0.4, but how many updates will we get in the future?
Is it better to switch to a Custom Rom for better and longer support in the future? If yes - what Custom Rom do you prefer and why?

stefan.irmen said:
Hi everyone!
I have my OP 5t (8/128) since release date and it is still my favourite phone!
I'm thinking about future update policy from OP... Still running OOS 9.0.4, but how many updates will we get in the future?
Is it better to switch to a Custom Rom for better and longer support in the future? If yes - what Custom Rom do you prefer and why?
Click to expand...
Click to collapse
Pretty sure they will update 5t to q, dont know what will happen after that.
As for custom roms, try anything you want and see what suits your taste. Resurrection remix is a good example for customizations (or aex, havoc, coltos etc)
Omni Treskmod is kinda a flash and use style of rom. It is almost like Pixel Experience. You can also try diffrent kernel-rom combinations. You can try HMP and EAS based kernels. EAS is the one google have in their phones. You can google it up.
At the moment im trying DerpFest. My top 5 roms are;
1.Aex-Krieg(love krieg aex kernel)
2.ColtOS(Reminds me miui cause of it's diffrent recents style)
3.DerpFest(love it's boot animation and wallpapers)
4.Omni Treskmod(simple custom rom that you will never have a headache with but lacks customization)
5.CrDroid(enough customizations and overall stability.)
Some of the roms have problems with camera2api with WhatsApp and Instagram. I have asked many devs and thankfuly thry have fixed those problems. I would stay close with roms that have active telegram groups as you might need to troubleshoot if you find a bug.
Some roms have outdated xda threads such as ViperOS(saw a comment),ResurrectionRemix(latest builds in their sourceforge). So be sure to check their websites(if they have one) for latest builds before you download an older one.
Hope it helps...
Sent from my OnePlus 5T using XDA Labs

Thanks a lot for your opinion!
I tried different Custom Roms, but all have one or two bugs, so i turned back to stock OOS... The most stable and bugfree Custom Rom for me was Pixel Experience!
Hope we will get a few updates in the future for our OP 5t

gsser said:
Pretty sure they will update 5t to q, dont know what will happen after that.
As for custom roms, try anything you want and see what suits your taste. Resurrection remix is a good example for customizations (or aex, havoc, coltos etc)
Omni Treskmod is kinda a flash and use style of rom. It is almost like Pixel Experience. You can also try diffrent kernel-rom combinations. You can try HMP and EAS based kernels. EAS is the one google have in their phones. You can google it up.
At the moment im trying DerpFest. My top 5 roms are;
1.Aex-Krieg(love krieg aex kernel)
2.ColtOS(Reminds me miui cause of it's diffrent recents style)
3.DerpFest(love it's boot animation and wallpapers)
4.Omni Treskmod(simple custom rom that you will never have a headache with but lacks customization)
5.CrDroid(enough customizations and overall stability.)
Some of the roms have problems with camera2api with WhatsApp and Instagram. I have asked many devs and thankfuly thry have fixed those problems. I would stay close with roms that have active telegram groups as you might need to troubleshoot if you find a bug.
Some roms have outdated xda threads such as ViperOS(saw a comment),ResurrectionRemix(latest builds in their sourceforge). So be sure to check their websites(if they have one) for latest builds before you download an older one.
What's your top pick in Kernel?
Click to expand...
Click to collapse

VirginPancake said:
gsser said:
Pretty sure they will update 5t to q, dont know what will happen after that.
As for custom roms, try anything you want and see what suits your taste. Resurrection remix is a good example for customizations (or aex, havoc, coltos etc)
Omni Treskmod is kinda a flash and use style of rom. It is almost like Pixel Experience. You can also try diffrent kernel-rom combinations. You can try HMP and EAS based kernels. EAS is the one google have in their phones. You can google it up.
At the moment im trying DerpFest. My top 5 roms are;
1.Aex-Krieg(love krieg aex kernel)
2.ColtOS(Reminds me miui cause of it's diffrent recents style)
3.DerpFest(love it's boot animation and wallpapers)
4.Omni Treskmod(simple custom rom that you will never have a headache with but lacks customization)
5.CrDroid(enough customizations and overall stability.)
Some of the roms have problems with camera2api with WhatsApp and Instagram. I have asked many devs and thankfuly thry have fixed those problems. I would stay close with roms that have active telegram groups as you might need to troubleshoot if you find a bug.
Some roms have outdated xda threads such as ViperOS(saw a comment),ResurrectionRemix(latest builds in their sourceforge). So be sure to check their websites(if they have one) for latest builds before you download an older one.
What's your top pick in Kernel?
Click to expand...
Click to collapse
Overall performance - battery = Aex Krieg
Best battery life = Mad Kernel
Best performance = Weeb Kernel
Sent from my OnePlus 5T using XDA Labs
Click to expand...
Click to collapse

gsser said:
VirginPancake said:
Overall performance - battery = Aex Krieg
Best battery life = Mad Kernel
Best performance = Weeb Kernel
Sent from my OnePlus 5T using XDA Labs
Click to expand...
Click to collapse
What's your opinion about RenderZenith or Weeb kernel? Those two are EAS right? Also franco kernel?
Click to expand...
Click to collapse

VirginPancake said:
gsser said:
What's your opinion about RenderZenith or Weeb kernel? Those two are EAS right? Also franco kernel?
Click to expand...
Click to collapse
Franco kernel and app feels like too complicated for me. RenderZenith is good if you want only eas and no other custom stuff(it will give you a little bit better results compared to stock kernel.). It is best for people who want to flash and use. Weeb also got better with it's beta versions but still, i would use it if i was playing heavy graphical games. If you want battery and stuff you can set manually go for Aex-Krieg kernel.
If you want pure HMP kernel that is focused on battery i would suggest Mad Kernel. Eas is not really best for battery, it is best for balanced
Dont get me wrong, franco kernel might be good but it doesnt suit me and i really didnt get use to it.
Click to expand...
Click to collapse

KERNEL] [LightningZap!-6/6T] [OOS 9.* / Pie Custom ROMs]

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...