Android Studio Emulator wont start "Waiting for target device to come online"

Question

So I am currently learning how to develop android apps. I am making my first application and I have no errors but my emulator wont run my app. It is stuck on "Waiting for target device to come online". I am confused on what is wrong because It has worked before. I completely reinstalled everything and it still does not work. Not sure what to do.

Digitalize

Answer 1

Uncheck then recheck 'Enable ADB Integration' from the Android Studio 'Tools - Android' menu and it will work.

Xenophon

Answer 2

Jonothan's solution directed me this one and it worked for me as the one that Jonathan mentioned didnt work for my case.

1. Close the emulator (if running).
2. Open the Android Virtual Device Manager (AVD Manager).
3. Click the dropdown arrow under 'Actions' (far right).
4. Select 'Wipe Data' (This is the additional step that I used)
5. Select 'Cold Boot Now'.

After the Emulator boots back up, you can run the application and this emulator will be connected and you can use it.

Hampden

Answer 3

I ran into this same issue and the problem was that Quick Launch caused the emulator to get out of sync with the IDE/adb for some reason.

Here are the steps I took to fix the problem:

1. Close the emulator (if running).
2. Open the Android Virtual Device Manager (AVD Manager).
3. Click the dropdown arrow under 'Actions' (far right).
4. Select 'Cold Boot Now'.
5. After the Emulator boots back up, click Run app and select the running Emulator.

Gusgusba

Answer 4

In my case I opened Android Studio and then, in the menu, navigated through Tools -> Android -> AVD Manager.

As seen at the image below, I had a message that "Android Emulator is incompatible with Hyper-V."

I have followed the steps suggested (as below):

Unfortunately, you cannot have Hyper-V running and use the emulator. Here is what you can do:

1. Start a command prompt as Administrator
2. Run the following command: C:\Windows\system32> bcdedit /set hypervisorlaunchtype off
3. Reboot your machine.

After the system reboot, I opened the same window (AVD Manager), and a next warning was available, to install HAXM:

After that, the emulator started, but very slow. The next suggestion was to install a better emulator using x86 which gives better performance in my machine (10x faster):

Google Play Intel x86 Atom System Image (system-images;android-24;google_apis_playstore;x86)

Michaelamichaele

Answer 5

My case, I used to use android emulator well. But when I tried to run adb by Android Studio one day, it just showed 'waiting for target device ...', and the emulator disappeared suddenly.

After checking some, and then I knew that docker was the reason, I think Docker (or Docker Kinetics) and android emulator conflict together on osx (mac).

Turning off Docker, I can use android emulator as usual.

Gastrointestinal

How do you turn off the docker in Mac. I have no idea what a Docker is – Cupellation

Answer 6

I solved this by turning off the emulator using the power off button, not using the close (x) button (avoiding saving emulator state message). Then launching again the emulator worked for me.

Rocca

Answer 7

I ran into this issue after installing Android Studio Canary and trying to run emulators I had already created.

Nothing I found online worked, but I finally managed to connect after I created a new Virtual Device.

Rosaleerosaleen