OLD Gamepad Autoconfig Thread

[system]

Hi, I don’t know if it’s the good topic to ask but I have a problem with my controller on retroarch android.

I own a nyko controller pad (not the pro one),it is recognized by retroarch in the menu (I can navugate etc), and when I launch a game I have “Port 0: Nykopad”.

Only problem is: the D pad work, but none of my buttons are recognized. I can’t map it in the menu, so I don’t know what to do.

It seems to work on other emulators or games so I have no clue what to do.

I have the latest version of retroarch and I run on a galaxy tab 10.1, android 4.1.2

Anyway thanks for the work on the emulator !

[hunterk]

Did you disable autoconfiguration before you tried manually mapping the buttons?

Either way, you can try to follow the instructions in the first post of this thread and post your keycodes. If it doesn’t conflict with the playpad pro, I imagine it will get added.

[system]

[quote=brown_trumpet]Hi Squarepusher, can you confirm whether you have already been supplied with the codes for the Android Bluetooth Gametel gamepad?

http://www.amazon.co.uk/dp/B006L2HBXA/ref=pe_385721_37038051_pe_217191_31005151_M3T1_dp_1

If not, here are the codes:

UP: Pad 0 : 19, ac = 0, src = 0.
DOWN: Pad 0 : 20, ac = 0, src = 0.
LEFT: Pad 0 : 21, ac = 0, src = 0.
RIGHT: Pad 0 : 22, ac = 0, src = 0.
SELECT: Pad 0 : 109, ac = 0, src = 0.
START: Pad 0 : 108, ac = 0, src = 0.


SQUARE: Pad 0 : 99, ac = 0, src = 0.
TRIANGLE: Pad 0 : 100, ac = 0, src = 0.
CROSS: Pad 0 : 23, ac = 0, src = 0.
CIRCLE: Pad 0 : 4, ac = 0, src = 0.

L1: Pad 0 : 102, ac = 0, src = 0.
R1: Pad 0 : 103, ac = 0, src = 0.

Thanks.

I need the HID name as well. See the OP (Original Post) in this thread.[/quote]

Hi Squarepusher, I’m trying to follow your instructions on the original post, but I’m having some trouble. Firstly, regarding this step:

1. go to ‘RetroArch Settings’ and go to ‘Input Settings’.

In RetroArch 0.9.9.6, this is actually in Main Menu --> Input Options.

when I follow these steps:

3. Make sure that "Debug Input Reporting Enable’ is set to ‘OFF’.

3. After that, start up a game with any emu (doesn’t matter which). The first thing I need to know exactly is the message that appears when yuo press a button on the pad - it should say something like

“HID {%some name here%] unbound”

Nothing appears on screen when I press a button on the control pad.

No codes appear on screen until I follow this step

4. Set "Debug Input Reporting Enable’ to ‘ON’.

Can you please review and maybe modify your original post so that I can provide you with the information you need? I can’t see a way of getting the HID code to appear on screen.

I’m using RetroArch 0.9.9.6 for Android.

[anon24419061]

Enable on-screen fonts on the input menu

[MarioMania]

I would like to Request some stuff

On the Gamecube Conteller - Map the Menu to Z + Start

I mosty play my emu’s with the Hori or my SNES Pad

For Game Boy, GBA, Game Gear add a Option for Screen Size

[system]

Enable on-screen fonts on the input menu

I do not see an option to Enable on-screen fonts on the input menu.

The options I do get, under Input Options, are:

Configuration Autodetect (Enable / Disable) Debug Input Reporting (Enable / Disable) Touchscreen Overlay (Enable / Disable)

??

[system]

Enable on-screen fonts on the input menu

Ok I’ve found it, Enable On-screen fonts is on the Video Options, not “Input menu”

However, it’s already enabled - So, I ask again, how do you view the HID name?

[anon24419061]

if it’s not printing when you first press a button you need to do a logcat

[system]

Hello, this is the controller: http://www.amazon.com/Folding-Computer- … controller

this is what it says when I turn it on:

Port 0: USB, 2-axis 8-button gamepad .

UP: Pad 0: x=0.00, y= 0.00, src=16777232 DOWN: Pad 0: x=0.00, y=0.00, src=16777232 LEFT: Pad 0: x=0.00, y=0.00, src=16777232 RIGHT: Pad 0: x=0.00, y=0.00, src=16777232

