Today is a good day, I think, for source code drops! Samsung has just released the source code for an update for the Epic 4G Touch, Sprint's variant of the Galaxy S II. The update (FF18) is said to be rolling out to devices right now as an OTA. If you want to get your hands on the kernel code to fiddle with it yourself before the update arrives, however, you can head to Samsung's download page here.
If you've used the official turntable.fm app, then you've probably noticed a couple of different things: firstly, it's awesome. Kicking it in a room and spinning tracks with your homies from your mobile is just rad, and the experience is very similar to that of its desktop counterpart.
Secondly, you've probably also noticed that, upon disconnection of headphones or Bluetooth audio devices, the volume was suddenly muted, even when the turntable app isn't running.
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.
Ding-ding-ding! EVO 4G LTE owners, the update you've been waiting for is ready. v1.22.651.3 of the software is rolling out starting today, July 11th, and according to Sprint fixes a whole array of bugs. The most important aspect of the update has to do with Google Wallet which has been broken since pretty much day one of the release. Other changes include improvements to Wi-Fi connectivity, playback of sideloaded videos, the crashing gallery app, calendar reminders, random power cycling, and more.
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.
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.
When Jelly Bean was announced, it's as if you could hear the entire Android community speak in unison: CM10! Anyone who has been around the block a time or two knows, though, you just don't ask for ETAs on CM builds. Of course, it wouldn't really matter if you did at this point - the JB source code isn't even available yet. However, the CyanogenMod Team took the time to address many of the questions on everyone's minds on their G+ earlier today, and we have to admit - it all sounds pretty good.