• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

VZW Nexus No longer a "Developer Phone"

This is ******, Verizon and Google implied that this would be a developer phone giving the end user full support. Whatever BS they use to justify "pulling support" is ludicrous. I bought a Nexus device knowing that I would get this full support and now that Google has stated they are treating the CMDA phone differently, I am pissed. I know that we will still have developer support and good ROMs will continue to be released but that is not the point. Pulling the wool over consumers eyes is wrong and right now I'm not a fan of Google.
 
Upvote 0
Nothing to worry about here, folks. The LTE GN will still get updates straight from EL GOOG.



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

That's not what it says. It says that Google will still be providing source to the carrier who will then need to add the necessary files to complete the update. I take that to mean that the updates will then have to come from Verizon and/or Samsung. At least that's how I interpreted it.
 
  • Like
Reactions: rexdog1888
Upvote 0
That's not what it says. It says that Google will still be providing source to the carrier who will then need to add the necessary files to complete the update. I take that to mean that the updates will then have to come from Verizon and/or Samsung. At least that's how I interpreted it.

Yes, but that is because CDMA requires that occur, and was how all updates were going to come to us anyways, even if this event hadn't occured. So Gunner is correct in that there is nothing to worry about here, not one thing is really going to change. Google will do the vast majority of the work, Verizon will finish it up, Google will sign-off, and we get the update. THis is exactly what happened for the 4.0.2 update we recieved on release day.
 
Upvote 0
That's not what it says. It says that Google will still be providing source to the carrier who will then need to add the necessary files to complete the update. I take that to mean that the updates will then have to come from Verizon and/or Samsung. At least that's how I interpreted it.

That is pretty much the way it always would have been. GSM phones can have OTA updates straight from the source because they all run the same radios. CDMA updates have always gone through the carrier's for testing before release to the end user. Even between CDMA carriers the set up is different. Hopefully this will all change once we get full LTE networks.
 
Upvote 0
I'm not sure how you can misinterpret this statement?

the company will continue to support the Verizon Galaxy Nexus through official firmware updates

This doesn't say anything about carrier compiled updates - it says EL GOOG will provide the official firmware updates. Seems pretty clear to me.

Edit: As OTD and AntimonyER have said, the carriers will test the firmware updates for quality control before giving the blessing to unleash, but that's always been the case. Google will still compile the firmware and release the updates, upon each carrier's blessing.
 
Upvote 0
That's the big question, isn't it. Seems like this could throw a large wrench in the works. Devs might have to hope for certain proprietary apk's to get leaked. But, GOOG did say that they hope to make available as many 'closed source binaries' as possible. I take that to mean they hope to make the necessary apk's available so that CDMA ROMs are still possible by devs.
 
Upvote 0
I'm not sure how you can misinterpret this statement?



This doesn't say anything about carrier compiled updates - it says EL GOOG will provide the official firmware updates. Seems pretty clear to me.

That is the wording used by Verge and not the official statement. The Verge really screwed the pooch on that article so I would take what the say with a grain of salt.

You can find the actual wording here: Google Issues Statement Regarding CDMA Nexus Devices – Droid Life

It doesn't say anything about directly supporting the Verizon Galaxy Nexus.
 
Upvote 0
That is pretty much the way it always would have been. GSM phones can have OTA updates straight from the source because they all run the same radios. CDMA updates have always gone through the carrier's for testing before release to the end user. Even between CDMA carriers the set up is different. Hopefully this will all change once we get full LTE networks.

All things being equal I would agree. However, something has changed. Prior to today you could get the signed files needed directly from Google but now they are saying they will no longer be able to provide them. Verizon has done something to get in the way here and we all know that's never a good thing for us Android enthusiasts.
 
Upvote 0
Yes, but that is because CDMA requires that occur, and was how all updates were going to come to us anyways, even if this event hadn't occured. So Gunner is correct in that there is nothing to worry about here, not one thing is really going to change. Google will do the vast majority of the work, Verizon will finish it up, Google will sign-off, and we get the update. THis is exactly what happened for the 4.0.2 update we recieved on release day.

Again that may be but it seems like the signed files were at one point being provided directly to Google speeding up the process. If the signed files were being provided to Google they are much more capable adding the files than Verizon would be. Who would you rather have responsible for getting the files working correctly in an efficient manner, Verizon or Google?
 
Upvote 0
All things being equal I would agree. However, something has changed. Prior to today you could get the signed files needed directly from Google but now they are saying they will no longer be able to provide them. Verizon has done something to get in the way here and we all know that's never a good thing for us Android enthusiasts.

If you notice the phrase that Google used in their statement:

recent CDMA Android devices implement core telephony functionality in .apk files provided in binary form by the carriers.

The files are provided by the carrier which means that the carriers more than likely own these files. This means they are also not likely open source which makes it understandable that Verizon or Sprint would not want the information all over the place. Especially if the information contained in those binaries would allow for network manipulation or anything else. Is Verizon behind it? Possibly, but keep in mind that they are not the only CDMA carrier to have or want a Nexus on their network. This could be Verizon, Sprint or one of the Asian carriers that use CDMA technology. Nobody knows for sure and nobody knows how it will affect things with regards to development or anything else.

