Introduction

The error Failed to install .apk on device: timeout usually means Android Studio or adb started the install but never completed it within the expected time. The root cause is often not the APK itself. It is usually a slow or unstable connection, a device-side install prompt, low storage, or an overloaded emulator or phone.

What Is Timing Out

When you click Run in Android Studio, the IDE typically builds the APK, connects through adb, pushes the package to the device, and asks the package manager to install it. A timeout can happen at any stage, but the most common ones are:

• 'adb connection problems over USB or Wi-Fi'
• the device being too slow to process the install
• the package manager waiting on user confirmation or cleanup
• very large debug builds taking too long to transfer or optimize

That is why the same project may install fine on one device and repeatedly time out on another.

Start with the Device and ADB Connection

Before changing Gradle settings, confirm the device is healthy and reachable.

1adb devices
2adb kill-server
3adb start-server
4adb devices

If the device appears as unauthorized, unlock the phone and accept the debugging prompt. If it disappears and reappears, the USB cable or port may be unstable.

On physical devices, use a reliable USB cable and avoid low-quality hubs. On emulators, a busy host machine can slow installation enough to trigger timeouts.

Check Storage, Prompts, and Existing App State

Android may refuse or delay installation if there is not enough free space, if an old app version conflicts with the new signature, or if the device is waiting on an install confirmation dialog.

Useful checks:

adb shell df -h /data
adb uninstall com.example.app
adb install -r app-debug.apk

If uninstalling the old package fixes the problem, the previous install state was likely the blocker. If the device storage is nearly full, installation can stall while the package manager tries to free space or optimize code.

Also watch the device screen. Some devices display confirmation prompts or security dialogs that pause the install flow while the IDE simply waits.

Reduce the Debug Install Cost

Large multi-dex builds, heavy asset bundles, and slow emulators all make install times worse. For development, it helps to keep the debug build smaller and simpler.

For example, you can inspect the final APK size:

./gradlew assembleDebug
ls -lh app/build/outputs/apk/debug/app-debug.apk

If the APK is unusually large, review included assets, debug-only dependencies, and whether you are shipping unnecessary resources in the development variant.

Keeping Android SDK platform tools up to date also matters, because newer adb versions often improve device communication and install reliability.

Use Logs Instead of Guessing

If the timeout keeps happening, collect direct evidence from the device and package manager instead of repeatedly retrying from the IDE.

adb logcat | grep -i package
adb shell pm path com.example.app
adb install -r app/build/outputs/apk/debug/app-debug.apk

Running adb install manually helps separate IDE issues from device issues. If the manual install also hangs, the problem is below Android Studio. If the command succeeds while the IDE fails, the IDE deployment configuration may be the culprit.

When Increasing Timeouts Helps

A timeout setting can be a temporary workaround, especially on slow emulators or very large builds, but it should not be your first move. If the underlying problem is an unstable cable, full storage, or a hung package manager, a longer timeout only hides the symptom.

Use longer timeouts only after you have ruled out the basic transport and device issues.

Common Pitfalls

The most common mistake is assuming the build failed when the real problem is the device connection. ADB instability is far more common than a broken APK in this specific error.

Another mistake is ignoring the device screen. Security prompts, install confirmations, or low-storage warnings can block the install while the IDE just reports a timeout.

It is also easy to keep retrying on a slow emulator with low host resources. If the machine is CPU or memory constrained, installation and dex optimization can take much longer than expected.

Summary

• The timeout usually happens during ADB transfer or device-side package installation.
• Restart ADB, verify the device connection, and use a stable USB path.
• Check device storage, remove old conflicting installs, and watch for on-device prompts.
• Test with manual adb install to separate IDE issues from device issues.
• Increase timeouts only after fixing connection and device health problems.