A2DP works randomly

Bug #1389781 reported by tobiasBora
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Expired
Low
Unassigned
unity-control-center (Ubuntu)
Expired
Low
Unassigned

Bug Description

Hello,

There is a problem with the bluetooth mode A2DP. When I connect my bluetooth headphone, sometimes I can activate the A2DP mode (which gives a good sound quality) and sometimes I can't (nothing happened when I change it in the configuration window), and I need to switch to HFS/HFP (bad sound quality). Note that some logs are attached.

I found on the internet a work around which is to put in /etc/bluetooth/audio.conf a line
    Disable=Socket

It seems to work (well it's hard to say for the moment because I didn't have the time to do much tests), but I would like to know what Socket is supposed to do.

Would it be possible to solve this bug when Socket is activated too ?

Thank you,

Tobias.

Revision history for this message
tobiasBora (tobias-bora) wrote :
Revision history for this message
tobiasBora (tobias-bora) wrote :

In fact even the work around doesn't work... I tried to make my computer sleeping, and then the A2DP mode doesn't work anymore...

Revision history for this message
tobiasBora (tobias-bora) wrote :

After some more researches I found a way to make A2DP work, to do that I need to put in /etc/bluetooth/audio.conf in [General] the line

Disable=Headset

(then sudo service bluetooth restart).

A2DP seems to work now, but there is an other problem which appears : I can't use HSP/HFP mode which is usefull to record a sound from the headphone.

So is there a solution to make both HSP and A2DP usable without a need to edit /etc/bluetooth/audio.conf and restart bluetooth ?

Thank you.

Revision history for this message
bryan paradis (bryan-paradis) wrote :

I have similar problems. Sometimes it works. Sometimes it doesn't. Have used multiple different bluetooth devices. Blueman doesn't work either seems like maybe a permission problem with pulseaudio?

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

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

Changed in bluez (Ubuntu):
status: New → Confirmed
Revision history for this message
bryan paradis (bryan-paradis) wrote :

Try this!

1) Pair the headset and run pavucontrol the pulse audio volume control panel.
2) Go to configuration
3) Change to off
4) Change to a2dp

or

pacmd set-card-profile cardnumber off
pacmd set-card-profile cardnumber a2dp

Opening unity-control-center sound will switch it back to hsp

Here is some output from unity-control-center when I open it with the bluetooth playing and when I try to switch it to a2dp

{code}
bparadis@bparadis-x79:/usr/bin$ unity-control-center 2>&1

(unity-control-center:23002): sound-cc-panel-WARNING **: Unable to find stream for bar '(null)'
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

(unity-control-center:23002): sound-cc-panel-WARNING **: active_output_update - couldn't find a stream from the supposed active output

(unity-control-center:23002): sound-cc-panel-WARNING **: active_input_update - couldn't find a stream from the supposed active input

(unity-control-center:23002): sound-cc-panel-WARNING **: pa_stream_disconnect failed, res = -15

(unity-control-center:23002): GLib-GObject-WARNING **: invalid unclassed pointer in cast to 'GObject'

(unity-control-center:23002): GLib-GObject-CRITICAL **: g_object_set_data: assertion 'G_IS_OBJECT (object)' failed
{code}

Revision history for this message
tobiasBora (tobias-bora) wrote :

Bryan Paradis : I'm sorry but using pulseaudio instead of the system configuration menu doesn't change anything for me (but I'm using KDE, so maybe there isn't the bug that affects Unity ?). But my problem is still here, even with Disable=Headset in my /etc/bluetooth/audio.conf sometimes I need a full reboot to make my bluetooth headset working (sudo services bluetooth restart isn't always enough).

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

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

Changed in unity-control-center (Ubuntu):
status: New → Confirmed
Maxime (lywela)
Changed in bluez (Ubuntu):
assignee: nobody → Maxime (lywela)
assignee: Maxime (lywela) → nobody
Revision history for this message
Angel-inn (christian-bizet) wrote :

Hi

I have similar problems. Sometimes it works. Sometimes it doesn't.
Blueman doesn't work either, and freeze the computer(AAO 725 on Ubuntu 14.04).
Reboot is the only way using "Ctrl+Alt+PrintScreen+b".

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try if that's still an issue with the new bluez stack in wily?

Changed in unity-control-center (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Changed in bluez (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
enebre (enebre) wrote :

I have also a headset bluetooh, and I arrive to set de device but the quality of sound is very bad.
I would like to be able to switch from one sound system to the other (headset or speaker to bluetooth or wired)
 xubuntu 14.4 and debian jessie xfce.
thanks you.

Revision history for this message
Charles DeBergh (cdebergh) wrote :

I have this issue on 14.04.3 as detailed here: http://askubuntu.com/questions/685549/selecting-a2dp-changes-nothing-whats-a-working-conf-file/685597

I have not tried updating to any version other than the current official version for 14.04.3

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

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

Changed in bluez (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for unity-control-center (Ubuntu) because there has been no activity for 60 days.]

Changed in unity-control-center (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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