From: "shhhum" <shum@posteo.net>
To: <linux-bluetooth@vger.kernel.org>
Subject: Dualshock 4 usb issues
Date: Wed, 03 Feb 2021 23:43:24 +0300 [thread overview]
Message-ID: <C906S5DXOPDO.28FTLRVJTQB56@shum> (raw)
Hello. I'm using BlueZ 5.55 and Linux 5.10.12.
After following Gentoo guide to connect DS4 with bluetooth -
https://wiki.gentoo.org/wiki/Sony_DualShock#DualShock_4 - I was able to
successfully pair, trust and connect the gamepad.
[bluetooth]# pair A4:53:85:AF:F5:05
Attempting to pair with A4:53:85:AF:F5:05
[CHG] Device A4:53:85:AF:F5:05 Connected: yes
[CHG] Device A4:53:85:AF:F5:05 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device A4:53:85:AF:F5:05 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device A4:53:85:AF:F5:05 ServicesResolved: yes
[CHG] Device A4:53:85:AF:F5:05 Paired: yes
Pairing successful
[CHG] Device A4:53:85:AF:F5:05 WakeAllowed: yes
Authorize service
[agent] Authorize service 00001124-0000-1000-8000-00805f9b34fb (yes/no): yes
[Wireless Controller]# trust A4:53:85:AF:F5:05
[CHG] Device A4:53:85:AF:F5:05 Trusted: yes
Changing A4:53:85:AF:F5:05 trust succeeded
[Wireless Controller]# info
Device A4:53:85:AF:F5:05 (public)
Name: Wireless Controller
Alias: Wireless Controller
Class: 0x00002508
Icon: input-gaming
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: usb:v054Cp09CCd0100
However, recently I've started to notice that after plugging my DS4 with usb I
can no longer connect my DS4 with bluetooth. After some "debugging" I've
noticed that for some reason plugging DS4 with usb cable prints those lines in bluetoothctl:
[CHG] Device A4:53:85:AF:F5:05 Connected: no
[CHG] Device A4:53:85:AF:F5:05 Trusted: no
Authorize service
[agent] Authorize service 00001124-0000-1000-8000-00805f9b34fb (yes/no):
And after some time:
[agent] Authorize service 00001124-0000-1000-8000-00805f9b34fb (yes/no): Request canceled
[DEL] Device A4:53:85:AF:F5:05 Wireless Controller
So my guess is while I'm doing my "buisness", authorization request gets
cancelled and BlueZ automatically deletes the device. But why BlueZ requesting
authorization in the first place if I'm plugging my gamepad through usb?
Inetestingly, authorization is requested every time I plug my gamepad with USB,
no matter if my device is already in "trusted" state.
I'm not sure if this is bug with BlueZ, Linux kernel or if it's even a bug at all,
but since BlueZ deletes my device, I decided to write this to linux-bluetooth
mailing list. I am happy to provide further information if required.
Thanks.
reply other threads:[~2021-02-03 21:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=C906S5DXOPDO.28FTLRVJTQB56@shum \
--to=shum@posteo.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox