As the Pixel phone announcement draws near, it seems that, if not going away entirely, Google's Nexus brand will at the very least be undergoing some major changes. Google intends to heavily market its Pixel phones if the last week is any indicator, meaning there really won't be much room for the Nexus phone program to exist in the same way it has in the last few years. Nexus may live on, but it will undoubtedly be in a capacity different from the more aspirational efforts we've seen Google make with it in devices like the Nexus 6, 5X, and 6P. Read More
Both Sprint and T-Mobile announced OTA updates for two long-forgotten handsets today stuck on Android 4.1.1 - the Samsung Nexus S and the HTC One S, respectively (that is, the Sprint Nexus S and the T-Mobile One S).
Both updates are described merely as containing security enhancements, but given that Android 4.1.1 is the only known OS version potentially vulnerable to the now-infamous heartbleed exploit, it's fairly easy to determine what this is all about (HTC's site actually confirms as much). It's certainly big of T-Mobile, Sprint, HTC, and Samsung to make this happen at all - many phones languish with serious security flaws after their software support comes to an end, but it seems Heartbleed got enough press that the parties involved deemed the fix a worthwhile endeavor. Read More
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. Read More
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.
As the day progresses, builds for the rest of the officially-supported devices should start appearing on the download page. Read More
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. Read More
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).
: A "nightly" is a bleeding edge release that is built on a daily basis, usually at night after a full day's worth of new code has been committed.
It could oftentimes be unstable and not properly tested, lacking any changelogs, but eventually evolving into alphas, betas, release candidates, and finally stable releases.
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). At least, that's what's implied. When asked for comment, JBQ said no further information could be given about future updates for the Nexus S or XOOM, which is the standard response to such inquiries. Read More
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 device must be the Soju variant with model number i9020T or i9023. In case you don't recall, the i9020T has T-Mobile 3G, and the i9023 is one of the overseas versions.
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). Sorry, guys - looks like we'll have to keep waiting for those. Read More