[sahilm]

Two quick questions, if anyone knows the answers:

Well, I (like almost everyone else on this forum) has seen the Verizon packaging for the Galaxy Nexus. Something caught my eye though:

Questions?
vzw.com/galaxynexus


I found this very interesting, and to be honest, slightly nerve-racking. Previous Nexus phones have had support done by google, the link users were given was google.com/nexus (and this holds true for the International GN). The Verizon version however sends users to Verizon, which means that they are handling support themselves, as opposed to Google.

My real question is if anyone thinks that this is a sign that Google will not be handling support and therefore updates themselves?

I know most of us don't care much about support, but updates is a big reason I'm getting this phone in the first place.

[protonchain]

Carriers don't dole out updates, manufacturers do. Google will be dealing with the updates, and carriers will be dealing with CS.

[gabbott]

sprint.com/nexus is an info site for the Sprint Nexus S 4G. I think you are reading too much into that.

[D1andOnlyOmen]

I was on the phone last a couple of weeks ago with guy at VZW that was in the executive something or another department (escalated an issue I was having) and I inquired about the Galaxy Nexus as a replacement for my POS Bionic and commented about how I would be able to get updates from Google directly with the Nexus and he claimed that the Nexus would have to get any updates from the "manufacturer" just like any other phone they have. At the time I just kind of wrote it off as him no being all that knowledgeable, even though he claimed to have previously worked in the the tech support area, but not sure if what you caught in the photo is any kind of confirmation his statement actually being accurate. I guess just take it FWIW.....I certainly hope it WON'T be handled that way and the VZW Nexus will be able to be updated directly just like all the previous versions of the Nexus line.

[jamesbrown33]

I was on the phone last a couple of weeks ago with guy at VZW that was in the executive something or another department (escalated an issue I was having) and I inquired about the Galaxy Nexus as a replacement for my POS Bionic and commented about how I would be able to get updates from Google directly with the Nexus and he claimed that the Nexus would have to get any updates from the "manufacturer" just like any other phone they have. At the time I just kind of wrote it off as him no being all that knowledgeable, even though he claimed to have previously worked in the the tech support area, but not sure if what you caught in the photo is any kind of confirmation his statement actually being accurate. I guess just take it FWIW.....I certainly hope it WON'T be handled that way and the VZW Nexus will be able to be updated directly just like all the previous versions of the Nexus line.

The rep probably though the nexus was just another samsung phone and did not realize that the nexii are google's responsibility. Outside of places like this there is no brand recognition for the nexus brand.

[sahilm]

Carriers don't dole out updates, manufacturers do. Google will be dealing with the updates, and carriers will be dealing with CS.

Sorry, my original post was a stupid moment. I meant will samsung be giving out the updates, or will Google directly (like past nexus phones).

[EggoEspada]

sprint.com/nexus is an info site for the Sprint Nexus S 4G. I think you are reading too much into that.

Did the Nexus S 4G get updates the same time as the Nexus S GSM? It seems Google will be handling updates, but curious if there's a difference in when each model would get the update.

[soccerfon711]

I have been fearing this for quite some time. I do not think that Google will be giving direct updates. As shown already by Verizon's testing on the nexus, they will most likely be testing Google's updates and there will probably be a delay, with the updates coming from them.

I am still geting the phone because it's stock android, but I am really doubting whether or not this will be a true nexus or if Samsung is using the nexus name for a clone of the real GSM nexus. I guess we'll have to see.

[Salacon]

Unfortunately, I cannot for the life of me find a link, but I can remember reading in another thread (where a link was posted) that the Verizon Galaxy Nexus would still be receiving updates from Google as stated by a Google engineer.

Edit: Yes, that's exactly it, jamesbrown33! I'm glad it was found, thank you.

[jamesbrown33]

Unfortunately, I cannot for the life of me find a link, but I can remember reading in another thread (where a link was posted) that the Verizon Galaxy Nexus would still be receiving updates from Google as stated by a Google developer/technician.

There've been several questions in this group about tuna vs maguro,
but such questions were buried in the middle on long threads so I'll try to summarize in a new clean thread.

The Galaxy Nexus family is codenamed "tuna". Using fish names in
relationship to devices isn't quite new, since in the past we've had
goldfish (emulator), trout (G1), mahimahi (Nexus One), herring (Nexus
S) and stingray (Xoom).

There are two actual Galaxy Nexus devices, codenamed maguro and toro.
Maguro is the GSM/HSPA+ variant, and Toro is the CDMA/LTE variant.
Toro is a bit fatter, hence its name.

In the source tree released yesterday, there are two directories
called device/samsung/tuna and device/samsung/maguro. The former
contains all the files that are common to both toro and maguro, while
the latter contains the maguro-specific files. There's no
device/samsung/toro in AOSP yet, that directory will get created when
we release the exact code that actually ships on toro.

