Links on Android Authority may earn us a commission. Learn more.
OS family reunion: Android part of Linux kernel again
One danger for open source software is the dreaded project fork. What happens is that someone writes lots of nice code and releases it as open source. Later, someone else starts to use the code but finds that the goals and aims of the original project don’t match theirs, and so, they decide to split away (fork) and start a new project based on a snapshot of the existing code. This never actually happened with Android (unless you count Amazon’s Android version a fork) but it came very close.
However, now it seems that the differences have been resolved, and, as the Android code makes its way back into the main kernel, there will be benefits for Android and Linux developers alike. First, developers will be able to use the latest released version of the Linux kernel to run an Android system, without having to apply any Android specific patches. Second, the burden (and cost) of maintaining independent patches from release to release for Android kernel developers will be reduced and, eventually, eliminated. The unification is also good news for driver writers and component manufacturers, as it will now be possible to develop drivers and board support features against either an Android kernel release or a mainstream kernel release.
One big winner will be the CyanogenMod custom firmware project (and similar projects), as the developers will be able to pick which kernel they want to use from the main stream Linux kernel, without having to wait for an equivalent Android kernel to appear. This could give rise to projects which take the latest Android code and couple it with the latest Linux mainstream kernel, to produce new firmware for those who like to live on the bleeding edge.