You can try the IP address option @Rugby mentioned, but just so that you are aware, using ISP-provided routers is not recommended as mentioned in our Networking Best Practices Guide as we have often seen ISP equipment not pass multicast traffic through properly.
Navigating to the WebUI doesn’t necessarily mean that multicast works as expected on your Android devices. These are two different types of communication, so it is still possible that there is a multicast issue somewhere along the line.
You can try entering the IP Address of the Core or `255.255.255.255 after pressing “Help” on the “Choose your Core” screen.
I’m not entirely sure since I haven’t had to use this work-around before. The more important thing to note here is if this workaround does indeed work, then it could point us in the right direction towards finding the root cause.
Do let me know if it works (even once), as this would be a great data point to have.
I had two incidents where my android roon remote failed to find the ROCK. The first time i put in 192.168.1.163. Didn’t work, but honestly i was rushed. The 2nd time i used 255.x4. This appeared to work, but then, sometimes it just works anyway after a small, or huge, delay. I will continue to report back. Even odder, it began by saying “you must be connected to a network”. Meanwhile Silk is loading pages and Outlook emails – so obviously it WAS connected to a wifi network. Still looks like a Roon remote for android networking bug either internal or in how it communicates with the android stack.
I’ll try to test it, but i doubt we will learn anything. The reason is 1) its inconsistent so it wont prove much, and 2) once it locks onto a server it tends to be fine, until , well, i dont know what the trigger is. but it will work fine for hours. But I’ll test the hard start this morning. In fact I will:
a) try it before hard-restart of the app (not of the android)
Thanks for doing that test, but I don’t think I’ll provide the necessary info. The test I was referring to was:
Next time you are in the state where the Roon App can’t discover the Core automatically, please try force-closing and opening the Roon app again (without specifying the manual IP). If you reboot just the Roon app, does that help you get out of this state and connected to the Core again?
Wait for the issue to re-occur when you can’t access the Roon Core via the Android Roon app
Exit out of the Android Roon app and force quit it, Amazon provides these instructions on how to force-quit an app:
To close apps, select the square icon in the bottom of the screen to show all open apps. Select the ‘X’ in the top right of each one to close.
Open the Android Roon app once more
Verify if you still have issues connecting with the Android App being the only variable that as changed
I was not aware you previously tried this. Have you been making sure to force-quit the app and start it again, or have you just been going to the home screen and opening it once more (without quitting it initially)?
yes to all. That’s exactly what i did. Swipe right and click the “X” are the same function. I often have to force quit it several times and maybe cycle the android. I can continue to try this now that i have forced it to 255.x4.
Again this NEVER EVER happens on MacOS (X.11,12,13), iOS (latest) or windows 10.
And other android apps work fine. (Firefox, Silk, Outlook)
OK. It did it again. I had put in “255.255.255.255” as the Ip address, and all was well for a while. Eventually it simply would not find the Roon core. Force-quit. No good. Put in 255x4 zgain. No good. Went to settings and changed to a different SSID (AP, on the same subnet/router/DHCP pool). With that it worked normally. I will add that nearly every time i wake up the android remote, the Roon remote app says “no WiFi connection, you must connect to the same network as your Roon core”. Then, after 20 seconds or so it suddenly connects. Again, i emphasize this NEVER happens with other apps on the same android device. Hope this info is helpful.