• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Eris to v2.x, when?

I can honestly say that that is the strangest yet most flattering compliment I have received in quite a while. ;)



Oh OTD... How you enjoy teasing the boys and making them all butterflies with your feminine wiles. Your craft has been cultivated through many years of trials. I will not bow to your tricks or your female guiles. Search else where for your blood thirsty lust of male childs. All you will find in me are rejections and denials...:rolleyes:


so... how about that 2.1? I hear its gonna be swell
 
I still think Verizon doing weeks of tests on a phone that was made FOR them by HTC, to their specifications, is silly. Especially a model whose hardware is known and thoroughly tested.

I mean it is rather like me giving my new Honda Accord to a mechanic for weeks of testing to determine if my engine works and has the options I ordered, after Honda just spent some months testing it in every way they could imagine.

Pre release candidates and ad hoc hybrids are one thing. A supposedly finished product, created to my specifications, delivered by the manufacturer, as a software update to a known and well tested model, should not take weeks to determine if it works as expected. I can tell in a few hours if my new version of Ubuntu more or less does what it is supposed to and functions as well or better than my old OS.

There are always going to be minor patches needed to any new OS, but the basic functionality should be VERY easy to determine. I can tell in five minutes by looking at that video OfTheDamned put up that 2.1 functions fairly well on the Eris.
 
... How you enjoy teasing the boys and making them all butterflies with your feminine wiles. Your craft has been cultivated through many years of trials. I will not bow to your tricks or your female guiles. Search else where for your blood thirsty lust of male childs. All you will find in me are rejections and denials...:rolleyes:

Haha the chickies like her too ;-)
 
I still think Verizon doing weeks of tests on a phone that was made FOR them by HTC, to their specifications, is silly. Especially a model whose hardware is known and thoroughly tested.

I mean it is rather like me giving my new Honda Accord to a mechanic for weeks of testing to determine if my engine works and has the options I ordered, after Honda just spent some months testing it in every way they could imagine.

Pre release candidates and ad hoc hybrids are one thing. A supposedly finished product, created to my specifications, delivered by the manufacturer, as a software update to a known and well tested model, should not take weeks to determine if it works as expected. I can tell in a few hours if my new version of Ubuntu more or less does what it is supposed to and functions as well or better than my old OS.

There are always going to be minor patches needed to any new OS, but the basic functionality should be VERY easy to determine. I can tell in five minutes by looking at that video OfTheDamned put up that 2.1 functions fairly well on the Eris.

I agree.



Sent from my Eris using Tapatalk
 
Based on the fact that there are clearly copies of 2.1 seeing day-to-day use -- and successfully so, according to the leaked video -- I tend to agree that unless some unexpected and particularly evil bug shows up we're probably pretty close to the end of the testing process. HTC clearly accomplished all the heavy lifting on this upgrade some time ago ... and we're probably at or near the point where further testing wouldn't be too cost-effective.

That said, as long as testing is going on I doubt that anyone knows with 100% certainty when the update will be released. That's going to be in a state of flux until the monitoring of the test devices is completed -- only then will a decision be made, and at that point we should get the update fairly quickly.
 
I still think Verizon doing weeks of tests on a phone that was made FOR them by HTC, to their specifications, is silly. Especially a model whose hardware is known and thoroughly tested.

I mean it is rather like me giving my new Honda Accord to a mechanic for weeks of testing to determine if my engine works and has the options I ordered, after Honda just spent some months testing it in every way they could imagine.

Pre release candidates and ad hoc hybrids are one thing. A supposedly finished product, created to my specifications, delivered by the manufacturer, as a software update to a known and well tested model, should not take weeks to determine if it works as expected. I can tell in a few hours if my new version of Ubuntu more or less does what it is supposed to and functions as well or better than my old OS.

There are always going to be minor patches needed to any new OS, but the basic functionality should be VERY easy to determine. I can tell in five minutes by looking at that video OfTheDamned put up that 2.1 functions fairly well on the Eris.

