You are not logged in.

#1 2017-02-03 19:04:04

daniel7558
Member
Registered: 2017-01-26
Posts: 3

Bluetooth Speaker not recognized in pulseaudio

Hi there,
I managed to connect my Amazon Echo as a bluetooth speaker to my computer after some inital problems.
I had the problem where I got the error "Failed to connect: org.bluez.Error.Failed" within bluetoothctl and solved it by running

pactl load-module module-bluetooth-discover

as described in https://wiki.archlinux.org/index.php/Bluetooth_headset

After that I was able to connect to my bluetooth speaker and use it as an output device within the audio settings of Gnome.
But once I rebooted I could no longer select the speaker in the settings (although I'm still able to connect to it properly).
loading the "module-bluetooth-discover"-module again results in an "module initialization failed".

systemctl status bluetooth

gives me

[daniel@homepc ~]$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2017-02-03 19:25:48 CET; 14min ago
     Docs: man:bluetoothd(8)
 Main PID: 441 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─441 /usr/lib/bluetooth/bluetoothd

Feb 03 19:25:48 homepc bluetoothd[441]: Failed to obtain handles for "Service Changed" characteristic
Feb 03 19:25:48 homepc bluetoothd[441]: Sap driver initialization failed.
Feb 03 19:25:48 homepc bluetoothd[441]: sap-server: Operation not permitted (1)
Feb 03 19:26:00 homepc bluetoothd[441]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource
Feb 03 19:26:00 homepc bluetoothd[441]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink
Feb 03 19:26:16 homepc bluetoothd[441]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource
Feb 03 19:26:16 homepc bluetoothd[441]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSink
Feb 03 19:26:16 homepc bluetoothd[441]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
Feb 03 19:26:45 homepc bluetoothd[441]: a2dp-source profile connect failed for 34:D2:70:XX:XX:XX: Device or resource busy
Feb 03 19:26:48 homepc bluetoothd[441]: /org/bluez/hci0/dev_34_D2_70_XX_XX_XX/fd0: fd(33) ready

Any ideas on how to solve this and get it working again?

Best regards,
Daniel

Offline

#2 2017-04-03 17:45:03

crashandburn4
Member
Registered: 2013-03-03
Posts: 105

Re: Bluetooth Speaker not recognized in pulseaudio

Hi daniel7558 I think I've hit the same issue that you have here. (also with an amazon echo). I have a similar question here: https://bbs.archlinux.org/viewtopic.php?id=224261

It seems that some ubuntu users have been stung by the same problem:

https://askubuntu.com/questions/871630/ … oth/888117

Did you manage to figure out a fix for your issue?

Offline

Board footer

Powered by FluxBB