We haven’t used the ‘Release Candidate’ nomenclature since the ICS days, but we feel the 10.1 branch is quickly approaching the point where a ‘final’ build is due. To prepare for that eventuality, RC1 builds for CyanogenMod 10.1.0 are now landing on our servers! This will be one of (if not the last) milestone releases before a 10.1.0 is pushed out. These builds will appear as they complete the build process and, as always, you can download the builds via get.cm!

The RC1 release list is as follows (codenames):

• a700
• captivatemtd
• crespo
• crespo4g
• d2att
• d2cri
• d2mtr
• d2spr
• d2tmo
• d2vzw
• e975
• endeavoru
• epicmtd
• galaxysmtd
• grouper
• hercules
• i9100g
• maguro
• mako
• manta
• odroidu2
• otter
• otter2
• p3100
• p3110
• p5100
• p5110
• p760
• p880
• p930
• quincyatt
• quincytmo
• skyrocket
• steelhead
• su640
• tf700t
• tilapia
• toro
• toroplus
• vs920

A little more than a month removed from our last M-release, the 10.1-M2 releases are now landing on our servers. These builds are based on Android 4.2.2.

We’ve expanded the release list to include quite a few new devices since the M1; the full list is further below.

With this release, we’d like to remind you all that while bug reports on nightlies will get summarily dismissed, we accept and encourage reports to be submitted against the M2 release. By identifying issues in the M-release, you can help to make the eventual ‘stable’ release that much better. Note that our bug tracker has relocated to jira.cyanogenmod.org. Additionally, if you report a bug but fail to attach a log (logcat or adb bugreport), your report will be considered invalid, and closed. Even if your device bursts into flames: no attached log means it didn’t happen.

Devices receiving an M release today are as follows:
Acer Iconia a700
Google Nexus S (crespo, crespo4g)
Google Nexus 7 (grouper, tilapia)
Google Galaxy Nexus (toro, toroplus, maguro)
Google Nexus 4 (mako)
Google Nexus 10 (manta)
Google Nexus Q (steelhead)
Hardkernel Odroid-U2
HTC One X (evita)
HTC Incredible 4G LTE (fireball)
HTC Evo 4G LTE (jewel)
HTC One S (ville)
LG Nitro HD (p930)
LG Optimus LTE (su640)
LG Spectrum (vs920)
Samsung Galaxy S (captivatemtd, galaxysbmtd, galaxysmtd, epicmtd)
Samsung Galaxy SII (i9100g, hercules, skyrocket)
Samsung Galaxy SIII (US variants d2att, d2cri, d2mtr, d2spr, d2tmo, d2vzw)
Samsung Note (quincytmo, quincyatt)
Samsung Galaxy Tab 2 7.0 (p3100, p3110)
Samsung Galaxy Tab 2 10.1 (p5100, p5110)

As per usual, the code has been tagged in our Github as ‘cm-10.1-M2’. Any device currently receiving 10.1 nightlies, but not listed above, will continue to get worked on until they are ready. This includes the Kindle Fire, Galaxy R and Motorola Devices added yesterday.

Happy Flashing,
The CyanogenMod Team

We at CM are very trusting of our members, showed by both respect and permissions granted to those people we consider part of the team. Last month, this trust was violated in a substantial way. In the spirit of openness, here is what happened.

CM’s history is well established, with Cyanogen releasing his original ROM for the G1 on XDA forums. Back then, there was no “CyanogenMod” in terms of the organization and structure that we have today. The builds were hosted on Steve’s personal machine, the original server was a donation of spare kit from Phaseburn. And due to the small size (and lack of funds), the CyanogenMod.com domain was bought by a third-party back in 2009 and donated to CM, when CM was a much smaller project and had no online presence besides XDA.

Fast-forward 3 years, we have 3 extremely powerful build boxes donated by the community and an army of developers, contributors, and supported devices. But, a little over a week ago, things took a bad turn. The person owning the CyanogenMod.com domain was caught impersonating Steve to make referral deals with community sites. When confronted and asked to hand over control of the domain amicably, he decided he wanted 10K USD for it, which we won’t (and can’t) pay.

