Database Develop

[KERNEL] [4.4] Werewolf kernel v008 [15/02/2015] SM-T210(R) and T211

Hey guys
As you already might have read in either the CM11 dev thread or the Q&A section, I am working on a custom kernel for our T210(R) and T211. It's still in a pretty early stage, but the current build is fully stable, so I thought why not share it
As I'm pretty new to this community, a few words about myself: My (only) device I have been working on is the LG Optimus 4x HD, for which I also made a custom kernel (also named werewolf kernel, who would have thought of that ). Me and 2 other fellow RDs were able to "switch" many blobs with the ones from grouper, which fixed many, many issues we were facing in 4.4 with the stock 4.1 blobs. I am the official maintainer of namelessROM and vanir for the 4x HD, and am also compiling GummyROM, LegoROM, unofficial CM 11 (using grouper blobs) and SlimKat for the 4x HD on a nightly base. And as soon as we have a proper device tree for our tab, I'm sure I can port the Tab3 to all those ROMs
Now, enough chit chatting, let's talk about the kernel
It's based on @ketut.kumajaya's blackhawk kernel (thanks again, mate ) From v004 on we are based on official KitKat sources, with some additions such as:
Features:
Various network tweaks
Entropy tweaks
I/O speed improvements
cortex a9 and neon omtimizations
Added frandom
Tweaked vm dirty ratios
Dynamic read-ahead values
Added I/O schedulers: ROW, SIO, BFQ, FIOPS, V(R)
Optimized AES and SHA1 routines
Added CPU governors: Lionheart, Adaptive, Intellidemand, Hotplug, Hyper
Reduced RAM usage from logger
Updated lowmemkiller
Overclocked to 1.420 GHz by default
Disabled vsync for better 2D performance
Overclocked GPU up to 624MHz (default 416MHz)
Custom user voltage control (CPU)
Undervolted by default (-25mV)
S2W and DT2W (WIP)
Fast Charging
KSM
Bugs:
You tell me!
Installation:
Download the kernel from HERE
Reboot into recovery (recommended to make a nandroid)
Flash the kernel zip
Recommended to wipe /cache
Reboot and enjoy!
And remember to remove phservice if you want to change some CPU/GPU settings yourself
Notes:
See 2nd post
GPL:
Kernel sources
Kernel Modules (only for v001 - v003)
Used defconfig
Used build script
Thanks:
@ketut.kumajaya for the initial kernel base
@gr8nole for general help, info and testing
XDA:DevDB Information
Werewolf kernel SM-T210/T211, Kernel for the Samsung Galaxy Tab 3
Contributors
laufersteppenwolf
Kernel Special Features: Tuned for best possible performance
Version Information
Status: Stable
Created 2014-07-21
Last Updated 2015-05-25

