It appears this bug is not fully fixed by 5.85-4ubuntu0.1 for at least one A2DP/AVRCP device.
**System** - Ubuntu 26.04 LTS (Resolute), x86_64, ThinkPad P16s Gen 4 AMD - bluez 5.85-4ubuntu0.1 - pipewire 1.6.2-1ubuntu1.1, wireplumber 0.5.13-1ubuntu1 **Device** - "Stage V2" Bluetooth speaker, Modalias `bluetooth:vE003p3528d0001` - Advertised services: AudioSink (110b), A/V_RemoteControlTarget (110c), AdvancedAudioDistribution (110d), A/V_RemoteControl (110e), PnPInformation (1200) — A2DP sink + AVRCP only, no HSP/HFP. **Symptom** Every attempt to change the sink volume from the host (via PipeWire/WirePlumber, e.g. `wpctl set-volume`) logs: ``` bluetoothd[...]: profiles/audio/avrcp.c:avrcp_set_volume() SetAbsoluteVolume not supported bluetoothd[...]: profiles/audio/transport.c:set_volume() Unable to set volume: Operation not supported (-95) ``` The practical effect: volume is either silent or "full" with no usable range in between; only pushing PipeWire's software gain above 100% produces an audible (clipped) change. Side note: On another bluetooth device (OnePlus Bullets Wireless Z) audio control works as expected. **Steps already tried, none of which resolved it:** 1. Simple disconnect/reconnect (`bluetoothctl disconnect` / `connect`) while keeping the existing pairing. 2. Full removal of the pairing (`bluetoothctl remove`) followed by a fresh pairing. 3. Bluetooth reset on the speaker itself, followed by a fresh pairing. All three produced the identical `SetAbsoluteVolume not supported` log line on the very first volume change attempt after (re)connecting. **Regression timing** On the same laptop under Ubuntu 25.10 (bluez 5.83), AVRCP absolute volume control for this same speaker worked almost always — the only known failure case there was occasionally after resume from suspend. After upgrading to Ubuntu 26.04 (bluez 5.85, including this SRU fix), it fails consistently, on every connection. Happy to provide a `btmon` capture of the AVRCP/AVDTP negotiation if that would help narrow down whether this is a different code path than the one fixed here. (AI assisted summary but I can vouch for the general information it contains) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2156488 Title: [SRU][Resolute] volume control broken when AVRCP connects before AVDTP due to uninitialised target volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2156488/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
