LTE Galaxy Nexus no longer supported by google?

[Pengwn]

As far as my phone goes, I'd like to think I know it inside and out. When it comes to adb, I haven't the slightest idea.

Is it possible that they're making two different adb's? One for CDMA devices and one for GSM?

Again, I have no clue. I'm just trying to figure this out like the rest of you.

 

[davidnc]

I saw this posted by android police via tweeter as well as droid life and other forums ,still dont know exactly how to take this news .
Time for a Chill Pill

 

[mrholzapfel]

time to relax...

Verizon Galaxy Nexus removed from Google's developer support pages (update) | The Verge

Update 2: Google has reached out to us again ? it turns out that they incorrectly responded to our request for comment on their relationship with the Galaxy Nexus on Verizon and that it will continue to support the device through official firmware updates. Disaster averted.

 

[racedog]

This entire Nexus deal with VZW just keeps on getting more and more interesting, and not necessarily in a good way. It really isn't clear yet what this means so I'll just sit on this until the dust settles a bit and things start getting a bit more clear.

I'm rooted and running the codename rom which is really nice but I also have ongoing serious problems with the weak radios which is why I finally decided to move on from the GN anyway. As much as I like ICS, it's even more important that the phone actually works as a phone and that data (both wireless and internet) work and that isn't happening for me.

As for leaving Verizon, I live in an area that has only TMO and Sprint as alternatives and TMO only has 1x in this area and Sprint barely has coverage and AT&T, well AT&T doesn't offer service here at all so I'm really stuck with Verizon.

 

[Phil Nickinson]

Read this. This is what is going on. https://groups.google.com/forum/?fromgroups#!topic/android-contrib/phz3S5ZdveU

Jerry is translating it into plain English. Will be on the blog shortly.

 

[MRW1215]

time to relax...



Update 2: Google has reached out to us again ? it turns out that they incorrectly responded to our request for comment on their relationship with the Galaxy Nexus on Verizon and that it will continue to support the device through official firmware updates. Disaster averted.

Aside from the last line (that the GNex will continue to be supported), I don't understand what this update is saying, as to the reason they removed these devices from the page to begin with.

This entire Nexus deal with VZW just keeps on getting more and more interesting, and not necessarily in a good way. It really isn't clear yet what this means so I'll just sit on this until the dust settles a bit and things start getting a bit more clear.

Honestly, I don't understand why there appear to be issues between Verizon and Google over the Nexus. I mean, didn't Verizon make a big deal about passing up on the SII just so they could put out the Nexus first? It's not like they were forced into carrying the phone, they seemed to really want it. Surely they knew what a "Nexus" phone constituted (a "pure" Google experience) when they got on board? So why would they start causing problems with Google over the phone? Just doesn't make any sense to me.

 

[racedog]

Read this. This is what is going on. https://groups.google.com/forum/?fromgroups#!topic/android-contrib/phz3S5ZdveU

Jerry is translating it into plain English. Will be on the blog shortly.

Interesting comment by google, especially the line "GSM/HSPA+ devices are still supported, as are any other devices we're able to support". That just seems to muddy the waters even more. So, GSM/HSP are still supported but what are the other devices that they are not going to be able to support?

 

[davidnc]

Read this. This is what is going on. https://groups.google.com/forum/?fromgroups#!topic/android-contrib/phz3S5ZdveU

Jerry is translating it into plain English. Will be on the blog shortly.

I just found that too ,You beat me to posting it Phil haha

 

[broadwayblues]

It has to do with keys and such: here is the official answer from Google:

Google Groups

 

[jerrod6]

Keys huh?

I am telling ya... If Verizon and it's CDMA/LTE technology continues to screw around and not do things like provide Google Wallet... provide direct updates from Google, and now this thing with Google wiggling out of support for the LTE GN I will move to At&T or sprint. I don't use 4G that much and I don't need unlimited data so I don't care. I don't care about the Verizon network. AT&T is already in the house by another person, I don't pay for it, so if I move I will get it for free. I travel in Europe so why not have a GSM phone?

Two years from now If there is no Pure android phone on Verizon I will leave it. Maybe even before then if this crap keeps up. I don't need this. I pay money, and I HAVE money, and I will use it to my benefit even if it means leaving VERIZON for something else that benefits me.

 

[steveholtam]

It seems pretty simple. From what I gather from Google's post, when a CDMA developer creates a ROM, it becomes unsigned and thus is no longer a "pure" AOSP phone. They are indicating this can cause problems with the phone. It sounds like Google (and the carriers) would rather not support unsigned code problems, thus are pulling the source code.

In the long run, it sounds like private custom non-AOSP rom on CDMA phones are going to be red-headed step kids... So stick with a stock Verizon ROM or be an outcast.

 

[Johnly]

Red headed step kids? Really? Who actually says that?

 

[ShinyTop]

Red headed step kids? Really? Who actually says that?

