Branches - GalaticStryder/android_kernel_leeco_msm8996 GitHub Wiki
There are three currently maintained branches that match our compilation script: lambda-reborn, nougat-mr2 and lineage-15.1. All others are peripherical branches with a mix of fixes, features, and obsession.
lambda-reborn
This branch is specially designed as an OEM Kernel replacement – you read it correctly – we're replacing the OEM role here and pushing the moribund OEM Kernel to its funeral since they don't push updates of any nature anymore.
Compilation on this branch is only available out-of-the-tree – obviously, since it's an OEM Android version – which demands a cross-compiler and the AnyKernel2 utility to avoid dealing with ramdisk manually, this method is the default one.
nougat-mr2
This branch was officially used on AOSPA (Paranoid Android) 7.x for the Le Pro3 and only supports that device, it has reached end-of-life as of now and shall not receive any updates whatsoever. Most of the current development is still intimately linked to this branch, it serves now as a good reference for changes at least.
Compilation on this branch can be either inline with AOSPA via lunch and make bootimage commands which will create a boot.img as the result to be written to device's boot partition or out-of-the-tree which demands a cross-compiler and the AnyKernel2 utility to avoid dealing with ramdisk manually, this last method is the default one for recovery based installation as it preserves ramdisk modifications.
lineage-15.1
This branch is now the current mainline branch of all Lambda Kernel development, it's still in early stage but should fill the hiatus from absent OEM releases just fine.
In theory, it should work on LineageOS 14.1 and even AOSPA 7.x due to the LA.UM Kernel base but we are not going to allow that kind of "upgrade" due to the potential incompatibility with userspace in those mentioned versions.
Compilation on this branch can be either inline with LineageOS 15.1 via lunch and make bootimage commands which will create a boot.img as the result to be written to device's boot partition or out-of-the-tree which demands a cross-compiler and the AnyKernel2 utility to avoid dealing with ramdisk manually, this last method is the default one for recovery based installation as it preserves ramdisk modifications.
Read more about compilation on the specific page.