9 Best Android Emulators For Windows PC And Mac 2019 Edition Android emulators serve a variety of purposes: from developers testing apps to gamers playing on a large screen. Regular users also yearn to experience Android OS on a Windows PC, complimented with a mouse and keyboard.

I’m having a problem with emulator-5554, it keeps telling me it is offline.

When I do a adb devices from the command line it says

emulator-5554 offline

Even after a fresh restart, I try that command and it still says it is offline.

The problem is when I try to install .apk files to the emulator using abd install <path> from the command prompt, it tells me that it is offline, if I create another device and run that one, then try to install the .apk files, it says I have too many devices connected. So in other words, I can’t install my .apk files.

How in the world can I get rid of that damn emulator-5554? I heard that if you do a restart, it should clear all the devices, but that does not seem to be working. It is like it is getting initialized when my computer starts up. Has anyone run into this issue?

Thanks

In such a case, you can do all of the following in order to be assured that your emulator starts working again :

1. Go to cmd and type “adb kill-server”
2. Go to task manager and find “adb” in processes. If you find one, right click on it and click on end process tree.
3. In eclipse, go to Window>Android Virtual Device Manager, click on the AVD you want to launch, click on start and uncheck “Launch From Snapshot” and then click on launch.

That’s it! It will take a while and it should resolve your problem.

The way that Android detects emulators is by scanning ports starting at port 5555.

The number you see in the adb devices list (in your case 5554) will be one less than the port that adb is finding open.

You probably have a process running that is listening on port 5555. To get rid of the “offline” device, you will need to find that application and close it or reconfigure it to listen to a different port.

1 . Simply “Wipe data” to fix this issue.

The USB 2.0 Video/Audio Capture Card - S Video / Composite to USB Transfer Cable - Function as Video Grabber Card and Audio Grabber Lead from VHS Player On Windows 10 or Mac OS 10.15 The Top-Longer USB 2.0 S-Video & Composite Video Capture Cable offers an easy to use video capture solution, enabling you to grab video from an S-Video or Composite video source, as well as the accompanying 2-channel RCA audio, to your Mac or Windows computer. Diamond VC500 USB 2.0 One Touch VHS to DVD Video Capture Device with Easy to use Software, Convert, Edit and Save to Digital Files For Win7, Win8 and Win10 Elgato Video Capture - Digitize Video for Mac, PC or iPad (USB 2.0).

2 . If it doesn’t work, go to emulated device and enable developer options > enable usb debugging

This solution is for Windows.

(See @Chris Knight’s solution for Mac/Linux)

1. Start Windows Powershell:

   Start -> type ‘powershell’ -> Press ENTER

2. Run the following command: adb devices

In this case, 12b80FF443 is my physical device, and the emulator-* entries are garbage.

3. Per @Brigham, “The way that Android detects emulators is by
   scanning ports starting at port 5555.”. The port number is indicated after the emulator name (in this case 5656 and 5652). The port number to check is the emulator port number plus 1. So in this case:-

   5656 + 1 = 5657

   5652 + 1 = 5653

   So let’s see which program is using these ports. In this case, the ports to check both start with “565”. So I’ll search for ports in use starting with 565. Execute: netstat -a -n -o Select-String ':565'

4. The final field in this output is the PID (Process ID) – in this case it’s PID 5944 for both of these two ports. So let’s see what this process ID is. Execute: tasklist /v Select-String 5944. Replace 5944 with the output of the previous command:

What a surprise. It’s ADB. As noted by other answers, it could be other programs, too.

5. Now, just kill this process ID. Execute kill 5944, replacing 5944 with the PID in the previous command.

6. To confirm that the spurious emulator is gone, re-run the following command: adb devices

ADB re-starts (as it was previously killed), and it detects no more fake emulators.

In my case, I found some process that makes adb not work well.
You can try to kill some strange process and run “adb devices” to test.

It worked for me:
kill the process name MONyog.exe

I solved this by opening my commandprompt:

adb kill-server

adb devices

After starting up, ADB now detects the device/emulator.

If you are on Linux or Mac, and assuming the offline device is ’emulator-5554′, you can run the following:

Which yields the following output:

This tells me that the process id 4848 (yours will likely be different) is still listening on port 5554. You can now kill that process with:

