Hi @Akella,
Thank you for taking the time to share your experience in such precise detail with the team.
We’ve taken your reports seriously and very much appreciate your candor and specificity. Reviewing diagnostics, we can see the clear story of your recent session in ARC during your second trial. Here are some thoughts the team wanted to pass along:
-
There was considerable memory pressure reported by the framework. While 7000 tracks is not an insignificant load for a phone, the stress on the RAM is not normal nor expected within ARC for this model. ARC Development is working seriously to overhaul and improve the current download implementation - what you experienced is a growing pain, the sharp expanding edge of ARC’s capabilities.
-
Logs seem to indicate that upon first redownloading, you encountered a database malfunction as a result of having ARC previously installed in an older build during your trial in November. This no doubt soured your experience right off the bat, but fortunately, it’s a known issue that will soon be history once work to overhaul ARC connectivity comes through the pipeline.
-
Background download functionality is something we’re working on, but we don’t have a timeline or any precise details of the implementation at this time. We recognize the enormous utility, particularly for large-library users and fans of USB DACs.
-
Bell Canada Home Hub and Gigahub users have a harder time than most; this gateway functionality is not intuitive for port forwarding and requires advanced bridging in some cases. I assume from your previous post that a manual rule resolved the connectivity issue. I suggest you leave the rule in place if you plan to try ARC again in the future.
Feel free to reach out if you have any questions.