Delayed Roon Startup on Android with Nucleus One (ref#1O4NYR)

Support
1

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· "Waiting for your Roon Server"

What happens if you press the "Select a different Roon Server" button?

· I don't see Roon Server.

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?

· *Nucleus*

Select any of the following components that are present in your local network setup

· None of the above

Describe the issue

Roon is delayed for a good 10 minutes before the app comes up on my two Android devices, but comes up right away on a windows laptop. Android worked fine when Roon server was on my old HP laptop PC, but I just bought the Nucleus One and it doesn't work with Android devices. I just requested to return the Nucleus since Android doesn't work. If someone can get it to work with Android, I'll keep it. I've been going around and around with my ISP thinking the issue is with my Calix Gigaspire U6 router. My ISP sent me this note an hour ago: Hey Jeff,

I heard back from the tech in Calix and he sent me the following message: “IGMP snooping is on by default on Calix RGs and they are able to handle multicast traffic over WiFi. If it works fine on the windows device which is connected to WiFi as well, then there is most likely an issue with the Android app/device. We can try to upgrade the RG to latest firmware to see if that helps, but otherwise I would point the subscriber to Roon support.”

I clarified for my tier 3 tech that you were using the windows computer wirelessly as well, and he agreed with what the Calix said after that. He was under the assumption that the Windows was connected with ethernet and that all wireless devices were having the same issue, but since it is isolated to the Android devices, they are both agreeing that issue is more likely to be on the Server side or the Android side.

My tier 3 tech said: “Oh, if Windows Computer is on wireless and working, that means all the knobs and switches to let Multicast and IGMP is already set correctly. It would be an Android issue. We don't have any mechanisms that can tell the difference between an Android vs a Windows computer. Even if we wanted to, we couldn't do it. “

I hope this information helps, I was really hoping it would be something we could just flip a switch and fix on our side, but it sounds like that is not the case.

Thank you,

Ty
Midwest Energy & Communications
Technical Solutions Agent
(Email and phone number redacted by staff)

Describe your network setup

Neither Android device can connect to my Nucleus One I just bought, both worked fine when I ran Roon Server on my old HP laptop. This product was advertised as "plug & play" but my experience is quite the opposite. It doesn't work with Android devices, so I just requested to return and get a full refund. If someone can get it to work with my Android devices, I'll keep it. My windows 11 old HP laptop works fine, but there's a delay of around 10 minutes for Android to find the server which is unacceptable. My ISP says it is a Roon server issue- there response is below: Hey Jeff, I heard back from the tech in Calix and he sent me the following message: “IGMP snooping is on by default on Calix RGs and they are able to handle multicast traffic over WiFi. If it works fine on the windows device which is connected to WiFi as well, then there is most likely an issue with the Android app/device. We can try to upgrade the RG to latest firmware to see if that helps, but otherwise I would point the subscriber to Roon support.” I clarified for my tier 3 tech that you were using the windows computer wirelessly as well, and he agreed with what the Calix said after that. He was under the assumption that the Windows was connected with ethernet and that all wireless devices were having the same issue, but since it is isolated to the Android devices, they are both agreeing that issue is more likely to be on the Server side or the Android side. My tier 3 tech said: “Oh, if Windows Computer is on wireless and working, that means all the knobs and switches to let Multicast and IGMP is already set correctly. It would be an Android issue. We don't have any mechanisms that can tell the difference between an Android vs a Windows computer. Even if we wanted to, we couldn't do it. “ I hope this information helps, I was really hoping it would be something we could just flip a switch and fix on our side, but it sounds like that is not the case. Thank you, (Email and phone number redacted by staff)

2

Hello @jeffreykweaver ,

Thanks for reaching out. Can you please let us know the exact local time + date when you next observe this issue, as well as which device model you reproduced the issue on? E.g: Opened Roon app on X device at 4:54PM on 12/5, loaded fully at 5:03PM.

Just to clarify, you are using the latest firmware on your router? It was not clear if you’ve tried upgrading it yet. The IGMP settings you mentioned may help, the router may not be able to tell the differnece, but the internal multicast settings of the device can be impacted, so it is worth a try to toggle the switch to see if it helps.

3

Giving this thread a quick bump @jeffreykweaver let us know if you’re able to run through the above, thank you!

4

I just installed a new router, a TP Link AXE7800 that Chat GPT indicated would work with Roon and Android devices. I had the exact same result as the Gigaspire U6. Windows connects fine but both Android Devices hung. With the new router, when I first launched Roon on Android, it showed my HP laptop PC as my server, it didn’t show the Nucleus One at all.

My ISP had a Calix tech analyze my traffic during error mode on Android and also looked at traffic with Windows, where Roon connected as normal. They came back today and indicated the Roon app is my issue.

Hey Jeff,

Mike from Calix finished analyzing the packets and had this to say:

“Hey Ty,

After looking at those captures, I am very confident that it is a Roon issue. Below are a few screenshots. In the first two are the working Windows device and the working android after the server was rebooted. You can see that I have highlighted a reply packet from the server. In the last screenshot, the broken phone, there is not reply from the server. This subscriber’s best course of action would be to engage Roon support.

Inline Image: (Salesforce)

Inline Image: (Salesforce)

Let me know if you have further questions. If not, I’ll go ahead and close this out as it is not an issue with the Calix system.

Regards,”

I’ll attach screenshots to the email so you can see what he’s talking about as well. I know you said that you were waiting for Roon’s reply on the issue last time we spoke, I’m hoping that they will be able to identify and fix the issue you are having. Thanks for all your patience and time and please feel free to reach out if you need any further assistance.

Thank you,

Ty

Midwest Energy & Communications

Technical Solutions Agent

1-800-492-5989

5

My ISP sent these 3 screen shots which show that Roon works with Windows and it works with Android right after a reboot of Nucleus. The 3rd screen shows Roon is broken with connecting to my Android Samsung S23 plus phone, just a few minutes after rebooting Nucleus. This proves that there is a bug with Roon software working with Android devices. Can this be fixed or should I return the Nucleus server and revert back to running Roon off my PC which had no issues with quickly connecting to Android devices? Thanks!

6

Just noticed, via Google, that I’m not alone with my frustrating experience with Roon Nucleus One not working with Android devices from Samsung. Has this been escalated to Roon leadership and is there an ETA on the fix? I’m heavily leaning towards returning my Nucleus One for a refund and reverting back to running it off my laptop PC which didn’t have issues connecting to my two Samsung devices.

Yes, many Roon users experience significant delays and connection issues with Android devices finding their Roon Core (like a Nucleus One), often due to Android’s network handling, firewall settings, or specific phone vendor issues, requiring troubleshooting like network restarts, firewall adjustments, or device-specific workarounds, though Apple devices usually connect fine.

Common Causes & Symptoms:

  • Delayed Discovery: Android apps often get stuck on “Waiting for Roon Server,” taking minutes or longer to connect, while iPads/PCs connect instantly on the same network.
  • Samsung Issues: Samsung phones are frequently cited as having problems due to how their OS handles network multicast for device discovery, affecting Roon and other apps.
  • Firewall/Antivirus Interference: OS firewalls or security software can block Roon’s discovery packets.
  • Network Glitches: Temporary network issues or router settings can cause connection failures.

Search the Roon Community for specific models (e.g., Galaxy S24) for targeted fixes, as users share solutions there.

The consensus is that it’s often a network/Android OS issue rather than just the Nucleus One, but it’s a widespread frustration.

7

Hello @jeffreykweaver,

Thank you for the update and for sharing those details.

Regarding the analysis performed by your ISP — could you please clarify where the Wireshark capture was taken?
Was it run on the Windows machine itself, or directly on your router/network device?

Regarding your comment below:

Yes, many Roon users experience significant delays and connection issues with Android devices finding their Roon Core…

I’d like to clarify that this isn’t a widespread issue affecting all Android devices. At the moment, we are investigating connection-related problems involving a small number of specific Android devices, primarily certain Samsung and Pixel phones/tablets. This is not representative of Android as a whole.

To help us determine whether your case aligns with the issue currently under investigation, we’ll need to review Android system logs captured at the time the problem occurs.

Please collect ADB logs as follows:

  1. Connect your Android device to a computer and install ADB
    (instructions for all platforms can be found here:
    How to install ADB on Windows, macOS, and Linux)
  2. Open a terminal/command prompt and run:
adb shell
  1. Then start log capture with:
logcat -v time
  1. Reproduce the issue on your Android device.
  2. Allow logging to continue for 3–5 seconds after the issue occurs.
  3. Copy the log output starting just before reproduction through the end of the issue.
  4. Upload the log file here and let us know once it’s done:
    https://workdrive.zohoexternal.com/collection/8i5239cc05950ac07456889838d9319545a82/external

Once we have these logs, we’ll be able to correlate them with our internal diagnostics and advise on next steps.

Thanks for your cooperation — we appreciate the detailed troubleshooting you’ve already done.

8

ISP worked with Calix (Router vendor) tech to collect data on my router when Roon works (with Windows) and when it is broken (with my Samsung S23 plus phone). Also, I ran the ADB tool and uploaded it to this site 2 days ago, have not heard any response to what was found from the large log file I uploaded. Do I really need to do it again, and can you validate someone is actually looking at what I uploaded? Thanks

9

Also, the comment about Many customers having issues with Android Samsung devices, that is what Google responds with when asking if others are experiencing similar issues. I strongly feel Roon marketing should be cautioning Android Samsung users to avoid further painful customer experiences. I invested in the Roon Nucleus One to have a better experience running Roon dedicated to the Nucleus vs. running on my PC laptop. It’s actually much worse running on Nucleus than on Android. Trying to validate if it can be fixed as if it remains broken, I’m returning the Nucleus.

10

Hello @jeffreykweaver

We are sorry to hear of your disappointment. Esentially from the screenshot you shared before both use cases looks broken.

We’ve reviewed the network capture from your system, and this does not indicate a faulty Nucleus.

The capture shows that the Nucleus is actively sending Roon Discovery and RATT UDP packets, which means the services on the Nucleus are running and functioning correctly. However, the expected discovery replies are not making it back. This pattern points to the network blocking or filtering the return multicast/broadcast UDP traffic, not to a failure of the Nucleus itself.

If the Nucleus were broken, we would not see consistent outbound discovery traffic at all. Since that traffic is present and correct, there is nothing on the Nucleus side that needs to be fixed — the behavior is consistent with a network-level restriction rather than a hardware or software fault.

Here is the screenshot for your reference how the networking works without any blocking

image
image1906×743 66.3 KB

11

I am returning my Nucleus Server, it’s a total nightmare experience and this product should not be sold to anyone using Samsung devices. Google AI confirms many users have the same issue. I bought a new router, installed it last night, and had the same issue. I’m done wasting time trying to get this to work. I’m extremely dissapointed and regret buying the Nucleus One.

12

Hi @jeffreykweaver,

We’re really sorry you’re running into this. One quick note of caution: AI tools can oftentimes give inaccurate or incomplete information about Roon, so we don’t recommend relying on them for technical details.

As @vadim mentioned, there are a few recent Android-related issues our team is actively investigating, but they aren’t widespread. We’re sorry this has affected you, and if you’d like to continue troubleshooting with us, we’re here and happy to help.

13

Benjamin, I’ve spent a ton of time, over a week, working with my ISP and sending tons of messages to this website. My ISP worked with a tech at the Router company (Calix) and they are telling me my issue is definitely with the Roon app. Everyone is pointing the finger, no one is solving the issue. I sent a logfile from the ADB process a couple of days ago, no one has given me any feedback on it. Was it readable? Did it show what was going on and provide more insight? Do I need to do this process again and load another file? And if I do, will I get a response back this time?

To reiterate, if I reboot the Nucleus, both Samsung devices (phone & tablet) will connect immediately. After a few minutes, it will no longer connect unless I reboot or wait up to 20 minutes. Windows connects all the time, right away. I’ve delted Roon off my PC and phone and reinstalled it with no change in the issue. I’ve powered down my PC and tried to launch Roon from both Android devices, still have the same issue.

I bought a new router (TP-Link AXE7800) and installed it last night. I configured it as suggested and still have the exact same issue. I returned the router to Amazon this morning, and put my U6 router back in place.

If I want to launch Roon off either Android handheld device, I need to reboot the Nucleus to be able to listen to my library or Qobuz through Roon. It’s almost like the Nucleus is going to sleep a couple of minutes after rebooting.

It’s been torture trying to figure out how to get Nucleus to consistently connect to either of my Samsung devices.

14

Another earlier note from Ty, my support contact at my ISP who was working closely with a tech at the Router company (Calix). I ended up working with Ty to do the packet capture which the Calix tech indicated proved my issue is with the Roon app.

Hi Jeff,

Just getting back into the office today after the weekend. I will go ahead and push that firmware update this morning. I also have another response from the Calix tech.

“Hey Ty,

I have checked existing and previous bug tickets. There is no “known issue” regarding our systems and Roon devices, or even our systems and multicast/mDNS over WLAN. My guess is that the android app is still trying to resolve the name of the old server that is no longer available which would explain why it works when the IP address is manually entered. Also, the only thing that has changed is Roon server, so I struggle to see this being an issue with the Calix RG.

And to be clear, all of the suggestions and assumptions in those AI outputs are hallucinations. Enabling IGMP proxying here doesn’t make sense as that is up stream and from what I understand, this connection between the device and server is a LAN layer 2 process. It is also not possible to even turn client isolation on a primary SSID which is the only one this subscriber has. Calix RGs have no way to permit or deny mDNS traffic over LAN/WLAN and no such thing as “Standard Mode Profile” exists for our systems.

With all that being said, we can get to the bottom of this. If the subscriber is willing, we can have them attempt the connection process with the Android device and the windows machine and get a packet capture during both. We can then compare to see what is really happening. For further evidence, we can also reconnect the old server and get the same captures to compare those as well.

Let me know how you would like to proceed.”

It sounds like we have someone who is willing to put the effort in to help us figure this out, I say we try doing some packet captures like he said and see what he can determine from the data. I’m going to verify how we go about getting the packet captures he’s talking about. I am unsure if that is something I do on my end or if that’s something you do on your end.

Thank you,

Ty

Midwest Energy & Communications

Technical Solutions Agent

1-800-492-5989

15

I just submitted another log file using ADB tool while having the wait on my S23 plus phone.

16

Thanks @jeffreykweaver,

Our team will be discussing your case further early next week, and we should have some concrete answers for you then. According to the documentation from Google, Android Version 10+ made a few key functions forbidden to access, which includes information about the device’s network state. It can only be accessed by system apps now. We’re looking closer into this and should have more information there as well.

Certainly, let us know if we can help with your other network techs in the meantime. :folded_hands:

17

Ok, hopefully the new log file I posted today will provide some clues to what is going on. My phone is running Android Version 16 and One UI version 8.0.
My tablet is running the same OS. My ISP (MEC) is saying my U6 router firmware is up to date. I recently updated my laptop to Windows 11, which again is working fine (and also connected via Wi-Fi). The Nucleus and my Oppo 205 are direct ethernet connected to my router.

18

Great news to report, both Samsung Android devices are working, they connect right away and I just rebooted my phone and it connected right away upon launching Roon. When Roon was hanging, I noticed it allowed me to enter the IP address of the Nucleus. After entering the IP, it appears to connect every time. Wish I had noticed and done this a week ago. Thank you for all the help and dealing with my PTSD frustration through the process of getting Nucleus up and running to replace running it on my old HP laptop PC.

Jeff

19

Hello @jeffreykweaver

Thank you for the update. We are happy to hear that the issue is resolved for you. Please enjoy your music.

20

Thanks, it has been rock solid with no delays. Achieved the goal of removing the PC going asleep.