Leaks and dev builds have been coming out for Verizon devices long before there was a Nexus on the network. Will this cause an issue because the files aren't on Google's website? I doubt it. If anything I actually think this may put more pressure on some of the developers to get more leaks from testers like they have in the past.


Again that may be but it seems like the signed files were at one point being provided directly to Google speeding up the process. If the signed files were being provided to Google they are much more capable adding the files than Verizon would be. Who would you rather have responsible for getting the files working correctly in an efficient manner, Verizon or Google?

I don't think this means that Verizon will no longer offer the files to Google, but rather that Google will no longer offer the files to us. There is a big difference there.
 
  • Like
Reactions: jroc and FragDroidX
Upvote 0
If you notice the phrase that Google used in their statement:



The files are provided by the carrier which means that the carriers more than likely own these files. This means they are also not likely open source which makes it understandable that Verizon or Sprint would not want the information all over the place. Especially if the information contained in those binaries would allow for network manipulation or anything else. Is Verizon behind it? Possibly, but keep in mind that they are not the only CDMA carrier to have or want a Nexus on their network. This could be Verizon, Sprint or one of the Asian carriers that use CDMA technology. Nobody knows for sure and nobody knows how it will affect things with regards to development or anything else.

Leaks and dev builds have been coming out for Verizon devices long before there was a Nexus on the network. Will this cause an issue because the files aren't on Google's website? I doubt it. If anything I actually think this may put more pressure on some of the developers to get more leaks from testers like they have in the past.



I don't think this means that Verizon will no longer offer the files to Google, but rather that Google will no longer offer the files to us. There is a big difference there.

All good points for sure. I have just learned to be sceptical about things when it concerns Verizon.
 
Upvote 0
That is the wording used by Verge and not the official statement. The Verge really screwed the pooch on that article so I would take what the say with a grain of salt.

You can find the actual wording here: Google Issues Statement Regarding CDMA Nexus Devices – Droid Life

It doesn't say anything about directly supporting the Verizon Galaxy Nexus.

Yep, I've read Morrill's statement. What I'm talking about is independent verification direct from GOOG, that both TheVerge and DroidLife have stated they've received which says that GOOG will continue to directly support the LTE GN w/ firmware updates. This is separate communication, not talking about the Morrill post. I even questioned Kellex at Droidlife directly about it (because I was also skeptical), and he said he got word separately from Google about supporting our GN's.

So, there's nothing to fear here, at least for the common end user. For dev's and ROM enthusiasts, that remains to be seen.

Verizon has done something to get in the way here and we all know that's never a good thing for us Android enthusiasts.

I don't believe this can be pinned on VZW, as support for the Nexus S on Sprint was also pulled. I believe it has to do w/ CDMA phones running Android 4.0.
 
Upvote 0
Yep, I've read Morrill's statement. What I'm talking about is independent verification direct from GOOG, that both TheVerge and DroidLife have stated they've received which says that GOOG will continue to directly support the LTE GN w/ firmware updates. This is separate communication, not talking about the Morrill post. I even questioned Kellex at Droidlife directly about it (because I was also skeptical), and he said he got word separately from Google about supporting our GN's.

So, there's nothing to fear here, at least for the common end user. For dev's and ROM enthusiasts, that remains to be seen.



I don't believe this can be pinned on VZW, as support for the Nexus S on Sprint was also pulled. I believe it has to do w/ CDMA phones running Android 4.0.

I truly hope you are right. Verizon is like the parent that always like to ruin the fun "for our own good".
 
Upvote 0
All good points for sure. I have just learned to be sceptical about things when it concerns Verizon.

I've learned that just because it is said, doesn't make it so and until there is solid proof that something is wrong there is no reason to get upset over it.

When the GSM Nexus gets an update and there isn't a whisper of one comeing for CDMA, then I'll be concerned.
 
Upvote 0
When the GSM Nexus get's an update and there isn't a whisper of one comeing for CDMA, then I'll be concerned.

I'm certain the GSM GN will always get updates way before the LTE version, since they'll come straight down the pipe. Our updates will inherently be delayed due to VZW's 'QC' (remember all the launch delays?). Just hopefully not delayed too much.
 
Upvote 0
I'm certain the GSM GN will always get updates way before the LTE version, since they'll come straight down the pipe. Our updates will inherently be delayed due to VZW's 'QC' (remember all the launch delays?). Just hopefully not delayed too much.

It won't necessarily go that way. GSM Nexus launched with 4.0.1 and LTE Nexus was released with 4.0.2 from beginning. GSM one got 4.0.2 a few weeks later.
 
  • Like
Reactions: icn4d
Upvote 0
So, the question is... can you still build AOSP for the nexus from the open source android package repositories?

So they just changed the text of the website, but nothing in the repositories is different? They will still update toro source as usual? And devs will continue to build custom roms?
 
Upvote 0
I've learned that just because it is said, doesn't make it so and until there is solid proof that something is wrong there is no reason to get upset over it.

When the GSM Nexus gets an update and there isn't a whisper of one comeing for CDMA, then I'll be concerned.


yeah it's just a rumor at this point, and even if it were true, to me it doesn't sound like a big deal...
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones