Troubleshooting Android Nearby Share Connection and Discovery Fails

I was standing in a friend’s kitchen trying to send her twenty photos from a birthday dinner, both phones on the table, both screens awake, and nothing happened. Her phone simply did not appear on mine. I toggled the switch off and on, moved the phones closer until they were almost touching, and still got the same empty list. Ten minutes later it worked for no reason I could see, and that randomness annoyed me more than the failure itself. I spent the next week breaking it on purpose on three different phones so I could work out exactly which setting, in which order, actually fixes it.

Here is what I found: Nearby Share almost never fails for one mysterious reason. It fails because discovery and transfer are two different jobs, handled by two different radios, and each one has its own way of going wrong. Discovery uses Bluetooth Low Energy to spot a nearby device. The actual file moves over Wi-Fi Direct or a local hotspot link. A phone can be perfect at one and broken at the other, which is why you sometimes see the device but cannot send, and sometimes cannot see it at all.

This guide walks through both halves in the order I test them in real life, from the thirty-second checks to the full reset. It also covers the name change that confuses everyone: Google renamed Nearby Share to Quick Share in early 2024 after merging it with Samsung’s sharing feature. On a newer phone the menu says Quick Share. On an older one it may still say Nearby Share. They are the same feature, and every step below applies to both names.

How Nearby Share and Quick Share find a device in the first place

Before fixing anything it helps to know what has to happen in the few seconds between tapping Share and seeing a device name. When you open the share sheet and pick Quick Share, your phone starts shouting its presence over Bluetooth Low Energy while also listening for other phones doing the same. That low-energy broadcast carries just enough information for the other device to recognise you and offer itself as a target. Nothing about this step needs a Wi-Fi network, a mobile signal, or an internet connection.

Once you tap a device name, the two phones agree on a faster channel for the file itself. In most cases that channel is Wi-Fi Direct, a direct phone-to-phone link that does not pass through your router. If Wi-Fi Direct cannot start, the phones fall back to a Bluetooth transfer or a hotspot link, both of which are much slower and more likely to stall on large files. A 4K video that crawls or dies halfway is usually a sign that the fast channel never started, even though discovery worked fine.

Why discovery and transfer fail in different ways

Discovery failures look like an empty device list, a name that appears and vanishes, or a “No devices found” message when the other phone is right beside you. Transfer failures look different: the device appears, you tap it, the other person accepts, and then the progress bar freezes, the transfer drops at 47%, or you get a generic “Couldn’t send” error. Treating the two as one problem is the most common mistake I see, because the fix for a discovery failure is usually a visibility or permission setting, while the fix for a transfer failure is usually a Wi-Fi or power setting.

The other thing worth knowing is that both halves depend on Google Play services running normally in the background. Quick Share is not a standalone app you can simply reinstall; it lives inside Play services on most phones, and on Samsung phones it also ties into the One UI sharing panel. That is why clearing an app cache or updating Play services sometimes fixes a problem that no amount of toggling Bluetooth will touch.

The four things that must be true at the same time

For a transfer to work, four conditions have to hold simultaneously. Both phones need Bluetooth switched on, both need Wi-Fi switched on, both need location switched on, and both screens need to be awake and open. Location surprises people most, because sharing a photo feels like it should have nothing to do with where you are. Android requires location for Bluetooth scanning, since scanning can reveal nearby devices, so the system treats it as a location permission. If location is off, discovery simply never starts, and the phone will not always tell you why.

On top of that, the receiving phone has to be visible. Visibility is a separate setting from the on-off switch, and it is the single most common cause of “my phone never shows up”. I cover it in detail below, but the short version is this: open Settings, go to Connected devices, then Connection preferences, then Quick Share, and look at who can share with you. If that is set to “No one”, nothing will ever find you.

The most common reasons Nearby Share discovery fails

After testing the same failed transfer on a Pixel, a Samsung Galaxy and a Xiaomi phone, the same handful of causes kept showing up. They are boring, which is exactly why people miss them. Nobody expects a file transfer to fail because of a battery saver setting, but that is how it goes on Android: the radios and background services that sharing depends on are the first things the system throttles when it tries to save power.

