Turn off hw-volume feature on Audio Pro A26
- PipeWire version (
pipewire --version
):
pipewire
Compiled with libpipewire 0.3.65
Linked with libpipewire 0.3.65
- Distribution and distribution version (
PRETTY_NAME
from/etc/os-release
):Debian GNU/Linux 12 (bookworm)
- Desktop Environment (
gnome-shell --version
):GNOME Shell 43.4
- Kernel version (
uname -r
):6.1.0-9-amd64
- BlueZ version (
bluetoothctl --version
):bluetoothctl: 5.66
-
lsusb
: (appears irrelevant; two USB hubs and one multitouch interface) - Bluetooth devices:
$ bluetoothctl devices
Device 7C:96:D2:XX:XX:XX Audio Pro_A26
Description of Problem:
After pairing and device connection, volume can be adjusted and the hardware emits a 'blip' sound to demonstrate the updated volume level with each adjustment.
However, after the device is disconnected and reconnected (by disabling and re-enabling the 'bluetooth' option in GNOME, in this case), the volume output by the device is reset to 100% (potentially resulting in high-volume output if audio playback was in progress).
How Reproducible:
Occurs reliably after every disconnect and reconnect.
Steps to Reproduce:
- Pair with the Audio Pro A26 using the GNOME control panel bluetooth settings area.
- Connect to the device (this should occur automatically after pairing, and the device should be confirmed as an audio output).
- Adjust the volume to below 100%.
- Disconnect from the device (either by disabling bluetooth entirely, or by disconnecting from the individual device in the control panel -- either approach reproduces the problem).
- Reconnect to the device.
Actual Results:
Audio output volume for the device is reset to 100% (both as displayed within the GNOME desktop environment, and as the output level of the audio produced by the speakers).
Expected Results:
The volume level selected during step three of the steps-to-reproduce should be restored, so that the audio output volume remains at the level chosen by the user previously.
Additional Info (as attachments):
-
pw-dump > pw-dump.log
:pw-dump.log - Bluetooth debug log: pipewire-bluez.log
Patch
From 3d881074de2c034e424b9a5d0d9bddbdd29ea912 Mon Sep 17 00:00:00 2001
From: James Addison <jay@jp-hosting.net>
Date: Wed, 17 May 2023 22:53:15 +0100
Subject: [PATCH] Audio Pro A26: disable hw-volume feature, because volume was
being reset to 100% on each reconnect
---
spa/plugins/bluez5/bluez-hardware.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/spa/plugins/bluez5/bluez-hardware.conf b/spa/plugins/bluez5/bluez-hardware.conf
index 9004675ea..83b3212f0 100644
--- a/spa/plugins/bluez5/bluez-hardware.conf
+++ b/spa/plugins/bluez5/bluez-hardware.conf
@@ -30,6 +30,7 @@ bluez5.features.device = [
{ name = "Air 1 Plus", no-features = [ hw-volume-mic ] },
{ name = "AirPods", no-features = [ msbc-alt1, msbc-alt1-rtl ] },
{ name = "AirPods Pro", no-features = [ msbc-alt1, msbc-alt1-rtl ] },
+ { name = "Audio Pro_A26", address = "~^7c:96:d2:", no-features = [ hw-volume ]}, # doesn't remember volume
{ name = "AXLOIE Goin", no-features = [ msbc-alt1, msbc-alt1-rtl ] },
{ name = "BAA 100", no-features = [ hw-volume ] }, # Buxton BAA 100, doesn't remember volume, #pipewire-1449
{ name = "D50s", address = "~^00:13:ef:", no-features = [ hw-volume ] }, # volume has no effect, #pipewire-1562
--
2.39.2
Edit: add bluetooth debug log Edit 2: add missing space (there should be two spaces before the comment marker)