We contacted those he had established deals with, only to discover that the person tasked with maintaining our web presence was setting up deals under the CM name, and impersonating Cyanogen himself. Plenty of satisfying evidence was provided by those sites / entities to make us certain that this wasn’t a misunderstanding or one-time thing.

This leaves us at a critical impasse. Being trusted with CM’s web presence means this member had control over the CM social network accounts (Twitter/FB) as well as domains (cyanogenmod.com). We have changed ownership of the social media accounts. When asked again to make the transition nicely, he responded with the following

“Hi, so you think by removing all my access across the infrastructure was going to be a great idea? We had a chat yesterday, you’ve decided to end this bitter. How about I just change the DNS entries right now. CM will practically go down.”

Refusing to be extorted for funds, and then being threatened is “ending it bitter”? Today, it happened: all of our records were deleted, and cyanogenmod.com is slowly expiring out of the Internet and being replaced by blank pages and non-existing sites. @cyanogenmod.com e-mail is now being directed to a mailserver completely out of our control, too.

We have begun the dispute process with ICANN to reclaim our domain. In the meantime, please utilize CyanogenMod.org and all applicable subdomains.

As mentioned, this member also managed our Google Apps for Business account, and therefore our @cyanogenmod.com email addresses. These addresses should be considered discontinued until further notice. We will be contacting the Google team to reclaim rights to the apps account. In the meantime, please contact devrel (at) cyanogenmod.org for any devrel questions or other issues. A mailserver is being established to transition other support email addresses. We will provide those when they are finalized, and they will utilize the .org domain.

We don’t like how this played out, and we are deeply hurt. Likewise, we are deeply saddened at the confusion this may have caused the community. We will continue to be open about the what, when, how, but unfortunately, we may never know the ‘why’ – though greed comes to mind. The team itself has not made a profit off of CM and that is not our goal. But to have one of our own betray the community like this is beyond our comprehension. We will update you all as things progress.

Know that we are pursuing every available legal means to regain control over our domain.

Please note, all donations that were given directly to Cyanogen (aka [email protected]) did indeed reach their destination and are not affected.

If you are a company out there that believes they have also entered into agreements with “CM”  by this person impersonating Steve, please contact [email protected]. We’d like to get a handle on how widespread this was before we file charges.

-The CyanogenMod Team

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.

As we continue working on CyanogenMod 10, we are taking an opportunity to revisit CM 9 for one more hurrah!  The introduction of something unique.

Welcome to Tapp!  A near field communication (NFC) payment platform for the CyanogenMod community and powered by SimplyTapp. Founded by two CM enthusiasts, Doug and Ted, Simplytapp provides a method for evolving, securing and expanding  NFC payments.

ICS, we hardly knew ye.

Builds for CyanogenMod 9 stable will be rolling out to our servers tonight. As noted before, this will be the end of the line for the ICS branch of our code; only critical bug fixes will be merged moving forward.

As a note, the maguro build from this morning was not meant to be linked publicly. Maguro’s build this evening will be marked 9.0.0.1 to be on par with the other 9.0.0 releases.

Tonight’s release is for the majority of our ICS supported devices, the stragglers will catch up, and  we will leave the door open for merging in additional devices from maintainers, external and internal. The team itself, will focus solely on Jelly Bean and maintenance of the CM 7 codebase.

Many have wondered why we bothered to finish CM 9 when we are already active in CM 10 development. To that, our answer is: we don’t like to leave things incomplete. There is no profit gained from what we do, so the satisfaction of completing a goal is our only reward. This release also serves as a release suitable for the masses, especially those who won’t have 100% functioning releases of CM 10 immediately or are averse to anything branded as ‘preview’, ‘alpha’, ‘beta’ or ‘nightly’.

On the topic of nightlies, this release also serves as an end to our CM 9 nightlies, to make way for nightlies chock full of Jelly Bean goodness. A follow-up post will be made when we enable those builds.