[HTC One X] BarryH_GEG:
OK guys, the more that's reported, especially the intermittent nature of the problems, the more I'm convinced the issue is Teg3 related.

I followed the Asus Prime's launch from the beginning and it had very similar issues that all turned out to be either code or drivers related to Teg3. It took Asus/Nvidia four updates to finally stabilize everything.

The One XL is out now and even though there aren't a lot in people's hand you'd think this would have popped up on at least one if it was common to the One X family. The One XL has a different SoC, kernel, and graphics drivers than the international version while I'm assuming the majority of the rest of the s/w is the same. So as long as it's unaffected you can draw the conclusion that the international version's issues are either Teg3 h/w or related s/w.

The good news is that the majority of issues were eventually resolved on the Prime. But just like Asus, HTC is dependent on Nvidia to identify, isolate, and release new code to correct the issues because their s/w and drivers are proprietary. Having two companies involved is certainly not going to speed up the process. Just like the One X, not every Prime had the issue(s). And when early updates were released devices that were fine suddenly had problems and devices that were broken were fixed. No one from Asus or Nvidia ever explained why devices with identical h/w and s/w behaved differently. My guess is that there are unforeseen variances between individual Teg3 chips and the s/w adjustments were made to enable the s/w to account for them. So while this isn't an answer or a fix hopefully it helps better frame the problem.

I snipped some posts from the Prime forum so you can see that a theme similar to what we're experiencing exists. The first couple are from an Asus manager that participates in the Prime forum.

~~~~~~~~~~

3/22/2012 Update –

The next firmware update is in qualification testing now. We are also working on solving some flickering problems reported by a few users and hopefully that will be addressed in this next release.

~~~~~~~~~~

4/2/2012 Update -

In addition, I have gathered additional details from a few users who are seeing locks or weirdness after playing a Tegra 3 optimized game after a few hours. I will be in California next week to work with NVIDIA and Google on this problem.

~~~~~~~~~~

2/1/12 Update - We received new code from NVIDIA today and are in the process of testing it. If this code is acceptable and provides a solution to the lock/reboot problem after the ICS update, we will release it in beta form for additional testing

~~~~~~~~~~~

2/7/12 Update - We received another new code update from NVIDIA for testing today. Hopefully we will be able to release a beta patch or OTA update shortly. I will have an update after testing is completed tomorrow.

~~~~~~~~~~

THE INITIAL ANDROID 4.0 UPDATE (BUILD 9.4.2.11) CAUSES FREEZES/REBOOTS FOR SOME. BUILD 9.4.2.13 FIXED THIS, BUT INTRODUCED A NEW BATTERY DRAIN ISSUE FOR SOME OTHERS. A FIX IS EXPECTED VERY SOON.

it is now believed that bugs in nvidia's tegra3 video drivers were the cause of freezes and reboots that some experienced after making the initial ICS update (build 9.4.2.11).

asus shipped new drivers with build 9.4.2.13 on 2/8/12 that fixed these issues, but a new battery drain issue was introduced that affects some others. this battery drain has been referred to as the "sleep of death"

asus confirmed on 2/14/12 that a fix has been developed for the battery drain and should be released within a week

~~~~~~~~~

I went 36 hours after the initial ICS update without a problem and then a sudden reboot. I then had no issues for another day of normal use. Then a reboot. No pattern at all and definitely not when playing games when the CPU/GPU was being stressed. So not a thermal issue. This reeks memory issue whether the storage or ram and could be bad code or bad memory.

~~~~~~~~~~

Wondering if any one else has had this issue. The left edge developed a series of blocks that would disappear when I touch he screen, and then reappear when I stopped touching the screen.. The issue persisted into app browser, but reappeared while playing a video in mx player.. It appeared again after I quit mx.

~~~~~~~~~~

I took screenshots, via the app switcher button throughout, and I can see the corruption in the shots, and so I suspect its a software issue and not something in the display itself. Screenshots will follow once I compression them a bit.

~~~~~~~~~~

Today I was playing zen pinball and i pressed hardly for the right flipper and this screen flickering again. Starting with the bezel when I apply pressure to the right bottom part of the tab the screen flickers into white. I don't think it is a common issue.

~~~~~~~~~~

I find I can replicate screen flickering just by tapping the recent items button after having a dozen apps/pages stored there. A reboot fixes it but it comes back later.