Starting with the fact that I'm really not sure where to place this anymore.
I had previously reported an issue with my phone staying connected to my Soundbar, and even went on to talk about a possible workaround, being under the impression that my issue may have been beta related and that i don't see a fix in time for the stable release. But now I'm not so sure. I've never seen this behavior before and can only speculate what the cause is.
See, I sat in front of my Soundbar last night listening to music, and watched as my Soundbar turned itself off after 15 minutes. The funny thing is that the Soundbar automatically shuts itself off after 15 minutes with no Bluetooth signal (which it did).... well except for the fact that it DID have a Bluetooth signal. For crying out loud i was in the middle of listening to Dance Macabre by Ghost when it shut itself off. At least 8 different devices had been connected to this Soundbar with no issues at all, yet i get a Samsung galaxy s26 and NOW my Soundbar wants to do this. I've had my pc, my TV, my nieces tablet, my cousins phone, my brother in laws last 2 phones, my last 4 phones, a Nintendo Switch... no issues at all. Then i get this phone and POOF instant regret.
The only thing i can think of is that this phone is sending the Bluetooth signal differently and my Soundbar isn't linking it. Does anyone know if this is some kinda possibility?
Just to check off some boxes, have you already un-paired and re-paired the connection? What does the BT connection show in your phone (i.e., connected for audio)? It certainly sounds like the Soundbar is not fully recognizing the ongoing connection.
EXACTLY MY POINT!!!! The question is why. Yes i did all that twice. I uninstalled the Soundbar app thinking that might have been it too no avail. it shows connected for audio.
