After celebrating CyanogenMod 6.0 hitting the final release version for a multitude of devices, the CM team got right back to work on the next version of the largest Android ROM on the planet. 2 months worth of sleepless nights paid off, as minutes ago, Cyanogen announced a new major milestone - CM 6.1 Release Candidate 1. According to the team, the release is definitely good enough to be a daily driver, and the remaining bugs will be quickly squashed, so go ahead and fearlessly hit up the download links below.
Remember when a new piece of code hit Gmail Labs called Mail Goggles - the one that made you do a few math problems before emailing somebody at pre-determined time-frames (such as late at night on the weekends)? Today, Brian was browsing the CyanogenMod (CM) Gerrit and noticed a new series of code - similar to Mail Goggles - has been added: Drunk Mode.
As I'm not a developer, I haven't the slightest idea how it works (and Brian is "in drunk mode" himself) - but I'd guess the "professional" in the description provides something of a hint.
Today, in the wee hours of the morning, Cyanogen tweeted what many people have been waiting for: video footage of CM6.1 up and running on his T-Mobile G2.
His explanation for how things work:
Basically what I'm doing is temprooting and rebooting all of userspace with CM on the sdcard. Gonna keep refining it while the really persistent and smart guys from #g2root keep working on a permanent root.
And there you have it.
The fact that it is actually running on the device is encouraging, but we could still be pretty far away from a testable version: no downloads are available yet, and if you look at the notification bar, you'll see a pretty significant bug in this build.
This is what happens when you try to one-up the open-source community. Just when we were beginning to think HTC Sense might have come up trumps with a real killer feature in their Fast Boot, CyanogenMod creator Steve Kondik's right there with a cheeky "Yeah, CM6 "does" too :)". Tweeting that the feature will be committed to the CyanogenMod source soon (possibly with the arrival of version 6.1), Cy noted that the Nexus One would likely last in this hibernation state for about a week.
There will also be support for a few new devices- Acer Liquid, HTC Wildfire and Samsung Vibrant. My eye is also on the new HTC phones that are about to get released like the G2.
It looks like their doors are still open to new devs and currently unsupported devices, as well - to quote Cyanogen once more:
It turns out that some Nexus One owners running CyanogenMod 6 (CM6) have been experiencing issues when trying to update a handful of system apps. As such, XDA-Devs forum member unforgiven512 has thrown the updates into a tidy package. The updated apps are:
Amazon MP3 Google Maps Google Search Google Voice ROM Manager Street View Superuser TalkBack Voice Search
Not only does this fix the app updating bug, but it moves the app info from the "data" partition to the "system" partition.
CyanogenMod 6 is one of the most popular Android custom ROMs, and for a good reason - besides supporting a myriad of devices, it is built from AOSP (Android Open Source Project), which means no extra garbage that normally comes installed by carriers and customizations/improvements for the people, by the people (the CM contributor community is huge).
Sprint has abandoned our beloved HTC Hero (it was my first Android device a bit under a year ago now and holds a special place in my heart) but the Android community hasn't.
CyanogenMod 6, a very popular custom Froyo ROM for a whole slew of Android phones, has given thousands of Android users something device manufacturers tried to take away - absolute freedom in customizing your Android experience. One glaring omission from the bunch is the Motorola Milestone, which Motorola decided to lock down way harder than its US counterpart, the original Droid.
One of the most common complaints about the recent builds of CyanogenMod 6 has been that Nexus One owners’ GPS would suddenly take ages to get a fix or wouldn't get a fix at all. The most frequent solution posted has been to change your Mobile Network APN type to “default,supl” to enable A-GPS through your cellular network. However, for some people this still didn’t solve the problem, including myself.
Well, today on the CM forums, user kursed posted a fix that may be the end of many frustrated N1-ers’ woes.