Tweaks and other stuff
Since v002, we have an updated lowmemorykiller. It behaves a bit snappier than the old one, also with the default minfree values. However, in case you like to tweak your device a bit to make it even more snappy (like me ), I tweaked the minfree values a bit to slightly increase the free RAM without really affecting the multitasking experience. The script can be found in the attachment. All you need to do is to extract the script and place it in your /system/etc/init.d/ folder and that's it. The values will be automatically set on boot.
UV interface
The min possible voltage is 1000mV for now, and the max one is 1400mV. If you want me to lower the min voltage, please let me know.
Also, please note, that the voltage has to be changed in 12.5mV steps. If you apply for example 1110mV, it will be rounded down to 1100mV.
Fast Charge interface
The main interface is inside /sys/kernel/fast_charge/*
/sys/kernel/fast_charge/force_fast_charge (rw)
0 - disabled (default)
1 - use custom mA configured through the sysfs interface (see below)
/sys/kernel/fast_charge/ac_charge_level (rw)
rate at which to charge when on AC (1.8A to 2.3A)
/sys/kernel/fast_charge/usb_charge_level (rw)
rate at which to charge when on USB (0.5A to 1.0A)
/sys/kernel/fast_charge/failsafe (rw)
0 - disabled - allow anything up to 2.3A to be used as AC / USB custom current (USE WITH CAUTION!)
1 - enabled - behaviour as described above (default)
/sys/kernel/fast_charge/version (ro)
display fast charge version information
New kmsg layout
From v008 onwards the kmsg looks a tiny bit different. Instead of displaying the time since boot, it logs the actual time and date.
Now, you may ask yourself: "does that any good?" Sure it does. When you encounter an issue and grab a log, you can send it my way saying "the issue happened at 15:35". It is way harder to find out the exact time (in seconds) since the device booted, right?

When changing the CPU gov, you might want to keep THIS (4.1) or THIS (4.4) in mind
Changelog:
v008 [15/02/15]
- Disabled zcache
- Added KSM (including deferred timer to save battery)
- Tweaked zRAM
- New kmsg log layout (see 2nd post for more details)
- Fixed kernel version in settings
- Disabled S2W and DT2W by default
When you flash this version, please wipe cache, otherwise bad things could happen
v007 [08/12/04] RIP Beth
- Slightly more RAM from logger
- S2W and DT2W (Still WIP)
- Decreased min possible CPU voltage to 800mV
- Undervolted by default (-25mV)
- Fast Charge support
v006 [01/11/14] MOAH CPU
- Added CPU UV interface
- OC'ed further to 1420MHz
- Max GPU freq limited to 624MHz until all issues are resolved
- Fixed init.d support on T211
v005a Minor fix
- Fixed DeviceControl GPU support
- Output all GPU freqs in Hz instead of KHz
v005 [18/10/2014] SM-T211 support
- Added support for the T211 variant (thanks to @sscsps for testing)
- Merged latest Sammy updates
- Enabled I/O accounting (only needed for devs)
- zcache enabled by default
- GPU OC up to 624MHz (default is 416MHz)
v004 [25/09/2014] Android 4.4 support
- Re-based on latest KitKat sources
- Re-added almost all features from v003
- Removed 156MHz freq step (causing trouble for still unknown reasons)
- Overclocked to 1.344 GHz (instead of 1.205GHz)
- Disabled vsync for better 2D performance
- Disabled "reboot recovery" to avoid being stuck in recovery on old recoveries (special version)
v003 [31/08/2014]
- new govs: Hotplug, Hyper
- new freq step @ 156MHz
v002 [25/07/2014]
- reduced RAM usage from logger
- new/updated lowmemkiller (see attachment in 2nd post for init.d script with tweaked minfree values)
v001 [18/07/2014]
- initial release

good work you link where ? and nice job workıng 4.1.2 ???? 4.2.2 .4.4.2 kernel android version what? @safariking [MENTION=3034891]gr8nole[/MENTION
not working dont flash ı using ultimate rom safarinking by 4.1.2 soft brick device

Not working yet hope you get it working good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app

sorry guys, I just found the issue... my last commit breaks the GPU module so it doesn't compile, doesn't get copied over into the zip and so does not get replaced on your system, but the new kernel cannot load the stock module as I used another defconfig name...
Will be fixed ASAP
EDIT: Fixed and uploaded

laufersteppenwolf said:
sorry guys, I just found the issue... my last commit breaks the GPU module so it doesn't compile, doesn't get copied over into the zip and so does not get replaced on your system, but the new kernel cannot load the stock module as I used another defconfig name...
Will be fixed ASAP
EDIT: Fixed and uploaded
Click to expand...
Click to collapse
Nice work. This kernel works. Will monitor battery life and game performance.
Sent from my SM-T210R using XDA Free mobile app

laufersteppenwolf said:
When changing the CPU gov, you might want to keep THIS in mind
Click to expand...
Click to collapse
is there anyway to flash it on tab 3 t211 kk 4.4.2 firmware

big job thank can you add overclock gpu ? downclock?

gr9nole said:
big job thank can you add overclock gpu ? downclock?
Click to expand...
Click to collapse
You can check if there is OC available by installing "No-Frills CPU Control" from the google play store

a question about toolchain
@laufersteppenwolf
hi, i would like to know which toolchain you used to build this kernel, a direct link to it would be helpful.
also, using the supplied defconfig can i make [defconfig] and then make -j# or are there additional things to do?
i build kernel for tab3 10 fine but setting up my system for sm-t210 is proving stubborn. there is another project going on
that i would like to learn from and help with, your help would be appreciated.
thank you for reading.
m

Anil Shovo said:
is there anyway to flash it on tab 3 t211 kk 4.4.2 firmware
Click to expand...
Click to collapse
I do not think so, as I'm using the ramdisk from t210, which most likely isn't compatible with t211, and sure not with 4.4.2
gr9nole said:
big job thank can you add overclock gpu ? downclock?
Click to expand...
Click to collapse
step by step
moonbutt74 said:
@laufersteppenwolf
hi, i would like to know which toolchain you used to build this kernel, a direct link to it would be helpful.
also, using the supplied defconfig can i make [defconfig] and then make -j# or are there additional things to do?
i build kernel for tab3 10 fine but setting up my system for sm-t210 is proving stubborn. there is another project going on
that i would like to learn from and help with, your help would be appreciated.
thank you for reading.
m
Click to expand...
Click to collapse
for this build, I used CM's 4.6 toolchain, but that'll change soon
I will also push the build script and modules to github ASAP, so just wait for that, as setting up the modules and stuff isn't the most pleasant thing to do

Werewolf is not playing lol so what your saying is that we will be having cm 11 and aosp all the good stuff soon ?
Sent from my SM-T210 using XDA Premium 4 mobile app

I've used this kernel for 2 days. I have noticed the screen flickers on the 2nd day and while watching a movie (while plugged in) the tab was battery drained battery was 30% when I started watching. Can others confirm this?
Goodside. Battery life is enhanced and performance is the same. Nice work on this
Sent from my SM-T210R using XDA Free mobile app

trazfer said:
I've used this kernel for 2 days. I have noticed the screen flickers on the 2nd day and while watching a movie (while plugged in) the tab was battery drained battery was 30% when I started watching. Can others confirm this?
Goodside. Battery life is enhanced and performance is the same. Nice work on this
Sent from my SM-T210R using XDA Free mobile app
Click to expand...
Click to collapse
I was experiencing the exact same flickering myself as well, but on stock kernel
This flickering isn't kernel related, but ROM related. Sammy must have screwed up the auto backlight handling, as it only happens at some certain brightness values

No ir blaster
Edit: This is what I get when I open peel smart remote

laufersteppenwolf said:
I was experiencing the exact same flickering myself as well, but on stock kernel
This flickering isn't kernel related, but ROM related. Sammy must have screwed up the auto backlight handling, as it only happens at some certain brightness values
Click to expand...
Click to collapse
He is tottaly right, also sometimes when you are using this tab, the screen locks by itself

Ripshock said:
No ir blaster
Edit: This is what I get when I open peel smart remote
Click to expand...
Click to collapse
Check your build.prop to see what the ro.build.product shows.

gr8nole said:
Check your build.prop to see what the ro.build.product shows.
Click to expand...
Click to collapse
I am using stockrom series with a build for sm-t210 but I have used device spoofer and spoofed my original build sm-t210r

Ripshock said:
I am using stockrom series with a build for sm-t210 but I have used device spoofer and spoofed my original build sm-t210r
Click to expand...
Click to collapse
It works for me with the stock firmware/rom with this kernel.

[Kernel][5.1][Stock][Linaro 5.3] KaminariKernel R3 [7 July 2016]

KaminariKernel​
Code:
#include "std_disclaimer.h"
/*
* Your already voided warranty is now void again.
*
* 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 my *** off at you.
* Really hard.
*/
Hiya fellas.
This is my modded kernel for our loved Moto G 1st gen (LTE version). I decided to resume developing it since I realized I was wrong (I thought no one was interested in it). So here we are again.
Features:
Sources & Optimizations
- Based on Motorola's shared falcon/peregrine source
- Compiled with generic Linaro 5.3 toolchain
- Compiled with -O3 optimization & some more flags (e.g. Pipe flag)
- Optimized ARM RWSEM & Square Root algorithms
- Kernel-side NEON mode
- Some miscellaneous armv7 tweaks
Click to expand...
Click to collapse
Hotplugging Drivers
- Ye Olde MPDecision
- AutoSMP
Click to expand...
Click to collapse
Extra CPU Governors
- Bioshock
- Dancedance
- Impulse
- Lionheart
- Smartmax
- Yankactive
- Yankdemand
- Zzmoove
Click to expand...
Click to collapse
Extra I/O Schedulers
- Bfq
- Fiops
- Sio
- Vr
- Zen (Default)
Click to expand...
Click to collapse
Sound
- Faux's Sound Control
- Headset High Performance Mode
Click to expand...
Click to collapse
Screen/GPU
- Kcal Screen Control
- Dt2w/s2w
- State Notifier driver
- Adreno Idler
- GPU overclock & underclock (533MHz/100MHz)
Click to expand...
Click to collapse
Extra Sh*t
- USB Fast Charge
- Disabled gentle fair sleepers
- Extra TCP Congestion Controllers
- HID Driver (Use your phone as a USB keyboard/mouse)
- Compass & Accelerometer drivers now use State Notifier
- Fsync enabled by default
- Kexec-hardboot patch (for multirom compatibility)
- Power-efficient workqueues
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
Regular Version
Overclock-Ready Version Soon™
Click to expand...
Click to collapse
Looking for previous releases?
- All releases until 1.2.x: Go here
- All releases from 1.3 onwards: Go here
- KaminariLite (discontinued): Go here
- KaminariSL (previously Optimized Stock): Go here
Click to expand...
Click to collapse
Got into trouble and need to go back to the stock kernel?
Then you should click this link here, bud!
Click to expand...
Click to collapse
Flashing & Tweaking Instructions (Follow this very carefully!!!):
- Place the zip at the root of your phone's internal storage (This is very important! If you flash the zip from a subfolder, you'll be left without wi-fi!!!)
- Reboot into recovery
- Flash the zip
(Another way: Reboot into recovery without copying the zip, and flash it via adb sideload)
- (Optional) Wipe cache and/or ART cache
- Reboot and have fun!
Coming from another kernel? Then I suggest you to (at least!!!) dirty flash your stock rom and kernel in order to avoid any issues!
Wanna tweak it? Use Kernel Adiutor! (I do NOT support Synapse!!!)
Click to expand...
Click to collapse
Want some info on what this kernel offers you?
Then go here! (Credits to @AssToast for suggesting and to @gsstudios for creating the site!)
Click to expand...
Click to collapse
"Thank You" Section
- Motorola/Lenovo, for putting up them sources
- The CyanogenMod team
- @Flashhhh, his work kinda inspired me to do this
- @Aayushya, he provided the initial cherry-picks
- @faux123, for Sound Control & Intellithermal
- @savoca, for Kcal Screen Control
- @hurtsky, a huge load of cherry-picks came from his sources
- @Alberto97, for the Linux version bumps (.43 up to .109)
- @YoshiShaPow, for some more stuff
- Some more fellas whose names I can't remember
Click to expand...
Click to collapse
XDA:DevDB Information
KaminariKernel (Lollipop-Peregrine), Kernel for the Moto G
Contributors
kingkaminari
Source Code: https://github.com/Kamin4ri/KaminariKernel/tree/L
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R3
Stable Release Date: 2016-07-07
Created 2015-10-15
Last Updated 2016-07-09

