All-around awesome guy Andrew Neal has released the result of his project in recent months: a new music app that will be coming soon to CyanogenMod 9. The good news is that you can download it now, before it's merged, and install it on your device. The (pretty major) bad news: it's only available for phones running Ice Cream Sandwich. So unless you've got a Galaxy Nexus, ICS-running Nexus S, or any phone rocking CM9, you're pretty much S.O.L.
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.
The minds behind CyanogenMod have done it again, bringing nightly updates to several LG Optimus variants, and adding official CM7 support for the Epic 4G (not to be confused with Sprint's Galaxy SII variant).
Among the newly-supported LG devices are the Optimus 3D (p920), Hub (e510), Pro (c660), and Black (p970) (which is technically seeing the return of nightlies). It may be worth noting that the Optimus Hub and Pro both received RomManager support tonight, making it excessively simple to get CM goodness on the devices.
Just after expanding Nightly support to Samsung's Epic 4G and a slew of LG handsets, the CyanogenMod team has brought nightlies to a handful of Xperia devices, including Coconut (the Xperia Live with Walkman), Iyokan (the Xperia Pro), and Satsuma (the Xperia Active).
In a Google+ post earlier today, CyanogenMod announced that CM7 support had arrived for multiple new devices, throwing out a special hint to Xperia users.
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).
Just two short weeks after the Kindle Fire received its first dose of Android development goodness (read: root), the first full custom ROM has made its way to the device. The ROM is question is, of course, CyanogenMod 7, the most widely distributed custom ROM among Android devices.
Basically everything works, though there are a few glitches. The touchscreen was initially on the receiving end of one said glitch, as the alignment was off by 90 degrees.
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.
In case you were wondering or had any doubt at all, the CyanogenMod 9 wheels are now in motion (as promised), and in a few months (likely weeks for nightlies) delicious ICS will drip onto 68+ supported Android devices, some completely forgotten by carriers and manufacturers. If you ask me, that's the best thing that could happen to them anyway - what do carriers know about keeping their devices up-to-date with Android, right?