Re: cannot connect to a bluetooth speaker

[Federico Bruni]

Il giorno gio 22 mar 2018 alle 22:32, Federico Bruni 
 ha scritto:



Il giorno gio 22 mar 2018 alle 9:26, Federico Bruni 
 ha scritto:



Il giorno gio 22 mar 2018 alle 8:21, Federico Bruni 
 ha scritto:

Let me add that I've tried also bluetoothctl.
I can pair it but after a few seconds it's disconnected:

[bluetooth]# trust AC:89:95:DA:52:5E
Changing AC:89:95:DA:52:5E trust succeeded
[bluetooth]# pair AC:89:95:DA:52:5E
Attempting to pair with AC:89:95:DA:52:5E
[CHG] Device AC:89:95:DA:52:5E Connected: yes

Failed to pair: org.bluez.Error.AuthenticationCanceled
[CHG] Device AC:89:95:DA:52:5E Connected: no




I've now searched this error and found a possible solution here:
https://bbs.archlinux.org/viewtopic.php?id=180165

It says that installing bluez-hid2hci would solve the problem.
It was not installed on my system, so I'll give it a try when I'm 
back home.




I'm doing some progress. Now the bluetooth connection is kept and the 
speaker appears in the Sound settings (see attached screenshot).


But the speaker is mute. It might be some audio library missing or 
what?
I tried `dnf search a2dp` and found only package sbc, which is 
already installed.

Some problem with PulseAudio?




I disabled pulseaudio respawning and added verbosity (pulseaudio 
-vv)

and I got this interesting information:

I: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo idle for too long, 
suspending ...


which brought me to the solution suggested here:
https://askubuntu.com/questions/218444/sound-output-starts-delayed

i.e. commenting load-module module-suspend-on-idle in 
/etc/pulse/default.pa


Now I can play music on that speaker. Success :-)

Sorry for this "solo thread", but I hope it can be helpful for others.

Best
Federico




___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: cannot connect to a bluetooth speaker

[Federico Bruni]

Il giorno gio 22 mar 2018 alle 8:21, Federico Bruni 
 ha scritto:

Let me add that I've tried also bluetoothctl.
I can pair it but after a few seconds it's disconnected:

[bluetooth]# trust AC:89:95:DA:52:5E
Changing AC:89:95:DA:52:5E trust succeeded
[bluetooth]# pair AC:89:95:DA:52:5E
Attempting to pair with AC:89:95:DA:52:5E
[CHG] Device AC:89:95:DA:52:5E Connected: yes

Failed to pair: org.bluez.Error.AuthenticationCanceled
[CHG] Device AC:89:95:DA:52:5E Connected: no




I've now searched this error and found a possible solution here:
https://bbs.archlinux.org/viewtopic.php?id=180165

It says that installing bluez-hid2hci would solve the problem.
It was not installed on my system, so I'll give it a try when I'm back 
home.



___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: cannot connect to a bluetooth speaker

[Federico Bruni]

Let me add that I've tried also bluetoothctl.
I can pair it but after a few seconds it's disconnected:

[bluetooth]# trust AC:89:95:DA:52:5E
Changing AC:89:95:DA:52:5E trust succeeded
[bluetooth]# pair AC:89:95:DA:52:5E
Attempting to pair with AC:89:95:DA:52:5E
[CHG] Device AC:89:95:DA:52:5E Connected: yes

Failed to pair: org.bluez.Error.AuthenticationCanceled
[CHG] Device AC:89:95:DA:52:5E Connected: no



___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

cannot connect to a bluetooth speaker

[Federico Bruni]

Hi all

I've tried posting this message via the web interface yesterday, but I 
don't see it in the archives. So I'm sending it again by regular email.


I have two speakers:

$ hcitool scan
Scanning ...
AC:89:95:DA:52:5E   Beoplay M5_27502524
00:12:6F:3F:BD:D5   Mu-so Qb BT 7047

I can connect via bluetooth to both using my Android phone.
I can connect via bluetooth only to Mu-so using Fedora 27.

If I try the bluetooth connection using GNOME setting, I don't get much 
information. I just see that it tries the connection and after a while 
it fails.

On a terminal I get a timeout:

$ bt-device -c AC:89:95:DA:52:5E
Connecting to: AC:89:95:DA:52:5E
Error: Timeout was reached

Finally, journalctl seems to suggest that may be some kernel problem?!?

Mar 22 07:36:45 fedora kernel: Bluetooth: hci0: last event is not cmd 
complete (0x0f)


I found the same error message in this bug report, which is for Fedora 
28 though:

https://bugzilla.redhat.com/show_bug.cgi?id=1514836#c15

Thanks in advance for any suggestion
Federico


PS The bluetooth service is running fine:

$ systemctl status bluetooth
* bluetooth.service - Bluetooth service
  Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; 
vendor preset: enabled)

  Active: active (running) since Thu 2018-03-22 07:25:05 CET; 26min ago
Docs: man:bluetoothd(8)
Main PID: 759 (bluetoothd)
  Status: "Running"
   Tasks: 1 (limit: 4915)
  CGroup: /system.slice/bluetooth.service
  `-759 /usr/libexec/bluetooth/bluetoothd

Mar 22 07:25:05 fedora systemd[1]: Starting Bluetooth service...
Mar 22 07:25:05 fedora bluetoothd[759]: Bluetooth daemon 5.48
Mar 22 07:25:05 fedora bluetoothd[759]: Starting SDP server
Mar 22 07:25:05 fedora systemd[1]: Started Bluetooth service.
Mar 22 07:25:05 fedora bluetoothd[759]: Bluetooth management interface 
1.14 initialized
Mar 22 07:25:19 fedora bluetoothd[759]: Endpoint registered: 
sender=:1.69 path=/MediaEndpoint/A2DPSource
Mar 22 07:25:19 fedora bluetoothd[759]: Endpoint registered: 
sender=:1.69 path=/MediaEndpoint/A2DPSink

Mar 22 07:42:45 fedora bluetoothd[759]: No cache for AC:89:95:DA:52:5E


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org