Skip to contentSkip to conversation

New: Bluetooth headset auto connected but failed to recognize as audio device

Bug 204629 [email protected] 1 participant 5 messages Aug 19, 2019 – Oct 24, 2021 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=204629

            Bug ID: 204629
           Summary: Bluetooth headset auto connected but failed to
                    recognize as audio device
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.2.8
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

This bug was originally reported to KDE
https://bugs.kde.org/show_bug.cgi?id=368883

When i start my headset, my bluetooth headset is autoconnect to kde. When it finish, the device is not added to output sound device.

When i diconnect and reconnect manualy, it works :)

Reproducible: Always

Steps to Reproduce:

1. Pair a bluetooth headet and configure it as auto connect
2. Auto connect the headset.
3. If not recognized, disconect and reconnect the headset manually.

Expected Results:

Audio device should be recognized automatically

Actual Results:

Audio device is not recognized. But when manually connect to it, it can be recognized as audio device by PulseAudio.

System logs:

bluetoothd[1896]: Unable to get io data for Headset Voice gateway: getpeername:
Transport endpoint is not connected (107)
dbus-daemon[953]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.37" (uid=1000 pid=2239 comm="/usr/bin/pulseaudio --daemonize=no ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.11" (uid=0 pid=1896 comm="/usr/lib/bluetooth/bluetoothd ")

I guess the cause might be: when the bluetooth signal appears, Bluez immediately connect to it and try to exchange data with it. But the headset is still booting and not ready for answering any request. And Bluez failed without retrying. Maybe it should keep trying every 3 seconds, maximum 5 times (15 seconds).

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
#1 lore raw

[Bug 204629] Bluetooth headset auto connected but failed to recognize as audio device

https://bugzilla.kernel.org/show_bug.cgi?id=204629

Juha-Pekka Savolainen ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |juha-pekka.savolainen@uniki
                   |                            |e.com

--- Comment #2 from Juha-Pekka Savolainen ([email protected]) --- Can you provide relevant commit(s) in master branch? I'm facing similar looking issue but can not upgrade the BlueZ. I could however try by patching the current version if pointed to correct commit(s).

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#2 lore raw

[Bug 204629] Bluetooth headset auto connected but failed to recognize as audio device

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=204629

mirh ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #3 from mirh ([email protected]) ---
b0ebdd778b06a71c1cbc2fcf30d7fe5842e749fb I guess?
Is this still a thing?

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#3 lore raw

[Bug 204629] Bluetooth headset auto connected but failed to recognize as audio device

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=204629

Cody Rude ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #4 from Cody Rude ([email protected]) ---
I'm having this same problem in bluez 5.62, which contains the commit to provide more updated logging information. However, the original error message is appearing, which I guess implies that this is an io error and not a regular error.

Here are my bluetooth logs:

Quoted 27 lines
Oct 16 21:58:51 Neltharion bluetoothd[413]: Bluetooth daemon 5.62
Oct 16 21:58:51 Neltharion bluetoothd[413]: Starting SDP server
Oct 16 21:58:51 Neltharion bluetoothd[413]: Bluetooth management interface
1.21 initialized
Oct 16 21:58:51 Neltharion dbus-daemon[414]: [system] Activating via systemd:
service name='org.freedesktop.hostname1'
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.2' (uid=0
pid=413 comm="/usr/lib/bluetooth/bluetoothd ")
Oct 16 22:09:46 Neltharion bluetoothd[413]: Endpoint registered: sender=:1.37
path=/MediaEndpoint/A2DPSink/sbc
Oct 16 22:09:46 Neltharion bluetoothd[413]: Endpoint registered: sender=:1.37
path=/MediaEndpoint/A2DPSource/sbc
Oct 16 22:09:46 Neltharion bluetoothd[413]: Endpoint registered: sender=:1.37
path=/MediaEndpoint/A2DPSink/sbc_xq_453
Oct 16 22:09:46 Neltharion bluetoothd[413]: Endpoint registered: sender=:1.37
path=/MediaEndpoint/A2DPSource/sbc_xq_453
Oct 16 22:09:46 Neltharion bluetoothd[413]: Endpoint registered: sender=:1.37
path=/MediaEndpoint/A2DPSink/sbc_xq_512
Oct 16 22:09:46 Neltharion bluetoothd[413]: Endpoint registered: sender=:1.37
path=/MediaEndpoint/A2DPSource/sbc_xq_512
Oct 16 22:09:46 Neltharion bluetoothd[413]: Endpoint registered: sender=:1.37
path=/MediaEndpoint/A2DPSink/sbc_xq_552
Oct 16 22:09:46 Neltharion bluetoothd[413]: Endpoint registered: sender=:1.37
path=/MediaEndpoint/A2DPSource/sbc_xq_552
Oct 16 22:11:32 Neltharion bluetoothd[413]:

src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#4 lore raw

[Bug 204629] Bluetooth headset auto connected but failed to recognize as audio device

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=204629

--- Comment #5 from Cody Rude ([email protected]) ---
I've discovered that setting the headphones as trusted fixes the issue and it auto-connects properly

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.