Following yesterday's Jelly Bean AOSP invasion, the HSPA+ Galaxy Nexus is now receiving the release build 4.1.1 (JRO03C) of Jelly Bean. That's indeed great news, but since the rollout is usually staggered, not all phones are allowed to receive it the second it's out there. If you're rooted or have an unlocked bootloader, why not just bypass the line and flash the update manually? I just did, and it took only a few minutes.
The Android development community couldn't be more on fire today now that Android 4.1 has been fully open sourced. While the Jelly Bean flavored CyanogenMod 10 is not just here just yet (though work has already begun), the CyanogenMod team released a fantastic treat for new Galaxy S III owners on AT&T, Sprint, and T-Mobile - official nightlies, available for downloading and flashing right now:
In a post to the Nexus Google+ page just minutes ago, it was revealed that the official rollout of Android 4.1 Jelly Bean to the Galaxy Nexus is beginning now (just after its addition to AOSP), starting with HSPA+ connected Galaxy Nexus Devices. Users of Galaxy Nexus devices carrying the Yakju and Takju software variants should expect to receive an OTA prompt some time within the "next several days."
The post also revealed that the HSPA+ Galaxy Nexus won't be alone in receiving an official Jelly Bean update.
Our I/O Nexus 7s just received update notifications that a new software build is available for download - this is very likely the final retail build users will see when they receive their devices.
While a "changelog" of sorts pops up with the update notification, it's stock dialogue from a full-on Jelly Bean upgrade, not something specific to this particular update for the Nexus 7. More than likely, this OTA just irons out some bugs and turns off some unnecessary data logging and pre-release testing tweaks.
So, you heard about Google's new predictive text engine in the Android 4.1 Jelly Bean keyboard, right? Now you can download that keyboard courtesy of Beansoft (developer of Thumb Keyboard), from the Play Store, free of charge. It's ported straight from AOSP, though it's currently in "alpha" state. The only catch is that you need to be running Android 4.0.3 or higher (Ice Cream Sandwich).
I've noticed the Android 4.1 keyboard also seems to have improved accuracy and speed (it looks ever so slightly different, too), so this is definitely worth a try.
OK, OK, that's actually Linus Torvalds expressing his feelings about NVIDIA, but there's no better way to articulate the continued frustration with the complete lack of Sprint Galaxy Nexus support in AOSP. Verizon is [almost] there. Sprint, however, is not. Try finding it (hint: its codename is toroplus) - specifically, the CDMA/LTE binaries.
If you still have doubts about the above notion so eloquently conveyed by Linus' gesture, Jean-Baptiste Queru's comment confirms:
Earlier today, the Jelly Bean source code rolled into AOSP (Android Open Source Project). This is a big deal - one we've been waiting for since the great Google I/O unveiling. What does it mean exactly?
It means that ROMs that are built from AOSP, like CyanogenMod, can now start integrating the Jelly Bean code and release the first true JB nightlies. Not broken ports from the Galaxy Nexus builds - real ROMs.
Jelly Bean was announced at Google I/O just recently, but a posting from Google's Android open source guru, Jean-Baptiste Queru has confirmed that Android 4.1 is hitting the Android Open Source Project (AOSP) repository right now. Time for the developers among you to update your clients to get all the official bits.
This release will be tagged as android-4.1.1_r1 in AOSP. While the source is going live now, the full proprietary binaries for Google-blessed devices won't be rolled out until later.
Months after AT&T's Samsung Galaxy SII Skyrocket got a leaked build of Ice Cream Sandwich, it looks like the device is finally getting an official update. Users at XDA began reporting the update earlier today, indicating that it is available over Kies. Unlike March's leaked build, the official update brings users to Android 4.0.4, rather than 4.0.3, and (of course) carries a different build number. Here's a snippet from the update's build.prop:
ro.build.description=SGH-I727-user 4.0.4 IMM76D UCLF6 release-keys
Of course, rooted users would be advised to wait for a pre-rooted build of the update.