Ethernet connection between Google Home mesh router, Spectrum (telco ISP) modem and Intel NUC running Roon ROCK music server and Synology NAS. Wifi to Samsung Galaxy A71 5G cell phone
Connected Audio Devices
Ethernet to dCS Bartók streaming DAC [principal audio system, controlled by wifi from Windows 11 Home on Dell XPS PC] and Raspberry Pi streamer with Audioquest Dragonfly DAC [“background” music in various rooms of the house]
Number of Tracks in Library
19,181 tracks (on NAS and via Tidal) in library.
Description of Issue
On cell phone, whenever I move away from Roon as the active application, it locks up. In other words, when I return to the cell phone’s Roon app, it has lost control of the Roon server and won’t respond to commands. I have to quit the Roon app and start it again to regain control.
Hi John, thanks for the update. Mesh networks in my experience can cause a few problem for some software (including Roon) when the wireless device switches between nodes.
You don’t mention the number of nodes but the first check would be to switch off or disable any nodes other than the primary and check if the problem persists.
FTR.
There are also a number of reports (example) where the client is losing communication with the server which, I believe, is being investigated. I have also had the same issue with an iPad which I am still checking out.
Thanks, PixelPopper. The node idea sounds interesting, and I’ll check it out. I have to say Roon has worked without this problem for several years before this became an (admittedly minor) issue a few months ago.
It’s not his network he has the known issue with Roon remote as many many others have including me where it just hangs but remains active to users inputs but does nothing . Roon have replicated and working on a fix. It affects Android as well as iOS and is very intermittent in nature.
Bearing in mind that the OP commented that disabling one node resolved the problem once it is possible that there is a local networking issue and there has been insufficient local testing, so far, to eliminate it.
We can’t discount the fact that there is also a Remote Issue which might be the source of the problem but as yet local checks haven’t been fully completed.
