Android Wi-Fi Problems: The Complete Troubleshooting Guide

Android Wi-Fi problems come in exactly four flavors, and each points to a different culprit. Failure one: the phone cannot connect at all, it tries, then reports 'Saved' or an authentication error. Failure two: it connects, shows full bars, and nothing loads, the dreaded 'Connected, no internet'. Failure three: it connects and works, then drops every few minutes. Failure four: it works but is miserably slow. People apply fixes for one failure to another and conclude nothing works; identifying your flavor first cuts the fix list by three quarters.

There is also the one-question diagnostic that instantly halves the search space: does another device work on the same network? Grab any laptop, tablet or second phone. If everything fails on that Wi-Fi, the router or the internet line is the patient and your phone is a witness; go to the router section below. If other devices are fine and only your Android struggles, the phone holds the problem, and phone-side fixes will land. Thirty seconds spent on this question saves entire evenings.

Keep in mind, too, that the phone and the router negotiate as a pair, and long-lived pairs accumulate stale state on both ends: cached credentials, old DHCP leases, band-steering decisions made months ago. This is why the unglamorous ritual, restart the phone, restart the router by unplugging it for thirty seconds, forget the network and rejoin fresh, resolves such a comical share of cases. Run the ritual before anything clever; the sections below assume you already have.

When the phone loops on 'Authenticating' or throws 'Authentication error' with a password you know is right, start by proving the password anyway. Long-press the network, choose Forget, then reconnect and retype it slowly, watching with the show-password eye icon; a surprising number of 'correct' passwords have a capital letter or an underscore wrong, and the forget-rejoin also discards stale keys the phone may be presenting from an old router configuration, the classic aftermath of a router swap or a password change.

If the retyped password still fails on your phone while other devices connect, look at router-side gates. MAC address filtering blocks unknown devices silently, and modern Androids present a randomized MAC per network by default, so a phone that was whitelisted once can look brand new to the router later. Two fixes: add the phone's current MAC in the router's filter list, or set the phone to use its device MAC for your home network, tap the network, Advanced or Privacy, and switch 'Randomized MAC' to 'Device MAC'. Also check whether the router runs WPA3-only security; older phones cannot join WPA3-only networks, and the router setting 'WPA2/WPA3 mixed' restores compatibility instantly.

A connection that fails with no error at all, endless 'Saved', often means the phone gave up acquiring an IP address. Assign a static IP as a test: tap the network, Advanced, IP settings, Static, and enter an address in your router's range. If static works where automatic did not, the router's DHCP service is sick, a router reboot or firmware update fixes it at the source. And exhaust the dumb-but-real possibilities: airplane mode leftovers, a Bluetooth-tethering toggle hijacking connectivity, or a 5 GHz-only network name that an older phone simply cannot see, covered next.

'Connected, no internet' means the phone-to-router link is healthy and the break lies beyond the router. First, split the path: can other devices on this Wi-Fi browse? If nothing can, log the router's status page or just look at its lights, an alarming ISP light means the internet line itself is down, and your call is to the provider, not to Android. If other devices browse fine and only your phone shows the no-internet flag, the break is in how your phone resolves or routes traffic, and three phone-side suspects cover nearly all of it.

Suspect one: a captive portal you have not completed. Hotel, airport and cafe networks intercept traffic until you accept terms on a login page; Android usually pops the page automatically, but when it does not, open the browser and try loading any plain site, which forces the portal to appear. Suspect two: private DNS. Settings, Network and internet, Private DNS; if it names a provider that is down or blocked on this network, everything fails while the connection looks fine. Set it to Automatic and retest; this single setting quietly breaks more phones than any other.

Suspect three: a VPN or a leftover proxy. An expired or misconfigured VPN captures all traffic and delivers none of it, and a proxy configured months ago for one network follows you around; check both in settings and in the network's Advanced options. If none of the three apply, reset network settings, Settings, System, Reset options, 'Reset Wi-Fi, mobile and Bluetooth', which wipes every stale network parameter at once. You will re-enter saved Wi-Fi passwords afterward, so note the important ones first. This reset is the closing move for stubborn no-internet states and resolves nearly everything that survived the suspects above.

Wi-Fi that connects fine and then drops every few minutes is nearly always one of three mechanisms: the phone's power management putting the radio to sleep, the router steering the phone between bands badly, or genuine signal-edge flapping. Start with power management, the most common and least suspected. Battery saver mode aggressively kills Wi-Fi on many models, as do manufacturer 'adaptive battery' features and third-party optimizer apps. Test with battery saver off and any optimizer uninstalled; if drops stop, you found it, and exempting Wi-Fi from optimization brings back both worlds.

The band-steering mechanism produces a distinctive signature: drops that happen mostly in one part of the home, or when moving around. Dual-band routers broadcasting one network name across 2.4 GHz and 5 GHz push devices between bands, and some phone-router pairs handle the push badly, reconnecting with a visible hiccup each time. The clean fix is naming the bands separately on the router, HomeNet-2G and HomeNet-5G, then connecting the phone to one deliberately: 5 GHz near the router for speed, 2.4 GHz farther away for range. Drops that vanish after splitting bands confirm the diagnosis.

