Get it while it's hot, kids - the DROID Incredible 2 is officially merged into CyanogenMod, and the nightly builds are now being pumped out (direct link here). These nightly builds may contain bugs, dragons, and other potentially annoying/broken things - so flash at your own risk. Your Dinc2 will also need to be fully unlocked, meaning you'll have to use the AlphaRevX Beta 2 software, which you can learn about in this post.
Hey, Droid 2 owners! Remember in the not so distant past when the Droid X received a workaround that allowed it to get its own build of CyanogenMod 7? Yeah, you knew it was only a matter of time before Team Douche hooked you up, too - and now the wait is over.
CM7 nightlies for the Droid 2 have officially hit the CyanogenMod mirror network. It's worth noting that this is build is for the Droid 2 only, and it will not work on the Droid 2 Global.
- Rooting Explained + Top 5 Benefits Of Rooting
- Top Android Apps Every Rooted User Should Know About: Part 1 (Apps 1-8),Part 2 (Apps 9-16), Part 3 (Apps 17-25)
- Custom ROMs Explained And Why You Want Them
- How To Flash A Custom ROM To Your Android Phone With ROM Manager + Full Backup & Restore
- So You Want To Know About Bootloaders, Encryption, Signing, And Locking?
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.
This week has definitely been the week of the Droid X - after about a year of being on the market, the magic of the "2nd init" hack allowed for the first ever unofficial build of CyanogenMod 7 on this popular U.S. device. Only days after the momentous announcement, the Droid X CyanogenMod, led by the great cvpcs, is now part of the official CM source tree and served nightly from the CM mirror network.
As Android users, we have a certain amount of freedom with our devices - especially if you're running a rooted device with a custom ROM like CyanogenMod. One of those freedoms is the ability change the look of Android with themes. In the past, changing themes required booting into recovery, flashing a zip file, and rebooting. On occasion, the theme wouldn't work correctly, so if you didn't perform a backup before you flashed, you were basically out of luck.
Even though it's only been two days since cvpcs first unveiled CyanogenMod 7 running on the Droid X, it seems that he has already worked out enough of the kinks to release the first beta/RC version to the masses. The flashing process is a bit more complex compared to other phone/ROM combos, but well worth the added trouble if you ask me. Everything you're seeing here today would have been impossible without the "2nd init" hack, which cvpcs explains in detail here.
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.
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.
Update 3: Swype has contacted us to clarify the following:
Swype does not, and will not ever make money off of the data it collects from you. They do not sell ads. They do not sell information. The comment made on the CM review forum was a generalization about the larger Android app developer community, and in no way was intended to imply that Swype uses your data for ad revenue.