How is it a 2.1 issue, since Desire, Inc and N1 do not have the cap? Seems it is a driver issue done intentionally. HTC got caught and now are in damage control mode. At least they are now looking at correcting the cap.
"Beer", it's what's for dinner.
I'm not saying it isn't strictly an HTC EVO problem - it's obviously that.
I am saying that we don't know what they did, or what else they did, just by having one thing addressed in that kernel mod.
I am also saying that it's more reasonable to expect the fix to come as part of 2.2 -
not because of 2.2 - as a part of it - because all of the device-dependent stuff is necessarily addressed in any major revision.
And this isn't a PC, it's an embedded real-time OS, so things are rarely as simple as we want them to be.
Even I talk and conjecture about this being part of power management - BUT - here's all we know:
1. They had a deadline to get the EVO out.
2. They put this cap in to fix or cover up something in the rush to integrate all of the new features in this phone. There's a few firsts here, yes?
3. It seems perfectly reasonable to expect a fix - I include myself.
The part I object to is the name calling and the charges of malfeasance and idiocy on HTC's part, along with everyone who has not fielded a real-time OS with a lot of new firsts trying to tell me how everything's just so easy.
I'm more liable to read all of HTC's newly changed responses like this:
- We knew what were breaking when we did that.
- We are covering up another problem with that breakage - not deflecting attention from whatever it is - covering it up (maybe some race condition or something - who knows?).
- We already know in the general sense that we can fix it.
- We already know how long it's going to take in general terms.
- Not today, soon, we're "investigating" it.
- What else do you want us to say when the competition - who has the luxury of getting to market later with fewer requirements on their device - is all ready to spank us?
The EVO's been publicly available less than 4 weeks - 27 days.
I've been enjoying mine for 24 of them, despite the world ending with:
- battery performance
- 30 fps cap
- something screwy with wifi signal strength (not so sure that's limited to just the status bar display but that's another one of my opinions)
Anyone having problems with dust under the display, glass lifting, grounding issues, screen vibrancy/wash-out issues or that sort of thing, I'd advise to seek immediate warranty relief.
For the rest of that list, I stick by what I wrote in my initial post in this thread: for those of us can keep their shirts on, this isn't that big a deal.
If you disagree, fine, take your business to another bleeding edge device and see what early delivery problems those may have. Myself, I don't know how we'll know that without having to wait for actual release into the wild of the Droid X, the Epic 4G, the.....
But if you think the next guy won't cut corners to meet a deadline, I've got a bridge that you might be interested in.
That's all I was trying to say.
