Might as well get the big one that goes right to 5.7 and keeps the webtop.
Easily upgrade to 5.7.893, keep root AND webtop now - xda-developers
For example, we have a machine that tests our equipment that we send to customers. It verifies all ports and buttons are working, as well as the software loaded and responding to commands (114 tests in all). Get it to the customer and have it hooked up and it won't even respond to input and won't load the latest firmware. A 'test' environment does nothing for real world implementation. My job is proof of that.
All devices have a life. Some last their expected life or longer, and others last 10 minutes. They are all built on an assembly line, from other devices built on an assembly line, from possibly others built on an assembly line.
But, you have to understand, software testing is very deliberate and methodical. Especially bug fixes... as I said, if the user doesn't know what the conditions are that trigger the problem, then they cannot deliberately test that, but instead it's left up to chance to see if those conditions arise and see how the software responds. You cannot leave software testing to chance like that. Beta testing is usually left to a small group with the specific purpose of trying to break the code, not just using it as a casual customer would day to day.
And, finally, unless the "testers" are documenting precisely what they are doing to create a problem, a software developer reading this forum has no way of knowing if the "reported" problem is the same one being tried to fix, or a totally new problem that "looks" similar but is triggered by something else.
Or, maybe I'm just giving Motorola too much credit?
I was trying to simplify a complicated process to the casual reader that may not understand the development/test/fix/test/release process.
I agree with your statements, but its my experience that what you speak of usually involves new development. Once you have identified certain bugs in the initial test release, you can be MUCH more specific in your research into what exactly is causing the problem, so you can then identify why the logic is not handling those conditions properly. Likewise, the testing is much more specific too. It is not left to chance as to whether the conditions have even occurred, thus not triggering the faulty software execution, as proof that the software is fixed.
Unless the casual user knows exactly how to trigger the faulty code execution, letting them use it and say it works fine does nothing to tell me if the problem is fixed, however I will give you that if even one person reports the problem has recurred, then I could be fairly sure the problem wasn't fixed, and that perhaps I don't correctly understand the triggering conditions or have simply not corrected the faulty logic.
I guess I'm just stating the obvious fact that the testing means nothing to "real-world" performance.
You are speaking just of test/fix/test/release.
But still after release, equipment still has issues, which is the overall issue with software OTA's in general IMO.
In a perfect world, software/firmware developers have all the time in the world to test and test and test their code to ensure it is bug free before releasing it.
In the "real world", there are other constraints (primarily cost) that limit how much testing gets done. Smaller companies are usually on tighter deadlines, and are guilty of taking shortcuts, with the understanding that they will probably have to fix bugs later, but at least they are able to release their product and get paid.
I don't think Motorola is this type of company. At least I'm assuming they are not, and that they have the resources to ensure their testing mimics the "real world" as much as possible. The fact that this problem of data dropouts would appear to be in an area of expertise (radio communications) for Motorola, and that they didn't catch this problem is very telling of either a deficiency in their testing/QC/QA departments, or that it was a management decision to forge ahead with the release despite the issues present in the phone.
I'm going with the latter.
No matter how they test the patches, one thing is clear - Moto has no idea what the problem is. The fact that there are 3 leaked updates and no fix shows that they are simply shooting in the dark. Not very encouraging.
I would be more than happy to let Moto folks come and pitch a tent in my yard so they can see the issue firsthand and work on a solution, rather than spamming people with "leaks", people who are already beyond tired of dealing with this issue in the first place.
I agree. The problem is that there is no recourse for the customers of such phones. I have not heard any of those companies recalling phones or generally compensating their customers for such actions.or that it was a management decision to forge ahead with the release despite the issues present in the phone.
I'm going with the latter.
I am not big government fan, but makes me wonder what's up with FCC and all those consumer protection agencies. How about we get some value for our tax dollars here?
Last edited by atlrus; 11-11-2011 at 02:44 PM.
Sent from my DROID BIONIC using DroidForums
(Verizon) Samsung Galaxy S4 - Rooted - VRUAMI1 (STOCK) | (Verizon) Casio (GzOne) Commando 4G - Rooted - C811M020 (STOCK)
I hate to say this but Motorola has no clue what is wrong with the data connection issues. Both Verizon and Motorola admit to the problem but the Bionic has been out over 2 months with no OTA fix set to be released. Surely if they had a fix for the data connection problem they would have released a fix for that issue and included it in the RAZR as well. They could always work on the smaller bugs after doing a hot fix on the radio.
I have had no data connection on my Bionic all day today and all I am being told is 30-60 days for a fix. I have a feeling that Verizon's network is partly to blame for this. I believe for some reason the Motorola 4G phones have a difficult time connecting to the towers. This problem seems to be affecting many but certainly not all of the phones and this is what makes me believe that a true fix is not coming anytime soon. Verizon is gambling by releasing the RAZR with such a defect. Only time will tell if the next 2 Verizon phones (the Nexus and the Rezound) have a similar issue. If they don't, I think Verizon is going to see a lot of angry Motorola owners demanding an exchange. I know I will be among them.