I did a fair amount of reading on what people think of the failed 2.1 update. I have visited several forums, read a bunch of articles and the associated comments on the 2.1 update and have come away feeling that a large number of people are pointing at this being a deliberate, and calculated move on the part of Verizon. A poster in this thread has even used the term "bait and switch"..... What bait and switch? Where is it, because if it's there, i haven't seen it.
Why can't people just accept that something went wrong, and whatever that thing was, it has delayed the release of the update. We can't do anything about that. How many people here have planned something, and have had something go wrong? How many people have planned something, and have executed perfectly, every time? Has anyone considered that this was just one big "cock-up" because someone, somewhere along the way dropped the ball?
Pushing out this OTA is, I would guess, a highly technical and complex activity that requires a certain set of systems has to work together, and as flawlessly as possible to execute the transmission of the update. On the 18th, something didn't work right. And now that problem, whatever it is is being taken care of. Why can't the simple explanation, which really amounts to an "oops we goofed" be the acceptable one? Why must everyone gas on about lawsuits, and patent rights, baiting and switching, corporate greed, and conspiracies? Motorola said the update was coming on the 18th. From all accounts (thin as they are) they started to do that on the date they said they would, and then the fertilizer hit the fan, and they couldn't do what they had said they were going to do. I realize, that from a corporate and customer service standpoint, that this is a big deal, and that Motorola should have made sure that things were going to work, after all the 2.0.1 update went out without issues. I realize that Motorola has a responsibility to it's customers to follow through on promises. No one can deny, or argue that... but, sometimes, things just get messed up, and when that happens, the mistake has to be identified and corrected, and then the plan attempted again. I think that is happening as we speak... err, write, and we will find something out soon enough.
Mistakes happen, machines break, rain falls, electricity fails, cars break down... sometimes things are what they are. Of course, steps can be taken to minimize what the British would call "cock-up potential", in an plan, but, remember, the operative word in the last statement is "minimize" not "eliminate". Do we know what happened? No, Motorola and Verizon aren't talking, and they probably have a good reason for it, but that doesn't mean it isn't being taken care of, nor does it mean they are actively trying to screw people over.
Something went wrong with the update, and now we have to wait. Sometimes, it is what it is, and nothing more.
