The gold release for CyanogenMod 10.1 (Android 4.2) is very, very close, folks. The CyanogenMod team has already gone through four (count 'em, four) release candidates to date, and the fifth has just started popping up on the CyanogenMod download page. RC5 for the Sprint, MetroPCS, Cricket, and AT&T versions of the Galaxy S III are available at the time of writing, as well as the Nexus S, Nexus S 4G, Samsung Captivate, Acer Iconia Tab A700, and the Nook Tablet.
With CM10, the CyanogenMod team started pushing out M-Series releases, which are designed to be a more stable alternative to nightly builds. In fact, CM cites these builds as being "mostly stable and ready for everyday use."
We saw two runs of M builds show up for CM10, which were followed by the stable release a few weeks later. Now, the team has released the first M build of CM10.1 for several devices:
- Samsung Captivate
- Samsung Nexus S (+4G)
- Samsung Galaxy S3 USA models (D2*)
- Samsung Galaxy S (galaxysmtd/galaxysbmtd)
- Google Nexus 7
- Google Galaxy Nexus (all variants)
- Google Nexus 4
- Google Nexus 10
- ODroid U2
- Samsung P3100, P3110
- Samsung P5100, P5110
Of course, this is just a starter list and more devices will be added in the coming days/weeks.
Another day, another round of nightly builds for the upcoming CyanogenMod 10.1. This time, the latest release of the custom ROM that brings Android 4.2 has been made available on a further 3 devices: the Google Nexus S, Nexus S 4G, and the ASUS Transformer Pad 300 (TF300T).
The newest sets of binaries for Nexus devices have been published and are now available to download on Google's Nexus drivers page. This new batch of binaries is for Android 4.1.1 build JRO03R, and covers basically all Nexus phones and tablets:
- Nexus S (crepso)
- Nexus S 4G (crespo4g)
- Motorola XOOM Wi-Fi (wingray)
- Galaxy Nexus GSM (maguro)
- Galaxy Nexus LTE (toro)
- Nexus 7 (grouper)
Back in July, Google made available the stock Jelly Bean images for a couple of the Nexus S variants, as well as the GSM Galaxy Nexus, and Nexus 7. Today, the build for the global Nexus S (soja) got updated to Android 4.1.1 (JRO03L), and the Nexus S 4G (sojas) Jelly Bean 4.1.1 image (JRO03R) made its way to Google's image download site, as well.
Unfortunately, there's still no sign of Jelly Bean showing up for the Korean version of the Nexus S (or the LTE Galaxy Nexii, for that matter).
There may have been a bit of a false start recently, when a Sprint employee took to the community forums to announce that the rollout of Jelly Bean for the Nexus S had begun. Maybe the rep confused the Nexus S for the Galaxy Nexus, as we hadn't heard any reports that users had received the OTA for the older of the two Nexii. Today, though, Sprint has posted in its forums details on the upgrade, including a release date of today, September 11th.
Just earlier today, we found Sprint documents that confirmed the Galaxy Nexus variant on the Now Network would be receiving Jelly Bean today. Now, a Sprint employee has confirmed on its community message board that the Nexus S rollout will begin today. As with the GNex update, this will be an OTA, so no, refreshing over and over won't get it to you any faster.
Of course, it's still a reminder that CDMA Nexii get the short end of the stick.
CDMA-based Nexuses (Nexii?) tend to get the short end of the stick when it comes to timely updates. The promise of the Nexus is that you'll always have the latest Android experience just the way Google imagines it. While the international version of the Galaxy Nexus has had Jelly Bean for a while, Sprint's been left in the cold. Until, tomorrow, September 6th, if Android Central's source is correct.
Here's the email that a tipster sent in:
The verdict in the Apple-Samsung legal battle came in much sooner than expected and the news hasn't been good for Samsung. To pull out one of the most relevant details amid all the patents and trade dress claims, the jury has ordered Samsung to pay Apple $1.05 billion in damages. Yikes.
Update: The jury was asked to reconsider Question 4 of the verdict form. After deliberating, the jury's answer was changed to "no" for the Intercept and one other device, and the damages amount officially changed to $1,049,343,540.
In a post to Google's Android Building group today, Jean-Baptiste Queru once again acted as the bearer of good tidings for developers and tweakers everywhere, announcing that "a new set of proprietary binaries for Jelly Bean are available."
The new batch of binaries includes those of the Nexus S and Nexus S 4G (Crespo and Crespo4G respectively), the latter of which we just recently saw added into the AOSP fold.