In a post to Google's Android Building group today, Jean-Baptiste Queru once again acted as the bearer of good tidings for developers and tweakers everywhere, announcing that "a new set of proprietary binaries for Jelly Bean are available."

The new batch of binaries includes those of the Nexus S and Nexus S 4G (Crespo and Crespo4G respectively), the latter of which we just recently saw added into the AOSP fold.

The set also includes updates to the both the GSM Galaxy Nexus (maguro), and Verizon's Galaxy Nexus (toro, which itself is ever so close to full AOSP support).

Conspicuously absent from the party is Sprint's variant of the Galaxy Nexus, but there's no surprise there.

JBQ also noted that the Nexus 7 (grouper) binaries have gone unchanged since JRO03C but are "suitable for JRO03H."


Despite the absence of Sprint's Galaxy Nexus, it's nice to see addition of Nexus S (4G) and Xoom binaries added, and the other Nexi kept punctually up-to-date. Those interested can see JBQ's original post or grab a fresh handful of code from the appropriate link below.

Source: Android Building, Google Developer Nexus Binaries

Liam Spradlin
Liam loves Android, design, user experience, and travel. He doesn't love ill-proportioned letter forms, advertisements made entirely of stock photography, and writing biographical snippets.

  • http://twitter.com/alxalejandro393 Alex Esparza-Sandy

    It's kind of cool seeing all of these updates, keeps adding fuel to all the development that's going on!

  • ModXMV

    So why exactly is the Sprint version not included?

  • br_hermon

    I'm confused... I thought that Peter Alfonso updated his Bugless Beast with JRO03H over a week ago now? Can someone confirm this?

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

      The binaries were likely pulled from OTAs or previous versions, or some place I'm not sure about.

  • Mark

    So when will the official 4.1.1 update come to the Verizon Galaxy Nexus since it does have AOSP support now.... This is just getting out of hand!!

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

      Official? Whenever Verizon gets its fat ass around to it, which may be months.

      • Mark

        That's the mistake on Google s part.. They offer it as a “Nexus" device but they arent in charge of the updates. A bunch of false advertisement there... Some Nexus device that turned out to be. Google shouldn't haven't given Verizon any control over the updates.

      • Mark

        I had a very I interesting email chat with a Verizon representative in regards to the who update process. I also informed them they didn't deserve the right to sell the Galaxy Nexus. They just go off on a rant about their 4G network being amazing.

    • flosserelli

      Don't hold your breath waiting for the official 4.1.1. Just grab a custom 4.1.1 rom from xda. That's why you bought a Nexus, right?

      • Mark

        It is but when I go searching I only come across the ROMs that have issues with WiFi or GPS.

      • fixxmyhead

        NO i got one for my wife for the DIRECT updates cuz she doesnt know about phone stuff (but i did root it and unlocked the bootloader just for fun) but she has a real one not that fake verizon one

      • bevardimusg

        Those rooms all have issues! Even the most supposedly stable ones had serious GPS issues to the point where I got fed up and went back to 4.0.4. And the REASON I got a nexus was for the pure google experience

        • Snake

          Yeah I just went back to 4.0.4 because the Vicious ROM starting causing me some issues. I went to reboot it and the OS wouldn't come back up. So I guess I am back to playing the waiting game until a better ROM comes out.

  • gnexguy

    So what exactly does the updated binaries mean? Are they just updated drivers? Or what

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


      • Tyler Chappell

        Ah ok thats what I thought, so basically, it just allows all the developers to bake the correct drivers into their custom ROMs to ensure that all those particular binaries (LTE/CDMA, Wifi, Bluetooth, Graphics, and accelerometer) are all functioning correctly right? My dad is having bluetooth issues on his Verizon GNex with the Vicious 4.1.1 ROM, apparently his bluetooth range is only like 5 feet and he uses his earpiece a lot so I need to find a ROM with great bluetooth, thus I will probably try bugless beast this weekend.

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

          That is exactly right, though I'm not sure it will fix your dad's issues. There could be many things going wrong.

          • Tyler Chappell

            Yeah, sometimes it is hard to narrow things like that down, though Gummy 1.2 running 4.0.4 was working great for him as far as bluetooth connectivity.

  • Tee

    I've been running JRO03H in my SGS Classic for a week now. Thanks to Elitemovil at XDA.

  • skinien

    Now if I only knew what to do with them...

  • Guy

    Anybody have a link for a guide?

    • Guy

      For Nexus S 4g sprint