Bose 35 Couldnt Connect Try Again

Currently, Arch Linux supports the A2DP profile (Audio Sink) for remote audio playback with the default installation.

Headset via Pipewire

PipeWire acts as a drop-in replacement for PulseAudio and offers an easy way to prepare Bluetooth headsets. Information technology includes out-of-the-box support for A2DP sink profiles using SBC/SBC-XQ, AptX, LDAC or AAC codecs, and HFP/HSP.

Install pipewire-pulse (which replaces pulseaudio and pulseaudio-bluetooth).

The daemon will be started automatically equally a user service. Use pavucontrol or your desktop environment'due south settings for configuration. For more data, encounter PipeWire#Bluetooth devices.

Bombardment level reporting

Note: This is an experimental feature. Enabling it may prevent some Bluetooth mice from connecting automatically (see GitHub consequence).

To get the electric current battery level of your headset reported to upower, the bluetoothd daemon must be started with experimental features.

This can be done by creating a replacement unit of measurement file for bluetooth.service and appending -E to the ExecStart line. Restart the service later on. Alternatively, experimental features can exist enabled in the configuration file (the corresponding section is given below.)

/etc/bluetooth/main.conf

[General]  [..snip..]  # Enables experimental features and interfaces, alternatively a listing of UUIDs # can exist given. # Possible values: true,false,<UUID List> # Possible UUIDS: # d4992530-b9ec-469f-ab01-6c481c47da1c (BlueZ Experimental Debug) # 671b10b5-42c0-4696-9227-eb28d1b049d6 (BlueZ Experimental Simultaneous Key and Peripheral) # 15c0a148-c273-11ea-b3de-0242ac130004 (BlueZ Experimental LL privacy) # 330859bc-7506-492d-9370-9a6f0614037f (BlueZ Experimental Bluetooth Quality Study) # a6695ace-ee7f-4fb9-881a-5fac66c629af (BlueZ Experimental Offload Codecs) # Defaults to false. Experimental = truthful

Restart the service afterward.

Headset via Bluez5/PulseAudio

This commodity or section is a candidate for merging with Bluetooth.

Install the pulseaudio-alsa, pulseaudio-bluetooth and bluez-utils packages, the last of which provides the bluetoothctl utility.

Notation: Earlier continuing, ensure that the bluetooth device is not blocked by rfkill.

Configuration via CLI

Start bluetooth.service.

At present we can apply the bluetoothctl command line utility to pair and connect. For troubleshooting and more detailed explanations of bluetoothctl see the Bluetooth article. Run

$ bluetoothctl

to be greeted by its internal command prompt. Then enter:

[bluetooth]# ability on [bluetooth]# agent on [bluetooth]# default-agent [bluetooth]# scan on

Now make sure that your headset is in pairing mode. It should exist discovered shortly. For case,

[NEW] Device 00:1D:43:6D:03:26 Lasmex LBT10

shows a device that calls itself "Lasmex LBT10" and has MAC accost "00:1D:43:6D:03:26". We volition now use that MAC address to initiate the pairing:

[bluetooth]# pair 00:1D:43:6D:03:26

Subsequently pairing, you also need to explicitly connect the device (if this does not work, try the trust command beneath earlier attempting to connect):

[bluetooth]# connect 00:1D:43:6D:03:26

If y'all are getting a connectedness error org.bluez.Error.Failed retry by killing existing PulseAudio daemon offset:

$ pulseaudio -grand [bluetooth]# connect 00:1D:43:6D:03:26

Finally, if you want to automatically connect to this device in the futurity:

[bluetooth]# trust 00:1D:43:6D:03:26

If everything works correctly, you now take a divide output device in PulseAudio.

Notation: The device may be off by default. Select its sound contour (OFF, A2DP, HFP) in the "Configuration" tab of pavucontrol.

You can now redirect any audio through that device using the "Playback" and "Recording" tabs of pavucontrol.

You can at present disable scanning again and exit the program:

[bluetooth]# browse off [bluetooth]# exit

Setting up automobile connection

To brand your headset car connect you need to enable PulseAudio'south switch-on-connect module. Do this by adding the post-obit lines to /etc/pulse/default.pa:

/etc/pulse/default.pa

### Automatically switch to newly-connected devices load-module module-switch-on-connect

Media controls

To use the media controls they may be forwarded to MPRIS, where they can exist picked upwards by media players that support MPRIS for external control. See MPRIS#Bluetooth for details.

Configuration via GNOME Bluetooth

Note: The A2DP profile volition not activate using this method with pulseaudio 9/10 due to an ongoing bug, leading to possible depression quality mono sound. Run across #A2DP non working with PulseAudio for a possible solution.