Square: Pad 0: 90, ac=0, src= 1281 Cross: Pad 0: 96, ac=0, src= 1281 Circle: Pad 0: 97, ac=0, src= 1281 Triangle: Pad 0: 100, ac=0, src= 1281 L1: Pad 0: 102, ac=0, src= 1281 R1: Pad 0: 103, ac=0, src= 1281 L2: Pad 0: 104, ac=0, src= 1281 R2: Pad 0: 105, ac=0, src= 1281 Select: unavailable Start: unavailable

Thank you very much.

P.S. It could be cool if we could manually remap the controllers.

thanks again

[anon24419061]

I’m pretty sure you will be able to remap in next version

[isadic]

Hi, I have an Xbox 360 Wireless Controller, the pad is recognized by RA, but only the left analog is working, so no buttons… can I help you with debug?

When buttons are pressed: A Button: Pad 0: 96, ac = 0, src =1281. B Button: Pad 0: 97, ac = 0, src =1281. Y Button: Pad 0: 100, ac = 0, src =1281. X Button: Pad 0: 99, ac = 0, src =1281. Start Button: Pad 0: 108, ac = 0, src =1281. Back Button: Pad 0: 4, ac = 0, src =1281. RB Button: Pad 0: 103, ac = 0, src =1281. LB Button: Pad 0: 102, ac = 0, src =1281. LThumb (Left analog pressed): Pad 0: 106, ac = 0, src =1281. RThumb (RIght analog pressed): Pad 0: 107, ac = 0, src =1281.

The DPAD is strange, report 0 for all: Right: Pad 0: 0, ac = 0, src =1281. Donw: Pad 0: 0, ac = 0, src =1281. Left: Pad 0: 0, ac = 0, src =1281. Up: Pad 0: 0, ac = 0, src =1281.

The left analog reports: Right: Pad 0: x 1.00, y 0.00, z 0.00, rz 0.00 Down: Pad 0: x 0.00, y 1.00, z 0.00, rz 0.00 Left: Pad 0: x -1.00, y 0.00, z 0.00, rz 0.00 Up: Pad 0: x 0.00, y -1.00, z 0.00, rz 0.00

The right analog reports: Right: Pad 0: x 0.00, y 0.00, z 1.00, rz 0.00 Down: Pad 0: x 0.00, y 0.00, z 0.00, rz 1.00 Left: Pad 0: x 0.00, y 0.00, z -1.00, rz 0.00 Up: Pad 0: x 0.00, y 0.00, z 0.00, rz -1.00

So we miss only the LT and the RT, the triggers, thet I can’t see in the screen, because are after the rz, in analog reports. The central button is read by Android as home button, so I can’t see it (Probably RA doesn’t capture it as button).

That’s all, I hope that this data is helpful to solve the pad problems. Thank you for the work behind RA

[foleyjo]

Here are the key codes for the JXD s5110b (Rom updated to Skelrom and tincore keymapper). The right analog stick is recognised as being pushed but does not give any values for the x y or z. I’m also not sure if these are the same keycodes that you would get if using the stock JXD s5110b.

tincore_adc_joystick.

Dpad Up = pad 0 : 19, ac = 1, src = 1281. Down = pad 0 : 20, ac = 1, src = 1281. Left = pad 0 : 21, ac = 1, src = 1281. Right = pad 0 : 22, ac = 1, src = 1281.

Triangle = pad 0 : 99, ac = 1, src = 1281. Circle = pad 0 : 96, ac = 1, src = 1281. Cross = pad 0 : 97, ac = 1, src = 1281. Square = pad 0 : 100, ac = 1, src = 1281.

Ltrigger = pad 0 : 102, ac = 1, src = 1281. Rtrigger = pad 0 : 103, ac = 1, src = 1281.

Select = pad 0 : 109, ac = 1, src = 1281. Start = pad 0 : 108, ac = 1, src = 1281.

Left Analog Stick Up = pad 0 : x 0.00, y -1.00, z 0.00, rz 0.00 src 16777232. Down = pad 0 : x 0.00, y 1.00, z 0.00, rz 0.00 src 16777232. Left = pad 0 : x -1.00, y 0.00, z 0.00, rz 0.00 src 16777232. Right = pad 0 : x 1.00, y 0.00, z 0.00, rz 0.00 src 16777232.

Right Analog Stick Up = pad 0 : x 0.00, y 0.00, z 0.00, rz 0.00 src 16777232. Down = pad 0 : x 0.00, y 0.00, z 0.00, rz 0.00 src 16777232. Left = pad 0 : x 0.00, y 0.00, z 0.00, rz 0.00 src 16777232. Right = pad 0 : x 0.00, y 0.00, z 0.00, rz 0.00 src 16777232.

[fivefeet8]

Hi.

I have some remarks and questions regarding the MOGA Pro support in RetroArch.

