Connectin XBOX One Controller (White) with Bluetooth

controller

#1

Hi. I have a generic BT 4.0 module (from eBay) that I try to use with my Lakka (x86_64, 2.1) machine

I can pair and trust the controller with bluetoothctl, but cannot connect to it.

This is what bluetoothctl says about the device:

[bluetooth]# info 5C:BA:37:3F:CA:E4
Device 5C:BA:37:3F:CA:E4
	Name: Xbox Wireless Controller
	Alias: Xbox Wireless Controller
	Class: 0x000508
	Icon: input-gaming
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: no
	LegacyPairing: no
	UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
	RSSI: -96

as said, it paired and trusted OK, no problems there.

When I try to connect to it, I get this:

[bluetooth]# connect 5C:BA:37:3F:CA:E4
Attempting to connect to 5C:BA:37:3F:CA:E4
[CHG] Device 5C:BA:37:3F:CA:E4 Connected: yes
[CHG] Device 5C:BA:37:3F:CA:E4 ServicesResolved: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 5C:BA:37:3F:CA:E4 ServicesResolved: no
[CHG] Device 5C:BA:37:3F:CA:E4 Connected: no

listing controller says this:

[bluetooth]# list Controller 00:1A:7D:DA:71:13 BlueZ 5.43 [default]


#2

More info:

If (after that) I do

systemctl status bluetooth

I get this:

Dec 30 12:21:46 Lakka bluetoothd[409]: Can't get HIDP connection info
Dec 30 12:21:53 Lakka bluetoothd[409]: connect error: Invalid exchange (52)
Dec 30 12:22:44 Lakka bluetoothd[409]: Can't get HIDP connection info
Dec 30 12:22:49 Lakka bluetoothd[409]: connect error: Host is down (112)
Dec 30 12:22:54 Lakka bluetoothd[409]: Can't get HIDP connection info
Dec 30 12:23:05 Lakka bluetoothd[409]: connect error: Host is down (112)
Dec 30 12:23:45 Lakka bluetoothd[409]: Can't get HIDP connection info
Dec 30 12:23:55 Lakka bluetoothd[409]: connect error: Invalid exchange (52)
Dec 30 12:23:57 Lakka bluetoothd[409]: Can't get HIDP connection info
Dec 30 12:24:01 Lakka bluetoothd[409]: connect error: Invalid exchange (52)

#3

Bump. I’m having the same kind of issues with my xbox one s controller (black). I’ve tried all of the suggestions detailed here with some success.

  1. From some other distro of linux create autostart.sh in /storage/.config then add this line:

    bash -c ‘echo 1 > /sys/module/bluetooth/parameters/disable_ertm’

Note: For some reason this works only occasionally work for me. Multiple times I’ve checked /sys/module/bluetooth/parameters/disable_ertm from Lakka’s tty and it says N instead of Y so I have to change it manually.

  1. Enable direct access to tty on lakka by adding tty to the bootloader as detailed here.

  2. Then attempt to connect it using the same procedure for the PS4 DualShock listed here.

After multiple attempts to connect it will only sometimes work. Once connected it works great but after rebooting (or shutting down powering) on again the controller will only automatically connect about 1 out of 10 times.

Also I’ve noticed a strange side effect that may or may not be connected but all of my gamecube roms boot extremely slow and the colors are wonked out and pixelated. Characteristically the Nintendo tm will flash from red to blue. No idea what that’s about.

Sorry for running a bit long.

Anyways @AnttiV did you disable_ertm?


#4

Yeah, I did. Unfortunately the ONLY thing that changes is I move from this:

[bluetooth]# connect 5C:BA:37:3F:CA:E4
Attempting to connect to 5C:BA:37:3F:CA:E4
[CHG] Device 5C:BA:37:3F:CA:E4 Connected: yes
[CHG] Device 5C:BA:37:3F:CA:E4 ServicesResolved: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 5C:BA:37:3F:CA:E4 ServicesResolved: no
[CHG] Device 5C:BA:37:3F:CA:E4 Connected: no

