The key distinction: Connecting to a Wi-Fi access point and reaching the public internet are two different events. A phone can show a strong wireless signal while the router has no working upstream connection, its DNS resolution is failing, or a sign-in page is waiting. The fastest fix comes from isolating which part of the path has failed.
Use three comparisons before changing settings
- Test a second device on the same Wi-Fi. If both fail, investigate the router, modem or internet service before altering the Android phone.
- Test the affected phone on a different network. If it works elsewhere, your original Wi-Fi network is the stronger suspect.
- Compare one website with several others. A single inaccessible domain is not the same as an internet-wide outage. Also check whether a browser redirects to a captive-portal login page.
Fixes ranked from least disruptive to most disruptive
Start by switching Wi-Fi off and on, confirming airplane mode is off and restarting the phone if needed. Next, disconnect and reconnect to the network. A router restart may help when several devices are affected, but make sure you have permission to restart shared networking equipment.
If only one saved network remains problematic, forget that network and join it again with the correct password. This clears the saved connection settings but requires re-entering credentials. Keep network-wide resets as a later step: they can remove saved Wi-Fi and Bluetooth configuration, and menu wording differs across Android versions.
Where DNS fits into the diagnosis
DNS turns domain names into network addresses. If DNS lookups fail, familiar websites may not open even though the wireless link itself is connected. However, changing a DNS provider cannot repair a broken modem, expired internet service or an incorrect captive-portal login. Before trying another resolver, distinguish a name-resolution symptom from a broader routing or connectivity problem.
Android’s Private DNS setting can also affect connectivity on some networks. If a custom hostname has recently been entered, verify its spelling and availability. Do not turn off security settings permanently merely to make an unfamiliar public hotspot work; use temporary diagnosis and restore appropriate protection.
Small decision table
- All devices fail: check router status, service provider and local outage notices.
- Only one phone fails everywhere: check Android updates, VPN settings, date/time and installed network-affecting apps.
- Only one Wi-Fi network fails: try reconnecting, captive portal and router configuration.
- Websites fail by name but other connectivity works: investigate DNS resolution, without assuming DNS is the only cause.
Read the sources
Google’s Pixel Wi-Fi troubleshooting guide details the device-versus-network approach. Google Public DNS documentation explains the name-resolution layer. For additional Android-oriented checks, consult SSMApps’ Wi-Fi troubleshooting walkthrough.
Editorial perspective: Diagnose before resetting; an unnecessary reset can erase useful settings without fixing the root cause.
Selected sources
Links lead to the original publishers. Their content and privacy practices are independent of Zaleyo.
- Google Pixel Wi-Fi troubleshooting (support.google.com)
- Google Public DNS documentation (developers.google.com)
- Android Wi-Fi troubleshooting walkthrough (ssmapps.com)