https://bugs.kde.org/show_bug.cgi?id=520606
Nate Graham <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Status|REPORTED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Nate Graham <[email protected]> --- (In reply to Piotr from comment #0) > A WirePlumber workaround fixes the issue, but only when both options are > used: > > monitor.bluez.properties = { > bluez5.enable-hw-volume = false > bluez5.dummy-avrcp-player = true > } This indicates that it's actually the device that's rejecting the system's attempt to control the volume, and instantly resetting it to the existing level. A device smart/dump enough to do this has to have some kind of UI that lets you disable that behavior, if you find it troublesome. I'd recommend looking for it and using it, if it exists. If not, the workaround you found seems reasonable to keep using. https://pipewire.pages.freedesktop.org/wireplumber/daemon/configuration/bluetooth.html also suggests that many devices are quirky and can need non-default options here. It would seem yours is among them, so I would recommend submitting an issue report about it to the bluez bug tracker. Thanks! -- You are receiving this mail because: You are watching all bug changes.
