Bose Headphones unable to Pair

Issues & Assistance
1

So I'm trying to use my bluetooth headphones and I can't get them to pair. I've run into this problem on a debian based distro with these same headphones, but they worked on Ubuntu Studio. I'm wondering if there's some easier way to see what the issue is on Garuda. I'm using the Dr460nized KDE version.

Screenshot__2

After selecting Bose AE2 Sondlink, I next get this screen. I'm not sure what the other item showing in the list is, maybe that's the mac address of the bose phones?:
Screenshot__1

Below are some logs that might help, but my skills aren't developed enough to know what this is telling me. Maybe there are some other logs I should be looking at that you could recommend?

bluetoothctl --version
bluetoothctl: 5.55

rfkill list
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

systemctl status bluetooth

Feb 10 11:15:46 dalegaruda bluetoothd[516]: src/main.c:parse_controller_config() Key file does not have key “LEMinConnectionInterval” in group “Controller”
Feb 10 11:15:46 dalegaruda bluetoothd[516]: src/main.c:parse_controller_config() Key file does not have key “LEMaxConnectionInterval” in group “Controller”
Feb 10 11:15:46 dalegaruda bluetoothd[516]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionLatency” in group “Controller”
Feb 10 11:15:46 dalegaruda bluetoothd[516]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionSupervisionTimeout” in group “Controller”
Feb 10 11:15:46 dalegaruda bluetoothd[516]: src/main.c:parse_controller_config() Key file does not have key “LEAutoconnecttimeout” in group “Controller”
Feb 10 11:15:48 dalegaruda bluetoothd[516]: Starting SDP server
Feb 10 11:15:48 dalegaruda systemd[1]: Started Bluetooth service.
Feb 10 11:15:48 dalegaruda bluetoothd[516]: Bluetooth management interface 1.18 initialized
Feb 10 11:17:06 dalegaruda bluetoothd[516]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSink/sbc
Feb 10 11:17:06 dalegaruda bluetoothd[516]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSource/sbc

Results of

journalctl -n 20

-- Journal begins at Tue 2021-02-02 10:48:55 CST, ends at Thu 2021-02-11 09:13:22 CST. --
Feb 11 09:13:07 dalegaruda auto-cpufreq[3824450]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:07 dalegaruda auto-cpufreq[3824450]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:12 dalegaruda ananicy[566]: renice: firefox[1523215/3824314] 0 -> -3
Feb 11 09:13:14 dalegaruda auto-cpufreq[3825129]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:14 dalegaruda auto-cpufreq[3825129]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:14 dalegaruda auto-cpufreq[3825129]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:14 dalegaruda auto-cpufreq[3825129]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:14 dalegaruda auto-cpufreq[3825129]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:14 dalegaruda auto-cpufreq[3825129]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:14 dalegaruda auto-cpufreq[3825129]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:14 dalegaruda auto-cpufreq[3825129]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:17 dalegaruda ananicy[566]: renice: firefox[1523132/3824472] 0 -> -3
Feb 11 09:13:22 dalegaruda auto-cpufreq[3825268]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:22 dalegaruda auto-cpufreq[3825268]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:22 dalegaruda auto-cpufreq[3825268]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:22 dalegaruda auto-cpufreq[3825268]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:22 dalegaruda auto-cpufreq[3825268]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:22 dalegaruda auto-cpufreq[3825268]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:22 dalegaruda auto-cpufreq[3825268]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 11 09:13:22 dalegaruda auto-cpufreq[3825268]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
2

Debian/Ubuntu is not the same as an Arch based distro. To prepare yourself for the change you need to start researching issues on the Archwiki prior to opening help requests. The Archwiki has very extensive documentation relating how to configure bluetooth for headphones or keyboards.

Research your issue on the Archwiki and if you have further questions post in detail what directions you have tried from their instructions. If you aren't making great progress then someone will likely be able to assist you with all the steps.

3 Likes
3

