Suedkiez
August 13, 2026, 6:15pm
12
This is a known behavior, 200k or so are the apparently official limit where it works really reliably. Depending on phone model. Though they are working on it and it’s already gotten better.
Tailscale probably won’t help you with that, it has to do with the inherent limits of a phone, where the OS heavily limits what apps can do, and there are hard limits on data transfer and other resources.
Several posts about it, e.g.
Hi @ajl ,
Thank you for your post, and we’re sorry to hear you’ve been experiencing performance issues with the app.
Diagnostics indicate that ARC is being throttled by the phone operating system due to memory and resource constraints. This is almost certainly related to the size of your library—about 250,000 tracks. ARC maintains a local “copy” of your Roon database on the phone to ensure changes sync properly when you’re back online. This acts as a metadata cache, helping maintain database pa…
Hi @Uli_Lennartz ,
Thank you for your patience.
Reviewing this case, your Roon database is almost certainly too large to sync reliably with ARC.
Diagnostics show your library contains roughly 700,000 tracks. ARC isn’t built for full-scale library management like RoonServer, but it still needs to maintain the object graph for the entire database to track changes while offline. Syncing a library of this size would require transferring metadata, artwork, and track information for hundreds of thou…
Hi @guimx ,
Unfortunately, what you’re encountering is a symptom of the database itself not syncing properly due to resource and data transfer constraints. This is a symptom of the database being too large for the ARC and the phone to handle.
To use ARC effectively, Roon needs to synchronize information about your music library to your mobile device. While the synchronized data is far smaller than what’s stored on the Roon Core, a library of this size—700+ tracks—can still be too large for a mo…
1 Like