[MTVisualizer] Lag when using ICS's Holo Theme

[GoogleCodeExporter]

(Bug originally filed by [email protected] when MTVisualizer was in a 
separate project.)

What steps will reproduce the problem?
1. sync source
2. insert <uses-sdk android:minSdkVersion="8"      
android:targetSdkVersion="15" /> above the <application>
3. compile
4. install & ran on galaxy nexus

What is the expected output? What do you see instead?
I expect it to run just as the version you released runs, but using the Holo 
theme. The outcome is an extremely laggy experience, along with trouble 
detecting multiple moving points, the the beautiful holo theme.

What version of the product are you using? On what operating system?
android 4.0.2, verizon galaxy nexus LTE (stock firmware)

Please provide any additional information below.

The only change to the app was the target sdk version, and minimum sdk version.
    AndroidManifest.xml:

<manifest xmlns:android="http://schemas.android.com/apk/res/android" 
package="org.metalev.multitouch.visualizer2" android:versionName="2.2.2" 
android:versionCode="13">
<uses-sdk android:minSdkVersion="8" android:targetSdkVersion="15"/>
<application android:icon="@drawable/icon" android:label="@string/app_name" 
android:debuggable="false">
<activity android:name=".MultiTouchVisualizerActivity" 
android:label="@string/app_name">
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
</activity>
</application>
</manifest>

I would like to add, the same code works fine on a stock nexus s 4.0.3

While android:targetSdkVersion 14 & 15 produce the lag, anything below 13 does 
not.

Original issue reported on code.google.com by luke.hutch on 22 Apr 2012 at 3:00

[GoogleCodeExporter]

Justin also added, "bug was still present as of 4.0.3, i just target a lower 
SDK and it goes away, so im targetting honeycomb instead of ICS."

Original comment by luke.hutch on 22 Apr 2012 at 3:13