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). Note: There could be other changes in closed-source components.

JOP40C (4.2_r1) to JOP40D (4.2.1_r1) AOSP changelog

This only includes the Android Open Source Project changes and does not include any changes in any proprietary components included by Google or any hardware manufacturer. The raw log was generated using a modified version of this script written by JBQ.

Project: platform/build

d4382dd : bump version to 4.2.1
476750c : JOP40D

Project: platform/external/bluetooth/bluedroid

0d15318 : Add HID gamepad/joystick as supported HID devices

Project: platform/frameworks/base

b361b30 : Revert "NumberPicker should adjust min and max when displayed values are set." (a.k.a. Santa is back)
cc2e849 : Notification vibration improvements: [DO NOT MERGE]

And there you have it - Android 4.2.1 is probably one of the most minor, yet necessary, updates ever pushed out by Google in a point release. Another mystery solved, now we can concentrate on finally getting that Nexus 4 ordered, this time, hopefully, without Google's servers melting down.

Source: Al Sutton

Artem Russakovskii
Artem is a die-hard Android fan, passionate tech blogger, obsessive-compulsive editor, bug hunting programmer, and the founder of Android Police.
Most of the time, you will find Artem either hacking away at code or thinking of the next 15 blog posts.

  • Sven

    Bummer. Was hoping for stability fixes...

    • Justin W

      Same here. My N10 has randomly rebooted a few times, although it's not that bad because it doesn't do it when I'm actively using it (only when it's locked for a period of time).

      • MrJigolo

        THIS. Why the hell hasn't Google addressed this? My Nexus 10 reboots all the time while in idle. It's really annoying and that's a good way to kill the battery. I wish someone from AndroidPolice would show Google some of these problems.

        • Mario

          Have you tried a factory reset? Similar thing was happening to people going to from 4.1 to 4.2 on the N7, but a factory reset fixed it. Could also be some of your old apps not playing well with 4.2, since the N10 comes stock with 4.2, no?

          • http://twitter.com/Alucard291 Alexey

            Factory reset doesn't fix random reboots on nexus 7 wth are you talking about lol?

        • Bamaloosa

          My nexus 4 has never rebooted. Ever best phone on the market. It's probably an app that you have installed that's causing your reboots.

    • Kenny O

      stability fixes for what devices? I have zero stability issues with the N4 or N7......

      • http://www.afzaln.com/ CuriousCursor

        Well the only issue I have is that sometimes I press the power button when device is sleeping and the screen lights up but nothing is shown.

        Had that more than 6 times today.

      • Trey

        I can name a couple.

        On my Nexus 7, the touchscreen is unresponsive when plugged into the charger. However, putting it to sleep and waking it temporarily brings it back to life. This has been an issue from the beginning.

        Secondly, I noticed a lot of skipping in Google Music when using Bluetooth. However, disabling then reenabling Bluetooth seems too temporarily correct that issue. This issue only came about after upgrading to 4.2.

        Just my 2 cents.

        • http://twitter.com/Alucard291 Alexey

          Also you can try plugging in an external kb and pressing ctrl + space that may amuse you

        • http://twitter.com/TiMthisIS Tim

          My N4 screen behaved a bit flaky on charger too before I got the last two updates. Mostly when I tried to two finger the settings shade from the top. It almost never worked, dropped the sensing and then launched whatever my finger was over when it began sensing again. Not so much a problem with the standard one finger shade. It's seemed to be a multi tough issue. I'm on 4.2.1 now

      • Simon Belmont

        I got my N7 the DAY before 4.2 dropped. The UI was smoother in 4.1 and battery drain was better.

        4.2 made the UI a bit sluggish in comparison to 4.1. Also, the battery definitely drains (and charges slower) faster. I've also encountered difficulties with my Bluetooth speaker, such as bad audio, etc. Oh well, hopefully 4.2.2 fixes this stuff.

  • http://kennydude.me/ Joe Simpson

    Wow, the diff for the December bug-fix is tiny! :D

  • http://www.facebook.com/vanhouse David VanHouse

    Does this mean working OTG?

  • http://twitter.com/valenzine Valentín Muro

    Is it possible that this also fixes our issues with Gmail's new messages vibrating in disregard of our settings?

  • Nelson

    What's with the commit saying [DO NOT MERGE]? Am I misinterpreting this, or didn't they merge it if it showed up in the changelog?

    • akellar

      That comment is all over the place in AOSP.

    • blunden

      Someone from Google explained it in some comment on Google+. It might've been Adam Powell. Unfortunately I don't remember specifically what he said but I think it was related to how to handle the commit in their internal tree or something like that. Regardless, it's quite common in AOSP for new platform releases and it is not related to any form of mistake.

  • Sven79

    I sure wish they'd have shipped my "pending"order before taking new orders

  • Faiz Visram

    Anyone thinking that the new Bluetooth compatibility might fix native support for the Wii controller?

    • Jared Morgan

      It fixes support for apps like USB/BT Joystick Center apparently.

  • ericl5112

    Did they also remove the LTE option from the N4? I expect that to go very soon.

    • http://www.androidpolice.com/ Artem Russakovskii

      They didn't.

    • Abhijeet Mishra

      That option is actually present in all Android devices afaik, so Google probably won't be removing it. But who knows, maybe they will.

      • ericl5112

        They will remove it almost guaranteed. As it stands, it is illegal to sell it as is. They do not have FCC approval to sell an LTE device in the N4.

        • http://twitter.com/RvLeshrac RvLeshrac

          As long as the LTE device in the N4 is legal to be sold, the N4 is legal as a whole. Do you work for IBM, perchance? They seem to have the same misguided opinion of the law.

          • ericl5112

            Huh? So that's why you never see a device getting FCC certification only modems. Oh wait...

            I like that you attempt to have wit, but there is a bit of missing logic there. Not to mention, people more knowledgeable on the topic share the opinion of questionable legality.

          • http://twitter.com/RvLeshrac RvLeshrac

            A functioning LTE radio would not affect the device's certification, as it was approved with the device present. They didn't have the device approved, then solder on the LTE radio.

  • Abhijeet Mishra

    Basically, Google wanted to give December back to the people before the month starts, hence this minor update. For those hoping for stability and performance improvements, well, maybe next time. :/

  • Guest

    Just noticed that the Jelly Bean isn't smiling anymore if go to about phone :(

    • http://www.afzaln.com/ CuriousCursor

      Yes it is!

  • Floss

    Well that's lame. Missing december only in a few specific cases was probably the least important bug in 4.2, yet the only one which was fixed :(

  • GregMG

    Nothing on my N7 yet.

  • Pete

    Nexus 4 isnt supported yet in AOSP so fixes specific to it likely won't be mentioned. There was a patch in the OTA for NFC that is larger than the other patch files. I notice Mifare classic 1k tags are nownable to be read and wrtten.

  • Rene Christensen Dokbua

    Bummer. I had hoped for a fix for the low volume problem.

  • thargic

    Factory re-set fixed my random booting problem

  • Fredrik

    I had a lot o crashes and reboots. Reverting to using only one user account removed most of them for me. The multi user support seems really buggy.

    • RedColoredGlasses

      This was the same for me. When I deleted the second user account, much of the lag went away. I still get the occasional reboot, but I can deal with that. (Nexus 7 User BTW)

  • aerialie

    I got this update and can now watch videos that were previously unavailable to me on Nexus 7.

  • Marc

    Has voice recognition improved for dialing? That really needed some work.