Cyanogenmod 10.1 release candidate 1 builds go live on 45 handsets

May 9, 2013

    Cyanogenmod

    Builds have been continually rolling out for CyanogenMod 10.1, in the form of nightly and M-releases, for quite a while, and after much hard work the custom ROM is finally considered stable on enough devices to move on up to the release candidate stage. RC is a term reserved for only the most stable of builds, marking it as suitable daily use without glitches and crashes.

    Reaching the RC1 stage also means that these are some of the last updates that these devices are likely to see for Android 4.2.2. As a quote from the CyanogenMod blog puts it:

    This will be one of (if not the last) milestone releases before a 10.1.0 is pushed out.

    So the team is probably quite close to pushing out a final release, which makes quite a bit of sense considering that a new Android version is rumoured to be appearing at Google I/O. The CyanogenMod team is known for pushing out stable, or finalised builds of their ROMs just before a new Android version shows up, in preparation for moving CyanogenMod onto the latest version of Android.

    Anyway, the new RC1 builds have rolled out on 45 handset variants so far, so here’s the full list:

    • Acer Iconia Tab A700 (a700)
    • Amazon Kindle Fire (1st gen) (otter)
    • Amazon Kindle Fire (2nd gen) (otter2)
    • Asus Transformer Pad Infinity (tf700t)
    • Barnes & Noble Nook Color (encore)
    • Google Galaxy Nexus (GSM) (maguro)
    • Google Nexus 10 (manta)
    • Google Nexus 4 (mako)
    • Google Nexus 7 (GSM) (tilapia)
    • Google Nexus 7 (Wi-Fi) (grouper)
    • Google Nexus Q (steelhead)
    • Google Nexus S (crespo)
    • Google Nexus S 4G (crespo4g)
    • Hardkernel ODROID-U2 (odroidu2)
    • HTC One X (endeavoru)
    • LG Nitro HD / Optimus LTE (p930)
    • LG Optimus 4X HD (p880)
    • LG Optimus G (Intl) (e975)
    • LG Optimus L9 (p760)
    • LG Optimus LTE (SK Telecom) (su640)
    • LG Spectrum (vs920)
    • Motorola Droid 4 (maserati)
    • Motorola Droid Bionic (targa)
    • Motorola Droid Razr (spyder)
    • Motorola Razr (umts_spyder)
    • Samsung Captivate (captivatemtd)
    • Samsung Epic 4G (epicmtd)
    • Samsung Galaxy Nexus (Sprint) (toroplus)
    • Samsung Galaxy Nexus (Verizon) (toro)
    • Samsung Galaxy Note (AT&T) (quincyatt)
    • Samsung Galaxy Note (T-Mobile) (quincytmo)
    • Samsung Galaxy S (galaxysmtd)
    • Samsung Galaxy S II (G) (i9100g)
    • Samsung Galaxy S II (T-Mobile) (hercules)
    • Samsung Galaxy S II Skyrocket (skyrocket)
    • Samsung Galaxy S III (AT&T) (d2att)
    • Samsung Galaxy S III (Cricket) (d2cri)
    • Samsung Galaxy S III (MetroPCS) (d2mtr)
    • Samsung Galaxy S III (Sprint) (d2spr)
    • Samsung Galaxy S III (T-Mobile) (d2tmo)
    • Samsung Galaxy S III (Verizon) (d2vzw)
    • Samsung Galaxy Tab 2 7.0 (GSM) (p3100)
    • Samsung Galaxy Tab 2 7.0 (Wi-Fi) (p3110)
    • Samsung Galaxy Tab2 10.1 (GSM) (p5100)
    • Samsung Galaxy Tab2 10.1 (Wi-Fi) (p5110)

    As always, if you haven’t already been prompted to install the CyanogenMod 10.1 update, then you can go to settings>about phone>cyanogenmod updates to manually check, or you can download your required zip file from the CyanogenMod download list to flash through recovery.

    Comments

    • MasterMuffin

      Gt-I9300, where are you?? Damn you Exynos >:(

    • Brociu

      Tab 2 7.0 has official CM support? O.o Great, maybe I flash it on my tab :P

    • harjifangki

      So this version is more stable than the M-Build?

      • Tits

        Yes

        • dogulas

          Not for me. Verizon GS3 here. I was using M3 and updated in the CM updater to RC1. Man, this build feels like a nightly compared to M3. Would a clean install change that, or are the Verizon GS3 CM devs just a little behind in stability this time? I was under the impression that a clean install was completely unnecessary. Right?

          • Dart

            Try a clean install. General rule is to do clean installs with changes of build types, especially if you encounter issues.

            For example, nightly to RC1 = clean install. But if it works fine the first go around, just stick with it.

            • dogulas

              yeah I didn’t think I had to, coming from a monthly. I guess I will give it a try. supposedly it is totally unnecessary in my case but I will see if it makes a difference.

            • Dart

              Haha. I like your avatar.

              It’s from that old Windows skiing game. That abominable snowman jumped over and over after eating your player.

    • http://www.facebook.com/sheheryar.rocks Sheheryar Khan

      Where is Anzu?? SE Xperia Arc

    • Will Coral

      Why not GT-I9100 !??! :(

      • mihaits

        because exynos

    • http://www.facebook.com/profile.php?id=100004201535721 Mark King

      I hope the one x+ comes soon

    • Mr. Rogers

      I’ll be happy once I can run stock Android on my HTC One..

    • Arsenal™

      no exynos support>? :S

    • dogulas

      Verizon GS3 here. I was using M3 and updated in the CM updater to RC1. Man, this build feels like a nightly compared to M3. Would a clean install change that, or are the Verizon GS3 CM devs just a little behind in stability this time? I was under the impression that a clean install was completely unnecessary. Right?

    • Rumit dhamecha

      no s2 i9100 International model? :(

    • Dart

      Yay, Nook Color. Gonna flash that this weekend.

      I feel bad for all the Exynos folks. Darn you, Samsung.

    Popular

    Latest