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:E5:18 profile Headset Voice gateway state
changed: disconnected -> connecting (0)
Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/service.c:change_state()
0x562f6441d710: device FC:58:FA:7F:E5:18 profile Headset Voice gateway state
changed: connecting -> connected (0)
This ext_connect() seems to be called whenever a profile connection is
completed, whether successfully or not, whether locally or remotely
initiated. Above, we see the state changes it orchestrated -- it first
transitions the HFP "service" to CONNECTING and then to CONNECTED pretty
quickly:
if (conn->service && service_set_connecting(conn->service) < 0)
goto drop;
...
if (conn->service)
btd_service_connecting_complete(conn->service,
err ? -err->code : -EIO);
Each of these state changes gets propagated to a bunch of listeners --
one of which is policy.c.
=========================
I think that first transition (to CONNECTING) should not have happened, because
it takes away the ability of any listeners to judge whether a connection was
locally or remotely initiated, and act accordingly. The HFP service should've
simply gone from DISCONNECTED to CONNECTED -- that first IF block should be
removed entirely.
=========================
If a connection were indeed locally initiated, the service's state
would've been set to CONNECTING way back, by btd_service_connect()
probably since it looks to be the one that kicks off the connection.
ext_connect() only has enough info to make that final jump to CONNECTED.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded 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 package in Ubuntu:
New
Bug description:
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.
EXPECTED RESULT
The PC's audio should now be streamed to the headset, over high-quality A2DP
ACTUAL RESULT
The PC's audio gets streamed over the low-quality HFP/SCO connection instead.
Stopping and resuming the stream changes nothing. I have to manually
open Blueman and right-click on the device and select "High-quality
A2DP profile", for it to switch to the expected high-quality A2DP
transport.
HCI snoop logs and verbose bluetoothd-syslogs taken in both headset-
initiated and PC-initiated connections are attached.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3.3 [modified:
lib/systemd/system/bluetooth.service]
ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114
Uname: Linux 5.4.0-74-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 29 03:49:08 2021
InstallationDate: Installed on 2019-06-08 (812 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. XPS 13 9380
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic
root=UUID=93dae559-0f0d-4e36-9318-ee7154840a9f ro
resume=UUID=01c18f00-e0eb-4891-9bf1-3110416d9b39 quiet splash
mem_sleep_default=deep vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.1
dmi.board.name: 0KTW76
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.12.1:bd12/14/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc.
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 9C:B6:D0:99:1D:20 ACL MTU: 1024:8 SCO MTU: 50:8
UP RUNNING PSCAN
RX bytes:3313120 acl:776 sco:26275 events:305102 errors:0
TX bytes:255208317 acl:298108 sco:22053 commands:6779 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2020-04-27T23:21:52.866445
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
