If you head on over to Google's factory image site, you'll find brand-new images based on the incremental update to Android 4.2.1. The devices with factory images currently available include the Nexus 7, Nexus 7 3G, Galaxy Nexus (takju, yakju), and Nexus 4. The 4.2.1 image for the Nexus 10 has been delayed, according to JBQ, due to an issue with JOP40C not being flashable over older builds. This has since been fixed, and you can download the new 4.2 factory image for the Nexus 10, though it's still build JOP40C.
Not to be left out, it looks like the Galaxy Nexus Takju is getting its own 4.2.1 update just after the 1.1MB package started hitting the Nexus 7 and 10.
If you've got a Takju Galaxy Nexus and don't feel like waiting around for the OTA to find its way to your device, you can – as always – install it yourself.
It should be noted that this update package is only meant for Takju – that is, the Galaxy Nexus available in the Play Store.
I understand that there have already been dozens of rants in regard to Google's "launch" (and yes, that requires ironic quotes) of the Nexus 4. And I understand that sitting here whining about it doesn't help anyone - so I'm going to avoid that. Really. I mean it. Mostly. But I am going to be critical.
From day one, the Nexus 4 has seemed - essentially - cursed. Victim to some dark techno-magic that has ensured nearly every step of the way that Google's flagship $300-350 phone would be delighting as few consumers as possible in the critical holiday sales season.
Android 4.2.1 along with its source were released today, but outside of the December bug in the People app, it wasn't immediately apparent whether it contained other fixes and improvements or not. The list of files touched by the Nexus 4 OTA was extensive, but now thanks to developer Al Sutton, we can confirm that most of those were probably just minor edits to bump the version number.
According to Al and his handy AOSP diff script, here are the only changes in Android 4.2.1 (4.2.1_r1) open source code compared to Android 4.2 (4.2_r1).
Earlier today, both the Nexus 4 and the Nexus 10 started receiving small ~1MB OTAs to Android 4.2.1 with fixes to the missing month of December in the People app, among other things. The corresponding open source files are being pushed by Google to the Android Open Source Project (AOSP) as we speak, Android release engineer Jean-Baptiste Queru just announced in the Android Building group.
The build number is JOP40D and the tag is android-4.2.1_r1.
When Hurricane Sandy pummeled the eastern seaboard late last month, no tech event was spared - including AllThingsD's Dive Into Mobile conference.
If you're not familiar with this particular technological get-together, you probably should be. Dive Into Mobile is where the big guys in mobile tech sit down and talk shop with Walt Mossberg and friends, and the show is particularly famous (or infamous, as hindsight may have it) to Android fans as the venue in which Android 3.0 Honeycomb and the Motorola XOOM were unveiled.
If you're looking for the Android 4.2.1 update to the Nexus 4 that started rolling out this morning (it's a very minor patch, at only 1.1MB), you can find it, straight from Google's servers, at this link.
The update, JOP40D, so far has one known fix: the missing month of December in the People app (Contacts.apk). Presumably it fixes other things, too - Google probably wouldn't release a patch just for a single bug, but we haven't figured out what else this patch may address just yet.
After beginning its steady march to wide release in Germany a few weeks ago, the Jelly Bean (Android 4.1) update for the Galaxy Note 10.1 is making its way to more European nations today. The UK, Spain, and various Nordic nations (presumably Denmark, Norway, Sweden, and Finland) have the firmware available now (grab it here or here), if you're feeling impatient. Otherwise, just keep hitting that "check update" button over the next week or two, and sweet Jelly Bean goodness should be on its way to you shortly.
Chrome for Android is expected to start aligning with desktop releases of the browser by "early next year," according to a post by the Chrome team on Google+.
Q. Chrome for Android is still at v18, while regular Chrome is at v23. When will Chrome for Android catch up?
A. Soon! We expect an update to Chrome for Android starting with a developer update to happen before the end of the year, and we’re actively working towards aligning releases across all platforms, including Android, starting early next year.
Well, folks, we don't want to say we told you so. But if you'll take a look at any app in the web version of the Google Play Store, you'll see that almost all of the reviews have had the name entry changed to "A Google User." Try to add a review, and you'll find that you're required to do so from your Google+ account.
The change seems to have affected the on-device view a little differently - according to checks on multiple devices here at Android Police, the names that were formerly there (usually linked to the old Google Profiles) are just plain gone.