Cant get Cyan update? Then switch carriers!

[windowsphoneuser2014]

Just for the record.

"The holdup is always the carrier. We'll only know a release date on the date they allow Cyan.

http://nokiatheone.com/2014/08/14/lumia-cyan-now-rolling-to-att-lumia-1020-devices-in-us/

[BigBearacuda]

We are the only carrier in the US without the update! Shame on you verizon!

[pa2k4p]

Our "new phone savings jar" is filling up fast. Can't wait to get all 3 of us o the family plan out of the Verizon ecosystem.

[BigBearacuda]

Probably need to start my own jar.

[vzw_customer_support]

We don't want to see you leave our family pa2k4p. We do our best to provide updates as soon as we receive them from the manufacture but we also want to make sure they will work the best. Are you having any issues with your phone we can address?

Kinquana_VZW
Follow us on Twitter @vzwsupport

[corkwatchr]

Thank you, Kinquana_VZW, for your response. I truly do believe that Verizon does care about ensuring quality updates to our Lumia devices.

Will Verizon eventually push the Cyan update to our Nokia Lumia phones when the updates are completed?

I own the Nokia 822, 928, and 929 (Icon) phones and would like to know that it is at least coming sometime in 2014, 2015, or 2016.

Thank you in advance and have a nice day.

[rednibkram]

Trust me, that answer you received is hogwash!  I've been fighting with Verizon since June to get a reply to that question and they have no intention of answering it!  Do yourself a favor, leave Verizon and go get a Windows Phone on AT&T like everyone else will be doing!  Verizon has made the Windows Phone experience a HORRIBLE ONE and they are the only ones to blame for it!

[corkwatchr]

I understand your frustration, rednibkram, but someone from Verizon Support was at least kind enough to respond to the OP. Let's see if they respond again with an answer to my question whether there will be an update.

Thank you.

[penterax]

You seriously bought that line?

The CS rep did nothing but shunt it to "Are you having a problem we can help you with?" in an effort to try to dodge the issue.

A REAL response would provide information we need. If the CS rep doesn't have that info then he/she/it shouldn't bother to post. It just looks like another snow job. Which it is.

We are asking for one of two things here:

1) The update to Cyan, or, if that isn't ready, if Verizon doesn't feel confident enough to offer a date as to when it will be ready, then

2) The reasons for the delay. If they really wanted to be honest they could tell us what the issues are and produce an actual timetable showing us when the ball was in their hands and when it was in Microsoft's hands. They could talk about what specifically doesn't work. They could demonstrate what is different about Verizon's service that makes it so much harder to fix than ATT's service.

We're talking 5 months here. ATT released Cyan weeks after Microsoft did. There is simply no reason other than incompetence for the delay to last this long. Verizon needs to acknowledge they dropped the ball and demonstrate to us with facts that they've picked it up again and are really on a time-appropriate schedule for getting Cyan to its customers.

Anything but a release date or actual, factual information is a meaningless gesture designed purely to appease the customers without actually making any effort to help them.

And of course we have to wonder - if it takes us 6 months to get Cyan, how long will it take to get Win 10? What about future updates?

