Samsung's Android devices have always come with easily unlockable bootloaders, so seeing the Verizon version of the Galaxy S III locked down at the request of the carrier (we don't buy your excuse, Verizon) was quite a shocker to many enthusiasts (not like it stopped them). Samsung, realizing how important it is to have unlockable bootloaders on its devices, decided to go the same way Motorola did back in January and release a user-unlockable Galaxy S III Developer Edition specifically for VZW.
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.
While Samsung may have started pushing the ICS update to international Galaxy Notes back in May, AT&T owners of what is essentially the same device were left wanting. Today, however, that all changes; Samsung has made available Ice Cream Sandwich for the AT&T version of the Note.
Aside from all the added benefits and enhancements of Ice Cream Sandwich, Samsung has also includes its "Premium Suite" of apps designed specifically for the Note.
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.
The Galaxy S III on Sprint has been seeing a considerable amount of update action in the short time since it's been released. Back on June 29th, the device saw a security update and now, according to Sprint's community website, a second "Google security updates" OTA software patch is headed to the device.
The carrier hasn't offered any details on what the update fixes, beyond that today's update is Google-related, while the previous update is just a generic security update.
Last night Samsung released the kernel source code for the Verizon Galaxy S III. While it's good that Samsung is making good on timely source releases, this particular bit of code didn't do a whole lot of good in way of GSIII development because of the VZW GSIII's locked bootloader. Fortunately, Team Epic has changed this with a new workaround called kexec hardboot (kernel execution hard boot) that should allow users to effectively "sideload" custom kernels without having to actually flash them on the device by bundling the kernel with the custom recovery.
Around the middle of last month, Samsung published the source code for the AT&T, T-Mobile, and Sprint versions of the Galaxy S III to its Open Source Release Center. Mysteriously, the Verizon variant's code was nowhere to be found - until late last night, anyway.
You can now find the kernel source for the Verizon GSIII alongside its brothers, thus rounding out the source release for the Big Four here in the U.S.