Many of you probably already know how I feel about CyanogenMod – I swear by it, especially on my EVO LTE. Nothing beats it in terms of bringing a (mostly) stock experience to your device with just the right amount of tweaks and extra features. Plus, there are nightly updates that satisfy my need to stay on the bleeding edge and get a daily fix of… fixes. The only downside to this is that each nightly update (for my EVO, anyway) hovers around 180MB, a download that takes just a little more time than I care to spend sometimes.
Earlier this evening, CyanogenMod's Google+ page published an announcement that read "Who says Everest is in Nepal?". That's right – the Motorola Xoom 3G (GSM) variant has joined the list of CM-supported devices, getting its first experimental build dated 10-17.
Steady Hawkin, in a comment to the announcement, notes that the experimental build is "still a WIP," and encourages users to report any issues they may encounter.
If you're a Xoom GSM owner looking for some CM10 action, just keep an eye on the CyanogenMod download center's Everest page (linked below) for the latest builds.
If you're a developer publishing apps on Google Play, the developer console is probably something you're checking every day compulsively. And Google understands that just because you're a developer, you don't need to look at something ugly and boring to track your apps' download and ratings stats, or manage their publication status. Back at I/O in June, Google showed off a bunch of new console features that were "coming soon."
And today, Google is finally unveiling those features in a brand-new version of the developer console, and you can start using it right now.
Ok, guys. Start your engines - here's the download and instructions you need to get the leaked Gmail 4.2 up and running on your device. Keep in mind that this is an unreleased version so some things may be buggy or broken, though I haven't run into any problems.
If you somehow don't know what I'm talking about, we have the next, unreleased version of Gmail, and we're finally allowed to share it with you.
It could oftentimes be unstable and not properly tested, lacking any changelogs, but eventually evolving into alphas, betas, release candidates, and finally stable releases.
If you own a Galaxy S Blaze 4G, first and foremost, I'm sorry. But, you can make it a lot less horrible if you flash CyanogenMod 10.
Moments ago, CyanogenMod's Google+ page announced that Sony's Xperia T, the flagship device we first covered during IFA 2012, is joining the CyanogenMod device roster, offering a link to the device's Gerrit code review page and a quick James Bond reference.
What's more, the Xperia T's first (experimental) nightly build is already live in CyanogenMod's download center.
If you've got an Xperia T and have been itching for CM goodness "shaken, not stirred," keep a close watch on get.cm (linked below) for the latest nightly builds.
Yesterday, Android maintainer JBQ posted up a number of binaries and Android 4.1.2 images for multiple Nexus devices. Owners of international GSM variants of the Galaxy Nexus, though, were left out on the image side. Today, both the "soju" (Nexus S) and "yakju" (Galaxy Nexus GSM) have had their factory images updated to Android 4.1.2, and you can find those images here.
Google also saw fit to finally release a factory image for the Nexus Q, though it's based on Android 4.0.4.
Are you dying to get your hands on the latest version of CyanogenMod, but don't want to cope with the bugs that come with nightly builds? The M-Series is just what the doctor ordered, with stable builds of upcoming releases coming every month.
Monthly builds of CM started this time last month, so it's no surprise to see CyanogenMod 10 M2 hitting servers today. As promised, device support is growing, with 7 more devices on the list for M2 than M1.
If you're a developer, you've likely been chomping at the bit for Google to release the updated binaries and full device images after yesterday's Android 4.1.2 release. Just moments ago, Android maintainer JBQ placed 4.1.2 driver binaries for all maintained Nexus devices on the Google Developers site, as well as updated factory images (JZO54K) for the Nexus 7 and "takju" and "maguro" variants of the Galaxy Nexus.
These files are absolutely essential for tinkerers and developers wanting to stay on the cutting edge of Android, and Google has always been pretty on top of getting them out in a timely fashion.
As a developer, I absolutely love days like today. If the high-level "improves performance and stability and fixes bugs" changelog of Android 4.1.2 isn't good enough for you, how about we dive into the actual low-level source code commit logs Android engineers made into AOSP since 4.1.1_r1.1 (JRO03D) all the way through today's release 4.1.2_r1 (JZO54K). These commit logs are spread over probably 100+ repositories, so hunting for all of them manually would probably take you days.