What happens if you press the "Select a different Roon Server" button?
· I don't see Roon Server.
Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.
· No, the issue remains the same
Please select how you've connected your Roon Server to the internet
· Roon Server is connected by *Ethernet*
Have you checked your firewall settings to ensure that Roon is allowed through?
· Roon still won't connect even after checking this aspect
Have you verified that Roon Server is on the same subnet as your Remotes?
· My Remotes and Server are on the same subnet and I still can't connect
Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.
· I've reinstalled the Roon Remote but it did not help
What is the operating system of your Roon Server host machine?
· *Nucleus*
Select any of the following components that are present in your local network setup
· *Mesh networks*
You mentioned a mesh network in your setup. Certain common mesh networks might require slight reconfiguration to support Roon.
· None of the above
Describe the issue
Samsung Android s21 ultra phone is having trouble connecting to the nucleus one for the last few days, it usually lands on the waiting for the roon server page. Even when it does connect it's very sluggish getting to the homepage. This is only on Android, the roon remote on my MacBook pro is fine. Nothing has changed as far as my router and modem. I've tried restarting them, I've tried restarting the nucleus, restarting the phone, tried reinstalling the roon app.
Describe your network setup
I'm using a nighthawk mesh router and Docsis 3.1 eMTA cable modem as well as a Netgear ethernet switch ethernet switch
Thanks for writing in and for sharing your issue! We were able to review a fresh diagnostic report from your Roon Server, but weren’t able to capture detailed failures, unfortunately, mostly generic disconnections:
Warn: [rnet/RnetJsonClient] failed to connect Connection refused
Trace: [raatserver] [RaatServer SM-G998U @ 192.168.1.7:9200] client connection failed. Giving up
One place to investigate could be any firewall or third-party antivirus blockers on your router, as well as any QoS options from your Nighthawk to allocate network priority to your mobile device and Nucleus if possible.
Ultimately, we’d be able to see more details by investigating android logs, but those are a bit tricky to gather. I’ll share the necessary steps below - let me know if you’re able to complete them:
Connect your PC to Android phone and install ADB (instructions are here (all platforms)). Then:
Unfortunately none of this is working with the terminal. It did get to daemon started successfully but cant get beyond that. Phone didnt get prompt to allow usb debugging.
No issues with the router as far as QOS and there’s no third party antivirus on it. Roon Arc has been fine as well as Roon on my MacBook pro, it’s just the Android that is become very slow.
I’ve got 69 GB of free storage space. I’ve tried all the things that you recommended but still no change. App either very slow to load or doesn’t load at all.
I’m not sure what’s going on just a little over a week ago everything was fine. Was there a recent update?
I’m a beta tester so could it be a recent update.
Nothing has changed on my end as far as the network I even increased the network speed to 2 GB.
Okay so I uninstalled the Roon app and left the beta testing, then reinstalled and now its connecting without any problems. So something connected to the beta version?
From the diagnostic data on your account, we can see that your Roon server was running the production build 10 days ago:
10/18 04:05:15 Info: Starting RoonServer v2.55 (build 1559) production on linuxx64
You mentioned that you are a beta tester. Could you kindly clarify whether you have actively participated in the beta testing program and if any recent beta updates were installed on your system? Are you referring to the beta testing program only in the Play Stor,e according to this article, but your Roon Server was still on the production build?
This will help us better understand if the issue could be related to a beta build or if it’s coming from the production environment.
I was a beta tester from the Play store for the room remote. Once I left the beta test and reinstalled the app it works fine. I wasn’t part of the early access for the server.
Please note that the current setup may cause unexpected behavior, as the Beta version of the Android Roon app is designed to work only with the EA (Early Access) build of the Roon Server.
When the Android app is running a Beta build, it expects to communicate with a server that contains the same Early Access components. Running it against a production Roon Server can result in connection issues, missing features, or playback instability.
To ensure compatibility and proper functionality, please either:
Switch your Roon Server to the EA build, or
Install the production version of the Android app instead of the Beta one.
Let us know which option you prefer, and we’ll be happy to guide you through the process.
Thanks for the clarification. Everything’s fine now that I’ve installed the production version of Roon for Android.
Thank you Vadim and Benjamin for your help.