[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] mosimchah:
################################################################

BlackScreen 3.1 upstream all teh kernels​

################################################################

Changes:

1. Swtiched to autosmp hotplug for all builds and optimized it a bit

2. tons of f2fs updates

3. some improvements from the le max2 BlackScreen maintainer [MENTION=1187148]infrag[/MENTION]

4. fully upstreamed the kernel from 3.18.31 to 3.18.63 (more info later in the post)

5. Improved lazyplug a bit

6. up to date with omni (latest caf tag, improved audio)

Info on upstream:

first off, huge thanks to [MENTION=6842057]The Flash[/MENTION] for all of his help

here's the explanation from his thread:

"

The case for upstreaming

This section is necessary as many kernel developers have built up this false narrative that upstream breaks drivers and OEM code. That's not universally true, at all, and defies the very definition of a stable kernel. Please read this section if nothing else, it is the most important!

Every Android device runs a version of the Linux kernel. However, that version may not be the latest. For example, my primary device at the time of writing this, the Nexus 6P, is running a 3.10.73 on stock whereas the latest upstream offers is 3.10.107. Other phones are on something as early as 3.10.40 or 3.10.49. Largely, the reason for this is CAF (Code Aurora Forum, an open source collaborative project largely sponsors by Qualcomm) does not merge upstream updates into their kernels, thus OEMs do not do it either.

It's important to stay up to date with the latest from kernel.org as there are many security and bug fixes coming down from the mainline kernel that fix bugs that have been present since 2007 in some cases. As stated by Greg Kroah-Hartman, the second most influential kernel developer, "If you are not using a[n up to date] stable/longterm kernel, your machine is insecure" (source, at 17:10 but I recommend watching the whole thing).

A lot of naysayers will say a lot of the patches from upstream are irrelevant to the architecture of most phones (arm/arm64) or are for drivers we don't have; while that may be true, there are several patches that are relevant and as Greg said in the above video, if you think you can sort through what is relevant, good luck. I personally don't think I am better than the professionals that push this stuff for free, thus I add it all. Greg's even getting sponsored by Google to do this for Google's kernel/common (3.18, 4.4, and 4.9). He's even helping the Google Pixel kernel team upstream the kernel for Android O, as evident by the android-msm-marlin-3.18-o-preview-3 branch. If this were a pointless process, why would Google even be investing time in doing it, especially since 3.18 was end of life before this?

Others will say that upstream can cause instability. While I will concede there may be a few problem patches here and there (listed below), these are NOT the norm, at all. I will argue that if something breaks while adding upstream, you most likely did it wrong (didn't pay attention to conflicts, read the context of every patch, etc) and it's SUPER easy to come back from (see the section below regarding bisecting). Furthermore, read the stable kernel documentation, they are small fixes to real world problems. Follow the below process while paying attention and GUARANTEE you will have no issues.

As another example/point, merging upstream allows you to get ahead of Google's security upstream. The infamous Dirty COW vulnerability, the fix for which released in 3.10.104 (committed on October 20th), was added by Google in the December security update. Sure, you could just add that one patch but you still have to be paying attention to upstream and filtering. It takes less effort to merge it all than it does to pick and choose. Even looking at the December bulletin, there is another critical security bug that they say affects the Pixel devices. It was fixed in 3.18.37, almost six months before it was added by Google. The stable kernels are used by MANY OEMs in real world critical situations and have no issues. These patches are also paid for by a lot of OEMs (check the signoffs since 2015) pushed to the public for free; I personally think it is extremely stupid to pass up on these fixes. "

https://xdaforums.com/android/software-hacking/reference-how-to-upstream-android-kernel-t3626913

As always there's more info on the kernel features (cpu, and gpu governors, hotplug driver, IO schedulers, tcp algorithms, and way more) in the third post, and fourth post

Regular build: https://www.androidfilehost.com/?fid=961840155545586639

Omni build: https://www.androidfilehost.com/?fid=745425885120753357

eas build: https://www.androidfilehost.com/?fid=961840155545586640

don't forget to flash supersu or magisk afterwords if you don't want to lose root ;)