Samsung Tab A 2019 just cant connect to Roon Core anymore, since updated to Android 10

Support
1

Core Machine (Operating system/System info/Roon build number)
Desktop PC Windows 10 / i5 2,67GHZ 16GB DDR/ Roon Server 1.7

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Wired network, using a TP Link Gigabit Switch

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Description Of Issue
Since I have updated (today) my Samsung Tab A 2019 with Android 10 i simply cant get the tablet connected to my Roon Core anymore. Previously i was using Android 9 and everything was ok.

I dont know what else to do. Need help.

Sheers
Ruben

3

Hi @Ruben_Sousa,

What kind of router are you using? What is it’s model/manufacturer?
Do you by any chance have an IGMP Snooping / IGMP Proxying setting on it you could try to toggle?

4

Hi Norris,

Everything was working fine while using Android 9 in the same Tablet. As soon as i updated the OS to Android 10 (automatic update from Samsung), it simply stopped connecting to Roon Server.

I haven´t changed nothing in my network settings. Just out of the blue, no more Roon Core connection through Samsung TAB A.

Iam using the same router as ever, supplied by my internet provider (optical fibre 500mbps/100mbps). You can check it out the router iam using: https://geektuga.ddns.net/gct/index.php/2018/09/06/4-dicas-avancadas-para-o-seu-fiber-gateway-meo/

Sheers
Ruben

5

Hi Norris,

It seems that there are some users with the same issue in the past. I did some research and found out that setting up Roon Core IP address, manually, could solve the problem. I´ve tried that and didnt work. So i saw that a user tried to put the subnet mask, 255.255.255.255 in the IP Address camp and out of the blue , the Samsung TAB connected to Roon´s Core.

So, until now, so far so good. Nevertheless you should try to understand better what may have been causing this issue. Everything was working fine until i updated to Android 10. And this issue only happens with my Samsung TAB A 2019. I have a Samsung Galaxy S20+ also with Android 10 and dont experience the same issue.

Sheers
Ruben

1 Like
6

Hi @Ruben_Sousa,

Happy to hear that the 255 workaround resolved the issue. It’s possible that multicast was not operating properly before, and Android 10 removed some of the multicast capabilities, which Roon was using to connect.

We do plan to improve our multicast implementation, but I can’t specify when exactly this will reach the front of the queue. In the meantime, I would suggest checking the router multicast settings and seeing if the IGMP suggestion I provided helps (or manually connecting via the 255 IP).

7

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.