Hi, all! Thanks for all the questions. Here’s a quick omnibus to answer the
questions folks have asked...
First, just to be clear this change is only related to AOSP support for
these devices -- that is, personal custom builds. These are obviously still
officially-supported Nexus devices for everyday use, they will receive
official software updates, and so on. Similarly, these are still
fully-supported development devices for app developers.
Second, as I noted at the top of the thread, Nexus devices will still have
unlocked bootloaders, and we’ll continue to make available as many of the
closed-source binaries as we can. CDMA support in AOSP has always been more
challenging than GSM, and this change is a reflection of that reality.
On that topic, here’s a quick clarification on the core issue. Every device
has a number of closed-source software packages included on it. Though
Google distributes some of these binaries for Nexus devices for use with
AOSP, Google does not own the software. Rather, this software is variously
owned by the device manufacturer, the carrier, and their suppliers. We try
to get distribution rights for as many of these binaries as possible, but
in some cases it is difficult or impossible to obtain these rights. (CDMA
specifically has a tricky history of intellectual property.) Combined with
the technical issues of needing to sign the apks correctly, this has
prevented us from obtaining the distribution rights we need to support
these devices in AOSP.
Finally, we will of course continue to work on improving support. If we can
resolve these issues, we’ll certainly restore CDMA support to AOSP. In the
meantime, we’ve updated our docs to be more accurate about the degree of
*I hope that answers your questions! For those of you with more technical
questions, JBQ’s posted with more gory technical details over on