Identify the direction of Bluetooth audio
The usual headphone task sends audio from the LibreELEC device to a speaker or headset. Receiving phone audio into LibreELEC is a different direction with a different configuration. Begin by naming the transmitter and the device that should produce sound.
Choose one familiar local speech sample and set a modest output level. Keep an ordinary working audio route available so a silent result can be compared without altering the media source. A paired device shown in a list is useful evidence, but it does not establish that Kodi is using it for playback.
Pair through the appliance settings
LibreELEC’s PulseAudio documentation describes pairing the Bluetooth audio device in the LibreELEC Settings add-on, then choosing Bluetooth Audio as Kodi’s output. Use the installed system’s actual controls and confirm the intended headset identity before connecting.
If several similar devices are nearby, keep only the intended device in the test and verify its own pairing mode. Record whether pairing completes and whether the connection remains active. A failed pairing should be diagnosed before changing Kodi’s media decoder or source account.
Select the output and listen to the same passage
After pairing, inspect Kodi’s audio-output choice and select the documented Bluetooth route where offered. Replay the same local speech sample. Confirm sound emerges from the intended headset and not from the television at a separate level.
If the selected output is silent, compare the connection state and ordinary output route separately. Keep the file, track and playback position unchanged. Do not add command-line PulseAudio modules simply because the documentation also contains more advanced receiving and network examples; those examples address different tasks.
Check reconnection and timing deliberately
Stop playback, reconnect the headset through its ordinary supported behavior and replay the sample. Record whether the intended output remains selected. If speech is audibly delayed, retain that as a separate synchronization result instead of treating successful pairing as proof of perfect timing.
The expected outcome is a known sending route to the actual Bluetooth device. It does not provide Chromecast-style video casting, certify every headset profile or guarantee identical delay after another hardware change. Keep the final output choice in the device notes so another viewer can return to the television speakers when needed.
Questions answered
Does successful pairing prove Kodi has selected the headphones?
No. Verify the audio-output choice and listen to a known sample on the intended device.
Should I use the phone-receiving command sequence for headphones?
No. Identify the audio direction first. The documented sending route and advanced receiving route serve different purposes.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.