It was towards the end of last year that news broke of Cyanogen Inc's plans to shut down. This was a huge blow to the community that had watched it grow from an ambitious pet project into a full-fledged company providing an OS for the likes of OnePlus and others. Luckily, not long after, LineageOS was launched to continue as a spiritual successor to Cyanogen. This week the company has announced new devices that will be supported, along with some modifications to the OS.
The folks at Lineage have been fairly busy, adding improvements to its OS. They have included some changes like the addition of AptX and AptXHD on supported devices, along with a modification in the way the torch function can be activated.
The Lineage team also made some revisions, which can be read in detail down below.
CAF Rebase and February Security Patches
When we started developing for Android 7.0 (not 7.1), we based our source code on CAF 7.0 (CAF we depend upon for almost all our Qualcomm based devices). When Android 7.1 was released to AOSP, we merged this on top, but kept CAF 7.0 for HALs. Now CAF have updated their repositories to Android 7.1, we have rewritten history and rebased all merged commits on top of the CAF 7.1 base. This means:
- much less time spent resolving merge conflicts
- AOSP’s February security patches (AKA r21) can be merged much more easily into LineageOS 14.1 (which is why we’re later than usual for this month’s security patches). Before we did the huge rebase (happening over the past week), we created branches called cm-14.1_prerebase to make sure we had a known good copy to go back to, just in case the rebase did not go successfully. We’ll be working on incorporating the Feb security release into 13.0 builds in the near future.
As for new additions, LineageOS has expanded to four new devices this week for 14.1, including: the Wileyfox Storm, Galaxy Tab S 8.4, Galaxy Tab S 10.5, and the 2014 Samsung Galaxy Note 10.1. For 13.0 devices there is the lone entry of the LeEco Le Pro3.