At this point we would like to ask you to switch your phone to 60 HZ refresh rate for test purpose and try to use Roon ARC app again and check whether it still heats.
Let us know please your findings once you have tested it.
We have a few tests we’d like you to perform in the app that will isolate ARC’s background processes on Android to pinpoint the resource demand.
Our team has activated granular logging on the backend, so we’ll gather all we need if you can simply share a timestamp of when you performed these tests.
First up, at your convenience, please simply close ARC and clear the cache before reopening.
Go to Settings > Apps. Select the ARC app. Tap on “Storage & Cache” and choose “Clear cache”. Open ARC again.
Hi there, cache cleared, ARC opened, let it sit untouched until it finished loading and fetching covers and last changes, then closed the app to the home screen. Didn’t force quit it.
Thank you! We’ve captured relevant logs and passed them to the developers.
As a second test, please add at least 10 songs of mixed bit-depths and/or sample rates to the queue in ARC and play to any endpoint. Background the app during playback and keep other apps closed on the phone.
This second test should be all we need to reproduce the symptom precisely internally.
Hi there, I`ve done so, as instructed. The playback is currently running, my phone speaker as endpoint. App is backgrounded, screen is off. All other apps are closed and removed from memory.
Added 11 songs ranging from 44.1 to 192khz and 16-24bit depth.
Start time; 22:04 CEST, end approximately 22:45 CEST.
We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.
You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.
Thanks for performing that test, we have added this info to the investigation ticket. The ticket has been submitted for developer review, meaning that this may take some time to be reviewed.
There aren’t any additional details needed at this time, so we will go ahead and close the thread for the time being, and if any other questions arise after the developers have reviewed the case, we will re-open the thread and reach out once more.
Thanks again for your report, and thank you in advance for your patience as the ticket progresses through the development queue for review.