Wrong volume binding when connecting bluetooth speakers

Bug #1008539 reported by Andrei
114
This bug affects 23 people
Affects Status Importance Assigned to Milestone
pulseaudio (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I have a 2.1 speaker system and a Logitech bluetooth adapter for them that connects to my Asus UL50AG notebook for sound.
In Sound Settings, I then have 2 entries: Built-in Audio Card and Logitech Adapter.

The problem is that when I connect/reconnect to the bluetooth adapter, the sound volume knob is not bound to the Logitech Adapter. Instead, in Sound Settings, the Built-in Audio Card is selected instead of the Logitech Adapter. And when I use the multimedia keys on my notebook (Volume Up, Down, Mute), they have effect on the sound coming out of the notebook, not the external speakers.

The expected result would be that, when I connect/reconnect the bluetooth adapter, the volume multimedia keys should bound to the new bluetooth setup, not the internal audio.

affects: ubuntu → gnome-settings-daemon (Ubuntu)
Revision history for this message
Andrei (andrei-doom) wrote :

Solutions:

By editing the /etc/pulse/default.pa we can load the pulseaudio module module-switch-on-connect to autoconnect to an audio sink as soon as it is presented to the pulseaudio sound server. We need to insert the following line

load-module module-switch-on-connect

-----
or
-----

stream2ip

----
or
----

bt-autoconnect

But still, right after connecting, the volume returned to the adapter is very loud at first; after I move the volume slider even a bit from its current location, then the volume corrects itself suddenly to it's ACTUAL position. This is so messed up in so many ways I can't even try to imagine the back-end of this all wreckage.... Just freaking do something... it's quite embarrassing.

affects: gnome-settings-daemon (Ubuntu) → pulseaudio (Ubuntu)
Revision history for this message
Andrei (andrei-doom) wrote :

The first solution is the best. Why wasn't it incorporated already in 12.04 ? Hell, why not even earlier ?

The problem remains with the volume right after the connection.
If the bluetooth audio adapter re-connects automatically after resume from suspend, the volume mutes, then you can set it wherever you want. That's perfect, because it doesn't go to full 100% to blow your ears off.
But, if you manually connect the bluetooth audio adapter, then the volume immediately hits 100% and you need to move the volume slider for the volume to retake it's ACTUAL intensity and not blow your ears off or cause you a heart attack...

Revision history for this message
Andrei (andrei-doom) wrote :

bump

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pulseaudio (Ubuntu):
status: New → Confirmed
Daniel Hahler (blueyed)
Changed in pulseaudio (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Andrei (andrei-doom) wrote :

Ah, finally. Now we're getting somewhere. Let's hope it's not going to transform into nowhere.

Revision history for this message
Andrei (andrei-doom) wrote :

Bump

Revision history for this message
Andrei (andrei-doom) wrote :

bump

Revision history for this message
Raymond (superquad-vortex2) wrote :

i don't think switch on connect should be default since user can connect multiple usb audio cards on a desktop

Revision history for this message
VisionInit (visioninit) wrote :

Oh wow - you explained this problem very well!! It has woken up my housemates many times.

Revision history for this message
Klaus Sobczynski (spamerella) wrote :

Please fix this. It's really annoying to have to go to the audio settings every time when you connect bluetooth speakers!

Revision history for this message
Andrei (andrei-doom) wrote :

"Oh wow - you explained this problem very well!! It has woken up my housemates many times."
Huh ?

@Klaus: Just use my first solution and it works pretty decent:
"By editing the /etc/pulse/default.pa we can load the pulseaudio module module-switch-on-connect to autoconnect to an audio sink as soon as it is presented to the pulseaudio sound server. We need to insert the following line

load-module module-switch-on-connect"

PS: I've lost my hope to this cause. It will never get resolved guys, just face it, when there's not something important to fix, they just ignore it. It's easier this way. I'm sick of this attitude. Just apply the solution I found and be happy that there is such one, instead of not having a fix at all. Yes, I know that by doing this all the time, with all of the problems, Linux is STILL going to have <5% market share, but hey, what can you do, right ? I'm out.

Revision history for this message
Klaus Sobczynski (spamerella) wrote :

Hi Andrei, the first solution works but this issue with the volume. Thanks anyway!

> Yes, I know that by doing this all the time, with all of the problems,
> Linux is STILL going to have <5% market share, but hey, what can you do, right ? I'm out.

Weird thing is in some earlier version of ubuntu all this audio/bluetooth business worked--and not only that, it seemed far more usable and easier to access than in that windows vista/7 or whatever I have there.

@ubuntu people: C'mon, fix it. It can't be that hard.

Revision history for this message
Luke Yelavich (themuso) wrote : Re: [Bug 1008539] Re: Wrong volume binding when connecting bluetooth speakers

To all affected, please get a log from PulseAudio as outlined here: https://wiki.ubuntu.com/PulseAudio/Log. Make sure you log PulseAudio's output when you connect the bluetooth adapter/change cards to be used, and when you attempt to change the volume with multimedia keys, to make sure PulseAudio's activity is logged when this occurs.

Revision history for this message
Sicco van Sas (sicco) wrote :

This bug is affecting me as well on Ubuntu 12.04 (64 bit). I connect to a Logitech Wireless Speaker Adapter (http://www.logitech.com/en-roeu/product/wireless-speaker-adapter?crid=47) via bluetooth so to stream my audio to the speaker connected to the Logitech device. The audio switches over to the bluetooth connected speakers just fine, but the 'Output' in 'Sound Settings' doesn't as it still selects the standard 'Speakers' of my laptop instead of the '(8D) Logitech Adapter'. The results is that the volume controls on my keyboard still affect the internal laptop speakers (accompanied with the Ubuntu 'increase/decrease volume' *plop* sounds coming out of my laptop speakers) instead of the audio coming out of my bluetooth connected speakers. Every time I connect the bluetooth speakers I have to go to 'Sound Settings' and select '(8D) Logitech Adapter' as output so the volume controls affect it (the situation just after connecting to the bluetooth device is shown in the attached screenshot). As suggested by the other people in this bug, the Output in Sound Settings should automatically switch over to the newly connected bluetooth audio device.

I attached two logs as requisted by Luke Yelavich. The first log depicts connecting the bluetooth device. In the second log the bluetooth connection is already made and I'm pressing the 'decrease volume' keys several times followed by a series of 'increase volume'. These volume change thus don't affect the bluetooth connected speaker.

Revision history for this message
Sicco van Sas (sicco) wrote :

Here are the two logs I mentioned.

Revision history for this message
Andy Pearson (andyrpearson) wrote :

This issue remains in 14.04.

Bump.

Revision history for this message
Madu Souza (madusouza) wrote :

The bug remains in 14.10. Andrei's solution worked for me.

Revision history for this message
Axel G. Rossberg (axel-rossberg) wrote :

Problem persists until today, first solution by Andrei works (add "load-module module-switch-on-connect" in /etc/pulse/default.pa).

Let me just add that I had to reboot the system for the changes to take effect.

I'd also suggest to ubuntu to add the line by default.

Revision history for this message
Francisco Lopes (oblita) wrote :

Thanks, Andrei fix works for me on latest Gnome 3 on Archlinux! as of 2016/02/27.

Revision history for this message
Fuel (fuel-h) wrote :

Same problem, still present on Ubuntu 16.04! =/

Revision history for this message
bitboy (zeus557) wrote :

This Bug also exists in Distributions based on Ubuntu like Linuxmint. Sometimes its really annoying why bugs aren't fixed over years, even if many users are affected.

Revision history for this message
Przemyslaw Kujawski (przemekk) wrote :

I can confirm that this bug is still present on Ubuntu 16.04.1 but solution suggested in first comment fixes it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.