Failed to install OlaMundo.apk on device 'emulator-5554': EOF

Question

Failed to install OlaMundo.apk on device 'emulator-5554': EOF

Navigation

#1 by (3 votes)

2

Occasionally when trying to run my application in the emulator I run into the error:

[2014-07-23 20:59:09 - OlaWorld] Failed to install OlaWorld.apk on device 'emulator-5554': EOF
  [2014-07-23 20:59:09 - OlaWorld] java.io.IOException: EOF
  [2014-07-23 20:59:09 - OlaWorld] Launch canceled!

After that when I try to run the application again Eclipse opens a new emulator instead of using the emulator that is already open. If I force Eclipse to ask me which device to run on, it opens that window to choose, though no device is already running ( Choose a running Android device ). It is as if the emulator that is open is no longer useful, but it is very time consuming to open a new emulator every moment and I would like to solve this.

How to prevent this from happening? If it can not be prevented from happening, then how to recover the old emulator so that I do not have to open a new one?

Increasing the " ADB connection timeout " did not make any difference.

I'm using the Eclipse ADT Bundle version "adt-bundle-windows-x86-20140702", downloaded from Android Developers .

android eclipse avd

asked by anonymous 24.07.2014 / 02:24

1 answer

css selector syntax for deleting td element with jQuery How to add a class to a li when the person is on the link page accessed?

score 3 · Accepted Answer

This should happen because the emulator (in most cases) is too slow, and when adb finishes installing and sends the commands to start the installed app the emulator is not ready yet and therefore can not open the app. But probably the app has been installed, and you can open it by clicking on its icon inside the emulator.

As for Wakim's tip, I'd tell you the same thing, give the Genymotion a try, it's a lot faster, some very cool functions like for example simulating the percentage of the battery or charging battery for example, and it's free.

Thanks!