Ethernet connection, upnp setup and Roon-Arc ready according to the Roon-Arc section in Roon. Bandwidth is 50 mbps upload and 950 mbps download.
Connected Audio Devices
Connection is from a Pixel 8 to Bluetooth on my car, a Honda Civic LX 2018
Description of Issue
When connected to my car via Bluetooth, album names do not update except for during the initial connection. It will show the album name on whatever was playing on my phone when the car was started, and then it stays the same throughout the entire rest of my car running.
Strangely, this only happens on Android 14. On my old LG V60, stuck on Android 10, Roon ARC DID update the album name with no problems with my car.
Even more strange, other programs like Spotify or Tidal on android 14 do not have this issue, they update the album name with no problems whatsoever on my current phone. Only Roon ARC seems to have this strange problem.
Hey! Sorry about the delay in answer. No sadly, I still have the same problem. In fact, it’s actually gotten worse, it doesn’t show ANY information now. Just says “Not Provided” for title and artist now.
Only Roon ARC does this, Spotify/YouTube/Whatever else displays perfectly fine on my car screen.
ARC needs to figure out why this happens and fix it. My guess is that there’s something to do with the BT standard that isn’t being used by ARC correctly, since my car’s from 2018 and doesn’t have Android Auto or anything like that.
Thanks for responding. Mine is also older, 2015 Subaru. It will do the same, just go completely blank. I have messed with it a bit more since posting and have discovered that opening up the Youtube app and just scrolling down a little bit ends up bringing back the Roon metadata to the screen. I don’t even have to play anything, this can just be done while Roon is playing. However it will randomly do it again eventually. Not quite sure why that would be but I’m thinking some app update (either Roon ARC or Youtube) must have broke it. Maybe you can try the same and see if it can be duplicated.
I also started looking at Bluetooth AVRCP versions in the Android dev settings, and switching to older ones, but haven’t got that far yet.
Interesting thing, I got in my car today and the issue seems resolved completely? How is it on your end? I’m using AVRCP 1.4, but it wasn’t working before today with that set there anyway, but now it’s completely fine.