Skip to main content

Hello everyone,

This is my first time posting in the community—I hope I can explain my issue clearly. I've been using Sonos for a couple of years and I love it, but for the past week, I've been facing a problem I just can't solve.

My setup:

  • 1 Sonos Beam (Gen 2) connected to the TV

  • 2 Sonos One SL as rear speakers

  • Router: TP-Link Archer C7

  • My phone: Samsung Galaxy S22 with the latest version of Android

The problem:
The Sonos app on my Android phone suddenly can't find any of my speakers. It shows the message "Unable to connect to Sonos." The strange thing is that if a friend comes over, their iPhone connects without any problems and can control the entire system. The music continues playing if started from their phone, but I can't do anything from mine.

What I've already tried, with no success:

  • Restarting the router and waiting 5 minutes

  • Unplugging and replugging all Sonos speakers

  • Uninstalling and reinstalling the Sonos app on my Android phone

  • Clearing the app’s cache and data

  • Making sure the app has all necessary network and location permissions

  • Connecting my phone to both the 2.4GHz and 5GHz Wi-Fi networks

I'm starting to think it might be due to a recent Android update or something related to my phone's settings, but I'm not a network expert.

To keep this post from getting too long, I’ve collected all technical details (app version, Android version, network settings) along with a small diagnostic log I created using a network analysis app.

Has anyone experienced something similar? Are there any specific router or phone settings I should check?

Any help or suggestions would be greatly appreciated.

Thanks so much in advance!

Did you try unplugging the Sonos devices while you rebooted the router, or did you do that sequentially?

Have you tried temporarily wiring your Beam to your router?

Have you called call Sonos Support directly to discuss it, and if so, what did they say?

Are you willing to share these network settings with us?


Anything running on the Android that isn’t on the Apple? VPN, spam filter

 


Did you have another network? Is it net unique router?

In Samsung we have a Wi-Fi protection free and that changes the DNS and all passes by a filter, have you have it disabled? Also which Android version do you have? Because for me in the latest patches and versions of Android 14 there was some problems until I updated to Android 15, could be.


This is a very common and frustrating issue with Sonos speakers. The problem is almost always related to the network, and a few simple steps can often fix it.

 

Solution: Troubleshooting Steps

 

 

1. Reboot Everything (In Order)

 

The fastest way to fix most network issues is to refresh everything.

  • First, unplug your router from the power for one minute, then plug it back in.

  • Once the router is fully back online, unplug all your Sonos speakers for about 30 seconds and then plug them back in.

  • Finally, reboot your Android phone.

 

2. Check Your Network Connection

 

Make sure your Android phone is connected to the exact same Wi-Fi network as your speakers. If your network has a 2.4 GHz and a 5 GHz band with different names, ensure both your phone and speakers are on the same one. Also, make sure your phone isn't connected to a guest network or a VPN.

 

3. Reinstall the Sonos App

 

If the first two steps don't work, there might be a problem with the app itself.

  • Completely uninstall the Sonos app from your Android phone.

  • Reboot your phone again.

  • Reinstall the app from the Google Play Store and try to reconnect to your system.


It looks like your Sonos system is fine, since it works with other devices, so the issue is specific to your Android phone. Here’s what usually helps in these cases: Check Network Isolation Settings – Some routers block device-to-device communication (often called “AP Isolation” or “Client Isolation”). Make sure it’s disabled for your network. Assign a Static IP or Forget/Rejoin Network – On your Samsung S22, try forgetting the Wi-Fi network and reconnecting. If needed, assign a static IP in your router settings for the phone. Check Android Permissions & Battery Optimizations – Ensure the Sonos app has all permissions, and disable battery optimization for the app (Settings → Apps → Sonos → Battery → Optimize battery usage → Off). Update the Sonos App & Android OS – Make sure both are fully updated. Sometimes network discovery breaks after OS updates, and Sonos releases fixes in minor updates. Try Connecting via Ethernet/Bridge (if available) – If the Beam or a speaker is wired to the router, it helps the Android app find the speakers more reliably. Check Wi-Fi Frequency – If your router is dual-band, try forcing your phone to the same band that other working devices are on (usually 2.4GHz for Sonos). Sonos Diagnostics / Reboot – Use the Sonos app diagnostics tool to check for errors, and then reboot all devices after changing network settings. Key Insight: This is almost always an Android/phone-specific network discovery issue, not a problem with your Sonos speakers themselves. Following the steps above usually fixes it without needing to reset the speakers.


Sounds like a multicast discovery issue on Android. On your Galaxy, disable MAC randomization + Private DNS, then reconnect Wi-Fi. Also check router: turn off AP isolation and allow multicast/IGMP. That usually fixes it.


Try temporarily disabling 5GHz on your router. Maybe your Android is connecting to your router on a different frequency to your other devices, and some routers are too janky to handle that.


Forget WiFi on your Galaxy, reconnect, and be sure you’re on the same SSID as Sonos. In Android settings, give Sonos app Location + Local Network permissions. Turn off Private DNS or VPN if active. Reboot router, then power cycle Sonos speakers after router is fully up. Test with Beam wired to router — if it works, the problem is WiFi discovery (multicast/UPnP). On TP-Link router, enable IGMP/multicast support and disable client isolation. If still not working, contact Sonos support with a diagnostic — it’s a known issue with some Android builds blocking local network discovery.