Google Sends Android 4.2.1 to AOSP, Changes Affect All Nexus Devices

| February 2, 2013 | 9 Replies


AOSP (Android Open Source Project) received a new chunk of code from Google today tagged android-4.2.1_r1.1 and android-4.2.1_r1.2 . So Nexus 4 owners will probably see an OTA update in the near future. Sadly, this was not the Android 4.2.2 that we have all be hoping for. There also don’t seem to be a lot of major changes, but there are a few bug fixes that we will discuss below. But before we get to that, lets talk about what isn’t included. There doesn’t seem to be any fix for the most common bug that is being reported from the Nexus 4, the Bluetooth issues. Apparently the developers over at Google are still working on this fix and hopefully we will have some better news for you Nexus 4 owners soon. None of the changes included in 4.2.1 are device specific. So Galaxy Nexus, Nexus 10, Nexus 7 and of course Nexus 4 owners will see improvements from this update.

This newest version does include a few minor fixes. The biggest are a few changes effecting power usage. Some users of the Nexus 4 and 10 have seen their devices turning off when the unplug it from their charger. This should eliminate this problem. There are still a few bugs to be fixed from Android 4.2 when we eventually see Android 4.2.2, but hopefully Google has these in the pipeline and we will see the Bluetooth bug fixed soon.

But issues as major as Bluetooth connectivity in a major Android update do beg a question: Are carriers and OEMs right to delay releases in order to test these devices and keep major software issues from effecting their customers? Obviously a nearly total blockade of updates for devices like the Galaxy Nexus on Verizon is a crying shame. But most carriers and hand set manufactures don’t neglect devices quite that badly. Obviously a middle ground between refusing to update devices months and months after an update is made available, and pushing untested software out to a large audience needs to be found. Of course, if you flash custom ROMs to your phone or tablet like most of us here at Android Headlines do, this isn’t as big of an issue for you. But since most Android users don’t take the time to customize their devices in this way, dependable OTA updates from Google will continue to be a necessity.

Source: AOSP

Category: Android News, Android Rom News

About Doug Scudder ()

Doug has been a fan of Android ever since he got his hands on the OG Droid a few days after it came out. Android and the mobile industry were his favorite hobbies long before he began writing about the mobile industry professionally. Doug currently resides in Chicago and you can find his musings about various TV related topics at
  • Gisela Conte

    is the bluetooth issue affecting all nexus? or was it reported only to some owners? I havent noticed any problem with mine..

    • spinado

      The bug affect some users of all nexus devices

  • Craig White

    affecting, not *effecting*.

    fix the msm_hsic_wakelock issue!

  • Vít Kyselák

    Is it faster than “old” 4.2.1 in action – press power buttom for lock? I wait for my Galaxy Nexus in 4.2.1 version after press the buttom for lock, maybe 0,5second. And it isn´t so comfortable

    • Alexander Maxham

      It’s not a new version of Android, it’s a new chunk of code for Android 4.2.1. Unless you’re running a custom ROM, you won’t see any changes until Android 4.2.2.

  • Momo

    Since this last update i started having a problem connecting to my home wifi ?? any idea

  • Marius Piedallu van Wyk

    Using a standard Nexus 3 car dock on a standard nexus 3 with unmodified Android 4.1 – 4.2.1 crashes the device (it reboots) when you have Ingress (by Google) running.

    This is a known problem (also affects other apps). It is sporadic, but has been around for a long time… I see this as a critical problem and it is sad that it has not been fixed yet.

  • Raúl Gómez C.

    I don’t get it, my Galaxy Nexus has been using Android 4.2.1 for long now, how is this news at all?

    • Shane Perszyk

      it’s just a new version of 4.2.1. think of it as