[ConTejas]

I do not have a PayPal account anymore because PayPal banned me for using my German
bank-issued credit card. (claiming that couldn't confirm my identity)

However, I'll gladly send you the $10 via a BestBuy or Walmart e-certificate. (or Lufthansa
certificate, since it costs me nothing to get one of those)

Sounds shady to me too

Don't worry though, I'll just give you my Paypal to donate to...and it's ONE 'merican dollar. $1.

[JHBThree]

The Nexus S got JB. The Xoom Wifi is in Soak testing for JB. And the only update being tested on the VZW GNex is one for ICS. Still no word from Verizon on our JB update yet.

I do believe Google was referring to the Nexus S when they said other Nexus devices would get it "shortly."

Sent from my VZW Galaxy Nexus using Android Central Forums

When has Verizon ever given official advanced warning that they're testing a new update?

Yeah, didn't think so...

Sent from my Galaxy Nexus using Tapatalk 2

[TheAssailant]

When has Verizon ever given official advanced warning that they're testing a new update?

Yeah, didn't think so...

Sent from my Galaxy Nexus using Tapatalk 2

I'm a student in Software Engineering which deals in the principles of software development and testing. Verizon is still testing an update, which leaves two possibilities for what the testing team is currently doing:

1) testing both IMM76Q and Jelly Bean at the same time (irresponsible, because if something changes in the bottom update, the top update has to retest as well, which adds time and overhead to the testing phase without any real benefit [the only way this would be beneficial is if IMM76Q is completely bug-proof, which is virtually impossible])

or

2) testing one, releasing, and then beginning the work on the next.

We know this (IMM76Q) update exists because it's already been leaked and there's a link to it on XDA pointing to Google's servers. And we know what is does because the lads at XDA have already peeked inside and taken a look at what the update changes.

It's likely the JB is ready for testing, but it would go against common sense to start testing it before this update is released.

So yes, IMM76Q does in fact add to the wait time before you can get your hands on any official JB OTA, so any scorn given for this update that does nothing except for the nerfing of search, is perfectly justified.

[JHBThree]

I'm a student in Software Engineering which deals in the principles of software development and testing. Verizon is still testing an update, which leaves two possibilities for what the testing team is currently doing:

1) testing both IMM76Q and Jelly Bean at the same time (irresponsible, because if something changes in the bottom update, the top update has to retest as well, which adds time and overhead to the testing phase without any real benefit [the only way this would be beneficial is if IMM76Q is completely bug-proof, which is virtually impossible])

or

2) testing one, releasing, and then beginning the work on the next.

We know this (IMM76Q) update exists because it's already been leaked and there's a link to it on XDA pointing to Google's servers. And we know what is does because the lads at XDA have already peeked inside and taken a look at what the update changes.

It's likely the JB is ready for testing, but it would go against common sense to start testing it before this update is released.

So yes, IMM76Q does in fact add to the wait time before you can get your hands on any official JB OTA, so any scorn given for this update that does nothing except for the nerfing of search, is perfectly justified.

Except we know that all the latest ics update does is remove universal search, something that JB does as well. It would not touch any of the rest of the system so there would be no issue with overlapping testing.

Sent from my Galaxy Nexus using Tapatalk 2

[Mooem]

As someone who works in software testing, I can tell you overlap testing happens all the time...specifically with interim patches. You don't simply halt major testing on a big release when you have to ready a patch that "fixes" one particular area of the software. Nor do you have to re-test the entire application if the interim build only affects a specific portion of the software. That would be unrealistic in terms of time and it would also be an inefficient use of resources.

Once the interim patch has been tested and deployed into production, it's then merged and integrated into the next major release being tested. Re-testing is performed only for the affected area that was patched. Later regression testing will hopefully catch any other anomalies that pop up as an effect of an interim build that was not caught during initial testing (before it was deployed to a production build).

Of course it all depends on how extensive the change is AND not every company's test process is the same as others.

