gsh wrote:You say 5% is that across all devices (i.e. are you finding that any device fails 5% of the time, in which case I should be able to reproduce the problem here)
To be accurate, we re-ran the test. Our text procedure is to repeatedly reboot. Each time, we make sure we see a cursor and then test the functionality of the touch via an app with a button. The test automatically repeats the boot every 90 seconds.
We have 3 machines (say, A, B, and C). With 3 machines booting every 90 seconds, we get two boots per minute. We ran the test for more than an hour, so we totaled about 150 boots.
During this sequence, we got 4 Display failures and 9 Touch errors, distributed as follows:
A had 2 Touch failures and 2 Display failures
B had 7 Touch failures and 0 Display failures
C had 0 Touch failures and 2 Display failures
Touch failures occur when either the cursor is absent, or it is frozen. A reboot always restores the Touch failure. On some occasions, the cursor is totally absent, but on others, it appears and is frozen. Our application comes up 10 seconds after boot and the cursor lands on its edit pad, and we see the cursor frozen as a vertical bar (text), so it seems to have frozen after some delay from the boot.
Display failures occur when the screen appears incoherent, grey, random pixels. A reboot does NOT correct the Display error, although on one occasions, it came back after a few reboots. Otherwise, Display errors require a power cycle.
In no cases were the failures due to boot failures... I puttty'd into the machine and it continued to work ok.
Hope this helps.