[SOLVED] LG TV: Bluetooth connected but no sound

[Pavel Frolov]

Hello,

I have raspberry pi 3b

...

Truly a Pi 3B and not a Pi 3B+?

Are you using both the WiFi and Bluetooth interfaces?

As soon as that model was released reports started showing up  on the Raspberry Pi Forum about its WiFi and Bluetooth not working well together. Not everyone had a problem and not everyone who did saw the same behavior. There was lots of speculation but I don't know that specific issues were ever resolved at the software level.

There are some steps you could take to see if this is the cause of your problem.

1) try using an external Bluetooth adapter. You have to disable the internal Bluetooth interface in moOde's System Configuration menu. 

2) alternatively, try using an external WiFi adapter. You have to disable the internal WiFi interface in moOde's System Configuration menu.

3) alternatively, try connecting to your local area network via the Ethernet interface instead of WiFi. Again, you can disable the internal WiFi interface in moOde's System Configuration menu.

Diagnosing Bluetooth problems from the command line without proper "sniffing" tools is tedious even for experienced Linux programmers.

I use later model Pis with 5GHz WiFi connections and a variety of either Bluetooth sources (e.g., smart phones, tablets, etc.) or Bluetooth sinks (e.g., speakers, headphones, etc.) and have no problem with the Bluetooth connection.

Regards,
Kent

Kent, thank you for the answer!

My devise is Pi 3 Model B

About WiFi, actually I had a problems with WiFi too, and I disabled it (in the moOde config) and use Ethernet now.

1) try using an external Bluetooth adapter. You have to disable the internal Bluetooth interface in moOde's System Configuration menu. 

It's very good advice for my case! I will try.

[Pavel Frolov]

Unfortunately I have a problem again.

I watch video and sometimes sound disappears and then connection is lost.

For now I caught error logs

Code:

...
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: a2dp-audio.c:403: BT read error: Connection timed out
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: a2dp-audio.c:403: BT read error: Resource temporarily unavailable
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: a2dp-audio.c:403: BT read error: Resource temporarily unavailable
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: a2dp-audio.c:403: BT read error: Resource temporarily unavailable
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: a2dp-audio.c:403: BT read error: Resource temporarily unavailable
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: a2dp-audio.c:403: BT read error: Resource temporarily unavailable
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: a2dp-audio.c:411: BT socket has been closed: 10
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: ba-transport.c:1054: Exiting IO thread: A2DP Sink (SBC)
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: dbus.c:59: Called: org.bluez.MediaEndpoint1.ClearConfiguration() on /org/bluez/hci0/A2DP/SBC/Sink/1
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: bluez.c:332: Disconnecting media endpoint: /org/bluez/hci0/A2DP/SBC/Sink/1
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: ba-transport.c:1006: Closing PCM: 11
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: ba-transport.c:361: Freeing transport: A2DP Sink (SBC)
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: ba-device.c:131: Freeing device: 20:3D:BD:F3:57:3B
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: bluez.c:1009: Signal: org.freedesktop.DBus.ObjectManager.InterfacesRemoved()
Sep 18 08:44:12 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: bluez.c:1009: Signal: org.freedesktop.DBus.ObjectManager.InterfacesRemoved()
Sep 18 08:44:12 frolov-media bluealsa-aplay[19187]: /usr/bin/bluealsa-aplay: D: aplay.c:290: Exiting PCM worker 20:3D:BD:F3:57:3B
Sep 18 08:44:13 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: bluez.c:1009: Signal: org.freedesktop.DBus.ObjectManager.InterfacesRemoved()
Sep 18 08:44:13 frolov-media bluealsa[1100]: /usr/bin/bluealsa: D: bluez.c:1009: Signal: org.freedesktop.DBus.ObjectManager.InterfacesRemoved()
Sep 18 08:44:13 frolov-media systemd[1]: Stopping Bluealsa-aplay...
Sep 18 08:44:13 frolov-media systemd[1]: bluealsa-aplay@b8:27:eb:de:93:4f.service: Succeeded.
Sep 18 08:44:13 frolov-media systemd[1]: Stopped Bluealsa-aplay.
Sep 18 08:44:13 frolov-media systemd[1]: Configuration file /etc/systemd/system/bluealsa-aplay@.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Sep 18 08:44:13 frolov-media systemd[1]: Configuration file /etc/systemd/system/bluealsa-aplay@.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Sep 18 08:44:19 frolov-media bluetoothd[1062]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 20:3D:BD:F3:57:3B: Host is down (112)
Sep 18 08:44:26 frolov-media bluetoothd[1062]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 20:3D:BD:F3:57:3B: Host is down (112)
Sep 18 08:44:35 frolov-media bluetoothd[1062]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 20:3D:BD:F3:57:3B: Host is down (112)

[clacla]

I had the same problem when I upgrade to 8.3.6.

I resolve it by changing the /etc/bluealsaaplay.conf to :

Code:

# bluealsaaplay.conf
#AUDIODEV=_audioout.conf
AUDIODEV=plughw:0,0
BUFFERTIME=500000

[Haroldfinch]

I had the same problem when I upgrade to 8.3.6.

I resolve it by changing the /etc/bluealsaaplay.conf to :

Code:

# bluealsaaplay.conf
#AUDIODEV=_audioout.conf
AUDIODEV=plughw:0,0
BUFFERTIME=500000

I don’t know if it helps but I have faced this similar issue on the latest release. In previous releases been able to connect to Moode via Bluetooth and then stream the audio.


The latest release broke this and I had to make the change that @clacla posted above.


@Tim Curtis let me know if there are any logs or other things you need to debug this problem.

[Tim Curtis]

Thanks for confirming.

What is your setting for ALSA Output mode in Audio Config?

[Haroldfinch]

Thanks for confirming.

What is your setting for ALSA Output mode in Audio Config?

The attached image has the settings that I currently have

[Tim Curtis]

Thanks for confirming.

What is your setting for ALSA Output mode in Audio Config?

The attached image has the settings that I currently have

That's what I thought. In that case Bluetooth would also be using Direct (hw) output which could cause a compatibility issue if the device doesn't support the exact format being sent. This is because Direct mode does not do any automatic format conversions.
I could add a "Compatibility" option to Bluetooth Control to allow it to use ALSA plughw. The only downside is that Bluetooth can't use any of the DSP's.
Alternatively you could set ALSA Output mode to "Default". This would allow Bluetooth to use DSP.

[s_mury]

Sorry to continue this thread but I have a similar problem to Paval. Since updating to 8.3.6, I no longer get sound when connected to moode in Bluetooth speaker mode (using a Pi Zero W and Hifiberry Miniamp). My computer connects but no sound is produced. Sound is produced using local audio so the setup is otherwise functional. Before updating, this setup worked fine and I had no drops like Pavel.

I have re-imaged with a fresh copy but its the same.

Before rolling back to an older version, do you have any idea on how I might resolve this?

Best
Sean

[Tim Curtis]

Try the change described in this post.
https://moodeaudio.org/forum/showthread....6#pid48716

[s_mury]

Try the change described in this post.
https://moodeaudio.org/forum/showthread....6#pid48716

Hi Tim,

Thanks, that helped. I didn't think to check it because that post seemed targeted at connection drops which I do not have (the connection is stable) and I have the alsa output mode set to default.

However, now I have a quite noticeable lag even though the pi and the PC are 30 cm apart. I turned the latency down to 60ms but it's very clearly there e.g. by looking at youtube videos.