[#10]

The other two providers use GSM.

Verizon uses CDMA. That could be the problem. Quite possible the new change over to that new LTE standard could be why it was sent back to Microsoft. A whole lot better reason than that crazy APP theory. Don't you think?

Nice post by the way.

[eschinger]

Maybe there were some quirks that had to be fixed by Microsoft.  No phone OS release is going to be perfect. 

If we're perfectly honest, Verizon could easily find something to nitpick in every release if they really would rather avoid upgrading the phone as again no phone will be 100% bug free.  I do find it hard to believe that there are any catastrophic bugs with the release as we have numerous users on the developer preview and things work great. 

It's hard to take Verizon's excuse about testing seriously when they have no problem allowing new iOS versions on their network on day one and every recent .0 version of a new iOS version has been incredibly buggy. 

[Tidbits]

Verizon doesn't allow on day one... Apple doesn't release an update unless ALL  their devices are ready. So it looks timely but they could have been done with one weeks ago and just finished the last device 4 weeks later and it would look all "timely" or Verizon allows it at the same time.  It's a nice perception trick.

[eschinger]

Apple completes an update and releases it for all their devices.  Unlike with Windows Phone, Verizon cannot prevent Apple from releasing iOS updates to iOS users.  That is probably the result of the negotiating position Apple had over Verizon when Verizon was getting killed not having the most popular device in the United States.  Luckily for iPhone users that leverage also allows iOS users to avoid being subject to the crapware that Verizon likes to inflict on it's users - there are no Verizon apps installed on iPhones.  Unfortunately for Windows Phone and Android users they didn't have the negotiating clout to avoid Verizon mucking up their phones.  But since Verizon did give in to Apples demands they can no longer make a credible claim that they can't let an OS on their network without extensive months long testing since they do every time a new iOS version is released.

[Tidbits]

Join ADC. It doesn't work that way you think. It just looks that way because Apple WAITS until all their devices are finished before releasing the update unlike other manufacturers pushing them as they finish them. I have done ADC for as long as Apple had had that program. If you pay attention to the change logs you can tell which devices are finished and which are being worked on.

[eschinger]

Apple internally sets a release date that corresponds with the event to announce new iPhones.  The iOS release schedule is not variable based on when things happen to be finished.  There are beta releases being updated until extremely close to the release date.  With iOS 8, the gold master wasn't ready until 8 days before it's general release.  If Verizon was able to treat iOS like it treats Windows Phone It would be a minimum of several months after the gold master was completed for Verizon to release it to its users.

Verizon is simply not credible in saying that months of testing are required before an updated OS can be released on it's network (if it is WP or Android) while at the same time allowing iOS to be released on it's network 8 days after Apple finishes the build.  Luckily for iOS users, Apple had enough clout to prevent Verizon for screwing over iOS users.

[Tidbits]

Like I said bro it doesn't work like you think. Did you know Verizon version was finished MONTHS  before the GSM version was for the last major release? Like I said Apple gives you a placebo effect into thinking it is timely. Join the ADC and spend a few months with an iPhone and their program. You'll see what I am talking about.

[eschinger]

I've run iOS beta's throughout the cycle.  The core of iOS8 is the same across all carriers.  The LTE implementation code that support Verizon may have been ready earlier in the process but there was no Verizon specific iteration of iOS8 completed and ready to go months beforehand.  And that is referring to a major release.  Even minor releases of other OSs take months whereas Apple has the ability to release point upgrades to fix bugs when it's ready.  iOS users never have to worry about Verizon being able to delay an upgrade by months (if they get around to releasing it at all).

Microsoft knows it's getting screwed over by the carriers but also knows that with it's market share it doesn't have the clout to truly do anything about it.  So they skate around the periphery by offering things like the Windows Phone Developer Preview to try to get around the carrier nonsense while at the same time trying to be deferential and not directly cross them.

[Tidbits]

Yes there was. For 4 month's the change logs said GSM... CDMA had no updates until GM build. The iPod and iPads. I guess people never paid attention to the change logs.

[eschinger]

I can only assume you are referring to the code related to the radios...  Surely if you look at change logs you would see that the OS as a whole was changed significantly between June and the gold master in September.

But let's use a simpler example.   As a result of issues with the 8.0 release Apple released 8.1 maybe 5-6 weeks after 8.0.  There were bug fixes as well as features added that applied to the cellular stack across the board.  Yet no issues with Verizon customers getting that on the same day as customers from every other carrier.   Apple did not have to wait for Verizon to put iOS 8.1 through the same deliberate (and painfully slow) testing process they put WP through. 

[Tidbits]

says who?  you?  You don't know that?

You also can't explain how Motorola can do what Nokia seem to can't do.  5.0.1 is coming around the corner from Motorola shortly too.  Motorola is in the same position as Nokia, or rather in a worse off position.  It has been broken down and sold twice.  Majority of it's plants has been closed down including their Texas plant.  So how can they push out updates do quickly on all carriers compared to Nokia?

[eschinger]

Nokia was owned by a company whose mobile platform has low single digits market share.

Motorola was owned by a company whose mobile platform has greater than 50% marketshare. 

If you can't see the difference, honestly I don't know what to say.  If Motorola is in position to do the same a year from now or whenever the 'M' version of Android is released that would be analogous and impressive.  However I won't hold my breath that they have the same level of success