ARC on Android Auto slow with playback issues and slow connection test (ref#UNKL00)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· For quite a while now, ARC on Android Auto has been annoyingly slow. Tracks initialize for a very long time (10-15s) and regularly simply stop in the middle of playback. I have port forwarding set up and the connection test in Roon is successful, although this test, too, is not very snappy, it takes about 8-10 seconds to complete the connection test.

Tell us about your home network

· Router: TP-Link ER7212PC, Roon server on Windows, connected via ethernet through a switch (TP-Link TL-SG105). No VPN.

Hi @Teun_Romme,

Thank you for the report. We have a few questions to pin down what’s wrong here.

Are you having this issue with both Qobuz and local files in ARC? Qobuz takes a different network pathway for ARC streaming and won’t pass through your server at home (the download goes straight from their API to your phone).

If you connect your phone via cellular data without connecting Android Auto, do tracks also load slowly?

What about browsing in ARC? Is it slow to navigate the app?

Thanks and we’ll watch for your reply.

Hi connor, thanks for reaching out. I will do some testing to properly answer your questions (Qobuz vs. local; cellular vs. Android Auto; slow browsing in ARC) and get back to you.

Sounds good @Teun_Romme, keep us posted on how that goes.

In addition, I’m curious, do you see any failures surrounding album art not loading as well, under the same conditions?

Hi,

  • Qobuz vs. local: local files are loaded significantly faster. Qobuz files can take anywhere between 5-30 seconds (if this takes long enough it will just time-out and pause playback), local files never take more than 2-3 seconds.
  • Cellular vs. Android Auto: same experience, no difference.
  • Slow browsing: yes, browsing can be slow but not always.
  • Album art: I am not seeing any failures loading album art, but this can take 2-4 seconds after starting the track.

Sorry, took me some time to do this test.

Regards,

Teun

Hi @Teun_Romme,

Thanks for taking the time to run those tests properly; the split you measured between local and Qobuz turned out to be exactly the right thing to look at. I’ve gone through your Roon Server logs from the past couple of weeks, and I can rule a few things out with confidence.

Your network and port forwarding are healthy. Across 82 connectivity checks in the logs, the port test passed in under a second every single time. The logs also show a single NAT with a normal public IP, no double-NAT, no carrier-grade NAT.

The 8–10 second connection test is expected in your setup, and it isn’t a symptom. Nearly all of that time is Roon searching your LAN for a UPnP-capable router and timing out after about 7 seconds, before it runs the actual test. Since you’ve forwarded the port manually on the ER7212PC and UPnP is off there, that search will always time out. You can enable UPnP if you’d like the test to feel snappier, but nothing functional changes, that number is safe to ignore.

On Qobuz, the logs confirm what your test results suggested. Your server really isn’t involved in Qobuz playback in ARC: across 109 Qobuz track starts, it made zero requests to Qobuz. It hands ARC the track and your phone downloads from Qobuz directly. Your server answered every one of those requests in under a second, and its own connection to Qobuz averages around 150ms. So the delay is happening between your phone and Qobuz, after your server is out of the picture.

What I can see is your phone giving up and restarting tracks, 28 of 89 Qobuz tracks were re-requested up to several minutes later. Local files show nothing like that.

There’s one asymmetry that likely explains it. For local files your server transcodes to a compact stream before sending, which is why they start in 2–3 seconds. For Qobuz it can’t do that, your phone pulls the original file at whatever quality Qobuz serves. On a cellular connection, a hi-res Qobuz album can be 10–20x the data of the same track played from your library.

Three things would confirm or kill that:

  1. In ARC’s settings, what’s your streaming quality set to for cellular? If it’s on Original, could you drop it a notch and retry the same Qobuz albums?

  2. Which Qobuz albums are the slow ones, and what sample rate / bit depth are they? Are the fast ones 16/44 and the slow ones 24/96 or higher?

  3. Could you try the same album in the Qobuz app itself, same phone, same cellular connection? If that also stalls, we’re looking at the link to Qobuz. If it’s instant, it’s something in how ARC handles that download.

We’ll be monitoring for your reply, thank you!