The makers of one of the most popular custom ROMs for Android phones and tablets are doing away “stable” releases, instead promising to offer new builds every 2-4 weeks as CyanogenMod “M” releases.

cyanogenmod logo

What does this mean for users? Not much really. It’s really more of a name change than anything: but names can be important. In this case, the word “stable” might have led people to assume that they could download a build of CyanogenMod and expect few-to-no bugs and a complete, unchanging set of features.

That was never really true for a community-built operating system designed to run across a wide range of hardware that the developers had no control over.

Instead, the CyanogenMod team explains stable releases were used as a marker during the development process that helped keep track of bugs, among other things.

Now the team is offering CyanogenMod M releases every 4 weeks, which means that folks who don’t want to download “nightly” builds which have a habit of introducing bugs from time to time as well as patching them, you can wait for a monthly build that will have a batch of updates including bug fixes and new features.

Eventually the CyanogenMod team plans to move to a 2-week release for its “M” builds, which means that every 2 weeks you’ll be able to install a new version of the software that’s about as “stable” as any earlier version that wore that label would have been.

The latest version of CyanogenMod is CM 11 M6, and it includes an updated Theme Engine, support for hidden apps and labels in the app launcher, options for smaller tiles in the Quick Settings panel, and a number of other updates and bug fixes.

But a new version will be along in about a month… and much like the rapid release schedules for the Firefox and Chrome web browsers, that means not every new version of CyanogenMod will be particularly notable to folks who aren’t die-hard followers of the team’s every move.

But it also means that folks looking for relatively stable releases won’t have to wait long for new builds… and shouldn’t ever expect the software to be absolutely stable.

It’s not clear that any of this holds true for CyanogenMod 11S builds which are commercial software developed for CyanogenMod, Inc for phones like the upcoming OnePlus One.

Support Liliputing

Liliputing's primary sources of revenue are advertising and affiliate links (if you click the "Shop" button at the top of the page and buy something on Amazon, for example, we'll get a small commission).

But there are several ways you can support the site directly even if you're using an ad blocker* and hate online shopping.

Contribute to our Patreon campaign


Contribute via PayPal

* If you are using an ad blocker like uBlock Origin and seeing a pop-up message at the bottom of the screen, we have a guide that may help you disable it.

Subscribe to Liliputing via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 9,547 other subscribers

2 replies on “CyanogenMod waves goodbye to “stable” releases”

  1. Makes sense. CM releases has always been buggy. There never really was a stable release. At least I wouldn’t consider them stable. They’re usually in a worse state than the stock OEM image. At least you get extra features but they’re mostly useful for only the modding crowd.

    I wonder how the commercial versions will fare. With the support of OEMs, I assume they’d have a better chance of making the hardware and software work. Many “modders” tend to overlook flakiness and issues. Sometimes even act like the problems don’t exist. However, many non-tinkering consumers won’t tolerate the usual CM issues on an out of the box device.

  2. Though I sincerely appreciate the Cyanogen Mod team’s efforts (because it prolonged the life and usefulness of my otherwise defunct HP TouchPad), the perpetual beta-esque nature of the OS versions is the reason I only stay on CM9 and do not upgrade to something more recent. It’s almost like the devs get bored and move on, leaving an always unfinished and buggy product. Android fragmentation in itself is bad enough. But add a double layer of CM fragmentation on top of that and you’ll most likely find frustration. CM is not for the faint of heart, it’s for geeks with a lot of time on their hands…

Comments are closed.