Best IT Recipes

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

The project that I was trying to run is set to minSDK level 7. I got the above error message when starting the Android-5554 virtual device (other devices work well). It runs so slowly and takes too long for the home screen to not even start. At the end, it throws this error:

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

I rebooted my computer and Eclipse several times, as well as clean projects. I also tried this. Why is the Android emulator so slow? How can we speed up the Android emulator? to fix it. Everything worked pretty well yesterday. Now it is so sluggish.

Any suggestion or help? thank

+54
android failed-installation
Jun 16 '11 at 18:24
source share
21 answers

I have come across this problem many times. Try each of these steps after each step to launch the APK file, if it does not work, go to the next step:

  • Run it again. (just try repeating it).
  • Project-> Clean (clean the project and any projects it relies on).
  • Right-click the project in the package explorer, then close it. Then close Eclipse. Then close again.
  • Same as previous step plus Project-> Clean.
  • Restart the AVD.
  • Remove AVD. Then go to the folder where the AVD is located in the Android-Sdk folder, and delete something named AVD (file plus folder). You may need to restart your computer to remove it. Create a new AVD.
+26
Jan 24 '12 at 19:27
source share

Run the following command:

adb kill-server adb start-server

It is possible that the following DeviceMonitor messages are drawn] Connection attempts: 1 DeviceMonitor] Connection attempts: 2

+15
Oct 18 '12 at 19:47
source share

Decision:

  • Run the emulator (separately) and wait for the full download.
  • Open the key lock.
  • Go to Eclipse and run the application.

Cause of the problem: The Android emulator did not load all of its libraries that handle the installation of a new application, and because of this you are running java.io.IOException: EOF

This caused me a problem.

+8
Jan 02 2018-12-12T00:
source share

you can try the following:

  1. Open the "Android Virtual device Manager" 2. Select from one the listed devices there and run it. 3. Right your Android App -> Run As -> Android Application

It worked for me. I tried this on an emulator in eclipse. It will take some time before the application is launched. For me, it took 33 seconds. Wait for the message in the console to say "Success!"

+4
Sep 26 '12 at 6:14
source share

When it shows a red record - an error, do not close the emulator - leave it as it is and run the application again.

+2
Feb 05 '13 at 12:51
source share

According to my information, there are two ways to solve the problem.

  • Remove the .apk, which regenerates again after compilation, and test the emulator again.

  • Remove the emulator and create a new emulator besides your application.

I think this will work ... if not, then please check your logCat, which will show you the actual error and try to solve it ....

I hope this helps you .........

+1
Jan 06 '12 at 9:00
source share

I was getting this problem due to coding issues. To fix this, you can (using eclipse 3.6. STS)

  • Right-click on the project, select properties, select "Resource" (first option on the properties screen)
  • In the "Text Encoding Files" section, select "Other" β†’ UTF-8
  • Click the Apply button and continue with Ok.

Project-> Clean

Project-> Run

.apk loads fine.

+1
Apr 15 2018-12-16T00:
source share

Try window-> show view-> devices-> browse menu β†’ Reset adb and run the application again.

+1
May 15 '13 at 9:48
source share

In my opinion, you should remove this AVD and create a new one for API-7. This will work fine if you don’t tell me, I will send you some more solutions.

Hello,

0
Sep 23. 2018-11-11T00:
source share
  • Remove apk from emulator.
  • Try starting the application again from Eclipse.
  • Please check the version of the Minimum Android SDK and try running it on the AVD Manager created by the emulator.

He will definitely work ...

0
Jan 16 2018-12-01T00:
source share

just close the eclipse and avd emulator and restart it. It works great

0
May 2 '12 at 6:25
source share

I had the same problem, but I tried to change the timeout of the ADB connection. I think this is the default, which is up to 5000 ms, and I changed mine to 10000 ms to get rid of this problem. If you are in Eclipse, you can do this by going through Window -> Preferences, and then into DDMS for Android.

0
Mar 06 '13 at 6:22
source share

Neither one nor the other helped me; instead, I connected my phone through the rear USB hubs (I used to use USB hubs before), and it helped me!

0
Jun 21 '13 at 7:51 on
source share

In my case, I used a tab size emulator (7 ") to test the application. But he gave me" Failed to install xxxxx.apk on device emulator-5554! "And the launch was canceled.

The only working solution for me was the size of the emulator, the size of the hopper size (1512 MB) and the heap size of the VM up to 36 .

After that, he worked like a charm.

Thank.

0
Nov 27 '13 at 5:53 on
source share

adb is very crazy, after several attempts, I found out that I was connecting to many devices (emulators and devices), so I deleted all the devices and returned to work again

0
Dec 07 '13 at 2:48
source share
  • Do not run Android emulator.
  • Right click on Project> Run As> Android Application

and then the Android emulator will automatically start

now ok

0
Feb 26 '14 at 11:29
source share

the solution is that you need to change the timeout value by at least 15000 ms (milliseconds), since milli are less than seconds, it will be in the instance .. there is no need to restart. We need to give some time for the emulator to download files to fully run. It depends on our system configurations. Go to windows->perspectives->android->DDMS->timeout up to 15000.

this will work ... change the time if it does not work. Increase the heap size and try to manipulate the minimum Api level.

0
Feb 04 '15 at 18:36
source share

I solved the problem by restarting Eclipse, then Project -> build all

0
Dec 04 '16 at 3:39
source share

Wipe Data and restart the virtual device, solve the problem in my case again.

enter image description here

0
Mar 19 '19 at 23:56
source share

In my case, I was getting these errors when installing apk on the device:

  • Error during synchronization: existing connection was forcibly closed by the remote host

  • Error during synchronization: EOF

  • Unable to open connection with: localhost / 127.0.0.1: 5037, due to: java.net.ConnectException: connection rejected: connection

This led to:

java.io.IOException: EOF

Error installing APK

Restarting the device and adb devices did not help.

I replaced the data cable and installed apk.

0
Apr 04 '19 at 9:44
source share

When this happened to me, I solved it by closing the emulator and starting the project again.

-2
Aug 13 2018-12-12T00:
source share


More articles:


All Articles