With stable builds of CyanogenMod 10 being released yesterday to a select devices, more devices should start seeing support as the days go on. Today the U.S. Samsung Galaxy S3, Galaxy Note (1 and 2), HTC One X and S, and Sony Xperia T are now supported, among many others. If you’re curious about your device and if the CM team supports it, you can check out their website for further details.
In other news, with Android 4.2′s source code dropping yesterday, you can expect developers like CyanogenMod to quickly get their hands on that code and start working on their custom version of it. The CM team has revealed that it will be dubbed as CM10.1, rather than a whole new number such as CM11. Since Android 4.2 is still technically Jelly Bean, the team didn’t feel the need to bump the number up to 11. That will probably be saved for the next iteration of Android (Key Lime Pie perhaps?).
Check out CM’s official statement on the matter after the break!
Last night we initiated the process of tagging and branching our source code for the CM 10 “stable” release.
Why is stable in quotes? Because that word does a disservice to the M-series and is misleading at worst. The word stable works great when discussing kernels, but calling this release ‘stable’ implies that the M-series builds were not ‘stable’, which is far from the truth. So think of this as stable, release, LTS, or M3; you pick. Regardless, we want your bug reports; we can’t fix what we don’t know is broken. (And yes, you do have to follow the template, or your issue will be ignored).
Builds have hit our download portal, with more queued on our Jenkins build manager, and we will be adding to their numbers as additional devices reach release quality. On deck for the near future are releases for the Nexus S, Sony Xperia devices and the Nook Color.
Android 4.2 received the OTA treatment yesterday from the powers that be and today JBQ pushed the buttons for the source to hit the AOSP repos. We have begun the task of defining what is new, what has changed, and what CM features should stay (or go). We already anticipate removing the CM enhancements to the Clock app (Google made their own), and enhancing the Quick Settings (most likely not porting over the Notification Power Widgets). Other areas include our Profiles code, lockscreen weather and calendar events and the larger effects of the multi-user support. However, these assessments are preliminary, and we’ll learn more as the merge process continues.
Android 4.2 will become CyanogenMod 10.1 and we will provide an update on our Google+ when nightlies with the 4.2 code begin.