True signal-edge flapping shows up at the same physical spots every time, the bedroom at the far end, the garden. There is no software cure for physics: the fixes are placement and coverage, raise the router off the floor and away from metal and microwaves, or add a mesh node or extender for the dead wing. You can map your coverage honestly in five minutes by running our internet speed test at various spots in the house; the numbers will show exactly where the edge lies, and whether the 'drops' are actually the phone falling to an unusable trickle rather than disconnecting outright.

Slow is the failure people misdiagnose most, because the speed you feel is the minimum of several links: internet plan, router capability, band, distance, congestion, and the phone itself. Measure before blaming: run our speed test next to the router, then at your usual spots. Next to the router you should see something resembling your plan; if you do not, the problem is the router or the plan, and no phone setting will help. If the near-router number is good and the bedroom number is a tenth of it, distance and walls are eating the signal, and the coverage fixes above apply.

The single biggest phone-side speed lever is which band you are on. The 2.4 GHz band penetrates walls better but is slow and shared with every neighbor, microwave and legacy gadget; 5 GHz is dramatically faster at moderate range. A phone that silently fell onto 2.4 GHz in a crowded apartment building can be five times slower than the same phone on 5 GHz in the same chair. With bands split by name as recommended above, you choose explicitly. While testing, also try a personal experiment: pause the household's streaming and re-test, congestion from three simultaneous 4K streams looks exactly like 'slow Wi-Fi' on the phone that measures it.

Phone-side factors are worth a two-minute sweep: a VPN adds overhead and sometimes routes you through a distant country, private DNS to a slow provider drags every page load, battery saver throttles radios on some models, and a phone case with metal elements measurably attenuates signal. And calibrate expectations against hardware: an older phone with Wi-Fi 4 cannot use the speed of a Wi-Fi 6 router and a gigabit plan; our device info tool shows what your hardware supports, and a mismatch there is a shopping decision, not a troubleshooting failure.

When the one-question diagnostic points at the router, a handful of router-side moves solve most of it, and none require expertise. The reboot with a purpose: unplug the router for a full thirty seconds, which clears its memory, drops stale client leases, and forces re-negotiation with the ISP; monthly reboots are legitimate maintenance for consumer routers that otherwise run for years accumulating cruft. While you are at it, check for firmware updates in the router's app or admin page, security and stability fixes ship there and almost nobody installs them.

Channel congestion is the apartment-building disease: dozens of routers shouting over each other on the same defaults. Most modern routers pick channels automatically at boot, another reason the reboot helps, but if yours allows manual selection, channels 1, 6 and 11 are the only non-overlapping choices on 2.4 GHz, and picking the one your neighbors use least yields real gains. On 5 GHz, congestion is rarer, one more reason to live there when range allows.

Two settings deserve suspicion when a specific phone misbehaves on an otherwise healthy network: band steering, covered earlier, disable it or split the bands; and any 'smart connect', QoS or client-limit feature that deprioritizes or caps unknown devices. Guest networks with client isolation also break casting and file sharing by design, so a phone that cannot see the Chromecast may simply be on the guest SSID. If the router is ISP-supplied, ancient and cranky, ask the provider for a replacement; they swap them routinely, and a five-year-old modem-router combo is the true bottleneck behind a startling number of 'Android Wi-Fi problems'.

When individual fixes have not landed, run the full escalation in order, testing between steps. One: forget the network and rejoin. Two: phone restart plus router thirty-second power cycle. Three: reset network settings (Settings, System, Reset options), which re-virginizes Wi-Fi, Bluetooth and mobile state at once; you will re-enter Wi-Fi passwords. Four: test the phone on a completely different network, a friend's Wi-Fi or a cafe. Five: test in Safe Mode, which rules third-party apps in or out, VPNs, ad blockers and optimizers are recurring Wi-Fi saboteurs. Six: as the last software word, a factory reset, justified only when Wi-Fi fails on multiple networks and in Safe Mode.

Hardware failure of the Wi-Fi radio itself is rare but real, and it has a recognizable profile: the phone sees no networks at all or only at point-blank range, the Wi-Fi toggle flips itself off, the MAC address reads as 02:00:00:00:00:00 in settings, or the problems began after a drop or a swim. A phone matching that profile after step six above has earned a repair-shop visit; the fix is typically a board-level antenna or module repair, and its price against the phone's value makes the repair-or-replace decision for you.

For everything short of that, the odds are strongly with you: the overwhelming majority of Android Wi-Fi misery is stale state, one wrong setting, power management, or router-side congestion, all covered above and all free to fix. Keep the two-line maintenance habit, occasional router reboots and updates installed on both ends, and verify your fixes with numbers from the speed test rather than feelings; a measured before-and-after is how you know a problem is actually gone rather than resting.