You can apply GNOME Bluetooth graphical front-end to easily configure your bluetooth headset.

Beginning, you need to be certain that bluetooth.service systemd unit is running.

Open GNOME Bluetooth and activate the bluetooth. Subsequently scanning for devices, you tin connect to your headset selecting information technology on the device list. You tin directly access to sound configuration panel from the device menu. On the audio panel, a new sink should announced when your device is connected.

LDAC/aptX

LDAC/aptX codecs are supported as of PulseAudio 15.0. Yous tin can verify the codec you are using for connection as follows:

$ pactl list | grep a2dp_codec

Troubleshooting

Annotation: Many users report frustration with getting A2DP/Bluetooth Headsets to work. see #Switch betwixt HSP/HFP and A2DP setting for additional information.

Bad audio / Static noise / "Muddy" sound

If you feel bad sound quality with your headset, it could in all likelihood exist because your headset is not prepare to the correct contour. See #Switch between HSP/HFP and A2DP setting to solve the problem.

Selected sound profile, but headset inactive and audio cannot be redirected

Deceptively, this carte is available earlier the device has been connected; annoyingly information technology will accept no effect. The carte seems to exist created as presently every bit the receiver recognizes the device.

Brand sure to run bluetoothctl as root and connect the device manually. At that place may be configuration options to remove the need to do this each time, just neither pairing nor trusting induce automatic connecting for me.

Pairing fails with AuthenticationFailed

If pairing fails, you tin try enabling or disabling SSPMode with:

# btmgmt ssp off

# btmgmt ssp on

You may need to turn off BlueTooth while you lot run this control.

Pairing works, but connecting does non

You might see the following error in bluetoothctl:

[bluetooth]# connect 00:1D:43:6D:03:26 Attempting to connect to 00:1D:43:6D:03:26 Failed to connect: org.bluez.Mistake.Failed

To further investigate, check the unit condition of bluetooth.service or have a look at the log as follows:

# journalctl -n twenty

You might encounter a message like this:

bluetoothd[5556]: a2dp-sink profile connect failed for 00:1D:43:6D:03:26: Protocol not available

This may be due to the pulseaudio-bluetooth package non beingness installed. Install it if it missing, and so restart pulseaudio.

It can likewise be due to permission, especially if starting pulseaudio equally root allows you to connect. Add your user to the lp group, then restart pulseaudio. See /etc/dbus-i/system.d/bluetooth.conf for reference.

If the issue is non due to the missing parcel, the problem in this case is that PulseAudio is not catching upwardly. A mutual solution to this trouble is to restart PulseAudio. Annotation that it is perfectly fine to run bluetoothctl equally root while PulseAudio runs every bit user. After restarting PulseAudio, retry to connect. Information technology is not necessary to echo the pairing.

If restarting PulseAudio does non piece of work, you need to load module-bluetooth-discover.

# pactl load-module module-bluetooth-discover

The aforementioned load-module command can be added to /etc/pulse/default.pa.

If that still does non work, or you are using PulseAudio'southward system-wide mode, as well load the following PulseAudio modules (again these tin be loaded via your default.pa or system.pa):

module-bluetooth-policy module-bluez5-device module-bluez5-find

It is also possible there are no write permissions for the owner of /var/lib/bluetooth/. If this is the case, yous may go the device to work by removing and re-pairing it, just the event will return after rebooting. Restoring write permissions fixes this issue:

# chmod -R u+w /var/lib/bluetooth

Connecting works, merely there are sound glitches all the time

This is very likely to occur when the Bluetooth and the WiFi share the same chip as they share the same physical antenna and possibly ring range (2.4GHz). Although this works seamlessly on Windows, this is not the example on Linux.

A possible solution is to move your WiFi network to 5GHz then that there will be no interference. If your card/router does not support this, you tin can upgrade your WiFi drivers/firmware. This approach works on Realtek 8723BE and latest rtl drivers for this scrap from AUR.

If nothing of the previous is possible, a less effective mitigation is to tweak the fragment size and the latency on PulseAudio output port, trying to recoup interference. Reasonable values must be called, considering these settings tin can brand the sound out of sync (e.g. when playing videos). To change the latency of the bluetooth headset's port (e.g. to 125000 microseconds in the following example):

$ pactl set-port-latency-offset <bluez_card> headset-output          125000

where the identifier of the menu can be establish with

$ pacmd list-sinks | egrep -o 'bluez_card[^>]*'

