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.
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.
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.
What does it mean? Captivate is the first device of the Galaxy S bunch to move to the official CM download area in the form of nightlies.
It's that time of the week again folks - time to hit the polls. This week's question is one that'll allow you to express what you think an Android handset should let you do in terms of customization, modification, and other various tinkering (think rooting, custom ROMs, kernels, etc). Basically, we want to know how important it is for you, as a consumer, that your next phone be easy to customize.
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.
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:
CyanogenMod, or simply CM, is hands down the largest and the most widely used Android custom ROM family on the planet, with support for 30 devices, both tablets and phones, from hundreds of developers all over the world. Over the past 4 months, these developers have been sweating day and night upgrading CM6's Froyo codebase to Gingerbread, and today CM7 is finally fully baked.
Most CM 7.0 mirrors are already up (with the rest going up shortly), so if you are anxious to try out the version for your device, head over to the CyanogenMod Stable Downloads page and download away.
One of the ways Android protects application users from unwanted activities is by requiring every app to declare a set of permissions and allowing users to view those permissions during the installation phase. Don't like what an app can do? Just don't install it.
However, this all or nothing approach doesn't allow you to selectively turn off specific permissions, so if you don't like that an application accesses your phone state, you can't just disable that and still have the app installed.