I have the same problem that my Android phone cannot connect with Roon Core installed on Synology NAS (Linux kernel) too. I have filled out the survey form yesterday, hope this my help Roon developer solve the issue earlier.
Below is my situation if you interest my case:
I use Synology DS1515+ NAS as storage of music file, I have different device to test the remote connection. I have two Android phone which version is 6.0.1 and 7.0, also have iPad iOS version 11.0.1. I have iMac, Macbook Pro on macOS Sierra and Surface Pro4 on Windows10.
If I use iMac as the Roon core, all device as Roon remote work fine, while I changed the Roon core to DS1515+ (same NAS of storage), all Roon remote work fine but only two Android phone fail to connect.
If I follow the survey form suggest to test disable the NAS Roon core frist, open the phone Roon remote apps waiting to connect then enable the NAS Roon core again, this moment the phone can connect the Core. Besides of that, just close the app and then re-open immediately will back to fail again. Iāve already disabled the battery optimization funcion.
There is no reason why it should not work. I have an MXQ pro box which connects reliably every time, as does my Pixel C which others are having problems with. But I presume it is an Android device with access to the Android market place and Roon loads from there OK. So, supported or not it ought to work at least some of the time. This should be a fixable problem.
Indeed. But without the help of the support it will be difficult for me to fix this problem.
As soon as I have a little time I will do some other tests.
Hereās another piece of troubleshooting information that may help.
When viewing the Coreās connected audio devices, my Pixel shows up as connected, even though the Pixel itself is perma-stuck on āWating for Remote Coreā¦ā
Again just to be clear, this problem only popped up on my Pixel after updating to 8.0.0. Before then I never had an issue.
So the Core and the Remote are definitely talking to one another, albeit a one way conversation at the moment.
Too bad.
Sorry to hear itās not working for you.
Would have beee nice to have stumbled across a general solution.
But I douted from the start that this was going be the caseā¦
Anybody else who found it a working solution?
Or is it just Bear FNF and me?
That again would be very unlikely, wouldnāt it?
@mike This whole issue is very mysterious. One thing Iād wish Roon would do is to release a version of the Android app that allow one to switch off the whole RAAT side that allows the core to stream to the remote device. My own investigation of logs several months ago made me feel that failure in the RAAT negotiation between core and Android remote was where the core decided the remote was AWOL, and so it would never talk with it again. Those of us focused on high quality sound donāt care about streaming to Android devices, anyway, only about using Android remotes to control play on other endpoints.
For whatever reason I had a week or two of no problems connecting my roon remote. But then I rebooted my router a couple of nights ago, and Iāve now returned to the same problem as before: I cannot connect my Pixel phone remote to my core (running on Fedora), unless I restart the core (systemctl restart roonserver.service). After restarting, I can connect to the core for a bit, and then at some point Iām unable to connect.
I do think itās interesting, as @anon55914447 noted, that the core can see the remote. Using a separate Mac as a roon client I see the same āNetworkedā device output that @anon55914447 sees. The Pixel device pops up in the Networked section when the Pixel tries to load the Roon app, which fails to connect. The Pixel device disappears as soon as I close the Pixel Roon remote app.
I updated roon core to the latest version. To my surprise today on my samsung galaxy tablet as well as my Meizu M5 smartphone, roon did connect!
If this is due to the updateā¦ thank you!. If it is something elseā¦ I still am a happy man.
We havenāt forgotten about this issue and we are still discussing it, but for now we have still never seen this happen in house, and a few theories posted here or discussed internally donāt seem to have panned out.
This theory, however, is interesting:
We are going to do some testing in this area, see if we can provoke some issues, and weāll follow up when we have some news.
Truly one of the more frustrating bugs ever, guys ā we (still) really appreciate everyoneās patience.
I am just breaking my head what changed in my setup. Actually nothing I can think off, or it must be that I deleted or dismanteled a lot of google services. What I know. a week ago I had trouble in connecting through my android devices and had to restart roonserver while the remote app was searchingā¦Now that isnāt necessairy strangely enough.
I have this problem too from my Android device. In linux I boot with the systemd service enabled. After boot roonserver is running without errors. However I cannot connect. Butā¦
if I restart roonserver after boot on the core computer, the android app will magically work. So to me it appears some sort of network problem. I will try to add a delay in the starting of systemd service.
I guess you are using audiolinux
Now I remember that I recently killed all audio services with the provided desktop button, before I did a system update. After the update I only used āstart roon server at bootā. I am fairly sure that after that I could use my remote apps again.
Not sure if this is useful for others, but Iāve found that I can re-establish the Android remote connection by turning off/on the wifi on the core machine.
The Android remote typically loses its connection sometime during playback: when I open the remote, it says āLost Connectionā and will not reconnect. Closing and re-opening the app does not help. Usually only a restart of the roon core will re-establish the remote connection.
However, when Iām unable to connect, turning off and on the wifi for the core will allow the remote to connect. My core machine runs networkmanager so I use nmcli radio wifi off, then nmcli radio wifi on. After the core wifi is back on, the Roon remote app will reconnect.
This is a helpful workaround for me because, at least for my setup, audio playback continues as normal during the entire process, which is obviously not the case when I have to restart the core.
I found that just hitting the āsaveā button on my ROCK/NUC settings screen helped the app reconnect. Donāt have to change anything just hit save.
But, since i enabled the WiFi this is not needed anymore. I also have ethernet connected to the NUC.
