Quote:
Originally Posted by dew.man
- has anyone actually tried the fix proposed by the OP, or did we all just jump on the soap box?
|
Yeah I'm waiting on a confirmation here. Or the 1st guinea pig.
BTW this whole thread has had my jaw gaping.
I honestly can't believe HTC is getting end user defense here with this issue. Many recent HTC devices are having the same driver issue, there is simply no valid excuse for it. Not only was it not physically obvious. It was nether stated in a written omission, spec omission nor an officially announced omission, pre-distribution from HTC or the carriers. Its is also a standard feature.
Its broadly acknowledged as an issue, not a misunderstanding or a multitude of assumptions.
A number of you took this issue on the chin and actually find no fault in it.
Some of you should really look into things like this with shaper eyes. Even if it was accidental, If someone can get over on you to save profit, time and/or effort, they are most likely to take advantage.
Heh, after reading through here IMO, some of you would probably shrug if you bought a qwerty keyboard smartphone only to find it only had those six keys with a 6sec entry delay.
So anyway, who is going to play pioneer with the ATI.cab?