Visibility is set to contacts only, or to no one

The default visibility on many phones is “Contacts”, which means only people saved in your contacts with a matching Google account can see your device. If the other person is not in your contacts, or their account email does not match the one on their phone, you are invisible to each other. The fix takes ten seconds: set visibility to “Everyone” for ten minutes while you transfer, then switch it back. The “Everyone” option on current versions runs on a ten-minute timer precisely so you do not forget and stay visible all day.

Bluetooth or Wi-Fi is off, or stuck in a bad state

Radios do not always report their true state. I have seen phones where the Bluetooth icon was lit but the radio had stalled after a long drive with a car kit connected, and the only cure was toggling it off, waiting a full ten seconds, and turning it back on. A quick flick off and on within a second is often not enough, because the radio never actually powers down. The same applies to Wi-Fi: if the phone has been connected to a weak network all day, the Wi-Fi Direct stack can be in a confused state until Wi-Fi is properly cycled.

Location is off or the permission is denied

Android 12 and later require the “Nearby devices” permission for Bluetooth scanning, and the system location switch must be on. Some phones also tie this to the precise location permission of Google Play services. If you once tapped “Don’t allow” on a permission prompt for Play services, discovery can go silent without any error message. This is worth checking before you blame the hardware, because it explains the otherwise baffling case of a phone that shares fine one week and stops the next after a permission clean-up.

Power saving, data saver and VPN apps are interfering

Battery Saver and the stricter Extreme Battery Saver modes limit background activity, and on some phones they pause the Bluetooth scanning that discovery relies on. Data Saver is less directly involved, since transfers do not use mobile data, but some VPN apps route all traffic through a tunnel and block the local Wi-Fi Direct handshake. I have watched a transfer fail three times in a row with a VPN running, then succeed instantly the moment the VPN was disconnected. If you use a VPN, turn it off for the transfer and turn it back on afterwards.

The two phones are too far apart, or one screen is locked

Quick Share is designed for devices within roughly ten metres, and in practice it works best under three or four metres with a clear line of sight. Thick walls, a phone buried in a bag, or a phone in a metal case can all weaken the Bluetooth Low Energy signal enough to break discovery. The receiving phone also needs its screen awake and Quick Share reachable; a locked phone will often not advertise itself at all, which is a privacy feature rather than a bug.

Fix Nearby Share discovery step by step

Work through these steps in order and test a transfer after each group of steps. The order matters, because the early steps fix most failures in under a minute, and the later ones are more disruptive. Do not jump straight to the network reset; you will wipe every saved Wi-Fi password for a problem that a visibility toggle would have solved.

Step 1: Put both phones side by side with both screens awake

Place the phones within a metre of each other, on a table, screens up and awake. Take both phones out of thick cases if you can. Open the share sheet on the sending phone and pick a small file first, a single photo rather than a 2 GB video, so you are testing discovery and not transfer speed at the same time.

Step 2: Check the Quick Share visibility setting on the receiving phone

On the receiving phone, open Settings, then Connected devices, then Connection preferences, then Quick Share. In the “Who can share with you” section, pick “Everyone” and leave the ten-minute window running. If the phone still says Nearby Share instead of Quick Share, the path is the same: Settings, then Connected devices, then Connection preferences, then Nearby Share. While you are there, check that the device name shown is one you recognise; a phone named after an old model can be easy to overlook in a crowded list.

Check the visibility window first before changing anything else

Visibility is the first thing I check on any failed transfer now, because it explains so many of them and takes seconds to rule out. If the receiving phone is set to “Your devices” only, it will only appear to other devices signed into the same Google account. That is a fine setting for moving files between your own phone and tablet, and a useless one when you are trying to send a photo to a friend. Flip it to “Everyone” for the transfer, then flip it back when you are done.

Step 3: Cycle Bluetooth, Wi-Fi and location on both phones

