Problem with bluetooth headphones

You didn’t run that as sudo bluetoothctl did you?

What’s the output of
[bluetooth]# info 00:23:01:0A:14:5C

Doing a bit of research, it seems that there is a specific module that pulse uses for handling HFP/HSP connections which bluetoothctl looks for. but we dont really care about that so after you’ve got the output of the info command in bluetoothctl, drop out of that quit, and lets set the pulse audio settings

pactl list sources short

See what comes up, we can go from there.

1 Like

edit: the problem of post deleted was solved restarted raspberry…

now i’m on this point but i don’t know which is the number or device? 1 or 2?

osmc@osmc:~$ pactl list sources short | grep 00_23_01_0A_14_5C
1 bluez_sink.00_23_01_0A_14_5C.headset_head_unit.monitor module-bluez5-device.c s16le ch 1 8000 Hz SUSPENDED
2 bluez_source.00_23_01_0A_14_5C.headset_head_unit module-bluez5-device.c s16le ch 1 8000 Hz SUSPENDED
osmc@osmc:~$

excuse me the command before

osmc@osmc:~$ pactl list sources
Sorgente #0
Stato: SUSPENDED
Nome: alsa_output.platform-soc_audio.analog-stereo.monitor
Descrizione: Monitor of bcm2835 ALSA Analog Stereo
Driver: module-alsa-card.c
Specifica di campionamento: s16le ch 2 44100 Hz
Mappa dei canali: front-left,front-right
Modulo di appartenenza: 1
Muto: no
Volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB
bilanciamento 0,00
Volume base: 65536 / 100% / 0,00 dB
Monitor del sink: alsa_output.platform-soc_audio.analog-stereo
Latenza: 0 usec, configurata 0 usec
Flag: DECIBEL_VOLUME LATENCY
Proprietà:
device.description = “Monitor of bcm2835 ALSA Analog Stereo”
device.class = “monitor”
alsa.card = “0”
alsa.card_name = “bcm2835 ALSA”
alsa.long_card_name = “bcm2835 ALSA”
device.bus_path = “platform-soc:audio”
sysfs.path = “/devices/platform/soc/soc:audio/bcm2835_alsa/sound/card0”
device.string = “0”
module-udev-detect.discovered = “1”
device.icon_name = “audio-card”
Formati:
pcm
Sorgente #1
Stato: SUSPENDED
Nome: bluez_sink.00_23_01_0A_14_5C.headset_head_unit.monitor
Descrizione: Monitor of AUKEY EP-B40
Driver: module-bluez5-device.c
Specifica di campionamento: s16le ch 1 8000 Hz
Mappa dei canali: mono
Modulo di appartenenza: 17
Muto: no
Volume: mono: 65536 / 100% / 0,00 dB
bilanciamento 0,00
Volume base: 65536 / 100% / 0,00 dB
Monitor del sink: bluez_sink.00_23_01_0A_14_5C.headset_head_unit
Latenza: 0 usec, configurata 0 usec
Flag: DECIBEL_VOLUME LATENCY
Proprietà:
device.description = “Monitor of AUKEY EP-B40”
device.class = “monitor”
device.string = “00:23:01:0A:14:5C”
device.api = “bluez”
device.bus = “bluetooth”
device.form_factor = “headset”
bluez.path = “/org/bluez/hci0/dev_00_23_01_0A_14_5C”
bluez.class = “0x240404”
bluez.alias = “AUKEY EP-B40”
device.icon_name = “audio-headset-bluetooth”
device.intended_roles = “phone”
Formati:
pcm
Sorgente #2
Stato: SUSPENDED
Nome: bluez_source.00_23_01_0A_14_5C.headset_head_unit
Descrizione: AUKEY EP-B40
Driver: module-bluez5-device.c
Specifica di campionamento: s16le ch 1 8000 Hz
Mappa dei canali: mono
Modulo di appartenenza: 17
Muto: no
Volume: mono: 65536 / 100%
bilanciamento 0,00
Volume base: 65536 / 100%
Monitor del sink: N/D
Latenza: 0 usec, configurata 0 usec
Flag: HARDWARE HW_VOLUME_CTRL LATENCY
Proprietà:
bluetooth.protocol = “headset_head_unit”
device.intended_roles = “phone”
device.description = “AUKEY EP-B40”
device.string = “00:23:01:0A:14:5C”
device.api = “bluez”
device.class = “sound”
device.bus = “bluetooth”
device.form_factor = “headset”
bluez.path = “/org/bluez/hci0/dev_00_23_01_0A_14_5C”
bluez.class = “0x240404”
bluez.alias = “AUKEY EP-B40”
device.icon_name = “audio-headset-bluetooth”
Porte:
headset-input: Headset (priority: 0)
Porta attiva: headset-input
Formati:
pcm

Thanks

@bengio @RobertJRussellLives

