Roon Remote 1528 crashes Samsung Fold upon reopening phone (ref#IDUFE6)

What’s happening?

· I am experiencing freezes or crashes

How can we help?

· I am experiencing freezes or crashes

Other options

· Other

Describe the issue

The latest version of the room remote for android 1528 crashes the Samsung Fold. It starts and works as expected. Once the phone screen is turned off and phone screen opens up, the phone will crash. The system UI is unresponsive, this happens always when reopening the phone. The phone has the latest Android version.

Describe your network setup

asus xt12 mesh

Hello @Christoph_Langenberg,

Thank you for reaching out to Roon support, and it’s great to see you back in our community!

Could you kindly clarify whether you’re experiencing the issue with the Roon app or the ARC app? In the meantime, let’s go through a few steps to ensure there’s nothing on your Samsung device that might be preventing the app from functioning properly.

1. Battery Optimization

Samsung’s battery management system can sometimes restrict background apps or network access:

  • Go to Settings > Apps > Roon ARC > Battery
  • Set to “Unrestricted” (avoid “Optimized” or “Restricted”)

2. App Permissions

Ensure that ARC has all necessary permissions:

  • Go to Settings > Apps > Roon ARC > Permissions
  • Allow Local Network, Storage, and Location (this is sometimes needed for local discovery)

3. Data Usage / Network Access

Make sure ARC has full network access:

  • Go to Settings > Apps > Roon ARC > Mobile Data & Wi-Fi
  • Ensure “Allow background data usage” and “Allow data usage while Data saver is on” are enabled

4. Device Care / App Protection

Samsung’s Device Care or App Protection features may limit ARC:

  • Go to Settings > Device Care > Memory and exclude ARC from auto-optimization
  • In Settings > Device Care > Battery > Background Usage Limits, make sure ARC is not on the sleeping/deep sleeping app list

5. App Security / Secure Folder

If you’re using Samsung Knox or Secure Folder, ensure ARC isn’t sandboxed or blocked.


Please let me know if any of these steps help resolve the issue, or if you’re still experiencing difficulties. I’m here to assist you further!

Thanks for the quick reply, it is not the room arc app. It is the roon app I use to remotely control my endpoints.
Everything worked smoothly before the latest update, and as long as the screen does not turn off, it is fine. I

Hi @Christoph_Langenberg,

Thanks for clarifying and for the clear reproduction steps — that’s very helpful. The next step is to take a closer look at your logs so we can better understand what’s causing the issue. Could you let us know the date and approximate time the most recent crash occurred? If that’s not possible, feel free to reproduce the crash again and then share the timestamp with us.

You mentioned the system UI becomes unresponsive — is this specifically happening when reopening the phone while using Roon, or does it occur more generally?

It only happens when I have Roon app open and running. It has never happened before, and only started with new update. The Samsung Software is UI7, android 15, latest version. When turning the screen of the phone on again, it is actually even difficult to reset it as the system UI starts in a loop again and again.

Last try I had 17:04 UTC+10 (Melbourne, Australia), thanks

Hi @Christoph_Langenberg,

We’ll try to reproduce this in-house on the same hardware/software combination - should we require additional information, we’ll post here, but the above should be sufficient for development to take action as necessary.

We can skip the reproduction if you’re willing to supply ADB-level logs, which should contain the fatal exception, rendering errors, or lifecycle resume issues that are causing this crash. This would require a few additional steps on your end, so only perform the following at your own willingness and convenience:

Connect a PC/Mac to your Android phone and install ADB (instructions are here (all platforms)). Then:

  1. Type adb shell in terminal
  2. Type logcat v (ref: Logcat command-line tool  |  Android Studio  |  Android Developers)
  3. Reproduce the problem and let terminal print logs for 3-5 more seconds
  4. Select output from the moment you started the reproduction of the bug till the very end
  5. Upload the log here:

https://workdrive.zohoexternal.com/collection/8i5239cc05950ac07456889838d9319545a82/external

We’ll watch for your response. Thank you!

Thanks again for your help. I have uploaded the log file. Hope that helps. I have left the phone cycle a couple of times through the process. I also installed the previous version of Roon, and it showed the same behaviour. I suspect a problem with the updated Samsung UI7 and Roon. Thanks

Hello @Christoph_Langenberg,

Thank you for uploading the files.

We’ve passed all the necessary information to the QA team and will provide an update here as soon as more information becomes available.

What’s happening?

· I am experiencing freezes or crashes

How can we help?

· I am experiencing freezes or crashes

Other options

· Other

Describe the issue

I use Roon version 2.5 (build 1528) on my Samsung galaxy S23+, and have for years. My phone's Android version recently updated to Android version 15, One UI version 7.0, and since then the phone crashes every time I have Roon running and try to unlock my phone (navigate from the lock screen to the home screen).

I can run Roon while my phone screen is on, but if my phone screen turns off and I need to unlock the phone, it crashes. I do not have this issue while any other media player (Roon Arc, Tidal, Qobuz, Audible, etc.).

Describe your network setup

I use Fios and have a VZPD CR1000A router. I do not have any range extenders or switches. My phone connects using wifi 6E

Hi @Christoph_Langenberg,

Thank you for your ongoing patience and for providing additional information. This item remains with the team for investigation at this time but we should have an update soon.

Please let us know if you’re willing to share an additional ADB logset - the more information we can have in-situ to compare our reproduction efforts, the better equipped development will be to pin this down in a single fix.

We’ll report back shortly!

Hi @af_gershwin,

Thank you for the report. The team is investigating a similar report with OneUI 7.0 here on a separate Samsung phone:

The team is investigating this crash report and will prepare a fix for release in an upcoming update. We can merge your report into the tracking thread, but if you’re willing to reproduce the issue on the affected phone, we’ll enable diagnostic logging to confirm you’re facing the same problem.

Thank you for your patience. We’ll report back shortly once we have more information.

Hi everyone,

If you haven’t already, please try changing the battery settings for Roon and let us know if this changes anything:

  • Go to Settings > Apps > Roon > Battery
  • Set to “Unrestricted” (avoid “Optimized” or “Restricted”)

I uploaded another logfile and I had changed the battery settings already, thanks again

Hi @daniel - this sounds like the exact same issue that @Christoph_Langenberg is having (we both have samsung phones running the same Android/UI/Roon versions, and both started experiencing the problem as soon as we updated to the newest Android/UI version). As they said, it is actually very difficult to restart the phone after trying to turn the screen on again, as the UI loops (screen turns off and on repeatedly). The only way I can get it to stop is by holding the side and volume down buttons for an extended period. I can try to supply ADB-level logs, but I’d prefer not to only because I already performed a factory reset (before figuring out that this likely a roon-related issue), and should that be necessary again I’d be stuck without the use of my phone for another extended period of time during the restore process. Please let me know if the logs provided by Cristoph are insufficient and/or you have been unable to reproduce the issue on your end. Thank you

To be clear, it is not an issue for everyone. I also have a Samsung, running on Adroid 15 and UI 7.0. I encounter, up till now, no issues. I know that this remark is not helping you any further, but just to say that is not a general fault. I hope for you that Roon Support is able to find the reason of your issue very fast.
Kind regards, Frank.

Have a Samsung Fold 6, same build, same Android. Only crashes if I start Roon with the phone open, turn off the screen, fold the phone, turn on the screen and watch it on my external screen. (Samsung Fold has two screens, the folded internal screen and the second screen on the outside)

If I start Roon in the closed position and keep it closed, turn off the screen, then turn on the screen, no crashes. Also if I have the phone in the open position and keep it open, turn off the screen, turn on the screen, no crashes. If I start Roon in the closed position, turn off screen, turn on screen and open the fold using the internal screen, no crashes but the screen is now the resolution of the outside screen. If I try to choose the full screen option with the outside screen resolution to full screen in open position the phone crashes.

So seems to be working for my needs, as I just don’t keep switching screens when using Roon.

Hi @af_gershwin / @Jdjung ,

Can you please let us know the exact local time + date when you next reproduce this crash?

@af_gershwin - Are the steps that you need to take to reproduce the same as @Jdjung mentioned, or are they different?

Thanks @Frank_M for confirming you don’t have this issue.

Hi @noris - per my last comment, I will not reproduce the crash again, as I will no longer run Roon on my phone until this is fixed. If you need additional data logging, beyond what @Christoph_Langenberg has provided, please let me know.

Also, no, the steps are not the same as what @Jdjung mentioned, as our phones are not the same, and my phone does not fold.

As I said, “I can run Roon while my phone screen is on, but if my phone screen turns off and I need to unlock the phone, it crashes.”

It then appears that problem is at least impacting the Samsung Fold 6 and Galaxy S23+ phones. It is not clear what phone @Frank_M has, but whatever phone he has seems not to be impacted.

Sure thing, just did it again. The crash is not my phone just the app stops playback when I bring the app back up and I just have to press the play button again. 4:53 pm, PST, May 9th, 2025. Not a big deal for me.

@af_gershwin
My phone is a Samsung S22 Note.
Kind regards, Frank.