If you happen to own an HP TouchPad and have been waiting patiently for a proper Android port, you'll be overjoyed to see a sneak peek of what CM9 brings to the table. If you recall our announcements for the CM7 Alpha 1 and Alpha 2 builds, you probably remember an overwhelming indication that neither build was all too stable, and running them was not for the faint of heart. Alpha 3 is a bit better, but still has a laundry list of issues.
In the custom ROM world, there's one name that can't be denied or avoided: CyanogenMod. It's the reigning champ of all custom ROMs, and for good reason - it's amazing. The CM team is always finding ways to innovate and bring new features to stock Android, resurrect older devices, and remove manufacturer/carrier restraints from modern devices.
Apparently we're not the only ones who think so, either - CyanogenMod hit one million unique installs last night.
The Cyanogenmod Team is thinking about building an app store. "Ugh, another app store?" you say? Hold on a minute, there's some serious merit to this one. This is an app store for rooted apps. Rooted apps that the carriers hate and frequently remove from the Android Market.
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.
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).
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.
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?
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.
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:
(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.