First thing : I only use the official MOGA Pivot app. I tried a few times to configure the generic driver-thing available on the Play Store, but I couldn’t make it work.

When I put the controller in A mode, Retroarch doesn’t recognize it at all, pure and simple. I can try to manually bind every keys, Retroarch just doesn’t register the button I press or the sticks I move on the controller.

When I put it in B mode, which is the HID mode, I can configure every buttons of the controllers, except for the two analog triggers. I think I read somewhere in this thread that this is a known issue with analog triggers (and analog sticks, which don’t work as analog but only like a standard D-pad), but as you fixed it for the 360 pad in the latest release, maybe you will fix this for the MOGA in a future version.

Finally, here is something I have thought : MOGA provides an SDK for developers, in order for them to easily add support for MOGA controllers in their games. Maybe you could request one of those SDK : this could be easier for you to add automatic configuration for MOGA controllers. Just to be clear : I am no developer by any mean, and it’s maybe a stupid idea.

Anyway, whatever you decide, thanks you for your work and the massive amount of time you put in this app.

I would like to second this suggestion. I’ve found that Mupen64Ae(non Retroarch) and PPSSPP support both triggers in B mode on my Moga Hero. And the other psx emulators on the play store support triggers through the A mode. It’s a bit hard to play a game like Metal Gear Solid without the triggers. Besides the triggers not working, all the other buttons, d-pad, and analogs work fine when set to Moga HID.

[isadic]

I was trying the ipega 9017 with Retroarch, but buttons are not working properly, can you look into this? I’m on a galaxy nexus, Android 4.3.1. Tried in stable (0.9.9.6) and test builds.

[lanciaux]

Hello,

I got a GameStick and it lacks a good emu as RetroArch (for now). By the way, pads are simple but fully workable, could you add some pre-configuration for using it also on my Galaxy Tab 2 Android 4.0.4 ?

I got information really difficult way because I had not found retroarch-manual.pdf anymore

So I got this with a command line entry (dmesg) :

input: GameStick Controller as /devices/platform/omap/omap_uart.1/tty/tty01/hci0/hcio:12/input16 keychord: using input dev GameStick Controller for fevent generic-bluetooth 0005:0F0D:1011.0009: input: BLUETOOTH HID v7/07 Keyboard [GameStick Controller]

I did not found HID (ubound) : only IME reporting Pad:0, ac=0, src=1281

I: Bus=0005 Vendor=0f0d Product=1011 Version=0707 N: Name=“GameStick Controller” P: Phys=0C:71:5D:A2:F5:F2 S: Sysfs=/devices/platform/omap/omap_uart.1/tty/ttyO1/hci0/hci0:12/input8 U: Uniq=8C:DE:52:1D:BC:2D H: Handlers=sysrq kbd mouse0 event8 keychord B: PROP=0 B: EV=2001f B: KEY=4 0 ffff0000 1f0000 10000 2000007 ff9f307a c14057ff febeffdf ffefffff ffffffff fffffffe B: REL=103 B: ABS=30627 B: MSC=10 B: LED=1f

L1=102 R1=103 Left Analog pad button = 106 Right Analog pad button = 107 Pads are classical values Left/Right Analog sticks A=96 B=97 X=99 Y=100 Start=108 Back=4

there is also special button that once pressed make retroarch going out (like the left arrow on Android Tab), I cannot take its value while fully “exiting”

Any additional tool recommended for bringing you better information to fully support GameStick controllers ?

Cheers

Ludovic (Belgium)

[system]

Here are the key codes for the JXD S7800 (G5A, G7 and so on, alse for S7300, S7300C, S5110b, MX72).

only the left analog is working, so no buttons… can I help you with debug?

input name:ADC joystick

Dpad Up = pad 0 : 19 Down = pad 0 : 20 Left = pad 0 : 21 Right = pad 0 : 22

A = pad 0 : 96 B = pad 0 : 97 X = pad 0 : 97 Y = pad 0 : 100

L1 = pad 0 : 102 R1 = pad 0 : 103 Ltrigger(L2) = pad 0 : LTRIGGER Rtrigger(R2) = pad 0 : RTRIGGER LThumb (Left analog pressed): Pad 0: 106 RThumb (RIght analog pressed): Pad 0: 107

Select = pad 0 : 109 Start = pad 0 : 108

Left Analog Stick Up = pad 0 : x 0.00, y -1.00 Down = pad 0 : x 0.00, y 1.00 Left = pad 0 : x -1.00, y 0.00 Right = pad 0 : x 1.00, y 0.00

Right Analog Stick Right: Pad 0: x 0.00, y 0.00, z 1.00, rz 0.00 Down: Pad 0: x 0.00, y 0.00, z 0.00, rz 1.00 Left: Pad 0: x 0.00, y 0.00, z -1.00, rz 0.00 Up: Pad 0: x 0.00, y 0.00, z 0.00, rz -1.00

all the key and stick like SHIELD, we need you to autodetect.

[system]

I can find “ADC joystick” in android/native/jni/input_autodetect.c, but run artroarch Device is 0, why?

android logcat I/RetroArch: ( 1688): device name: ADC joystick I/RetroArch: ( 1688): Detecting keybinds. Device 0 port 0 id 1 keybind_action 16 I/RetroArch: ( 1688): Input debug: Port 0: ADC joystick.

[system]

Codes for 7800 already posted here: viewtopic.php?p=8615#p8615

[lanciaux]

Hello,

I got a GameStick and it lacks a good emu as RetroArch (for now). By the way, pads are simple but fully workable, could you add some pre-configuration for using it also on my Galaxy Tab 2 Android 4.0.4 ?

I got information really difficult way because I had not found retroarch-manual.pdf anymore

So I got this with a command line entry (dmesg) :

input: GameStick Controller as /devices/platform/omap/omap_uart.1/tty/tty01/hci0/hcio:12/input16 keychord: using input dev GameStick Controller for fevent generic-bluetooth 0005:0F0D:1011.0009: input: BLUETOOTH HID v7/07 Keyboard [GameStick Controller]

I did not found HID (ubound) : only IME reporting Pad:0, ac=0, src=1281

I: Bus=0005 Vendor=0f0d Product=1011 Version=0707 N: Name=“GameStick Controller” P: Phys=0C:71:5D:A2:F5:F2 S: Sysfs=/devices/platform/omap/omap_uart.1/tty/ttyO1/hci0/hci0:12/input8 U: Uniq=8C:DE:52:1D:BC:2D H: Handlers=sysrq kbd mouse0 event8 keychord B: PROP=0 B: EV=2001f B: KEY=4 0 ffff0000 1f0000 10000 2000007 ff9f307a c14057ff febeffdf ffefffff ffffffff fffffffe B: REL=103 B: ABS=30627 B: MSC=10 B: LED=1f

L1=102 R1=103 Left Analog pad button = 106 Right Analog pad button = 107 Pads are classical values Left/Right Analog sticks A=96 B=97 X=99 Y=100 Start=108 Back=4

there is also special button that once pressed make retroarch going out (like the left arrow on Android Tab), I cannot take its value while fully “exiting”

Any additional tool recommended for bringing you better information to fully support GameStick controllers ?

Cheers

Ludovic (Belgium)

[system]

First I would like to express my thanks to Hunter Kaller for activating my account so that I can post here. Thank you Hunter !

I have Retroarch V0.9.9.6 on my S3 and I use it with a Snakebyte idroid:con bluetooth controller. It works perfectly and I’m really grateful to the developers. I’ve just updated my Justop K9B Android TV dongle to 4.2.2 and installed Retroarch for the very first time in the hope that I will be able to now play games on the TV instead of my phone. Unfortunately this new version no longer appears to work with my controller. The D-pad (Up, Down, Left and Right) work correctly but none of the other buttons appear to work in the cores, even though they do work in Android and the Retroarch menu. Now I don’t know if the fault is elsewhere so I’ve decided to post what info I can to see if the problem can be solved by anyone here.

The Snakebyte idroid:con is now being identified as a Red Samurai by Retroarch V1.0.0.0 so I have got all of the rest of the required info below:

Snakebyte idroid:con (as Game Controller 1) connected via bluetooth to a Justop K9B (Model Rikomagic MK802IIIS/Android 4.2.2/Kernel 3.0.36+) using IME com.android.inputmethod.latin/.LatinIME running Retroarch V1.0.0.0

