01
Mar
image

As an addendum to the announcement of Google completing AOSP rollout for Android 4.2.2, I wanted to highlight a big milestone for the Nexus program - something that has never been the case before today.

After asking JBQ (not to be confused with JDQ39) a follow-up question, I was able to get some clarity on his earlier post and confirm that as of today, with the release of Android 4.2.2 binaries, we have for the first time ever Nexus devices that have 100% of proprietary binaries available. These devices are the Nexus 4 and the Nexus 7.

Previously, even Nexuses marked as AOSP-supported were missing at least one driver that needed to be ripped out of live devices in order to build a fully working ROM.

image

A snapshot of all binaries available for the Nexus 4 as of today

More Info

Here are some more quotes and info, for those looking for cold, hard facts.

Me, on today's announcement and the fact that the Nexus 4 binaries don't list GSM, which other Nexus devices with mobile networking do:

JBQ, I noticed the Nexus 4 GSM binaries are missing, while all other devices, including the N7 3G have it. Does that mean you can't compile Nexus 4 with telephony support?

JBQ's reply (emphasis mine):

Telephony will definitely work.

I probably forgot to mention those binaries on the download page. It's
also possible that no proprietary binaries are needed to use telephony
on Nexus 4, in which case it wouldn't get mentioned on the list of
proprietary files. I'm not sure which of the two explanations is the
right one. Either way, telephony works.

For Nexus 4 and for Nexus 7, 100% of the proprietary binaries are
available. That had never been the case for other devices at any point
in the past. That way, you can know that 100% of the functionality on
Nexus 4 and Nexus 7 is supposed to work, without restrictions (other
than those caused by bugs).

JBQ

The Building for devices page was also updated today. It lists the state of building completeness for all Nexus devices and once again confirms that the software blobs provided by Google for the Nexus 4 and Nexus 7 result in fully functional hardware:

With the current release, it is possible to build for Nexus 4, Nexus 10, Nexus 7, and for some variants of Galaxy Nexus. The exact level of functionality for each device depends on the availability of the relevant proprietary hardware-specific binaries.

For Nexus 4 and on Nexus 7, all configurations can be used, and all the hardware is functional. Due to hardware differences, do not use 4.1.1 on a Nexus 7 that was originally sold with 4.1.2 or newer.

All configurations of Nexus 10 can be used. On those devices, graphics, audio, Wi-Fi, Bluetooth, camera, NFC, GPS and orientation sensors are functional.

The variants of Galaxy Nexus that can be used are the GSM/HSPA+ configuration "maguro" (only if it was originally sold with a "yakju" or "takju" operating system) and the VZW CDMA/LTE configuration "toro". On those devices, graphics and audio are functional, as well as Wi-Fi, Bluetooth, and access to the respective cellular networks. NFC and the orientation sensors are functional.

The Sprint CDMA/LTE configuration "toroplus" of Galaxy Nexus is supported experimentally, in the master branch only. On that configuration, the cellular network is not functional, and the other peripherals work like they do on "toro".

The Motorola Xoom can be used in the Wi-Fi configuration "wingray" sold in the USA, with Android 4.1.2. Graphics and audio are functional as well as Wi-Fi and Bluetooth and the orientation sensors.

All configurations of Nexus S and Nexus S 4G can be used with Android 4.1.2. On those devices all the hardware is functional.

So, there you have it. Truly good news for Android, the Android community, and the Nexus program.

I hereby nominate today as the new official Nexus Day. Who's with me?

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://www.Nave360.com Sebastian Gorgon

    Feel like such a noob but how different is this to what we had in the past? Nexus phones always had amazing rom support and everything always worked, what does this change in terms of custom roms?

    • http://k3rnel.net Juan Rodriguez

      Previously, ROM Builders had to "extract" binary files from an actual, functional device in order to compile a ROM, because these binaries could not legally be distributed as part of the source.
      These binaries are now available to make things easier for those that do build ROMs.

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

        From what I understand, this is exactly right. I tried to explain this point in the story.

        • http://k3rnel.net Juan Rodriguez

          You did convey it, but I happen to know from personal experience building and messing around the Android source :-)

      • http://www.Nave360.com Sebastian Gorgon

        Ah i see, but was there a disadvantage using extracted binaries?

        • http://k3rnel.net Juan Rodriguez

          Not really. If you're gonna build a ROM, you most likely want to test that it works, and you need a device for that. Binaries can also be extracted from any "rom.zip" you get off xda, so an actual device isn't really needed.

          I guess the good news is that Google cleared a legal hurdle. One that wasn't really in the way for Rom Devs, but a hurdle nonetheless. :-)

          • http://www.Nave360.com Sebastian Gorgon

            Thanks for explaining all of this, Nexus day it is indeed =)

          • Larizard

            but what about Verizon and CDMA binaries?

            Never. :/

          • http://twitter.com/trlovejoy trlovejoy

            Yes, what does this mean to toro users? JBQ's comments on that "seems" positive - are they?

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

    edit: nevermind

  • http://tablified.com Ayman Suleiman

    What about the Nexus 10? Or does this only apply to devices with a radio? i.e. Nexus 4 and Nexus 7 3G.

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

      From what I can tell, the Nexus 10 has component(s) that Google is not allowed to distribute. I'm not sure what the full set is, but comparing to others, it looks like Media, DRM, Camera, Sensors, and possibly more.

      • XBIRDIE98

        To quote the original 4.2 release (the one without tilapia or mako) on the N10: (see http://goo.gl/RBsqZ )

        "-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."

        But then, the page that you guys reference says "On those devices, graphics, audio, Wi-Fi, Bluetooth, camera, NFC, GPS and orientation sensors are functional." and that only the N4 and N7 have full support. These seem to contradict one another, so there must be one or two little proprietary things that they haven't gotten out yet.

    • mihaits

      it's beacause fuck samsung and their closed-as-fuck-source exynos

  • Cuvis

    This is a great milestone on the road to a truly open phone.

    Now we just need source for those drivers. Pretty please?

  • XBIRDIE98

    It is interesting to note that the Nexus S is described as fully functional on 4.1.2 as well, but then how does this milestone not apply to it? An oversight, perhaps?

    • SergioHC

      Nexus S was updated to 4.1.2 time ago, but it is stuck there. I used one for a long time, and 4.1.2 was slow on it, so upgrading beyond 4.1.2 may be non practical, and hardware not well supported.

  • Faust

    WOO!!! Finally I have no worries about my N4 support anymore. This baby will be able to live through the ages even after Google drops support for it 4+ years later!

  • Darren C B

    I have no clue what this post is about,no clue,is this some geeky thing

  • FrogdogSweden

    This really makes me all warm inside.. Yeah, I'm a 100% geek and I like it :-)

  • Venkat Renuka Prasad Sahukara

    So, can it be known whether the Nexus 7 can have a HDMI adapter?

Quantcast