Why I received a message about the disabled emulator-5554

When I run my Android emulator, it takes several times, then it will show a message about the 5554 emulator disabled. Can someone tell me what the problem is?

+29
android emulation
Feb 25 '10 at 10:32
source share
11 answers

Open the Android device view in the Eclipse IDE. Then click the Reset Adb menu item in the device menu. Then run the application again. enter image description here

+30
Jan 02 2018-12-21T00:
source share

I solved this by following these steps:

  • Run emulator
  • Store the emulator (no matter what the error)
  • Make sure the emulator main screen appears.
  • go to the window β†’ Show prospects β†’ DDMS β†’ In the "Devices" panel β†’ in the "Corner" drop-down menu
  • Reset adb

Hope this helps you.

enter image description here

+12
Apr 18 '13 at 4:50
source share

Restart emulator

Select & Right Click on Android Project Run Configurations Go to tab Target Enable option Wipe User Data on Emulator launch parameters Run Application 

If you are using a different IDE, you can restart your emulator using the -wipe-data flag to delete all temporary files created by the emulator in previous runs.

+11
Sep 27 '11 at 8:18
source share

Please note that to search for the "reset adb" option, you must click the down arrow located next to the camera to the right of viewing devices. The arrow may appear gray, like everything else on the toolbar. Previously, a few hours were used to successfully launch the emulator, due to constant disconnections, until I found this option and where it was buried.

+5
Aug 6 2018-12-12T00:
source share

Today I faced the same situation: I started the emulator from the AVD manager, and after starting it appeared offline in DDMS, resetting ADB did not help - it tried to run several times and led to the same with an offline status. Another symptom was that the emulator did not respond to clicking on it. In the end, I realized that the reason is because the emulator saved the last execution state, which may have crashed. To fix this, I unchecked the "Run from snapshot" checkbox when the emulator started. And it worked for me.

+3
01 Oct '14 at
source share

See Related Post

Another related post

And further

This worked on Linux for me:

  • Launch the emulator (Wait until the emulator main screen loads)
  • Click Window> Open Perspective> DDMS
  • In the Devices panel, click the drop-down menu> Reset adb
  • Run project
+2
Sep 05 '13 at 5:44 on
source share

Seems to be problem 1.6

Upgrade to 2.1 and it will disappear.

0
Feb 26 '10 at 6:56
source share

enter image description here

Goto β†’ Prefrencess β†’ Android β†’ DDMS β†’ 1.visible checkbox Use ADBHost, 2.ADB Connection timeout up to 1,000,000, 3.Method Profile Buffer size changes from 8 MB to 20 MB.

This is the solution. A developer who has a lower end machine will run into this problem. Please check it out.

0
Feb 21 '14 at 20:39
source share

Try to start the emulator from AVD Manager. Wait until you get the main screen, and then run the project.

0
30 Oct '14 at 19:48
source share

This happened to me, apparently another application (VideoStream in my case) used the same port as adb. To fix this, use PowerShell (with elevated permissions) to find the process using the port where you get the error message:

 Get-Process -Id (Get-NetTCPConnection -LocalPort portNumber).OwningProcess 

You will know the PID because it is displayed in the Id column.

Then open the task manager and right-click on the toolbar at the top (Name, Status ...) and enable the PID to view the process ID. Then find the PID you got during the search and kill it.

This fixed it for me.

0
Jan 15 '19 at 10:04
source share

The problem that I discovered is that the project does not have the corresponding virtual device defined for it in the AVD manager.

So, the recommended steps in eclipse are:

  • Go to the "Project" section β†’ Properties-> Android.
  • In the right pane, see which row is marked in the target assembly of the project.
    Remember the number of the target platform that appears on the selected line.
  • Go to the Windows section β†’ AVD Manager.
  • Check the list of existing Android Android devices for a device that matches the platform level and API set for your project (see step # 2 above).
  • If there is no line containing AVD for your platform (as I suspect), add it using the "Create" button.
  • The Create New Virtual Android Device window opens. set a new device name. in the "Target" selection box, select the correct platform for your project.

Enjoy the emulator again!

-3
Dec 13 '11 at 10:40
source share



All Articles