Hey!!! Are you looking for the changelogs?
I'm moving them to this page here! So please wait!
F.A.Q. Read this before moaning!!!!!!
Q: ERMAHGERD DIS KERNEL SUCKZ, MAH BATTERY IS DEAD IN 30 MINS, PLZ HALP!
A: When I created this kernel, I never had the intention to have it decrease battery life. So before / instead of complaining, go check your f***ing wakelocks and fix them! The kernel isn't responsible for this, your apps and/or services are.
Q: Will this kernel work on AOSP / CM12.1 ROMs?
A: No.
Q: Will this kernel work on xyz rom?
A: No. Non. Nein. Title clearly says: STOCK.
Q: How do I report bugs?
A: If you wanna report a bug, then grab your kernel log - either by pulling /proc/last_kmsg (in case of a random reboot / kernel panic or oops) or copying the output of "dmesg" via shell - and paste it at pastie.org and link it in your post (or save it to a text file and attach it to your post). Don't bother getting logcats, they don't apply for kernel debugging purposes.
Q: How do I flash this?
A: I suggest you scroll up and read the OP. The instructions are there.
Q: How do I tweak this kernel?
A: Download Kernel Adiutor from the Play Store and have fun. For Synapse, scroll up and read the OP first.
Q: This kid is such a n00b!
A: Oh well then, why don't you go work on a kernel yourself, instead of criticizing my work and, by doing so, wasting your time?

Optimized Stock Kernel (aka "Kaminari SuperLite")
Since KaminariLite has been discontinued, and Kaminari has become cleaner regarding features, I've been working on a version closer to the stock kernel, only more optimized.
So here is my Optimized Stock kernel.
Differences in relation to the stock kernel:
- Compiled using my custom Linaro 5.2 toolchain
- Bumped to Linux version 3.4.110
- Compiled with -O3 and Graphite flags (Same as Kaminari)
- Most if not all of Kaminari's optimizations have been applied
- All governors except Interactive removed
- Default I/O scheduler changed to cfq
- Default TCP congestion algorithm changed to Westwood
- Supports both stock and GPE roms, regardless of filesystem (f2fs or ext4) used on /data
- Adds init.d support
- Default ZRAM size changed to 400MB
Differences in relation to Kaminari:
- All governors except Interactive removed
- All TCP congestion algorithms except Westwood and Reno removed
- Additional I/O schedulers (zen, vr, sio, fiops, bfq) removed
- Bricked Hotplug has been replaced by MPDecision
- All non-essential features (FauxSound, Kcal, Dt2w...) have been removed
- Stock PowerHAL has been re-enabled
- Version bump to 3.4.110 (Kaminari has been kept at 3.4.42)
- Compressed using LZO (Kaminari uses XZ)
Download it from here.
This one is mostly flash-and-forget. No need to tweak anything.
If you're coming from Kaminari, and you're using Kernel Adiutor, you MUST clear the app's data before flashing this build. If you can flash the stock kernel before flashing this, it's even better.

One more reserved...

Okay. Last reserved.

Oh guys... Can someone provide me their init.rc? So I can add proper init.d support

kingkaminari said:
Oh guys... Can someone provide me their init.rc? So I can add proper init.d support
Click to expand...
Click to collapse
Here the mine, :good:

Second test build is up! https://www.androidfilehost.com/?fid=24052804347838189
Changelog is in the second post.

pretty stable kernel as far as i can tell. There is just one thing.. how do i get the over clock to stick? no matter if i have intelliplug on or off it always changes back to default frequencies after a while

EpiccSkillZz said:
pretty stable kernel as far as i can tell. There is just one thing.. how do i get the over clock to stick? no matter if i have intelliplug on or off it always changes back to default frequencies after a while
Click to expand...
Click to collapse
Try a different governor. Interactive likes to reset the frequencies to their default values. Or the chipset may be incompatible (despite it still being - technically - only an msm8226 with lte support).

kingkaminari said:
Try a different governor. Interactive likes to reset the frequencies to their default values. Or the chipset may be incompatible (despite it still being - technically - only an msm8226 with lte support).
Click to expand...
Click to collapse
Could you please recommend me a governor?

EpiccSkillZz said:
Could you please recommend me a governor?
Click to expand...
Click to collapse
Either intelliactive or yankactive
Sent from my XT1033 using Tapatalk

