OLD Gamepad Autoconfig Thread

RetroArch Android devices
#245

trying to play with a PS4 controller on Android. pairing the controller with my phone via Bluetooth worked by holding the PS and Share button, and selecting the controller in the Android bluetooth settings.

navigating between apps in Android homescreen already works using the controller arrow keys. in RetroArch, arrow keys also seem to work, but other keys do not.

adb logcat gives me the following:

I/EventHub( 747): New device: id=16, fd=179, path=’/dev/input/event12’, name=‘Broadcom Bluetooth HID’, classes=0x80000141, configuration=’’, keyLayout=’/system/usr/keylayout/Generic.kl’, keyCharacterMap=’/system/usr/keychars/Generic.kcm’, builtinKeyboard=false, usingSuspendBlockIoctl=true, usingClockIoctl=true I/InputReader( 747): Device added: id=16, name=‘Broadcom Bluetooth HID’, sources=0x01000511

keycodes:

cross - Pad 0 : 97, ac = 0 circle - Pad 0 : 98, ac = 0 square - Pad 0 : 96, ac = 0 triangle - Pad 0 : 99, ac = 0

L1 - Pad 0 : 100, ac = 0 R1 - Pad 0 : 101, ac = 0 L2 - Pad 0 : 102, ac = 0 R2 - Pad 0 : 103, ac = 0

left analog stick press - Pad 0 : 109, ac = 0 right analog stick press - Pad 0 : 108, ac = 0

share (= select) - Pad 0 : 104, ac = 0 options (= start) - Pad 0 : 105, ac = 0

PSbutton - Pad 0 : 110, ac = 0

#246

XBOX 360 WIRELESS CONTROLLER (THROUGH USB WIRELESS RECEIVER) (not using IME) results are different for analog controls and digital.

Somone allready asked for the xbox wireless controller support, but i had differente results I got some buttons responding, but neither the d-pad or analog pad responds.

BUTTONS ARE: (digital) Pad 0 : xx, ac = x, src 1281

D-PAD: UP, LEFT, RIGHT, DOWN: all the same results: Pad 0 :0 , ac = 0, src = 1281 (ac=0 when pressed, and ac=1 when not pressed)

BUTTONS (in all cases ac=0 when pressed and ac=1 when released)

A : Pad 0: 96 ac=0, src = 1281 B : Pad 0: 97 ac=0, src = 1281 X : Pad 0: 99 ac=0, src = 1281 Y : Pad 0: 100 ac=0, src = 1281 START : Pad 0: 108 ac=0, src = 1281 BACK : Pad 0: 109 ac=0, src = 1281 L1 : Pad 0: 102 ac=0, src = 1281 R1 : Pad 0: 103 ac=0, src = 1281 L3 : Pad 0: 106 ac=0, src = 1281 R3 : Pad 0: 107 ac=0, src = 1281

LEFT ANALOG PAD AND LEFT AND RIGHT TRIGGERS

This show a combination of codes no the screen: Pad 0 : x x.xx, y x.xx, z x.xx, rz x.xx

The values for “x & y” are used for the left analog pad: 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

The values for “z” is used for the left trigger and the values for “rz” are used for the right trigger

Left trigger Un-Pressed: Pad 0 : x 0.00, y 0.00, z -1.00, rz -1.00 Left trigger Pressed: Pad 0 : x 0.00, y 0.00, z 1.00, rz -1.00

Right trigger Un-Pressed: Pad 0 : x 0.00, y 0.00, z -1.00, rz 1.00 Right trigger Pressed: Pad 0 : x 0.00, y 0.00, z -1.00, rz -1.00

RIGHT ANALOG: when pressed i can see text on screen, but it seems that doesnt fits the results

Thank you…

#247

http://www.xgaming.com/support/question … OS+Support http://www.mayflash.com/Products/iPhoneiPad/AD001.html Mayflash Brand PS2 wireless adapter for android, ios and PC PS2 Controller Bluetooth Adapter for Android & iOS

Bought two of these adapters in hopes of getting my Xarcade dual stick to work wirelessly with retroarch 2 players simultaneously and not dice! Only one stick works. :frowning:

