Testers needed! (input plug-in, touchscreen controls)

[Paul]

Announcing two great new features that are being added to the app!  It will be great to have lots of testers with a variety of devices to help out!

I've merged both tests into a single APK, so you won't need to install them separately.  Here's a link to the APK:

Input Plugin Test

NOTE: If you've installed an earlier test, you will probably need to uninstall it to avoid a signature conflict.

The first thing we need to test is the brand-new input plug-in that littleguy wrote!  This bad-boy not only cuts out most of the excess code we aren't using from input-sdl, but it also has some awesome new features like Rumble Pak emulated with the vibrator, and pak-switching.

We need to run stress tests on a variety of devices to work out any remaining kinks.  I'll be spreading the word on various other sites, and it would be great if everyone here could give it a whirl and report the results.  And besides, Diddy Kong Racing is a lot more fun with rumble working 

The second thing we need to test is the new system I'm working on for the touchscreen controls.  When you're done testing the input plug-in, please run some tests with the touchscreen controls as well.  The new system does some scaling and layout management based on the screen size in pixels and inches and orientation!

I need to have this tested on a variety of screen sizes to address any problems of incorrectly sized or overlapping buttons.  Please mention your device model (and screen resolution and size if you know)

For now I'm just looking for feedback on control sizes and in particular if there is any button overlap.  Please test in both landscape and portrait modes.  Also, there is a setting to make all buttons visible, in the Touchscreen layout settings.  Please test with it as well as the normal layout (in both landscape and portrait).  Screenshots to demonstrate problems are helpful if you can provide them.

[WinSuk]

Aria in portrait has an overlapping dpad (http://dl.dropbox.com/u/1077120/mupentesting/Screenshot_2013-03-04-23-37-13.png)
Nexus 7 in landscape is a little close, but not overlapping (http://dl.dropbox.com/u/1077120/mupentesting/Screenshot_2013-03-04-23-44-35.png)

[littleguy]

You could merge the two branches for the test build, get twice the interest

[Paul]

You could merge the two branches for the test build, get twice the interest

Great suggestion!  I updated the first post. 

I also merged in the other thread (ended up accidentally deleting WinSuk's first reply, but the useful one is still here)

[Paul]

Aria in portrait has an overlapping dpad

Nexus 7 in landscape is a little close, but not overlapping

Could you give this one a try?  I have a feeling that the change is too small to make any difference, but I just want to get a fee for how much I need to adjust the numbers to get the desired results:

Touch Controls Test #2

(You'll need to uninstall the previous test first, or it won't install due to a signature conflict)

[WinSuk]

Could you give this one a try?  I have a feeling that the change is too small to make any difference, but I just want to get a fee for how much I need to adjust the numbers to get the desired results:

Touch Controls Test #2

(You'll need to uninstall the previous test first, or it won't install due to a signature conflict)

Still overlaps a little. http://dl.dropbox.com/u/1077120/mupentesting/Screenshot_2013-03-05-16-18-09.png

[Paul]

Great, getting closer.  Give this one a try:

Touch Controls Test #3

I'm back on my home computer, so you'll first have to uninstall the last test to avoid a signature conflict.  Sorry for the hassle!

[WinSuk]

No problem

No longer overlapping: https://dl.dropbox.com/u/1077120/mupentesting/Screenshot_2013-03-05-18-49-41.png
Really close to Z though... guess there isn't much that can be done about that

Also tested the input plugin for awhile with my 360 controller. Rumble works and I didn't have any problems

[littleguy]

So as I mentioned on github, the new version shrinks the controls on my 7" 1280x800 tablet.

Old
http://dl.dropbox.com/u/3899306/Screenshot_2013-03-05-23-23-02.png
http://dl.dropbox.com/u/3899306/Screenshot_2013-03-05-23-22-12.png

New
http://dl.dropbox.com/u/3899306/Screenshot_2013-03-05-23-10-44.png
http://dl.dropbox.com/u/3899306/Screenshot_2013-03-05-23-11-50.png

My personal preference is also to keep exactly the same size in portrait or landscape.  I know you added a 1.5x scale in the code but that's not the exact ratio.  I say just make the scale with respect to the larger of (width, height) so they are the same physical size in either orientation.

[Paul]

Aha, that's a good idea.

[Tom.K]

Crashes on my X10 Mini Pro when launching emulator. Report should've been sent thru app.

[Paul]

Rgr, I'll take a look

[Paul]

For some reason it isn't sending the logcat output from your device with the reports, unfortunately.  That said, it looks to be failing when it tries to set the scale for one of the numeral images (which must mean that it failed to load one or more of them for some reason).  Could you try reloading the app resources, then running with and without the FPS indicator visible?

I'll upload another test shortly that should squash the crash when a digit is null (but it won't address whatever the underlying cause for the digit being null)

BTW, I like the value in android.os.Build.MANUFACTURER for the X10 Mini Pro (especially since I work for Ericsson )

Spoiler: Build.MANUFACTURER • show

Sh!tEricsson

[Paul]

Ok, this one should (hopefully) not crash.  If it does, I'll take a look at the crash report.  You'll have to uninstall the previous test, since it has a different digital signature

Numeral Crash Test #1

[Tom.K]

For some reason it isn't sending the logcat output from your device with the reports, unfortunately.  That said, it looks to be failing when it tries to set the scale for one of the numeral images (which must mean that it failed to load one or more of them for some reason).  Could you try reloading the app resources, then running with and without the FPS indicator visible?

I'll upload another test shortly that should squash the crash when a digit is null (but it won't address whatever the underlying cause for the digit being null)

BTW, I like the value in android.os.Build.MANUFACTURER for the X10 Mini Pro (especially since I work for Ericsson )

Spoiler: Build.MANUFACTURER • show

Sh!tEricsson

Sorry about that,  it's Custom ROM GingerDX, developed by djnilse and eagleeyetom (< How ironic, that's not me.)
Luckily, I've saved this logcat when it did happen, if it helps: http://pastebin.com/B448xzSU

About further results and testing, you'll have to wait until weekend comes (or when I stop studying).