CyanogenMod has released the last Android 4.3 based ROM, CM 10.2.0, signalling the end of an era. With the recent release of Android 4.4 KitKat, it only makes sense that the team at CyanogenMod Inc. would set their sights on bigger and better things. The company announced the news in a blog post yesterday.
Although CyanogenMod will be putting all of their effort into their Android 4.4 based build CM 11, they will not be abandoning CM 10.2.0 by continuing to add hotfixes and security patches. CM 10.2.0 nightlies will continue to flow, allowing users with supported devices to update their ROM with new features and bugfixes as they become available. As CyanogenMod continues their work on CM 11 code, more and more devices will become available for installation, so don’t fret if you’re running CM 10.2.0. Your device may just be supported soon.
With the recent release of the first smartphone with CyanogenMod bundled, the Oppo N1 and the company hinting at a new hardware partner, things are really heating up for CyanogenMod.
For more info on the death of Android 4.3 based CyanogenMod builds, check out CyanogenMod’s blog post below.
December 2nd, 2013 • Written by ciwrl
CyanogenMod 10.2.0 Release
With the release of CM 10.2.0 we end our foray into Android 4.3-land and planned releases based on that code. We will of course continue to provide hot-fixes, security patches and similar as needed. The device roster for this initial run includes all devices that received an RC1.
Echoing the RC1 post, make sure you update your third party addon zips. As a cursory note, for those of you coming from 10.1 or earlier, if you notice your Phone app reports as ‘not installed’: simply remove the shortcut and re-add it from your application drawer.
As we’ve done with similar ‘end of branch’ releases, this marks the point where the team will shift focus solely to CM 11 and Android 4.4 (KitKat) code. CM 10.2 nightlies will continue and as we ramp up CM 11 nightlies, device maintainers will signal which devices are ready to make that jump as well. Whether you prefer stable, almost stable or bleeding edge, all of you will have something to flash very soon!
Some additional administrative items. We’ll soon be retiring the ICS branches from the nightly rotation. There are less and fewer changes going into that branch, and with CM 11 nightlies on the horizon, it makes more sense to task the buildbots to actively changing branches instead (ie 10.0 and above).
We’ve also made a change to the release tagging process. For those of you who like to build for releases for yourself, note that all but the device repositories themselves are being built off of a new ‘stable/cm-10.2? branch in our source. Think of ‘cm-10.2? as the development branch and ‘stable/cm-10.2? as the release branch. Just pass the relevant arguments on sync to decide which you prefer. This change has no impact to gerrit or any code contributions.