I searched for information on setting up the Roon Remote software on Android but did not see anything about my issue.
I installed the Roon Core on my NUC last night. Did not got exactly as planned since it turned out I could not use my Dell laptop to control the Core. I reinstalled the full package on my NUC and proceeded to get things setup.
I’m mentioning this in case it relates to the issue I’m having with running Roon Remote on a Samsung Galaxy Tab S tablet.
My issue is that even though Roon Remote connected to my Core it shows that I have no Music and that I have not backed up my system. When I run the Roon application on my NUC it sees all the Music folders I have configured and I can play anything I want. I’ve also setup two backup tasks and manually backed up to both backup locations.
I find it hard to believe that each Roon Remote would have its own Core configuration so I’m guessing I missed something or did something wrong. Maybe I should not have installed the full package over the top of the server only package. I have uninstalled the Roon Remote software and reinstalled it but I’m still having the same issue.
Has anyone seen this? How should I proceed? So far I have not changed any settings from the Roon Remote.
Thanks for adding Support, still new at this and was not sure if I should have posted here or in the Support section.
I read the articles and found that my tablet is on the “known to work list” and that my Core was set to accept remote connections and that my Remote shows it is connected to my Core so I think my network settings are OK.
I disconnected from the Core and restarted the app and connected again and got the same result.
I’m going to wait a while before uninstalling the Core and reinstalling it just in case a solution is found.
I’ve moved your topic over to the support category so that we can give you some more focused attention. Can you confirm that when you open the Settings>General screen on your tablet and then “Disconnect” from the core, that on the following “Choose Your Roon Core” screen you only see one available option?
I’m assuming you guys have called it a day but it’s still early here on my side of the pond so I decided to reinstall and see what happened.
I refreshed both the backups I had setup, uninstalled all the Roon software on my NUC leaving the default checkbox to keep my configuration data, rebooted the NUC, downloaded the full 64 bit installer, installed and started Roon on the NUC.
I was not prompted to login, the app started and everything appeared as it was. I could see my music, backup sets and my RoPieee endpoint. I then started the Roon Remote on my tablet, connected to my core and this time it worked as expected and I saw all my music and was able to control playback to my RoPieee.
You had asked how many core options I saw when starting the Roon Remote and as before I only saw one option. However, before I uninstalled and reinstalled the name of the core I saw was TSJ-PLEX (the name of the NUC running both PLEX and the Roon Core) even though I had changed the Core Name to be NUC Core in Roon. Now the Roon Remote shows the updated name (NUC Core).
Thanks for your assistance. No idea what was wrong just glad it is working and now I can sit in my living room and listen using my tablet to control things instead of having to run upstairs.
Everything is working although not exactly the way I expected.
When I first installed Thursday night I installed the Roon Server (Core & Output) first and then installed Roon (Control, Core & Output) over the top of it when I found out I could not run Roon on my laptop due to Open GL issues. My mistake was not uninstalling Roon Server. When I uninstalled and reinstalled last night I installed Roon since I needed Control, Core & Output.
Before I went to bed last night I closed the Roon app on my NUC. When I got up this morning I could not connect to the server using the Remote app on my tablet. Took a few minutes but I figured out that as currently installed I need to have the Roon app running on the NUC. As long as it is then the Remote works as expected.
I’m pretty sure I now know that my original problem was due to the fact that when I installed Roon over Roon Server I ended up with two different installations, Roon Server running essentially un-configured since I had not connected a Remote to it and Roon which I configured on the NUC. When I stared the Remote on my tablet it was talking to the Roon Server instance which had not been configured. This is borne out by the fact that there is still a Startup entry for Roon Server on the NUC but there is no program for it to run so it does nothing. I added a Startup entry for Roon and rebooted and it started and my Remote was able to connect.
I was in a hurry Thursday night and probably did not read enough documentation to realize that Roon Server (Core & Output) and Roon ( Control, Core & Output ) are two completely different things. I assumed Roon installed Roon Server along with a Control program for it but it does not. Roon is everything wrapped in one program and has to be running all the time.