Just thought I’d share the news as I’m sure lots of xarcade owners are wondering and I share here in hopes retroarch developers may be able to come up with a solution, so that we can have an xarcade dual stick work wirelessly on android retroarch. I would assume though to do it the retroarch program wou have to independently manage bluetooth device input.

#248

Controller ipega 9025 in joystick mode

Identifies as “ipega media gamepad controller”

B: Pad 0: 96, ac=0,src= 1281 A: Pad 0: 97, ac=0,src= 1281 Y: Pad 0: 99, ac=0,src= 1281 X: Pad 0: 100, ac=0,src= 1281 R1: Pad 0: 105, ac=0,src= 1281 L1: Pad 0: 104, ac=0,src= 1281 R2: Pad 0: 103, ac=0,src= 1281 L2: Pad 0: 102, ac=0,src= 1281 R3: Pad 0: 107, ac=0,src= 1281 L3: Pad 0: 106, ac=0,src= 1281

Select: Pad 0: 109, ac=0,src= 1281 Start: Pad 0: 108, ac=0,src= 1281

Analog left stick

Up x=0.00 y=-1.00 z=0.00 rz=0.00 src=16777232 Down x=0.00 y=1.00 z=0.00 rz=0.00 src=16777232 Left x=-1.00 y=0.00 z=0.00 rz=0.00 src=16777232 Right x=1.00 y=0.00 z=0.00 rz=0.00 src=16777232

Analog right stick

Up x=0.00 y=0.00 z=0.00 rz=-1.00 src=16777232 Down x=0.00 y=0.00 z=0.00 rz=1.00 src=16777232 Left x=0.00 y=0.00 z=-1.00 rz=0.00 src=16777232 Right x=0.00 y=0.00 z=1.00 rz=0.00 src=16777232

Thank you…

#249

I use Retroarch with Ouya. I’m here after problem with Ouya controller (d-pad direction work bad) and PS3 controller (d-pad don’t work).

PS3 TRIANGLE: Pad 0: 100, ac=0,src= 1281 CIRCLE: Pad 0: 97, ac=0,src= 1281 X: Pad 0: 96, ac=0,src= 1281 QUAD: Pad 0: 99, ac=0,src= 1281 R1: Pad 0: 103, ac=0,src= 1281 L1: Pad 0: 102, ac=0,src= 1281 R2: Pad 0: 105, ac=0,src= 1281 L2: Pad 0: 104, ac=0,src= 1281 R3: Pad 0: 107, ac=0,src= 1281 L3: Pad 0: 106, ac=0,src= 1281

Select: Pad 0: 109, ac=0,src= 1281 Start: Pad 0: 108, ac=0,src= 1281 PS BUTTON: Pad 0: 82, ac=0,src= 1281

Analog left stick

Up x=0.00 y=-1.00 z=0.00 rz=0.00 src=16777232 Down x=0.00 y=1.00 z=0.00 rz=0.00 src=16777232 Left x=-1.00 y=0.00 z=0.00 rz=0.00 src=16777232 Right x=1.00 y=0.00 z=0.00 rz=0.00 src=16777232

Analog right stick

Up x=0.00 y=0.00 z=0.00 rz=-1.00 src=16777232 Down x=0.00 y=0.00 z=0.00 rz=1.00 src=16777232 Left x=0.00 y=0.00 z=-1.00 rz=0.00 src=16777232 Right x=0.00 y=0.00 z=1.00 rz=0.00 src=16777232

OUYA Y: Pad 0: 100, ac=0,src= 1281 CIRCLE: Pad 0: 96, ac=0,src= 1281 A: Pad 0: 97, ac=0,src= 1281 U: Pad 0: 99, ac=0,src= 1281 R1: Pad 0: 103, ac=0,src= 1281 L1: Pad 0: 102, ac=0,src= 1281 R2: Pad 0: 105, ac=0,src= 1281 L2: Pad 0: 104, ac=0,src= 1281 R3: Pad 0: 107, ac=0,src= 1281 L3: Pad 0: 106, ac=0,src= 1281

