If you have a Samsung Vibrant running CyanongenMod, then you probably want to flash a a stock-based ROM double-quick. Why? Because you can't call 911 while running CM on this particular device. Sure, you may not remember the last time you had to call 911 (if ever), but can you imagine what would happen if you were in a situation where you needed to call 911 and couldn't?
For this exact reason, the CM team has decided to drop support for the Vibrant. The issue could be resolved with the radio source from Samsung, so if Sammy ever decided to release this code, there is a chance that CM could pick up support for the Vibrant again.
In a reassuring blog post, Cyanogen recently told readers that "things are slowly starting to come together," regarding progress on the hotly anticipated Cyanogenmod 9, which is based on Android 4.0.
The entry goes on to explain that the devices most likely to see CM9 first are those based on OMAP4, MSM8660/7X30, and Exynos chips, as well as a few Tegra 2 tablets (including the Galaxy Tab 10.1 and ASUS Transformer).
That's the good news. The bad news is that owners of the OG Droid will be left in the cold, come CM9. The team is also facing challenges due to framework changes in Android 4.0 that "break compatibility with older proprietary camera and graphics drivers." Despite such setbacks, however, Cyanogen writes "I am confident that the team will be able to overcome these issues like we have in the past."
The progress update also promises shorter "spin-up time" when compiling Cyanogenmod from source, and a few other enhancements, including an overhauled music app, a brand new file manager, and a new launcher based on Ice Cream Sandwich.
Update: Steve Kondik (Cyanogen) himself verified via his Google+ page that TeamDouche was not involved in the project.
I guess you can finally buy a phone with something that resembles CM on it. Unfortunately, our team wasn't involved in this.
Under normal circumstances, I find unboxing videos to be pointless and boring. However, this isn't what I would call normal circumstances. A beta tester for the new Republic Wireless service received her phone yesterday and decided to do an unboxing for all to see. When she powered the phone up, it's clear that it's not running stock Android - it appears to be running CyanogenMod 7 (or some variant of).
Dear Android Custom ROM developers: I love most of you. Really. You're part of what makes Android so awesome, because you're so enthusiastic about it, and about making it better. Because of you, we have awesome things like CyanogenMod.
I want to give you some numbers. Let's just look at some popular Android devices:
T-Mobile Galaxy S II: 9
AT&T Galaxy S II: 8
HTC ThunderBolt: 23
DROID BIONIC: 7
Epic 4G Touch: 10
What do these figures represent? The number of different custom ROMs found on the first page of the XDA forums for the above devices. The ThunderBolt's count comes from the pinned post on the ThunderBolt's forum with a listing of ROMs - and those are only the Gingerbread ones.
While we've seen the newest iteration of Android show its stuff on the phone, we've yet to see what the experience will be like on a tablet. That's all about to change, though, because Cyanogen himself posted the following on his Google+:
ICS on the Galaxy Tab 10.1 is pretty great. Coming soon to a CM mirror near you :)
I, for one, am giddy with excitement about this; I've been looking forward to ICS on my Tab 10.1 for a while now. Of course, we all know the first rule of Cyanogenmod by now, so we'll just hang out on the sidelines and wait for this one to make its way to the mirror network.
Just six days after The CyanogenMod (CM) team released the first alpha build for the TouchPad, they're back with alpha 2. Despite being bumped up a version, it's still an alpha, meaning there are many things that can (and likely will) go wrong. Still, it looks like they've made quite a few improvements with the update:
Changelog: (AKA things we hope we fixed)
* Plugging headphones in should now shut off speaker volume * Battery drain issues have been (partially) addressed * More apps now available in market (thanks to Flemmard) * Temporarily removed suspect fsck_msdos to fix random folder deletion on media/sdcard.
At the end of today's Ice Cream Sandwich unveiling, we found out that the ICS SDK (API 14) was available immediately, but a much more important bit - the source code - was not mentioned at all. It didn't really come as a surprise - historically the source was released about a month after the SDK (with the exception of Honeycomb), but I'd like to clarify something right away for those confused between the SDK and the source code.
The SDK (software development kit), which includes the Android emulator, does not contain any source code whatsoever, which means any ROMs built from source, like CyanogenMod, will be waiting for said source to be released before we see any ICS releases.
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.
CM 7.1 adds support for the following (note that not all of these have stable releases out):
At the beginning of August, the CM team announced that they would be supporting the Sony Ericsson Xperia Play, arc, and neo. Cyanogen himself has now announced via Google+ that they have joined together with the FreeXperia Team to bring CM7 to seven other Xperia devices in future releases, totaling the number of supported Xperia devices to ten. The full list includes:
Xperia Mini Pro
Xperia X10 Mini
Xperia X10 Mini Pro
There's no word on when this update will roll out, but we'll make sure to keep you posted.
It has been a while since we've talked about anything new for the Desire S, but thanks to the Revolutionary unlock tool, this handset is getting its first taste of CyanogenMod. Nightlies for the device went live last night, joining the dozens of other handsets that have been missing over the last several weeks.
So, if you're ready to show your Desire S some CM7 lovin', head over to this link to grab the download, and don't forget to grab Gapps while you're at it.