I thought everyone else EXCEPT FOR VERIZON had already updated to JB
http://www.androidcentral.com/jelly-bean-rolling-out-canadian-galaxy-nexus-phones
Well done Verizon. Well done.
Yeah slow clap.
This is the worst.
First the release delay, then it was released broken.
Then the update to fix the problems delay for 5 months, then the problems weren't fix.
Now the update to fix the problems delay redux + JB will be delayed for another 4 months, then............. drumroll
.....the phone still wont work. They will either give me another phone, non android phone. Or i will go to ATT. Coverage isn't as good you say? I don't get coverage with this phone anyway.
GSM version...
At this point I don't care if it's GSM, CDMA, or rotary. I am just tired of waiting. I don't wan't to root so I'll whine and moan. I like knowing that VZW is having to pay people to follow up on the emails I send and on the complaints I file. Does it do any good? Obviously not. Do I smile every time I get a call and see that the call is coming from the 609 area code? Oh yes, I certainly do.
Message was edited by: Verizon Moderator
I recently emailed vzw about my dissatisfation with the lack of info pertaining to updates, and that any info is good just to tell people they are working on it. I was shocked when I received an informative replay and said it was unofficial of course to cover themselves.
The email stated they are having problems with the JB Gnex update and it pertains to the radios. They have to create new radios for the update for it to be released and that it will be a few weeks before the update will be released.
I posted the email over at androidcentral forums with screenshots of the email in the Galaxy nexus forum as proof. The email was censored poorly though from the sender and when it went into details about the radios and problems someone deleted a paragraph and left a half written sentence. so I guess outgoing emails from verizon are censored too like these forums here.
link to ac blog with email about radios delaying update:
Here is my question...What specifically has Verizon done to their radios that causes everyone else to be able to use this update but them? Probably the same thing with ICS. I am pretty confident since Google worked cooperatively with Samsung to create this phone, and they probably programmed the os together, why can sprint and phones in Canada use it, but Verizon claims there are radio problems?
Read up on it. Read how to code for CDMA. Sprint is late to the game and they don't have to worry about the LTE as much. They have like 8 locations and you think all of the ones that are sold are in those locations? There are differences in the proprietary bits between CDMA and GSM which makes a large difference.
Fair enough. I was aware that there was a major difference between GSM and CDMA....but was not aware of the CDMA and "CDMA." Though I am very tech savvy, I do realize that you know way more about this than I do...
I gave a small break down one of the major differences in coding in the other thread. GSM is mostly open source, and CDMA is proprietary. One requires 1 signature, and the other requires 3. One someone can write their own code, and only the library remains untouched. CDMA can't be touched from top to bottom. So Google, Samsung, Verizon has to wait until Qualcomm finishes the radio's during testing before anything can be signed for testing.
If Qualcomm is dragging their feet on this, then, VZW should have signed a contract with them containing considerable penalties for making them look like d****-bags. 😉
That would be on Google, and Samsung not Verizon. You have to remember Verizon didn't manufacturer the device.
No matter what device people will often blame the carrier first. Honestly this is bad IMHO. The reason being this allows carriers more control as to "testing" and among other things as it takes slack off manufacturers. It allows manufacturers to push a subpar product at times with the "fix it later" attitude.
Yes, but if I were VZW and Qualcomm was making me wait this long, I'd be a tad annoyed... So assuming VZW isn't at least partly at fault (which I don't believe for a minute...) Then they are being made fools of by another organization. If that other organization has to test stuff for you, you'd do it under contract wouldn't you? Would you not put in some sort of incentive to do this in a timely fashion? Assuming it's somebody's fault (unless it's just gross <insert insult here> on the part of all parties... a point not totally out of the question) then it's VZW taking a lot of heat unfairly because of *silence*. Or perhaps it's the classic no-win scenario: they really can blame someone else but it just looks like buck-passing... so say nothing. Personally I'd come out with something like: "Yes we are testing an update and there are things we've found that are slowing us down but rest assured we will have an excellent experience waiting for you when this is finished. We thank you for your loyalty and patience." (HA like that'd ever happen with any company)
NDA is the problem. If you sign one you don't want to break it. Verizon may get a lot of heat, but breaking business relationships will have a far worse repercussion than a small number of users complaining about an update. If a business like Verizon breaks one then most manufacturers would opt into not dealing with Verizon and in turn lose phone deals in turn customers may never upgrade devices or switch carriers for other devices.
Excellent point... it does all depend on what the NDA says and admittedly I didn't think of that...
But I can see it now: "In the event <insert guilty party name here> decides to rake you over the coals, you, VZW, have to sit there and take it like a man...".
But all in all, I would not think it would violate an NDA if VZW admitted that an update is being worked on and that "issues" have been found that are causing delays. If you are not saying someone else ran into issues.... and it's not like you're saying there is something new coming that would eat into your current sales... this is support for people who have already bought in.
It's actually common sense to think it is being worked on. With the way people are... If they respond to one question 50 questions come their way. 49 of them they can't answer. With the way in the past 3 years with the lawsuits I see why manufacturers, and carriers don't want to say anything until they are near ready for release. I can give you examples of 8 devices in the past 3 years that when someone said something including a cookie-cutter response everything hit the fan. There are actually more, but those are the ones I remember off the top of my head.
Cliq
Nexus S
Behold II
Thrill
Vibrant
Captivate
Epic 4G
iPhone(MMS and AT&T)
I hope 4.2 gets approved quicker
Considering the phones weren't updated to 4.2 yet and 4.2.1 will be getting pushed out to phones soon that is very doubtful.
Start a new topic or ask questions in the open forum.
