Share this Story

CM 10.1 Reaches Release Candidate Status, Builds Starting to Hit Servers Already


Since Android 4.1 Jelly Bean hit almost a year ago, we haven’t heard the words “Release Candidate” used in terms of a CyanogenMod ROM. That doesn’t mean they aren’t polished and well developed, but the team hasn’t gone so far to make any builds a Release Candidate, until today. 

In their blog post, the CM team says that this is “one of (if not the last) milestone releases” before a final build of CM 10.1 is finished. Release Candidate builds are not Final ones, but you can generally expect most bugs to be squashed and to have a polished ROM that can easily serve as your daily driver. The list of devices to receive this build is long, so to check if your phone is on it hit the link below.

Via: CyanogenMod

Cheers Albert!

  • Zach Tanksley

    droid dna has a port coming along too on xda! http://forum.xda-developers.com/showthread.php?t=2219979

  • Ray

    I’ve ran the M builds as well. But my only gripes with it was that bluetooth would not work at ALL!! I couldn’t pair it to my LG tone and was wondering if anyone who’s tried the RC can verify if the bluetooth issues are resolved?

  • chd87

    Will the gapps I have for the m3 build work with this?

  • Confused

    Anyone having trouble with d2vzw only having sound in the right channel?

  • peezwizz

    trying it out with toro gnex… only issue I had with one of the nightly builds was random shut downs

  • Guest

    trying it out on toro gnex… the only issue I had with the nightly builds was random shut downs

  • I’m running CM9 on my TouchPad, is this update compatible? Thanks.

  • 🙁

    I was hoping the bugs would get fixed before it became an official release

    • jpfrasier

      They eventually will but that does not include release candidates

  • MrToTo83

    Love the CM builds just wish that the home key would work again on my Xoom.

    • xXAaronSXx

      It’s not the rom. Something errored when you flashed it. This has happened to me. I just flash a different ROM (I usually flash Team EOS) and the flash CM10.1 and wipe. Usually only takes once. Now I just flash the Nightlies dirty and never run into the problem. Like I said, it only happened to me once and it happened when I put CM on my friends. This fixed it both times. The nightly CM10.1 roms run flawlessly on my Wingray.

  • Brandon Golway

    It took a long time but it’s finally here!

  • Sweeet! I went back to CM & have been rocking the nightlies since M2 when they switched over to 4.2.2

  • Same for the Droid Razr Maxx HD. Low signal/drops on any AOSP rom.

  • Clint O

    No note2 love

  • enigmaco

    Col can’t wait to try it on my nexus 4, want something solid

  • Mike

    Sweet, now if only S3s could get decent signal on AOSP.

    • PhoenixPath

      …or if WiFi worked respectably on the Nexus 10.

      Stock: it works great.

      Any AOSP: low, low signal, crap.

      One of these days…

  • edoggy

    The three 10.1 M-snapshots (monthly builds) for the Galaxy Nexus (toro/Verizon) have been very stable. No complaints!

  • brkshr

    That’s great to hear! I know their 10.1 Nightlies have been rock solid since December (edit: at least for the N4… any other phone… YMMV), but it’s still nice for newcomers to see the ‘RC’ & eventually the ‘Stable’ status, for peace of mind.

    • sc4fpse

      Don’t forget, there have been a few scattered M builds along the way. In my current living/working situation overseas I wasn’t exactly comfortable running nightlies like I did back in the U.S., but the M builds have always been sturdy enough for me. Nonetheless, I’m excited to finally see another RC.

      • brkshr

        Yep. I keep my Galaxy Nexus (now used by my GF) on Milestone builds. No problems whatsoever with them.