bluetooth-speaker-volume-fix.md

bluetooth-speaker-volume-fix.md

Workaround: Bluetooth Speaker Volume Slider Not Working After Kernel Update (Fedora)

Note: This is a workaround, not a root-cause fix. It disables hardware volume control for Bluetooth devices rather than resolving the underlying volume-mapping bug. If a proper upstream fix lands (kernel or WirePlumber), this page will be updated.

Symptom

• After updating to kernel 7.1.3-200 (or similar), Bluetooth speaker volume control stops working correctly.
• The volume slider (KDE Plasma, GNOME, or other DE) moves visually, but has no effect on the actual output volume of the connected Bluetooth speaker.
• Can result in the speaker playing at full/maximum volume regardless of the slider position — potentially very loud/startling on reboot.

Cause

This is a Bluetooth audio volume-mapping issue between WirePlumber and the Bluetooth device's hardware volume control (bluez5.enable-hw-volume). When hardware volume control is enabled but not working correctly with the device, the software slider and the actual speaker volume become disconnected.

Workaround

Create a WirePlumber drop-in configuration file to disable hardware volume control for Bluetooth devices, forcing volume control to happen in software instead:

mkdir -p ~/.config/wireplumber/wireplumber.conf.d/
cat > ~/.config/wireplumber/wireplumber.conf.d/btvolume.conf <<'EOF'
monitor.bluez.properties = { bluez5.enable-hw-volume = false }
EOF

Then restart WirePlumber to apply the change:

systemctl --user restart wireplumber

Notes

• This workaround is persistent — the config file survives reboots and future kernel updates. No need to reapply it.
• It sidesteps the issue rather than resolving it: hardware volume control is disabled entirely for Bluetooth devices, rather than fixing the mapping between the software slider and the device's actual hardware volume.
• If you still have volume issues after this, try disconnecting/reconnecting the Bluetooth device once to let WirePlumber re-negotiate its audio profile.
• Worth periodically checking whether a kernel or WirePlumber update resolves the underlying bug, at which point this drop-in could be removed.

Environment Tested

• Fedora Linux
• Kernel: 7.1.3-200 (issue first observed here; may affect other versions)
• Desktop Environment: KDE Plasma (also applicable to GNOME/other desktops using WirePlumber/PipeWire)
• Audio stack: PipeWire + WirePlumber

---

Originally diagnosed and shared in an r/Fedora thread. Feel free to repost, adapt, or link back if it helps someone else. Thanks to u/ymmvxd for the useful distinction between workaround and fix.