Understanding multitouch limitations

[Guest jimmy2x2x]

Im looking to understand the limitations of the Blades multitouch screen

Im running Froyo alpha 1, with these 2 applications from the market:

Multitouch Tester

Multitouch Visualizer

(both applications yield the same results for me)

Using a single touch (1 finger) the tracking seems accurate and is as expected.

Multitouch Test:

Position 2 fingers on the touchscreen, one on the left of the screen, one on the right, both about half way up the screen.

Move the left finger up, the right finger down and alternate this movement so when left is going down, right is going up

if I repeat this a couple of times the tracking seems to get confused, switching the X coordinates of the tracking indicators!

In this scenario both tracking indicators are showing on the screen where there isnt any screen press!

Something like this:

1 and 4 are the actual finger positions on the touchscreen

2 and 3 are the reported positions in the test software

**************

*...1............3..*

*.....................*

*.....................*

*.....................*

*.....................*

*.....................*

*.....................*

*...2.............4..*

**************

Edited October 30, 2010 by jimmy2x2x

[Guest Acathla-]

Same as the multi touch on the Nexus One. This was a big issue when the Nexus first came out as the HTC Sense phones don't have this.

I guess I can't think of many actions that in normal usage would cause this multitouch bug.

[Guest jimmy2x2x]

So it is a limitation of the screen and not a defective unit?

[Guest thomas01155]

Wasn't there a big thread on this before?

[Guest spoonium]

http://android.modaco.com/content/zte-blad...range-san-fran/

[Guest blackmath]

Same as the multi touch on the Nexus One. This was a big issue when the Nexus first came out as the HTC Sense phones don't have this.

I guess I can't think of many actions that in normal usage would cause this multitouch bug.

Well the HTC Desire had the problem. Which isn't surprising as its pretty much a Nexus One.

But this was fixed in subsequent phone Droid-Incredible/Evo 4G/Wildfire etc.

Edited October 30, 2010 by blackmath