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:
Hi Brian, would you mind filing an issue on bluez tracker for this
analysis here https://github.com/bluez/bluez/issues
To me it looks valid, but still running this through bluez maintainers
is a good idea.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941977
Title:
PC streams music over low-quality HFP/SCO connection,
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941977
Title:
PC streams music over low-quality HFP/SCO connection, instead of
For comparison, I've attached these Android HCI snoop logs, taken when
the same headset initiates a connection to an Android handset this time.
From ~22:00:50 UTC when the ACL was connected between them, one can see
that the handset remains chill, allowing the headset to connect any
profiles its
** Attachment added: "HCI snoop taken when the headset initiates the connection
on Indri"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1941977/+attachment/5522607/+files/HeadsetInitiated_Indri.snoop
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Nope, if anything, it's even worse. On Indri, the PC audio doesn't even
get streamed over SCO at all -- the media channel just gets disconnected
when Bluez times out in the middle of an AVDTP SET_CONFIGURATION. Here,
as before, both headset and Bluez are jockeying for first to
connect/setup A2DP
Please test Ubuntu 21.10 where many of these issues are now fixed and
tell us if the issue persists:
http://cdimage.ubuntu.com/daily-live/current/
** This bug is no longer a duplicate of bug 1838151
Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide
band speech
*** This bug is a duplicate of bug 1838151 ***
https://bugs.launchpad.net/bugs/1838151
Hi Daniel, thanks for responding. This isn't a duplicate of that issue
-- that ticket complains of the current NB/8k default which is pretty
low-quality, now requesting that the stack support WBS/16k for
*** This bug is a duplicate of bug 1838151 ***
https://bugs.launchpad.net/bugs/1838151
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1838151, so it is being marked as such. Please
** Tags added: a2dp hfp sco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941977
Title:
PC streams music over low-quality HFP/SCO connection, instead of
A2DP/AVDTP
To manage notifications about
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]:
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
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
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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 Ubuntu
Bugs, which is subscribed to
18 matches
Mail list logo
