Google kicked off the Nexus program back in early 2010 with the Nexus One. It was a fine phone for the time, but it's vastly different than the most recent iterations of the Nexus flagship. That's illustrated quite well by this quick GIF.
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).
With all the excitement of Nexus availability and the Android 4.2 source code being pushed into AOSP this morning, one little statement by Android developer JBQ regarding 4.2 device support in the AOSP announcement was easy to overlook.
-There is no support for 4.2 on Nexus S and Xoom. Those devices should continue using 4.1.2.
Yep, that (very, very likely - it's intentionally vague) means exactly what you think it does: it's the end of the road for software updates on the Nexus S and Motorola XOOM (and yes, that means all variants).
The dedicated Android community has a way of tracking down OTA update files almost before the rollout begins. This is again the case for the newest Android 4.1.2 update for some variants of the unlocked Nexus S. Waiting for updates is for chumps, so get your Nexus S in hand, and proceed with caution.
To use this update file, your Nexus S has to meet the following conditions:
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).
After the successful landing of NASA's Curiosity rover on Mars this month, space exploration is once again at the forefront of everyone's minds. While the rover goes about its mission on the red planet, there are plenty of other exciting projects happening closer to home.
One of those projects is the CubeSat Launch initiative (CSLI), in which nanosatellites built by teams across the United States are hitching a ride into orbit on rockets planned for upcoming launches.
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.