Android: the emulator is often turned off (disabled)!

Question

Once, right after I launched a new emulator, I tried to download my apk for the first time, but I got "emulator: ERROR: user image used by another emulator. Aborting".

I launched a new emulator and left it alone, a few minutes later, DDMS showed "device offline."

I had to restart a new one, you know, wasted minutes.
It really bothers me that I keep getting this error and slow down debugging.
How to fix it?

Answer 1

If the emulator is still alive, you can say that adb connects to it via tcp (which I believe that it does anyway, only it usually uses a class called "emulator" and will now get ip: port one)

Some time has passed since I had to do this, but I think that if you used the 5554 emulator, you would connect one port above to your development machine loop, that is:

adb connect localhost:5555 

If it works, adb devices will show that the eclipse should see it as a deployment option

The "in use" problem sounds like an outdated lock file, possibly left after a crash

Answer 2

I have another solution. try it

Launch Configurations> Goal> Clear User Data> Run

Answer 3

In my case, this happens when I have another process listening on the emulator port.

eg. if i see:

 emulator-5554 offline 

that means something uses port 5554

Answer 4

Manually delete the following folders:

C: \ Users \% UserName% .android \ AVD \ AVD2.1.avd \ cache.img.lock

C: \ Users \% UserName% .android \ AVD \ AVD2.1.avd \ UserData-qemu.img.lock

this always works for me .: 3

Answer 5

On Arch Linux x64, I had a similar issue that led me to this question. With Eclipse, the emulator-5554 window freezes and Eclipse prompts me to launch a new one. In the next dialog, emulator-5554 reported that it was disabled for an unknown purpose. If I started a new instance, it would be emulator-5556 . This problem continued with Eclipse restarts and logout cycles! In addition, killx will close the window, but the process is still running.

So, find the emulator64-arm process id (not emulator-arm !):

 ps ax | grep "emulator64-arm" 

... and then just kill -9 it:

 sudo kill -9 6728 

... where 6728 was his PID. This completely disables the emulator, so Eclipse may try to start it again.

Answer 6

Open the android debug monitor window by typing "monitor" in cmd, then select the device in the monitor window, click the down arrow as shown in the figure, then just click on the reset tab, on which you will get an Internet connection.

Answer 7

It was kind of weird

I had this problem, automatically stopped the localhost: 5554 emulator after starting the application.

I did not know why this was happening, but today I did something else, I could start as normal.

What I did as another is to change the presentation of Eclipse ADT. I ran the application from Debug, and now I executed it from a Java perspective, it worked, I don’t know the reason, I had to share it, voice some .. this answer, but I decided to do it without deleting and not creating my android again virtual device.