Those of us who are older than 12?

 

[pauldroidr2d2]

I'd wait a little before overreacting guys. I know that's a lot to ask the internet, but I'm sure there's a reason for this. In case none of you noticed, The Nexus S 4G and Xoom LTE are not on there either. Could very much be that Google doesn't think of carrier-locked phones as developer devices. It doesn't necessarily mean we wont get the updates, as we have, further down the line, from Google.

I'm sorry, can you repeat that? I was having trouble reading the above post while sharpening my chains and pitchforks.

 

[ejaymd11]

Keys huh?

I am telling ya... If Verizon and it's CDMA/LTE technology continues to screw around and not do things like provide Google Wallet... provide direct updates from Google, and now this thing with Google wiggling out of support for the LTE GN I will move to At&T or sprint. I don't use 4G that much and I don't need unlimited data so I don't care. I don't care about the Verizon network. AT&T is already in the house by another person, I don't pay for it, so if I move I will get it for free. I travel in Europe so why not have a GSM phone?

Two years from now If there is no Pure android phone on Verizon I will leave it. Maybe even before then if this crap keeps up. I don't need this. I pay money, and I HAVE money, and I will use it to my benefit even if it means leaving VERIZON for something else that benefits me.

Seems people are still getting confused. They are not wiggling out of support, sound more like they are saying only we (Google) will deal with updates and source for these phones. The issue has to do with developers and not being able to create a rom the functions 100%. So to end all the messed up roms, that can't dial 911 or send mms we will just stop making the source AVAILABLE. The main reason for the Nexus on VZW I thought was so we can get timely updates directly from Google? That is not going to change. Because CDMA is different on VZW doesn't mean that it's not good. I mean how is your service? I can say that having CDMA/LTE on Verizon that my service is still amazing. However I think I will not buy a new phone untill VoLTE is standard

 

[ejaymd11]

It seems pretty simple. From what I gather from Google's post, when a CDMA developer creates a ROM, it becomes unsigned and thus is no longer a "pure" AOSP phone. They are indicating this can cause problems with the phone. It sounds like Google (and the carriers) would rather not support unsigned code problems, thus are pulling the source code.

In the long run, it sounds like private custom non-AOSP rom on CDMA phones are going to be red-headed step kids... So stick with a stock Verizon ROM or be an outcast.

You mean stock Google rom since it's a Nexus right?

 

[sniffs]

I am not sure why people aren't getting this.

Verizon requires signed APK's in their builds and only provides to Google for official releases, NOT AOSP. So because of this, Google pulled AOSP for the CDMA GN.

This means that developers and themers, can't build their own AOSP from source and make it work 100%.. so it's effectively killing developer support from a developer phone.

Way to go Verizon, I hate you.

 

[pauldroidr2d2]

Keys huh?

I am telling ya... If Verizon and it's CDMA/LTE technology continues to screw around and not do things like provide Google Wallet... provide direct updates from Google, and now this thing with Google wiggling out of support for the LTE GN I will move to At&T or sprint. I don't use 4G that much and I don't need unlimited data so I don't care. I don't care about the Verizon network. AT&T is already in the house by another person, I don't pay for it, so if I move I will get it for free. I travel in Europe so why not have a GSM phone?

Two years from now If there is no Pure android phone on Verizon I will leave it. Maybe even before then if this crap keeps up. I don't need this. I pay money, and I HAVE money, and I will use it to my benefit even if it means leaving VERIZON for something else that benefits me.

Why wait? Instead of making idle threats, show VZW whose boss and bail now.

 

[pauldroidr2d2]

Seems people are still getting confused. They are not wiggling out of support, sound more like they are saying only we (Google) will deal with updates and source for these phones. The issue has to do with developers and not being able to create a rom the functions 100%. So to end all the messed up roms, that can't dial 911 or send mms we will just stop making the source AVAILABLE. The main reason for the Nexus on VZW I thought was so we can get timely updates directly from Google? That is not going to change. Because CDMA is different on VZW doesn't mean that it's not good. I mean how is your service? I can say that having CDMA/LTE on Verizon that my service is still amazing. However I think I will not buy a new phone untill VoLTE is standard

Timely updates? VZW, still has to sign off to allow the OTA. What is to prevent them from making Google's request sit in the inbox pile for extended periods of time?

 

[ejaymd11]

I am not sure why people aren't getting this.

Verizon requires signed APK's in their builds and only provides to Google for official releases, NOT AOSP. So because of this, Google pulled AOSP for the CDMA GN.

This means that developers and themers, can't build their own AOSP from source and make it work 100%.. so it's effectively killing developer support from a developer phone.

Way to go Verizon, I hate you.

You hate them why? Because they use a different network? One that is voted superior than the rest year after year? Pretty dumb reason to hate something. The fact that the Nexus S4g was pulled as well means that the signed APK is more than a VZW requirement.