Troubleshooting
Why your Wi-Fi endoscope keeps disconnecting
Published · Last updated
Your phone is leaving on purpose. A Wi-Fi scope has no internet behind it, and Android tests every network it joins for internet access. When that test fails, the phone can quietly hand you back to mobile data — mid-inspection, with no warning. Turn off automatic network switching and the drops stop.
It always happens at the worst moment. You've fed the probe two feet into a wall cavity, you're watching the screen, and the picture freezes. Or the app throws up "camera disconnected". Or the feed just goes black and the scope's little LED is still glowing at you from inside the wall.
Almost nobody's scope is faulty. The phone walked away.
Jump to
What your phone is actually doing
Every time an Android phone joins a Wi-Fi network, it quietly runs a test. It sends a small HTTP request to a Google address — connectivitycheck.gstatic.com/generate_204 — and waits for an empty 204 No Content reply. Get the 204, and the phone knows the network reaches the internet. This is how your phone spots hotel and airport logins before you do.
Your endoscope is a camera on the end of a cable. It has no internet, no gateway, nothing upstream. The check goes out and dies.
What happens next depends on the phone. Android has three ways of reacting to a network that fails the check, and the third one is the problem:
- Prompt — you get the "this network has no internet access" notification and get to decide. Annoying, but survivable.
- Ignore — the phone stays put and says nothing. This is what you want.
- Avoid — the phone drops the network and won't come back to it. This is the one that ruins your afternoon.
Layered on top is a separate feature with a friendlier name and the same effect. Samsung calls it Switch to mobile data, and it lives under Intelligent Wi-Fi. Other makers call it Adaptive Wi-Fi, Auto network switch, or Smart network switch. It watches for Wi-Fi that looks slow or dead and moves you to cellular without asking.
To that feature, a borescope looks exactly like a broken router.
The connectivity check doesn't run once. It repeats, and it repeats more eagerly when the screen is on and you're actively using the phone — which is precisely when you're staring at the probe feed.
That's why the drop so often lands two minutes in rather than immediately, and why it can seem to happen only when you're paying attention. You aren't imagining the timing.
Match your symptom
Different failures look different. Find yours before you start changing settings.
| What you see | Almost certainly | Go to |
|---|---|---|
| Connects fine, drops after a minute or two, phone back on mobile data | Automatic network switching | The setting |
| "No internet access" notification, then it leaves | Connectivity check, set to avoid | The setting |
| Won't rejoin the scope's network at all after one bad session | Android has blacklisted it as a dead network | Forget and rejoin |
| Joins, but the app never finds the camera | Something else is already holding the stream | One client |
| Picture stutters and drops the deeper the probe goes | 2.4 GHz signal losing a fight with metal | Range |
| Fine for twenty minutes, then dies for good | Transmitter battery | Battery |
| Image is there but frozen — probe moves, picture doesn't | Feed already dead, app still painting the last frame | Read this |
The setting that stops it
One change fixes this for most people. The wording differs by manufacturer, which is why generic advice tends to miss.
Samsung Galaxy
Settings → Connections → Wi-Fi → the three-dot menu → Intelligent Wi-Fi → turn off Switch to mobile data. While you're in there, turn off Auto reconnect for your home network if the phone keeps hopping back to it.
Google Pixel
Settings → Network & internet → Internet → the gear icon next to the scope's network → turn off Automatically use this network if you see it. Pixels lean more on the "stay connected?" prompt, so the practical fix is to answer it and tick the box that stops it asking again.
Xiaomi, Redmi and POCO
Settings → Wi-Fi → Additional settings → turn off Wi-Fi assistant (some builds call it Wi-Fi speed mode or Data saving). MIUI is the most aggressive about this of any Android skin, and it's why so many "endoscope keeps disconnecting" complaints come from Redmi owners specifically.
The one that works on every phone
Turn mobile data off while you're inspecting. Blunt, ugly, and completely reliable — with no cellular connection to run to, the phone has nowhere to go. If you're in a crawlspace or a plant room you probably had no signal anyway.
If your phone now refuses to rejoin the scope's network at all, it has remembered it as a dead end. Long-press the network, choose Forget, then join it again fresh. Do the mobile-data change first, or you'll just teach it the same lesson twice.
Only one device at a time
Most Wi-Fi borescopes accept exactly one client. Not "one is recommended" — one, and the second one gets nothing.
This catches people constantly on a job. You hand the phone to someone, they can't see anything, and you both assume the scope is broken. What's actually happened is that your phone is still holding the stream from three minutes ago, or a tablet in the van rejoined the network automatically the moment it came in range.
Before you troubleshoot anything else: turn Wi-Fi off on every other device nearby, then power-cycle the scope. If a second phone connects instantly after that, you've found it.
Battery, metal and range
The transmitter has its own battery
The Wi-Fi module on the cable is a separate device with its own cell, and it runs down in one to three hours depending on the model and how bright you've got the LEDs. It also charges over the same USB port you'd use for anything else, so it's easy to assume it's charged when it isn't.
The tell is a session that works perfectly and then ends. Sudden, complete, no recovery. If reconnecting does nothing and the scope's own light is dim or dead, that's a flat battery, not a network problem.
2.4 GHz does not enjoy buildings
Wi-Fi scopes broadcast on 2.4 GHz. It travels further than 5 GHz, which is why they use it — but it's still radio, and you're deliberately pushing the transmitter into a wall, an engine bay, or a length of steel pipe.
If the picture degrades as you feed more cable in, that's range and shielding, not a setting. Move the phone closer to where the cable enters. Ductwork, foil-backed insulation and anything with rebar in it will all cut the link short.
Microwaves, genuinely
2.4 GHz is the same band a microwave oven leaks into. Working under a kitchen sink with the microwave running above you is a real and very specific way to lose your feed, and it will look like the scope is faulty.
Worth knowing whatever app you use: when a Wi-Fi scope drops, plenty of viewers keep showing the last frame they received. No error, no grey screen, no timeout. Just a still photograph of where the probe was a moment ago.
Push the probe further in and nothing changes, so you conclude the space ahead looks the same as the space behind. In a wall cavity that's misleading. In an engine bay or a live panel it's worse than misleading.
The check takes a second: put a finger over the lens. If the picture doesn't go dark immediately, you're looking at a corpse. Reconnect and start again.
On iPhone
iOS runs the same kind of connectivity check and is just as capable of deciding your scope's network isn't worth staying on. Two settings matter.
Under Settings → Wi-Fi, tap the ⓘ next to the scope's network and turn off Auto-Join for your usual networks instead — the goal is to stop the phone hopping home mid-job. Then, under Settings → Mobile Data, turn off Wi-Fi Assist. That feature exists specifically to abandon weak Wi-Fi for cellular, and a scope with no internet is exactly what it's hunting for.
Wi-Fi Assist is on by default and most people have never opened that screen. If your iPhone keeps dropping the scope, start there.
Thinking about a USB scope instead?
USB borescopes have no network to lose, no transmitter battery, and no lag — but they don't work on iPhone at all, and on Android the cable causes most of the failures. The Android troubleshooting guide covers those, the iPhone answer is here, and the compatibility list records models tested on real hardware.
Questions people ask
Why does my Wi-Fi endoscope keep disconnecting from my phone?
Because the scope's network has no internet, and your phone tests for internet on every network it joins. When the test fails, automatic network switching moves you back to mobile data. Turn that switching off — on Samsung it's Intelligent Wi-Fi → Switch to mobile data — or turn mobile data off entirely while you work.
Why does my phone say "connected, no internet" for my endoscope?
That message is correct and harmless. A borescope is a camera, not a router, so there is nothing behind it to reach. Tap the option to stay connected, and tick the box that stops it asking again for that network.
My phone won't reconnect to the scope's Wi-Fi at all now.
Android can mark a network that repeatedly fails its internet check as one to avoid, and then stops rejoining. Long-press the network, choose Forget, and join it again — but change the automatic-switching setting first, or the phone will just relearn it.
Can two phones use one Wi-Fi borescope at the same time?
Almost never. Most scopes serve a single client, and the second device simply gets no video. If someone else can't see the picture, check that your phone or a tablet nearby isn't still holding the connection.
How long does a Wi-Fi endoscope battery last?
Typically one to three hours, depending on the model and LED brightness. A session that runs fine and then stops dead, with no reconnection possible, is usually a flat transmitter rather than a network fault.
Is a USB borescope more reliable than Wi-Fi?
For staying connected, yes — there's no network to drop and no transmitter battery to run flat, and the picture has no lag. The trade is that USB scopes don't work on iPhone, and the cable becomes the thing most likely to fail.
If your phone behaves differently from what's described here, tell us the model and what it does. Manufacturer-specific behaviour is exactly what this page exists to record.