You're at home or a cafe, your Android says "Connected, no internet" or just shows full Wi-Fi bars. You open Chrome or YouTube — nothing. Not even a spinner. You toggle Wi-Fi off and on. Still dead. This usually hits right after a router reboot, a phone update, or when you've just joined a hotel or airport network. It can also hit out of nowhere on a network that worked five minutes ago.
What's actually going wrong
Wi-Fi and internet are two separate things. Your phone can connect to the router just fine — good signal, valid password, solid link — but the router itself can't reach the outside world, or it hands your phone an IP address that can't talk to anything. Three culprits cover 90% of cases:
- Captive portal not loaded. Hotel, airport, and coffee shop Wi-Fi blocks everything until you tap through a login page. If that page never pops up, you're stuck with a connection that looks alive but routes nowhere.
- DNS failure. Your phone got an IP but can't resolve names. The connection is fine, the lookup is not.
- DHCP or IP conflict. The router handed your phone an address that's already in use, or handed it a bad one. This is common after a router reboot or when 30 devices fight for a small DHCP pool.
The real fix is usually one of these three, in that order. Skip the "forget network" reflex first — it wipes saved credentials for no reason.
Fix it step by step
1. Force the captive portal to appear
Open Chrome and type any http:// address, not https. Try
http://neverssl.comhttp://example.com2. Toggle Wi-Fi and Airplane mode
Swipe down the notification shade. Tap Airplane mode on, wait 10 seconds, tap it off. Then toggle Wi-Fi off, wait 5 seconds, turn it back on. You should see the network reconnect in under 20 seconds. This forces a fresh DHCP request. If a stale lease was the problem, this fixes it.
3. Renew the IP address
This is the step most guides skip. Open Settings > Network & internet > Internet. Tap the gear icon next to your connected network. Tap the pencil or "Modify network" — you may need to tap "Advanced options" or "IP settings." If it's set to Static, switch to DHCP. If it's already DHCP, switch to Static, enter a different address in the same subnet (for example, if the router is 192.168.1.1 and your phone had 192.168.1.104, try 192.168.1.140), then switch back to DHCP. That forces a clean lease. Save, and your phone should reconnect within 15 seconds.
4. Change DNS to Cloudflare or Google
Still nothing? DNS is the likely culprit. Go to Settings > Network & internet > Private DNS (the path is under "Advanced" or "More connection settings" on Samsung and older Android). Select "Private DNS provider hostname" and enter:
one.one.one.oneOr use Google's:
dns.googleTap Save. Now open Chrome and load a site. If it loads instantly, your ISP or router DNS was the problem. Set it back to "Automatic" later only if you need to — private DNS is fine to leave on.
5. Check the router from another device
Grab a laptop or another phone. Does it have internet on the same Wi-Fi? If not, the problem is the router, not your phone. Unplug the router for 30 seconds, plug it back in, and wait 2 minutes for it to fully boot. Cable modems especially need that cold restart — the modem and router often lose sync after a power blip, and the router keeps broadcasting Wi-Fi like nothing's wrong.
6. Reset network settings on the phone
Only do this if steps 1–5 fail. Settings > System > Reset options > Reset Wi-Fi, mobile & Bluetooth. On Samsung it's under Settings > General management > Reset > Reset network settings. You'll lose saved Wi-Fi passwords and paired Bluetooth devices. Your phone reboots the Wi-Fi stack clean. After the reset, reconnect to your network. You should see it ask for the password again, then connect normally.
If it still doesn't work
Test on a different Wi-Fi network — a friend's house, a hotspot from another phone. If the internet works there, your phone is fine and the router or ISP is the problem. Call your ISP and ask if there's an outage in your area; that catches way more cases than people admit.
If the internet fails on every Wi-Fi network, try a mobile hotspot from another phone. Still failing? The Wi-Fi radio or the saved network profile is corrupted. A factory reset is the last resort, and honestly, on a phone older than four years, the Wi-Fi chip may be on its way out — intermittent no-internet on known-good networks is a classic dying-radio symptom.
One more thing worth checking: some Android 13 and 14 builds on Pixel and Samsung had a bug where MAC randomization broke DHCP on certain routers. Go to the network's settings, tap "Privacy" or "MAC address type," and switch from "Randomized MAC" to "Phone MAC." Reconnect. That fixed a wave of "connected, no internet" reports on TP-Link and Asus routers in late 2023.
Quick rule of thumb: if the Wi-Fi icon shows an exclamation mark or says "Connected, no internet," it's almost always DNS, DHCP, or a captive portal — in that order. Start there and you'll skip 80% of the guesswork.