Android Won’t Connect To Wi-Fi | Fix Login Loops Fast

When your phone refuses to join Wi-Fi, it can feel random. One minute it’s fine, the next you’re stuck on “Saved,” “Obtaining IP,” or “Connected, no internet.” The good news is that Android’s Wi-Fi stack is predictable once you match the symptom to the right fix.

It’s annoying, but it’s fixable.

This guide walks through the moves that solve the most common failures, from a bad saved password to a router feature that your phone won’t accept. You’ll start with quick checks, then move into settings that stop repeat dropouts on specific networks.

Match The Symptom To The Right Fix

Wi-Fi problems look similar, but the cause shifts based on what you see on screen. Use the table to pick a starting point.

What You See	Common Cause	What To Try First
“Saved” then disconnects	Wrong password or security mismatch	Forget the network and rejoin
“Obtaining IP” hangs	DHCP lease conflict or router overload	Restart phone and router
Connected, no internet	DNS issue, captive portal, or router block	Open a browser, then switch DNS
Works on other Wi-Fi, not home	Router band, channel, or WPA mode	Try 2.4 GHz, check WPA2/WPA3
Only one device fails	MAC filtering or device-level setting	Toggle Private MAC, reset network

Fast Checks That Fix Most Android Wi-Fi Failures

Start here if you need Wi-Fi back right now. These steps clear the easy stuff without wiping your phone or touching router settings.

• Toggle Airplane mode — Turn it on for 10 seconds, then turn it off to reload radios and clear stuck scans.
• Restart the phone — A full reboot refreshes Wi-Fi drivers and drops stale network state that a simple toggle won’t clear.
• Forget and rejoin Wi-Fi — Tap the network name, choose Forget, then join again and retype the password slowly.
• Turn off VPN and ad blockers — Some VPN profiles and local filters break Wi-Fi sign-in pages and make networks look offline.

If your device keeps looping between “Saved” and disconnected, treat it like a saved network mismatch. A changed router password or security mode can trap Android in that loop.

Try a hotspot next. If that works, the fix is in the saved network or router settings.

Android Won’t Connect To Wi-Fi After Updates

Updates can reset network pieces in ways you don’t notice until you reconnect. If the timing lines up, start with the device-side resets first.

Reset Wi-Fi And Bluetooth The Clean Way

Android includes a reset that wipes saved Wi-Fi networks, paired Bluetooth devices, and some network preferences. It’s often the quickest way to clear a broken configuration without erasing apps or photos.

1. Open Reset options — Go to Settings, then System, then Reset options (wording varies by brand).
2. Pick the network reset — Tap Reset Wi-Fi, mobile & Bluetooth or Reset network settings.
3. Confirm and restart — Run the reset, then reboot the phone before you reconnect.
4. Rejoin your Wi-Fi — Join the network again and re-enter the password from scratch.

Check Private MAC And Router Access Lists

Android can use a randomized MAC per network. That protects privacy, but it can confuse routers that use MAC allow-lists, parental controls, or device reservations. If your router expects a known MAC, Android may look like a new device each time.

1. Open Wi-Fi network details — Tap and hold your Wi-Fi name, then open the settings panel for that network.
2. Find the MAC option — Look for Private MAC, MAC type, or similar text.
3. Switch the MAC mode — Try Device MAC for that network, then reconnect and test.
4. Check router lists — If your router blocks unknown devices, add the phone or turn off the block rule.

If you still can’t join, test with mobile hotspot Wi-Fi. If the phone joins a hotspot but not your router, the update likely changed a setting that clashes with your router’s security mode or band settings.

Fix Home Router Issues When Other Networks Work

When your phone works on coffee shop Wi-Fi and hotspots but fails on your home network, the router is the main suspect. You usually need one setting change, or a quick cleanup after months of uptime.

Start With A Simple Router Refresh

• Restart the router — Unplug it for 30 seconds, plug it back in, then wait for full internet lights before testing.
• Reboot the modem — If you have a separate modem, reboot it too so the router gets a clean upstream link.

Try 2.4 GHz Versus 5 GHz

Many routers broadcast 2.4 GHz and 5 GHz. 5 GHz is faster up close, but it drops sooner through walls. Some routers combine both under one name, which can cause jumpy switching.

• Split the network names — Give 2.4 GHz and 5 GHz different SSIDs, then join each one and test stability.
• Use 2.4 GHz for distance — If you’re far from the router, 2.4 GHz may stay stable while 5 GHz fails.
• Turn off band steering — If your router has band steering, disable it and test with separate SSIDs.

Check Security Mode And Password Type

Security mode mismatches are a classic cause of “Saved” loops. If your router is set to a newer mode that your phone can’t negotiate cleanly, joining fails even with the right password.

