Go Back   Android Forums > Android Community > The Lounge > Google

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

test: Reply
 
LinkBack Thread Tools
Old February 5th, 2012, 07:31 AM   #1 (permalink)
Senior Member
Thread Author (OP)
 
zuben el genub's Avatar
 
Join Date: Jan 2011
Posts: 4,762
 
Device(s): Nexus 4, Galaxy S 4G, Nexus S
Carrier: Not Provided

Thanks: 51
Thanked 868 Times in 698 Posts
Default Whatinell is this?

Google Pulls Support For CDMA Devices - Slashdot

Are we starting another major spat?

zuben el genub is offline  
Reply With Quote
sponsored links
Old February 7th, 2012, 06:37 PM   #2 (permalink)
Over Macho Grande?
 
alostpacket's Avatar
 
Join Date: Nov 2009
Location: NY
Posts: 7,873
 
Device(s): GlassXE, MotoX, N5, N4, N7'12, GNex, N1, SGT10.1, Revue, Xoom, Eris, OG Droid
Carrier: TMO

Thanks: 4,582
Thanked 3,563 Times in 1,522 Posts
Default

Not exactly:

[UPDATE: Google responds] Verizon Galaxy Nexus, other CDMA devices, no longer listed with Google developer support


https://groups.google.com/forum/?fromgroups#!topic/android-contrib/phz3S5ZdveU

Quote:
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
(Dan Morrill is an AOSP engineer)
alostpacket is offline  
Reply With Quote
The Following User Says Thank You to alostpacket For This Useful Post:
9to5cynic (February 8th, 2012)
Old February 8th, 2012, 02:23 PM   #3 (permalink)
Over Macho Grande?
 
alostpacket's Avatar
 
Join Date: Nov 2009
Location: NY
Posts: 7,873
 
Device(s): GlassXE, MotoX, N5, N4, N7'12, GNex, N1, SGT10.1, Revue, Xoom, Eris, OG Droid
Carrier: TMO

Thanks: 4,582
Thanked 3,563 Times in 1,522 Posts
Default

I should say, as a dev I'm still pretty disappointed in them. I left TMO and unlim data for the Gnex so this is a bummer for sure. Even if it's not as big a bummer as they reported originally.
alostpacket is offline  
Reply With Quote
Reply


Go Back   Android Forums > Android Community > The Lounge > Google
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 11:50 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.