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?
· *Linux Server* (Ubuntu, Fedora, ArcLinux...)
Select any of the following components that are present in your local network setup
· *Antivirus* *software *installed on RoonServer _or _Roon Remotes
You mentioned antivirus software. Please select the specific Antivirus you have from the list below
· Avast
Click below for next steps with a Avast Antivirus
· I still need help.
Describe the issue
After upgrading a phone (Google Pixel 6) and a tablet (Google Pixel Tablet) to Android 16, the Roon Client on those devices will not automatically connect to the Roon Server.
Other devices (including other Android phones still on Android 15 and earlier continue to work fine. The affected devices had no issues prior to the Android upgrade.
On the affected devices, selecting "Need help finding your Roon Server?", entering the ip address of the Roon server and then selecting "Scan" finds the Roon Server and allows me to connect to it. Thereafter, the Roon Remote on the Android 16 device works fine - even after force stopping the Roon app or rebooting the phone.
Clearing the Roon App storage on the Android 16 devices cause the problem situation and the resolution is the same.
Edit: it now appears that it is Android related and not just Android 16.
Describe your network setup
Opnsense router connected to ISP ONT and a series of 2.5Gb/s switchs. All devices other than mobile phones and tables are connected by wired ethernet. No Mesh Wifi is employed. Wifi is provided by a single ASUS RT-BE88U router configured in access point mode.
Thank you for the detailed report and for reaching out to Roon Support.
It worth mentioning that I am also unable to reproduce the same on OnePlus 13 running Android 16
Just to clarify before we proceed further:
Is this issue something you only need to resolve once per device (after the upgrade or storage clear), or do you have to manually enter the Core IP repeatedly?
Does the issue recur daily, after device restarts, or only after clearing app storage?
Just to better understand the situation—could you please share the reason or purpose for clearing the storage of the Roon app on your Android 16 devices? Was this part of troubleshooting, or do you do it regularly for other reasons?
I initially thought so - but, having just gone out of range of my WiFi network (so my phone switched to a cellular connection) and then returned home so it reconnected to WiFi, I found the same issue recurred. By contrast, forcing the switch to cellular and back to WiFi by turning the phones WiFi off does not cause the issue to recur.
I shall monitor this further and report back.
I have only installed android 16 last night and only subsequently tried to use the devices for Roon this morning so I can’t comment on ‘daily’.
The two device restarts that I have done as part of troubleshooting did not cause the issue to recur.
Clearing app storage always causes the issue to recur - as does uninstalling and re-installing the Roon app.
This was purely part of troubleshooting. I never do this on a ‘working’ app - but it is one of my first ports of call when diagnosing problems with an app (not quite as intrusive as a uninstall/re-install but has largely the same effect).
As an aside, Roon ARC, connected by WiFi, is able to connect as normal. Even disconnecting from the Roon server and then re-connecting does not cause issues (other than losing all downloads).
I don’t use a VPN when at home. I have wireguard installed on the phone but the one configured tunnel is disabled.
I just wanted to let you know, that I am facing exactly the same issues. 2x Android 16 Phones, and 1x Android 14 on a tablet. I have two windows machines running great as remote, strangely. Server is a Intel NUC i built by myself, 7 years ago, ran fine - mostly
As an experiment, I factory reset my Google Pixel Tablet (which is used for relatively little and can more easily be re-configued) and, without restoring apps/data from backup, I performed the initial setup of the tablet. I did nothing apart from connecting to WiFi, logging in to my google account and then installing Roon.
The issue persisted. On starting the Roon App, it did not initially find the Roon Server. If I scan the Roon Server ip address, then the Roon Server is identified immediately.
However, as part of my repeat testing, I cleared the app data (as I had done serveral times on my phone) and then tried to restart Roon. This time, before I could do the manual ip address scan, I was interrupted and, on returning to my tablet, I found that it had discovered the server.
Further experimenting appears to suggest that the server discover does work but it takes a whole minute or more.
Having discovered this, I went back to my phone and repeated the same experiment with the same result - The Roon app does eventually find the server but it takes a minute or more to do so.
Prior to installing Android 16, I have never noticed any significant delay so this does appear to be something new in relation to Android 16.
As an experiment, I used the Dell 2.5Gbps USB ethernet adaptor that I use for my laptop on my tablet instead of using WiFi. This exhibited exactly the same issue. My laptop, when used as a Roon Remote, does not suffer this issue.
I also, connected my laptop using WiFi - something I don’t normally do at home - and that continued to work without issue - even after disconnecting the Roon Client from the server and then restarting the App.
Consequently, I do not believe that this issue is caused by anything related to WiFi.
I have been wondering if it is something to do with the Android changes for ‘Local Network Protection’ as described at:
Scroll down to the ‘Privacy’ section at the end (for some reason, attempting to create a direct link results in a link to a japanese language version of the web page )
Unlikely as Roon obviously has network access. And still no such issue on my Pixel 8a so unlikely to be a (high level) OS issue at all. Maybe driver (and thus device) specific issue?
Still the same after the android 16 install/restart. I haven’t had this problem ever before and there have been no other changes to my system. Restarted Roon server and network connections. Any help would be appreciated.
I raised this issue and my issue has not been fixed. How come there is a reply marked as a solution? I have cleared the ‘solution’ flag.
In addition my wife’s Pixel 7, still on Android 15 has now started exhibiting the same issue. Waiting for much more than a minute did not result in the phone auto connecting. I had to do the explicit ip address scan.
On the plus side, my phone, that I connected yesterday still connects OK.
I have no idea what is going on. My wife’s phone was fine until yesterday. I did notice that her phone had the June security update installed but I don’t know exactly when that was installed.
I did run wireshark on my laptop yesterday when connected to WiFi and I could see plenty of traffic from both the phone and the Roon Server addressed to ip addresses within the multicast address range (224.0.0.0/4) - IGMP, MDNS, SSDP and other protocols - so this does not appear to be a network issue but rather an Android issue - and not necessarily, as I thought earlier, an Android 16 specific issue.
I may also have the issue on a Lenovo Tablet (P11Pro I think) running Android 11. The connection on this device does eventually work - but it takes a lot longer than it should.
)