The fragment size can be set in /etc/pulse/daemon.conf and takes effect after a restart of PulseAudio (for more details delight see PulseAudio/Troubleshooting#Setting the default fragment number and buffer size in PulseAudio).

Perhaps it will help to add together options ath9k btcoex_enable=1 to the /etc/modprobe.d/ath9k.conf (with the appropriate bluetooth adapter):

/etc/modprobe.d/ath9k.conf

# possibly set for audio glitches options ath9k btcoex_enable=1

Then restart.

Connecting works, just I cannot play sound

Make certain that you see the following messages in your organization log:

bluetoothd[5556]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource bluetoothd[5556]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink

If you encounter a message like to this, you tin can go on and investigate your PulseAudio configuration. Otherwise, get back and ensure the connexion is successful.

When using GDM, another instance of PulseAudio is started, which "captures" your bluetooth device connection. This tin be prevented by masking the pulseaudio socket for the GDM user by doing the following:

# mkdir -p  /var/lib/gdm/.config/systemd/user # ln -due south /dev/cypher  /var/lib/gdm/.config/systemd/user/pulseaudio.socket

On adjacent reboot the 2d example of PulseAudio will not be started.

It may happen that bluez wrongly considers an headset as non a2dp capable. In this case, search the index of the bluetooth device with

$ pacmd ls

Amidst the output at that place should be a section related to the bluetooth headset, containing something similar to

$ pacmd ls

index: 2         proper name: <bluez_card.XX_XX_XX_XX_XX_XX>         driver: <module-bluez5-device.c>         owner module: 27         properties:                 device.description = "SONY MDR-100ABN"                 device.string = "Twenty:Xx:20:Twenty:XX:Twenty"                 device.api = "bluez"                 device.class = "sound"                 ...

To manually set the contour, run

$ pacmd set-card-profile 2 a2dp_sink

where 2 is the index of the device retrieved through pacmd ls.

Connecting works, sound plays fine until headphones become idle, then stutters

If the headphones play audio correctly until they become idle so stutter on resume (e.thousand. because the sound is paused, or considering no audio is played for a while), try disabling PulseAudio'south automatic sink/source suspension on idle.

Some user reports huge delays or even no audio when the Bluetooth connectedness does not send any data. This is due to the module-suspend-on-idle module, which automatically suspends sinks/sources on idle. Equally this tin cause problems with headset, the responsible module tin can be deactivated.

To disable loading of the module-suspend-on-idle module, comment out the following line in the configuration file in utilise (~/.config/pulse/default.pa or /etc/pulse/default.pa):

~/.config/pulse/default.pa

### Automatically suspend sinks/sources that become idle for likewise long #load-module module-suspend-on-idle

Finally restart PulseAudio to apply the changes.

UUIDs has unsupported blazon

During pairing you might see this output in bluetoothctl:

[CHG] Device 00:1D:43:6D:03:26 UUIDs has unsupported type

This message is a very common i and can be ignored.

PC shows device as paired, just is non recognized by device

This might be due to the device not supporting bluetooth LE for pairing.

Try setting ControllerMode = bredr in /etc/bluetooth/main.conf. See [ii].

Device connects, then disconnects after a few moments

If you come across messages like the post-obit in the journal, and your device fails to connect or disconnects soon after connecting:

bluetoothd: Unable to go connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107) bluetoothd: connect error: Connection refused (111)

This may be because you have already paired the device with another operating organisation using the aforementioned bluetooth adapter (e.g., dual-booting). Some devices cannot handle multiple pairings associated with the same MAC address (i.east., bluetooth adapter). You can ready this by re-pairing the device. Start by removing the device:

$ bluetoothctl [bluetooth]# devices Device XX:XX:Xx:XX:20:Twenty My Device [bluetooth]# remove XX:Xx:XX:XX:XX:XX

Then restart bluetooth.service, turn on your bluetooth adapter, make your device discoverable, re-scan for devices, and re-pair your device. Depending on your bluetooth director, you may need to perform a full reboot in order to re-discover the device.

Apple AirPods have low volume

Create a drib-in file for bluetooth.service with the following contents:

/etc/systemd/system/bluetooth.service.d/noplugin-avrc.conf

[Service] ExecStart= ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=avrcp

Then, restart bluetooth.service, reload its configuration, and reconnect your headset.

Additionally, for AirPods Pro, disable the spatial sound and enable Mono in the settings of your iPhone.

This can also solve issues with some devices that are unable to exist controlled through AVRCP.

Apple AirPods Pro working with PulseAudio as A2DP Sink just not with HSP/HFP

If yous find that AirPods Pro are working with PulseAudio, merely are incapable of using the HSP/HFP configurations (in pavucontrol's Configurations tab, unremarkably listed as unavailable), endeavor switching to pipewire-pulse.

Note that switching to pipewire-pulse (and restarting your computer or the appropriate user-level systemd services) should enable HSP/HFP, only may also disable A2DP. (When selecting A2DP Sink in the Configurations tab, the option is instantly deselected and becomes Off.) If you lot meet this issue, try removing/renaming the /var/lib/bluetooth folder like so:

# mv /var/lib/bluetooth /var/lib/bluetooth.bak

Re-pair your AirPods Pro (and other devices) later on. This should make all configurations (HSP/HFP and A2DP) available once again and easily accessible from pavucontrol and pacmd.

HSP problem: the bluetooth sink and source are created, but no audio is being transmitted

Yous may be missing firmware or the SCO (sound protocol of HSP and HFP) routing might be wrong. Encounter [three] - the firmware for BCM20702 tin can be installed via bcm20702a1-firmware ^AUR or bcm20702b0-firmware ^AUR.

Error: Failed to first discovery org.bluez.Fault.InProgress

If your headset is discovered, but fails to connect with the error "Failed to start discovery org.bluez.Error.InProgress", install bluez-hciconfig ^AUR and run

$ hciconfig hci10          upward $ hciconfig hciX          reset

where X is the identifier of your computer's bluetooth device (typically 0).

You should then be able to connect following the steps in #Configuration via CLI.

Loftier audio volume due to synchronization between headphones and PulseAudio

Equally of PulseAudio xv, "Absolute Volume" interlocks the sound volume of your headphones with PulseAudio, making information technology impossible to change ane without the other. On some headphones, e.g. on the the Hoco W25, this may event in irritating loudness. To disable "Absolute Volume", edit /etc/pulse/default.pa and change the line

          load-module module-bluetooth-discover

          load-module module-bluetooth-discover avrcp_absolute_volume=fake

Switch between HSP/HFP and A2DP setting

This can easily be accomplished by the following command where the card_number tin be obtained by running pacmd list-cards.

$ pacmd prepare-bill of fare-contour          card_number          a2dp_sink

For enabling automatic profile switching from A2DP to HSP when a recording stream appears without whatever role set, you tin suspend auto_switch=2 to load-module module-bluetooth-policy in /etc/pulse/default.pa.

For more data about PulseAudio profiles, see PulseAudio Documentation.

A2DP not working with PulseAudio

Socket interface trouble

If PulseAudio fails when changing the profile to A2DP with bluez 4.1+ and PulseAudio 3.0+, you can try disabling the Socket interface from /etc/bluetooth/main.conf by removing the line Enable=Socket and adding line Disable=Socket.

A2DP sink profile is unavailable

When the A2DP sink contour is unavailable it volition not be possible to switch to the A2DP sink (output) with a PulseAudio front-end and the A2DP sink will not even be listed. This can be confirmed with pactl.

$ pactl list | grep -C2 A2DP      Profiles:              headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, sources: 1, priority: xxx, available: yes)              a2dp_sink: Loftier Fidelity Playback (A2DP Sink) (sinks: 1, sources: 0, priority: 40, available: no)              off: Off (sinks: 0, sources: 0, priority: 0, available: yeah)         Active Profile: headset_head_unit

Trying to manually prepare the card profile with pacmd will fail.

$ pacmd set-bill of fare-profile bluez_card.C4_45_67_09_12_00 a2dp_sink Failed to set carte profile to 'a2dp_sink'.

This is known to happen from version x.0 of Pulseaudio when connecting to Bluetooth headphones via Bluedevil or another BlueZ front-finish. See related bug report.

This upshot also appears after initial pairing of Headphones with some Bluetooth controllers (e.grand. 0a12:0001, Cambridge Silicon Radio) which might default to the Handsfree or Headset - HS service and will not allow switching to the A2DP PulseAudio sink that requires the AudioSink service.

Possible solutions:

For some headsets, using the headset'southward volume or play/pause controls while connected tin trigger the A2DP profile to get bachelor.
It is possible that connecting to a headset via bluetoothctl from bluez-utils will brand the A2DP sink profile available. There is an automation for this every time a bluetooth device is connected: prepare-bt-a2dp ^AUR (detailed usage)

[bluetooth]# connect          headset_MAC_address

Manually switching to Bluetooth'southward AudioSink service which would make the A2DP contour and its A2DP PulseAudio sink available. This can be washed with blueman-manager which included in blueman or by registering the UUID of the AudioSink service with bluetoothctl.