Woww! Finally CPU overclock! It works very good! Thankyou man

I had read that overclock was virtually impossible because our phone was locked to a maximum CPU freq, it wasn't true? It's nice to have other options, thank you for the development.

rodsayd said:
I had read that overclock was virtually impossible because our phone was locked to a maximum CPU freq, it wasn't true? It's nice to have other options, thank you for the development.
Click to expand...
Click to collapse
I also believed that. But I once ran two Antutu benchmark tests, one with the default freq (1.2GHz) and the other with an increased freq (1.6GHz), and in the second test, I got a slightly higher score (which leads me to assume that the overclock actually works). Plus, my overclock implementation is different from the previous ones.

kingkaminari said:
I also believed that. But I once ran two Antutu benchmark tests, one with the default freq (1.2GHz) and the other with an increased freq (1.6GHz), and in the second test, I got a slightly higher score (which leads me to assume that the overclock actually works). Plus, my overclock implementation is different from the previous ones.
Click to expand...
Click to collapse
The phone has a locked multiplier, but it still have FSB overclock (like the old AMD athlom XP Days)

Dirty flashed on xt1039, it works. It's now time for tuning.
Thanks a lot! I was waiting for a kernel like this.
Is there the possibility to add the undervolting feature?

sclcn12 said:
Dirty flashed on xt1039, it works. It's now time for tuning.
Thanks a lot! I was waiting for a kernel like this.
Is there the possibility to add the undervolting feature?
Click to expand...
Click to collapse
I've tried to do that with falcon. I had to solve the merge conflicts manually, but in the end the phone wouldnt boot - it went into a red screen saying "watchdog reset detected" right after the motorola logo. So, with that being said, we wont have undervolting for now, at least till i manage to solve that conflict

Third test build up!
Download
Changelog is in the second post.

Thanks for the work, it's a great kernel. Working really great
Enviado desde mi XT1040 mediante Tapatalk

[EOL][KERNEL] [OnePlusX] [OOS 3.x.x/2.x.x] Boeffla-Kernel (12-06-2017)

