Earlier today, Google started pushing some new open source code to AOSP (Android Open Source Project) marked with 2 new tags: android-4.2.2_r1.1 and android-4.2.2_r1.2. The build number corresponding to the 4.2.2_r1.2 release is JDQ39E.


The dates you see here are commit dates, not dates the commits were made public (which is today, April 17th 2013)

What's New?

After weeding out the changes from the commit logs, it looks like all of them are, as expected, very minor. We've seen these _r1.X releases before, and the last one didn't fix much at all.

Here are the aforementioned changes between 4.2.2's tags 4.2.2_r1 (JDQ39) and 4.2.2_r1.2 (JDQ39E). Unless the push is still going, I think this is everything (everything that has its source in the open anyway), but if you spot something I didn't, please drop a note below. The first list is compact, while the 2nd expands on each commit.

Note: lge/mako is the Nexus 4.

Oh, and another fun thing we noticed (thanks, @Bluewall!) is this older commit message in platform/build/CleanSpec.mk by Dianne Hackborn (<3) from a few months ago:

Look, up in the sky! It's a bird! It's a plane! It's Android 4.2 API 17!

And a code comment a little lower:



Source: AOSP (1) (2)

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.

  • http://twitter.com/redbullcat Phil Oakley

    Is there any fix for the flickering music controls on the lockscreen? Happens every time I play music.

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


    • Damon

      Install Gentoo

    • Death Becomes Me

      See if you have maximize lockscreen widgets in your settings checked.

      • http://twitter.com/redbullcat Phil Oakley

        Just checked and I don't. Does enabling them 'fix' the issue?

        • Death Becomes Me

          No. That's the only time I notice it happening with the music widget maximized. Maybe toggle it on and off to see if it fixes it.

          • http://twitter.com/redbullcat Phil Oakley

            Righto. Thanks!

  • Alex Mocaby

    So, I assume this is just them "fully" fixing JB before they move on to KLP?

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

      I don't know if there's going to be a bigger JB release, because all the _r1.X ones are super tiny. They have a whole lot more to fix, though maybe those fixes will roll out in K*-whatever after all.

      • Freak4Dell

        Would it even matter if they did? It's not like manufacturers are going to push out an update just because Google updated a few lines in the JB code. Any Nexus devices that would get the minor JB update would get the K-whatever update, too, so that's pointless as well.

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

          It would for at least Nexus users.

          • Angel Penabad

            I'm not sure but I think that even among Nexus users, only those using custom roms (that are built from this source) will receive this changes. I don't think stock users will get OTA, as it happened with 4.2.1 r.1.2 (JOP40G).

            Poor update, the only thing I like about it is that few weeks after de JOP40G update we got 4.2.2 (JDQ39) which was a great update in my opinion (battery life increased a lot).

    • http://profiles.google.com/tim.glaser Tim Glaser

      If you can call AOSP not supporting AVRCP 1.3+ [meta data over bluetooth] fixed. :)

  • Justin Winker

    So... Can you write this up in normal english for us? :)

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

      Sure. Here goes.

      "Google didn't really push out anything particularly useful."

      • Justin Winker

        Haha, thanks!

  • http://twitter.com/expertontech Tylar Overturf

    Guys this was only for mako and thats it. Nothing changed for anything else. They were mako specific.

  • http://twitter.com/A2Eric Eric S

    New radios would be nice. My signal goes from -95dBm to -105dBM every few seconds.

    • brkshr

      Are you on T-Mobile?

    • c0Ld

      I have that issue sitting in my office on an MVNO, but I've always just chalked it up to AT&T's network sucking. It'll be fine on my desk and drop it 100% if my phone is in my pocket. Infuriating.

  • MrJigolo

    Ah yis. This better fix Nexus 10 random reboots. Still getting them while the tablet is in idle. It's annoying as hell.

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

      Not a chance.

    • Patrick Cedrowski

      I had the same issue. Call Google and get yourself a new Nexus 10. The newer models seem to have fixed the random reboots.

      • Geoffrey Pursell

        What number did you call, and what did they tell you, if you don't mind my asking? And how often did your tablet reboot?

      • MrJigolo

        Good to know thanks. I might wait out Google I/O to see if that version messes things up even more or what not.

  • Joshua Percell

    So... Does this mean an update is in the works? Not an android version update, obviously, as it is only for the N4, and would cause fragmentation among all nexus devices which defeats the purpose of Nexus. But a very minor update?

    • Sam Hollis

      Yes, a software update is forthcoming, similar to how other phones receive updates to the software without updating the actual android version.

      • Joshua Percell

        Awesome! I love updates!

  • Josh Flowers

    For the love of crumb cake I wish this fixed the Wi-Fi bug on my N10 that's rampant in the community.

  • http://twitter.com/Mo3tasm Mo3tasm

    so people in Google are still coding....

  • http://www.facebook.com/a1exus Dmitry Chorine

    How is that going work w/ Verizon?

    • Joshua Percell

      Nexus 4 isn't available on VZW, so not sure what you mean...

  • http://www.facebook.com/nicole.dallal.9 Nicole Dallal

    Huh. My RazrM picks and changes its default ringtone ON ITS OWN, regardless of what I do.

  • Magneira

    Maybe this implements the qualcomm bug that's drawing the nexus 4 battery... no? let s hope so!

  • Matthew Fry

    Crippling Nexus 10 bugs? Nah not important.