· I'm having trouble with Roon ARC
· Other
Bluetooth Metadata/Track info does not display on car screen when connected to my Pixel 7 pro over bluetooth.
Asus router, verizon fios ONT box, Intel NUC running ROCK. Google Pixel 7 pro, Android 14
I see there is another topic here with the exact same issue, but that topic is closed with no resolution.
Hi @KungFuNat,
Thanks for reaching out to us about this issue. Since this is an issue with a head unit can you tell us which model of head unit you are using or if it came with your car the make and model of your car? That will help us determine the issue.
2024 Honday Odyssey. Stock factory head unit… The only Info I can find is that it supports AVRCP 1.3. I have tried setting my phone to AVRCP 1.3, 1.5, and 1.6. All of them behave similarly. The metadata will show very rarely. One of the things I have noticed is that if ARC is showing the faulty behavior, and I open the Spotify app, start music, it will show the correct metadata. If I then re-start the music in ARC, the metadata shows correctly.
Hi @KungFuNat,
Thank you for the report. Just to confirm a few details about this report before we attempt to reproduce it internally:
The track metadata populates from ARC on the head unit but only after closing and reopening the app after connecting,
The track metadata will not populate if ARC was already open before you pair the Bluetooth connection with the head unit.
Does this summarize the issue correctly?
1 - No, the track data only returns if I close the bluetooth connection via the phone settings and turn on bluetooth again. Or, if I open another music streaming or podcasting app, start an audio stream, then return to arc and start playing music again.
2- Whether the ARC app is open or not before the bluetooth connection is established makes no difference.
I went through a number of iterations of connections/app openings and closings today(10/14) around 5:30pm to 5:50pm EST. if you can pull the logs, this should show the failure state several times.
@KungFuNat Thank you for clarifying this for us! We will attempt to reproduce this ourselves. We will get back to you when we know more.
Thanks @KungFuNat. We have a ticket in with our QA team to reproduce this and we’ll post updates here.
Hi @KungFuNat,
If possible, can you please record a short video of this display issue on the head unit using the phone or another device? Use this link to upload the video for our team.
This will greatly expedite our investigation and potential fix. Thanks!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.