On both phones, turn Bluetooth off, wait ten seconds, and turn it back on. Do the same for Wi-Fi and for location. Use the Settings app rather than the quick settings tiles for at least one of these cycles, because the tiles sometimes only toggle a partial state. After cycling, wait another ten seconds before opening the share sheet again; the radios need a moment to start broadcasting.

Confirm Bluetooth and location are really on, not just showing as on

Open Settings, then Connected devices, then Bluetooth, and confirm the switch is on and the phone is not stuck on “Turning on”. Then open Settings, then Location, and confirm the main location switch is on. If either screen shows a spinner or a greyed-out toggle, restart the phone before going further. A radio that will not settle is a phone-level problem, not a sharing problem, and no amount of tapping in the share sheet will fix it.

Step 4: Turn off battery saver and disconnect the VPN

Open Settings, then Battery, then Battery Saver, and turn it off on both phones. If either phone has an “Extreme Battery Saver” or “Maximum power saving” mode, turn that off too. Then disconnect any VPN app and close any app that manages Wi-Fi connections automatically, such as a Wi-Fi auto-connect tool. Try the transfer again with both phones on their normal power mode.

Step 5: Restart both phones and try a small file again

A restart clears the Bluetooth and Wi-Fi stacks and restarts Google Play services, which is the component that actually runs Quick Share. Restart both phones, not just one, and test with a single small photo before attempting the real transfer. If the small file goes through, the path is healthy and you can send the larger files; if it does not, the problem is still in discovery or permissions, not in file size.

Step 6: Clear the cache of Google Play services and update everything

Open Settings, then Apps, then See all apps, then Google Play services, then Storage and cache, and tap Clear cache. Do not tap Clear storage, which can sign you out of things and cause more trouble than it solves. Then open the Play Store, check for updates to Google Play services and to the system, and install anything pending. A stale Play services version is a quiet cause of sharing failures after a major Android update.

Symptom, cause and fix at a glance

Use this table to match what you are seeing with the most likely cause. Start with the row that matches your symptom, try its fix, and only move to a different row if the symptom changes. Guessing at random through settings is how a two-minute fix turns into an afternoon.

One pattern in that table deserves a second look: a transfer that freezes at 0% almost always means the fast channel failed. Wi-Fi Direct transfer is what makes sending a video take seconds instead of minutes, and when it cannot start, the phones either crawl over Bluetooth or give up entirely. That is why cycling Wi-Fi and disconnecting a VPN fix so many “stuck at 0%” cases, even though the problem looked like a Bluetooth issue at first glance.

Wi-Fi and Bluetooth faults that break Nearby Share

Quick Share sits on top of your phone’s normal Wi-Fi and Bluetooth, so a fault in either radio shows up as a sharing failure. The tricky part is that the fault can be subtle: your Wi-Fi can work fine for browsing while its Wi-Fi Direct mode is broken, and your Bluetooth can play music to headphones while its Low Energy advertising is stalled. A phone can look healthy and still fail at sharing.

Start with Wi-Fi. If your phone drops its home network, struggles to stay connected, or shows full signal with no usable connection, the Wi-Fi stack itself needs attention before Quick Share has a chance. A good reference for sorting that side out is the guide to frequent Wi-Fi disconnections on Android, which walks through the router and phone settings that cause repeated drops. Fix the underlying Wi-Fi instability first, then test sharing again; a stable Wi-Fi stack makes Wi-Fi Direct far more reliable.

There is a second Wi-Fi trap worth knowing about. If your phone is connected to a Wi-Fi network but has no working internet through it, Android may mark the network as unusable and throttle background services that depend on the Wi-Fi radio. The guide to Wi-Fi connected but no internet errors covers how to tell a router problem from a phone problem and what to check on each side. You do not need internet access for Quick Share itself, but you do need the Wi-Fi radio in a healthy state, and a broken network connection is a good sign that the radio is not.