device/samsung/tuna contains makefiles as if it was an actual device.
There's no such device in reality, but the abstraction is convenient
for engineering purposes as it allows creating a common system image
that works on both toro and maguro, even though it supports neither
GSM/HSPA+ nor CDMA/LTE. This is only meant for engineering purposes,
and the only real devices are maguro and toro.

Looking a little bit in my crystal ball, we'll be supporting toro in
AOSP along with maguro, with similar downloads for proprietary
binaries, and the whole process is tied to shipping toro. Be aware
that my crystal ball is rarely more accurate than a Magic 8-ball, so
you should take this with a grain of salt.

Personally, I prefer working with maguro, as supporting GSM in AOSP is
easier than CDMA in my experience.

JBQ

[greydarrah]

My guess is that if you root and turn your back on Verizon, the developer community will be able to supply any GN with the latest up to the minute updates. If you don't want to root (I have no idea why anyone that would buy a GN would not root it), you'll probably be getting the same 3 months late release, pull it back, re-release, pull it back, re-re-release...that they do for all their phones.

[soccerfon711]

Was that supposed to be reassuring? The guy said that he is rarely more correct than a magic 8 ball and to "take this with a grain of salt." I still stand by my assertion that this is Verizon's device, not Google's.

[Droid800]

Was that supposed to be reassuring? The guy said that he is rarely more correct than a magic 8 ball and to "take this with a grain of salt." I still stand by my assertion that this is Verizon's device, not Google's.

Stand by it all you want, but you're still wrong. This IS google's device, and updates will come directly from Google. Period.

[jamesbrown33]

Was that supposed to be reassuring? The guy said that he is rarely more correct than a magic 8 ball and to "take this with a grain of salt." I still stand by my assertion that this is Verizon's device, not Google's.

I am more inclined to be assured by a statement of a google engineer on the tentative status of direct updates then to be panicked by baseless conjecture to the contrary in a forum

[soccerfon711]

I am more inclined to be assured by a statement of a google engineer on the tentative status of direct updates then to be panicked by baseless conjecture to the contrary in a forum

Baseless? How about the fact that Verizon is blocking a Google feature from being on it's phone? http://www.androidcentral.com/verizo...s-galaxy-nexus

They have taken over the launch of the phone (with Matias Duarte saying that it is their phone now), they added bloatware (2 apps is still bloat), and are checking for bugs themselves (meaning the update process will go through them). I think that this will be a great stock phone with a nexus name, but it will not be a true nexus. And I know that people aren't going to like hearing that, but as of right now, that's what it appears to be. I hope that I am proven wrong and that Google takes over.

Regardless, I'm still getting the phone and I'm super excited for it. Flame me anyways.

[Droid800]

Baseless? How about the fact that Verizon is blocking a Google feature from being on it's phone? http://www.androidcentral.com/verizo...s-galaxy-nexus

They have taken over the launch of the phone (with Matias Duarte saying that it is their phone now), they added bloatware (2 apps is still bloat), and are checking for bugs themselves (meaning the update process will go through them). I think that this will be a great stock phone with a nexus name, but it will not be a true nexus. And I know that people aren't going to like hearing that, but as of right now, that's what it appears to be. I hope that I am proven wrong and that Google takes over.

Regardless, I'm still getting the phone and I'm super excited for it. Flame me anyways.

If you're getting flamed its because you're posting something without spending the time to read the other threads. The nonsensical idea that Verizon will be holding updates hostage, or that they will somehow prevent the timely updates that are a part of the Nexus experience, has been addressed at least half a dozen times in other threads. So we'll say what has been said in those other threads: you are wrong. The updates will come from Google, Verizon's influence will NOT delay timely updates, and this is most assuredly Google's phone, not Verizon's.

[soccerfon711]

If you're getting flamed its because you're posting something without spending the time to read the other threads. The nonsensical idea that Verizon will be holding updates hostage, or that they will somehow prevent the timely updates that are a part of the Nexus experience, has been addressed at least half a dozen times in other threads. So we'll say what has been said in those other threads: you are wrong. The updates will come from Google, Verizon's influence will NOT delay timely updates, and this is most assuredly Google's phone, not Verizon's.

Other threads are speculation, just like this one. And if it were up to Google, this phone would have been released already; Verizon has already caused a delay from it being released with the rest of the Nexus line. It's really common sense that this is a Verizon phone, not a Google one (just look at the back of the phone). Ultimately, you can believe what you want; but you also cannot refute my comments at this point.

[YourMobileGuru]

I was on the phone last a couple of weeks ago with guy at VZW that was in the executive something or another department (escalated an issue I was having) and I inquired about the Galaxy Nexus as a replacement for my POS Bionic and commented about how I would be able to get updates from Google directly with the Nexus and he claimed that the Nexus would have to get any updates from the "manufacturer" just like any other phone they have. At the time I just kind of wrote it off as him no being all that knowledgeable, even though he claimed to have previously worked in the the tech support area, but not sure if what you caught in the photo is any kind of confirmation his statement actually being accurate. I guess just take it FWIW.....I certainly hope it WON'T be handled that way and the VZW Nexus will be able to be updated directly just like all the previous versions of the Nexus line.

