While the official OTA update to Android 4.2.2 began rolling out to the Galaxy Nexus, Nexus 4, 7, and 10 last night, you may not have received it yet. We already posted a link for the Galaxy Nexus takju build, but now we've got a couple more to share.
Update: JDQ39 from JOP40F for the Nexus 10 added.
- Nexus 7: Android 4.2.2 update (JDQ39 from JOP40D, 47.7MB) (Note: Wi-Fi model only, aka grouper/nakasi)
- Nexus 10:
Your device needs to be running the JOP40D build in order to flash the updates, doing so from another build will probably just fail, but we wouldn't attempt it either way. Read More
A couple of hours ago, Google started rolling out the Android 4.2.2 update to a very limited subset of Nexus devices (build JDQ39). At this point, almost nobody can get the OTA pulled by going through the Settings screen, but don't worry - one of our loyal readers extracted the OTA url for the Galaxy Nexus and sent it over to us (great work, Daniel Koch!).
For now, we only have the link for the takju Galaxy Nexus variant, i.e. Read More
Nexus owners may have a reason to stay up tonight, as a couple of Reddit users report that Android 4.2.2 has begun rolling out to the GSM Galaxy Nexus and the Nexus 7.
There's not much word regarding what the update (which carries build JDQ39) includes just yet, but readers may remember that Google promised a Bluetooth A2DP audio streaming fix in the "next release" of 4.2 after 4.2.1.
Update: Here's The Android 4.2.2 JDQ39 Update For The GSM Galaxy Nexus [Manual Installation Instructions] Read More
Good news, basketball fans. Google has been gradually upgrading the Now service to include a wider range of sports teams, and today Division I NCAA basketball teams from all over the US can be manually added to your personal Now results. Go into the Google Now settings page, tap "Sports," and search for your favorite school. Only basketball is supported at the moment - here's hoping that football teams are added before the season starts. Read More
Yearly releases of flagship hardware are a staple of the smartphone world - in fact, we're generally pretty pleased if twelve whole months can pass before we get a "+" or "HD" slapped onto our formerly cutting-edge phone. But in the console world, it's a different story, with at least five years between major releases being the norm. Android-powered gaming console OUYA intends to take the mobile approach, according to Joystiq. Read More
Update: We've heard from US Cellular that the rollout will begin on February 12th - apparently someone jumped the gun on the update page.
After promising to do so in Q1 2013 back in December, Motorola has officially begun rolling out Android 4.1.2 to the Electrify M on US Cellular. The Electrify M is basically a de-Verizoned RAZR M, so it makes sense that the Electrify's update follows after its DROID kin's. Read More
After an initial debut in France, Motorola has begun distributing the Android 4.1 update to RAZR i handsets in the UK today. Just hit that 'Check for update' button as often as possible over the next week or two, and you should be able to get it. Here's Motorola's statement on the rollout.
We’re excited to announce that MOTOROLA RAZR™ i with Intel Inside is getting upgraded to Android™ 4.1 Jelly Bean.
It's that time again! We get another glimpse at what the platform distribution numbers are like for Android. If you've been following along, you'll notice there aren't many changes: Gingerbread is still the biggest slice of the pie, Ice Cream Sandwich is second, and the two major versions of Jelly Bean together make up the third largest. 2.3 is down to 45.4% from 47.4% a month ago. That 2% difference seems to have gone overwhelmingly to Jelly Bean which went up to 13.6% from 10% a month ago. Read More
Just a quick note to those Nexus 4 owners and developers out there looking for a quick and reliable way to download the official factory image: Google has put it back online. While the image has been readily available in the community during its unexplained absence, it's nice to see that whatever issue prevented Google from posting it has presumably been resolved.
The Android version and build numbers remain unchanged, as do the checksums, so it appears this is the same file that was posted originally. Read More