Need Galaxy Nexus Tester (if having multi-touch problems)

[Paul]

If you own a Galaxy Nexus and are having problems with multi-touch, please respond so I can see if there is something wrong with my code, or if I'm just not receiving the touch events.

[Paul]

Here is the multitouch test app:

Multitouch Test

If you are not familiar with accessing the logs, please read this thread.

Please perform the following actions, then post the logcat output.  The log file will likely be very large, so you'll probably need to email it to me if you don't have a hosting service to upload it to.  PM me if you need my email address.

1) Run aLogcat and clear the logs.
2) Run the above multitouch test app (will show up as "Mupen64Plus TEST" in your apps list).
3) Start Mario64, and play around with it until the multitouch problem occurs.
4) Press the "Z" button several times (this will flag where in the log the problem started).
5) Play around with the analog control while pressing the jump button (make sure the problem happens a few times).
6) Exit the app.
7) Return to aLogcat, and save the log.
8) Send me the log file.

[xcasto]

Just to clarify a few questions I have about the logs..

aLogcat has some preferences that can be set these include:

• Level = Verbose
• Format = Brief
• Buffer = Main
• HTML = No

I figure these are probably the preferences you'd care about most, but since the defaults listed (with those preferences above) might not give the information that would help you most, could you also include the settings for those preferences you'd like the log to capture?

Typically I use Debug for Level, but you might want these set differently or have you noticed that it doesn't matter and those settings are just for display?

[Paul]

As long as the "verbose", "information", and "error" messages are getting into the logs.  I think whatever the default settings are does this.  I've never actually played around with aLogcat settings before.

[Paul]

Got some interesting results from the test harley ran.  It appears that the problem is not that the second pointer isn't being registered, but instead it seems to be getting "stuck" down (the pointer up events are not registering, but the pointer down and move events are).  I'm going to write another test tomorrow to try and get some more useful data to see if there is a logic error in my code somewhere, or if there's another way it could be written to process the input that I am getting.

[Paul]

Here is another test, if anyone with a Galaxy Nexus experiencing the multi-touch problem happens to be reading:

Verbose test

If you've installed any of the previous tests or the 1.99.5 core test, please uninstall them first before installing this one.  Grab the logcat after pressing on the virtual gamepad until you experience the problem.

If you are not familiar with accessing the logs, I've posted instructions in this thread.