• Use WPA2 or WPA2/WPA3 — Set security to WPA2-PSK (AES) or a mixed WPA2/WPA3 option if your router offers it.
• Avoid WEP and WPA — Older modes can be blocked by newer Android builds or cause unstable joins.
• Confirm the password — Re-enter it on a second device to confirm the router password didn’t change.

Deeper Fixes For Stubborn “Connected, No Internet” Cases

When Android says it’s connected but pages won’t load, the Wi-Fi link is up and the problem is past authentication. That usually points to DNS, captive portal sign-in, IP settings, or a router rule that blocks traffic.

Force A Captive Portal Sign-In

Some networks need a sign-in page. If Android doesn’t pop it up, opening a plain, non-HTTPS page can trigger it.

• Turn Wi-Fi off and on — This can retrigger the sign-in detection.
• Open a browser tab — Type neverssl.com to force a simple page that often redirects to the sign-in screen.
• Forget and rejoin — If the page still won’t show, forget the network and connect again.

Switch DNS Or Clear Private DNS

A bad DNS path makes the internet feel down even when Wi-Fi is connected. If you use Private DNS, a provider outage can break browsing on every Wi-Fi network.

1. Open Private DNS — In Settings, search for Private DNS and open it.
2. Set it to Automatic — Turn off any custom hostname and test Wi-Fi again.
3. Try a public DNS — If your router allows DNS changes, set it to a well-known DNS provider and retest.

Refresh IP Settings Without Guesswork

If “Obtaining IP” hangs, Android may be stuck waiting for DHCP. A quick way to clear the lease is to toggle between DHCP and static settings, then return to DHCP.

1. Open network IP settings — Tap your Wi-Fi network, then IP settings, then DHCP or Static.
2. Switch to Static briefly — Select Static, wait a few seconds, then switch back to DHCP.
3. Reconnect and test — Turn Wi-Fi off and on, then test with a simple site.

If the same network breaks only on one phone, look for a router rule tied to that device. Reservations, access control, and per-device limits can block traffic while leaving the Wi-Fi link itself “connected.”

Stop Repeat Dropouts And Slow Loads On Android

Sometimes Wi-Fi connects fine, then drops every few minutes, or loads feel sluggish. Small toggles can change a lot, especially on phones that try to save battery.

Turn Off Battery Limits For Wi-Fi

Some devices put Wi-Fi to sleep in the background or cut network access for apps. That can break VoIP calls, streaming, and even sign-in flows if the phone keeps pausing connectivity.

• Disable battery saver — Turn off Battery Saver and test Wi-Fi stability for 10 minutes.
• Allow background data — In App info for your browser or chat app, allow background data and remove data limits.
• Keep Wi-Fi on during sleep — If your device has a Wi-Fi sleep setting, set it to stay on.

Check “Switch To Mobile Data” Features

Some Android builds can switch away from Wi-Fi when it thinks the network is weak. That can create loops where Wi-Fi keeps reconnecting while apps keep using mobile data.

• Turn off adaptive connectivity — Search Settings for Adaptive connectivity and disable it, then test.
• Disable “Wi-Fi assistant” — Some brands call it Wi-Fi assistant or Smart Wi-Fi; turn it off and retry.
• Disable auto switch — If there’s an auto switch option, disable it to keep Wi-Fi as the main path.

Clean Up Saved Networks

A long list of saved networks can cause constant scanning and auto-joins to weak signals. Cleaning the list helps your phone stick to the right network at home.

• Forget weak networks — Remove old hotspots and networks you no longer use.
• Turn off auto-connect — For networks you only use sometimes, disable auto-connect.
• Restart after cleanup — Reboot the phone to refresh the Wi-Fi list and scan cache.

When The Problem Is Hardware Or Your Account

If none of the steps above work, the failure may be physical or tied to your internet service. You can still narrow it down before you spend money or reset the phone completely.

• Test in Safe Mode — Boot into Safe Mode to see if a third-party app is interfering with Wi-Fi, then test the same network.
• Try another router — Connect to a friend’s home router to confirm the phone can join normal WPA2 networks.
• Update router firmware — A router update can often fix DHCP and WPA bugs that show up with newer phones.
• Check ISP outages — If every device shows “connected, no internet,” the line may be down even if the router is on.
• Plan a factory reset — If Android Wi-Fi fails on every network and Safe Mode doesn’t help, a reset can clear deep system corruption.

If you’re stuck right at the start and the phone shows android won’t connect to wi-fi across multiple networks, start with device-level resets and Safe Mode. If it only happens on one router, start with band, WPA mode, and router access rules.

Once Wi-Fi is stable again, keep one simple habit. When you change your router password or security mode, forget the old network on your phone and join again. It prevents the same loop the next time android won’t connect to wi-fi when you least want to troubleshoot.