Add the option to Toggle Absolute/Hardware Volume in the volume panel. Currently there is no simple way to enable and disable absolute volume barring diving into the system files and manually editing bluez configs then restarting pipewire and bluez. This isn't the best UX. It would be great if this option was available.
Please explain a bit more why this needs to be a preference in Plasma. This sounds more like something that should be handled better by Pipewire out of the box
(In reply to Nicolas Fella from comment #1) > Please explain a bit more why this needs to be a preference in Plasma. This > sounds more like something that should be handled better by Pipewire out of > the box That is fair that this should be handled by pipewire out of the box. But even if this feature is implemented by pipewire, there needs to be an easy place to configure if it is enabled or disabled.
> there needs to be an easy place to configure if it is enabled or disabled. why? Is there a *subjective preference* why one would choose to have it enabled/disabled?
(In reply to Nicolas Fella from comment #3) > > there needs to be an easy place to configure if it is enabled or disabled. > > why? Is there a *subjective preference* why one would choose to have it > enabled/disabled? Ah, I think I get what you're asking. For me, many of my bluetooth headphones minimum volume is just too loud to comfortably listen to in quiet environments (like a library or such). Having absolute volume is convenient because that means you only have one set of controls to deal with, but having it disabled allows for greater control over exact volume levels.
So your problem is that absolute volume is off but you want it on?
My problem is that absolute volume is enabled for all devices by default and I want the ability to disable it on some devices. This is possible by editing bluez configs but I'd like it if it were an option somewhere in plasma.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I could be wrong but I do not think the intention is for this to be user configurable at their pleasure. Instead it's almost certainly a way to deal with misbehaving hardware and most likely devices needing such toggle for one user should just have it set for everyone upstream by editing (in case of PipeWire) /usr/share/spa-0.2/bluez5/bluez-hardware.conf and then upstreaming the required rule changes to spa/plugins/bluez5/bluez-hardware.conf over at PipeWire's FDO Gitlab repository.