As I always used my Bose Bluetooth speakers and never had an issue I now took a Headphone/Headset similar to what @bengio is using.

  1. Didn’t had any issue to connect using bluetoothctl / scan on / trust / pair . The Headset the connected but disconnected with in a few seconds. After I issued connect all was good.
    Headset was showing similar as @bengio first the headset then the audio sink.
    UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
    UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)

  2. When trying to play from Kodi when I connected the headset the sound moved away from HDMI but didn’t reached the headset. When disconnecting the headset it took up to a minute for sound coming back to HDMI

  3. I then tried @RobertJRussellLives pactl list sources short with my headset connected but it was not showing any of the MAC info from the headset.

0 alsa_output.platform-soc_audio.analog-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz IDLE

So not much of a help for you but clearly a confirmation that headset profiles could be part of the issue.

EDIT:

When connecting the Bose Speakers I get this output
|0|alsa_output.platform-soc_audio.analog-stereo.monitor|module-alsa-card.c|s16le 2ch 44100Hz|SUSPENDED| |---|---|---|---|---| |3|bluez_sink.08_DF_1F_21_CB_03.a2dp_sink.monitor|module-bluez5-device.c|s16le 2ch 44100Hz|SUSPENDED|

1 Like

Ok here comes the trick how it worked for me. Not using the sources but the cards approach

pactl list cards short
This showed the bluez device as number 7
pactl set-card-profile 7 a2dp_sink
And bam, sound on the headphone.

And when I disconnect audio on HDMI directly. But a reconnect didn’t made it come to headset directly and card index moved from 7 to 8.

1 Like

Roger that, Ok so a little pulse audio 101, there are two directions that audio can travel, it can be incoming like a microphone or an input audio stream or whatever, these are refereed to as source devices. when we are talking about audio output such as speakers or an output audio stream we are talking about a sink. So because the headset profile that its creating has both input and output to the headphones it creates both a sink and a source.

So you can see on that result that the first line
1 bluez_sink.00_… its refering to the audio stream coming out from osmc, into the headset.
2 bluez_source.00_… its refering to the audio stream coming from the headset into osmc.

you kind of have to take it from the perspective of osmc as it is the software handling the connection.

So in this case, we want the audio going out from osmc into the device which is the sink so our device is 1 does that make sense?

so give pactl set-card-profile 1 a2dp_sink a go.

Looks like @fzinken has some additional info to look through as well.

1 Like

That is what worked for me, the only issue I currently see every disconnect/reconnect increases the card ID which seems odd

1 Like

Hi @RobertJRussellLives
Hi @fzinken

yesterday i doesn’t set card profile attending Robert responce
this morning i have launch command and the numbers have changed. (now they are 5 and 6). so hypothetically, I can no longer put 1.
obviously this night I turned off my headphones
so what do i do?
thanks

osmc@osmc:~$ pactl list sources short | grep 00_23_01_0A_14_5C
5 bluez_sink.00_23_01_0A_14_5C.headset_head_unit.monitor module-bluez5-device.c s16le ch 1 8000 Hz SUSPENDED
6 bluez_source.00_23_01_0A_14_5C.headset_head_unit module-bluez5-device.c s16le ch 1 8000 Hz SUSPENDED
osmc@osmc:~$

As I wrote I suggest to use the card command instead.
pactl list cards short
Check Number of Bluez card and use on next command
pactl set-card-profile <ID> a2dp_sink

Or reboot which would make it card 1 again.

1 Like

Just look for sink in the output.

bluez_sink.00_23

whatever number that is is the one you’re after.

1 Like

HI @RobertJRussellLives
Hi @fzinken

now the quality of audio is correct!!

0 alsa_card.platform-soc_audio module-alsa-card.c
osmc@osmc:~$ pactl list cards short
0 alsa_card.platform-soc_audio module-alsa-card.c
1 bluez_card.00_23_01_0A_14_5C module-bluez5-device.c
osmc@osmc:~$ pactl set-card-profile 1 a2dp_sink
osmc@osmc:~$

but the second problem persist
when i turn off and turn on the headphones i have to go to “audio output device” and switch ALSA->HDMI->ALSA

Thanks

As I wrote with the headset I see a similar behaviour while with the speakers this works flawless. Maybe also related to the multiple profiles.

1 Like

so this means that the moment we can not do anything and it is necessary to wait for future releases that solve the problem for the headphones?

thanks

Well for the time being I think only way is to further investigate what’s happening and as we now have a starting point that is good.
Don’t expect any fixing from OSMC side till bluez stack is switched. So for the time being can just hope someone in this thread has a bright idea

great news, glad to hear it !

thanks @RobertJRussellLives for support and for never having left me for a moment
thanks @fzinken for support

Hi. Is there any news or idea to solve the problem about bluetooth headphone?
Thanks . Happy New Year.

I haven’t heard from others having the issue.
And as written I only expect a change when OSMC may switch to bluez

Ok thanks for reply

Hi.
Are There anythings news about bluetooth with the last release of osmc?
ty

It’s still experimental.