CODEWITHSUNDEEP
androidinstallationemulationapk
Mahe
Mahe

Reputation: 2737

Error: "Failed to install apk on device 'emulator-5554': timeout"

I have run my application using an emulator. Its taking so long time of about 5 mins to upload & 2 mins of installing my application on my emulator. After the two minutes it fails.

This is the Error console,

[2013-03-28 14:13:18 - newwaterreadingapp] ------------------------------
[2013-03-28 14:13:18 - newwaterreadingapp] Android Launch!
[2013-03-28 14:13:18 - newwaterreadingapp] adb is running normally.
[2013-03-28 14:13:18 - newwaterreadingapp] Performing     
com.example.newwaterreadingapp.MainActivity activity launch
[2013-03-28 14:13:18 - newwaterreadingapp] Automatic Target Mode: using existing     emulator 'emulator-5556' running compatible AVD 'NewAvd_water_electricity_reading'
[2013-03-28 14:13:18 - newwaterreadingapp] Uploading newwaterreadingapp.apk onto device 'emulator-5556'
[2013-03-28 14:18:31 - newwaterreadingapp] Installing newwaterreadingapp.apk...
[2013-03-28 14:20:35 - newwaterreadingapp] Failed to install newwaterreadingapp.apk on   device 'emulator-5556!
[2013-03-28 14:20:35 - newwaterreadingapp] (null)
[2013-03-28 14:20:37 - newwaterreadingapp] Launch canceled!

My application is located in E:\Projects folder. And I have increased my adb timeout to 15000ms. But still I see that my application is not loaded on to emulator.

Upvotes: 16

Views: 37702

Answers (6)

aravind kumar eruventy
aravind kumar eruventy

Reputation: 83

If your using Emulator then open the Emulator and then go to settings->Apps->Select and uninstall your Application from Emulator.

Close the Emulator

Now Right click on your project->Run as->Run Configuration-> in Target Select Automatically pick compatible device option and then click on run.

Upvotes: 0

Chetan Gaikwad
Chetan Gaikwad

Reputation: 1268

The default timeout of adb is small, so change its value If using eclipse follow the following path Window -> Preferences -> Android -> DDMS -> ADB Connection Timeout (ms)

Upvotes: 3

chedabob
chedabob

Reputation: 5881

I had the same problem and it was caused by the emulator not having enough memory. I was running the 3.0 emulator with only 512mb RAM, and it was by pure chance that I saw a tonne of OutOfMemory exceptions in LogCat coming from system processes. Upped it to 1024mb and increased VM heap to 64mb and it installed fine.

Upvotes: 0

Sagar Devanga
Sagar Devanga

Reputation: 2819

1 reason may be because your emulator is hanged shut it down and start a new one If the new emulator is also taking time to start then just restarts the eclipse It worked for me

Upvotes: 0

Harshid Vasoya
Harshid Vasoya

Reputation: 5721

If you are using Emulator then restart.

If you are using phone then reboot then phone.

Completely power down and power up. That fixed it for me.

OR

In Eclipse, select Window → Preferences, then Android → DDMS and set ADB connection time out (ms) to something longer than the default (which is 5000).

Upvotes: 6

Sulabh Gupta
Sulabh Gupta

Reputation: 642

Yon can increase your adb timeout setting in eclipse. Go to Preferences-> Android-> DDMS-> find "ADB connection time out (ms)" and give some more higher value.

Also, try to see if your emulator in connected to the DDMS. Either check from DDMS view or run "ADB devices" in command prompt

Upvotes: 24

Related Questions