Yesterday, Cyanogen himself stopped by XDA to drop some preview builds for CM10 for some of US variants of the Galaxy S III. Today, the rest of the world gets in on the action, as TeamHacksung member XpLoDWilD offers up a preview build for the international Galaxy S III (i9300). As with the previous release, this thing is packed to the brim with warnings, but when has that stopped you?
Google recently decided to make my life a lot easier by releasing the changelog for Jelly Bean. Cool!
While, of course, I take issue with its thoroughness, it also wasn't all that accurate when it was first published. It's since been corrected, but the internet never forgets. Check out this Google listing:
Yeah... There isn't actually a ringtone editor in Jelly Bean. Google seems to agree, because, after the initial posting, the mention of the editor was completely removed from the changelog.
In the middle of a rousing discussion on G+ about the uniformity of Jelly Bean's new default app dialog (GTKA article forthcoming), Adam Powell, an Android framework engineer, clued us in to the following Jelly Bean protip:
You know the app pickers in Jelly Bean? These things:
They've been given a makeover in JB.
CyanogenMod 10 is still cooking, and heck, CM9 isn't even fully baked for all devices yet. That hasn't stopped Steve Kondik, aka the guy who puts the Cyanogen in CyanogenMod, from posting preview builds of CM10 over on XDA for the AT&T and T-Mobile Galaxy S III variants. Plus, a third preview build being posted for the Sprint version by another developer. Keep in mind, of course, that "preview build" translates into "absolutely nothing is guaranteed to work." It is exciting, nonetheless.
If you bought a pre-LTE Evo phone in the last year and you've been feeling left out in the cold, worry not. Sprint and HTC are in the process of bringing Ice Cream Sandwich to your device. If your device happens to be an Evo 3D or Evo Design, that is. The older flagship Evo and this year's midrange phone are slated to reach Android 4.0 sometime in August.
Yes, we know that once again, it's not Jelly Bean.
Need some reading for the weekend? Google has you covered. To celebrate the shipping of the first batch of Nexus 7 pre-orders, Google has posted up the full, official, exhaustive changelog for Android 4.1 Jelly Bean.
Covering everything from Accessibility to Widgets, the changelog delivers comprehensive explanations of each and every change users can expect to find in Android's latest iteration, as well as changes to Google apps and the "new Google experience on Android," including Google Search and Google 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.
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.
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.
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.