Declan O'Shaughnessy

I don't think it's the thread I'm thinking of, but this thread might offer some things to look at.

I'm guessing you have tried rebooting your phone also at this point? It's not unknown for Android phones to do background updates which change / break functionality. With that in mind, I'd start with first principles and have a poke around in the Bluetooth settings on your phone. It's different for every manufacturer, but somewhere in there you should be able to select whether you want your phone to connect to your car just for phone calls or for phone calls and media. I have mine (Oneplus 6T) only set-up for phone calls, for example. You might have to delete the existing connection and start again (no bad thing anyways), in order to be able to select what you want the Bluetooth connection to do. On my phone, access the Bluetooth menu, click the "gear" icon next to the SKodaBT connection and I can choose what I want to use it for from there. I'm sure something similar happened to someone on here not too long ago, and it was a background update that caused the problem. But I can't find the post at the minute, and my grip on time has loosened somewhat with lockdown! I keep thinking we're still in March...

It's an old "fix" but have you tried rebooting the Columbus? If not, reboot it by (from memory) holding down the < > and i buttons (your "i" button might look like a little wand I think in later builds to my car). The screen should go black and then reboot. 9 times out of 10 it fixes most Columbus glitches. If for any reason you can't see those buttons on your Columbus, or the unit won't reboot, just Google "reboot columbus rns 510" and you should find the full procedure.