*Temporary Fix *

Well I finally got to the bottom of this. Amiberry does not register when button 15 (select) or 16 (xbox) are pressed on an Xbox One 2016 Bluetooth pad (maybe some other Xbox pads as well). The short term solution is to assign the Hotkey to another button that is not used in Amiga emulation e.g. 14 (right analogue press).

Is it possible to make a dedicated Amiberry joypad config file in Retorarch that only Amiberry will pick up on. While I'm at it could I do the same for other emulators such as LR PCSX Rearmed?

Thanks to Horaceandthespider at Github for help in resolving this.

@theretroprince said in Xbox One Blue Tooth Joy-Pad Connection Problem:

@lip9571 The udev rules are an option that you can automatically set in RetroPie-setup. They just write a line of configuration to your bluetooth rules. It is not enabled by default. As long as you haven't enabled them, you don't need to concern yourself with them. If you have enabled it, you can disable it within the Bluetooth setup in RetroPie-Setup.

Thanks for the reply. I got it all working in the end all I need to do was re bind the buttons for Bluetooth in retro arch and it worked perfect

@zacho95 Also another thing you can try is powering off the console, pulling the power cord/power supply, press the power button on the Xbone a couple of times to drain it, and then reboot and retry.
I used to get paid to do this shit for Microsoft :)

When you connect a controller to an XBONE via wired or wireless, it saves the ID of the console in the controller's memory, so if it is not connecting to it after all of these steps, it is probably the wireless functionality on the controller that is dead (in all my years of working we have not had the wireless adapter on the console side break). I have seen a lot of those original controllers break over the years :)

Also if you have a friend with an XBONE, try to pair it to that console

@aditkrator said in Changing Xbox driver based off game:

Parsec for Raspberry Pi

I hadn't heard of Parsec, but it looks like something similar to Moonlight, which I use (or did use, but ever since I updated to RetroPie 4.4 I can't seem to get it to work). I have quite a few individual bash scripts that invoke xboxdrv and then start moonlight and then individual games, so it can be done:

sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv > /dev/null 2>&1 \ --silent \ --detach-kernel-driver \ --deadzone=4000 \ --deadzone-trigger 15% \ --force-feedback \ --mimic-xpad \ --trigger-as-button \ --ui-buttonmap lb=void,rb=void,tl=void,tr=void,guide=void,lt=void,rt=void \ --evdev /dev/input/by-path/platform-3f980000.usb-usb-0:1.3.2:1.0-event-joystick \ --device-name "Player_1" \ --evdev-absmap ABS_X=x1,ABS_Y=y1 \ --evdev-keymap BTN_THUMB=a,BTN_TOP=b,BTN_PINKIE=x,BTN_TRIGGER=y,BTN_THUMB2=back,BTN_TOP2=start \ --ui-axismap X1=KEY_DOWN:KEY_UP,Y1=KEY_RIGHT:KEY_LEFT \ --ui-buttonmap a=KEY_Z,b=KEY_E,x=KEY_X,y=KEY_Q,back=KEY_SPACE,start=KEY_ENTER \ --ui-buttonmap back+start=cycle-key:KEY_ESC:KEY_LEFTCTRL+KEY_LEFTSHIFT+KEY_LEFTALT+KEY_Q \ & sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv > /dev/null 2>&1 \ --silent \ --detach-kernel-driver \ --deadzone=4000 \ --deadzone-trigger 15% \ --force-feedback \ --mimic-xpad \ --trigger-as-button \ --ui-buttonmap rb=void,tl=void,tr=void,guide=void,lt=void,rt=void \ --evdev /dev/input/by-path/platform-3f980000.usb-usb-0:1.3.4:1.0-event-joystick \ --device-name "Player_2" \ --evdev-absmap ABS_X=x1,ABS_Y=y1 \ --evdev-keymap BTN_THUMB=a,BTN_TOP=b,BTN_PINKIE=x,BTN_TRIGGER=y,BTN_BASE=lb,BTN_THUMB2=back,BTN_TOP2=start \ --ui-axismap X1=KEY_F:KEY_R,Y1=KEY_G:KEY_D \ --ui-buttonmap a=KEY_S,b=KEY_P,x=KEY_A,y=KEY_W,back=KEY_J,start=KEY_H \ --ui-buttonmap back+start=cycle-key:KEY_ESC:KEY_LEFTCTRL+KEY_LEFTSHIFT+KEY_LEFTALT+KEY_Q \ & sudo /opt/retropie/emulators/moonlight/moonlight stream -bitrate 5000 -audio local -720 -fps 30 192.168.0.5 -app "UnderDefeat" moonlight quit 192.168.0.5 sudo killall > /dev/null 2>&1 xboxdrv

The above script invokes xboxdrv, maps out 2 of my joysticks as against keyboard inputs and then starts moonlight and, ultimately, the game Under Defeat via an emulator on my Windows 7 based PC.

@mitu said in Issue configuring PowerA Fusion wired XBox One controller:

@AdamBeGood You should have opened a new topic instead of bumping 2 years old topics.

I'm sorry, I should have started a new topic and referenced this thread. Apologies.

Let me know if I am okay to carry on posting here now, or if the best route is to still open a new topic.

