Skip to content

bluez5: fix initial profile selection

P V requested to merge pvir/wireplumber:bluez-start-off into master

Currently, spa-bluez5 devices start in non-off profile, which causes m-device-activation logic to set the highest priority profile instead of the saved one.

Fix this by having spa-bluez5 start devices in off profile, similarly as spa-alsa does.

This will start working in Pipewire releases containing pipewire!1131 (merged) On earlier Pipewire versions, this is a no-op.

Fixes #143 (closed)

Merge request reports