The road to CyanogenMod 7.1, undoubtedly the largest Android custom ROM, now covering a mind-boggling number of devices (68), has been long and rough. We've been hearing rumblings that the final release was almost here for a number of days (just watch the video of the CM sessions from the Big Android BBQ below), but a couple of hours ago it really did seep through and end up at CM download mirrors across the web.
I'm curious to see what percentage of our readers who run custom ROMs are using AOSP (Android Open Source Project - something pretty close to vanilla Android, such as CyanogenMod), and what percentage are using something based on stock device ROMs. More specifically, I want to find out if people on certain manufacturers are more likely to go AOSP than others - in other words, is Blur/NinjaBlur pushing more people to AOSP than TouchWiz, or is there no difference?
Not content to wait for manufacturers to get in to shape and update our phones to the latest and greatest versions of Android, most of us here at Android Police have had a brush with a number of custom ROMs in the past.
Whether it's the latest version of Cyanogen or a more obscure mod, there is always a ROM floating around on my phone, and until now I've always had to uninstall one before installing the other.
The technology that allowed custom ROMs like CyanogenMod on the Droid X/2 and Atrix - 2nd-Init - has now been ported to the Droid X2 by XDA forum member edgan. According to the source thread, it was a direct port from the Atrix, as the code was not modified whatsoever, only re-compiled.
Before I go any further, let's get one important piece of information out of the way: this does not unlock the bootloader or allow custom kernels; it simply brings full custom ROM support.
The team behind the most popular custom Android ROM on the planet, CyanogenMod, is not planning to take a break even for the national holiday (happy Independence Day, everyone!), giving us a number of new reasons to praise their product over and over again.
Update 2: SMS send and receive and mobile hotspot are non-working. Do not download this file (the link has been removed) - wait until a more stable release is available. If you need to flash back to Froyo, please check out this thread on MyDroidWorld.
Disclaimer:This article contains very device-specific flashing instructions. Read them carefully. We are not responsible for any damage, bricking, loss of data, or inadvertent explosions resulting from your attempts to flash this update onto your DROID Charge.
The recent unlocking of the HTC Incredible S' bootloader made possible some astonishing feats, not the least of which is the possibility for custom ROMs. Cyanogen and his team have already gotten to work on that last part, and the fruits of their labor are nothing to scoff at: a nightly build of CyanogenMod 7 is now available for the Incredible S.
This article deals with a couple of advanced topics.
Update: In a new Facebook update, HTC explained that some apps would be cut to allow enough space for the Gingerbread update. Looks like it was all about internal storage after all, rather than RAM.
That was quick. HTC, via its UK Facebook page, has announced that Gingerbread will be coming to the Desire after all. Despite the all but scientific conclusion of HTC's engineers, after rigorous testing, that "there isn’t enough memory to ...
Ladies and gentlemen, it appears that cvpcs has achieved the impossible: he's thrown together (but not yet publicized) a build of CyanogenMod 7 that works on the Motorola DROID X!
Naturally, since no one but cvpcs has the firmware yet, there are still a few kinks that need to be ironed out before the ROM goes public - for example, GPS, 3G, Bluetooth, and the camera/camcorder have not been proven to work just yet, and audio (including phone calls, speakers, the microphone, etc.) definitely isn't functional at the moment.