Bluetooth deserves the same treatment. If your phone has trouble holding a connection to headphones or a car kit, the Bluetooth stack may be the real culprit behind your sharing failures too. The walkthrough for Bluetooth pairing errors with wireless earbuds covers the pairing, cache and interference checks that also apply here, because the same radio handles both jobs. In particular, a phone that is already connected to several Bluetooth accessories at once can struggle to advertise itself for discovery; disconnecting an unused watch or speaker before a transfer is a cheap test that often helps.

Interference is the last piece. Bluetooth Low Energy shares the 2.4 GHz band with Wi-Fi, microwaves and a crowd of other gadgets. In a busy office or a flat full of smart home gear, discovery can take longer and transfers can slow down. Moving the two phones into a quieter spot, or simply closer together, is not a superstition; it genuinely reduces the noise the radios have to shout over.

Visibility, contacts and account settings that quietly block transfers

Visibility is where most “it worked last week” mysteries live. The setting has three levels, and each one changes who can see your phone. “Everyone” lets any nearby Android device see you for ten minutes. “Contacts” limits visibility to people in your Google contacts whose account details match. “Your devices” limits it to devices signed into your own Google account. The default varies by phone and by Android version, and a system update can change it without drawing your attention to the change.

The Contacts option has a catch that trips up real people: it only works when the sender is saved in the receiver’s contacts with the same email address that is attached to their Google account. A friend saved under a nickname, or saved with only a phone number, may not match. If you regularly share with the same people, saving their Google account email in their contact card makes Contacts mode work smoothly. If you share with strangers, clients or a new colleague, Everyone mode is the honest choice for those ten minutes.

Check the Google account on both phones

Quick Share identifies devices partly through the Google account signed into them. If one phone recently switched accounts, or a second account was added and became the default, the Contacts visibility match can break silently. Open Settings, then Accounts or Passwords and accounts, and confirm the expected Google account is present and syncing on both phones. A phone that was factory reset and signed into a different account will not match old contact entries until the contacts are updated too.

Device name and the “hidden” phone problem

Sometimes the device is visible but you cannot recognise it in the list. Phones often advertise a generic model name such as “Galaxy S24” or “Pixel 8”, and in a room full of the same model that is not much help. You can rename your device under Settings, then About phone, then Device name, and pick something distinctive. It takes thirty seconds and it removes an entire class of “I tapped the wrong phone” mistakes, which are more common than anyone admits.

When a network reset is the right move

A network reset is the heavy tool in this guide, and it earns its place only after the earlier steps have failed. It wipes all saved Wi-Fi networks and passwords, all paired Bluetooth devices, and mobile network settings, then returns them to factory defaults. That sounds drastic, and it is, but it also clears the corrupted radio configuration that a restart and a cache clear cannot reach. I have used it twice in three years of testing, and both times it fixed a phone that failed every transfer while its twin worked perfectly.

Before you reset, write down or screenshot your Wi-Fi passwords and make a note of your Bluetooth pairings, because you will be re-entering them afterwards. Then open Settings, then System, then Reset options, then Reset Wi-Fi, mobile and Bluetooth. The exact menu wording varies by brand; on Samsung phones it is under Settings, then General management, then Reset, then Reset network settings. Confirm, let the phone restart its radios, and then reconnect to your home Wi-Fi and re-pair your headphones before testing Quick Share again.

The full walkthrough for this step, including what gets wiped on each brand and what to back up first, is covered in the guide to resetting network settings on Android. Read it before you tap confirm, because the reset cannot be undone and the re-pairing afterwards takes longer than the reset itself. If the reset does not fix sharing either, the remaining suspects are a managed device policy, a hardware fault in the radio, or a system update that broke Play services, and those need a different kind of help than settings can offer.

What to do if the reset does not help

If a full network reset still leaves discovery empty, check whether the phone is managed by a work profile or a device admin app. Work profiles can disable peer-to-peer sharing entirely, and the block will not show up in any setting you can change. Look under Settings, then Security, then Device admin apps, and under Settings, then Accounts, for a work account. A phone that belongs to an employer may simply not be allowed to share this way, and no reset will change that.

