When mobile data is on but Google sign-in won’t complete (spins, loops, or says “can’t connect”), the fix is often a small privacy or network setting—not your password. Below is a privacy-safe two-path guide: Android apps first, then the mobile web.

Padlock blocked by cellular signal icon on duotone background

Keep your personal data where it belongs: on your device.

Before you start: avoid “testing” by uninstalling security apps, installing random VPNs, or turning off screen lock. You usually don’t need any of that.

Choose your path based on where sign-in fails.

Path A: you’re signing in inside an Android app (Gmail, YouTube, Maps, Drive, Play Store).

Path B: you’re signing in on the web (Chrome/Firefox/Samsung Internet) to accounts.google.com or a “Sign in with Google” page.

If both fail, follow Path A first (it fixes more root causes).

1. Path A (Android apps): confirm it’s a mobile-data-only problem

Do this quickly so you don’t chase the wrong issue.

  • Turn Wi‑Fi off, keep mobile data on, then try opening a simple non-Google site in your browser (example: a news site).
  • If nothing loads, you have a carrier/data issue (skip ahead to section 4).
  • If other sites load but Google sign-in fails, continue below.

Smartphone with app grid and cellular data icons

2. Path A: check the privacy-safe blockers first (no resets yet)

These are common and reversible, and they don’t require deleting accounts or wiping storage.

  • Data Saver: Settings → Network & internet → Data Saver. Turn it off temporarily, then retry sign-in. (You can turn it back on after.)
  • App-specific mobile data: Settings → Apps → (the affected app) → Mobile data & Wi‑Fi (or Data usage). Make sure Background data and Unrestricted data aren’t blocking it.
  • Private DNS: Settings → Network & internet → Private DNS. If it’s set to a custom provider, switch to Automatic for testing. (Some DNS filters break Google auth endpoints.)
  • VPN / “always-on” VPN: Settings → Network & internet → VPN. Disconnect and retry. If you use a VPN for privacy, just test without it; don’t uninstall it.
  • Firewall/ad-blocking DNS apps: If you run a local VPN-based blocker, pause it briefly and retry sign-in. Re-enable it after testing.

If sign-in works after one of these toggles, re-enable your privacy tools one by one until you find the specific setting that conflicts.

3. Path A: fix time, SIM, and Google services without sharing extra data

Google sign-in is sensitive to time drift and to stale system tokens. You can address both without “clearing everything.”

  • Set time automatically: Settings → System → Date & time → enable Set time automatically and Set time zone automatically. Then restart the phone.
  • Toggle airplane mode: Turn on Airplane mode for 15 seconds, then off. This forces a clean mobile network attach.
  • Reseat mobile data for the app: Force stop the affected app (Settings → Apps → (app) → Force stop), then reopen it.
  • Clear cache (not storage) for Google services:
    • Settings → Apps → See all apps → Google Play services → Storage & cache → Clear cache
    • Repeat for Google (the Google app) and the specific app failing sign-in

Avoid “Clear storage” unless you’re ready to sign back into apps and re-download offline data.

4. Path A: carrier/mobile network checks that keep your privacy intact

If Google auth fails only on cellular, the network path (APN, IPv6, captive filtering) can be the trigger.

  • Check APN: Settings → Network & internet → SIMs → Access Point Names. If you didn’t set it yourself, don’t “experiment” with random APNs. Use your carrier’s official APN values.
  • Disable “2G” (if available): Settings → Network & internet → SIMs → Allow 2G. Turn it off to avoid insecure fallback and unstable connections in some areas.
  • Try a different DNS mode: If Private DNS on Automatic fails, try setting it to a reputable provider you already trust. If you’re unsure, keep it on Automatic.
  • Test another SIM or eSIM line (if you have access). If another line works, it’s likely carrier-side filtering or account provisioning.

If other services work but Google sign-in consistently fails on one carrier only, it can be a carrier routing issue. In that case, contacting the carrier with timestamps (not screenshots of your account) is usually enough.

5. Path B (mobile web): stop sign-in loops without nuking cookies

Web sign-in issues on mobile data are often cookie, redirect, or “secure DNS/VPN” mismatches. You can test safely without deleting all browsing history.

Cookie and refresh icons around a globe symbol

  • Use a private tab once: Open an Incognito/Private tab and try signing in. If it works there, the issue is likely cookies/site data in the normal session.
  • Clear site data for Google only:
    • In Chrome: Settings → Privacy and security → Site settings → All sites → find google.com (and the site you’re signing into) → Clear & reset
  • Disable “Use Secure DNS” temporarily: In Chrome: Settings → Privacy and security → Use Secure DNS. Turn it off for a quick test, then decide whether to re-enable.
  • Turn off “Lite”/data compression features if your browser has them. Some proxies interfere with auth redirects on certain networks.
  • Try a different browser just for testing: If Chrome fails, test Firefox or Samsung Internet. Don’t install unknown “privacy browsers” you don’t trust.

If the web login works on Wi‑Fi but not mobile data, it points back to Path A section 2 (Private DNS/VPN) or section 4 (carrier path).

6. Stop-points: what not to do (and when support is the right move)

These steps often create more problems than they solve.

  • Don’t factory reset to fix a mobile-data sign-in issue unless you’ve confirmed it’s device-only and you’ve exhausted the checks above.
  • Don’t remove your Google account as a first step. It can break app data sync and 2FA prompts.
  • Don’t disable your lock screen or weaken security to “make sign-in easier.” If sign-in requires less security, that’s a red flag.

Consider contacting support (carrier first, then Google) if:

  • Google sign-in fails on multiple devices using the same SIM/line.
  • It fails only in one location/cell area for days.
  • You see consistent errors like “can’t reach server” only on cellular, while other sites load normally.

Final thoughts

Most “Google sign-in won’t work on mobile data” cases come down to one privacy/network toggle: Data Saver, Private DNS, or a VPN-style blocker. Test those first, and keep changes minimal and reversible.

If you find the exact setting that breaks it, you can usually keep your privacy tools—just adjust the one conflicting piece.