MrMP in regard to Lollipop

[Salisbury]

   Have read some of your earlier post you make excellent points and glad to see you speak up. I've worked extensively will computer hardware replacement, installing operating systems, drivers, etc. along with multimedia since 1998. And have participated with Microsoft and Apple support forums for years. In fact some years back Apple emailed me to ask if I'd willing to run a version of QuickTime, before it was released to the public.

  In all those years I have never seen the magnitude of such problems with a computer operating system, as Lollipop is showing by the numerous posts. It would appear that most problems with Lollipop are the result of hardware drivers. Which you have no control over, where Lollipop is installed by way of the cellular network, and obviously not tested properly before release.

  You are at the mercy of Verizon who don't have a clue, you obviously have seen that just reading their responses. So basically this forum is a waste of time as far as getting anywhere with Lollipop.

  If you are under contract with Verizon you can void the contract. I can tell you how to go about that. But they'll likely delete this post first. They don't like anyone rocking the boat, from their normal nonsense.

[Tidbits · Accepted solution]

It's not Verizon job to test those things. People believe they should, and would be so if they actually touched the code. The problem lies with the OS itself and there is documentation even from Google(You can find the specific bugs people complaining about from AOSP) about in through their bug pages. If Samsung did their job then the problems would be only on the Verizon model, but it happens on the other models as well including overseas.

Of course everyone will find some justification why the carrier is to blame. Even though overseas shows more and often better results in the long run blaming the manufacturer when it comes to shoddy code.

[B33]

Well the thing I guess I just don't understand is all of these updates go through the Soak Testing unless that requirement has been removed if there's a place to stop the update why not there or as what I stated before but in another way there are person's" with enough power that pushes the update so hard the soak testing is just overlooked and the update comes out anyway..

To me if there was a last place point to put a hold on an update the Soak Test was the Game stopper in shutting down the update for it to be reworked..

[Salisbury]

  Agree it is not Verizon that should test Lollipop. Samsung produces the building of the Galaxy s5 with many companies from all over the world making parts for it. Android 5.0 is developed using many software engineering companies as well. Verizon simply delivers the installation of the operating system. But as posted by NrMP. Verizon continues to make lame post in regard to Lollipop.

  It's not about throwing Verizon under the bus. It's more about, is there any light at the end of the tunnel, after a month?

If someone is under contract with their Galaxy s5 and don't have another smartphone to switch to with the same contract plan, or are not in the position to buy another smartphone at full retail, then they're not in a good situation.

  So it seems they just wait it out, or does insurance cover it? So at some point you have to move on, get a workable smartphone, and get out of the contract. Is that reasonable thinking to you? Don't know how these stars come in with correct answers here. I think MrMP made great post.

[Tidbits]

The problem lies with support. Verizon is bound by support agreements and if Samsung says only this version will get support. Their tech support will force you to update to get any support unless your device doesn't turn on. Verizon and carriers are bound to push their updates and if it isn't "downgradable" from the manufacturer. Carriers and manufacturers are forced to deliver these updates in a timely manner. Regardless  if the carrier doesn't want to deliver the update look at all the hoopla that gets. I have always said it's  a catch 22 in the states because they are messed up either way. Europe if you see the amount of updates they get. They sign contracts too with their respective carriers and yet they still blame the manufacturer. Yes they do carrier testing just like the USA does (Sony AOSP project with Google confirms this) when it comes to network connectivity and nothing else. So if you look how often and how fast they get updates doesn't that make you wonder just a little? The USA Galaxy Note 2 has gotten 3 updates total to date from what I remember, but the European version has had like 7-8 in the same time frame.

[Salisbury]

  I read about 3 sentences of your post. The operating system is a failure. Pathetic!

[Tidbits]

Just read the last 6. It'll make a difference if people actually applied it, but of course that would be to hard for us Americans and the manufacturers know it.