I've had some issues recently with pairing Bluetooth devices that worked without issue previously.

The most reliable way at the moment seems to be using bluetoothctl directly - check the Arch wiki for detailed steps.

Short version:

$ sudo bluetoothctl
> scan
> connect aa:aa:aa:aa:aa:aa
1 Like
4

@tbg and @jonathon thank you both for your help. Tbg, I had been looking at the archwiki and was confused by what it said, there were issues mentioned having to do with dual boot.

Combining Jonathon's idea to open bluetoothctl directly I was able to watch what was really going on and see that it was failing and the wiki talked about if pairing manually like this didn't work, it was likely related to dual boot. These headphones were previously paired on this machine under a different OS, so this led me to think if I cleared the headphones stored pairings it might work.

Since I had already dropped the other OS's and reused their partitions for Garuda there was no reason to keep the old settings anyway. This did the trick. Pairing worked after clearing using the built in bluetooth gui.

Original failures:

sudo bluetoothctl
Agent registered
[bluetooth]# scan
Missing on/off argument
[bluetooth]# scan on
Discovery started
[CHG] Controller 28:C6:3F:87:CA:02 Discovering: yes
[NEW] Device 6F:3C:1F:4A:55:27 6F-3C-1F-4A-55-27
[NEW] Device 2C:41:A1:1D:D4:E1 Bose AE2 SoundLink
[CHG] Device 2C:41:A1:1D:D4:E1 RSSI: -38
[CHG] Device 2C:41:A1:1D:D4:E1 ManufacturerData Key: 0x0110
[CHG] Device 2C:41:A1:1D:D4:E1 ManufacturerData Value:
  40 0a 01 01 64 5a ed 1d 44 4a                    @...dZ..DJ      
[bluetooth]# pair 2C:41:A1:1D:D4:E1
Attempting to pair with 2C:41:A1:1D:D4:E1
[CHG] Device 2C:41:A1:1D:D4:E1 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationFailed
[CHG] Device 2C:41:A1:1D:D4:E1 Connected: no
[DEL] Device 6F:3C:1F:4A:55:27 6F-3C-1F-4A-55-27
[NEW] Device 6F:3C:1F:4A:55:27 6F-3C-1F-4A-55-27
[DEL] Device 2C:41:A1:1D:D4:E1 Bose AE2 SoundLink
[NEW] Device 2C:41:A1:1D:D4:E1 Bose AE2 SoundLink
[CHG] Device 2C:41:A1:1D:D4:E1 Class: 0x00240418
[CHG] Device 2C:41:A1:1D:D4:E1 Icon: audio-card

Once I had cleared the phones memory of previous parings:

[CHG] Device 2C:41:A1:1D:D4:E1 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 2C:41:A1:1D:D4:E1 UUIDs: 00001131-0000-1000-8000-00805f9b34fb
[CHG] Device 2C:41:A1:1D:D4:E1 RSSI: -59
[CHG] Device 2C:41:A1:1D:D4:E1 RSSI: -42
[CHG] Device 2C:41:A1:1D:D4:E1 Connected: yes
[CHG] Device 2C:41:A1:1D:D4:E1 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device 2C:41:A1:1D:D4:E1 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 2C:41:A1:1D:D4:E1 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 2C:41:A1:1D:D4:E1 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 2C:41:A1:1D:D4:E1 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 2C:41:A1:1D:D4:E1 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 2C:41:A1:1D:D4:E1 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 2C:41:A1:1D:D4:E1 ServicesResolved: yes
[CHG] Device 2C:41:A1:1D:D4:E1 Paired: yes
[CHG] Device 2C:41:A1:1D:D4:E1 Trusted: yes
[CHG] Device 2C:41:A1:1D:D4:E1 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device 2C:41:A1:1D:D4:E1 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
3 Likes
5

This is the sort of thread I like to see. :grin:

4 Likes
6

Yes indeed. Very nicely done.

2 Likes
7

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.