Is connecting remote and headphones via Bluetooth possible?

fzinken · 1 August 2020 08:46

Whats the output of dpkg -l | grep -i pulse?

Harbour · 1 August 2020 08:48

Got this:

osmc@Vero4K:~$ dpkg -l | grep -i pulse
ii libpulse0:armhf 10.0-1+deb9u1 armhf PulseAudio client libraries
ii libpulsedsp:armhf 10.0-1+deb9u1 armhf PulseAudio OSS pre-load library
ii pulseaudio 10.0-1+deb9u1 armhf PulseAudio sound server
ii pulseaudio-module-bluetooth 10.0-1+deb9u1 armhf Bluetooth module for PulseAudio sound server
ii pulseaudio-module-zeroconf 10.0-1+deb9u1 armhf Zeroconf module for PulseAudio sound server
ii pulseaudio-utils 10.0-1+deb9u1 armhf Command line tools for the PulseAudio sound server

fzinken · 1 August 2020 08:52

Ok, not really sure what is going on. If you want and have a few more minutes to spend we could try to move you to bluez solution that we are in the progress to switch to in the future.

Harbour · 1 August 2020 09:07

I wonder, if re-installing a2dp would fix my issue? I believe that I’ve seen pulseaudio a couple of years ago when I was trying to [unsuccessfully] pair my old Beoplay H9 with Vero4K.

However, if you believe that all attempts have been exhausted, and the new solution does not spoil what is already here, then I am happy to try.

fzinken · 1 August 2020 09:13

Let’s go for it we always can go back.

sudo apt-get remove --purge a2dp-app-osmc
sudo apt-get remove --purge pulseaudio
sudo apt-get install wget libbluetooth3 libsbc1 libfdk-aac1
wget https://collab.osmc.tv/s/hxG3JX4m3rY2XiM/download -O armv7-bluez-alsa-osmc.deb
sudo dpkg -i armv7-bluez-alsa-osmc.deb

Then need to create config file via sudo nano .asoundrc with this contents

# This file describes the bluetooth sinks available for Kodi to play to
# add lines like the following for each BT device (speaker or headphones)

pcm.beoplayh9 {
        type bluealsa
        device "00:09:A7:46:D8:52"
        profile "a2dp"
        hint {show on description "BeoplayH9"}
}

# using the MAC of the device (see bluetoothctl) instead of 12:34:56:78:9A:BC
# Use any letters or numbers for the description which will show up in Settings-System-Audio

After that reboot and then you should have an entry “BeoplayH9” in your settings - system - audio

Harbour · 1 August 2020 09:19

Thanks @fzinken. I’ll follow these steps after dinner. It’s already late in the down under

Harbour · 1 August 2020 13:40

I have followed all the steps above, had no error messages. Created .asoundrc as described. Rebooted.

Unfortunately, I still have the old 4 options in ‘Audio output device’ in settings, i.e. no pulseaudio or “BeoplayH9”.

Interestingly, upon reboot Beoplay H9 did not connect. I had to connect headphones manually via command line. Is it expected?

fzinken · 1 August 2020 13:46

Can you post paste-log .asoundrc

It should automatically connect, but could you connected it and then check power - exit in Kodi and check again

Harbour · 1 August 2020 13:48

Done!
https://paste.osmc.tv/ubicokenok

fzinken · 1 August 2020 13:56

That looks all good.
So still no new entry after exit?

Maybe just upload full logs for us to see what’s happening.

grab-logs -A

Harbour · 1 August 2020 14:07

Done!
https://paste.osmc.tv/irecuparun

fzinken · 1 August 2020 14:12

Looks all good but no trace of the Beoplay. Maybe @grahamh has some ideas what to check on bluez.

grahamh · 1 August 2020 15:15

Yes. Vero doesn’t (can’t/shoudn’t) search around for BT devices to connect to. If you turn off the speaker and turn it on again and the speaker is trusted by vero it should connect.

Please turn on debug logging in Settings, restart Kodi (Power->Exit) and post the logs again.

Harbour · 2 August 2020 03:18

Good morning! Thank you @grahamh, all done as requested:

https://paste.osmc.tv/hilegudimi

grahamh · 2 August 2020 08:35

Thanks. Can you confirm the Beoplay is successfully connected and post aplay -l and aplay -L.

Harbour · 2 August 2020 12:47

Switching on Beoplay H9 does not initiate connection unfortunatley.

So far, the only way to connect headphones is from the command line: bluetoothctl → connect 00:09:A7:46:D8:52

This command returns:

osmc@Vero4K:~$ aplay -l
-bash: aplay: command not found

Am I doing something wrong?

grahamh · 2 August 2020 13:32

sudo apt-get update
sudo apt-get install alsa-utils

Can you check the headphones aren’t already connected to a different device?

Harbour · 3 August 2020 03:09

100% positive! The only other paired device is Galaxy S10 which shows no connection. Gave it another go: turned off Bluetooth on Galaxy S10 and switched on Beoplay. Headphones did not connect to Vero4K (checked in ‘info 00:09:A7:46:D8:52’).

bluetoothctl → connect 00:09:A7:46:D8:52 - works w/o issues, connects instantly.

Harbour · 3 August 2020 03:12

After this update aplay worked!

osmc@Vero4K:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: AMLM8AUDIO [AML-M8AUDIO], device 0: I2S.39 T9015-audio-hifi-0
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: AMLM8AUDIO [AML-M8AUDIO], device 1: SPDIF.40 dit-hifi-1
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: AMLM8AUDIO [AML-M8AUDIO], device 2: PCM.41 pcm2bt-pcm-2
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: U20 [USB Audio 2.0], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0

Harbour · 3 August 2020 03:13

osmc@Vero4K:~$ aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
beoplayh9
BeoplayH9
default:CARD=AMLM8AUDIO
AML-M8AUDIO,
Default Audio Device
sysdefault:CARD=AMLM8AUDIO
AML-M8AUDIO,
Default Audio Device
hdmi:CARD=AMLM8AUDIO,DEV=0
AML-M8AUDIO,
HDMI Audio Output
dmix:CARD=AMLM8AUDIO,DEV=0
AML-M8AUDIO,
Direct sample mixing device
dmix:CARD=AMLM8AUDIO,DEV=1
AML-M8AUDIO,
Direct sample mixing device
dmix:CARD=AMLM8AUDIO,DEV=2
AML-M8AUDIO,
Direct sample mixing device
dsnoop:CARD=AMLM8AUDIO,DEV=0
AML-M8AUDIO,
Direct sample snooping device
dsnoop:CARD=AMLM8AUDIO,DEV=1
AML-M8AUDIO,
Direct sample snooping device
dsnoop:CARD=AMLM8AUDIO,DEV=2
AML-M8AUDIO,
Direct sample snooping device
hw:CARD=AMLM8AUDIO,DEV=0
AML-M8AUDIO,
Direct hardware device without any conversions
hw:CARD=AMLM8AUDIO,DEV=1
AML-M8AUDIO,
Direct hardware device without any conversions
hw:CARD=AMLM8AUDIO,DEV=2
AML-M8AUDIO,
Direct hardware device without any conversions
plughw:CARD=AMLM8AUDIO,DEV=0
AML-M8AUDIO,
Hardware device with all software conversions
plughw:CARD=AMLM8AUDIO,DEV=1
AML-M8AUDIO,
Hardware device with all software conversions
plughw:CARD=AMLM8AUDIO,DEV=2
AML-M8AUDIO,
Hardware device with all software conversions
default:CARD=U20
USB Audio 2.0, USB Audio
Default Audio Device
sysdefault:CARD=U20
USB Audio 2.0, USB Audio
Default Audio Device
front:CARD=U20,DEV=0
USB Audio 2.0, USB Audio
Front speakers
surround21:CARD=U20,DEV=0
USB Audio 2.0, USB Audio
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=U20,DEV=0
USB Audio 2.0, USB Audio
4.0 Surround output to Front and Rear speakers
surround41:CARD=U20,DEV=0
USB Audio 2.0, USB Audio
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=U20,DEV=0
USB Audio 2.0, USB Audio
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=U20,DEV=0
USB Audio 2.0, USB Audio
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=U20,DEV=0
USB Audio 2.0, USB Audio
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=U20,DEV=0
USB Audio 2.0, USB Audio
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=U20,DEV=0
USB Audio 2.0, USB Audio
Direct sample mixing device
dsnoop:CARD=U20,DEV=0
USB Audio 2.0, USB Audio
Direct sample snooping device
hw:CARD=U20,DEV=0
USB Audio 2.0, USB Audio
Direct hardware device without any conversions
plughw:CARD=U20,DEV=0
USB Audio 2.0, USB Audio
Hardware device with all software conversions