Thanks Igor, I didn't know Bluez issues are being tracked on Github,
would've probably raised this there first/instead. I've opened it here:
https://github.com/bluez/bluez/issues/205, offering a summary, people
can always come here if they need to get traces and such.
** Bug watch added: github.co
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1941977
Title:
PC streams music over low-quality HFP/SCO connec
** Tags added: a2dp hfp sco
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1941977
Title:
PC streams music over low-quality HFP/SCO connection, instead of
A2DP/AVDTP
Status in bluez p
I attached snoop/logs where the PC initiated the connection, for
comparison. There, the issue doesn't happen, the headset calmly allows
the PC to establish all the profiles since the PC connected the ACL.
One can also see the difference in flow:
Aug 29 01:57:02 RhoPC bluetoothd[4053589]: src/devi
That one's clear enough from the earlier log snippet and source:
Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/profile.c:ext_connect() Headset
Voice gateway connected to FC:58:FA:7F:E5:18
Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/service.c:change_state()
0x562f6441d710: device FC:58:FA:7F:
So why did Bluez initiate A2DP even when the headset was the one that
established the ACL?
The bluetoothd logs help out here:
Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/adapter.c:connected_callback()
hci0 device FC:58:FA:7F:E5:18 connected eir_len 5
Aug 29 00:54:47 RhoPC bluetoothd[4046739]:
I've spent a while studying the snoop/syslogs and Bluez source, and I
believe I've narrowed down the issue.
* From the Headset-Initiated snoop, we can see where the headset
connected the ACL (23:54:47 UTC), followed shortly by connecting HFP
(successfully).
* Very soon after the headset connected
** Attachment added: "Syslog taken when the PC initiates the connection"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+attachment/5521418/+files/syslog_PCInitiated
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez i
** Attachment added: "HCI snoop taken when the PC initiates the connection"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+attachment/5521417/+files/PCInitiated.snoop
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
** Attachment added: "Syslog taken when the headset initiates the connection"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+attachment/5521416/+files/syslog_HeadsetInitiated
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
This issue was first discovered when I got this headset 2 years back:
https://www.amazon.co.uk/gp/product/B01C2QCPYI.
STEPS
* Enable Bluetooth on the PC
* Have music or some video playing on the PC
* Power on the (already-paired) headset. It automatically connects to the PC.
11 matches
Mail list logo
