The SoundSend App is Spinning/Won't Connect

The SoundSend App is Spinning/Won't Connect

SoundSend App Stuck on Loading Screen or “No Device Found”

If the SoundSend mobile app hangs on the loading screen or displays:

“No device found”

even though Bluetooth is enabled on your phone, this is usually caused by missing Bluetooth or location permissions on your mobile device.

Why This Happens

The SoundSend app communicates with the SoundSend puck using:

Bluetooth Low Energy (BLE)

Modern Android and iOS security settings can block BLE device scanning if the correct permissions are not enabled, preventing the app from detecting the SoundSend device.

How to Fix the Issue

Step 1 – Fully Close the App

Completely close the SoundSend app from your phone’s recent apps/background applications list.

Then reopen the app after checking permissions.

Android Devices

Enable Location Permissions

  1. Open:

    Settings

  2. Go to:

    Apps > WiSA SoundSend

  3. Select:

    Permissions

  4. Ensure the following are enabled:
  • Bluetooth
  • Nearby Devices (if available)
  • Location Services

Android requires Location Services for BLE device scanning, even when GPS location itself is not being used.

iPhone / iOS Devices

Enable Bluetooth & Local Network Permissions

  1. Open:

    Settings

  2. Scroll down to:

    WiSA SoundSend

  3. Ensure the following are enabled:
  • Bluetooth
  • Local Network Access

Step 2 – Reopen the App

After enabling permissions:

  1. Reopen the SoundSend app.
  2. Wait a few moments for device discovery.
  3. The SoundSend puck should now appear correctly.

Additional Troubleshooting Tips

If the app still cannot find the device:

  • Toggle Bluetooth off and back on
  • Restart your phone
  • Power cycle the SoundSend puck
  • Ensure the puck is powered and within range
  • Confirm no other device is actively controlling the SoundSend system

Common Symptoms

This fix is recommended if you experience:

  • Endless loading screen
  • “No device found” message
  • App unable to detect the puck
  • Bluetooth appears active but setup fails
  • Initial setup not progressing

Enabling the correct permissions resolves this issue in most cases.