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

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

The existing Google Code tracker was started when we only supported 2 devices and Cyanogen was the only developer. Now we have about 150 devices and almost as many developers/maintainers, across 3 major versions of Android. There are almost 500 open issues on the tracker and nearing 7000 submitted in the last 3 years. The logcats and screenshots (and the occasional mp3 or video) attached to all the issues take over a gigabyte of space, and each increase in that quota has to be asked for manually. Google recently silently removed the RSS feed for all project updates, making issue tracking a bit harder for me.

The last two points there indicate the need for our own hosted solution. As several project members have worked with it before, JIRA was chosen. They provide a free licence for open-source projects (just like Google Code) and provide for a much better bug submission form and overall workflow.

If you have ever submitted a bug to a bugzilla or trac issue tracker, JIRA should be easily useable. Instead of the Google Code single-textarea form that is easily blanked, there are text boxes for each piece of required data with descriptions below. The bug searching should be better than Google Code’s, and the need for me to hand-tag every issue will be reduced (if not largely eliminated). In addition, we have loaded a plugin that ties our issue tracker to gerrit, better tracking when bugs are solved.

Utkanos, our wonderful new Wiki overlord, has rewritten my (admittedly bad) “How to use the issue tracker” page both for clarity and to correspond to JIRA.

But, and this is a big ‘but’, there are no pre-existing ways to transfer Google Code issues en-masse to JIRA. JIRA supports importing from several other trackers, as well as CSV files, but not Google Code. Meanwhile, Google Code doesn’t have any easy export options (the CSV download offered on the main issue list is only the summary/tags, not the complete text and comments) and the Google Data (gdata) XML interface can pull either the initial submitted report for all issues or comments for one. I haven’t found any good xml-to-csv converters that can handle the data, and writing one by hand has proved problematic at best.

So we will need you, the community, to re-submit your bugs to JIRA. For me to manually copy/paste everything by hand would be hours, if not days, of work. For each one of you that has submitted a bug or enhancement request to move your report to JIRA should only take a few moments.

This blog post will coincide with a bulk update of all open issues (except ‘shouldbefixed’ ones already handled). I would request that only the original submitter copy their issue into the new tracker. When doing so, they should include a link back to the original googlecode submission so I can close it. Alternatively, a link on googlecode to the new JIRA bug will suffice.

As of right now, new issues will NOT be accepted on the Google Code tracker, users should begin submitting bug reports to the JIRA instance at jira.cyanogenmod.org. Existing issues will be closed as they are moved to JIRA. In a couple weeks, I will close any remaining issues on the Google Code tracker. After that point, anything reported on JIRA will be treated as a new issue, and the google code tracker will be closed and shut down.

[An added bonus to the move to Jira is the ability for you as end users to better communicate what you’d like to see included in CyanogenMod. A new form and tag for ‘feature request’ has been added. As with bug submissions, you should search to see if your request or one similar to it has already been submitted. Duplicates, or perceived duplicates, will be merged. Please understand, unlike bugs (where we shipped something in a broken state) we are under no such obligation to fulfill requests. The sheer number of you out there compared to those available to code instantly eliminates our ability to fulfill every request. That said, if we spot a good idea that also interests us (and that’s the key stipulation here), we will work towards it.]

This has and will be a lot of work for everyone, but ultimately we will have complete control of our bug tracker and hopefully a better experience for users and developers going forward.

-PsychoI3oy, your CyanogenMod BugMonkey

We’re building M for these devices:
* Samsung Captivate
* Samsung Nexus S (+4G)
* Samsung Galaxy S3 USA models (D2*)
* Samsung Galaxy S (galaxysmtd/galaxysbmtd)
* Google Nexus 7
* Google Galaxy Nexus (all variants)
* Google Nexus 4
* Google Nexus 10
* ODroid U2
* Samsung P3100, P3110
* Samsung P5100, P5110

Head over to Get.CM to find a build for your device.

Enjoy our first release of CM-10.1 and please report any and all bugs you find to our bug tracker.

So earlier today we put up a post on what prompted us to transition to our new CyanogenMod.org domain. We refrained from identifying the ex-member out of respect for his privacy and career outside of CM. Suffice it to say you guys aren’t slouches, and figured it out on your own.

With that said, the ex-member in question contacted us and has agreed to hand over control of the CyanogenMod.com domain. This was done as amicably as these things can be, and CM did not pay the fee he requested.

We will still be using CyanogenMod.org as our primary domain, and the .com address will simply redirect to this new domain. Ironically enough, ‘.org’ is better than ‘.com’ as we are not a commercial entity, and is far more in line with how CyanogenMod is structured.

We received a common question, that we’d like to take a moment to answer. Some of you contacted us mentioning that you had previously donated to a different address. When the forum began, up until about 3 months ago, the forum utilized this other address as the mechanism for forum donations and establishment of the ‘Donator’ badge. Donations made to this address prior to three months ago were used for the CyanogenMod forum IPB licence and forum related costs and were not misappropriated.

On a side note, we have also gone through internal restructuring to make sure that this sort of thing doesn’t happen again. Nobody has control over everything, and there is no longer such a large single-point of failure. Our lessons have been learned.

We ask that you please not perform any vigilante actions, we do not condone any such thing; just let this fade.

We want to move on, get you the builds you expect from us, and not mess around with distractions.

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 Shade@chemlab.org) 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 Shade@chemlab.org. We’d like to get a handle on how widespread this was before we file charges.

-The CyanogenMod Team

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.

The M-Series is our monthly release series. The devices we build M for are essentially stable, and ready to be your daily driver.

We are building M2 for these devices:

• Galaxy Nexus GSM (maguro)
• Galaxy Nexus VZW (toro)
• Galaxy Nexus Sprint (toroplus)
• Galaxy S2 GT-I9100G (i9100g)
• Galaxy S2 AT&T LTE (skyrocket)
• Galaxy S2 T-Mobile (hercules)
• Galaxy S (galaxysmtd)
• Galaxy S B (galaxysbmtd)
• Captivate (captivatemtd)
• Galaxy S3 Sprint (d2spr)
• Galaxy S3 VZW (d2vzw)
• Galaxy S3 AT&T (d2att)
• Galaxy S3 TMO (d2tmo)
• Galaxy S3 US Cellular (d2usc)
• Motorola Xoom (wingray/stingray)
• Nexus S (crespo)
• Nexus S 4G (crespo4g)
• Galaxy Note AT&T (quincyatt)
• Galaxy Note T-Mobile (quincytmo)
• Google Nexus 7 (grouper)
• LG Nitro HD (p930)
• LG Optimus Black (p970)
• LG Optimus LTE SKT (su640)
• Sony Xperia Acro S (hikari)
• Sony Xperia S (nozomi)

More devices are on the way! Many other supported devices are available as nightly builds, but may have a glitch or two that we are still working out.

The latest builds are available via the new CM Updater, as well as ROM Manager. Or, you can download manually from Get.CM. With any M release, we are zooming in on a stable version so we need your feedback and bug reports to make it as good as it can be!

If you like what we’re doing, please consider dropping a couple of bucks at our donation link below. It helps us outfit the teams with new devices as well as keep our infrastructure running.

Enjoy M2!

We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.

M-Series builds will be available under the EXPERIMENTAL tag. The filename will include the date stamp as well as the M version. These builds should be stable enough for daily use, and we encourage feedback and bug reports.

Tonight’s M1 build is available for these devices:

• Galaxy Nexus GSM (maguro)
• Galaxy Nexus VZW (toro)
• Galaxy Nexus Sprint (toroplus)
• Galaxy S2 GT-I9100G (i9100g)
• Galaxy S (galaxysmtd)
• Galaxy S B (galaxysbmtd)
• Captivate (captivatemtd)
• Galaxy S3 Sprint (d2spr)
• Galaxy S3 VZW (d2vzw)
• Galaxy S3 AT&T (d2att)
• Galaxy S3 TMO (d2tmo)
• Galaxy S3 US Cellular (d2usc)
• Nexus S (crespo)
• Nexus S 4G (crespo4g)
• Galaxy Note AT&T (quincyatt)
• Google Nexus 7 (grouper)
• Sony Xperia Acro S (hikari)
• Sony Xperia S (nozomi)

In standard CM style, we will continue to add devices as time goes on up until our stable release.

Head over to Get.CM to grab the latest build for your device. Installation instructions and other documentation can always be found at the CM Wiki and help is always close at hand over on our official forums.

Happy flashing!

How do you enter? It’s simple, all you have to do is this:

• Like Amzer on Facebook and leave a wall post saying why you want to win.
• Follow @AmzerInc and @CyanogenMod and retweet the competition entry tweet (click here to retweet)

Doing both will earn you two entries into the drawing and doing so multiple times will increase your chances of winning. This contest is available globally, and there is no limit on the number of times you can enter.

The competition is open Today through September 17th 2012. Cutoff for entries are at 12-midnight PST on the 17th (8am BST).

We will randomly select 14 winners to receive a case and 2 winners to receive a Nexus 7, for a total of 16 winners. Winners will be announced via a followup to this blog post and contacted on Twitter or Facebook.

Learn more about Amzer and check out their range of cases at: About Amzer

Good Luck!

Terms & Conditions

• The competition is open to ANYONE worldwide. Please note that Amzer will cover shipping costs, however the winner will be responsible for any taxes, customs fees or import duty upon receipt of the prize.
• To enter this competition you must be 13 years old or over at the time of entry.
• The competition is not open to employees (or members of their immediate families) of Amzer, CyanogenMod or any associates.
• No purchase necessary.
• There is no limit on number of entries by a person.
• If you want to enter the contest – you must Like Amzer on Facebook (fb.me/Amzer) and leave a wall post saying why you want to win, or Follow Amzer on Twitter (@Amzerinc) and re-tweet the entry tweet. Doing both doubles your chances and doing it multiple number of times increases your chances.
• Winners will be picked in the end by Amzer, and they will be notified via Social Media and Blog posts at the time of decision. All winners must contact Amzer via Facebook or Twitter to claim their prize, within 7 days.
• The closing date is 17th September 2012. Cutoff for entries are at 12-midnight PST on the 17th (8am BST).
• If you win a competition, we will notify you by Facebook / Twitter post. The judges’ decision will be final, and no correspondence will be entered into.
• By entering the competition the winner agrees to participate in such promotional activity and material as Amzer may require.
• The prize will not be transferable to another person.
• No part of a prize is exchangeable for cash or any other prize.
• If an advertised prize is not available, Amzer reserve the right to offer an alternative prize of equal or greater value.
• Incorrectly completed entries will be disqualified.
• This competition is being run by Amzer and is hosted by CyanogenMod
• Amzer reserves the right to use the contest material at any time in the future, without any prior permissions.
• Amzer reserves the right to amend these rules at any time. Amzer may also create rules which will apply to a specific contest only. If we do this we will publish the amended competition rules and/or specific competition rules on the relevant contest page.
• Amzer will endeavour to send prizes within a month of the competition end date but cannot guarantee this delivery time. Products cannot be sent to P.O. Boxes