Thanks for sharing. That's a great example of the lack of customer service I am talking about. I called AT&T yesterday to inquire about the Denim update for the Lumia 1520, the lady did all but offer me a glass of iced tea and I'm not even an AT&T customer.
However, here is the major difference. Whereas Verizon told you they have no information on the update and left it at that, the AT&T person kindly stated, that they:
"have not received the update from Microsoft yet, but, our technicians are standing by to receive it. Once we receive the update from Microsoft, we will be working hard to provide the update as soon as possible."
She then went on to further inform me something about "sometimes errors are discovered in updates", etc., but did state "in which case we will inform our customers of any possible delays." (She even made a comment about how Verizon and T-Mobile won't do that. Wow!) I guess AT&T is learning something from Verizon's customer releations mistakes.
Think! What did you expect AT&T to say to you? Blame? Cajole?
Wake up. People lie with smiles on their faces all the time.
And I hope I did my good deed for today in Windows Phone Land.
My friend I have known for 38 years called and said he was buying an HTC (M8) windows phone. I explained he should stick to his android devices. Said he was going to read up on Windows phones and if it was going to work with his Windows 8.1 laptop?
I tried and tried to tell him that its not the phone to get. I tried and tried to have him just get the HTC One instead. I may have put a thought in his mind, I hope so.
He is reading the web posts to see what issues it has. Since he is a very smart person I hope he sees this is not the device for him.
But his son & daughter bought them and one works at Sprint and the other T-Mobile and I have no idea what the name is but they like them.
Now I may get to play around with one just for kicks.
Looks like Verizon is the slowest, worst carrier to have for Windows Phone users. T-Mobile just released 8.1 for their Lumia 925 yesterday. The icon is a much newer device and still Verizon doesn't seem to care about releasing the update.
And, just as I have been saying for the longest time, Verizon is the one holding up this update. Even Joe Belfiore, CEO of MS Mobile Division is frustrated with VZW in his latest tweet. "MS/Verizon are working on some bug fixes---VZW taking the quality seriously. We aren't sure how long it will take, but work is underway."
Verizon has had this update since July 15th when Microsoft gave it to them. They are just now getting the update information back to Microsoft to fix bug issues after 3 months!? That is PATHETIC! I could have done better with a crew of monkies!
And the worst part is this is concerning the Cyan firmware update. Not even a mention of the Denim update which this phone is supposed to be one of the FIRST phones to get it. I'm hoping the "working on some bug fixes" is related to Denim update instead of Cyan, but if not, and AT&T gets Denim first, I will DEFINITELY be going to AT&T!
Your reading is a little off. If the update was buggy it went to Microsoft for a fix and then back and forth. That is my take on the Twitter posting.
Microsoft could have at anytime made that statement. But you have no idea how long Microsoft had it back to make those corrections, again you are blaming the carrier.
Could it have been Verizon? Could it have been Microsoft? Now we see it is a combination of both.
Like I said I await your postings at the AT&T forums when you leave.
I'm BLAMING Verizon.
You can blame anyone you like. That does not mean you are right.
See in America you can blame who you like. That is your right!
Elector, you always want to stand up for Verizon. Good for you. But, in my opinion, and in MOST peoples opinion, you are wrong. This is Verizon's fault. They had the update since July 15th and they are just not sending it back to Microsoft for edits. I know from a very reliable source that this is the first time it is being sent back to Microsoft for changes. Believe it or not, I don't care, but it is fact!
rednibkram wrote:
Elector, you always want to stand up for Verizon. Good for you. But, in my opinion, and in MOST peoples opinion, you are wrong. This is Verizon's fault. They had the update since July 15th and they are just not sending it back to Microsoft for edits. I know from a very reliable source that this is the first time it is being sent back to Microsoft for changes. Believe it or not, I don't care, but it is fact!
Like I said multiple times before... If the update fails it goes back to Nokia. They finally admitted this, but NONE of you fathom the idea it has happened more than once... I implore ANYONE to ask Microsoft how many times this has happened. I will bet they will NEVER give you an answer. If they are going to be transparent they will say how many times, but of course all the fanboyism going around none will bother to ask because just like Google for a lot of Android users can't do any wrong even if there are evidence pointing they are doing something wrong. Ask them for the FCC filings and you can actually see how many times it went through the FCC if this is about XLTE. They won't give it to you even though every time it pass it becomes PUBLIC record.
Who would you blame if a scenario like this happens?
Microsoft submits update
Verizon returns it 2 weeks later failed testing
Microsoft submits update 2 months later
Verizon returns it 2 weeks later failed testing
Microsoft submits update 2 months later
Verizon returns it 2 weeks later failed testing
Without knowing the dates submitted and returned with just one instance of Microsoft being transparent about anything. I say we will never get this information from Microsoft. They may have said it one time, but that's the only bone they are going to give.
Start a new topic or ask questions in the open forum.