No he was exactly right. Verizon does not write the phone updates, the OEM's do, and always have. Verizon tests the updates for quality control but ultimately the update is written and the first round of testing done by the OEM.

In all other phones (except apparently the iPhone) the carrier then does a second round of somewhat lengthy testing called TA or Technical Acceptance and this is where a lot of the blame for update delays is often laid. Weather the GN will have to go through the same process, be exempt from it, or (most likely, IMHO) go through an abbreviated form of TA to allow VZW to make sure that no obvious bugs were missed by Google/Samsung is still an unknown.

EDIT: Yep, from what I am reading it looks like I am right, VZW will do some testing but the bulk will be dome by Google, and there will be no significant delay in updates similar to what i am seeing with my LTE Xoom now vs the WiFi version.

[Droid800]

Other threads are speculation, just like this one. And if it were up to Google, this phone would have been released already; Verizon has already caused a delay from it being released with the rest of the Nexus line. It's really common sense that this is a Verizon phone, not a Google one (just look at the back of the phone). Ultimately, you can believe what you want; but you also cannot refute my comments at this point.

Oh good lord. Yes, we can. We have two and a half generations of Nexus phones as proof. We also have the word of someone that works for Google, and another one that works for Google AND used to work for Verizon. Frankly, we also have no idea WHY the Nexus was held up. Testers have reported significantly improved radios in the newer updates, and far more stability, so it is very possible (and more likely than not) that GOOGLE was the one that held up the Verizon version. Since you apparently know so much, you must be aware that the LTE version is considered a completely different model by Google and Samsung compared to the GSM version, right? The fact is NO ONE knows why it was delayed, and certainly no one can say that it was a Verizon delay.

The updates are coming from Google. Period. End of story. You are wrong. Accept it and move on.

[soccerfon711]

Oh good lord. Yes, we can. We have two and a half generations of Nexus phones as proof. We also have the word of someone that works for Google, and another one that works for Google AND used to work for Verizon.

The updates are coming from Google. Period. End of story. You are wrong. Accept it and move on.

You're basing this all on nexus devices that were never on Verizon. Big difference. Verizon has already shown that they are doing things differently. I'm not going to argue forever. I expressed my opinions; you can believe whatever you need to in order to keep yourself going.

[Droid800]

You're basing this all on nexus devices that were never on Verizon. Big difference. Verizon has already shown that they are doing things differently. I'm not going to argue forever. I expressed my opinions; you can believe whatever you need to in order to keep yourself going.

Your opinion is not based in factual reality.

[jamesbrown33]

Baseless? How about the fact that Verizon is blocking a Google feature from being on it's phone? http://www.androidcentral.com/verizo...s-galaxy-nexus

They have taken over the launch of the phone (with Matias Duarte saying that it is their phone now), they added bloatware (2 apps is still bloat), and are checking for bugs themselves (meaning the update process will go through them). I think that this will be a great stock phone with a nexus name, but it will not be a true nexus. And I know that people aren't going to like hearing that, but as of right now, that's what it appears to be. I hope that I am proven wrong and that Google takes over.

Regardless, I'm still getting the phone and I'm super excited for it. Flame me anyways.

OMG TMOBILE BLOCKS GOOGLE WALLET ON THEIR VERSION OF THE NEXUS S!!!!!!!! THIS IS NOT A TRUE NEXUS!!!!!!!!

oh wait, it is and receives updates directly from google just the same (just like the at&t version, which also blocks google wallet)

[JediJesus95]

Biggest thing here is that we don't have to worry about Samsung getting their skin to work with updates. That alone will get us the updates 3-6 months faster. And of course I mean major updates.

[E.T.]

I think we all agree that the updates come from Google. I dont think anyone is suggesting that Verizon somehow writes android code. But I think there is a legitimate question as to:

a. whether Google's updates will go through a Verizon quality control process (Keywords: Verizon. Control. Process.)

and b. how long that process will take. Isn't it possible that Google could have an update ready extremely quickly, but quality control takes several weeks to months?

[jamesbrown33]

I think we all agree that the updates come from Google. I dont think anyone is suggesting that Verizon somehow writes android code. But I think there is a legitimate question as to:

a. whether Google's updates will go through a Verizon quality control process (Keywords: Verizon. Control. Process.)

and b. how long that process will take. Isn't it possible that Google could have an update ready extremely quickly, but quality control takes several weeks to months?

I don't know the exact timeframe, but verizon's version of the xoom got its updates around the same time as the wifi only model, I think it may have even gotten either 3.1 or 3.2 earlier