$ bluetoothctl [bluetooth]# menu gatt [bluetooth]# register-service 0000110b-0000-one thousand-8000-00805f9b34fb [bluetooth]# quit

Disable the headset contour

/etc/bluetooth/main.conf

[Full general] Disable=Headset

Enable MultiProfile back up. This may aid with headsets that support A2DP every bit well as Headset sound.

/etc/bluetooth/master.conf

[General] MultiProfile=multiple

Sometimes, none of the steps above volition work. Y'all may have tried rebooting and powering bluetooth off and on to no avail. In this instance, try restarting the bluetooth.service.
For some headphone models with audio command panel, the A2DP profile must be enabled by pressing the Play/Suspension button on the panel.

Gnome with GDM

This article or section is a candidate for merging with #Connecting works, but I cannot play sound.

The instructions below were tested on Gnome 3.24.2 and PulseAudio 10.0 still they may notwithstanding be applicable and useful for other versions.

If PulseAudio fails when changing the profile to A2DP while using GNOME with GDM, y'all demand to prevent GDM from starting its own instance of PulseAudio:

Prevent Pulseaudio clients from automatically starting a server if one is not running by calculation the following:

/var/lib/gdm/.config/pulse/client.conf

autospawn = no daemon-binary = /bin/true

Prevent systemd from starting Pulseaudio anyhow with socket activation:

$ sudo -ugdm mkdir -p /var/lib/gdm/.config/systemd/user $ sudo -ugdm ln -southward /dev/null /var/lib/gdm/.config/systemd/user/pulseaudio.socket

Restart, and check that at that place is no PulseAudio process for the gdm user using:

$ pgrep -u gdm pulseaudio

Further discussion well-nigh this problem and alternative fixes can be plant at [four] and [5]. Alternatively, ane may effort and install fix-bt-a2dp ^AUR.

HFP not working with PulseAudio

HFP-just bluetooth headsets may not exist usable in the standard configuration of PulseAudio. The corresponding profiles occur, but they are not available:

bluetoothctl info output shows:

UUID: Audio Sink                (0000110b-0000-g-8000-00805f9b34fb) UUID: A/Five Remote Control Target (0000110c-0000-grand-8000-00805f9b34fb) UUID: A/5 Remote Control        (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree                 (0000111e-0000-thousand-8000-00805f9b34fb)

pactl listing of respective device shows:

... Profiles:       ...       headset_head_unit: Headset Caput Unit (HSP/HFP) (sinks: 1, sources: i, priority: 30, bachelor: no)

To solve the respective issue, update PulseAudio and BlueZ to latest versions. And then install ofono ^AUR (start and enable using systemctl) and phonesim ^AUR and create / actuate a faux modem as described here [6]:

Note: The steps following the creation of phonesim.conf should be done every time y'all desire to connect the headset.

Create /etc/ofono/phonesim.conf with:

[phonesim] Address=127.0.0.ane Driver=phonesim Port=12345

Start as user:

$ phonesim -p 12345 /usr/share/phonesim/default.xml &

Enable and start ofono service.
Power modem:

$ dbus-send --print-reply --organization --dest=org.ofono /phonesim org.ofono.Modem.SetProperty string:"Powered" variant:boolean:truthful

Activate modem:

$ dbus-send --print-reply --organization --dest=org.ofono /phonesim org.ofono.Modem.SetProperty string:"Online" variant:boolean:truthful

To bank check the results, use the test commands from ofono ^AUR installed in /usr/lib/ofono/exam/. To power, activate, and test the modem you can use:

$ /usr/lib/ofono/test/enable-modem /phonesim $ /usr/lib/ofono/exam/online-modem /phonesim $ /usr/lib/ofono/test/list-modems

The output of the respective modem section should read similar this:

... [ /phonesim ]   Online = i   Powered = 1   Lockdown = 0   Emergency = 0   Manufacturer = MeeGo   ...

Finally, restart pulseaudio and reconnect headset. Now, HFP should be bachelor:

headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, sources: i, priority: thirty, available: yes)

Note: HFP support is non stable and may cause glitches with switching to A2DP; try reconnecting, if the needed mode is not available.

Disable machine switching headset to HSP/HFP

When using a bluetooth headset that supports multiple profiles, some applications switch to HSP/HFP profile automatically. If this behaviour is undesired you can disable this by appending the auto_switch=false parameter to the bluetooth-policy module:

/etc/pulse/default.pa

load-module module-bluetooth-policy auto_switch=false

lunsfordconand1977.blogspot.com

Source: https://wiki.archlinux.org/title/bluetooth_headset