Holy crap. Brace yourself for some Friday afternoon bad news -- it looks like Google may be washing its hands of all associations with the Verizon Galaxy Nexus. No one knows for sure why El Goog would do this, but all signs point to the fact that it is indeed turning its back on the first ICS phone here in the US.

Update x2: Let's see if we can clear this up a bit, shall we? The basic gist is this: CDMA phones require proprietary code in order for voice and data service to work. This code is handled on the carrier-side of development, not Google's. Therefore, Google can't provide full "support" for these devices since it can't provide the full code. This doesn't mean that Google is dropping the Nexus altogether - it's actually far from that. This update to the developer support pages was simply a means of letting devs know what is going on and will actually have little-to-no effect on the end user.

The good thing about all of this is that we now know what's going on with CDMA devices. Unfortunately, we had to go through a lot of kerfuffle to get to the end result.

Update: Dan Morrill just posted an official word on the state of CDMA devices:

Hello! This is a quick clarification about support for CDMA devices.

For various technical reasons, recent CDMA Android devices implement core telephony functionality in .apk files provided in binary form by the carriers. To function correctly, these .apk files must be signed by the so-called "platform" key. However, when an individual creates a custom build from the AOSP source code, they don't use the same signing key as these CDMA flies were signed with.

The result is that these files don't work properly, and pure AOSP builds running on these devices can't place calls, access mobile data, and so on. Because we aim to make sure that we are as clear as possible about the degree of support that devices have, we updated the docs over at source.android.com to reflect this reality.

We will still make available as many as possible of the closed-source binaries for these devices, and Nexus devices will continue to have unlockable bootloaders. And, of course, GSM/HSPA+ devices are still supported, as are any other devices we're able to support. We've simply updated the documentation to be clearer about the current extent of CDMA support.

We are of course always working to improve support, and we'll keep everyone updated as we make improvements. Thanks as always for your interest in AOSP!

- Dan

The Evidence

A claim this heavy can't be made without some sort of proof, right? Droid-Life has done most of the heavy lifting on that one, and came up with some pretty damning evidence.

First off, if you check out the "Building for devices" section on the Android Development site, you'll notice a list of devices: Maguro, Wingray, Crespo, Passion, Sapphire, and Dream. Those are all the Nexus devices of old, with Maguro being the GSM version of the Galaxy Nexus. Nowhere on that list will you find Toro, the LTE/CDMA version of the GN. It was there just a few days ago according to this cached version of the page.

If you look a little closer, though, you'll notice more discrepancies between the two: not only is the US GN missing, but so is the VZW XOOM (Stingray) and the Sprint Nexus S 4G (Crespo 4G). Those are all CDMA devices. What exactly is Google doing here?

2012-02-03 14h54_39


2012-02-03 14h54_24


From there, if you head over to the "Factory Images for Nexus Devices" page on Google Code, you'll find even more proof. The mysid factory images for Toro are now listed as "archived, for reference only." What the hell does that even mean?

2012-02-03 15h25_45

Of course, this may all just be a misunderstanding and Google could be doing something random, like separating US devices from global devices, or something similar. We're really not 100% sure what to make of all this, but you better believe we'll let you know as soon as more evidence comes to light.