Waiting for Target Device to Come Online

Question

I recently updated to Android Studio 2.3, and now when I try to run the application, the emulator does not come online. It times out after 300 seconds.

Additionally,

Answer 1

This solution works for me : Tools -> AVD Manager -> click drop down arrow -> select Cold Boot Now

Answer 2

Go to terminal and type android avd. Select your AVD and select "Edit". Make sure you do not see No CPU/ABI system image available for this target - it will show in red font at the bottom. Change the target to the one that is available or download the ABI image. Sometimes, if you create an AVD from inside Android Studio, it does not ensure this requirement.

Answer 3

I had this issue twice and tried everything in this thread with no results, I finally fixed it closing "BlueStacks" emulator.

If BlueStacks (and maybe others android emulators) are running when I run the app, by default Android Studio installs the app there, even when I never selected it as a device in AVD Manager, then Android Studio waits for an incorrect device "to come online".

Closing BlueStacks (or any other Android emulator) solved the conflict between devices for me.

I hope this info helps someone!

Answer 4

Like urupvog's answer, make sure that you aren't running any other virtual machines like VirtualBox. When I restarted my computer, AVD worked until I started Vagrant for backend development (then it wouldn't launch).

See Android emulator and virtualbox cannot run at same time for more info.

Answer 5

Finally, I solve this problem by setting the right export path in bash file:

export ANDROID_HOME=/Users/[username]/Library/Android/sdk

Answer 6

I discovered that having a running instance of Docker on my machine (OSX) prevented the Android Emulator from running (see Android Studio Unable to run AVD)

Previously, my emulator would appear to start, then fail before any device window was shown.

I also had to use 'kill -9' (as per @MarkDubya ) to get Android Studio to connect to the virtual device.