CyanogenMod-7.0.1 Update Release

It’s been about two weeks since we rolled out the first stable version of CyanogenMod-7, and it unfortunately came with a few bugs. 7.0.1 brings many bugfixes, including GPS fixes for many devices, a handful a new features, and support for a few devices that weren’t quite ready in time for 7.0 (original Droid).

As always, the best way to install CM is to use ROM Manager. If you are running the current stable release, you should get a notification when a build is ready for your device. You can also manually download from our mirror network (powered by TD Revolution”), or head over to our forums.

Check out the latest CHANGELOG for a quick summary of everything included in this release.

Thanks to everyone for their continued support and contributions!

EDIT: Sorry guys, we made a mistake and there are issues with 7.0.1. 7.0.2 will be up shortly.

CyanogenMod 7.0 Released!

After over 4 months of work, many sleepless nights, and contributions from people all around the world, I am proud to release CyanogenMod 7.0 into the wild!

CM7 is based on the 2.3.3 (Gingerbread) release of Android from Google. We’ve added most of the great features from CM6 you know and love, and many new ones including support for several tablets. We are currently providing support for 30 devices! I continue to be amazed with this community and the dedication of everyone involved. It’s a neverending work-in-progress so if you find a problem, please let us know on our issue tracker. There are a few CM6 features that aren’t part of CM7 yet, but they are in the queue for 7.1 already.

The best way to install CM7 is to use ROM Manager. Detailed instructions for rooting your device can be found at our wiki. Manual downloads can be obtained from our Read the Rest…

CyanogenMod-7.0.0-RC2 is here!

Another round of release candidates for CM7 are on their way out.. This version is an update to Android 2.3.3, and also brings a few new features like WiMAX on the EVO (from #TEAMWIN), Notification Profiles, and many bugfixes. We are feature-frozen and in bugfix mode at this point, so please let us know about any issues on our bug tracker.

Get the latest from ROM Manager, or head over to our forums or our mirror network for manual downloads.


We could never have imagined such a turnout on RC2.  In less than 24 hours since the release, we have accumulated over 150,000 downloads between the RCs of the officially supported devices.  This blows our mind and makes doing this all the more rewarding.

CyanogenMod-7 Release Candidates!

The first CM7 release candidates are starting to roll out for our supported devices! These are builds that are feature-complete and fairly well tested, but still have some minor tweaking that needs done. You should find them stable for everyday use though!

A lot of work has gone into CM7, particularly in the device compatibility area. CodeAurora Forum and have been a huge help, and all the sneaky coders on the CM team who have figured out the remaining issues. And hats off to T-Mobile for open-sourcing their theme engine! Better documentation on creating themes is forthcoming. You’ll also find some very cool new features like a revamped and customizable lockscreen, a restyled music app, “phone goggles”, gesture support everywhere, etc, etc :)

CM7 is still a work in progress. Some of your favorite features from CM6 might not be there yet, but this is our …

Read the Rest…

A Note On Unofficial Ports, and How To Get It Right

There’s been some recent talk about unofficial versions of CyanogenMod being created and released on sites like XDA, with large amounts of missing features and broken functionality, and I just wanted to talk about our position on this.

An “official” CyanogenMod version is one that uses our code review system, our source repository, and our mirror network. It should look, act, and feel like CM on any other device, and more importantly, it should follow our release schedules (which is a “when it’s ready” kind of thing, but we do plan our final/RC releases when we feel it’s ready). Most importantly, no major hardware functionality should be broken.

We want to see CM available for every device out there, and our infrastructure (and our developer community) is there for anyone to use. We spend a lot of time making new releases of Android backward-compatible with devices that are not ready for …

Read the Rest…