UE Roll (bluetooth speaker) is displayed as "Headset - \u0002\u0017
My UE Roll (bluetooth speaker) is displayed as a headset in GNOME Settings. It is also described with two non-printing characters.
This is down to the metadata provided by Pipewire:
$ pactl list sinks | cat -v
[...]
Sink #158
State: IDLE
Name: bluez_output.C0_28_8D_xx_xx_xx.1
Description: ^B^W
Driver: PipeWire
Sample Specification: s16le 2ch 48000Hz
Channel Map: front-left,front-right
Owner Module: 4294967295
Mute: no
Volume: front-left: 32510 / 50% / -18.27 dB, front-right: 32510 / 50% / -18.27 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: bluez_output.C0_28_8D_xx_xx_xx.1.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
Properties:
api.bluez5.address = "C0:28:8D:xx:xx:xx"
api.bluez5.codec = "sbc_xq"
api.bluez5.profile = "a2dp-sink"
api.bluez5.transport = ""
card.profile.device = "1"
device.id = "66"
device.routes = "1"
factory.name = "api.bluez5.a2dp.sink"
device.description = "^B^W"
node.name = "bluez_output.C0_28_8D_xx_xx_xx.1"
node.pause-on-idle = "false"
priority.driver = "1010"
priority.session = "1010"
factory.id = "8"
clock.quantum-limit = "8192"
device.api = "bluez5"
media.class = "Audio/Sink"
media.name = "UE ROLL 2"
node.driver = "true"
factory.mode = "merge"
audio.adapt.follower = ""
library.name = "audioconvert/libspa-audioconvert"
object.id = "78"
object.serial = "158"
client.id = "33"
api.bluez5.class = "0x240404"
api.bluez5.connection = "disconnected"
api.bluez5.device = ""
api.bluez5.icon = "audio-headset"
api.bluez5.path = "/org/bluez/hci0/dev_C0_28_8D_xx_xx_xx"
bluez5.auto-connect = "[ hfp_hf hsp_hs a2dp_sink ]"
bluez5.profile = "off"
device.alias = "^B^W"
device.bus = "bluetooth"
device.form_factor = "headset"
device.icon_name = "audio-headset-bluetooth"
device.name = "bluez_card.C0_28_8D_xx_xx_xx"
device.product.id = "0xffff"
device.string = "C0:28:8D:xx:xx:xx"
device.vendor.id = "bluetooth:000a"
Ports:
headset-output: Headset (type: Headset, priority: 0, available)
Active Port: headset-output
Formats:
pcm
Perhaps Pipewire should be sanitizing the descriptions of its devices, if you think that's more appropriate I will move the issue to their issue tracker.