Boy, do we ever have some fantastic news for the AOSP ROM-loving crowd: CyanogenMod nightlies are finally back, meaning the first official CM7 builds are rolling out as I type this. Sure, they're probably moderately buggy (although generally, CM nightlies are still pretty good), and yeah, they may be missing some features - but let's be frank: it'll still probably be one of the most solid Gingerbread builds around, regardless of what device you're using.
Over the past couple of weeks, I spent countless hours debating whether I should wait around a few months and see what tablets come out or get one now. In the latter case, which tablet was right for me?
Let me start out with what I wanted out of a tablet. First and foremost, I needed a device that let me check my email and read the news. Every morning, I wake up, grab my Sprint EVO 4G, and check my email using Gmail and my work email using Exchange.
A few days after releasing the Android 2.3 SDK, Google officially pushed Gingerbread to the Android Open Source Project (AOSP). Shortly thereafter, developers (such as the CyanogenMod crew) immediately started working on their custom ROMs based on the AOSP code (e.g. CyanogenMod 7).
It has only been a few days since CyanogenMod released version 6.1.1, their most recent stable update, so it's still likely to be a few weeks before a stable release of CM 7 is available.
Those of you acquainted with the inimitable Ander Webbs have been waiting for this one for a while. Once dubbed ADW Freak, the souped-up version of everyone's favourite open-source launcher has arrived, and it's now named ADW Ex.
On the surface, Ex brings ... well, it brings crazy transitions and UI effects, mainly. But underneath all that is some pretty impressive performance improvements. In a launcher, the real place where performance counts is in the drawer scrolling, and if you've been feeling that ADW is a bit laggy lately, Ex will quell your frustration with its silky smoothness.
That's right, carrier billing is now available for some Android users on the least Android-friendly wireless carrier in the US. Huzzah. I guess I shouldn't be so cynical - I am an AT&T customer, after all. Unfortunately, I also run CyanogenMod 6 on my AT&T Nexus One, and have not yet received any Market update to allow me to use carrier billing, and doubt I will until an official Gingerbread build coaxes me off my custom ROM goodness.
The Android dev team has generally been assumed to have a passive stance on rooting and unlocking Android devices. That is, do it if you want - we won't stop you. And there's certainly evidence abound supporting this - Google's Nexus One could be unlocked via a simple ADB (Android Device Bridge) command: fastboot oem unlock. The same is true of the Nexus S.
Of course, it only makes sense - Google doesn't want to put any unnecessary barriers between Android developers and the open source OS, especially on developer phones.
Prepare your party gear and break out the keg, people: Google is officially starting the push of Gingerbread to AOSP (Android Open Source Project) as we speak. Jean-Baptiste Queru just announced that fact, saying he was going to begin pushing the code to the AOSP, and the process is expected to take a few hours.
What does that mean for you? ROMs built on AOSP code (such as CyanogenMod) will now have access to Gingerbread, so expect CyanogenMod for Gingerbread (CM7?) to start cooking shortly.
Big news from kernel-master toastcfh about an hour ago: WiMax (Sprint's 4G) is now working on CyanogenMod. This has long been one of the most heard complaints from CM fans with EVOs in particular (in fact, just about every time we post on CM, somebody comments about the lack of 4G). At the moment, details are light - for example, we don't know how long it's going to take to make it into a release, or if there's anything special involved.
We didn't exactly expect it to take long, but the Nexus S that went on sale today has now been rooted by Koush, the creator of ClockworkMod recovery and ROM Manager.
Is it that time already? It was just 11 days ago that CM6.1 was dropped, and the team has already released 6.1.1. As this is a minor update, the changes aren't anything revelatory, but an update is an update, right?
- Common: Add rotary lockscreen - Kmobs/cvpcs
- Common: Updated translations - (everyone)
- Common: Push update notificatiosn - Chris Soyars
- Common: Fix camera sounds - CAF/Cyanogen/mtwebster
- N1/DS/Supersonic: Kernel performance tweaks and fixes (various)
- N1: Update build fingerprint
- Vision: Fix MMS over WiFi calling - Zinx
- Vision: Add console=null to kernel command line - Adam Tygart
- Vision: Kernel to 126.96.36.199 and some performance tweaks
- Droid: FRG83D fingerprint, translations, camera, torch fixes
At the moment, the new revision has only been released for four devices: The EVO 4G, Nexus One, T-Mobile G2, and MyTouch Slide.