Yesterday we told you that cvpcs managed to find a way to put together a CyanogenMod build for the DROID X, despite its locked bootloader. It turns out that the DX wasn't the only locked up Moto device that was getting CM-ified, as Quarx over at XDA has ported CM7 to the Motorola DEFY.
This build is basically usable as a daily driver, with everything aside from 720p video capture and WVGA photos working.
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.
Shortly after officially adding support for the original Galaxy S line that is now approaching its first anniversary, the CyanogenMod team set out to prove once again that it's the single greatest ROM family in the world of Android, breathing lives even into devices that are approaching retirement age.
No, it's not a shiny new Atrix or a beefy G2x (at least not yet) - this time it's the good old gramps Motorola CLIQ, also known as DEXT outside the U.S.
After spending almost a year with my EVO 4G in what was essentially rooted stock condition (Fresh ROM, based on stock Sense, minus bloatware), I finally got frustrated to the point that I was ready to make the jump to CyanogenMod and see just how much better the fully unlocked stock Android experience with CM improvements is.
The Sense ROM offered by Fresh, even in its supposedly optimized form, was starting to get quite slow and would sometimes start choking for no reasons whatsoever.
Back in March we reported on a proposed patch to CyanogenMod that would allow users to deny apps access to certain permissions while retaining the connection to others. This lets users install applications they are interested in, while remaining mindful of their privacy.
Update: Indeed, the "faking data" patches did not make it into CM and probably never will - thanks to all who posted the correction, including the patch author.
What a week for Samsung Galaxy S family device owners! First, the Captivate was officially added to the list of devices supported by CyanogenMod, the largest Android ROM community in the world, and now not 1 but 3 more phones are following suit - the Galaxy S, the T-Mobile Vibrant, and the Sprint Nexus S 4G (crespo4g).
Galaxy S owners, you may have a reason for some early celebration. CyanogenMod 7 for the GS variants, which has been around in relatively unsupported early alpha stages for the last couple of months, has just gone quite a bit more formal with the introduction of the new "captivatemtd" device branch.
CyanogenMod 7.0.3, an incremental release for CM 7, is now live at cyanogenmod.com. While we're waiting for the official changelog from Cyanogen himself, I can tell you that it does not contain Android 2.3.4 (it's still based off 2.3.3) - that's been saved for CM 7.1 (if you can't wait for 2.3.4, you can update to it by using the nightlies). It does, however, contain important security fixes, among other things.
The CyanogenMod crew seem to have had a pretty busy Easter weekend - first they released the pre-alpha for the Thunderbolt, and last night they dropped an update to CM7 for all other platforms. This update brings the current version of CyanogenMod to 7.0.2 and is primarily a bug fix release, but it is also the first "stable" release of CM7 that we've seen for the OG Motorola Droid.
Among the many bug fixes included in 7.0.2 is the GPS issue that EVO owners have been experiencing since the initial release of CM7.
Yes, you read right - CyanogenMod 7 for the Thunderbolt. We're super excited, too, because we can finally get our Thunderbolt Gingerbread on! But, please be careful, this is a pre-Alpha release (that means the release before the release before the beta), so be careful. Here's what does not work:
-USB Tethering does not work. -Phone Testing menu does not display correct radio options. If you play with it, you will have to relfash a Stock based rom to 4G back.