[HTC One X] BarryH_GEG:
For what they're worth, here are my thoughts:

- I don't think HTC knew about the graphics issues before the phone shipped. None of the dozens of devices shipped to professional reviewers displayed the issue(s) nor do a large percentage of production units. For all the bluster in this thread there were only about 30 people that put their names on the pledge list. I don't know how many phones have been sold but I'm sure it's in the tens of thousands.

- I do think they began taking the issue seriously as soon as it started appearing on more than just a handful of devices. From earlier postings linking to articles and videos from Taiwan, HTC's base, it was know there before it became a big deal here. The implication that their not taking a serious launch issue with their flagship phone to heart is both ignorant and unfounded (at least at this point).

- Seeing an issue present itself is very different from identifying with certainty what the underlying cause is. The more random the issue the more difficult it is to identify. Once it's identified developing a fix is done in two stages. Actual coding followed by exhaustive testing. If the fix was thought to be identified but issues are still found in testing the process starts over and repeats until the problem is 100% resolved. And since it's random and doesn't affect every phone that makes testing more difficult. Add to that that because it's most likely a Teg3 related issue both Nvidia and HTC are involved adding time to the process as code is provided by Nvidia and then incorporated in to HTC's s/w and tested.

- HTC's not incompetent. The XL, S, and V seem to be having fewer technical launch issues than most recently released Android devices. Devs have commented that the One X's issues are most likely s/w and related to the video drivers developed and released by Nvidia. It makes sense because the XL's almost an identical device but isn't having any similar issues.

- Communication wise HTC has two choices, neither of them good. 1) Come out and say there's a problem and, at this point, they haven't dug in deep enough to say what it is or when it will be resolved, or 2) Use back channels like the communication shared with XDA to convey they're working on a fix while holding back on anything formal until they have more to say. Damned if you, damned if you don't. The Asus Prime had more Teg3 issues than the One X and Asus communicated their awareness of the issues and that there was no ETA for the fix. People went nuts so picking option one over two doesn't stop the *****ing, it only changes what it looks like.

Some of you are on your sixth exchange and/or seventh duplicate post saying how disappointed you are with the phone/HTC, how fearful you are the problem could be h/w, and how your life will be ruined because of the limbo we're currently in. Just return the phone. Re-buy it once the fix is announced or follow through with your "HTC, never again threat" and buy a SGS3 when it's released. So far, nothing leads me to believe that this problem won't be resolved and/or that HTC is going to abandon or mistreat their prized early adopters when they're trying to turn around a miserable 2011 and Q1 2012.

You all need to do what you think's best and if that's an endless succession of duplicate and irate posts so be it. But there's more melodrama in this thread than fact and the outcome, either positive or negative, faster or slower, won't be determined by our random musings. And onine media coverage isn't going to do a thing if in fact Nvidia and HTC are applying all the resouces they can (which I believe they are) to getting this resolved. There's an old adage, "nine women can't have a baby in a month." There's another one, "good things come to s/he who waits."