U BUTTON IN THE CENTER: Pad 0: 82, ac=0,src= 1281

Analog left stick

Up x=0.00 y=-1.00 z=0.00 rz=0.00 src=16777232 Down x=0.00 y=1.00 z=0.00 rz=0.00 src=16777232 Left x=-1.00 y=0.00 z=0.00 rz=0.00 src=16777232 Right x=1.00 y=0.00 z=0.00 rz=0.00 src=16777232

Analog right stick

Up x=0.00 y=0.00 z=0.00 rz=-1.00 src=16777232 Down x=0.00 y=0.00 z=0.00 rz=1.00 src=16777232 Left x=0.00 y=0.00 z=-1.00 rz=0.00 src=16777232 Right x=0.00 y=0.00 z=1.00 rz=0.00 src=16777232

#250

I just got the nvidia shield tablet and the new controller. Are controllers still added using this thread? If they are I’ll upload the button press info. I don’t want to go through the trouble if controllers are going to be added differently in future releases though.

#251

Looks like the Shield tablet controller already works. Must be the same setup as the Shield portable which is cool.

#252

Nice :smiley:

That’s good to know!

#253

Will the original moga be supported in v1.1(the upcoming release)

#254

Hi guys

I play with Minix Neo X7 and my setup is as follows:

Controller 1: T-Wireless Black - Thrustmaster, is detected as T Mini Wirless is works very well on the SNES or Megadrive console emulators, but I have problem with MAME 2003 and 2010 .

For example cadillac dinosaur or Asterix KONAMI, not i can start the game I have only one button for a menu and the directional pad works !

the button does not work in M.A.M.E : input_b_btn = “b” input_y_btn = “c” input_select_btn = “L2” input_start_btn = “R2” input_a_btn = “a” input_x_btn = “x” input_l_btn = “L1” input_r_btn = “R1” input_l2_btn = “y” input_r2_btn = “z”

Controller 2: Saitek P380 Dual Analog is detected as Jess Tech Dual Analog Pad, here I have the directional button and dual analog works

the button not work are the following: input_b_btn = “3” input_y_btn = “1” input_select_btn = “9” input_start_btn = “10” input_a_btn = “4” input_x_btn = “2” input_l_btn = “5” input_r_btn = “7” input_l2_btn = “6” input_r2_btn = “8”

I notice that the Saitek P480 Dual Analog is suported by RetroArch.

Thank you in advance for your help and wonderful emulator

#255

hi guys, i love this emulator but i can’t get my xbox 360 wireless controller working. when i plug it in i can controll the phone and everything. retroarch even recognizes the signals in the cumstom binds. but when im starting diablo the controlls don’t work. they also not work in the gui. am i doing something wrong? thank for your help!

sorry for the bad english :smiley:

greetz

#256

hi, for me wireless controller is dectected as portable shield but autoremapping not working for me, have to reconfigure all keys. also in source code shield joypad seem to be forced to be port 0 which is bad for shield tablet , as we can hook like to 4 wireless controllers.

ps: i assume you are the same shifted in gforce forum ?

#257

This is a config I tryed to make in a few minutes. Please test. https://drive.google.com/file/d/0B5HuG10h5HbncVRobGlWcVV5ZzA/edit?usp=sharing This is for the moga hero power.

#258

Hello guys, I just wanted to play with my Icade and retroarch and I have seen in the release notes that it’s supported. But I can’t play and don’t understand how it’s work. Should I post the requested sentences ? Or is there something I do badly ? I try to autodetect with all the profile (not working) and to configure manually the input (not working great). Thanks in advance

#259

I noticed that the Phonejoy wasn’t supported as a controller in the latest version off the Google Play store. I’ve pulled the information needed for the button mappings. Manual configuration will work but the analog sticks aren’t working with that so I was hoping autodetection would could be added for it. Let me know any way I can help. When this is added will it show up on the weekly builds section or just keep on updating from the play store?

