Skip to content
Snippets Groups Projects
Commit 2db8c0a2 authored by P V's avatar P V Committed by George Kiagiadakis
Browse files

bluez5: fix initial profile selection

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.
parent 411378d9
No related branches found
No related tags found
Loading
Pipeline #491873 passed
......@@ -104,6 +104,9 @@ function createDevice(parent, id, type, factory, properties)
end
properties["device.name"] = name
-- initial profile is to be set by m-device-activation, not spa-bluez5
properties["bluez5.profile"] = "off"
-- apply properties from config.rules
rulesApplyProperties(properties)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment