Author Topic: Need Galaxy Nexus Tester (if having multi-touch problems)  (Read 4436 times)

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Need Galaxy Nexus Tester (if having multi-touch problems)
« on: February 05, 2012, 07:46:49 PM »
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.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Need Galaxy Nexus Tester (if having multi-touch problems)
« Reply #1 on: February 09, 2012, 05:51:14 PM »
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.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline xcasto

  • bit
  • Posts: 5
    • View Profile
Re: Need Galaxy Nexus Tester (if having multi-touch problems)
« Reply #2 on: February 10, 2012, 06:56:24 PM »
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?
Device: HTC EVO 4G Version: 0003
CPU: Qualcomm? Snapdragon S1 QSD8650, 1GHz (single core)
GPU: Adreno 200, 133MHz
RAM: 512 MB
Resolution:  480 x 800
Colors: 65,536 (16-bit)
Rom: Stock Sprint Android 2.3.5/Gingerbread

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Need Galaxy Nexus Tester (if having multi-touch problems)
« Reply #3 on: February 10, 2012, 07:02:58 PM »
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.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Need Galaxy Nexus Tester (if having multi-touch problems)
« Reply #4 on: February 12, 2012, 09:51:53 PM »
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.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Need Galaxy Nexus Tester (if having multi-touch problems)
« Reply #5 on: March 28, 2012, 05:11:55 PM »
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.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted