I'm still experiencing a persistent issue with Roon Remote on my Samsung S25 Ultra, even after installing your latest update.
When using Roon Ready to stream to my dCS DAC, the phone becomes unresponsive or crashes upon waking from sleep. This typically happens when the screen has been off for some time, and I try to unlock the phone. The device freezes or restarts. This does not occur when using AirPlay as the streaming method — only with Roon Ready.
I've already tried the following steps:
Disabled battery optimization for Roon
Allowed background data and unrestricted background activity
Cleared cache and reinstalled the app
Restarted the device
Nothing has resolved the issue. It appears to be related specifically to Roon Remote running in the background with RAAT activity.
Please let me know if this is a known issue or if you need any device logs or further information to help resolve it.
Thanks for reaching out to us to ask about this issue and for providing a detailed description of what’s going on. That is much appreciated!
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
Yes, that thread exactly describes the same issue I’m experiencing on my Samsung S25 Ultra. So it does seem related – the crash happens when Roon Remote is in the background and the phone wakes up, while using Roon Ready.
If you could please bring the Roon mobile app back online and connect to your network, we’ll enable a fresh diagnostic report to share with our development team to help investigate further.
I restarted the Roon Remote app and connected it to the network, as requested, so that diagnostics can be collected. However, the crash still happens exactly as described earlier.
Please keep the thread open while the issue is being investigated.
Sorry about closing the thread early. Your logs have been added to the developer ticket tracking this issue, and we’re continuing to investigate. As soon as we have an update from the team, we’ll follow up with you here. Thanks again for your patience!