Every single operating system developed by Google to date has one thing in common: they're based on the Linux kernel. Chrome OS, Android, Chromecasts, you name it. Linux has powered Google hardware for years.
However, the Linux kernel is not ideal for every situation. Especially in the case of embedded devices like car dashboards or GPS units, full-blown desktop kernels like Linux impact performance and cause other issues. There’s a massive ecosystem of operating systems designed for embedded hardware, and Google may be working on their own.
Enter “Fuchsia.” Google’s own description for it on the project’s GitHub page is simply, “Pink + Purple == Fuchsia (a new Operating System)”. Read More
Just a couple weeks ago, HTC sent the Sense 6 Lollipop update to owners of the unlocked and developer editions of the One M8. Now, the kernel source for those devices has been posted to the HTCDev website. Remember, this is not the same as the Lollipop kernel source published well over a month ago for Google Play Edition devices; this is for phones running Sense.
For most users, there's nothing to see here. Don't rush off to download because there's nothing of direct use to you. However, custom ROM development relies on resources like this so you may benefit indirectly if you like to flash third-party software on your M8. Read More
On the heels of their release of the Android 5.0.1 Lollipop OTA update to the HTC One M7 and M8 Google Play Editions, HTC has quickly made the kernel source for both devices available at the HTCdev website. Most users don't need to worry about this either way, but developers and fans of custom ROMs should be happy to see these available so soon.
While HTC is required to release the kernel source since it has adapted from the open source Android code, this is kind of like returning a library book a few days early; it's just nicer to do it sooner rather than later. Read More
The final round of Developer Preview images released on Friday left a number of users without root access on their devices, but a lightning fast quick-fix by Chainfire had them back in business the following day. Yesterday, he took to Google+ with a follow-up of how it works and the issues that are making it more difficult to acquire root on the latest version of Android.
Due to increasingly effective security measures and stricter enforcement of SELinux, it seems that many, or possibly all of the available methods for initializing the SuperSU daemon at startup have been rendered ineffective. As part of Chainfire's updated root, custom kernels were posted for the Nexus 5, Nexus 7, and ADT-1 that switch a few SELinux policies to permissive mode so that SuperSU can be run in the correct context after a device boots up. Read More