After nearly five months of nightlys, Cyanogen has finally released its first stable version of CyangoenMod 10 based on Android 4.1 Jelly Bean. It is no coincidence that this happens on the day of the release of the source code of Android 4.2, since surely Cyanogen developers are working on what according to them will be CyanogenMod 10.1, the updated version to the new OS from Google.
The list of devices that already have CyanogenMod 10 stable below, more devices will be added over time ..
- Samsung Galaxy S III (Sprint)
- Samsung Galaxy S III (vzw)
- Samsung Galaxy S2 ATT LTE
- Samsung Captivate
- Samsung Galaxy S III (US Cell)
- Samsung Galaxy S III (TMUS)
- Samsung Galaxy S Blaze 4G
- Samsung Galaxy Nexus (vzw)
- Samsung Epic 4G
- Samsung Galaxy S III (AT&T)
- Samsung Galaxy S III (M. PCS)
- Samsung Galaxy S (B)
- Samsung Galaxy S
- Samsung Galaxy S2 T-Mobile
- Samsung Galaxy S II (G)
- HTC Evo 4G LTE
- HTC One XL
- HTC One S
- Google Galaxy Nexus (GSM)
- Google Nexus 7
- Sony Xperia T
- LG Nitro HD / Optimus LTE
- LG Optimus Black
- LG Optimus LTE (SKT)
- Motorola Xoom (vzw)
- Motorola Xoom (3G)
- Motorola Xoom (Wifi)
- ASUS Transformer Pad
- ASUS Transformer Pad Infinity
To download Cyanogen should go to their download site and look for your device, you may find it by model although some are a little confusing to find.
Early CyanogenMod nightlys 10.1 will be released in their Google Plus Account.
The official statement below:
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.
In short we will upload tutorials on how to update your device to the latest stable version of CyanogenMod to enjoy Jelly Bean.