Please try to restart your Roon Server by closing the Roon app in the taskbar or rebooting your Roon Server machine.
· No, the issue remains the same
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
· None of the above
Describe the issue
When trying to connect my Android phone to Nucleus and we are on the same subject, I can see that during scan alot of ip addresses are being scanned but not my subnet er both reside on.
Your screenshot shows the term “Outbound” also. So it might be a snippet from your firewall logging outbound traffic (only – nothing else to expect). Your local network is local though and so not outbound – in fact does your router / firewall not get involved handling internal traffic in the same subnet.
And many others that face the same issue wrote that it finds the server even without, you just have to wait a long time for it to happen. You provided a picture with the term “Outbound” on it as evidence. I just commented on your picture and why your subnet doesn’t show there (why it doesn’t do as evidence, or at least requires a good explanation why your subnet should show there).
PS: The issue with Android and the workaround are a “thing” already since at least 2018. And not everyone is affected by the issue – back then as well as now and in-between.
We wanted to ping this thread once more before it automatically closed due to inactivity.
Let’s set aside the network diagnostics and traffic analysis for a moment. What is the precise symptom you encounter in the Roon app on your Android remote? Does this occur when you wake the phone after having had the Roon app backgrounded?
Roon development is working on more graceful handling of Android’s network prioritization after wake. Try ensuring that Roon and ARC have no restrictions in the battery saving settings on this phone. Ensure background activity is enabled.
You restart RoonServer to initiate a discovery cycle if you’re still having trouble connecting. There is an additional workaround involving assigning the local broadcast IP (255.255.255.255) in the thread shared above.
This thread will close without a response, but please let us know if we can assist further. Thanks!
Manually entering in the ip for the nucleus running roon, works. But it should also work without manually typing in the ip.
So the question asked, is why is roon client on my Android not scanning the local subnet my Android phone is on, that is the same the roon server is on.
Also another issue I experienced is that if the internet connection goes down, there is no way to find Roon on the local network, to stream local music. That also I find very strange.