While I see what you are saying, where do you think the pre release candidates for OS updates come from? Most of them are tested and scrapped versions of the final product that is released to the end user.

Everyone likes to make car analogies to smart phones, so try this one instead. Verizon testing and releasing a new OS on a smart phone is like Mercedes releasing a car with a brand new engine. Now, they have the car design down and they may have made a few alterations here or there, but overall the car is pretty much the same as last years model, save the engine. The engine was designed by Mercedes and tested by Mercedes, but they aren't going to just drop it into a car and start shipping them out, are they? They will do road tests, lab tests and endurance tests on the new engine inside the new car before it is ever made available to the public. After they are satisfied with it, then it has to be tested again by government agencies to make sure that it meets or exceeds the standards set forth by that agency. All that being said, you are still talking about mechanical stuff. Software adds a whole new level to it.

Maybe not the best analogy in the world, not really that into cars honestly.:o
 
While I see what you are saying, where do you think the pre release candidates for OS updates come from? Most of them are tested and scrapped versions of the final product that is released to the end user.

Everyone likes to make car analogies to smart phones, so try this one instead. Verizon testing and releasing a new OS on a smart phone is like Mercedes releasing a car with a brand new engine. Now, they have the car design down and they may have made a few alterations here or there, but overall the car is pretty much the same as last years model, save the engine. The engine was designed by Mercedes and tested by Mercedes, but they aren't going to just drop it into a car and start shipping them out, are they? They will do road tests, lab tests and endurance tests on the new engine inside the new car before it is ever made available to the public. After they are satisfied with it, then it has to be tested again by government agencies to make sure that it meets or exceeds the standards set forth by that agency. All that being said, you are still talking about mechanical stuff. Software adds a whole new level to it.

Maybe not the best analogy in the world, not really that into cars honestly.:o

I'm a test engineer, and this is certainly a much more accurate analogy when refering to testing, at least through my experience. People are very afraid of software and consider it high risk, so they will have a very long test period for software, no matter how much it was tested by Google or HTC. I mean Google released 2.1 a while ago, and does the Droid have it yet? Motorola doesn't even need to test a proprietary UI, just the vanilla OS on the phone. Think how anal Verizon is being with the Eris having another layer of software involved.
 
While I see what you are saying, where do you think the pre release candidates for OS updates come from? Most of them are tested and scrapped versions of the final product that is released to the end user.

Everyone likes to make car analogies to smart phones, so try this one instead. Verizon testing and releasing a new OS on a smart phone is like Mercedes releasing a car with a brand new engine. Now, they have the car design down and they may have made a few alterations here or there, but overall the car is pretty much the same as last years model, save the engine. The engine was designed by Mercedes and tested by Mercedes, but they aren't going to just drop it into a car and start shipping them out, are they? They will do road tests, lab tests and endurance tests on the new engine inside the new car before it is ever made available to the public. After they are satisfied with it, then it has to be tested again by government agencies to make sure that it meets or exceeds the standards set forth by that agency. All that being said, you are still talking about mechanical stuff. Software adds a whole new level to it.

Maybe not the best analogy in the world, not really that into cars honestly.:o

The only difference between a car and phone software is that a car can potentially kill people if not tested right. A phone on the other hand can just piss somebody off. Just my .02.
 
While I see what you are saying, where do you think the pre release candidates for OS updates come from? Most of them are tested and scrapped versions of the final product that is released to the end user.

Everyone likes to make car analogies to smart phones, so try this one instead. Verizon testing and releasing a new OS on a smart phone is like Mercedes releasing a car with a brand new engine. Now, they have the car design down and they may have made a few alterations here or there, but overall the car is pretty much the same as last years model, save the engine. The engine was designed by Mercedes and tested by Mercedes, but they aren't going to just drop it into a car and start shipping them out, are they? They will do road tests, lab tests and endurance tests on the new engine inside the new car before it is ever made available to the public. After they are satisfied with it, then it has to be tested again by government agencies to make sure that it meets or exceeds the standards set forth by that agency. All that being said, you are still talking about mechanical stuff. Software adds a whole new level to it.

