Hi @benjamin
Arc is working good again so far.
Only the Android Remote App at home needs a few times to start properly.
The phone and tablet app seem to go to sleep more and take some time to connect again, very similar to the initial connection when you start the Roon client on Android.
Hello @Gernot_Poeltl ,
Glad to hear that ARC is still working as expected.
I wonder, does the Android remote also have the same issue on Windows as well if it is temporarily used as the Roon Server? Or does the issue only occur with ROCK?
My Fire HD 8 Plus tablet started working again today 
It hasn’t worked for about the past week. My other 2 Fire tablets were never impacted (different generations).
Hi @noris
I used the Win 11 PC for my Roon Server and tested to open the Android App for 30 times. It worked fine and fast every single time. Then I made a reboot of the Win PC and tried again 30 times. Successfully.
After that I switched back to my ROCK with my last backup. I tried also to start the app 30 times. Worked fine but not as fast as on the Win PC. Then I made a Reboot on the ROCK. Starting two times successfully again. On third time it failed again and the troubles are like before.
I started with my tests at 03:28 PM 2026/02/27 MEZ if you want to have a look in my logfiles.
Win PC and ROCK are on the same switch.
Hello @Gernot_Poeltl
Thank you for the additional information and for trying those steps.
I’ve looked at the diagnostic logs from your Android device, and we found the exact reason why it cannot connect. The Android app is failing to discover your ROCK locally. Instead, it is relying on “Internet Discovery” and finding your router’s external public IP address (93.xx.xx.xx) rather than your local IP (192.168.xxx.x).
Because it’s trying to connect via the external IP route, the connection is being blocked or reset by the router (which explains the Connection reset by peer errors we saw on the server side).
This means that Multicast traffic (which Roon uses to discover devices on the local network) is being blocked between your Wi-Fi (where the tablet is) and your Ethernet (where the ROCK is).
Here is how we can fix this:
- Fritz!Box Wi-Fi Isolation: Please log in to your Fritz!Box settings. Go to Wi-Fi > Security and ensure that the option “The active wireless devices displayed below may communicate with each other” (Die angezeigten WLAN-Geräte dürfen untereinander kommunizieren) is checked/enabled. Also, verify that the tablet is connected to your main Wi-Fi, not the “Guest” network.
- Active VPNs or Ad-Blockers: In the previous server logs, we noticed that
Tailscaleis running on your ROCK. Do you have Tailscale, a VPN, or an Ad-blocker (like AdGuard or Blokada) running on your Android devices? If so, please turn them off completely on the Android tablet. These apps create a network tunnel that breaks local Multicast discovery. - D-Link Switch IGMP Snooping: Some unmanaged multi-gigabit switches drop multicast traffic across ports. As a temporary test, please bypass the D-Link switch and plug your Asus NUC ROCK directly into the LAN port of the Fritz!Box. Does the Android device find it immediately?
Let me know how the test directly into the Fritz!Box goes!
Hello @vadim
“The active wireless devices displayed below may communicate with each other” was enabled.
I have no active VPNs or Ad-Blockers on my Devices.
You said Tailscale is running on my ROCK, but I’am not signed in. Can you please tell me how to deactivate/deinstall Tailscale. I didn’t find an option. I deleted now all devices on the tailscale homepage. I remember I only tried tailscale a long time ago but never used it.
I connected my ROCK directly to the Router without success. It was at 2:43 MEZ 2026/03/08. In this case this was a very simple network configuration. Only ROCK and Hue-Bridge was connected to the Router.
So maybe Tailscale is the problem? Please doublecheck if I’am connected to tailscale now. As I mentioned before, I am not signed in with my ROCK and have no Tailscale App on my devices. Also i deleted all devices on the Tailscale website. Is there any other option?
Hi @Gernot_Poeltl,
Thank you for your post and for your diligent troubleshooting.
The Tailscale interface won’t have any affect on network discovery and if you’re signed out of Tailscale, it’s effectively inactive.
We’ve reviewed logs thoroughly for both the ROCK and the Android 13 tablet. Here’s what we can confirm:
-
Both the ROCK and the tablet advertise themselves correctly over mDNS
-
The ROCK and the tablet receive these announcements from one another without issue
-
The tablet briefly connects to the ROCK but is almost immediately disconnected.
-
Steps 1-3 repeat in a pattern
Nothing indicates the network isn’t handling traffic correctly. Something is severing Roon’s access to the network interface on the phone shortly after it connects to the broker.
There are really three possibilities here, and they may be intertwined to exacerbate the behavior.
The most likely possibility is aggressive battery optimization with Android 13 tablets. This will be a factor whenever the app is backgrounded. Even if you’ve configured your Android battery settings to avoid energy-saving, backgrounding Roon on this tablet can cause Android 13 to impose a ceiling on Roon’s network activity. When the app connects to your ROCK and begins receiving data, Android terminates its access to the network to save energy. The only real solution here is to keep the app foregrounded in the app.
An unlikely possibility that is still worth mentioning: the tablet might be switching between the 2.4GHz and 5.0GHz, which is why we recommend disabling band steering or forcing the network to a single band. You mentioned you’ve already tested for this.
The last possibility would involve MAC randomization. In your tablet WiFi Settings, look for an option under “Advanced” to set “device MAC” instead of “randomized MAC.”
We’ll watch for your response and proceed from there. Thank you!
Hi @connor
I will try to keep the APP foregrounded.
Jump between 2.4 and 5GHz isn’t possible, because my Router is set to “5GHz only” since a few years.
I changed WIFI settings to “device MAC”.
But no positive changes so far…
I also want to tell you: I am using the same Tablet since I started with Roon (09/2022) without any issues till February 2026. I builded up my ROCK in the end of 2024. If this are useful informations. Same troubles are on my Pixel Phone with Android 16. But that’s not so annoying to me, because in most cases i use the tablet for Roon services.
1 Like
Hello @Gernot_Poeltl
Connect your PC to an Android tablet and install ADB (instructions are here (all platforms)). Then:
- Type adb shell in the terminal
- Type logcat v (ref: http://developer.android.com/tools/help/logcat.html)
- Reproduce the problem and let the terminal print logs for 3-5 more seconds
- Select output from the moment you started reproducing the bug till the very end
- Upload the log here and let us know once you have done so:
https://workdrive.zohoexternal.com/collection/8i5239cc05950ac07456889838d9319545a82/external
I am sorry to say that I have the same problem, and since today I can’t find any workaround to connect to my Rock Server via Android. iPad, ARC, and Windows work fine.
None of my three Galaxy phones, all different versions up to Android 16, work with Roon anymore, and neither does an Amazon Fire tablet.
All router settings are configured exactly as recommended; the Speedport Smart 4 supports IGMPv3. All previously recommended settings are configured for the respective devices, with no use. Since today, I can’t connect to my Rock Server at all, no matter what I try.
iPad and Windows work fine. It’s very inconvenient. I can’t easily carry my iPad or laptop around the house all the time, and am I supposed to buy an iPhone just for this?
Could the problem described here possibly be related to this other case?
I have no idea what changed and what caused it:
Since this morning everything works again, flawlessly and smoothly like before. All four Android devices connect to the server immediately and are ready to use. I’m very happy and hope it stays that way. 
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.