2

whenever i start eclipse or android studio an emulator is constantly running in the background. when i try to turn it off it restarts again immediately. no matter if i work with a real device or an emulator i have created, this other emulator is not stoppable. in the android debug monitor this emulator is listed as emulator-5554 - Online - ? [2,3,4, debug] (Version API10). i never created or used this emulator, and there is no place to find and delete it.

actually i am able to work with eclipse or android studio with that annoying emulator, but it seems to slow down the performance and i would like to get ride of it.

richard
  • 724
  • 2
  • 14
  • 36
  • What host? On linux you could use the /proc/pid#/fd directory to figure out what avd it has open and remove that, identify the parent responsible, etc. – Chris Stratton Mar 26 '14 at 12:00
  • i use windows 7 (64 bit). – richard Mar 26 '14 at 14:52
  • Can you actually find an emulator process running in task manager or whatever windows calls it these days? – Chris Stratton Mar 26 '14 at 14:55
  • in the task manager i only can find the adb.exe running. if i end it the annoying emulator also ends, but then starts again. – richard Mar 26 '14 at 15:02
  • If you are not finding an emulator process, then likely this is just a "ghost" in the adb devices report due to some minor bug, and not an actual emulator. – Chris Stratton Mar 26 '14 at 15:04
  • thanks, seems to be realy something like that. i now realized that i can see an emulator-x86.exe in the taskmanager when i start an emulator intentionally, but not when this annoying one runs in the background. anyway this background emulator also produces constantly logcat messages, like following ones: 2524-2531/system_process E/PGA﹕ PgaSocketWriteAllHdipc: hd_ipc_send() failed 2524-2531/system_process W/PGA﹕ ctlSwapBuffers(133): Host Connect failed, err = -1(0xffffffff) – richard Mar 26 '14 at 15:27

3 Answers3

1

Strange, but should be able to kill a "hidden" emulator instance from the command-line by connecting to its console, i.e.:

telnet localhost 5554
kill

Replace 5554 with your emulator instance's number.

Digit
  • 2,073
  • 1
  • 13
  • 10
  • thanks, but the hidden emulator suddenly disappeared. i don't know what solved the problem because i tried a lot of things without direct effect. so i can not check if your solution would have solved the problem. but if it happens again i will check it out. – richard Mar 28 '14 at 12:15
  • cannot connect to that emulator via telnet – Dane411 Dec 01 '14 at 16:03
1

Were you using BlueStacks back then by any chance? It uses the port 5554, and that might have been your problem too! It happened to me as well and found the solution in another question:

Eclipse Android Emulator-5554 is always displayed

Community
  • 1
  • 1
Dane411
  • 823
  • 1
  • 13
  • 27
0

I use AndroVM. For me its perfect.

Todo is:

  • install VirtualBox first
  • download AnroVM
  • file will open in VirtualBox
  • start the machine and set USB debug on (settings >> dev. options)
  • in commandprompt goto your "sdk\platform-tools" type adb connect 192.168.15.101

When it's ok you will see your device in Eclipse.

edit: When your Eclipse is not working well, just download a new bundle again

Community
  • 1
  • 1
Johan Hoeksma
  • 3,534
  • 5
  • 28
  • 40