Hi all,
some of you know me from the other OnePlus (One and Two) or Samsung devices areas, where I provide my kernels already for more than two years to OnePlus One, OnePlus Two, Galaxy S5, S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.)
Please note:
I am not heading to have as many features as possible implemented, this is not my design goal. If you are more into that, move on to other kernels. If you are searching for a good mix of improvements and new functions while not sacrificing stability, you are welcome here (see below the history section for more info).
Compatibility
Important: This kernel is only meant to be compatible with official OnePlus OOS and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
Important notes
]When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
Make sure you flash the correct kernel version, depending on whether you really use Oxygen OS or a different OS !!!
Also note: You have to use Boeffla-Config app which I provide on my homepage to tweak the kernel. 3rd party apps will not be able to unleash the full power of the kernel.
Saying that, the Boeffla-Sound app in Play Store is not designed to work on the OPX, neither was it developed by me, hence it will never work on the OPX ever. Boeffla-Config is the way to go here !!!
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app (quite outdated, as it is focused on S3 still).
Click here to learn about using the config app (quite outdated, as it is focused on S3 still).
I will refuse to give support if you do any undervolting and experience freezes or hot reboots.
I will also not provide any support if you do not use Boeffla-Config app to tweak the kernel, other 3rd party tweaking apps are known (and intended) to cause issues.
I will refuse to give support if you have xposed framework installed and reporting any kind of weird issues. My opinion to xposed it quite clear: too powerful for >90% of the users that just mess up their system with it.
Otherwise, you can get in touch with me via the support e-mail address: [email protected]
Please provide kernel version, rom version, a detailed issue description and ideally supporting screenshots or log files.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for Oxygen OS 3.x.x kernel - Click here
Change log for Oxygen OS 2.x.x kernel - Click here
Features
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 (you need at least version 2.2.29 or higher !!!) configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Additional governors: zzmoove, intelliactive, intellidemand, intellimm, wheatley, smartmax, smartmax_eps, slim, intellimm, pegasusq, nightmare, lionheart, impulse, ondemandplus, yankactive
Zzmoove supporting native hotplugging profiles
Additional schedulers: fiops, bfq, sio, tripndroid, zen
Many Hotplug tweak profiles (Default, Optimized, 1 core max, 2 cores max, 3 cores max, 2 cores min, 3 cores min, 4 cores min, 2 cores exact, 3 cores exact)
Notification LED control (fading, speed, brightness)
Boeffla-Sound engine (Headphones volume configurable currently)
True dynamic FSync (activated if screen on, deactived if screen off), configurable
Touch boost frequency and duration configurable, touch boost switch
CPU Overclocking up to 2.54 GHz
CPU Voltages interface for undervolting/overvolting
GPU idle frequency 27 Mhz added
GPU governor selection support with fixed simple_ondemand0
Show GPU frequency usage per frequency in Boeffla-Config
KCAL color control driver
Swipe2wake gestures
Swipe2sleep gestures
Haptic feedback control
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (default to on, can be disabled)
System Tweaks predefined supported
Kernel logger (dmesg) configurable
Charge rates for AC charger and USB charging separately configurable (set charge rate to 0 to have stock charge logic back)
Charge information display support via Boeffla-Config V2 app
CIFS support (module, do not mount inside /data, if you rooted with Chainfire SuperSu, make sure you uncheck the namespace separation in SuperSu app)
NFS support (module)
exFat opensource support
NTFS support (module) - read-only
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Multiple additional TCP congestion algorithms available
Swap supported
init.d support (in /system/etc/init.d - set correct permissions!)
Default entropies increased
Automatic EFS backup
Full support for mpdecision for best compatibility and smoothness (no min cpu frequency reset, use Boeffla-Config to configure min frequencies only)
Integrated full busybox 1.24.2 (own compilation)
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Presets supported in Boeffla-Config by kernel (Extreme power, power, normal, battery friendly and battery saving)
Kexec hardboot patch for multirom usage (not supported, not fully working)
Google gcc 4.8 toolchain used for best stability
Always using latest Oxygen OS Initramfs
Always based on latest Oxygen OS kernel sources (https://github.com/OnePlusOSS/android_kernel_oneplus_msm8974)
Note: I do NOT upstream the kernel to higher Linux kernel versions anymore as this usually has zero benefit but likely introduces new issues + is a waste of effort in the end
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
History and design targets
Basically I created my first Boeffla-Kernel in 2012 as there was no kernel for the Samsung Galaxy S3 around that had exactly the mix of functionalities that I wanted. I wanted to have full flexibility in undervolting and charge rates for instance, but did not like the sharpness and/or brightness tweaks many kernels have implemented as per default.
Hence, I began to create my own kernel after a while, adding all the features I like. This is the result of my work, which in the end I decided to share with you. I hope you like it as much as I do.
The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. Also it does not aim to have the broadest feature set available everywhere.
It aims more for a good mix of all, not sacrificing stability and functionality in the end.
And - most important: It aims to stay quite close to stock !!!
These design targets are also valid for the OnePlus kernel here!!!
This said, I will definitely NEVER implement:
things I do personally not need
things I do not like
things that are in any way dangerous
anything which is highly experimental
f2fs - it is known to cause various issues and compatibility problems
custom hotplugging algorithms
a CAF based kernel
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it if it falls into the listed categories. Everything else I am happy to check and decide.
And: I do not really care about benchmark numbers, they say almost nothing as long as something is not completely wrong. Important for me is the feel-good factor.
I am also not interested in gaming at all, so never expect a gamer kernel. It will just not happen...
Compatibility
To reiterate it again: Flash the correct kernel depending on whether you are using Oxygen OS or another rom !!!
Configuration of the kernel
To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from the downloads section on www.boeffla.de.
You need at least version 2.2.29 or higher for the OnePlus X Boeffla Kernels.
Donation
If you like my work, feel free to donate: Donation-Link
If you donate at least 2,49 EUR (to be in line with the donation app prices on Google Play store), you will receive a personal donation code which unlocks some nice little comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Github repository: http://github.com/andip71
Credits to developers
Of course, I had never been able to create all that by my own. So I want to give credits to the really good developers around, that have given me all the inspiration and from which I cherry picked lots of the implemented functionalities:
* ZaneZam
* Grarak
* Yank555
* Hardcore
* Chainfire
* AndreiLux
* Netarchy
* Gokhanmoral
* Simone201
* Mialwe
* Entropy512
* Faux
* Harunjo
* FranciscoFranco
* Ak
... I just hope I did not forget someone. If so, please let me know and I will add you of course.
Thanks to all of you for your great work !!!
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in your custom recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi

Latest change logs:
http://kernel.boeffla.de/oneplusx/boeffla-kernel-oos/oos3xx/changelog.htm

*** You want my support? Then stick to my rules ***
Guys, I am receiving more and more completely useless support requests in different threads. Useless because people provide nothing to be able to help, not even the minimal possible information they could give.
Hence, I will now remind anyone again on the support guide lines stated here:
http://boeffla.de/index.php/support/support
Also you need to ensure you follow the installation guide lines incl. trouble-shooting stated here:
http://boeffla.de/index.php/support/installation-how-to
And to cut a long story short: If you do not at least provide what I request in the support guide lines, I will IGNORE YOUR REQUESTS IN FUTURE.
Straight and simple. I have enough of people wasting my time just because they are too lazy to write details.
Period.
Also as a reminder:
you use xposed? -> no support, everything is your own issue
you use a custom rom and not the official stock or CM one? -> good luck, you are on your own
you undervolt or overclock? -> have fun, but without my support
Sorry, this might sound harsh (and it is meant to sound harsh), but you cannot imagine about how crappy support requests can be. Stating something does not work is just not enough.
Please consider that!!!
Andi

Great to have you here

Welcome Andi !!! Gonna flash your kernel as soon as I get my OPX .... Will make profiles for it too
Welcome again !!!

Naman Bhalla said:
Welcome Andi !!! Gonna flash your kernel as soon as I get my OPX .... Will make profiles for it too
Welcome again !!!
Click to expand...
Click to collapse
Hehe, nice. I see you everywhere, isn't it?
Andi

sorry if i sound like a noob but if i have bluspark kernel already flashed, can i just flash this ontop of it? or do i have to restore a backup (of the opx before i flashed bluspark) and then flash this kernel? thanks in advance

Thanks a ton. Is CM support planned?

ihs0201 said:
sorry if i sound like a noob but if i have bluspark kernel already flashed, can i just flash this ontop of it? or do i have to restore a backup (of the opx before i flashed bluspark) and then flash this kernel? thanks in advance
Click to expand...
Click to collapse
You can flash on top of it as Boeffla kernel works on a different principle (Sorry.. I forgot what it is called... LOL... Maybe Andi can tell) .... But yeah, if issues come, flash stock and then the Boeffla (shouldn't happen though )
#HappyFlashing
Lord Boeffla said:
Hehe, nice. I see you everywhere, isn't it?
Andi
Click to expand...
Click to collapse
hehe !! I try to help the community as much as possible...
---------- Post added at 12:04 AM ---------- Previous post was at 12:01 AM ----------
RJDTWO said:
Thanks a ton. Is CM support planned?
Click to expand...
Click to collapse
I don't wanna post on behalf of Andi... But if you have been following Andi , he usually builds for CM once official builds roll out with everything working... For now, there is no official build, though almost everything is working now...
But Boeffla is in initial phase of development for OPX so I feel lord will focus more on Oos...
In short, don't expect a CM version till official nightlies start.

Naman Bhalla said:
You can flash on top of it as Boeffla kernel works on a different principle (Sorry.. I forgot what it is called... LOL... Maybe Andi can tell) .... But yeah, if issues come, flash stock and then the Boeffla (shouldn't happen though )
#HappyFlashing
Click to expand...
Click to collapse
Thanks for the quick reply

Nice to see boeffla kernel here. Was waiting for this after seeing a thread on oneplus forum. Is there a version for cm12/13 as well?
Edit: Never mind

Finally, I can't wait to flash it. You're the best, Andi, I'm proud I can say I designed your avatar, hahaha.

well i tried to install, and it gave me the error : your device is onyx. this zip is for ONE
i did install this zip: boeffla-kernel-4.0-beta1-OOS2xx-OnePlusX.recovery.zip
can anyone help/has the same problem

ihs0201 said:
well i tried to install, and it gave me the error : your device is onyx. this zip is for ONE
i did install this zip: boeffla-kernel-4.0-beta1-OOS2xx-OnePlusX.recovery.zip
can anyone help/has the same problem
Click to expand...
Click to collapse
Which recovery did you use ? As can clearly be seen, this issue is from Updater-script .... So either you can delete that line from the script or best is to use another twrp

Naman Bhalla said:
Which recovery did you use ? As can clearly be seen, this issue is from Updater-script .... So either you can delete that line from the script or best is to use another twrp
Click to expand...
Click to collapse
it is version twrp v.2.8.7.0, but i will try and update and then get back to you

ihs0201 said:
well i tried to install, and it gave me the error : your device is onyx. this zip is for ONE
i did install this zip: boeffla-kernel-4.0-beta1-OOS2xx-OnePlusX.recovery.zip
can anyone help/has the same problem
Click to expand...
Click to collapse
You downloaded the wrong kernel ( you downloaded the OnePlus one variant) so don't flash it as it might brick your device.
Scroll a bit more down in the Web page till you find OnePlus X.
P.S. The website can be a bit confusing for newer members, so here you go.
http://boeffla.df-kunde.de/oneplusx/boeffla-kernel-oos/oos2xx_download/Test/
Cheers.

dagger said:
You downloaded the wrong kernel ( you downloaded the OnePlus one variant) so don't flash it as it might brick your device.
Scroll a bit more down in the Web page till you find OnePlus X.
P.S. The website can be a bit confusing for newer members, so here you go.
http://boeffla.df-kunde.de/oneplusx/boeffla-kernel-oos/oos2xx_download/Test/
Cheers.
Click to expand...
Click to collapse
no it was the opx variant, as the filename showed opx when i flashed it. thanks anyway, and yeah the website is a bit jumbled
but the problem was an old twrp version. updated it and the kernel flashed no problem . BTW i like ur icon pack, might try it

Can someone explain the difference between this kernel and blu-spark to us common people?
What do you take into consideration when deciding which one to use?

Hi Andi,
Good to have Boeffla kernel again!

The real deal just came to opx. Thanks, bro! Hope opx gets official cm so you can provide support for cm too, as I cannot live without cm.

[KERNEL][MIUI/CM]ZD Kernel || 20160806

Code:
#include <std_disclaimer.h>
/*
* 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 ROM
* 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.*/
Features
You get the usual set of well known tweaks, mods and other improvements. Please check commits of the source repo which will be mentioned below for detailed list of changes. The key ones are -
Live Kernel flashing with backup support for previous kernel - Liverepack implementation of @psych.half is used, which also backs up your previous kernel (boot.img) and other system files which would be changed.
KCAL - A well known display parameters calibration driver for MSM devices, written by @savoca.
Dynamic Fsync 1.2 - We all know what it is about, dont we? Credits - @faux123
ThunderPlug - A hotplug driver by @varun.chitre15.
Kernel Add-on support - For CM based ROM only. More about it in later posts.
More features will be eventually added.
Kernel Adiutor will list 90% of stuff that can be tweaked by the kernel, rest will be mentioned in further posts.
What does not work?
Various display tweaks by Xiaomi like Reading mode etc in MIUI ROMs - That is because Xiaomi did not open source that aspect of the kernel. The same will probably not work on any Kernel that is compiled from source. But thanks to KCAL, this tweaks can be worked around, check further posts.
Compatibility
This kernel is only meant to be flashed on lollipop based MIUI 7/8 ROMs.
This kernel is also compatible with Official CM and other similar source based ROMs.
Version naming
I gave up on maintaining proper versions of a kernel, its lot of hard-work. Instead, naming scheme of CyanogenMod and other prominent ROMs has been used, reflected in the zip naming. LOCAL_VERSION will be same for all versions hence we will talk about versions on date of build basis.
Installation
Make sure the ROM on which you are going to flash is compatible. Once done, simply flash it through TWRP.
Reporting Bugs
In case an error has occurred during flashing, please report it with /sdcard/liverepack.log.
In case of kernel errors, please get me a dmesg.
Feature Requests
I mainly focus on quality rather than quantity. But still, you can request a feature you would like and I will see what can be done.
Download - Here
If you want to download MIUI version, please download the file with no suffix (zd-20160803-kenzo.zip). Suffix will come in the next MIUI update.
If you want to download CM version, please download the file with cm suffix (zd-20150806-kenzo-cm.zip).
Add-ons can be found in Addons folder. Only CM based kernel supports Addons.
Source/ Tools used
Source - https://github.com/TeamButter/android_kernel_xiaomi_kenzo
Toolchain used - Aarch64 4.9 by google
XDA:DevDB Information
ZD Kernel, Kernel for the Xiaomi Redmi Note 3
Contributors
corphish
Kernel Special Features:
Version Information
Status: Stable
Created 2016-08-02
Last Updated 2016-08-06

Reserved
Kernel Addons
There are certain features which some people want in the kernel, whereas others do not want that at all (they even dont want the feature to be present in the kernel ).
So to meet the needs, we would have to maintain to separate kernel builds, one with the feature, one without it.
Which is where kernel add-on comes to play,
Here the users will need to flash the main kernel. Then, if they choose to, they can flash the kernel addon (which generally contains a feature).
If users choose not to, that feature wont be present at all (just as they wanted), whereas for those who flashed the addon, the feature will be present.
It makes lives of both us and users easier, right?
Addons are low in size flashable zips, as the name suggests. You will need to flash addons if you choose to, after flashing the kernel.
Only CM based ROMs support addons, as init.d support is needed, which is not present in MIUI.
Also, by distributing addons, I guarantee that no copyright infringements are made.
Addons available
-Thunderplug
Workaround for Xiaomi's display tweaks
We will use different values for tweaking offered by KCAL. To do that, open Kernel Adiutor and go to 'Screen' page.
Reading mode
Set Blue to 196.
Colour mode: Warm
Set Green to 240, Blue to 208
Colour mode: Cool
Set Red to 208.
You can also tweak contrast values and other stuffs.
If you are not satisfied, feel free to tweak similarly.
Thunderplug
For some reason, TZ app crashes on MIUI, and kernel adiutor does not fully have support for ThunderPlug.
By default, ThunderPlug does sched based hotplugging. Hence stuffs like endurance mode wont work as it only works when hotplugging is done on per-core basis.
To enable hotplug on per-core basis, open terminal and type:
Code:
su
echo 1 > /sys/kernel/thunderplug/hotplug_style
To go back to sched based hotplug:
Code:
su
echo 2 > /sys/kernel/thunderplug/hotplug_style

Reserved
Changelog
20160803
-Fixed -2% battery bug and camera bug on devices shipped with newer hardware.
20160802
-Initial release for MIUI ROMs

Wow, zapdos was my fav kernel on condor, let's see on kenzo xD

Flashed, no problems for now great work :good:

Working great here, thank you, I have one question, Did you implement Adreno idler? Because my gpu is going to 19mhz, and also Can you please explain the sched and per core mods of thunderplug? Thax

It has the bug of the battery of -2%
dmesg: http://pastebin.com/df8fBgme

donalberto17 said:
Working great here, thank you, I have one question, Did you implement Adreno idler? Because my gpu is going to 19mhz, and also Can you please explain the sched and per core mods of thunderplug? Thax
Click to expand...
Click to collapse
No Adreno idler is not implemented yet.
In sched based hotplugging, the load is shared among cores, there are no practical differences with the stock setup.
In per core basis of hotplugging, cpu cores are only plugged in when its really required, otherwise they are off.
mega-samu said:
It has the bug of the battery of -2%
dmesg: http://pastebin.com/df8fBgme
Click to expand...
Click to collapse
Alright, could you tell me when does this happen? When the battery is very low?
And looks like its a well known bug heh?

Ok thank you for your answer, based on your experience wich one it's better? Per-core or sched?

Waiting for CM version, nice work!

corphish said:
Alright, could you tell me when does this happen? When the battery is very low?
And looks like its a well known bug heh?
Click to expand...
Click to collapse
The mistake happens after flash the kernel. I think that it is for that xiaomi the new one put in indicator of battery, in the recent xiaomi.
I leave this post you, for if it can use you as help:
http://forum.xda-developers.com/redmi-note-3/how-to/fingerprint-battery-issues-custom-roms-t3429464

Well I discovered 2 bugs, when I change the style to per-core basis it doesnt stick after a reboot, another bug is when I change to per-core basis the Fingrepint sensor stops working

mega-samu said:
The mistake happens after flash the kernel. I think that it is for that xiaomi the new one put in indicator of battery, in the recent xiaomi.
I leave this post you, for if it can use you as help:
http://forum.xda-developers.com/redmi-note-3/how-to/fingerprint-battery-issues-custom-roms-t3429464
Click to expand...
Click to collapse
Ok. Have you flashed any other ROMs or kernel in which this issue isnt there.
Looks like xiaomi has done quite some changes in kernel since release.
donalberto17 said:
Well I discovered 2 bugs, when I change the style to per-core basis it doesnt stick after a reboot, another bug is when I change to per-core basis the Fingrepint sensor stops working
Click to expand...
Click to collapse
That change wont persist through reboot, you will have to do it everytime, or perhaps write an init.d script. Not any app supports this toggle which can provide set on boot.
And all I can make from this FP sensor issue when per core basis is it requires like all 6 cores to function, because in stock, I never saw any core go offline.

corphish said:
Ok. Have you flashed any other ROMs or kernel in which this issue isnt there.
Looks like xiaomi has done quite some changes in kernel since release.
Click to expand...
Click to collapse
In cm13 santosh with the patch camera fix or in mokee official, does not happen to me.
Nowadays I have the miui 8 of xiaomi.eu, that does not happen with the kernel stock either.

corphish said:
Ok. Have you flashed any other ROMs or kernel in which this issue isnt there.
Looks like xiaomi has done quite some changes in kernel since release.
Click to expand...
Click to collapse
I havn't tried your kernel but as i'm one of people with newer devices that have this problem, i can answer the question
mokee rom doesnt have this problem and the camera fix mentioned in here fixes the problem on CM maybe you can take a look and see what is the fix in that file.

mega-samu said:
In cm13 santosh with the patch camera fix or in mokee official, does not happen to me.
Nowadays I have the miui 8 of xiaomi.eu, that does not happen with the kernel stock either.
Click to expand...
Click to collapse
Alright, I am making a new build and will upload it as soon as its done.
Unfortunately I cant verify whether the battery bug is fixed or not.
Could you flash it and see then?
Thanks both of you for bringing this to my notice.
Let me know if there are any other breakages.
Edit
Here it is - https://www.androidfilehost.com/?fid=24659325368664523
Could you flash this and see? @mega-samu

corphish said:
Alright, I am making a new build and will upload it as soon as its done.
Unfortunately I cant verify whether the battery bug is fixed or not.
Could you flash it and see then?
Thanks both of you for bringing this to my notice.
Let me know if there are any other breakages.
Edit
Here it is - https://www.androidfilehost.com/?fid=24659325368664523
Could you flash this and see? @mega-samu
Click to expand...
Click to collapse
I have just proved it and it continues the bug.
Edit: The camera does not work
Edit2: In the kernel radon they finish of fix.: http://forum.xda-developers.com/redmi-note-3/development/kernel-t3414884/post68012485#post68012485
Enviado desde mi Redmi Note 3 mediante Tapatalk

mega-samu said:
I have just proved it and it continues the bug.
Edit: The camera does not work
Edit2: In the kernel radon they finish of fix.: http://forum.xda-developers.com/redmi-note-3/development/kernel-t3414884/post68012485#post68012485
Enviado desde mi Redmi Note 3 mediante Tapatalk
Click to expand...
Click to collapse
Alright, could you test yet another build soon?
Edit:
Here you go, this build has same name as previous one but they are different build, separately made and uploaded - https://www.androidfilehost.com/?fid=24591000424951734
Also check whether camera works fine or not @mega-samu

corphish said:
Workaround for Xiaomi's display tweaks
We will use different values for tweaking offered by KCAL. To do that, open Kernel Adiutor and go to 'Screen' page.
Reading mode
Set Blue to 196.
Colour mode: Warm
Set Green to 240, Blue to 208
Colour mode: Cool
Set Red to 208.
You can also tweak contrast values and other stuffs.
If you are not satisfied, feel free to tweak similarly.
Thunderplug
For some reason, TZ app crashes on MIUI, and kernel adiutor does not fully have support for ThunderPlug.
By default, ThunderPlug does sched based hotplugging. Hence stuffs like endurance mode wont work as it only works when hotplugging is done on per-core basis.
To enable hotplug on per-core basis, open terminal and type:
Code:
su
echo 1 > /sys/kernel/thunderplug/hotplug_style
To go back to sched based hotplug:
Code:
su
echo 2 > /sys/kernel/thunderplug/hotplug_style
Click to expand...
Click to collapse
if i change to echo1 fingerprint sensor is misbhaving ... one finger works other doenst and also a little bit of irresponsiveness

sasaboor64 said:
if i change to echo1 fingerprint sensor is misbhaving ... one finger works other doenst and also a little bit of irresponsiveness
Click to expand...
Click to collapse
Yeah I realized that.
Looks like all CPU cores are needed for it properly function.
As in stock all cpu cores are always on, I never saw anyone go off.
I might remove hotplug in next build.

[ALL][Kernel][8.1][AOSP] LightningZap! Kernel

Greetings all!
Introducing LightningZap! kernel for the Moto Z2 Force. It is based off Pantheon kernel with some of my own little tweaks and enhancements to improve performance and battery life.
Pantheon features:
Upstream kernel from source
Edits to avoid Safetynet/CTS (If you have root, it will fail signature check inherently without SUhide or Magisk hide)
Disabled CRC check
Disabled dm-verity
Over Clock / Under Clock on CPU Frequencies added:
Little CPU: 175 MHz, 230 MHz, 2035 MHz
Big CPU: 175 MHz, 230 MHz, 2476 MHz; 2592 MHz
Slight undervolt (our device is overvolted compared to other msm8998 devices)
UC GPU (added 180 Mhz step for battery savings when web browsing, low GPU usage)
OC GPU (changed 710 MHz to 750 MHz)
Same Adrenoboost tweaks as the Pixel 2 ElementalX kernel.
Wakelock fixes by Boeffla
Added Zen, FIOPS, BFQ, and SIO IO schedulers
LigthningZap! Features:
Insane readahead tweak: No need to raise readahead cache with a kernel tweaker. With this tweak all partitions are set to their maximum readahead possible and is handle by the io-scheduler. This tweak is best used with FIOPS (set by default), BFQ and SIO schedulers. I haven't ran many tests on other schedulers.
LightningZap! sysctl tweaks: Adjust values for kernel system controls for better performance and battery life.
Lionheart governor added: This is the recommended governor for LightningZap! kernels. I have set the dbs_tuners_ins.sampling_rate and min_sampling_rate to 100 (lowest value)so the end user can adjust the values in their favourite kernel tweaker add to suit their needs. It's very simple, when setting the sampling rates, a high number will improve battery life but performance will take a slight hit, and a lower number will increase performance but battery life will take a small hit. Values for these range between 100-1000. This governor is not set by default, but can be set with you favourite kernel tweaking app
Aroma Installer: Same options as in Pantheon kernel for now. More to come as I work them in.
Compiled with Linaro 4.9 only (no clang here)
See second post for fixes, improvements, changelogs, and downloads
Source code: LightningZap! kernel for nash
Flashing Instrcutions:
Device must be rooted with custom recovery (TWRP)
Place LightningZap! kernel for nash on sdcard
Reboot to recovery and flash .zip
Follow on screen prompts
Re-flash root (Magisk)
Reboot, wait 15 minutes, and enjoy
For further adjustments, I recommend Kernel Toolkit
I wasn't going to post this kernel, but since there is very little other support and options going on with this phone, I changed my mind. I ask everyone to keep things civil, do your best to stay on topic, be patient when asking/answering questions, try to search for an answer before you post a question, and PLEASE make a backup.
Special thanks to Uzephi for the base source code (Pantheon Kernel)

Fixes, Improvements, Changelogs, and Downloads
LightningZap! kernel for nash v1.0 (Download link)
Insane readahead tweak (v2)
LightningZap! sysctl tweaks
Lionheart governor
Aroma Installer
Compiled with Linaro 4.9 only (no clang here)
USB Tethering fixed

Working on LineageOS?

matheusgcdj said:
Working on LineageOS?
Click to expand...
Click to collapse
He used my LOS base. Will work on LOS, but not other AOSP ROMs. @thomas.raines, you might want to start merging from o8x-caf. Your kernel is at 4.4.132 latest stable is 4.4.138. (Just going off your git). It might make WiFi break with LOS, but @npjohnson stated they will be merging those caf commits in the very near future where you don't need two forks anymore.
Thanks for the USB tethering fix as well. Merged into mine today and sending a release shortly.
Edit: oh, yeah, verity bypass isn't in my kernel anymore, so if you want to add it, you might want to pick it from EX, Franco, or Kirisakura kernels. Didn't see the point, so when I rebased, I didn't pick it in.

matheusgcdj said:
Working on LineageOS?
Click to expand...
Click to collapse
Haven't tested. Would be nice if you tested for me...
Uzephi said:
He used my LOS base. Will work on LOS, but not other AOSP ROMs. @thomas.raines, you might want to start merging from o8x-caf. Your kernel is at 4.4.132 latest stable is 4.4.138. (Just going off your git). It might make WiFi break with LOS, but @npjohnson stated they will be merging those caf commits in the very near future where you don't need two forks anymore.
Thanks for the USB tethering fix as well. Merged into mine today and sending a release shortly.
Edit: oh, yeah, verity bypass isn't in my kernel anymore, so if you want to add it, you might want to pick it from EX, Franco, or Kirisakura kernels. Didn't see the point, so when I rebased, I didn't pick it in.
Click to expand...
Click to collapse
I'm using your AOSP branch (I thought)... It's working on AOSiP flawlessly. Thanks for the heads up on the verity bypass. I'm actually working on that now, but not sure if I'm going to or not... Glad I could help with the USB thethering...

thomas.raines said:
Haven't tested. Would be nice if you tested for me...
I'm using your AOSP branch (I thought)... It's working on AOSiP flawlessly. Thanks for the heads up on the verity bypass. I'm actually working on that now... Glad I could help with the USB thethering...
Click to expand...
Click to collapse
Pantheon branch is stale, o8x-caf is current.

Motomods?
Sent from my Moto G4 Plus using XDA Labs

KelleyCook said:
Motomods?
Click to expand...
Click to collapse
If it comes off my source, Motomods should work.

thomas.raines said:
Haven't tested. Would be nice if you tested for me...
I'm using your AOSP branch (I thought)... It's working on AOSiP flawlessly. Thanks for the heads up on the verity bypass. I'm actually working on that now, but not sure if I'm going to or not... Glad I could help with the USB thethering...
Click to expand...
Click to collapse
Removed the stale branch. My source just got 4.4.139 merged into it. I use Nathan Chancellor's msm-4.4 tree if you ever don't want to wait for jbats or I to push the Linux-stable commits.

Uzephi said:
Removed the stale branch. My source just got 4.4.139 merged into it. I use Nathan Chancellor's msm-4.4 tree if you ever don't want to wait for jbats or I to push the Linux-stable commits.
Click to expand...
Click to collapse
Just merged the 08x-caf branch... Thanks

So if flashed on stock and it broke my Wifi how do I go about fixing it? This Moto Z2 force is like starting all over. I thaught i was good at this once? Other than no WiFi the kernel works great. Thanks for the development this phone needs all it can get.

I got a bootloop. Any advice?
I'm on Lineage OS 15.1-20181106.

zZLord said:
I got a bootloop. Any advice?
I'm on Lineage OS 15.1-20181106.
Click to expand...
Click to collapse
Unless OP updated for Treble (mounting /vendor instead of /oem) this won't work on Treble. Any LOS built after August is Treble enabled. Try with DU official.