Unable to connect with bluetooth

HuckleSmothered · 2013-09-25 21:09:21

I am unable to connect to a wireless speaker I have.

HDMX Jam Wireless Speaker. Relatively new. Works with my Android phone over bluetooth no problem.

Here's what's happening (same thing when using sudo bluetoothctl -a):

 ** (~) $ bluetoothctl -a
[NEW] Controller 00:15:AF:FA:05:63 eeepc [default]
[NEW] Device 46:8F:E8:07:EB:15 HMDX JAM
Agent registered
[bluetooth]# info 46:8F:E8:07:EB:15
Device 46:8F:E8:07:EB:15
	Name: HMDX JAM
	Alias: HMDX JAM
	Class: 0x240414
	Icon: audio-card
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: no
	LegacyPairing: no
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
[bluetooth]# show 00:15:AF:FA:05:63
Controller 00:15:AF:FA:05:63
	Name: eeepc
	Alias: eeepc
	Class: 0x00010c
	Powered: yes
	Discoverable: no
	Pairable: yes
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0509
	Discovering: no
[bluetooth]# connect 46:8F:E8:07:EB:15
Attempting to connect to 46:8F:E8:07:EB:15
[CHG] Device 46:8F:E8:07:EB:15 Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 46:8F:E8:07:EB:15 Connected: no

I've been unable to find any info online about this error that is relevant to Bluez5 (I'm on Bluez5.9).

Any advice?

spychodelics · 2013-09-25 22:26:16

Ive got a similar problem using a Bluetooth USB Stick and trying to connect my Headset to it.

extra/bluez 5.9-1
extra/bluez-libs 5.9-1
extra/bluez-utils 5.9-1

