Quote:
Originally Posted by visitador02
How to avoid similar occurrences in the future? Well, as Michael stated in his blog awhile ago, a smartphone is like a computer. Customers should start treating their phones as such and understand the limitations of software upgrades.
|
I think most people understand that. However, this wasn't the case here was it? The hardware was perfectly capable of handling the new OS version.
Of course if the hardware does not meet the requirements of the new software version, it would be silly to still demand an upgrade. That is not what I'm saying however. What I'm getting at is that Android is a platform that will continue to pick up speed from here on. There will be a lot of more phones, a lot more upgrade vectors. More importantly, there will be new versions that are supported by the current (or future) generation of hardware and there might be no technical limitations that prevent the upgrade. Is Rogers or HTC prepared to allow smooth software upgrades then? The times when your "phone" (if we can still call them "phones") was just an appliance, and once you bought it you kept it as it came out of the box, are over. Rogers and partners should understand that because customers, and developers such as myself, definitely do and will be expecting that.
The long term goal of the Open Handset Alliance was to smooth out issues like this, if carriers and manufacturers work together to accomplish those goals, their costumers and the companies themselves will see gains from this. Listen, I am glad that the immediate problem was fixed but I see this "Rogers Dream 1.6 Update" mess as a symptom of a bigger problem.