Back to Home
android-system-errors

110

Error 110: Connection Timed Out

9 views
Updated March 17, 2026

Quick Fix

Check your Wi‑Fi, restart the router, and reboot your phone. If it still fails, clear the DNS cache via Settings > Apps > System > Storage > Clear Cache.

What it Means

Error 110 indicates that the Android device couldn't establish a network connection within the allowed time. It usually shows up when the phone tries to reach a server but the request times out.

Possible Causes

  • 1
    Weak or unstable Wi‑Fi signal
  • 2
    Router firmware issues
  • 3
    DNS resolution problems
  • 4
    VPN or proxy interference
  • 5
    Outdated network drivers

How to Fix

    Step-by-Step Solutions

    1. Restart Wi‑Fi Router

      Power cycle your router to clear temporary glitches and refresh the IP lease. This often resolves timeout errors caused by router hiccups.

    2. Forget and Reconnect

      On your phone, go to Settings > Wi‑Fi, tap the network, choose Forget. Then reconnect and re-enter the password. This forces a fresh handshake.

    3. Clear DNS Cache

      Open Settings > Apps > System > Storage. Tap Clear Cache to flush DNS entries. Alternatively, use ADB: adb shell ndc dns clear.

      adb shell ndc dns clear
    4. Disable VPN/Proxy

      If you use a VPN or proxy, temporarily disable it. VPNs can add latency and cause timeouts.

    5. Update Firmware

      Check for router firmware updates via its admin panel. Also ensure your Android OS is up to date in Settings > System > Advanced > System update.

    Commands You Can Try

    adb shell ndc dns clear
    adb shell netcfg

    Technical Details

    Error TypeRuntime
    SeverityMedium
    Platformandroid-system-errors
    App VersionAll

    Still stuck?

    Pro tips

    • Use a static IP to avoid DHCP delays
    • Enable IPv6 if supported
    • Set DNS to Google 8.8.8.8 or Cloudflare 1.1.1.1

    If the error persists after all the above steps, contact your carrier or the device manufacturer’s support, as the issue may be hardware or a deeper software bug.

    If these solutions didn't help, try searching our database for similar issues.

    Contact Support