Yes @connor - I’ve had a few thermal warning notifications from Arc in recent days.
my sense is that seemed to be at its worst when battery life is getting lower 30-40% on cellular and in transit.
Yes @connor - I’ve had a few thermal warning notifications from Arc in recent days.
my sense is that seemed to be at its worst when battery life is getting lower 30-40% on cellular and in transit.
Just hit another thermal notification @connor I was downloading on WiFi, Downloads paused - I can confirm the phone is really quite hot.
@connor i hit the restart thing again yesterday morning. About 9:05 I think. Linked to failed downloads the night before when I got the thermal warning perhaps?
Hey @Greg_Ince,
Thanks for sticking with us on this, and for enabling the extra logging. It’s given us a much clearer picture.
What we found
How you can help
Could you send us the iOS analytics reports from October 4, 9, 10, and 11? You’ll find them here:
Settings > Privacy & Security > Analytics & Improvements > Analytics Data
We’re looking for:
Tap a file, then use the share icon to AirDrop or email it to yourself. Zip them together and send them to us via the uploader link below. iOS only keeps these reports for a limited time, so the sooner you can grab them, the better.
Upload link:
https://workdrive.zohoexternal.com/collection/nocvrfc5b2ddab55140af8640f1d7ce13291e/external
Apple keeps very tight control over how much memory an app can use on iPhone. A few things are worth knowing:
A very large library like yours (about 170,000 tracks) means ARC has more to keep in memory, so it can run into that background limit sooner.
Thanks again, Greg.
Thanks @benjamin - this is interesting. I sensed the phone was somehow throttling things.
I’ve quickly checked the logs, and sadly the ones from the dates you reference have already gone.
I’ll try and watch out for future failures and grab logs quickly next time time.
Hi @Greg_Ince,
Ultimately, it’s expected to see low memory events during downloading, playback, or even background syncs with a database this size. The number of tracks in the library is generating an associated object graph that is simply too large for iOS to allow ARC to sync. This is causing performance degradation within the app itself, but also causing iOS to kill ARC entirely under certain conditions.
In order for ARC to retain parity with your database at home on the server, it has to create an equivalent object for every entry in the server. This doesn’t mean it’s duplicating track files (although downloading does that), but it does mean that thousands of metadata entries, artwork files, and other data must transfer between the phone and the server.
Even if the iPhone has storage to handle this volume of data, the operating system imposes limits on the scale of data transfer any one app can perform. In this case, iOS is almost certainly killing ARC because it’s violating a threshold for network and processing usage.
We’d like to promise that ARC will eventually work on a library of over 100,000 tracks, but in our internal testing, that’s the ceiling for reliable operation, even on new, major market phones with huge RAM and memory. This is a reality imposed by the phone manufacturers, rather than Roon.
The only reliable solution is to sync ARC on a fresh database that is considerably smaller. This might not be desirable, but it would drop the app’s data transfer below iOS limits. This process would require you to create an entirely new database rather than remove content from your current library.
We wish we could offer better news, but we wanted to be transparent about the technical blockers in this case.
We’re happy to answer any questions. Thank you.
We’re going to allow this thread to auto-close due to inactivity, but we invite you to reopen it at any time (or submit a new request) if you experience any change in symptoms or simply wish to pursue the issue further.
As things stand, it’s not possible for us to engineer around the limitations of library size. With a library over 100,000 tracks, we can’t promise ARC will perform reliably, during downloads or even just browsing. That said, we’re working to improve the app, and we’re not abandoning this case.
Thank you.
@connor Thanks. I’ve long had it on my list to sift, sort and purge duplicates to reduce library bloat (I often retain multiple versions of albums, in support of comparison, but usually defaulting to one).
If simple deletion of excess from the library wouldn’t help, I need to properly think through the implications of starting again from scratch if that could actually need to improve stability, assuming I concluded I could get nearer to a 100K track count.
I can see the case for starting a brand new library, and thinning things out, in service of improved stability, but I imagine that I would lose a lot of local work in playlists and curation - am I right that I would basically lose everything in starting from scratch?
I use Qobuz for streaming music in parallel with researching/exploring/tracking catalogues or releases I may wish to go back to, but do this by adding items to my library. It also stops me buying things at that point! I suppose listen later may be an alternative mechanism for this in the future, but I expect there would be limitations to that feature, too.
Hi Greg,
Thanks for thinking this through with us. We’re sorry it’s come down to this choice.
To answer your question: a fresh database starts empty. Playlists, edits, tags, play counts, favorites and anything you’ve added from Qobuz won’t carry over. You also can’t restore just part of a backup into a new database. A restore brings back the whole database, including its size.
You don’t have to give up your current library to try a fresh one, though:
Make a backup first. Follow our Roon Backups guide. The database reset steps rename your existing RoonServer folder rather than delete it, so you can go back to your current setup at any time by restoring that backup.
Keep a record of your playlists. From a computer, you can export playlists to Excel. The Excel export lists every track, Qobuz included, which makes rebuilding easier. Folder Export with M3U only covers local files.
Track Qobuz releases with a playlist. For releases you want to come back to, saving them to a playlist instead of adding them to your library keeps them out of your library count.
On deleting content instead: trimming your current library may lighten the load, but we can’t promise it will make ARC stable at this size. Running ARC on a fresh, considerably smaller database is the only option we can stand behind.