Arch Linux

angelo

Member

Registered: 2015-12-28

Posts: 38

[SOLVED] bluetooth: failures to connect and to pair

I'm having trouble getting a bluetooth headset working. The strangest thing is, every day seems to be worse than before.

Yesterday, after tinkering for a while with bluetoothctl, I managed to connect and use the headset for a brief time. Earlier today I was still paired to the headset, but could not connect, with error "Failed to connect: org.bluez.Error.Failed"

I tried resetting pairings from the headset. Now both my phone and laptop find the device, and the phone has no problem pairing or connecting, but the laptop will not even pair, with error "Failed to pair: org.bluez.Error.ConnectionAttemptFailed".

[bluetooth]# show 30:52:CB:81:11:52 
Controller 30:52:CB:81:11:52
	Name: private
	Alias: private
	Class: 0x1c010c
	Powered: yes
	Discoverable: no
	Pairable: no
	UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
	UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
	UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d052E
	Discovering: no
[bluetooth]#  devices
Device 00:14:BE:8F:C8:09 BHS-750
[bluetooth]# info 00:14:BE:8F:C8:09 
Device 00:14:BE:8F:C8:09
	Name: BHS-750
	Alias: BHS-750
	Class: 0x240404
	Icon: audio-card
	Paired: no
	Trusted: yes
	Blocked: no
	Connected: no
	LegacyPairing: no
[bluetooth]# pair 00:14:BE:8F:C8:09 
Attempting to pair with 00:14:BE:8F:C8:09
Failed to pair: org.bluez.Error.ConnectionAttemptFailed

Throughout, the failures to pair/connect do not add anything to journalctl. Restarting bluetooth (and even rebooting) did not help.

This is XPS13(9350); It seems a similar model (but with a different Broadcom chip) requires some drives, but the fact that the headset connected yesterday seems to this out as the issue. See https://forums.linuxmint.com/viewtopic.php?t=228805

Any pointers will be appreciated.

EDIT (perhaps solved):
After installing bcm4350-firmware and rebooting I can connect and use the headset. I do not know how it worked yesterday without the firmware, or whether it will work tomorrow. I am not satisfied, since I do not really understand what was the issue and why it works now, so am not confident that it will keep working. Hopefully this stays solved.

EDIT: After suspending and resuming, I again cannot connect. (Still paired, though.) Could it have been the clean reboot that allowed it to work earlier? I'll keep experimenting another day.

Last edited by angelo (2017-08-23 22:44:55)

Docbroke

Member

From: India

Registered: 2015-06-13

Posts: 1,433

Re: [SOLVED] bluetooth: failures to connect and to pair

If you have connected your headset with your phone before trying to connect with laptop, try removing the device from bluetoothctl, followed by search, trust, pair, connect. Atleast I had this connection problem whenever I connect my bluetooth with some other device.

---

Arch is home!
https://github.com/Docbroke

angelo

Member

Registered: 2015-12-28

Posts: 38

Re: [SOLVED] bluetooth: failures to connect and to pair

Thanks, Docbroke.

Indeed, re-pairing seems to work, and I was able to reconnect today also after resume from suspend. I mark this as solved, though I'm not really sure what is going on, or what to do if the problem returns.