After numerous nightly and monthly builds, CyanogenMod 10 is finally ready for its stable release. The custom ROM is already available to download for the Samsung Galaxy S II LTE, LG Optimus Black, and the Samsung Galaxy S III (both Verizon and Sprint models).

The latest version of CyanogenMod includes a number of new features, such as an 'expandable desktop' mode, and a built-in, root-enabled file manager, as well as support for new devices.

Screen Shot 2012-11-13 at 11.20.24

If you can't see a stable build of CyanogenMod 10 for your device just yet, hang tight, as some builds have been failing. Hopefully, the issue will be addressed soon, but we aren't sure how long this might take. If you can't wait to get your hands on the final version, keep checking the stable downloads page for new builds.

Update #1: Many more builds have gone live this morning.


Update #2: Here are the release notes. The most exciting part - Android 4.2 will map to CM version 10.1 and will be on its way to the nightlies soon:

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.

What’s Next?

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.

Source: CyanogenMod Downloads

John Thompson
John's been addicted to technology ever since he tinkered with his first custom built PC when he was 10 years old. He's also the proud owner of seven Amazon Kindles, but only because he destroyed the first six.

  • Astrofrigo

    Don't expect stable builds for GT-I9100 and GT-I9300 until Samsung releases source code (if they even do it), guise.

    • NicholasMicallef

      I don't expect RC versions before that... :(. I still use it on my daily driver (i9100) and it has a few problems I can deal with. Haven't they fixed the i9300 problems when they got the leaks?

      • Astrofrigo

        I'm currently using CM10 on my GT-9300 and it has some issues, not too serious, but it does have them. I think I need to make a fresh install soon, it's getting slow and I'm getting some FCs every now and then. Might be Siyah kernel though.

  • Jeremy Gomez

    This gives me even more of a reason to upgrade to the Galaxy SIII next month. The Optimus G looks great too, but I always love seeing CyanogenMod support.

  • Jeremy Gomez

    This gives me even more of a reason to upgrade to the Galaxy SIII next month. The Optimus G looks great too, but I love having CyanogenMod on devices I own.

    • Andrew Dodd

      I9300 or one of the Qualcomm-based d2 variants. DO NOT buy an Exynos4-based device if you're looking for a good Cyanogenmod experience.

      • Ivailo Stoyanov

        Couldn't agree more. If I'd known the issues around Exynos devices, I wouldn't have bought an I9100 a year ago. I was an Android noob back then.

  • jordanjay29

    Wow, there are no Nexus devices in that initial batch. I'm stunned.

    • http://twitter.com/rsaka10 Fugmedia

      Yes it is search in the download page of cyanogenmod I'm using right now in my gnex

    • NicholasMicallef

      It's definitely out for the Nexus 7 (grouper) xD... The funny part is I just flashed it but I'm actually waiting for Android 4.2 (Isuppose that will still be CM10), so it won't be for long before it's replaced by another nightly xD

    • http://www.androidpolice.com/ Artem Russakovskii

      Some are there now. Grouper, maguro just hit too.

  • Andrew Townsend

    Very surprised maguro isn't one of the "launch" devices

    • Andrew Dodd

      What part of "and counting" didn't you understand? Buildserver has typically been running for over 12 hours each day to get all builds done.

      • Unni

        Andrews, stahp fighting....

      • Andrew Townsend


  • fsrdh

    my GF has an LG black running a nightly build from yesterday and it still has some quirks with the proximity sensor switching the display off whenever there is a call, the GPS failing to lock onto any satelites, missing flashlight option from the powermenu, issues with running costum ringtones/notifications in MP3 format and funniest of all the lack of an option to download dictionaries from the Google 4.2 swipe keyboard - courtesy of AP :-D I'll give it a go and see if they got it together, she would be so happy to Foursquare again heh.

    • Sorian

      Nightly builds are very experimental, so bugs, quirks, missing features are normal. These are stable builds should not have any problems

  • libbrichus

    Any clue as to when or if they will ever support a Droid RAZR. I bought it on a Verizon contract without checking custom support. Serves me right for getting a Verizon Droid device although I love the battery on my Max.

    • Andrew Dodd

      Device support always depends on the availability of a maintainer. It's a volunteer organization.

      Devices with locked bootloaders are unattractive to developers, and hence are almost always poorly supported.

      I would recommend leaving Verizon, their bootloader locking policies are atrocious.

  • http://twitter.com/misterE33 Mr E

    it still warms my heart to see official cm10 releases for the verizon galaxy siii after the launch fiasco with the locked bootloader

  • nexusSjelly

    i don't hope they rushed this due to 4.2 release ASOP coming soon.. Last nightlies for my nexus s were a bit buggy from time to time.

    • Scott

      I've been running many of the latest nightlies from CM10 and they're all very stable. No worries from me!

  • http://www.facebook.com/profile.php?id=1312291338 Tim Miller

    Am I the only one who isn't impressed by Cyanogen anymore?...

    They're always one stable branch behind AOSP. In my opinion their work isn't worth being behind the AOSP curve. Their ROMs are also far less impressive then they used to be.

    • libbrichus

      They already have a stable version out for 4.1.2 which is the latest and have had them almost since day 1 of AOSP in their nightlies. I would guess 4.2 nightlies to be out very soon. How are they behind?

      • http://www.facebook.com/profile.php?id=1312291338 Tim Miller

        Nightlies come with a giant disclaimer that they are not finished, stable builds. I realize they probably are actually stable 99% of the time, but being part of that 1% is not worth the risk to me - I'm not signing up for a beta test. I rely on my phone heavily for work - the last thing I need is some bug causing it to reboot when I am on a conference call with my boss.

        • burntcookie90

          Then you shouldn't be ROMming.

          • http://www.facebook.com/profile.php?id=1312291338 Tim Miller

            That's my point - I'm not. Stock rooted AOSP with a few select root apps is far more stable and reliable than most random ROMs with a bunch of useless buggy features sloppily coded in by a random 15 year old "programmer".

            Cyanogen used to be the exception to the rule back in 2.X days as they make damn solid ROMs, but they no longer seem capable of having an official stable release until AOSP has already moved up a branch.

          • burntcookie90

            That's not their fault, AOSP is moving very quickly. They also have so many devices to support now.

          • http://www.facebook.com/profile.php?id=1312291338 Tim Miller

            I'll never pretend it's their fault, managing a project that large is a pain in the ass. I have nothing but respect for what they are trying to accomplish, and I loved their work on the Nexus One and original Droid.

            My entire point from the beginning is that I'm simply no longer impressed because they can't keep up.

            I see it constantly: users that don't need to rely on their phone TOO heavily install the nightlies, love it, get used to the extra features, and then BAM, a new AOSP branch comes out. Suddenly, most of them move up to a stock ROM to be able to have the newest version, and lose those features they had gotten used to. It's an annoying and pointless cycle.

          • squiddy20

            I'll never understand why people go to the stock ROM after running a custom one, simply because stock is slightly newer. I've had CM (mostly M releases and stable mixed with the occasional nightly) installed on my Sprint Galaxy Nexus since I purchased the thing. Never once put it back to stock, even when the Jelly Bean update rolled out.

          • Freak4Dell

            If people are installing nightlies and loving, they know what they'll lose by moving too a stock ROM, and they're usually just doing it to check out the new features of the stock ROM. A week to a month later, they'll be back on the nightly with the newest version.

            Your argument as a whole makes absolutely no sense. CM is not Google, so they have no choice but to be behind the release schedule. They have nowhere the amount of resources and manpower that Google and all these other manufacturers have, yet they manage to provide a ROM for a ton of devices. They are slightly slower than Google, and a lot faster than the manufacturers. They care about the quality of their product, so they won't release a build they officially label as stable until they are absolutely sure. If you're not interested in running beta software, then custom ROMs are not for you. You are better off with the stock ROMs. There's no reason to insult a brilliant team of developers just because you have this irrational idea that they should be as fast as Google.

        • Scott

          I've been running CM10 nightlies for a few months now and I've had nothing but success. I had to move away from AOKP when I started seeing some issues, and CM10 has been rock solid. You don't have too much to worry about.

    • http://www.facebook.com/pobegam Michael Pobega

      AOSP targets just a handful of devices; Nexus S, Galaxy Nexus, Nexus 4/7/10, Wifi Xoom and that Sony Xperia device that was just added recently. CM10 supports tons of different devices, as well as aiming to have a stable release out just one version behind AOSP.

      And CM10 also has features that really need to be integrated into AOSP, such as quick reply in the default text messaging app and notification LED control. I'll happily lag just a little bit behind for the features, stability and improved battery life a stable Cyanogenmod build gives me.

    • Davy Jones

      Are you a Nexus owner? Because if not, believe me, even being one stable version behind on AOSP is a hell of a lot more than you can say for most of the devices it is available for. Cyanogenmod is in some ways one of the best thing Android has going for it. Without it, who knows how many devices would be stuck with semi-abandoned versions of Touchwiz or Sense.

    • http://brgulker.wordpress.com/ brgulker

      To a point, I agree with part of this.

      What I don't agree with is not being impressed by the CM team. I am impressed by them and what they do.

      What I do agree with is that they don't seem to offer a whole lot beyond stock, rooted AOSP, and I generally prefer other AOSP ROMs to theirs.

      The big 'however', however, is that I own two Nexus devices, and so it's very easy to find a variety of AOSP-based ROMs to suit my fancy. For those who don't own Nexus devices, CM is an absolute God send if you want to run AOSP.

      The reason I don't use CM myself is that I prefer ROMs like AOKP that offer a variety of custom features on top of AOSP that I really like using. If I were using a non-Nexus device, though, I'm sure I'd love CM to death.

  • Gah!

    Fucking Samsung, i want a stable version for my galaxy s3 international aodåjgfipsgbdz

  • Ashish Raj

    Can anyone point me towards a site or link containing all the features of CM10 in layman terms?? I do found the changelog but it's too technical for a noob like me... I'm sure this doesn't matter but I'm looking specifically for the Jewel (Evo 4G LTE) model.

  • http://www.twitter.com/RaptorHawk Hawk

    It is available for Yakju Galaxy Nexus as well?

    • Cherokee4Life

      you could follow the link and check for you self..

      its available for the EVO LTE and thats all that matters!!!!!!!!!!!!!!!!!!!

      • http://www.twitter.com/RaptorHawk Hawk

        hahahahaha congrats!

  • http://www.stevenmattera.com Steven Mattera

    Can quincyatt (Galaxy Note [i717]) have some love. Still using CM9 Stable. =D

  • http://twitter.com/psych2L Joseph Lee

    Just in time for Android 4.2 lol

  • Ghuru

    Any Updates as to when will a stable version of cm10 be available for se xperia ray?

  • raytheI.Tguy

    find source codes here http://opensource.samsung.com/

  • satchy1986

    hello.. my cm10 on my galaxy s2 t989. slow internet.always overheating. and sometimes its not charging... pls help..