Arch Linux

AndyRTR

Developer

From: Magdeburg/Germany

Registered: 2005-10-07

Posts: 1,642

bluez fails to connect to my headset

https://bugs.archlinux.org/task/37236 - I'm running into a similar issue with this Philips headset.

[NEW] Device 00:22:37:0E:97:BF Philips SHB9100WT
[bluetooth]# pair 00:22:37:0E:97:BF
Attempting to pair with 00:22:37:0E:97:BF
[CHG] Device 00:22:37:0E:97:BF Connected: yes
[CHG] Device 00:22:37:0E:97:BF UUIDs has unsupported type
[CHG] Device 00:22:37:0E:97:BF Paired: yes
Pairing successful
[CHG] Device 00:22:37:0E:97:BF Connected: no
[bluetooth]# connect 00:22:37:0E:97:BF
Attempting to connect to 00:22:37:0E:97:BF
[CHG] Device 00:22:37:0E:97:BF Connected: yes
Failed to connect: org.bluez.Error.Failed
Authorize service
[agent] Authorize service 0000110c-0000-1000-8000-00805f9b34fb (yes/no): yes
[CHG] Device 00:22:37:0E:97:BF Connected: no
[bluetooth]# 

Nov 03 22:11:02 laptop64 bluetoothd[724]: Unable to select SEP
Nov 03 22:11:08 laptop64 kernel: input: 00:22:37:0E:97:BF as /devices/virtual/input/input13

This is without pulseaudio. I'm not going to use pulseaudio or any further gnome stuff. The headset has to run with plain bluez/bluez-utils + alsa. Any help is welcome.
I'm running bluez 5.10 stack + either LTS 3.10 or 3.11 kernel without success.

Maybe some additional modprobe and/or bluetooth.conf parameter are needed. How can I get a more verbose output?

PS: hci0 device is always down at boot. Shouldn't the bluetooth.target bring it up automatically without the need to add a custom udev rule?

whatshisname

Member

Registered: 2010-04-24

Posts: 163

Re: bluez fails to connect to my headset

Good luck getting bluez working without pulseaudio and gnome-applet.  I have spent *days* trying to get bluetooth to work by just using bluez-utils and alsa and finally gave up.

Is there anything more frustrating than getting bluetooth working in Linux?

No.  Hands down, bluetooth has given me more trouble than anything I've ever tried to do in Linux.

Having said that, a couple of things that worked for me.  YMMV

I was only successful with an /etc/asound.conf file and not an ~/.asoundrc file.

When trying to get your headset configured, restart your bluetooth daemon often.  Take hci0 down and up often.

Sometimes it helps to just reboot and follow all the steps again in order.  Order seems to matter.

If you find the trigger for getting bluetooth to work without Pulse, I'd sure love to hear about it! :-)