Roon ARC not working on Samsung Galaxy Flip 7 (ref#DDT8UE) [Ticket in]

What’s happening?

· I'm having trouble with Roon ARC

What best describes your issue with ARC

· I can't log into ARC but I can log into Roon

How can we help?

· None of the above

Other options

· My Roon software won't start up

Describe the issue

I have a new Samsung Galaxy Flip 7, two weeks old. Everything i use is working except for Roon ARC, and i use a lot of home security and streaming services. I have followed steps via internet searches to solve the issue re data usage setting, app permissions as far as i can with no success. Also followed steps in removing app and reinstalled rebooted etc. Roon ARC works fine on my iPad tethered to my phone so there is no issue with Roon ARC settings and access. All i get on the phone is the ARC splash screen and not even getting to the sign in screen, wifi disabled. Please help!

Describe your network setup

As indicated, Roon ARC works fine on my iPad so there are no network related issues. My Galaxy Flip 7 phone contract is with Sky who i believe use o2 mobile 4/5g networks. Phone is using Android 16, one UI v8.0

Hi @Andrew_Woods,

Thanks for your detailed report!

We already have an active ticket open with our R&D team regarding this specific behavior. At the moment, no additional information is needed from your side.

We’ll go ahead and close this thread for now, and we’ll reach back out once further details or updates become available.

Thank you again for your patience and for taking the time to report this!

Hi @Andrew_Woods,

Our QA team has asked us to request you to reproduce the event and share ADB logs from the affected phone, if you’re willing. This will help expedite their investigation.

Here are instructions you can use to capture the crash in ADB logs and upload them for our team to inspect. This process requires about 5-10 minutes.

First, connect your PC to the Android phone and install ADB (instructions are here (all platforms)). Then:

  1. Open the Terminal and type adb shell
  2. Type logcat v (ref: Logcat command-line tool  |  Android Studio  |  Android Developers)
  3. Reproduce the problem and then let Terminal print logs for an additional 3-5 more seconds
  4. Save the log output from the moment you started the reproduction of the bug till the very end
  5. Upload the log here and give us a ping:

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

Thank you for your help and your ongoing patience.