Samsung Galaxy Nexus for Verizon no longer listed on Google’s dev support pages [Update]

This is an interesting turn of events, if you ask us. While the Google Wallet situation between Google and Verizon seemed to delay the launch of the device back in December, it seemed to have died down after the official launch. But now it looks like it may be the reason why there’s a huge change of events happening over at Google’s developer support pages.

It’s been revealed that the LTE-based version of the device has been removed from the Nexus program. That’s right, the Galaxy Nexus from Verizon is no longer a “Nexus” device. Specifically, if you dig into the Android Open Source Project listing, you won’t find the LTE Galaxy Nexus, which is codenamed “toro.” There is a lot of belief that the Google Wallet situation, which recently became available as a public download for the GSM-based Galaxy Nexus from the Android Market, is the root cause of this.

To bolster this belief, The Verge reached out to Google, without specifically referencing Google Wallet, and this is the response they received:

“Every day, Android developers openly distribute applications via Android Market. Google is also a developer within this ecosystem and we want to offer the apps we develop such as Google Wallet, so people have access to the full range of functionality offered by the platform.”

So, take that for what you will.

Update: Well, it looks like the brouhaha was for nothing. Here’s a statement found on the Google Groups page for Android Contributors:

“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 atsource.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.”

So, while Google clarifies things, the rest of the world watches with eagle eyes.

via The Verge

Tags: , , , , , , , , , ,