[TheAssailant]

As someone who works in software testing, I can tell you overlap testing happens all the time...specifically with interim patches. You don't simply halt major testing on a big release when you have to ready a patch that "fixes" one particular area of the software. Nor do you have to re-test the entire application if the interim build only affects a specific portion of the software. That would be unrealistic in terms of time and it would also be an inefficient use of resources.

Once the interim patch has been tested and deployed into production, it's then merged and integrated into the next major release being tested. Re-testing is performed only for the affected area that was patched. Later regression testing will hopefully catch any other anomalies that pop up as an effect of an interim build that was not caught during initial testing (before it was deployed to a production build).

Of course it all depends on how extensive the change is AND not every company's test process is the same as others.

I doubt Verizon would have the foresight to be that efficient. Otherwise IMM76K wouldn't have taken as long as it did.

Sent from my VZW Galaxy Nexus using Android Central Forums

[dmmarck]

I doubt Verizon would have the foresight to be that efficient. Otherwise IMM76K wouldn't have taken as long as it did.

Sent from my VZW Galaxy Nexus using Android Central Forums

Although, one could argue it only took 4 weeks, for that was roughly the time period between leaking it and rolling it out.

[Mooem]

I doubt Verizon would have the foresight to be that efficient. Otherwise IMM76K wouldn't have taken as long as it did.

Sent from my VZW Galaxy Nexus using Android Central Forums

Well I'm not trying to defend Verizon here, I'm just saying that interim builds don't necessarily have to delay future deployments. Besides, without really knowing Verizon's test process or resources, it'll be difficult to determine exactly what their inefficiencies are...if any.

[cbbartley]

Anybody read the news that the Samsung has pretty much finished testing JB for the GS3 and is basically waiting for the OK from Google to roll it out?

That would be a serious blow to Verizon Nexus owners. Of course not to those who have rooted and booted, but to the thinking that the Nexus line got official OTAs quicker than any other phone. Many have been defending that as something that would hold true, but the GS3 is challenging that notion and taking the rug out from a lot of techies who nudged friends, family, and otherwise based on this.

[jjt981]

Anybody read the news that the Samsung has pretty much finished testing JB for the GS3 and is basically waiting for the OK from Google to roll it out?

That would be a serious blow to Verizon Nexus owners. Of course not to those who have rooted and booted, but to the thinking that the Nexus line got official OTAs quicker than any other phone. Many have been defending that as something that would hold true, but the GS3 is challenging that notion and taking the rug out from a lot of techies who nudged friends, family, and otherwise based on this.

I had this thought earlier but then remembered that just because Google has approved it means Verizon will still have to test it. So I'm not to worried.
And as for the phone not being updated as we feel as timely ya shouldn't get one controlled by a carrier. Yes its cheaper but comes with a cost (and honestly now the unlocked from Google is only what $50 more then of was for me to buy on launch day with an update.
I have learned to stick with unlocked and gsm. I love Verizon service but I like to get the updates and because the world uses gsm, gsm is the more supported device. Just like Apple and the iPhone for how many years. Just my many thoughts.

[SOTK]

It now seems more likely that Verizon's Samsung Galaxy S3 and certain Verizon/HTC phones
will receive Jelly Bean OTA first. (BEFORE the VZW CDMA Galaxy Nexus)

Yes, anybody can get Jelly Bean on their VZW Galaxy Nexus right now by flashing it, but
that's not the point...

How will you feel if this really happens?

I could care less. I stopped relying on Verizon for technical support and firmware releases two phones ago!

Sent from my Galaxy Nexus using Tapatalk 2

[JHBThree]

Anybody read the news that the Samsung has pretty much finished testing JB for the GS3 and is basically waiting for the OK from Google to roll it out?

That would be a serious blow to Verizon Nexus owners. Of course not to those who have rooted and booted, but to the thinking that the Nexus line got official OTAs quicker than any other phone. Many have been defending that as something that would hold true, but the GS3 is challenging that notion and taking the rug out from a lot of techies who nudged friends, family, and otherwise based on this.

