I am running the latest version of Roon server. After the last update I applied (last week?), ARC has become unusable. It will typically play one or two tracks, and then start spinning. I have seen a "poor connection" message a couple of times. Roon is running in a docker container alongside Plex, and when Roon ARC hangs, PlexAmp still works fine, running on the same server, accessing the same FLAC files.
I typically run ARC through Android Auto on a Pixel 10 XL Pro, using a wireless adapter. The issue happens every time I am in the car now.
Tell us about your home network
· Roon at home has no problems. Router is an Eero. My phone does have the tailscale client on it, but I have disabled it to see if ARC would reconnect, and it did not.
Does this happen in ARC outside of Android Auto? Does it happen equally often with local files and with streaming service tracks?
Try testing with WiFi disabled, playing a local server file to the phone speakers.
Long-term, the team has major work planned to address instability in ARC and Android Auto. Pixel can sometimes limit ARC’s access to the audio or network stack to aggressively save battery, and the ARC framework will interpret it as an actual poor connection problem. Try limiting any adaptive battery settings, or closing and re-opening ARC just prior to entering the car and connecting to Android Auto. These aren’t obviously long-term solutions, but they may help relieve some of the symptoms while the team works to improve the underlying framework.
I did some testing from home, wifi disabled. I started ARC and played an album from Qobuz. It played 2 tracks and hung. I closed and restarted ARC and played a local album. The whole album played fine. I then pulled up a Qobuz album, it played one track and then hung. Looks like this has nothing to do with Android Auto.
If you’ve confirmed the issue is only with Qobuz, that actually narrows things down considerably and (somewhat) removes the Pixel or Android as a variable here.
Qobuz streams don’t pass through your Roon Server machine, only the authorization requests. This means the disconnection here is in the actual downstream connection from the Qobuz API’s edge node or CDN serving your region and your phone. That’s a problem we’ve documented before and are working with Qobuz to resolve.
Do you happen to have any consumer VPN installed on this phone (NordVPN, MullvadVPN, anything like that)? A useful test to pinpoint whether the Qobuz connection is at fault is to connect the phone via cellular data with a VPN turned on, with a different geographic region assigned for the network path. If you can stream Qobuz uninhibited with the VPN on, we’ll have isolated the issue.
We’ll watch for your reply. Thank you again for your patience.
I do not have a consumer VPN installed. I do have a Tailscale client on my phone that I use for connecting to Nextcloud on the same server as Roon, but I had already disabled it to eliminate that variable.
Thanks for confirming that. This is still being investigated by our dev team, and since we can’t confirm the VPN aspect, we’ll need to wait for the investigation to finish on their end. Please keep an eye on the main tracking thread for any updates:
To update you on the status here, Qobuz is working with their infrastructural partners to resolve a delivery issue affecting certain tracks and certain geographies.
The Roon team is assisting in their investigation and we’ll share updates in the thread @noris has posted above. Thank you for your patience.
Please note that any update on this issue will be posted in the linked thread, we will go ahead and close this one and keep the other one open for general tracking. Thank you.