Port 0: Broadcom Bluetooth HID. A -> Pad 0 : 190, ac = 0, src = 1281 B -> Pad 0 : 189, ac = 0, src = 1281 X -> Pad 0 : 191, ac = 0, src = 1281 Y -> Pad 0 : 188, ac = 0, src = 1281 Up -> Pad 0 : x 0.00, y 0.00, z 0.00, rz 0.00, src 16777232 (buutmethod.latin/.LatinIME running Retroarch V1t works correctly) Down -> Pad 0 : x 0.00, y 0.00, z 0.00, rz 0.00, src 16777232 (but works correctly) Left -> Pad 0 : x 0.00, y 0.00, z 0.00, rz 0.00, src 16777232 (but works correctly) Right -> Pad 0 : x 0.00, y 0.00, z 0.00, rz 0.00, src 16777232 (but works correctly) Select -> Pad 0 : 196, ac = 0, src = 1281 Start -> Pad 0 : 197, ac = 0, src = 1281 L1 -> Pad 0 : 192, ac = 0, src = 1281 L2 -> Pad 0 : 194, ac = 0, src = 1281 L3 -> Pad 0 : 198, ac = 0, src = 1281 R1 -> Pad 0 : 193, ac = 0, src = 1281 R2 -> Pad 0 : 195, ac = 0, src = 1281 R3 -> Pad 0 : 199, ac = 0, src = 1281 Left Analog Up -> Pad 0 : x 0.00, y -1.00, z 0.00, rz 0.00, src 16777232 Left Analog Down -> Pad 0 : x 0.00, y 1.00, z 0.00, rz 0.00, src 16777232 Left Analog Left -> Pad 0 : x -1.00, y 0.00, z 0.00, rz 0.00, src 16777232 Left Analog Right -> Pad 0 : x 1.00, y 0.00, z 0.00, rz 0.00, src 16777232 Right Analog Up -> Pad 0 : x 0.00, y 0.00, z -1.00, rz -1.00, src 16777232 Right Analog Down -> Pad 0 : x 0.00, y 0.00, z 1.00, rz 1.00, src 16777232 Right Analog Left -> Pad 0 : x 0.00, y 0.00, z -1.00, rz 0.00, src 16777232 Right Analog Right -> Pad 0 : x 0.00, y 0.00, z 1.00, rz 0.00, src 16777232

I have also noticed that Retroarch V1.0.0.0 has many more controllers available, including the Saitek P480. I have a Saitek P380, so I thought I’d give that a go; but no luck there either. I also tried the idroid X360 and the i.droid options in case either of them would work with my idroid:con; but still no luck. Anyway in case there’s any chance of getting the Saitek P380 added in the next version of Retroarch, I’v included the required info below:

Saitek P380 connected via USB to a Justop K9B (Model Rikomagic MK802IIIS/Android 4.2.2/Kernel 3.0.36+) using IME com.android.inputmethod.latin/.LatinIME running Retroarch V1.0.0.0

Port 0: Jess Tech Dual Analog Pad. A -> Pad 0 : 191, ac = 0, src = 1281 B -> Pad 0 : 190, ac = 0, src = 1281 X -> Pad 0 : 189, ac = 0, src = 1281 Y -> Pad 0 : 188, ac = 0, src = 1281 Up -> Pad 0 : x 0.00, y 0.00, z 0.00, rz 0.00, src 16777232 (but works correctly) Down -> Pad 0 : x 0.00, y 0.00, z 0.00, rz 0.00, src 16777232 (but works correctly) Left -> Pad 0 : x 0.00, y 0.00, z 0.00, rz 0.00, src 16777232 (but works correctly) Right -> Pad 0 : x 0.00, y 0.00, z 0.00, rz 0.00, src 16777232 (but works correctly) Select -> Pad 0 : 196, ac = 0, src = 1281 Start -> Pad 0 : 197, ac = 0, src = 1281 L1 -> Pad 0 : 192, ac = 0, src = 1281 L2 -> Pad 0 : 193, ac = 0, src = 1281 L3 -> Pad 0 : 198, ac = 0, src = 1281 R1 -> Pad 0 : 194, ac = 0, src = 1281 R2 -> Pad 0 : 195, ac = 0, src = 1281 R3 -> Pad 0 : 199, ac = 0, src = 1281 Left Analog Up -> Pad 0 : x 0.00, y -1.00, z 0.00, rz 0.00, src 16777232 Left Analog Down -> Pad 0 : x 0.00, y 1.00, z 0.00, rz 0.00, src 16777232 Left Analog Left -> Pad 0 : x -1.00, y 0.00, z 0.00, rz 0.00, src 16777232 Left Analog Right -> Pad 0 : x 1.00, y 0.00, z 0.00, rz 0.00, src 16777232 Right Analog Up -> Pad 0 : x 0.00, y 0.00, z -1.00, rz 0.00, src 16777232 Right Analog Down -> Pad 0 : x 0.00, y 0.00, z 1.00, rz 0.00, src 16777232 Right Analog Left -> Pad 0 : x 0.00, y 0.00, z 0.00, rz -1.00, src 16777232 Right Analog Right -> Pad 0 : x 0.00, y 0.00, z 0.00, rz 1.00, src 16777232

Hope someone can enlighten me as to why things aren’t working for me.

Thanks.