Maybe not the best analogy in the world, not really that into cars honestly.:o

I think that is pretty much the best way it could be said. Like everyone else, I am trying to stay patient. We wouldn't want 2.1 to be rushed too much, or we may have a Toyota-like fiasco on our hands....:eek:
 
The only difference between a car and phone software is that a car can potentially kill people if not tested right. A phone on the other hand can just piss somebody off. Just my .02.

Very true, but a poorly tested phone can kill business. Verizon has a good reputation for customer service for a reason. Testing phones to make sure they work and aren't going to piss off an entire group of customers is a part of that.
 
I guess all I am saying is that this is more like the Mercedes dealership doing its own testing after the engineers have done the testing on the new motor, say it is definately ready for production, produced it and the data to back up its performance, and delivered it to the showroom.
 
Very true, but a poorly tested phone can kill business. Verizon has a good reputation for customer service for a reason. Testing phones to make sure they work and aren't going to piss off an entire group of customers is a part of that.

True, I just think that they should give us a beta or something just to let us try it and stop us from waiting.
 
Very true, but a poorly tested phone can kill business. Verizon has a good reputation for customer service for a reason. Testing phones to make sure they work and aren't going to piss off an entire group of customers is a part of that.


  1. Verizon customer service has taken a beating over this new mandatory data fee thing
2. The phones end up needing patches and updates regardless of how long they wait, so they might as well not annoy us by making us wait forever and still have to send out patches anyway.
 
Yep, releasing a new os is definitely a big deal, even for something like a mobile phone. There are multiple levels of testing, spread out over weeks our months.

The thing is, though, we really have no absolutely definitive knowledge of what stage of 2.1 testing they're in. I'm guessing they're pretty close to the end, but it's just a guess. The os on that video looks pretty damn polished, though.
 
HTC and other testers have obviously been using this ROM daily for weeks already. By all accounts it works. Send in the clones already.

You know they will be sending out 2.1 patches and updates for the next six months anyway no matter how long they sit and redundantly test it. There have been three updates since i got my Eris in December, and that is after they supposedly tested it to death prior to launch. It will never be perfect.
 
... and of course, they're not going to test it until it's perfect. They're going to test it until they think it's no longer cost-effective to do so; that is, until they think the overall cost of continued testing is greater than the overall cost of releasing bugfixes, combined with the likelihood of increased system costs relating to a possible undiscovered bug.
 
I guess all I am saying is that this is more like the Mercedes dealership doing its own testing after the engineers have done the testing on the new motor, say it is definately ready for production, produced it and the data to back up its performance, and delivered it to the showroom.

The dealership would actually be the Verizon store and they aren't doing the testing. The testers are like the little German engineer guys at Mercedes.

True, I just think that they should give us a beta or something just to let us try it and stop us from waiting.

Now why int he world would anyone that uses their phone for business and personal data want to run a beta OS? Seriously think about that for a minute. Do you want to have all the information that you store on your personal phone running a beta OS? I sure don't.

  1. Verizon customer service has taken a beating over this new mandatory data fee thing
2. The phones end up needing patches and updates regardless of how long they wait, so they might as well not annoy us by making us wait forever and still have to send out patches anyway.

1 - They did start getting yelled at for it. They have had mandatory data in place for a while now for smart phones. Adding it to their line of "feature" phones that suck data just as much doesn't seem like a big deal to me. Just my opinion though.

2 - If you really think we have been waiting such a long time for an update don't ever buy a BlackBerry, iPhone or WinMo phone. Those folks get updated maybe, just maybe once a year and not even that in some cases. We have been waiting for a few months, it really isn't that long.
 
Now why int he world would anyone that uses their phone for business and personal data want to run a beta OS? Seriously think about that for a minute. Do you want to have all the information that you store on your personal phone running a beta OS? I sure don't.

They don't have to make it mandatory. Just give us the option. What's so bad about beta? It's not like the guy just got done writing the code, it's been out for a while so I wouldn't worry that much.
 
Back
Top Bottom