Bluetooth -> SPDIF routing is broken on Vero V

Help and Support Vero V
1

I use bluetooth to stream music from Android phones to Vero V and output it on the optical SPDIF interface. I’ve discussed some of this here, but the issue is not bluetooth related as I originally thought: Bluetooth issues, possibly due to codec?

Regardless of the phone I use, the following happens.

Scenario 1: If I 1) connect Android via bluetooth to Vero V and 2) fire up music app and play music, all works fine.

Scenario 2: But if I 1) play music on phone and 2) connect phone via bluetooth to Vero V, there is about 2 seconds of music playing over bluetooth and then no more music, even though it still shows as playing on my phone.

Now, this is my hardware setup:

Screenshot 2025-05-10 163700
Screenshot 2025-05-10 1637001907×541 20.7 KB

Thing is, apparently OSMC streams audio both on HDMI and SPDIF if both are connected so I can simply switch my DAC to optical in1 or optical in2 to select one of the above audio pathways. If the audio source is a movie OSMC plays locally or off the internet, both pathways work fine.

However if the audio source is bluetooth AND I find myself in scenario 2 (music is playing while bluetooth is connecting), the direct pathway from Vero V to my DAC doesn’t work!, yet the path that goes through HDMI and TV works. I suspect there is a bug somewhere in the bluetooth → SPDIF routing.

I noticed that by toggling the Audio Output Device on Android from Bluetooth → Speakers → Bluetooth, fixes the issue. But this screams a bug, something is not initialized correctly when setting up the Bluetooth → SPDIF routing when bluetooth is connected.

Please try to reproduce this, I have laid out all the info you need to reproduce this, you just need to have a SPDIF cable and SPDIF DAC/Speakers connected.

2

We will try to reproduce this. Meanwhile, debug logs from your Vero would be useful. Just restart, play music on Android and then route that audio to Vero. I assume you do that just on the Android device and aren’t having to use MyOSMC to connect? Reason: using MyOSMC if you have GUI sounds turned on makes Kodi grab the audio devices, stopping the passthrough from BT.

1 Like
3

Here’s the log, I played music on Android phone, then connected via bluetooth around timestamp 00:15, I heard about 2s of music then it stopped, then changed Audio Output Device on phone to Speakers, toggled it back to Bluetooth Audio Device and music played well after that. It should all be captured in the log.

https://paste.osmc.tv/evocecasaz

4

Thanks. We’ll take a look but it would be better to get a full log via MyOSMC or grab-logs -A from the command line.

5

I updated the link https://paste.osmc.tv/evocecasaz

1 Like
6

So I can’t reproduce this here, playing S/PDIF to my AVR. BT from my Samsung S8. In your log I see
[ 125.137914] input: Willie Trombone (AVRCP) as /devices/virtual/input/input11

after which things seem to go continuously. The log messages are the same as I see here.

I don’t know what to suggest.

7

thanks for trying to replicate

yeah, that’s the device, to me this happens both from Pixel 9 and Huawei P30 pro

when the fault condition occurs, i get a spam in my dmesg , see the dmesg log in my other thread, pay attention, I annotated it, Bluetooth issues, possibly due to codec? - #3 by radius

(annotations go through a scenario where i toggle bluetooth codecs, but i get the same output if i toggle sound output device on Android)