Fix Your Apps. Keep Going.

Nearby Share Not Working on Android? 6 Fixes (2026)

October 24, 2026

You open a photo, tap Share, pick Nearby Share — and the other phone never shows up in the list. Or the transfer starts and then dies halfway. Nearby Share (now rebranded as Quick Share on Samsung and newer Pixels) is supposed to be Android's answer to AirDrop, but it depends on a small stack of radios and settings all agreeing at once. When one of them is off, transfers fail silently, with no useful error.

The six fixes below go in the order they resolve the problem most often: visibility and the basic radios first, the deeper Google Play Services repairs last. A few of these need doing on both phones — the sender and the receiver — because Nearby Share is a conversation between two devices, and one misconfigured side breaks the whole exchange. This guide covers Android 10 through 14.

Nearby Share not working on Android — phones not discovering each other during file transfer

Quick Answer

Nearby Share fails most often because device visibility is off or Bluetooth/Location is disabled on one of the two phones. Turn Nearby Share on, set visibility to Everyone (temporarily), enable Bluetooth and Location on both devices, and keep them close and unlocked. If that fails, clear the Google Play Services cache.

Fix 1: Turn On Nearby Share and Set Visibility to Everyone

The single most common reason two phones cannot find each other: one of them is invisible. Nearby Share has a visibility setting — Everyone, Contacts, or Hidden — and if it is set to Contacts while the other device is signed in to a different account (or not in your contacts), discovery just fails with no explanation.

  1. On both phones, open Settings → Connected devices → Connection preferences → Nearby Share. (On Samsung phones the feature is called Quick Share: Settings → Connected devices → Quick Share.)
  2. Make sure the main toggle is ON on both devices, and complete the quick setup with a Google account if it asks.
  3. Tap Device visibility and choose Everyone — at least while you are testing. You can switch back to Contacts afterward.
  4. Check the Device name shown here is recognizable; the receiving phone appears under this name in the sender's list.
  5. Try the transfer again. If it works, the culprit was visibility all along.

Turn on Nearby Share and set device visibility to Everyone to fix discovery problems

Fix 2: Turn On Bluetooth and Location

Nearby Share uses Bluetooth for the initial handshake and Location services for scanning. The transfer itself goes over Wi-Fi Direct, but if Bluetooth or Location is off, the two phones never start talking. This needs to be true on both devices — one side with Bluetooth off is enough to break discovery.

  1. On both phones, swipe down twice from the top to open full Quick Settings and confirm Bluetooth is on.
  2. Confirm Location is also on. On Android 12 and newer, you can use approximate location — Nearby Share does not need precise GPS.
  3. Turn on Wi-Fi on both phones. You do not need to be on the same Wi-Fi network — Wi-Fi just needs to be enabled so Wi-Fi Direct can work.
  4. Make sure Airplane mode is off. Toggling it on for 10 seconds and back off is also a decent way to reset all three radios at once.
  5. Retry the share. If the other phone appears now, one of the radios was the blocker.

Fix 3: Keep Both Devices Close, Unlocked, and Awake

Bluetooth discovery is short-range and picky. Phones across a room, one of them locked in a pocket, or a screen that just went to sleep — any of these can make a device vanish from the list or drop a transfer halfway through.

  1. Bring the two phones within about a meter of each other (arm's length is ideal).
  2. Unlock both phones and keep the screens on during the whole transfer.
  3. On the receiving phone, leave the Nearby Share / Quick Share screen open while the sender initiates.
  4. If the transfer is large, do not let either screen sleep — tap the screen occasionally or temporarily set the screen timeout longer (Settings → Display → Screen timeout).

Fix 4: Turn Off VPN and Data Saver

VPNs reroute your traffic off the local network, and Nearby Share's discovery handshake expects both phones on the same local network space. Data Saver, meanwhile, can throttle or block the background connections the transfer needs. Either one can turn a working feature into a silent failure.

  1. On both phones, disconnect any VPN: Settings → Network & internet → VPN (Samsung: Settings → Connections → More connection settings → VPN).
  2. Check Data Saver: Pixel: Settings → Network & internet → Data Saver → Off. Samsung: Settings → Connections → Data usage → Data saver → Off. Xiaomi: Settings → SIM cards & mobile networks → Data saver → Off.
  3. If Data Saver must stay on, add Google Play Services to its unrestricted list where the option exists.
  4. Try the transfer with both disabled.

Fix 5: Clear the Google Play Services Cache

Nearby Share is not a separate app — it lives inside Google Play Services. When that cache corrupts, sharing breaks in weird ways: devices that never appear, transfers that freeze at 0%, phantom error toasts. Clearing the cache forces the whole component to rebuild its state. This does not delete any personal data.

  1. Open Settings → Apps → See all apps → Google Play Services.
  2. Tap Storage & cache, then Clear cache. Do not tap Clear data / Clear storage — that would reset much more than sharing.
  3. Do this on both phones.
  4. Restart both phones after clearing.
  5. Retry the transfer. Cached-state corruption is a surprisingly common fix for stuck discovery.

Clear the Google Play Services cache to fix Nearby Share transfer failures

Fix 6: Update Google Play Services

If the cache clear did not do it, the underlying component may simply be out of date. Google ships Nearby Share improvements through Play Services updates, and a version that is months behind can fail against a newer one on the other phone.

  1. Open Settings → Apps → See all apps → Google Play Services.
  2. Scroll down and tap App details (or "App details in store") — this opens its Play Store page.
  3. If an Update button appears, install it. Do this on both phones.
  4. Also check the phone's system update: Settings → System → System update (Samsung: Settings → Software update → Download and install), and install anything pending.
  5. Restart both phones after updating and test again.

Watch: Fix Android Nearby Share or Quick Share Not Working

The video below walks through the same fixes — enabling the feature, checking visibility, and sorting out the Bluetooth and Location settings on both phones.

Video by DiziSight — full credit to the creator.

Frequently Asked Questions

Is Nearby Share the same as Quick Share?

Effectively, yes. Google rebranded Nearby Share to Quick Share to match Samsung's name for the same feature. On older phones you will see "Nearby Share" in settings; on Samsung and newer Pixels it says "Quick Share." The steps in this guide apply to both.

Do both phones need to be on the same Wi-Fi network?

No — and this surprises people. Wi-Fi just needs to be turned on so the phones can use Wi-Fi Direct for the transfer. They do not need to be joined to the same network, or any network at all.

Why does the transfer start but then fail?

Usually distance or a sleeping screen. Keep the phones within arm's reach with both screens awake. Large files over Wi-Fi Direct are also sensitive to interference — moving away from a busy router can help.

Can I share with someone not in my contacts?

Yes. Set Device visibility → Everyone on the receiving phone before starting. That makes the phone discoverable to any nearby device for the transfer, and you can switch it back to Contacts when you are done.

By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026