Android Stuck on 'Obtaining IP Address' — Real Fix

Android hanging on 'Obtaining IP Address' means DHCP failed — your phone can't get a lease from the router. Usually a router-side issue, not the phone. Here's how to fix it fast.

You tap your Wi-Fi network, type the password, and then... nothing. The status just sits there: Obtaining IP Address. Sometimes it cycles through Authenticating, Obtaining IP Address, then drops back to Saved and loops forever. I've seen this on a Pixel 6a after a router firmware update, on a Samsung A54 at a hotel with a captive portal, and on a Xiaomi at home right after the neighbor's kid filled the DHCP pool with smart bulbs. Same symptom every time.

The good news: this is almost never a hardware failure. It's a DHCP handshake that isn't completing, and you can usually fix it in five minutes.

What 'Obtaining IP Address' Actually Means

Your phone has authenticated with the access point (WPA2/WPA3 handshake is done), but it hasn't received an IP address yet. Every device needs an IP, a subnet mask, a gateway, and DNS servers. On most home and office networks those come from DHCP — the router hands them out from a pool.

When you see Obtaining IP Address, the phone has sent a DHCPDISCOVER packet and is waiting for a DHCPOFFER that never arrives. That can happen for a few reasons:

The router's DHCP pool is exhausted (every lease is in use).
The router's DHCP server is disabled or crashed.
Your phone has a stale lease that conflicts with another device.
A MAC filter or client isolation is silently blocking the phone.
You're on a captive-portal network that expects a browser handshake (hotels, airports).
The phone's saved network profile is corrupted.

Nine times out of ten, it's one of the first two. The phone gets blamed because it's the thing showing the error, but the phone is usually just the messenger.

Fix It — In This Order

Don't factory reset your phone. Don't reflash anything. Don't disable 'Wi-Fi scanning' in developer options — that does nothing for this error. Work through these steps.

1. Toggle Wi-Fi off and on

Sounds dumb, works maybe 10% of the time. The phone re-sends DHCPDISCOVER and sometimes the router actually answers. Try it once, then move on.

2. Forget the network and rejoin

This clears the saved profile and any cached lease info. Long-press the network name, tap Forget, then reconnect and type the password again. On Samsung it's under Settings → Connections → Wi-Fi → three-dot menu → Saved networks. On stock Android it's the gear icon next to the SSID.

3. Restart the router, not just the phone

Reboot your phone first, then the router. Pull the router's power for 30 full seconds. A lot of consumer routers (looking at you, older Netgear and ISP-supplied boxes) leak DHCP leases after a few weeks and stop handing out new ones. If that fixes it, you've got a router problem, not a phone problem.

4. Check the DHCP pool on the router

Log into the router admin page. Common addresses: 192.168.1.1, 192.168.0.1, or 10.0.0.1. Look for DHCP settings or LAN setup.

Pool size: If it's set to something like 192.168.1.100–192.168.1.110, that's only 11 addresses. Twenty smart devices will eat that in an afternoon. Expand it to at least .100–.200.
Lease time: If it's set to 'Forever' or 'Infinite', old leases never expire. Set it to 24 hours or 1 day.
DHCP server: Confirm it's actually enabled. Sounds obvious, but I've seen techs disable it 'temporarily' and forget.

5. Assign a static IP on the phone (best quick test)

This bypasses DHCP entirely. If it works, you've proven the problem is DHCP — router side or phone side. To do it:

Long-press the network, tap Modify network (or Advanced options).
Change IP settings from DHCP to Static.
Fill in something outside the DHCP pool. If your pool is .100–.200, use .50.
Gateway: your router's IP, e.g. 192.168.1.1.
DNS: 1.1.1.1 and 8.8.8.8 — don't use the router as DNS for the test.

If you get online with a static IP, DHCP is the culprit. Keep it static as a workaround, but really you should fix the router so every new device works.

6. Reset network settings on the phone

Only if steps 1–5 didn't help. This wipes saved Wi-Fi networks, Bluetooth pairings, and mobile APN settings. On Pixel: Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth. On Samsung: Settings → General management → Reset → Reset network settings. You will have to rejoin every network after this. Don't do it casually.

If It Still Won't Connect

Run through this checklist:

Try another device on the same SSID. If an iPhone or laptop also hangs, it's 100% the router or the network. Stop messing with the phone.
Try the phone on another Wi-Fi. If it fails everywhere, the phone's Wi-Fi chip or driver is suspect. Test in safe mode before assuming hardware.
Check the 2.4 GHz vs 5 GHz SSID. Some older routers have a broken DHCP relay on one band. If the two SSIDs share a name, split them and test each.
Look for MAC filtering. Router admin → Wireless → MAC filter. If it's on and your phone isn't in the allow list, you'll never get a lease.
Check for a captive portal. Open Chrome and hit http://neverssl.com. Hotels and airports will show a login page. If nothing loads, the portal itself is broken.
ISP router in bridge mode? If someone put the ISP box in bridge mode and forgot to enable DHCP on the downstream router, no one gets an IP. That one's a classic after a router swap.

One more thing: if you're on Android 14 and only one specific SSID fails while others work, check the router's WPA3 setting. Some Android 14 builds have DHCP flakiness with WPA3-Transition mode on certain Broadcom-based routers. Drop to WPA2/WPA3 mixed or plain WPA2 and retest.

Bottom line — 'Obtaining IP Address' is a DHCP problem. Fix DHCP and you fix the error. The phone is the last thing to blame.