[Bug 1197607] New: Bluetooth speaker has no volume control (sound full on)
http://bugzilla.opensuse.org/show_bug.cgi?id=1197607 Bug ID: 1197607 Summary: Bluetooth speaker has no volume control (sound full on) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai@suse.com Reporter: websl-osmat@vasten.co.uk QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 857434 --> http://bugzilla.opensuse.org/attachment.cgi?id=857434&action=edit dmesg Not sure if this belongs in the "sound" or "bluetooth" categories. I'm running the MATE desktop. My laptop, previously installed with OpenSUSE 15.3, was upgraded using the approved upgrade process to 15.4 beta. All working as expected, except the paired bluetooth speaker. Bluetooth connects perfectly, but the speaker is at full volume. The mate volume control applet sliders have no effect on bluetooth speaker output. Volume control works perfectly with the built=in speaker. inxi -E Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb Report: bt-adapter ID: hci0 state: up address: 5C:3A:45:DC:9A:F6 inxi -A Audio: Device-1: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition Audio driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.14.21-150400.11-default running: yes Sound Server-2: PulseAudio v: 15.0 running: yes inxi -b System: Host: bumpkin Kernel: 5.14.21-150400.11-default x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Leap 15.4 Beta Machine: Type: Laptop System: HUAWEI product: NBLL-WXX9 v: M1030 serial: 87KPM20908000217 Mobo: HUAWEI model: NBLL-WXX9-PCB v: M1030 serial: PM13P02095001247 UEFI: HUAWEI v: 1.05 date: 07/20/2020 Battery: ID-1: BAT1 charge: 51.4 Wh (100.0%) condition: 51.4/54.9 Wh (93.5%) CPU: Info: 6-Core AMD Ryzen 5 4500U with Radeon Graphics [MCP] speed: 1397 MHz min/max: 1400/2375 MHz Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel Device-2: Quanta ov9734_techfront_camera type: USB driver: uvcvideo Display: server: X.org 1.20.3 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa tty: 132x40 Message: Advanced graphics data unavailable in console for root. Network: Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8822ce Drives: Local Storage: total: 476.94 GiB used: 243.88 GiB (51.1%) Info: Processes: 257 Uptime: 0h 29m Memory: 7.13 GiB used: 2.17 GiB (30.4%) Init: systemd runlevel: 5 Shell: Bash inxi: 3.3.07 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197607 http://bugzilla.opensuse.org/show_bug.cgi?id=1197607#c1 --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- Could you check the behavior with pavucontrol, too? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197607 http://bugzilla.opensuse.org/show_bug.cgi?id=1197607#c2 --- Comment #2 from Stevan Lockhart <websl-osmat@vasten.co.uk> --- Thanks for the reply. I was going to leave this for another day to see if I now understood it better. To reply to your question, yes, I tried pavucontrol, and the outcome was the same, ie different to 15.3, the speakers were set at maximum volume. I decided to try various things, a switched to pipewire, with the pulse plugin. (Nice work, pipewire and sound team -the switch was seamless.) But the outcome was the same; moving the volume slider appeared to have no effect. Idly, I clicked the volume control on the speakers, and the slider moved! What's more the volume decreased. I them realised that, if I moved the slider very very slowly, the volume was able to change. It "feels" as though the volume control now tells the bluetooth speaker to reduce or increase volume, and there is a long lag between moving the slider and the speakers responding. I have not tried this on bluetooth headphones, but I imagine it must be the same for those - the mate-volume-control - (and presumably pavucontrol) doesn't control output but seems to instruct the bluetooth device to reduce or increase volume. Under 15.3, the effect of using the slider was immediate and predictable. I hope that makes sense. Stevan -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197607 http://bugzilla.opensuse.org/show_bug.cgi?id=1197607#c3 --- Comment #3 from Stevan Lockhart <websl-osmat@vasten.co.uk> --- I've now done a little more work on this issue and may understand the cause, but I have a poor understanding of the interaction between bluetooth, pulse, etc, so may be wide of the mark. I noticed that, under "Sound Preferences", "Hardware", the bluetooth device was listed as disabled, even though it was working. I changed "Settings for the selected device" from the default "High Fidelity playback (A2D2 Sink, codec SBC)" to ""High Fidelity playback (A2D2 Sink, codec SBC-XQ)" and the device was no longer enabled. The volume control sliders work perfectly with this setting. So I suspect the change may be with the selection of the default sink, but here's where my knowledge becomes even sketchier. --------------------- pactl list short sinks 42 alsa_output.pci-0000_03_00.6.analog-stereo PipeWire s32le 2ch 48000Hz SUSPENDED 123 bluez_output.F4_4E_FD_B6_A6_64.a2dp-sink PipeWire s16le 2ch 48000Hz SUSPENDED ---------------------- In short, I don't know if this is specific to my system triggered by the upgrade to 15.4 or if it suggests a wider issue, but it's something that Just Worked under 15.3. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197607 http://bugzilla.opensuse.org/show_bug.cgi?id=1197607#c4 --- Comment #4 from Takashi Iwai <tiwai@suse.com> --- Thanks, that's an interesting outcome. (In reply to Stevan Lockhart from comment #3)
I noticed that, under "Sound Preferences", "Hardware", the bluetooth device was listed as disabled, even though it was working. I changed "Settings for the selected device" from the default "High Fidelity playback (A2D2 Sink, codec SBC)" to ""High Fidelity playback (A2D2 Sink, codec SBC-XQ)" and the device was no longer enabled.
Do you mean no longer "disabled"? IIRC, SBC-XQ is a new profile that wasn't available in the early releases. But it doesn't justify the non-working volume with SBC. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197607 http://bugzilla.opensuse.org/show_bug.cgi?id=1197607#c5 --- Comment #5 from Stevan Lockhart <websl-osmat@vasten.co.uk> --- Yes. The alternative (non-default) sink removes the "Disabled" notice. Can't see a way to add a screenshot to this message but I will try to add them to the original message. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197607 http://bugzilla.opensuse.org/show_bug.cgi?id=1197607#c6 --- Comment #6 from Stevan Lockhart <websl-osmat@vasten.co.uk> --- Created attachment 857625 --> http://bugzilla.opensuse.org/attachment.cgi?id=857625&action=edit Device disabled with default sink -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197607 http://bugzilla.opensuse.org/show_bug.cgi?id=1197607#c7 --- Comment #7 from Stevan Lockhart <websl-osmat@vasten.co.uk> --- Created attachment 857626 --> http://bugzilla.opensuse.org/attachment.cgi?id=857626&action=edit Device now enabled when different sink is selected Volume control works as before when this sink is actively selected. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com