Did the update and renamed .asoundrc.
After connecting the buds, I can chose Bluetooth audio from the Audio setting, but still no sound.
Moved here so we don’t spam the wiki post.
Story so far: you are running the November 2021 update and can get your enacfire headset to work but not the Galaxy buds.
Can you get sound through the buds using aplay?
Have we discussed SSH yet? If not read this
Accessing the command line - General - OSMC
Then from the command line type:
sudo apt-get update
sudo apt-get install alsa-utils
Now post here the output of
aplay -L
and see if you get sound by typing (after the buds are connected)
speaker-test -D btaudio -c 2 -p 1 -t wav -l 3
Here is the output of aplay -L:
Discard all samples (playback) or generate zero samples (capture)
btaudio
Bluetooth Audio
default:CARD=sndrpihifiberry
snd_rpi_hifiberry_digi, HifiBerry Digi HiFi wm8804-spdif-0
Default Audio Device
sysdefault:CARD=sndrpihifiberry
snd_rpi_hifiberry_digi, HifiBerry Digi HiFi wm8804-spdif-0
Default Audio Device
iec958:CARD=sndrpihifiberry,DEV=0
snd_rpi_hifiberry_digi, HifiBerry Digi HiFi wm8804-spdif-0
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=sndrpihifiberry,DEV=0
snd_rpi_hifiberry_digi, HifiBerry Digi HiFi wm8804-spdif-0
Direct sample mixing device
dsnoop:CARD=sndrpihifiberry,DEV=0
snd_rpi_hifiberry_digi, HifiBerry Digi HiFi wm8804-spdif-0
Direct sample snooping device
hw:CARD=sndrpihifiberry,DEV=0
snd_rpi_hifiberry_digi, HifiBerry Digi HiFi wm8804-spdif-0
Direct hardware device without any conversions
plughw:CARD=sndrpihifiberry,DEV=0
snd_rpi_hifiberry_digi, HifiBerry Digi HiFi wm8804-spdif-0
Hardware device with all software conversions
default:CARD=vc4hdmi
vc4-hdmi, MAI PCM i2s-hifi-0
Default Audio Device
sysdefault:CARD=vc4hdmi
vc4-hdmi, MAI PCM i2s-hifi-0
Default Audio Device
hdmi:CARD=vc4hdmi,DEV=0
vc4-hdmi, MAI PCM i2s-hifi-0
HDMI Audio Output
dmix:CARD=vc4hdmi,DEV=0
vc4-hdmi, MAI PCM i2s-hifi-0
Direct sample mixing device
dsnoop:CARD=vc4hdmi,DEV=0
vc4-hdmi, MAI PCM i2s-hifi-0
Direct sample snooping device
hw:CARD=vc4hdmi,DEV=0
vc4-hdmi, MAI PCM i2s-hifi-0
Direct hardware device without any conversions
plughw:CARD=vc4hdmi,DEV=0
vc4-hdmi, MAI PCM i2s-hifi-0
Hardware device with all software conversions
I’m not getting any sound after speaker-test -D btaudio -c 2 -p 1 -t wav -l 3:
speaker-test 1.1.8
Playback device is btaudio
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 960 to 4194304
Period size range from 480 to 4096
Requested period time 1 us
Periods = 4
Unable to set hw params for playback: Device or resource busy
Setting of hwparams failed: Device or resource busy
I’ve tried to do the same test with enacfire and it fails with the same message, but the audio still works fine.
You haven’t got Kodi outputting to BT, right?
BTW I’m not clear on what the -p parameter does, but my BT speaker doesn’t work without it. You could try another value eg -p 10 or 100
My bad, Kodi output was to BT.
After changing it to HDMI, buds are still not working with the same message even with diffrent values for parameter p.
On the other hand, enacfire is working well:
speaker-test 1.1.8
Playback device is btaudio
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 960 to 4565228
Period size range from 480 to 4459
Requested period time 1 us
Periods = 4
was set period_size = 480
was set buffer_size = 1920
0 - Front Left
1 - Front Right
Time per period = 2.981870
0 - Front Left
1 - Front Right
Time per period = 3.009861
0 - Front Left
1 - Front Right
Time per period = 3.009899
What’s the output when speaker-testing Galaxies?
Same as before:
speaker-test 1.1.8
Playback device is btaudio
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 960 to 4194304
Period size range from 480 to 4096
Requested period time 1 us
Periods = 4
Unable to set hw params for playback: Device or resource busy
Setting of hwparams failed: Device or resource busy
I think I’ve got it. Can you confirm the output of
bluetoothctl
info 64:03:7F:56:E6:ED
osmc@osmc:~$ bluetoothctl
[NEW] Controller B8:27:EB:A8:15:31 osmc [default]
[NEW] Device 00:00:90:B0:EF:77 ENACFIRE Future
[NEW] Device 64:03:7F:56:E6:ED Galaxy Buds+ (E6ED)
[Galaxy Buds+ (E6ED)]# info 64:03:7F:56:E6:ED
Device 64:03:7F:56:E6:ED
Name: Galaxy Buds+ (E6ED)
Alias: Galaxy Buds+ (E6ED)
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (a23d00bc-217c-123b-9c00-fc44577136ee)
UUID: Vendor specific (b4a9d6a0-b2e3-4e40-976d-a69f167ea895)
UUID: Vendor specific (e7ab2241-ca64-4a69-ac02-05f5c6fe2d62)
UUID: Vendor specific (f8620674-a1ed-41ab-a8b9-de9ad655729d)
Modalias: bluetooth:v0075pA012d0001
1 Like
Dammit. When you posted before it was not showing (0000110d- …) so I thought it was only a hands-free. But no 
Let’s try this. Make a .asoundrc like this:
pcm.galaxybuds {
type plug
slave.pcm {
type bluealsa
device "64:03:7F:56:E6:ED"
profile "a2dp"
}
hint { show on description "Galaxy Buds+"}
}
Get rid of the automatic conf file:
sudo rm /etc/alsa/conf.d/21-bt-audio-osmc.conf
sudo alsactl nrestore
Now try speaker-test with -D galaxybuds.
It’s really strange. While following your instructions today, I’ve managed at some point to hear the sound of going thought the options and thought that it finally worked, but it was gone as soon as I tried to play a movie.
Never got it again no matter how many times I’ve tried to connect and disconnect the buds.
Edited the post above. Please try that.
osmc@osmc:/etc/alsa/conf.d$ sudo rm 21-bt-audio-osmc.conf
osmc@osmc:/etc/alsa/conf.d$ sudo alsactl nrestore
osmc@osmc:/etc/alsa/conf.d$ ls
20-bluealsa.conf
osmc@osmc:/etc/alsa/conf.d$ speaker-test -D btaudio -c 2 -p 1 -t wav -l 3
speaker-test 1.1.8
Playback device is btaudio
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
ALSA lib pcm.c:2565:(snd_pcm_open_noupdate) Unknown PCM btaudio
Playback open error: -2,No such file or directory
Should I restart the pi after the changes?
should be speaker-test -D galaxybuds -c 2 -p 1 -t wav -l 3
osmc@osmc:/etc/alsa/conf.d$ speaker-test -D galaxybuds -c 2 -p 1 -t wav -l 3
speaker-test 1.1.8
Playback device is galaxybuds
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 960 to 4194304
Period size range from 480 to 4096
Requested period time 1 us
Periods = 4
Unable to set hw params for playback: Device or resource busy
Setting of hwparams failed: Device or resource busy
Right let’s raise an issue with the bluez-alsa guys. Do you have a github login?
Yes I do.
If you give me the link to the project and tell me what is the relevant data to provide, I can raise an issue.
Tell them your headset worked so we think BA is set up OK. Tell them the bluetoothctl info, your .asoundrc and output from speaker-test. And you are on RPi, right?