to this:

[bluetooth]# connect 5C:BA:37:3F:CA:E4
Attempting to connect to 5C:BA:37:3F:CA:E4
[CHG] Device 5C:BA:37:3F:CA:E4 Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 5C:BA:37:3F:CA:E4 Connected: no

#5

That’s what I get too. And you’ve tried to connecting repeatedly? Also do you keep pressing the pair button at the top of the controller? That’s the only way that I can connect mine.


#6

Same here. I try connecting repeatedly multiple times, but no change really. I’ve never gotten it to work. And yeah I need to press the pair button when the led stops flickering rapidly - I can’t connect to it in non-pairing mode.

I wonder if the Genuine Microsoft USB stick that you use on non-bluetooth-enabled PC would work on Lakka? That’d take the pairing and connecting part out, I think.


#7

Perhaps. I would rather put the ~$30 towards a PS4 DualShock controller instead than sinking more money into getting the xbox controllers up and running. Also it’s almost 2018 no one should have to use dongles (Disclaimer: I mean no disrespect to the Libreto, Lakka, or Retroarch devs the fact that all of it works as well as it does is a real feat of engineering).


#8

Oh, yeah, I wouldn’t pay for it for this purpose alone. I bought my XBOX One controllers to use with my Desktop Win10 PC (which doesn’t have BT) so I already have that. It’s just that I would prefer it to stay on that computer and that I wouldn’t need to swap that between the computers whenever I want to play…

But, I’ll test it at least.

I’ll probably order two Dualshocks to use with Lakka though. As an added bonus they’ll come in handy if I ever decide to purchase a PS4 :slight_smile: (I’m not a huge current-gen console fan though, I much prefer the older generations that I can buy games for cheap. Like the original XBOX and PS2 - and of course everything older that Lakka handles).


#9

Microsoft XBox One Wireless USB Dongle for Windows 10

Long story short: no, it doesn’t work with Lakka :frowning:


#10

That sucks. Thanks for doing the research on that.


#11

Yes unfortunately it is not yet supported on Linux in the xpad driver and also on the dongle driver.


#12

But the controller itself should be, though? At least it is listed as a recommended controller in the Lakka documentation?


#13

Wired should work, it is wireless which is not working.


#14

ooooh, ok. I didn’t know that. (You might want to add that to the recommendation, that it only works wired.)

I do have a couple of nice long sturdy USB cables I can try with. Wireless would of course be better, but I think in my case I can do wired just fine.


#15

I tried to connect a DualShock 4 controller via bluetooth today and couldn’t get it to work either. I give up :frowning:


#16

For the record, XBox One gamepads worked perfectly when connected via USB cables. It was a tad inconvenient with four players and only one had wireless (XBox360 pad), but we managed and had loads of fun.

@draperjames Dualshok 4 is supported wirelessly though. You do have genuine Dualshocks, and not some china knock-offs? (My china xbox360 pads, er… “work”, but not to the extent I’d like to use them :stuck_out_tongue: )


#17

The DualShock 4 controller I was using was out of the box from Best Buy. It kinda worked while wired but I could not get it to pair with bluetooth. I also have a couple xbox 360 controllers and they work great with the genuine microsoft 360 dongle. And I’ve successfully used those controllers with the xbox one controller wired for 3 player mario kart and star fox on the gamecube. I understand that this is a lot to ask for universal bluetooth support for all controllers on all the computers even the raspberry pi so I’m gonna stop complaining :slight_smile:


#18

I know this is an older topic but did anyone have luck pairing an xbox one controller with a generic bluetooth dongle? I know only the newer of the xbox one controllers are bluetooth. I’m trying to pair my controller on an Odroid XU4 if that makes any difference. I can find posts related to the XU4 or to Lakka but not both. Kinda lost.

Edit: After trying a bunch of things I still end up at the same dead end involving “Failed to connect: org.bluez.Error.Failed”

Looks like no resolution for now…