bluetoothctl 
[NEW] Controller 00:11:B1:07:A3:38 archlinux64 [default]
[NEW] Device 00:1D:43:A0:A2:C7 MC00
[CHG] Controller 00:11:B1:07:A3:38 Discoverable: no
[bluetooth]# pairable on
Changing pairable on succeeded[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent 
Default agent request successfuldiscoverable yes
Changing discoverable on succeeded
[CHG] Controller 00:11:B1:07:A3:38 Discoverable: yes
[bluetooth]# scan on
Discovery started
[bluetooth]# info 00:1D:43:A0:A2:C7
Device 00:1D:43:A0:A2:C7
	Name: MC00
	Alias: MC00
	Class: 0x240404
	Icon: audio-card
	Paired: no
	Trusted: no
	Blocked: no
	Connected: no
	LegacyPairing: yes
	UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree
[bluetooth]# pair 00:1D:43:A0:A2:C7
Attempting to pair with 00:1D:43:A0:A2:C7
Pairing successful
[CHG] Device 00:1D:43:A0:A2:C7 Paired: yes
[CHG] Device 00:1D:43:A0:A2:C7 Connected: yes
[CHG] Device 00:1D:43:A0:A2:C7 Paired: no
[CHG] Device 00:1D:43:A0:A2:C7 Connected: no
[CHG] Device 00:1D:43:A0:A2:C7 RSSI: -48
[CHG] Device 00:1D:43:A0:A2:C7 RSSI: -62
[CHG] Device 00:1D:43:A0:A2:C7 RSSI: -54
[CHG] Device 00:1D:43:A0:A2:C7 RSSI: -73
[CHG] Device 00:1D:43:A0:A2:C7 RSSI: -64
[CHG] Device 00:1D:43:A0:A2:C7 RSSI: -54
[bluetooth]# connect 00:1D:43:A0:A2:C7
Attempting to connect to 00:1D:43:A0:A2:C7
[CHG] Device 00:1D:43:A0:A2:C7 Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 00:1D:43:A0:A2:C7 UUIDs has unsupported type
Authorize service
[agent] Authorize service 0000110c-0000-1000-8000-00805f9b34fb (yes/no): yes
[CHG] Device 00:1D:43:A0:A2:C7 Connected: no
[CHG] Controller 00:11:B1:07:A3:38 Discoverable: no

Maybe someone can point out, where our problem is.

HuckleSmothered · 2013-09-25 22:39:59

I'm noticing that yours never asked for a passcode. When I was first attempting to connect, it did not ask me either. I had to start bluetoothctl with the "a" switch.

bluetoothctl -a

Then it asked me the passcode to which I eventually got paired. Still couldn't get connected, but I got paired that way.

At least that's how I recall it happening. The last time I messed with bluetooth was a few weeks ago. I think trusting the device skips the passcode, or saves it, or something. I am not asked anymore even when using bluetoothctl -a.

Anyway, that's my only thought on your situation. Considering that we're in the same boat in failing to connect, take my suggestion with the appropriate credibility attached (aka minimal).

worryag · 2013-10-08 17:30:45

PulseAudio doesn't yet support BlueZ 5 (except the branch in git)

RobertBuhren · 2013-10-08 21:10:03

pulseaudio 4.0.3 from testing also supports bluez 5. So either just wait for it to enter Extra or install pulseaudio from testing

See: https://projects.archlinux.org/svntogit … 013d185729

stronnag · 2013-10-19 20:22:25

pulseaudio and bluez from testing is still a regression from the equivalent capability shipped with gnome 3.8. With 3.8 / bluez4, I could just switch on the BT audio device, and the sound would transfer automagically. Now, I switch the BT adapter on, then I have to go to 'user' menu thing in the shell, select settings, select bluetooth, select the BT audio device and then click 'Connect' to manually connect the device. 0 clicks in 3.8, 5 clicks in 3.10; no doubt yet another gnome 'usability' 'improvement' ....

HuckleSmothered · 2013-10-23 19:25:38

I had pulseaudio when I was trying to connect. I removed pulseaudio completely. Tried to connect to the bluetooth speaker again and it failed, same error.

Another search a bit ago took me to a site that implied linux does not support bluetooth through audio. It will do file transfer, but not audio. Maybe it's just XFCE though, because it seems others have gotten it to work. Maybe that's an assumption. Anyone using a bluetooth speaker? If so, on XFCE?

Oh, and I've now tried blueman, bluez4, and bluez5. And strictly using the hcitool commands. No love.

felixonmars · 2013-11-06 06:04:23

I got the very same problem. Downgraded bluedevil, libbluedevil and installed bluez4, still using latest pulseaudio, and it works correctly. Hope this helps someone.

vially · 2013-11-11 23:52:21

I've had the exact same problem and I managed to solve it by removing the device from bluetoothctl followed by a repairing and a reconnect.

These were the bluetoothctl commands:

remove <MAC ADDRESS>
pair <MAC ADDRESS>
connect <MAC ADDRESS>

I'm using of pulseaudio-4.0 and bluez-5.10

netskink · 2013-12-06 03:28:09

I'm working on a update for bluez5 and pulseaudio writeup on the wiki now. I finally got it working.

BasT · 2013-12-12 13:03:32

vially wrote:

I've had the exact same problem and I managed to solve it by removing the device from bluetoothctl followed by a repairing and a reconnect.
These were the bluetoothctl commands:
remove <MAC ADDRESS>
pair <MAC ADDRESS>
connect <MAC ADDRESS>
I'm using of pulseaudio-4.0 and bluez-5.10

I've been having the same problem since bluez5.
I tried connecting with your bluetoothctl commands, but got this:

[bluetooth]# connect 00:1B:66:02:37:72
Attempting to connect to 00:1B:66:02:37:72
[CHG] Device 00:1B:66:02:37:72 Connected: yes
Connection successful
[CHG] Device 00:1B:66:02:37:72 UUIDs has unsupported type

Any ideas?

BasT · 2013-12-20 22:01:29

Latest bluedevil update fixed it for me (2.0.git1381.f02fd99-1).

vially · 2014-01-03 17:07:20

BasT wrote:

I've been having the same problem since bluez5.
I tried connecting with your bluetoothctl commands, but got this:
[bluetooth]# connect 00:1B:66:02:37:72
Attempting to connect to 00:1B:66:02:37:72
[CHG] Device 00:1B:66:02:37:72 Connected: yes
Connection successful
[CHG] Device 00:1B:66:02:37:72 UUIDs has unsupported type
Any ideas?

I get the exact same output (Device UUIDs has unsupported type) but the headphones work nevertheless.

fahq613 · 2015-05-26 18:36:33

BasT wrote:

Latest bluedevil update fixed it for me (2.0.git1381.f02fd99-1).

I can confirm that installing bluedevil-git from aur resolved the problem for me as well

WorMzy · 2015-05-26 21:35:14

Hi fahq613, welcome to the Arch Linux forums. Please take a moment to read through the forum etiquette, particularly the section regarding necrobumping.

https://wiki.archlinux.org/index.php/Fo … bumping.22

Closing.

Arch Linux

#1 2013-09-25 21:09:21

Unable to connect with bluetooth

#2 2013-09-25 22:26:16

Re: Unable to connect with bluetooth

#3 2013-09-25 22:39:59

Re: Unable to connect with bluetooth

#4 2013-10-08 17:30:45

Re: Unable to connect with bluetooth

#5 2013-10-08 21:10:03

Re: Unable to connect with bluetooth

#6 2013-10-19 20:22:25

Re: Unable to connect with bluetooth

#7 2013-10-23 19:25:38

Re: Unable to connect with bluetooth

#8 2013-11-06 06:04:23

Re: Unable to connect with bluetooth

#9 2013-11-11 23:52:21

Re: Unable to connect with bluetooth

#10 2013-12-06 03:28:09

Re: Unable to connect with bluetooth

#11 2013-12-12 13:03:32

Re: Unable to connect with bluetooth

#12 2013-12-20 22:01:29

Re: Unable to connect with bluetooth

#13 2014-01-03 17:07:20

Re: Unable to connect with bluetooth

#14 2015-05-26 18:36:33

Re: Unable to connect with bluetooth

#15 2015-05-26 21:35:14

Re: Unable to connect with bluetooth

Board footer