Bug 198919 - Xbox (One) Wireless Controller won't connect
Summary: Xbox (One) Wireless Controller won't connect
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: All Linux
: P1 high
Assignee: linux-bluetooth@vger.kernel.org
URL: https://bugs.launchpad.net/gnome-cont...
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-24 15:44 UTC by Jeb Eldridge
Modified: 2024-03-27 19:05 UTC (History)
7 users (show)

See Also:
Kernel Version: Linux 4.13.0-32-lowlatency x86_64
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Jeb Eldridge 2018-02-24 15:44:25 UTC
** SEE THE ORIGINAL BUG REPORT IN LAUNCHPAD HERE: 
https://bugs.launchpad.net/gnome-control-center/+bug/1750146 **

Xbox One Wireless Controllers refuse to connect via bluetooth with Ubuntu 17.10 in the gnome-control-center.
Placing the controller into pairing mode makes it visible on the Bluetooth Devices list and the device pairs, but does not make the full connection needed to pull the controller out of pairing mode.

This renders my controller unusable with my Ubuntu PC unless I want to resort to using the wire (microUSB).

Please fix. See the attached system information below.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
Uname: Linux 4.13.0-32-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 17 09:26:14 2018
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
Comment 1 Jeb Eldridge 2018-05-03 01:07:37 UTC
I've tried on Ubuntu 18.04 LTS and I'm still getting the same issues.
Comment 2 Jeb Eldridge 2018-05-03 01:07:56 UTC
I've tried on Ubuntu 18.04 LTS and I'm still getting the same issues.
Comment 3 Noel 2020-06-05 20:42:57 UTC
Same issues with Ubuntu 20.04 LTS with the 5.7.0 Kernel.
Comment 4 op 2020-08-17 13:12:21 UTC
Same issue in Arch linux kernel 5.8.1. Worked fine before with xpadneo or xpad driver if disabled bluetooth ertm. Works properly with lts kernel (5.4.58) so regression happened somewhere between 5.4 and 5.8. Systemctl status bluetooth spams this:  

Refusing input device connect: No such file or directory (2)
Refusing connection from *controller mac*: unknown device
Comment 5 op 2020-08-17 14:00:26 UTC
Correcting my previous post: doesn't work with lts 5.4 anymore. Seems to be rare occasion that i got it to pair succesfully with 5.4, after that it connected normally with even 5.7 and 5.8. Then suddenly again doesn't connect or pair properly with any of those.
Comment 6 Kai Krakow 2020-09-23 09:41:16 UTC
Yeah, it seems to get worse with every 5.4 LTS update. Worked almost flawless about some months ago (despite taking something from 30-60s to successfully connect). But I don't see a correlation to any commits. But now, it's almost impossible to connect successfully, it usually disconnects after a 1-2 minutes (coincidentally just when entering a game).

I usually also see messages like this:

During use of the controller (probably around disconnect time):
[ 5304.480502] Bluetooth: Unexpected continuation frame (len 52)

When plugging the BT dongle:
[ 5241.926752] Bluetooth: hci0: unexpected event for opcode 0x0000

While it's in a loop of constantly connecting and disconnecting:
[ 1120.736530] Bluetooth: hci0: hardware error 0x58
[ 1120.923550] debugfs: File 'le_min_key_size' in directory 'hci0' already present!
[ 1120.923555] debugfs: File 'le_max_key_size' in directory 'hci0' already present!
[ 1120.923557] debugfs: File 'force_bredr_smp' in directory 'hci0' already present!

Other BT devices seem to just work fine tho I don't use a lot of them and only occasionally. It seems that the Xbox One S firmware does something strange in the BT protocol. It also needs either ERTM disabled to connect. Alternatively, one can apply this patch to be able to use ERTM:

https://github.com/kakra/linux/commit/c8b24d83f227a7fecfa9420d6756074e8f9b542c

I'm also feeling there's some internal state getting messed up within the controller on each BT pairing: Results are not really reproducible. I managed to get it to work flawlessly one time (stable connection despite 20-30s connect handshake time), then purged my Bluetooth config from /var/lib, re-paired the controller and now it's a mess - still with the same kernel version.
Comment 7 Matthias.Pritschet 2020-09-23 09:46:58 UTC
Dear sender!

Thank you for your message! Unfortunately, I am out of office until 27.9.2020 and hence will not be able to reply immediately.
Your email will not be forwarded, but I will answer your email as soon as possible on my return. In very urgent cases, however,
please contact our service center via email <info@escrypt.com<mailto:service@escrypt.com>> or phone +49 234 43870-200.

Yours sincerely,
Matthias Pritschet

Sehr geehrte Damen und Herren,

Vielen Dank für Ihre E-Mail! Ich bin leider bis zum 27.9.2020 nicht erreichbar und kann daher nicht unmittelbar antworten.
Ihre Nachricht wird nicht weitergeleitet. In dringenden Fällen können Sie sich jedoch gern an unser Service-Center (<info@escrypt.com<mailto:service@escrypt.com>> oder +49 234 43870-200) wenden.

Mit freundlichen Grüßen
Matthias Pritschet
Comment 8 Bráulio Bhavamitra 2021-06-30 22:44:08 UTC
I'm having the same Bluetooth errors on dmesg, then it quickly disconnects. KDE will keep trying to connect and disconnect until the device leave the pairing mode.
Comment 9 Vincent Delor 2024-03-20 11:20:52 UTC
I always need to install [Xpadneo](https://github.com/atar-axis/xpadneo) in 2024. Without it, my Xbox One gamepad is not detected. Every distro and DE is affected.
Comment 10 Reaven 2024-03-27 19:03:11 UTC
Hello, can you add drivers for the Xbox controller? It's one of the most used controllers on PC and it's annoying because xpadneo disables secure boot.
Comment 11 Reaven 2024-03-27 19:05:09 UTC
I am also affected by this bug, can you fix it? Thank you.

Note You need to log in before you can comment on or make changes to this bug.