my Vero 4K just arrived! I’m trying to configure it in the same way as my ancient laptop is, that means to stream audio through bluetooth. I have read various topics in here, but still no luck.
I have installed the a2dp-app-osmc package.
I have managed pair with the device using bluetoothctl, but unable to connect.
I have started pulseaudio using pulseaudio -D
After that, I have managed to connect to the device using bluetoothctl.
Is there an approximate timeline to get Bluetooth working properly on the vero4k? I appreciate its not an easy fix otherwise you’d have achieved it by now
Does Bluetooth work out of the box on the new raspberry pi 3 b+ ? I could switch to one of those instead
No, the Bluetooth audio issue is not Hardware dependent but just a software audio system issue.
While it also still will have to be seen if the internal Bluetooth of the Pi3B+ is better than the one in the Pi3
Still no luck. I guess my problem si different. I have no “system instance” running on Vero 4K.
osmc@osmc:~$ systemctl status pulseaudio
Unit pulseaudio.service could not be found.
osmc@osmc:~$ systemctl --user status pulseaudio
● pulseaudio.service - Sound Service
Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2018-03-24 13:01:08 CET; 6min ago
Main PID: 2020 (pulseaudio)
CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
└─2020 /usr/bin/pulseaudio --daemonize=no
Mar 24 13:01:08 osmc systemd[1456]: Starting Sound Service...
Mar 24 13:01:08 osmc pulseaudio[2020]: E: [pulseaudio] shm.c: shared memfd open() failed: Function not implemented
Mar 24 13:01:08 osmc pulseaudio[2020]: W: [pulseaudio] core.c: Failed to allocate shared memfd memory pool. Falling back to a normal memory pool.
Mar 24 13:01:08 osmc pulseaudio[2020]: W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunc
Mar 24 13:01:08 osmc pulseaudio[2020]: W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-
Mar 24 13:01:08 osmc systemd[1456]: Started Sound Service.
If I disable autospawn in /etc/pulse/client.conf, pulseaudio output is no longer available in Kodi.
Also If I disable pulseaudio service systemctl --user disable pulseaudio, I can no longer list sinks.
osmc@osmc:~$ systemctl --user stop pulseaudio
Warning: Stopping pulseaudio.service, but it can still be activated by:
pulseaudio.socket
osmc@osmc:~$ pacmd list-sinks
No PulseAudio daemon running, or not running as session daemon.
However with configuration described in my first post of this topic, I can hear sound from my bluetooth speakers using command speaker-test. Apparently Kodi is the problem.
I’m testing on a fresh install of OSMC on a Pi3, which is my sandbox machine, but I’m seeing the pulseaudio service – which is what I’d expect.
Based on some tests I’ve managed to run, the system-wide pulseaudio.service is installed as part of the a2dp-app-osmc package. If it’s not there, it looks like you haven’t yet installed the package you built.
The version of OSMC was the latest but the version of a2dp-app-osmc was taken from git, per this post:
as you seem to be willing to tinker with this a bit, I’d recommend you get to where we were before we made changes to try and get it running out of system mode.
apt-get install git build-essential
git clone https://github.com/osmc/osmc
cd osmc
git checkout 27a9e28b6d7224c540424445b45da87096042030
cd package/a2dp-app-osmc
make
Sam was suggesting that Den4t use the previous version of a2dp-app-osmc , which contains the system instance of pulseaudio.
