Thanks for letting us know that your problem is persisting. We will create a ticket for this and bring it to our dev team to look into further. We will respond when we have some more information.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
Thanks Daniel.
If it’s helpful, I can tell you that this also just now happened with a downloaded file. The track is “I Lose Hope” by Leprous. It has happened several times in quick succession.
Hi @Dylan_Forbes,
The team has a ticket in for playback issues on Pixel phones matching the symptoms you’ve described here.
We’ll post here when this ticket has merged into the public build and the fix is available via an update. Thank you for your patience.
1 Like
Hi @grzlybear,
We have a ticket in for this issue and there should be improvements merged into the Early Access build within the next few releases. We’ll post an update here. Thanks!
1 Like
Hi all. I want to chime in and clarify that there are at least three separate issues being described here. I assume they are all specific to Android.
- playback stops after transitioning from WiFi to cellular while listening to non-downloaded tracks. specifically it stops right at the end of the last track that was begun while on WiFi. the play button and the queue both become non-functional. this has been happening to me for several months. the workaround is to close the app, reopen it, then skip backwards and forwards in the queue.
- playback stops intermittently during any track being played. this has been happening only since the latest stable ARC release. it happens on downloaded and streamed tracks, and while set to offline mode. it seems to be an issue with the priority of the background task responsible for the playback, because the workaround is simply to navigate back to the app.
- ARC randomly loses a connection to the server, with errors such as “corrupt data”. this has been happening to me since the very beginning of using ARC. at the very least, we need better error messages, because I know that my tracks are not corrupted, as they work while played via Roon directly.
should a separate thread be spun up for each of these, or should all “ARC Android playback” bugs be tracked in one thread?
thanks
1 Like
Also, Connor, could you clarify which of these issues the devs have merged a fix for into the early access build?
I’m not sure if this helps, but more info can’t hurt.
I have this issue on a s24 ultra and on a s23 ultra on the verizon 5g network. After activating either phone, the connection to roon arc was good, but then after a phone restart or app update or reinstall of the app, the troubles would start. it would sometimes queue up a song eventually, most of the time it was just infinite spinning. I could get local music from my library in the server to play, but anything from qobuz or tidal will cause the issue.
However, I did find a temporary workaround, running a vpn on my phone, the connection works perfect, only issue is when the vpn jumps servers, roon arc loses the playlist thats playing. Android auto also has some issues this way. If the vpn is on, android auto wont work at all, so i have to split tunnel the vpn to only roon arc and not the whole phone. That’s how I’ve been operating roon arc for a couple of months now without issue.
Strangely, if I use the s23 Ultra on cellular network and turn on mobile hotspot, any phone connected to the s23s hotspot can play music, but the s23 itself cant. This also was not an issue on my old LG v60 that also had 5g, but only mmwave.
It’s 100% something to do with cellular networks, but somehow hotspotting that network to a different phone doesn’t cause the issue. Playback on any wifi network seems to be fine.
Hi Connor! Are there any updates on this?
Hello All,
This issue should be fixed with a Roon release from October, but if you are still seeing this issue please let us know or open up a new support request, thanks!
Hi Noris!
Thanks so much for the update! Can you clarify which of the issues has been fixed? I identified a few issues in an earlier comment, and I’m not sure if they’re all from the same underlying problem.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.