Stable Builds Of CyanogenMod 10 Emerge For Various Devices

[UPDATE] The CyanogenMod team has finally released an official statement regarding these stable builds. The entire statement (found on Google+) has been posted below.

While the CyanogenMod team has yet to issue an official statement it appears that stable builds are coming out of their popular CyanogenMod 10 ROM. According to the CyanogenMod download site these stable builds are available for various devices. As of now the stable ROMs of CM10 are available for the Sprint and Verizon Samsung Galaxy SIII, the Samsung Galaxy SII Skyrocket, and LG’s Optimus Black. It is expected that more are likely to follow in the coming hours and days so this is certainly exciting news.

The Jelly Bean-based custom ROM reaches its milestone as the Nexus 4 and Nexus 10 go up for sale around the world as well as the Galaxy Nexus and Nexus 7 receive their Android 4.2 updates.

DroidDog will keep an eye for any official confirmation or statement by the CyanogenMod team as to these stable builds.


Just in time for something new

As most of the community frantically press the F5 key’s on their machines, waiting (impatiently) to throw their money at +LG Mobile and +Google, we thought we’d join in the fun.

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).

So, with those semantics and topics discussed, the CM 10.0 releases are already hitting and more are queued on our Jenkins build manager.

What’s next?

Android 4.2 is getting the OTA treatment from the powers that be. We eagerly await the source to hit the AOSP repos. When it does, we will begin 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). However, these assessments are preliminary, and won’t be finalized until MR1, or whatever tag is used, gets has the source to go with it.

Edit: Oh and yes, before its asked, 4.2 will be CM 10.1 (not CM11). via Android Central

Tags: , , , , , ,