Arch Linux

Maybelline

Member

From: Denver, CO

Registered: 2017-08-10

Posts: 5

Autoselect A2DP profile when Bluetooth headphones connect

I'm pretty sure I've figured this out previously, but it's escaping me after a recent SSD crash.

When I connect my bluetooth headphones (AirFi Matrix2) via Blueberry, they automatically show up in the Configuration tab of pavucontrol.  I'm able to change the Profile to A2DP and it works beautifully.

However, I'm pretty sure that previously, this all happened automatically when I turned on the Bluetooth headphones.  I'm sure there's something I'm missing.

$ cat /etc/bluetooth/audio.conf                                                                                                        

[General]
Disable=Headset # Added this


$ cat /etc/pulse/default.pa | grep switch-on-connect -C5                                                                               
#load-module module-oss device="/dev/dsp" sink_name=output source_name=input
#load-module module-oss-mmap device="/dev/dsp" sink_name=output source_name=input
#load-module module-null-sink
#load-module module-pipe-sink

load-module module-switch-on-connect  # added this

### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else

Anyone know a way to make it set the profile to A2DP as soon as I turn on the headphones?

c00ter

Member

From: Alaskan in Washington State

Registered: 2014-08-28

Posts: 395

Re: Autoselect A2DP profile when Bluetooth headphones connect

This part of the Wiki may help: https://wiki.archlinux.org/index.php/Bl … e_with_GDM

---

UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn

Maybelline

Member

From: Denver, CO

Registered: 2017-08-10

Posts: 5

Re: Autoselect A2DP profile when Bluetooth headphones connect

This part of the Wiki may help: https://wiki.archlinux.org/index.php/Bl … e_with_GDM

Well, I'm running LightDM, not GDM.  But, when I get a chance, I'll give it a try.  However, it seems to me that I had only changed /etc/bluetooth/audio.conf previously -- that's just not doing it this time.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,738

Re: Autoselect A2DP profile when Bluetooth headphones connect

module-bluetooth-policy should be doing that, do you have that loaded? I'm also not entirely sure about that disable in the bluetooth/main.conf are you sure you need that?

Maybelline

Member

From: Denver, CO

Registered: 2017-08-10

Posts: 5

Re: Autoselect A2DP profile when Bluetooth headphones connect

This part of the Wiki may help: https://wiki.archlinux.org/index.php/Bl … e_with_GDM

No dice on the GDM front.  No pulseaudio was running for any user but me.

module-bluetooth-policy should be doing that, do you have that loaded?

It is loaded in /etc/pulse/default.pa (in an "ifexists" clause).  I also removed the line from bluetooth/audio.conf (I read that audio.conf was deprecated), and rebooted, still no luck.  I'm stumped.

Thanks for trying, gang.

c00ter

Member

From: Alaskan in Washington State

Registered: 2014-08-28

Posts: 395

Re: Autoselect A2DP profile when Bluetooth headphones connect

I have read about this problem before--have run into it myself--and thought I had it all bookmarked.

Here: https://bbs.archlinux.org/viewtopic.php … 8#p1705498
Here:  https://bbs.archlinux.org/viewtopic.php … 8#p1722778

Buena Suerte!

Last edited by c00ter (2017-08-15 02:05:00)

---

UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn

Maybelline

Member

From: Denver, CO

Registered: 2017-08-10

Posts: 5

Re: Autoselect A2DP profile when Bluetooth headphones connect

I have read about this problem before--have run into it myself--and thought I had it all bookmarked.

Here: https://bbs.archlinux.org/viewtopic.php … 8#p1705498
Here:  https://bbs.archlinux.org/viewtopic.php … 8#p1722778

Buena Suerte!

I tried most/all of that, to no avail.  But, after some more googling, I'm finding [this bug](https://bugs.freedesktop.org/show_bug.cgi?id=92102), which matches my logs:

Aug 15 10:41:02 Rumble pulseaudio[548]: W: [pulseaudio] module-bluez5-device.c: Profile has no transport
Aug 15 10:41:09 Rumble bluetoothd[334]: /org/bluez/hci0/dev_A0_E9_DB_12_4E_FF/fd0: fd(26) ready

It looks like pulseaudio is trying to switch to A2DP a few seconds before bluetoothd actually has the device ready.