Balena sound doesn't work with new OS on samsung S10 and S10+

Hello,
i use balena sound since longer time and it worked perfectly but since the latest OS update on my S10+ i can’t connect to belana sound via Blue-Tooth anymore, my S10 and my samsung tablet still worked fine. after some tries i did a new installation of balena sound and it worked BUT only for the first time,
after diconnecting no new connection could be established.
Now my S10 erceived a OS update too and … same problem now.

The phones still connect to other blue-tooth speakers but NOT to balena sound.
the tablet still works with balena sound but … how long …till an OS update ?

No more working OS
S10: G973FODXDFUI5
S10+: G975FXXSDFUI5
AND SINCE LAST UPDATE
S10+: G975FXXSEFUJ2

Now my galaxy TAB A got an update too and same behavios as the other both , only one time connecting then never more.
Here the list of not working OS

Galaxy Tab A Software Version T510XXUSCUJ1 / T510OXMSCUJ1

Galaxy S10 Software Version G973FXXSDFUI5 / G973FODXDFUI5 / G973FXXSDFUI5

Galaxy S10+ Software Version G975FXXSDFUI5 / G975FOVFDFUI5 / G975FXXSDFUI5
and G10+ newer Version G975FXXSEFUJ2 / G975FOVFEFUJ2 / G975FXXSEFUJ2

somebody can help ?

Hi @pit, bluetooth issues are very hard to troubleshoot for us but we can give it a shot. Can you download the logs from the dashboard and share them here? Be sure to attempt to connect and capture anything that’s being logged too.

Also, can you clarify what the OS update is about? What version of Android were you in previously, and what version are you in now?

Hi @tmigone I unfortunately dont know if android version has changed but actually it is 11
and balena sound runs the latest version, the interesting thing is, if i install a new image i can connect but after a unconnect i can’t connect anymore.

i own three other bluetooth speakers and they still work only balena sound not.

i hope you can help
i tried to get the logs:
root@balena:~# balena ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8c9baacfc7e3 690361d275ba “/usr/bin/entry.sh /…” 7 days ago Up 3 minutes logging_4177658_1960465_6a4b252e82b196a198524fe48f949b89
286978391cd0 5531464cb5c2 “/bin/bash /usr/src/…” 7 days ago Up 3 minutes bluetooth_4177659_1960465_6a4b252e82b196a198524fe48f949b89
d90739cb4732 49f35c3f139f “/usr/bin/entry.sh /…” 7 days ago Up 3 minutes spotify_4177661_1960465_6a4b252e82b196a198524fe48f949b89
ec41842f5ae7 c6fd8cea8107 “/usr/bin/entry.sh /…” 7 days ago Up 3 minutes airplay_4177660_1960465_6a4b252e82b196a198524fe48f949b89
8159a1771213 6b761d33fa27 “/usr/bin/entry.sh n…” 7 days ago Up 3 minutes sound-supervisor_4177654_1960465_6a4b252e82b196a198524fe48f949b89
a7b5cf845cb7 fd0414759fa4 “/bin/bash /usr/src/…” 7 days ago Up 3 minutes 0.0.0.0:4317->4317/tcp audio_4177653_1960465_6a4b252e82b196a198524fe48f949b89
8fb97a24e4ef 9c8ca03f5620 “/bin/bash /usr/src/…” 7 days ago Up 3 minutes 1704-1705/tcp, 1780/tcp multiroom-client_4177657_1960465_6a4b252e82b196a198524fe48f949b89
56419216235c fad6575bb7f3 “/bin/bash /usr/src/…” 7 days ago Up 3 minutes 0.0.0.0:1704-1705->1704-1705/tcp, 0.0.0.0:1780->1780/tcp multiroom-server_4177655_1960465_6a4b252e82b196a198524fe48f949b89
665cc70436a3 balena/aarch64-supervisor:v12.10.10 “/usr/src/app/entry.…” 14 months ago Up 3 minutes (health: starting) balena_supervisor

root@balena:~# balena logs 8c9baacfc7e3
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0curl: (6) Could not resolve host: PATCH
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 48484: Connection refused
root@balena:~# balena logs 286978391cd0
Running balena base image entrypoint…
— Bluetooth —
Starting bluetooth service with settings:

  • Device name: balenaOS d6ac
  • HCI interface: hci0
  • Pairing mode: SSP
  • PIN code: 0000
    Available HCI interfaces: hci0
    Resetting hci0
    Configuring selected interface: hci0
    hci0 Set Connectable complete, settings: powered connectable ssp br/edr le secure-conn
    hci0 Set Bondable complete, settings: powered connectable bondable ssp br/edr le secure-conn
    hci0 Set Discoverable complete, settings: powered connectable discoverable bondable ssp br/edr le secure-conn
    hci0 Set Secure Simple Pairing complete, settings: powered connectable discoverable bondable ssp br/edr le secure-conn
    Pairing mode set to ‘Secure Simple Pairing Mode (SSPM)’. PIN code is NOT required.
    Bluetooth agent started!
    Checking for known bluetooth devices…
  • Attempting to reconnect to Galaxy Tab A (E0:D0:83:77:3B:7A)…
    org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
  • Could not connect to Galaxy Tab A (E0:D0:83:77:3B:7A)…
  • Attempting to reconnect to S10+ von Peter (6C:00:6B:76:DB:7A)…
    org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
  • Could not connect to S10+ von Peter (6C:00:6B:76:DB:7A)…
    root@balena:~#

@tmigone
In the meantime i talked to Samsung but didn’t get an information about changes.
So i took all three devices and went to a know shop and asked the owner if i could try to test pairing and unpairing and pairing again with several of the avaiable Blue-Tooth devices in the shop.
Every of my devices worked fine with the tested Shop devices, so in result it’s a programming problem iwth Balena-Sound , maybe an incorrect or not complete Blue-Tooth implementation.

Hey @pit, can you get the logs from the balenaCloud dashboard? There is a button that lets you download the logs. Be sure to capture the moment you try to connect.

bs-radio-wz_little-engine-22.12.21_07 19 49_(+0100).txt (6.5 KB)

hey @tmigone , i uploaded the logs to this message but it shows the same what i pasted into the message 2 steps before

@pit, I don’t see any noteworthy errors really. One thing you can try is to force balenaSound to unpair from your device and start the pairing process from scratch.

Here are instructions to do it:

  1. Go to your device page on balenaCloud dashboard
  2. Open a Terminal session on bluetooth service (bottom right corner)
  3. Run bluetoothctl, then paired-devices. You should see a list of paired devices MAC addresses in the form of AA:BB:CC:DD:EE:FF.
  4. Find your device and run: remove AA:BB:CC:DD:EE:FF

That should reset the pairing status, you’ll now be able to start the pairing process all over again.

@tmigone , that works , but the problem seemed to be that, if i unpair the device on the device , Balena still shows the device as paired. i suppose the paired entry must be deleted by balena sound while unpairing on the device , it can’t be to log into balena every time to delete entries .

wish you to have a merry christmas.

@pit, great! Let us know if you have any further issues :blush:

@Lizzieepton , Means “great!” the issue will be solved and we get an info ? :smile:

have a great day !