- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Never reveal. I should proofread better.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm sure some have had issues. Smartphones often experience bugs. You keep saying this over and over like it means something significant LOL. My dad's old Droid was one issue fixed, another issue introduced, for it's entire update lifecycle. He's had his fair share of hiccups with his previous Galaxy Nexus and his Note 2 has email issues after a recent update. How many times has an iOS update caused any number of bugs, from annoying to crippling? All the time! That has never stopped the updates. Verizon is "taking quality very seriously" with WP 8.1... nudge nudge wink wink *cough*stalling*cough*. I sure as heck don't see them waiting until there's zero bugs on all devices for other smartphones.
At the very least be more open about how long you're sitting on the updates before testing commences, err I mean, how the testing process is going.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For the record Tidbits I'm not calling you a troll nor do I mean to imply you are one. There's a couple of those lurking around ready to "Help" users by telling them we don't matter (marketshare), or insist that since Verizon legally owes us nothing and we should just shut up. You're not one of those. However, I must reiterate that the fact that there's a few bugs affecting some AT&T devices should not automatically throw an all-stop lever. Perhaps they could set up an opt-in beta program that is better than the dev preview - more current code, more current firmware (dev preview on VZW doesn't have current Cyan firmware at the moment, IIRC).
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is another of those times when it is easy to blame Verizon. I know it is frustrating to not get answers, but never assume that Verizon has the answer and is refusing to give it to you. Asking any representative to give you information that they are not provided with will either lead to "I don't know" or it will lead to rumors without facts. As for Verizon handing down the information, that would be like asking Verizon to look into the future and tell you if you will win the lottery next month. Verizon will not pass down information that either; they do not have, or that they have any reason to believe will change. Providing updates is not something verizon does themselves. The company that creates the update makes a deal with each carrier to sell the updates to them. These legal deals can take a very long time to come to an agreement on, they may even give up if it is seen that no reasonable deal will ever be made.
I cannot speak for Verizon really, this is my understanding of how business's work. To provide something to your customers you must first have this something in your possession. To get this something you must make a deal with the people that do have this something that you want.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Before you all tear me apart I apologize in advance. I admit I did not read all of the comments and I may be restating old news. I apologize if I am. And I would also like to say this is not any fault of the customers and I am not saying this should not cause frustration. I do not have a Windows phone so I am not sure what update this is about exactly, but I do understand how poor Verizon's communication can seem in a lot of aspects.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's a huge update football. It adds and improves so much stuff it's like having a new phone. I haven't even really cared about previous updates... this is the first one that's gotten me fired up. But I don't think you'll find many asking Verizon to see into the future with any certainty. We're asking them to state what has already occurred, and what is happening now. A guesstimate or some kind of indefinite timeline would be a bonus at this point. The reason they're so quiet is that they have been, uh, moving at a slow pace shall we say. So stating the facts would only make them look bad. Better to remain silent.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have said it before about a device preview. Nokia doesn't need Verizon approval to make this happen.
HTC and Motorola have beta programs. Carriers don't opt in to it.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I see. I wonder if Nokia is the same though. It would be hard for Verizon to say, this will be out in a few months and then have something happen and not be able to get it out by then. That would be worse than staying silent as you said Alex.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Alexvrb wrote:
At the very least be more open about how long you're sitting on the updates before testing commences, err I mean, how the testing process is going.
100% positive carriers are under an NDA and only the manufacturer can give any detail. See Motorola, and T-Mobile with the Motorola Cliq. T-Mobile regurgitated what Motorola said only after Motorola said it. People sued T-Mobile and not Motorola... Which was hilarious... Motorola flat out said it was a driver issue with Sharp and it took Sharp 6 months to deliver their drivers to Motorola. I wish the old threads were around to show you. There was similar things happening with HTC and the One S update not happening. People still blamed T-Mobile for it.
So no matter a carrier does they are in a catch 22. Microsoft finally admitted they got the update back. Not one person even bothered to ask them how many times this has this happened. I bet they won't give you an answer(which make me believe more than a handful of times).
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The dev preview is no replacement. If a beta program could have the latest firmware too, it would be acceptable. In that case it would probably have to be at least Verizon-sanctioned. Regarding NDAs, if that was the case they could state they are under NDA and not allowed to discuss X Y and Z as a result, and tell us whatever they can.
Anyway, if non-Verizon models weren't already running the update on essentially identical hardware, I'd certainly blame MS a lot more here. If there was a really massive important Android update for several SGS models and Verizon was way behind the other carriers, I don't know that blaming it on some minor bugs would go over all that well. Nor would the lack of communication in general. But at this point I think a lot of people would be happy to hear they're getting it before the year is over.