After Android 4.2.2 update, entire Nexus line gets full AOSP support


Now that the Android 4.2.2 update is on the books, Google has taken to updating their codebase of android Open Source Project binaries, bringing the latest version to all currently supported Nexus devices. This includes the previously neglected Nexus 4 and Nexus 7 3G, as well as Verizon’s version of the Galaxy Nexus.

The absence of full AOSP support for certain Nexus models was a bit perplexing, especial the Nexus 4. But Google has been working their way toward this end. These binary files provide hardware-specfic drivers necessary for running a complete and functional AOSP build on any Nexus device. The latest build version is JDQ39 and can be found at the source link below.

[via Google Developers]

Kevin Krause
Pretty soon you'll know a lot about Kevin because his biography will actually be filled in!

Samsung, Chillingo launch 100% Indie initiative

Previous article

Clockworkmod Superuser now available in the Google Play Store

Next article

You may also like


  1. entire nexus line != currently supported nexus line

  2. include cdma?

    1. Says it right in the article. Galaxy nexus is cdma.

      This includes the previously neglected Nexus 4 and Nexus 7 3G, as well as Verizon’s version of the Galaxy Nexus.

    2. that’s what it says, yea

  3. Uhhhh… toroplus is still listed at the bottom as being “experimental”, and isn’t even listed in the Contents section at the top.

    1. Verizon > Sprint :)

  4. I’m not a coder or a hacker or a subscriber to XDA.

    Could someone please explain what all this means and what relevance does this have to the lay user? I’m on a Nexus 4 with 4.2.2.

    1. If your not a developer or a custom rom user, it means nothing to you.

    2. This essentially means Google has brought the source code up-to-date with all of their supported Nexus products (GNex, VZW GNex, N7, N10, N4). Now all of their sources are up-to-date and supported in AOSP (Android Open Source Project):

      For example, this will be good for VZW Gnex users who received poor support from Verizon from day one. It’ll help CyanogenMod and similar efforts a lot.

      This actually makes me want to buy a used VZW Gnex as my next phone (since i’m stuck on Verizon), instead of going iPhone 5 or whatever my company gives me this spring.

    3. Best way I can describe it, anything that is developed for 1 Nexus device should work across all Nexus devices. The framework and drivers have been standardized.

    4. It means my stock Verizon GNex will finally be getting the latest Android 4.2.2 update soon.

      1. Do you mean update or ROM? This is still nowhere near a guarantee that Big Dread will bother updating a phone that they’ve already EOL’d. In fact, chances are pretty good that they won’t (given their track record). I’m looking forward to a nice, stable AOSP build (or maybe AOKP) coming from this, though.

        EDIT: I’m an uninformed dolt. Carry on.

        1. You mean the update that is already confirmed and in tester’s hands? “Eye4Detail” … LOL

          1. Holy crap! It doesn’t pay to take a few days off from tech news. I rescind my previous statement (though I did punch it into Google first to be sure it wasn’t “confirmed” by a rumor…it is VZW after all).

            Thanks for the correction and the great news.

    5. I think it means that EVERY version of the Nexus 4, Nexus 7, Nexus 10, and Nexus Galaxy have official Google support (whereas the Verizon Nexus Galaxy was Verizon-mandated before this annoucement).

  5. And yet we still wait… How long? Well, I have just two-hundred-and-eighty-five days left… http://itsalmo.st/#timetoditchvzw

Leave a reply

Your email address will not be published. Required fields are marked *

More in Handsets