I/EventHub( 753): New device: id=21, fd=298, path=’/dev/input/event5’, name=‘Ph onejoy Gamepad Mode ‘, classes=0x80000141, configuration=’’, keyLayout=’/syst em/usr/keylayout/Generic.kl’, keyCharacterMap=’/system/usr/keychars/Generic.kcm’ , builtinKeyboard=false, usingSuspendBlockIoctl=true, usingClockIoctl=true I/InputReader( 753): Device added: id=21, name='Phonejoy Gamepad Mode ', sou rces=0x01000511

Left analog:

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 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

Right analog:

Left: Pad 0: x 0.00, y 0.00, z -1.00, rz 0.00, src 16777232 Right: Pad 0: x 0.00, y 0.00, z 1.00, rz 0.00, src 16777232 Up: Pad 0: x 0.00, y 0.00, z 0.00, rz 1.00, src 16777232 Down: Pad 0: x 0.00, y 0.00, z 0.00, rz -1.00, src 16777232

D-PAD Left: Pad 0: 21, ac = 0, src = 1281 D-PAD Right: Pad 0: 22, ac = 0, src = 1281 D-PAD Up: Pad 0: 19, ac = 0, src = 1281 D-PAD Down: Pad 0: 20, ac = 0, src = 1281

Button Y: Pad 0: 100, ac = 0, src = 1281 (placed as triangle in psx layouts) Button B: Pad 0: 97, ac = 0, src = 1281 (placed as cross in psx layout) Button X: Pad 0: 99, ac = 0, src = 1281 (placed as Square in psx layouts) Button A: Pad 0: 96, ac = 0, src = 1281 (placed as Circle in Psx layouts)

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

button_ThumbL: Pad 0: 106, ac = 0, src = 1281 (like l3 in PS3) Button_ThumbR: Pad 0: 107, ac = 0, src = 1281 (like R3 in ps3)

START: Pad 0: 108, ac = 0, src = 1281 SELECT: Pad 0: 109, ac = 0, src = 1281

#260

I have a red samurai & the auto configuration does not read it. So I have to use a custom bind for it to read, the analog sticks do not work at all. I don’t know if I need to install a custom IME or what should i do.

#261

Hi, I have a 8-Bitty and while I can play RetroArch in Windows fine (using this site as guide http://www.richtamblyn.com/icade-8-bitty/ ) I’d like to see it working in Android. I can help to debug it if 8-Bitty is still an issue in Android.

Sorry, in case this has already been answered, but the Search feature works funny and does not result posts containing either “8-Bitty” or “ThinkGeek”.

#262

Hi there.

Thanks for taking submissions for new gamepads. I am submitting one for the following controller:

HID unbound: Port 0: Afterglow controller for PS3

Select:104 Start:105 Triangle:99 Square:96 X:97 Circle:98 L1:100 L2:102 R1:101 R2:103 L3: 109 R3:108

Hope this helps.

#263

Hello SquarePusher,

just wondering if you could add Android ‘GameStick gamepad’ support such a way those can be a bit more useful than dust they have been covered since a couple of weeks now.

Check my previous posts and do not hesitate to ask me more information if I can gather it.

Yours

Ludovic

#264

Hello (again) SquarePusher,

I have walked trough Retroarch 1.0.0.2 with my GameStick gamepad and found them to be not confortable (not supported and I need to do mapping and analog do not work). Check my other posts coz they can be useful from time to time.

I had also read several android user were happy of SixAxis PS3 pads support - I bought one (not a Sony one, a one manufactured as BigBen). Thanks to Dancing Pixel Studio SixAxis tool, SisAxis mapped immediately on my Android (4.1.2) and with application working charm except …in retroarch.

  1. Not supported in 1.0.0.2 except in main menu and if i do not choose sixaxisIME (leaving android keyboard), I can play with it (sixaxis tool has a setting making it mapping as gamepad anytime) except analog are not working at all ;
  2. In 1.0.0.3 (experimental builds I have found on a DropBox account) - it is not working anymore ;

Could you add support for it ? Keys are similar to ‘DualShock3.cfg’ you have had today in Android retroarch-joypad-autoconfig ?

Do not hesitate to ask more information if required

Thanks a lot

Ludovic (again)