diff options
| author | Tanu Kaskinen <tanuk@iki.fi> | 2017-09-02 15:44:58 +0300 |
|---|---|---|
| committer | Tanu Kaskinen <tanuk@iki.fi> | 2017-09-05 13:46:27 +0300 |
| commit | 9c7a9be7cd907262683c720f4f9afae3f056a4f1 (patch) | |
| tree | f366a28b695771e9abfded589ef52266b0fc288e /src/modules/bluetooth/bluez5-util.c | |
| parent | 15386a710c1500f70085a6312fb4d84be4d254c9 (diff) | |
| download | pulseaudio-9c7a9be7cd907262683c720f4f9afae3f056a4f1.tar.gz | |
bluetooth: recognize another HSP HS UUID
There are actually two HSP HS UUIDs. My theory is that the second one
was added, because someone was not happy with the old UUID being used
for identifying two different things (the HSP profile as a whole, and
the HS role within the HSP profile). Some headsets only use the new
UUID, and those headsets won't work if we don't recognize the new UUID.
BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=93898
Diffstat (limited to 'src/modules/bluetooth/bluez5-util.c')
| -rw-r--r-- | src/modules/bluetooth/bluez5-util.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/modules/bluetooth/bluez5-util.c b/src/modules/bluetooth/bluez5-util.c index c92832329..304a26e84 100644 --- a/src/modules/bluetooth/bluez5-util.c +++ b/src/modules/bluetooth/bluez5-util.c @@ -176,6 +176,7 @@ static bool device_supports_profile(pa_bluetooth_device *device, pa_bluetooth_pr return !!pa_hashmap_get(device->uuids, PA_BLUETOOTH_UUID_A2DP_SOURCE); case PA_BLUETOOTH_PROFILE_HEADSET_HEAD_UNIT: return !!pa_hashmap_get(device->uuids, PA_BLUETOOTH_UUID_HSP_HS) + || !!pa_hashmap_get(device->uuids, PA_BLUETOOTH_UUID_HSP_HS_ALT) || !!pa_hashmap_get(device->uuids, PA_BLUETOOTH_UUID_HFP_HF); case PA_BLUETOOTH_PROFILE_HEADSET_AUDIO_GATEWAY: return !!pa_hashmap_get(device->uuids, PA_BLUETOOTH_UUID_HSP_AG) |