Also consider the age of the phone. Devices running Android 10 or older, or phones whose Play services can no longer update, may run a version of Nearby Share that struggles with newer devices. The feature still works in principle, but the handshake has changed over the years, and very old versions sometimes fail against phones running current software. Updating the system, or accepting that an old phone may need a cable or a cloud link for large files, is the honest answer there.

Sharing with a Chromebook or a Windows PC

Quick Share also works with Chromebooks signed into the same Google account and with Windows PCs running Google’s Quick Share app. The same rules apply: Bluetooth and Wi-Fi on, location on, visibility set correctly, and the PC app open and signed in. On Windows, the most common failure is the app being closed or the PC’s Bluetooth driver being out of date. On a Chromebook, the usual culprit is the “Your devices” visibility setting combined with a different account on the Chromebook. Treat the computer like a second phone and run the same checks in the same order.

Nearby Share questions readers keep asking

Why does Quick Share show “No devices found” even when the other phone is right next to me?

The usual answer is visibility, not distance. The receiving phone is probably set to Contacts only or Your devices only, or its screen is asleep, or its location is off. Check the receiving phone first: Settings, Connected devices, Connection preferences, Quick Share, and set “Who can share with you” to Everyone for ten minutes. Then confirm location is on and the screen is awake. In my testing this fixes the empty list more often than every other step combined.

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

No. Quick Share does not use your home Wi-Fi network or your router at all. It uses Wi-Fi Direct, a direct link between the two phones, and it works with no router in range. Both phones do need Wi-Fi switched on, though, because Wi-Fi Direct runs on the Wi-Fi radio. That distinction explains a lot of confusion: people turn Wi-Fi off because they think they are “offline”, and then wonder why sharing stops working.

Why does a transfer start and then stall at 0% or fail halfway through?

A stall at 0% usually means the fast Wi-Fi Direct channel failed to start, so the phones are stuck negotiating or falling back to slow Bluetooth. Disconnect any VPN, cycle Wi-Fi off and on, turn off Battery Saver, and keep both phones still and close together during the transfer. A stall halfway through a large file usually means the fallback channel dropped, often because one phone locked its screen or moved out of range. Send large files with both screens awake and the phones sitting still on a table.

Can I use Quick Share without a Google account?

You can use it with visibility set to Everyone without the two phones sharing an account, and that is how most friend-to-friend transfers work. The account only matters for the Contacts and Your devices visibility modes, which use the account to decide who is allowed to see you. If you are moving files between your own phone and tablet, signing both into the same account and using Your devices mode is the most private setup.

Is Quick Share the same thing as Nearby Share, or do I have both?

They are the same feature under a new name. Google renamed Nearby Share to Quick Share in early 2024 and merged it with Samsung’s sharing system, so newer phones show Quick Share in the share sheet and in Settings. Older phones that have not received the update still show Nearby Share. You do not have both, and you do not need to enable one and disable the other; whichever name your phone shows is the current version of the feature.

A quick checklist to run before your next transfer

Most failed transfers are fixed by a short routine you can run in under a minute. Put both phones side by side with both screens awake. Set the receiver’s visibility to Everyone for ten minutes. Confirm Bluetooth, Wi-Fi and location are on for both phones. Turn off Battery Saver and disconnect the VPN. Then send a small photo first to prove the path works before you send the real files. That routine sounds basic, and that is the point: device visibility window and radio state cause nearly every failure I have seen, and checking them first saves you from resetting settings that were never broken.

If the routine fails, work through the steps in order instead of guessing. Clear the Google Play services cache, check for system updates, and only then consider the network reset. Keep a note of which step fixed it, because the same cause tends to come back: a phone that once lost its visibility setting after an update will often do it again. The feature itself is reliable once its four conditions are met, and the fastest way to enjoy it is to make those checks a habit rather than a rescue mission. The next time a friend holds out their phone for a photo, you will know within seconds whether the problem is visibility, a radio, a permission, or something worth a deeper look, and that is a much better place to be than staring at an empty device list in a kitchen.