Fair enough 
Microsoft support site has changed th status of the cyan update for all Verizon windows phones to "under development".
All other phones say "available" or "under testing". What does "under development" mean versus "under testing". Does this mean we are going backwards with the update instead of forwards? 😞
This means that Verizon has decided that they want their software apps to work flawlessly with the new firmware update before they will grant approval of it, so they sent it back to Microsoft to "develop changes" to the firmware that will work well with their apps. I found this out just today in a 3 way conference call between Nokia, Verizon and myself. Nokia admits that they are "re-developing" the software to work with Verizon's apps (My Verizon, VZ Navigator, Voicemail, etc.)
If you ask me, this is either plain STUPIDITY, or Verizon once again trying to squash the Windows Phone platform. These are APPs, not part of the operating system. These apps can be changed AFTER the Cyan firmware is delivered. There is absolutely NO reason the Cyan firmware has to be delayed for APPs! However, Verizon has decided they will not approve the firmware for delivery until their apps work "PERFECTLY" on the Cyan firmware update.
If this is what they are doing for the Cyan firmware update, how long do you think it will take them to deliver the Denim firmware update. I'm quite sure I'll be enjoying my Denim firmware update on my Lumia 1520 over on AT&T by then!
What a cluster #@!%#@. I'm guessing that Microsoft/VZW cannot get XLTE and VoLTE working properly. If they would have started this way back in July they might have had it finished by now.
I'm hoping that what ever is being fixed in Cyan can be ported over to Denim being it hasn't been officially released yet.
Part me is hoping that they are working on both firmwares in conjunction....
Wow so VZW can't even code their own apps (VZW Navigator (waste of money), My Verizon, and Visual Voice (another piece of garbage app) and has to have Microsoft do it for them... Sad....
primortal wrote:
Wow so VZW can't even code their own apps (VZW Navigator (waste of money), My Verizon, and Visual Voice (another piece of garbage app) and has to have Microsoft do it for them... Sad....
They don't code those apps... They are done by a 3rd party developer and branded Verizon. I used to work for companies that do that kind of stuff all the time. We had AT&T and Sprint as clients.
Tidbits wrote:
They don't code those apps... They are done by a 3rd party developer and branded Verizon. I used to work for companies that do that kind of stuff all the time. We had AT&T and Sprint as clients.
Thanks for the info. Still sad that Microsoft/VZW can't tell the truth and place blame on components that aren't even part of the firmware or OS.
primortal wrote:
Tidbits wrote:
They don't code those apps... They are done by a 3rd party developer and branded Verizon. I used to work for companies that do that kind of stuff all the time. We had AT&T and Sprint as clients.
Thanks for the info. Still sad that Microsoft/VZW can't tell the truth and place blame on components that aren't even part of the firmware or OS.
As a developer the possible reason why it went back into development would be a problem with the RIL. If I was Verizon and I was having trouble keeping connectivity with the network during testing I would sent it back as many times as needed. If they released the update and people had problem keeping connection a lot of people would blame Verizon one way or another.
I completely understand the testing but it's been 4 long months that Microsoft released Windows Phone 8.1 + Cyan and its now that they encounter problems with the firmware/OS. Like I mentioned before the only hold up I see is XLTE and /or VoTLE is being problematic.
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.
Can you imagine the outrage if VZW withheld iOS8 for non-iPhone 6 devices for this long....
rednibkram wrote:
This means that Verizon has decided that they want their software apps to work flawlessly with the new firmware update before they will grant approval of it, so they sent it back to Microsoft to "develop changes" to the firmware that will work well with their apps. I found this out just today in a 3 way conference call between Nokia, Verizon and myself. Nokia admits that they are "re-developing" the software to work with Verizon's apps (My Verizon, VZ Navigator, Voicemail, etc.)
If you ask me, this is either plain STUPIDITY, or Verizon once again trying to squash the Windows Phone platform. These are APPs, not part of the operating system. These apps can be changed AFTER the Cyan firmware is delivered. There is absolutely NO reason the Cyan firmware has to be delayed for APPs! However, Verizon has decided they will not approve the firmware for delivery until their apps work "PERFECTLY" on the Cyan firmware update.
If this is what they are doing for the Cyan firmware update, how long do you think it will take them to deliver the Denim firmware update. I'm quite sure I'll be enjoying my Denim firmware update on my Lumia 1520 over on AT&T by then!
I bet it doesn't mean that... I am willing to bet my house on it.
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).
It really URKS you that I am in a position to know more than you, doesn't it. Sorry, but no amount of "phishing" will make me provide you any information that you (personally) don't need to know. What I provide on this forum is TRUTH and FACT, and I provide it for the benefit of the paying customers of Verizon Wireless who are very angry, disappointed, frustrated and irritated over this entire Cyan firmware update fiasco that Verizon has created!
FACT: I spoke with Nokia and Verizon in a 3 way conversation where it was admitted by BOTH parties that the reason the Cyan firmware update was returned to Microsoft for re-development is because of the apps not working "perfectly" with the Cyan firmware upate. This has NOTHING to do with RIL whatsoever! You want proof, call Nokia Tech Support and ask them yourself.
FACT: Nokia (Microsoft Mobile OY) sent the Cyan firmware update to ALL U.S. Carriers on 15 July 2014, Verizon included. Want proof, call Nokia Tech Support and ask them, then call Verizon Tech Support and ask them. Neither will dispute this fact.
FACT: It was not until late October that Verizon sent the firmware back to Microsoft to request re-development for their apps. The only proof I will provide at this time is the Twitter tweet sent by Joe Belfiore regarding this fact.
FACT: Verizon Wireless has remained completely SILENT on this issue since day one! They have said absolutely NOTHING to anyone regarding this fiasco. [SUMMATION: If they are really so innocent, then why not show respect their paying customers and make a statement, an apology, a brief explanation, or SOMETHING to let us know it isn't their fault. If they aren't HIDING something, then they should SAY something! That's not a "requirement" of them, sure, but don't you think it would be the "moral and proper" thing to do for your paying customers as, at least, an attempt to satisfy them!? ]
With exception to the [ ] bracketed section above, nothing of what I have stated above is "my opinion." It is all FACT!!
It doesn't urk me. I just don't believe you because you claim to have done what thousands of people are not able to do. What media outlets have not been able to do as well.
All while showing no proof you have done this. How can you talk to the people in the know in a conference call? Yet NO ONE outside yourself can even pull that off. Right... Have at that one.
Last thing I am going to be saying about your lies...
Anyone who is a Windows Phone User wanting Cyan can't deny this as well and shows how much bull without evidence you say.
If this information is indeed fact pushing the evidence in the forefront would BENEFIT every windows phone users on Verizon. By you WITHHOLDING said evidence you are not helping your cause. This is how I know it's a load of bull with what you are saying treating hearsay and rumors as facts and trying to pass them as facts. Windows Phone Central would love to push your story if you had any factual information to give them and it would help get the word out there. Seriously If you are not going to share the information and evidence here share it with the media outlets. So why withhold this information and evidence if you want results?
Either that be quiet about what information you do not have...
Tidbits to refute rednibkram claims, why don't you call VZW support and have them conference Nokia in and ask them same questions rednibkam asked and see what they tell you.
You asking provide proof of a phone conversation and the only way would be to record it and post it. Support doesn't provide a transcript of the conversation; I think.
I've tried that more than once. It wouldn't surprise me others have tried as well. He also made other claims not just that conference call. He said he had emails with Verizon CEO's explaining things to him because of the FCC dealings yet others who did the exact same thing have even yet come close to talking to a CEO. A lot of things don't add up. The best I got were LOW LEVEL employees who wouldn't know what is going on in another department is happening. I even asked to escalate it and I couldn't even come close to anyone who would know.
Fair enough
I agree. This so called executive calls and letters just don't add up.
If you read the former "complaints" he posted on not getting a Android Update it is a wash, rinse, & repeat cycle. On his part.
And for all this complaining it shows you were correct in that it was not actually approved by Verizon and Microsoft indeed had it.
So his first claim of what Verizon and Microsoft said to him "that it was at Verizon and the carrier has to release it" shows it was bogus.
Start a new topic or ask questions in the open forum.