From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 198919] Xbox (One) Wireless Controller won't connect
Date: Wed, 23 Sep 2020 09:41:16 +0000 [thread overview]
Message-ID: <bug-198919-62941-ZMY1AV5AH4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198919-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198919
Kai Krakow (hurikhan77+bko@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hurikhan77+bko@gmail.com
--- Comment #6 from Kai Krakow (hurikhan77+bko@gmail.com) ---
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.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-09-23 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-198919-62941@https.bugzilla.kernel.org/>
2020-08-17 13:12 ` [Bug 198919] Xbox (One) Wireless Controller won't connect bugzilla-daemon
2020-09-23 9:41 ` bugzilla-daemon [this message]
2020-09-23 9:46 ` bugzilla-daemon
2024-03-20 11:20 ` bugzilla-daemon
2024-03-27 19:03 ` bugzilla-daemon
2024-03-27 19:05 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-198919-62941-ZMY1AV5AH4@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.