Android Basics 101: Recognizing Kernels
Par for the course in XDA is to personalize our apparatus.
This includes a customized theme or a customized ROM with different launchers, designs, and color schemes.
However, a valuable portion of a device's firmware and applications bundle is that the kernel.
You do not notice when it is working fine.
Nevertheless, when it isn't, you detect.
He gives a simple summary of what a kernel does.
Afterward, Kevin talks about a couple of customized kernels on XDA and also what they can supply for you.
Therefore, in case you wish to find out more about this kernel, check out this video.
That isn't universally true, whatsoever, and defies the very definition of a secure kernel.
Each Android apparatus runs a variant of the Linux kernel.
But, that version might not be the most recent.
By way of instance, my primary device at the time of composing this, the Nexus 6P, is operating a 3.10.73 on inventory whereas the hottest upstream provides is 3.10.107.
Other mobiles are on something as ancient as 3.10.40 or even 3.10.49.
Largely, the main reason behind this can be CAF (Code Aurora Forum, an open source collaborative endeavor mostly sponsors by Qualcomm) doesn't merge upstream updates in their kernels.
Hence OEMs don't do it either.
It is important to stay current with the most recent from kernel.org since there are lots of bug and security fixes coming down from the mainline Kernel Adiutor which fixes bugs which were present because 2007 in particular scenarios.
According to Greg Kroah-Hartman, the 2nd most influential kernel programmer, "If you're not using an[n up-to-date] stable/longterm kernel, your device is insecure" (origin, at 17:10 but I suggest watching the entire thing).
A good deal of naysayers will say plenty of the patches from upstream are immaterial to the structure of the majority of mobiles (arm/arm64) or are accountable for motorists we do not have; while that could be accurate.
Numerous patches are pertinent and since Greg stated in the video as mentioned above if you believe that you can sort through what's relevant great luck.
Personally, I do not think I'm far better than the professionals who push this stuff at no cost, so I add all of it.
If this were a controversial procedure, why would Google even be spending time in doing this, particularly since 3.18 was ending of life before this?
Others will state that upstream can lead to instability.
I will assert that when something breaks while incorporating upstream, you probably did it wrong (did not listen to conflicts, browse the circumstance of each patch, etc.) and it is SUPER easy to return out of (see the section below about bisecting).
Additional browse the secure kernel documentation, they're little fixes to real-world issues.
Follow the below procedure while paying attention and GUARANTEE you'll not have any difficulties.
As yet another example/point, consolidating upstream permits you to get before Google's security upstream.
Sure, you may only add that one spot, but you still must be paying attention to upstream and filtering. It requires less effort to combine it all than it will pick and choose.
Even taking a look at the December bulletin, there's another critical security bug that they state affects the Pixel apparatus.
It had been repaired in 3.18.37, nearly six months until it was inserted by Google.
The stable kernels have been used by several OEMs in crucial real-world scenarios and don't have any difficulties.
These patches can also be paid for by plenty of OEMs (assess the signoffs because 2015) pushed into the public at no cost; I think it's very dumb to pass up on those fixes.