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.
The LG G2x is showing up all over the place today, isn't it? This time it's joined by its cousin, the Optimus 2X, as they are both graced with the custom ROM goodness of CyanogenMod. Be warned, though - these are only nightly builds so they are not yet polished, final versions of CM7. They are however, official CyanogenMod builds from TeamDouche, not ported versions from other developers.
Now that you know what's up, you can grab the downloads from their respective threads over at XDA.
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:
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.
That's right folks - CyanogenMod7 RC3 is up for grabs, and we'll be posting the devices it's available for as they come in. Here's the links we have so far:
- HTC Desire HD (and Inspire 4G)
- HTC Click/Tattoo
- Commtiva Z71
- Geeksphone Zero
- Geeksphone One
- Hero CDMA
- myTouch 4G
- Nexus One
- EVO 4G (Download link only, will add thread when it's open)
- HTC Legend
- HTC Slide
We'll keep this list updated as more devices are added.
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.