That goes back to Nokia. Like I said more than a few times. No one is bothering asking when Nokia has submitted and how many times was submitted. Let's assume what if the first time around Verizon returned it for the same problem 2 weeks ago and Nokia didn't bother with it for a month spent 2 weeks actually working on it? They submitted again and Verizon returned it 1 week later because the problem wasn't resolved. Who's fault would it be at that point? To me it's Nokia because they are honestly not putting in an effort. So Nokia may have been lying through their teeth for the past 4 months while they put most of their effort on AT&T devices(their largest customer. They buy more overall units and T-Mobile and Verizon combined).
Oh the RIL also affects VZNav, Soft Card, Voicemail, and a few authentication security protocols as well as connectivity.
What does it mean? It means we're screwed. It means whatever has to happen to get it working and down to us is not going to happen in the next couple of weeks. Because if we were in the homestretch on it, they wouldn't bother to create a new label called "Under Development." Presumably, the status will also have to change back to "Under Testing" at some point, and we'll (potentially) be right back where we were 4 months ago. This is Microsoft's way of saying "sorry gang, but you're not going to see it any time soon." Until VZW says something to shed more light (not likely), I would assume the worst.
The only reason I can think of Verizon wanting the OS or Cyan update to be changed just for them is to support Verizon changing different options or Verizon embedding apps that cannot be uninstalled without illegally unlocking your phone.
I am guessing that Verizon wants special privileges (rights) to install permanent software or the ability to change (turn off) certain OS features that it deems expensive to Verizon (too much bandwidth) or competing with their private apps. They want more control and Microsoft will bend over backwards for them.
Yep - AT&T, with their network, is going to be my next provider come end of contract.
I don't mind that Verizon is trying make the quality of the code better or put strict standards on Microsoft, but without giving out details on my credentials, I would consider myself an advanced user, so I would like the option to install what firmware and updates that have come out. So if AT&T is buying the most devices as Tidbits says, I definitely will be eyeing them once my contract comes up too. But I don't think Verizon should have to submit something to their user base, granted I only think their "My Verizon" app is useful, I wouldn't want to be Verizon fielding calls from Novice to Intermediate users who have bought a Windows Phone and for whatever reason use Verizon's apps.
So we're all focused on Microsoft/Lumia and VZW delaying the Windows Phone 8.1 + Cyan update....
We're leaving out HTC 8X and the Samsung ATIV SE. There hasn't been any news after HTC tweet that the 8X was going to get the update in late October.
I can understand no news about the ATIV SE, but if the HTC One M8 is 8.1 compliant than there really shouldn't be any delay releasing the update for the 8X. It shouldn't have taken HTC this long to port the changes from One M8 firmware/OS to the 8X.
So I think VZW is really screwing with the Windows Phone ecosystem on purpose and not Microsoft.
Then, unless you have two homes, you'd be homeless. I got this information directly from Verizon Tech Support and Nokia Tech Support. Both agreed that this is EXACTLY why the Cyan firmware has been returned to Microsoft. My subsequent phone conversation with Microsoft confirmed it as well. Verizon is holding up the Cyan firmware update for "their apps." Call VZW Tech support, ask them to conference in Nokia and see what answer you receive. The problem isn't with the actual connectivity of the OS, but with connectivity issues on their apps, something 95% of customers uninstall upon getting their phone anyway!
Uhuh... Like I said before... Who are to be able to talk the FCC like no one else could and get NDA qualified information and then later on get information from Nokia and Verizon(low level reps on both accounts)...
Like I said show your proof and prove me wrong. You keep hiding behind an NDA or claim proprietary information yet you also say Verizon doesn't have one more than one occasion yet MS and Verizon will make you hold one but MS and Verizon wouldn't have one for each other and their employees... Right... Your just a bubble of information unwilling to share with the masses and believe everything you say.
Like I also said before the RIL affects any Verizon services including connection and security. If it wasn't MS proprietary software. Verizon can't touch it(remember it's proprietary and MS doesn't let any company touch their code and if they did... There would definitely be an NDA).
On the contrary the 8X delay is in fact HTC. They recently started their beta testing with their evaluate community. They always do a beta prior to submitting anything to Verizon or any carrier for that matter.