and the ghost offline-device is no more!

Go to windows task manager and end process “adb.exe”. There might be more than 1 instances of the same process, make sure to end all of them.

The “wipe user data” option finally solved my problem. just wipe user data every time you start the emulator. This always works for me!
I use windows 8 x64 , eclipse

Do you have bluestacks installed? If you do, the background processes that it runs creates the offline device “emulator-5554”.

Go to the task manager and end all the processes with the description of “Bluestacks”

Enable USB Debugging into your emulator

1. Settings > About Phone > Build number > Tap it 7 times to become developer;
2. Settings > Developer Options > USB Debugging.

That’s it enjoy

Did you try deleting and recreating your AVD?
You can manually delete the AVD files by going to the directory they’re stored in (in your user’s /.android/avd subdirectory).

I found that the emulation environment comes up as “offline” when the adb revision I am using was not recent. I properly updated my paths (and deleted the old adb version) and upon “adb kill-server”, “adb devices”, the emulation environment no longer came up as “offline”.

I was immediately able to use “adb shell” after that point.

Try this …

1. Close emulator if it Running.

2. Start Emulator again and wait for its online.

3. enter Command in commandprompt and press ENTER key : adb tcpip 5555

(Make sure that only One emulator running at a time.)

1. adb -s emulator-5555 emu kill

2. Press Enter Key….

3. Done.

4. check devices by command “adb devices” in cmd.

If the emulator is already open or executing it will tell you is offline. You can double check on the Command Line (Ubuntu) and execute:

You must see your emulator offline, you have to close the running instance of the emulator (since the port will show as busy) and after that you can run your application. Hope this helps someone.

I tried everything but only this one works for my case:
Use SDK manager, and reinstall the system image.
Android Studio, click Configure, SDK Manager, Launch Standalone SDK Manager,
Check all “Google APIs Intel x86* System Image”, “Intel x86 Atom*System Image” and install. Then re-start Android studio.

You might have to reconfigure and wipe the virtual device with AVD Manager, make sure you choose x86 version.

Ensure that your enable ADB integration is marked;
go to Tools>Android>Enable ADB integration .

if doesn’t checked , check this option and close your virtual device and re-open it . this worked for me. good luck!!

I also had the same issue. I’ve tried all described here solutions but they didn’t help me. Then I’ve removed all emulators in the Android Virtual Device Manager and created new ones. The problem was in CPU/ABI system image configuration of the Android Virtual Device Manager. On my Windows10 machine emulator with system image x86 always is offline where emulator with system image x86_64 is working fine as expected. Just be aware of this

Simply delete and created gear avd again.It will work.

In my case the cause was that I had resumed a VM with android-x86 inside. Rebooting the VM with Android-x86 and restarting the adb server fixed the problem.

That is because of the fact that you have another virtual device installed on your machine. It might be Bluestacks as I also faced a similar problem. I uninstalled Bluestacks and then checked
adb devices
It was running fine then.

In my case, I have unchecked “GPU Host” and its worked 🙂

Just Wipe user data from AVD manager and then enter adb kill-server and adb devices.
Wiping data also saves lot of memory space in the System .

I’ll add another possible solution here, which is what worked in my case.

I found there was a process called SpiceWorksEventProcessor running, which was tying up port 5555, and apparently being read by adb as an emulator. Killing that process was what finally removed that stubborn emulator device for me.

I’m not sure what this thing is, but if you have it, it might be the cause of your offline emulator.

Cheers

on linux or mac the port thats blocked will emulator-id + 1 so 5555 so:

sudo lsof -i :5555

will show you the pid of process that are taking the port (should be the second column) so to kill it:

sudo lsof -i :5555 awk '{print $2}' xargs kill


then adb (fake) devices will no longer show on the list

All above answers didn’t helped,and then I deleted and recreated emulator all worked fine

In MAC, you can use Activity Monitor utility, since, unlike Linux, we cannot use netstat -tulpn command in MAC. Search for the running instance of the emulator, typically qemu-system-i386. Kill that instance and you will see none of the ghost emulator running.

Simplest way to grab Activity monitor utility is to use spotlight search. just hit cmd-space and type in Activity Monitor.

Tags: android