Your issue is probably caused by the usage of rpi-update, which overwrote the xpad driver with the stock Linux kernel version. As explained throughout the topic, RetroPie includes a patched version, which modifies the default driver behavior and maps the triggers as buttons instead of axis.
Don't use rpi-update as a regular update mechanism - it's not intended to be used as such. RetroPie uses dkms to install additional Linux kernel drivers, so that any normal Linux kernel update (via apt) will automatically re-install the drivers. When using rpi-update, this is not possible and causes issues if you rely on a certain driver to be installed and working.

I wouldn't normally use rpi-update but I wanted to try out the KMS change to see how that affected N64 emulation.

Any idea how I resolve this issue now? I looked at amending the line mentioned in the thread but that line doesn't seem to be present in my script, and there is a reference to the trigger issue also so I think the script has been updated since the above was written.

dkms install -m xpad -v 0.4 -k "$kernel" dkms install --force -m xpad -v 0.4 -k "$kernel"

I tried re-installing xpad from Source but that hasn't changed anything.

The below line is also present in "xpad.conf"

options xpad triggers_to_buttons=1

My controller is connected by a USB lead, I'm not using Bluetooth.

Later Edit: it is especially strange as it is only my Elite Controller that is having this issue. Standard XBox One Controller is perfect.

@aditkrator Can you check my update in the other topic to see if the workaround I posted there works for you also ?

@jasonw im having the same issue with the 360 controllers going all weird after the update. i guess your way is the best, just dont update for now. ill roll back to an image before the update and move on.

Here are some tests i have done :

$ jstest /dev/input/js0 Driver version is 2.1.0. Joystick (PowerA Xbox One wired controller) has 6 axes (X, Y, Rx, Ry, Hat0X, Hat0Y) and 13 buttons (BtnX, BtnY, BtnTL, BtnTR, BtnTR2, BtnSelect, BtnStart, BtnMode, BtnThumbL, BtnThumbR, ?, ?, ?). Testing ... (interrupt to exit) Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off 12:off $ lsmod | grep xpad xpad 18566 0 ff_memless 5315 1 xpad $ evtest /dev/input/event[0] Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x24c6 product 0x543a version 0x101 Input device name: "PowerA Xbox One wired controller" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 304 (BTN_SOUTH) Event code 305 (BTN_EAST) Event code 307 (BTN_NORTH) Event code 308 (BTN_WEST) Event code 310 (BTN_TL) Event code 311 (BTN_TR) Event code 312 (BTN_TL2) Event code 313 (BTN_TR2) Event code 314 (BTN_SELECT) Event code 315 (BTN_START) Event code 316 (BTN_MODE) Event code 317 (BTN_THUMBL) Event code 318 (BTN_THUMBR) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 1 (ABS_Y) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 3 (ABS_RX) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 4 (ABS_RY) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 16 (ABS_HAT0X) Value 0 Min -1 Max 1 Event code 17 (ABS_HAT0Y) Value 0 Min -1 Max 1 Event type 21 (EV_FF) Event code 80 (FF_RUMBLE) Event code 81 (FF_PERIODIC) Event code 88 (FF_SQUARE) Event code 89 (FF_TRIANGLE) Event code 90 (FF_SINE) Event code 96 (FF_GAIN)

I had no trouble to connect both x-Box one s controller via Bluetooth (pi 3b - disable ertm and updated retropie and the both controllers via my Xbox one). I conectet the first one and after it was done I connected the other one. But I have trouble to configure them in the retroarch GUI. Does the controllers work in retroarch gui for you?

Well, I don't think that this issue's gonna get fixed but because I was impatient I decided to flash regular Raspbian and I think that I'm gonna just dual-boot Lakka (Since it uses more of RetroArch functions natively).

@backstander

That is funny. I guess he either meant that it doesn't work with RetroPie, or meant to list it under Pros. The review might have actually been written by a forum user named @PECONAUT. I don't know if he ever got his issue with the controller sorted out, but the "Liquid Metal" stuck out in my memory. It's a sharp looking controller and a good deal. It also might still be possible to get it working. You just never know with a 3rd party controller.

@overfl0w Try this! It worked for me
https://retropie.org.uk/forum/topic/6198/xbox-one-controller-via-bluetooth/26

Sorry, I guess I just assumed it was, but yes it's cased with a fan using a 5V/2.5A power supply. I haven't checked that, I haven't used Linux in years so pretty much back to beginner but I can take a look later on today when I get home. Not sure about the firmware, I've tried so many things it's a possibility but I honestly can't remember.

I've got some problems with 1708 revision gamepad. Moving to 4.8+ kernel solved the problem for me. 4.9 is in the NEXT branch now btw. But older gamepad revisions seemed to work well afaik. Is it working at all (LED on..?)

No matter what I tried, I couldn't get XBOX One and XBOX One S controller working on RetroPie 4.1 (and on 3.8) running on Raspberry Pie 1 Model B.

However, when I tried the same thing on Raspberry Pie 3 Model B, it worked like charm. It worked both for XBOX One and XBOX One S controllers. But I had issues connecting XBOX One S controller via Bluetooth; which I need to research further.

With this experience of mine, I believe we can safely assume that Raspberry Pie 1 Model B is somehow incapable of pairing with XBOX One and XBOX One S controllers.

Thanks,

Version 4.1.1 (grabbed it from github with manual install on raspbian). RPi model B.
Yeah, tried both removing and reinstalling. No luck with that. Maybe github version of the driver is a bit outdated..? product and vendor ID's are correct, but something is just not working with 4.4 kernel.