Including <uses-sdk minSdk="4"> (or higher) in manifest breaks multitouch

[Polatrite]

After successfully integrating the library into my test harness, I then moved the code into my core product and noticed that multitouch (specifically on an OpenLayers map) was not working as intended on a 2.3.6 device.

After a lot of investigation, I have narrowed the problem down to the attribute in the manifest file. Whenever this is present and the minSdk is set to 4 or higher (3 and lower all work), the multitouch functionality breaks - in fact, even touch functionality doesn't work as expected.

To reproduce this issue, download a fresh copy of the github tarball and then add this line to the manifest:

<uses-sdk android:minSdkVersion="3" android:targetSdkVersion="3" />

Then run the application in standard portrait orientation. You should notice a few touch related bugs:

1. Touches on the right hand side of the screen sometimes aren't activated. This appears to be somewhere around 66-75% toward the right - however these touches are still recognized by the status text at the top of the screen.
2. Multitouch events are recognized only as multiple single touch events. In the OSM/OpenLayers example this causes the map to snap wildly around when attempting a pinch-zoom.

I tested this on an original Google Nexus (2.3.6), Google Nexus (2.3.5), HTC Incredible (2.3.3) and Samsung Galaxy S (2.3.6), and had the problem on each.

[Philzen]

@Polatrite i am unable to reproduce this on HTC Vision - tried setting the <uses-sdk ... />-directive in both wmp project as well as in the Demo Project, tried values 3 and 4, but none showed the problems you describe.

Pls advise on any other ideas on how to reproduce the problem along with any other info (suspicious log entries, wmp version used, 3rd party libraries and version no. involved with WebView or Activity Base Class such as Cordova).

[Philzen]

May be related to #25