Since when does 'samsung has pretty much finished testing' equate to 'verizon has even started testing'. Here's a hint: it doesn't.

Sent from my Galaxy Nexus using Tapatalk 2

[cbbartley]

Since when does 'samsung has pretty much finished testing' equate to 'verizon has even started testing'. Here's a hint: it doesn't.

Sent from my Galaxy Nexus using Tapatalk 2

It doesn't. But for them to moving on this stage, and Verizon soak testing a variant of ICS on the Nexus should raise an eyebrow. Taking into account this period of time for soak testing, then the period of time for them to get the OTA out, and the time to soak test JB; we could conceivably see JB on GS3 first.

I love when the geniuses give hints in the forums. It makes life so much easier for everyone else.

[F34R]

I've learned through Verizon from phones in the past, that I don't expect OS updates. It almost kept me from getting the s3.

Sent from my Nexus 7 using Android Central Forums

[JHBThree]

It doesn't. But for them to moving on this stage, and Verizon soak testing a variant of ICS on the Nexus should raise an eyebrow. Taking into account this period of time for soak testing, then the period of time for them to get the OTA out, and the time to soak test JB; we could conceivably see JB on GS3 first.

I love when the geniuses give hints in the forums. It makes life so much easier for everyone else.

The gs3 will not get JB first.

Sent from my Galaxy Nexus using Tapatalk 2

[slik6996]

The gs3 will not get JB first.

Sent from my Galaxy Nexus using Tapatalk 2

You might be surprised it might get it first
Verizon cares more about there new phone.

[Touchpaddle]

The gs3 will not get JB first.

Sent from my Galaxy Nexus using Tapatalk 2

GSM GS3s will get JB before VZW CDMA GN ,that's for sure.

[dmmarck]

GSM GS3s will get JB before VZW CDMA GN ,that's for sure.

Perhaps, but that's a Verizon issue, not necessarily a Galaxy Nexus issue.

[Touchpaddle]

Perhaps, but that's a Verizon issue, not necessarily a Galaxy Nexus issue.

yes... Verizon is trying to get rid of the Galaxy Nexus.

my local VZW corporate store no longer has the Galaxy Nexus on display. it was removed last week.
for some strange reason, they have 5 working Galaxy S3 on display now. all white....

[FramCire]

Anybody read the news that the Samsung has pretty much finished testing JB for the GS3 and is basically waiting for the OK from Google to roll it out?

That would be a serious blow to Verizon Nexus owners. Of course not to those who have rooted and booted, but to the thinking that the Nexus line got official OTAs quicker than any other phone. Many have been defending that as something that would hold true, but the GS3 is challenging that notion and taking the rug out from a lot of techies who nudged friends, family, and otherwise based on this.

Nexus JB was completed weeks ago. GS3 just got done? How does that make it likely it comes quicker.

In the end, Verizon might push Motorola phones as quickly as possible. However Samsung and HTC don't usually get a quick push.

Sent from my Galaxy Nexus using Tapatalk 2

[F34R]

You might be surprised it might get it first
Verizon cares more about there new phone.

That would be the biggest surprise in the history of phone software updates.

Sent from my SCH-I535 using Android Central Forums

[slik6996]

That would be the biggest surprise in the history of phone software updates.

Sent from my SCH-I535 using Android Central Forums

Its Verizon it would not be a huge surprise.

[JHBThree]

You might be surprised it might get it first
Verizon cares more about there new phone.

It will not get jellybean before the nexus. Period.

Sent from my SCH-I535 using Tapatalk 2

[slik6996]

I do see the galaxy s3 on Verizon getting JB first.

[dmmarck]

I do see the galaxy s3 on Verizon getting JB first.

I can see other S3's getting it first, but Verizon has very exacting standards.

FWIW, the Verizon OTA is testing.