How to Fix WiFi Connected but No Internet on Android: DHCP Failures, Captive Portal Loops, and Router Compatibility Issues on Samsung, Pixel, and OnePlus

Android’s WiFi status bar icon looks identical whether your phone has a solid internet connection or is stuck in a state where packets go nowhere. When your Samsung, Pixel, or OnePlus device shows “Connected” but every app fails to load, you’re dealing with one of a handful of well-documented problems — none of which require a factory reset to fix. This guide walks through the most common causes in order of likelihood and gives you the exact steps to resolve each one.

Why Android Says “Connected” With No Internet

Android continuously probes the internet in the background to validate a connection. When the probe succeeds, you see the normal WiFi icon. When it fails, Android displays a small exclamation mark next to the WiFi icon and may show “Connected, no internet” under the network name in Settings. The probe failure can happen for several reasons: the router itself has lost its upstream connection, your phone failed to receive an IP address from the router’s DHCP server, a captive portal (hotel or coffee shop login page) is intercepting traffic, Android’s Private DNS setting is blocking the probe, or a MAC address conflict is preventing proper DHCP assignment. The fix depends entirely on which of these is the actual cause.

Step 1: Check Whether the Problem Is Your Router

Before changing anything on your phone, check whether other devices on the same network have internet access. If your laptop, smart TV, and other phones also have no internet, the problem is your router or ISP — not your Android device. Reboot the router by unplugging it for 30 seconds and plugging it back in. If only your Android phone is affected, continue with the steps below.

Step 2: Toggle Airplane Mode

The quickest first fix is a full radio reset. Pull down the notification shade, enable Airplane Mode, wait 15 seconds, then disable it. This forces Android to release and renegotiate its network connection from scratch, including a fresh DHCP request. This resolves a surprisingly large percentage of “connected, no internet” cases that stem from a stale or corrupted connection state after waking from sleep.

Step 3: Forget and Rejoin the Network

If Airplane Mode does not help, go to Settings > Network & Internet > WiFi, long-press your network name (or tap the gear icon), and select Forget. Reconnect by selecting the network again and re-entering the password. This clears any cached session tokens or malformed DHCP state that may be preventing internet access without dropping the WiFi association itself.

Step 4: Disable Private DNS

Android 9 and later includes a “Private DNS” feature that routes all DNS queries through an encrypted DNS-over-TLS server. When that server is unreachable — or when the network you’re on blocks port 853 (the TLS port used by Private DNS) — Android fails its internet probe and marks the network as “no internet,” even though your IP address and routing are perfectly fine. Go to Settings > Network & Internet > Private DNS and temporarily set it to Automatic or Off. If internet access returns immediately, Private DNS was the culprit. You can either leave it off or switch to a server that works on that network (Google’s dns.google or Cloudflare’s one.one.one.one are reliable choices for home networks). For more on DNS options, see our guide on changing your DNS server for faster internet.

Step 5: Fix DHCP Failures With a Static IP

If your phone is stuck at “Obtaining IP address” or connects but receives a 169.254.x.x self-assigned address, your router’s DHCP server has failed to assign a valid IP. This happens when the DHCP pool is exhausted (too many devices), when a DHCP lease has become corrupted, or when your router’s DHCP server is misconfigured. The fastest fix is to assign a static IP directly on your phone:

1. Go to Settings > Network & Internet > WiFi and tap the gear icon next to your network.
2. Tap IP Settings and change it from DHCP to Static.
3. Enter an IP address in your router’s range (e.g., 192.168.1.200), the gateway (your router’s IP, typically 192.168.1.1), subnet mask (255.255.255.0), and a DNS server (8.8.8.8).
4. Save and reconnect.

If this restores internet access, log in to your router’s admin page and increase the DHCP pool size, or check for duplicate IP reservations that are exhausting the available addresses.

Step 6: Disable MAC Address Randomization

Android 10 introduced per-network MAC address randomization as a privacy feature. While useful on public networks, it can trigger problems on home routers that use MAC-based filtering or that assign DHCP leases tied to a specific MAC address — causing your phone to appear as an unknown device every time it connects. On Samsung devices, go to Settings > Connections > WiFi, tap the gear icon next to your network, and look for MAC address type. Set it to Phone MAC (use device MAC). On stock Android (Pixel), tap the gear icon next to the network, then Advanced > Privacy > Use device MAC. Forget and rejoin the network after making this change.

Step 7: Fix a Captive Portal Loop

On hotel, airport, or coffee shop networks, a captive portal (login page) must be completed before internet traffic is allowed through. Android is supposed to automatically detect and open the portal, but it often fails to do so — especially when Private DNS is enabled, when the network uses HTTPS-only interception, or when a previous session token is cached. To force the portal to appear:

• Disable Private DNS (Settings > Network & Internet > Private DNS > Off) before connecting.
• After connecting, open a browser and navigate to a plain HTTP site (for example, neverssl.com). This forces Android to follow the portal redirect that HTTPS connections suppress.
• If the portal still does not appear, forget the network, turn off Private DNS, reconnect, and try again immediately after joining.

On Samsung devices running One UI 6 or later, the system automatically prompts you to open a captive portal login page — tap the notification when it appears rather than dismissing it.

Step 8: Clear WiFi Configuration Cache (Samsung and OnePlus)

On Samsung devices, the “Wi-Fi Direct” service can accumulate corrupted state that interferes with normal WiFi operation. Go to Settings > Apps > See All Apps, tap the three-dot menu, enable Show system apps, and find Wi-Fi Direct. Tap Storage > Clear Cache. Do the same for the Wi-Fi system app if it appears in the list. On OnePlus devices, the equivalent is found under Settings > Apps > System Apps — clear the cache for WiFi and restart the phone before reconnecting.

Step 9: Reset Network Settings

If none of the above steps resolve the issue, a full network settings reset clears all saved WiFi networks, Bluetooth pairings, mobile data settings, and VPN configurations in one step. On Samsung, go to Settings > General Management > Reset > Reset Network Settings. On Pixel, go to Settings > System > Reset Options > Reset WiFi, Mobile & Bluetooth. On OnePlus, go to Settings > System > Backup & Reset > Reset Network Settings. You will need to re-enter WiFi passwords afterward, but this resolves persistent connectivity issues caused by deeply corrupted network profiles. A full speed test after reconnecting will confirm everything is working at full capacity.

Summary: Fastest Path to a Fix

Start with Airplane Mode toggle and Forget/Rejoin — these resolve the majority of cases in under a minute. If the problem persists, check Private DNS (the most overlooked cause on Android 9+) and MAC randomization (most common source of DHCP failures on home networks). Captive portal loops require disabling Private DNS before connecting. Reserve the static IP assignment and network settings reset for cases where standard steps have failed. Working through these steps in order almost always resolves “connected, no internet” on Android without requiring a factory reset.