13
Nov
http://www.androidpolice.com/wp-content/uploads/2012/07/AOSP_Bugless_Beast_thumb.png
Last Updated: November 14th, 2012

The new Nexus devices just went live, and, as promised, Google has simultaneously started pushing the code for the latest iteration of our favorite mobile OS - Android 4.2 Jelly Bean - to the Android Open Source Project. Jean-Baptiste Queru, chief Android release engineer, announced the news via a post to the Android Building group.

Update 11:22am: Android 4.2 source just finished replicating to AOSP. "The platform source files for 4.2 have finished replicating, you can now sync." -JBQ

The build number is JOP40C, while the AOSP tags is android-4.2_r1.

The Nexus 10 is now the most compatible AOSP device with everything but the GPU code open sourced. It's the most open flagship Android device ever, according to Google. On the other hand, neither the Nexus 4 nor the Nexus 7 3G is currently supported, presumably due to lack of licensing rights for the GSM stack.

Unfortunately, it looks like it's the end of the road for the Nexus S and the XOOM - these devices will not be supported in AOSP past Android 4.1.2. We've reached out to Google to clarify this point. Update: JBQ's response is "I can't comment about the future of Nexus S and Xoom, sorry."

Google also released the factory images for several Android 4.2 devices, including the Nexus 4, Nexus 7, Nexus 10, and the takju variant of the Galaxy Nexus.

If all goes well, we should start seeing Android 4.2 in our favorite AOSP-based ROMs (looking at you, CyanogenMod, AOKP, and others) very soon - possibly even tonight.

Happy Nexus day, folks!

Good news everyone!

-The source code for 4.2 is being pushed to AOSP right now. Look for it under the name "android-4.2_r1" once the replication completes. The matching development branch (for CTS contributions) is jb-mr1-dev, and all the changes are merged into the master branch where platform contributions are accepted.

-Nexus 10 is now the best choice for AOSP work on 4.2. Everything except the GPU code is Open Source, and the only proprietary binaries besides the GPU libraries are firmware files that get loaded into the various peripheral chips. No flagship device so far has been so open, and no flagship device so far has had that level of AOSP support at launch.

-Nexus 7 3G isn't supported. We haven't been able to license the GSM stack for AOSP yet, and without the GSM stack this device doesn't do more than a plain Nexus 7.

-If AOSP starts pointing toward Nexus 4, you are having a bad problem, and you will not go to space today (i.e.: there is nothing in AOSP related to Nexus 4).

-Factory images for the "takju" Galaxy Nexus as well as Nexus 7 (both variants), Nexus 4 and Nexus 10 are available at
https://developers.google.com/android/nexus/images

-Proprietary binaries to run AOSP on Galaxy Nexus (maguro, toro and toroplus), Nexus 7 (grouper) and Nexus 10 (manta) are available at https://developers.google.com/android/nexus/drivers

-There is no support for 4.2 on Nexus S and Xoom. Those devices should continue using 4.1.2.

JBQ

PS: don't reply to this thread if you have specific questions. Start
new threads instead.

PPS: no ETAs for OTAs.

Source: Android Building

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/navjotbatra Navjot

    Does this mean no 4.2 for Nexus S?

    • http://www.facebook.com/profile.php?id=1503310639 Kree Terry

      Thats what i got from it as well

      • http://twitter.com/navjotbatra Navjot

        kinda sucks. 4.2 doesn't bring anything new to the table that crespo wouldn't be able to handle. They probably don't want to just because 4.x doesn't run as smoothly on our devices as Gingerbread used to. Good thing I'm getting a N4 though.

        • http://www.facebook.com/profile.php?id=1503310639 Kree Terry

          yea i think that its not that they couldnt handle it its just google knows how slow things are on jelly bean as is and the extra features must have just pushed it over the edge. im sure some custom roms will prob bring it up to 4.2 with reasonable performance.

    • http://twitter.com/xplodwild Guillaume

      For now (I guess). But I'll come eventually later.

    • http://richworks.in Richie

      not officially at least... cyanogenmod to the rescue

  • skitchbeatz

    Consolation prize for the clusterf**k that was the Nexus4/10 launch?

    • http://www.facebook.com/mr.ramsamy Sebastien Ramsamy

      maybe...but it's not enough!!!!

    • Sean

      What clusterfuck? they've sold out!

      • Alex Luckett

        Precisely.

  • mattdonders

    YES, YES, YES, YES, YES!

  • Ken Gorab

    Alright, Cyanogenmod, it's up to you guys now!

  • theentropic

    OK Pete, Time to work your magic and get a Bugless Beast release ready to go!

  • Swapnil Chitnis

    So are both Nexus S and Motorola Xoom retired :(

  • DaveNull

    So, turned out that Nexus 4 is not an AOSP device. :o What a huge disappointment.

    I was actually waiting for this as it would have been the first time that there is AOSP supported devices on every major platform (TI OMAP, Tegra, Qualcomm, Exynos). Is Qualcomm to blame for this?

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

      I'm not completely sure, but I don't think that's what it means. That would a complete and utter fail on Google's part.

      Need to do more research on this.

    • http://codytoombs.wordpress.com/ Cody Toombs

      It's better to say that the Nexus 4 is not an AOSP-supported device yet. This is likely to be something that will be resolved in a few weeks and probably has everything to do with the slow-as-molasses rate that lawyers work out licensing. It would have been great if these details had been worked out sooner, but I'm pretty sure the Nexus 4 and Android 4.2 were pretty hastily arranged, and a side effect of that was that this particular detail had to be tabled until everything else was solidly worked out.

    • Alvin Brinson

      I wouldn't be surprised if it's LG screwing things up. LG just can't seem to license or update ANYTHING reliably. Why would we expect them to suddenly learn how when they get a Nexus? For example, when they updated the g2x from 2.2 to 2.3, they lost the license to the camera software they'd included! So the special camera that some people bought the phone based on became the stock 2.3 camera after the update.

      LG has a history of pulling this kind of stuff.

  • Alchemy08

    Today is the day the Nexus S dies..... :(

    • Simon Belmont

      Old Androids don't die. They just get a new lease on life with developer community support.

      The support for the Nexus S has been very strong. It will continue I'm sure.

      • Alchemy08

        Your right. In the words of Theon Greyjoy "What Is Dead May Never Die!!!"

        • ASOIAF

          But rises again, harder and stronger

      • Dale

        Agreed. I still have a mytouch. It's not dead.

  • Davy Jones

    Lol at 11GB. What is that, 2 compressed movies at 1080p?

    • Davy Jones

      whoops, wrong article. please delete

      • superlaser

        Lol

  • Ian Peterson

    So is the nexus 7 getting 4.2 or not?

  • http://twitter.com/psych2L Joseph Lee

    CM11 is coming up!

    • Simon Belmont

      Will it really be CM11? It may be a minor version iteration, but it didn't change the code name (Jelly Bean). CyanogenMod has historically gone by the corresponding number of the letter. In this case 'J' for Jelly Bean is the tenth letter.

      My guess is it will just be merged into the current CM10. CM11 will probably be Key Lime Pie or whatever sweet it turns out to be.

      • http://codytoombs.wordpress.com/ Cody Toombs

        I can't speak for CM, nor can I find any statement from them to confirm this, but a few friends have told me that they had read it will be called CM10.1. That's what they did with the multiple Gingerbread updates and CM7, so it makes a lot of sense. Bumping up to CM11 for this update just felt somehow wrong to me too.

        • Simon Belmont

          Yeah. This I can get on board with. The multiple minor versions of CM7 were actually features back-ported from ICS. At least CM7.2 DEFINITELY was.

          Jumping to CM11 goes against their normal convention of using the number of the letter in the alphabet to represent the CM build's version. Cheers.

          • http://codytoombs.wordpress.com/ Cody Toombs

            Good point, I'd completely forgotten about the Number Letter parity thing they've got going on.

    • http://www.facebook.com/YAYSAVERGN Eric James Salcido

      Actually, no. Cyanogenmod only makes new versions for a new codename from Android. So CM11 will probably be Key Lime Pie, which also is the 11th letter of the alphabet. 4.2 will be merged into CM10 stable.

      • Simon Belmont

        Exactly. You said it perfectly.

        CyanogenMod's version convention is simple. It works well, too.

  • http://twitter.com/andrewscorgie Andrew Scorgie

    Would be good if they could fix the bugs in 4.1.2 for the Nexus S, ever since that update it has suffered Lag issues and random reboots when connected to the USB port on my car stereo, was rock solid stable on 4.1.1 and 4.0.x

    • J_Grouchy

      Yeah...each update seems to put more strain on my NS4G battery than the one before. I'm at the point where I am lucky to get to mid-afternoon without having to recharge.

  • donttrollmepeople

    happy nexus day indeed

  • http://btwnworlds.tumblr.com/ Lou G

    So..I should the update for my 8gb nexus 7 soon? *crosses fingers*

  • kitti

    thats the reason why i bought a nexus device. i know that after 2 years the device isnt supported anymore but its easily rootable and its quite simple to install roms like cyanogenmod. its not the end of my nexus s, its just a new start. android devices never die because of the huge community.

  • OrdinaryAmerican

    What happens when you're not a geek, but rather a geezer who wants the latest JB? Is there a place that specializes in jail-breaking Android phones? Is this something Best Buy would do, or do I have to go down a dark alley looking for a hacker in a Guy Fawkes mask?
    Thanks, any advice would be greatly appreciated.

    • Sootie

      Look at the cyanogen mod wiki page mate there are step by step instructions on how to gain root access (jailbreak) and install the latest cyanogen mod version. As long as your device is supported then you will have a fully up to date os no matter the phone.

  • GazaIan

    WOOOOOOOOOO

  • surka

    why nexus s not upgrade??!!

  • http://www.facebook.com/people/John-Charitos/536042829 John Charitos

    got it on my galaxy nexus, almost bricked it but damn was worth it !

  • http://twitter.com/freeantiviruses john reily

    4.2 sucks on the nexus 7. Firefox Broke etc etc. I think its aggressive memory management. And being a lousy "developer", why so many changes?

  • gnexus

    Hey guys! But the geotag i con in camera app ,notte appear!!!!!

  • Angela Snyder

    So I got the 4.2-JOP40C upgrade yesterday morning, Nov 14, and now my battery keeps dying. It doesn't even last till 12-noon. Recharging all day. Solutions?!?!?! The battery was lasting all day till I went to bed at night, before the update. I like what I see from the update, but I want my battery to last and allow me to have my phone on me throughout the day. Help!?!?!

Quantcast