android: Failed to install .apk on device "device": timeout

Question

A few days ago I started having troubles while trying to install a .apk on my Galaxy S2. I select my phone as the target, click OK and in the Console get the following error:

Failed to install AvatarRun.apk on device 'device number': timeout Launch canceled!

Without changing anything in code and running again I can also get the error:

Failed to install AvatarRun.apk on device 'device number': device not found com.android.ddmlib.InstallException: device not found Launch canceled!

I have tried opening a command window and navigating to android-sdk\platform-tools and running:

adb kill-server adb start-server

This did not fix the issue.

This seems to just be a coincidence, but after failing many times I changed the minimum SDK in the Manifest from 10 to 7 and the .apk loaded on the next try, but has worked intermitently since and generates the same errors.

Can anyone suggest a method for finding what is causing this error?

Solution 1

After trying the fixes mentioned above, I ended up installing and reinstalling the Galaxy drivers. This didn't help. What eventually worked (so far) was to switch which USB port the Galaxy is plugged into. Once I did this everything was functioning as it should.

Solution 2

It may sound ridiculous, I tried all the ways suggested in Android error: Failed to install *.apk on device *: timeout

None of them works for me except unplugging the current cable and change for a new one.

Solution 3

There are various solutions:

1. Try changing the ADB connection timeout. The default is 5000; you should change it to 10000ms or so.

   Window -> Preferences -> Android -> DDMS -> ADB Connection Timeout (ms)

2. Try to unplug and re-plug the cable. It seems that sometimes Eclipse loses the connection with Device. Sometimes you just need to plug into other USB port.

3. You might need to kill the ADB process and restart it.

   adb kill-server and then adb start-server

Solution 4

For me, the solution is to uninstall the old apk from the phone.

View more solutions

Comments

[ishhhh]

lol @user1842396 i never expected this would work , but it did :) Thanks a lot :)

[Scott Solmer]

Did you actually have this problem, and resolve it by doing this?

[user2953067]

It worked for me. I used to get this error one after the other. Sometimes I had to wait more than half an hour to run the application once. I had 2gb memory and emulator itself was using almost all.

[u_pendra]

it's not ridiculous this happened with me also. Some time if we used other devices cable this problem may occur, not very often.

[Nikita Bosik]

I have six USB ports: (1) and (2) works perfectly, (3) and (4) allows to view phone's SD, but not to upload/debug apps (which the question stands for), (5) and (6) allows charging only. Possibly USB 2.0/3.0 support affects it somehow?

[Sonhja]

Not the most complicated one... but absolutely it solved my problem!! Haha