Roon ARC Metadata Update and Stability Issues on Xperia 5 V (ref#9EV5O4)

Hi! What’s not quite right with Roon?

· Can’t reach my Server, remotes or ARC

Can’t connect to my Server, remotes or ARC

· Other ARC issues

Tell us what's going on

· Hello,

I am experiencing two issues with Roon ARC on my Xperia 5 V.

System:

- Xperia 5 V
- Android 15
- Latest Roon ARC version
- Daihatsu OEM head unit NMZK-W69D
- Bluetooth AAC connection

Issue 1: Bluetooth metadata does not update correctly

Music playback works normally, but the track information shown on the head unit does not update when tracks change.

- Audio playback continues normally.
- The head unit continues to display an older track title, album, and artist.
- If I press Next or Previous on the head unit, the metadata updates correctly.
- Qobuz works correctly on the same phone and head unit.
- The issue only occurs with Roon ARC.

Additional information:

- AVRCP 1.6: metadata is often missing completely.
- AVRCP 1.4: metadata appears, but does not update when tracks change.
- I have photos showing the mismatch between the current ARC track and the metadata shown on the head unit.

Issue 2: ARC stability problems

I have also experienced repeated ARC crashes and playback problems.

- "Roon ARC keeps stopping" messages appear.
- Sometimes playback time continues to advance, but no audio is heard.
- Occasionally playback becomes unstable and requires restarting the app.
- I have been using the USB Audio Driver (Beta) setting, which may be related.

Thank you.

Tell us about your home network

· Home network:

- ISP: Kvision cable internet
- Main router: NEC Aterm WX7200D8BE
- Mesh Wi-Fi network with additional NEC access points
- Roon ROCK running on Intel NUC8i5BEK
- ROCK connected via Ethernet
- ARC access configured and working normally
- No VPN in use

Hi @miyamoto31113, welcome to the community.

Thanks for laying this out clearly. The Bluetooth metadata behavior and the ARC stability issue may be separate, so we should look at them one at a time.

For the ARC crashes and playback stalls, we’ll need diagnostics from the app around the next failure. We’ll enable those on your account, then the next time ARC stops or playback becomes silent, please note the exact local time, date, and what was playing, and let us know here. That gives us a clean window to review.

For the Bluetooth metadata problem, a couple of checks would help narrow it down:

  • Does the head unit update correctly if you change tracks from the phone itself, rather than using the head unit buttons?
  • Does the same metadata behavior happen with ARC when the USB Audio Driver (Beta) setting is turned off?

Since you already confirmed this is specific to ARC and not Qobuz on the same phone and car, that points us toward how ARC is handling AVRCP metadata on this device. If you can also share a photo of the mismatch, that would be useful for us to compare what ARC is sending versus what the head unit is keeping on screen.

Reply with the next timestamped crash, plus the answers above, and we’ll take it from there.

Thank you.

To answer your first question: the metadata does not update even when I change tracks directly from the phone using the ARC app.

I will continue testing and will report the next ARC crash or playback stall with the exact date, time, and track that was playing.

Thanks for your help.

Sounds good, thank you @miyamoto31113 :folded_hands: