CODEWITHSUNDEEP
android-studioandroid-emulator
user1154390
user1154390

Reputation: 2429

Error while waiting for device: Time out after 300seconds waiting for emulator to come online

I have been trying to use android studio 2.0 emulator but I can not run my App on the Emulator. When I Run my App it shows the emulator with following details:

Hax is Enabled

After that it takes to next TAB Launching app and shows Waiting for the device to Come online After that it shows error: Error while waiting for device: Time out after 300seconds waiting for emulator to come online.

What I have tried so far.

What's the solution?

I haven't found any solution yet. I opened new issue on 4th may 2016 because it is known bug in previous versions. Please report on the following link if you have same issue.

https://code.google.com/p/android/issues/detail?id=209095

Upvotes: 94

Views: 191440

Answers (27)

Smaillns
Smaillns

Reputation: 3127

In my case I had to do the following

lsof -i :5037
kill <PID>

then you just need to restart the adb

/Users/.../Library/Android/sdk/platform-tools/adb start-server

That should resolve the issue encountered when trying to install the apk

Upvotes: 0

Diego Salvati
Diego Salvati

Reputation: 63

I have faced the same issue and after having tried basically all the solutions found out there, this was what worked for me:

Go to Preferences -> search for Emulator -> Uncheck Launch in a tool window

Upvotes: 0

shapoor molaee
shapoor molaee

Reputation: 101

I encountered the same problem, when I tried to run it from the terminal by following command

~/Documents/development/android/SDK/emulator/emulator -avd Resizable_Edited_API_31

I encountered the following error

qemu-system-x86_64: -chardev socket,port=36201,host=::1,nowait,nodelay,ipv6,id=modem: address resolution failed for ::1:36201: Name or service not known
^C^X^Z

And I realized that I had disabled ipv6 in the system, after I activated it, avd ran for me.

Upvotes: 0

Ebrahim Momin
Ebrahim Momin

Reputation: 78

To fix it I went to Tools > SDK Manager > SDK Tools and updated Android SDK Build-Tools 31

  • Somebody said they needed to do a cold boot afterword

Upvotes: 0

Leo
Leo

Reputation: 930

Go to Device Manager (Tools -> Device Manager)

Wipe the data of your device and try starting it again.

enter image description here

Upvotes: 18

Abdel Moumen Abdel Raouf
Abdel Moumen Abdel Raouf

Reputation: 127

I experienced a similar issue, i fixed it by deleting the Android emulator then created a new one with a higher API level.

In my case I've selected API-30

Upvotes: 0

Mahdi Safari
Mahdi Safari

Reputation: 298

If you install HAXM and still doesn't work go to this link below and install Hyper-V. Next, restart your computer. If It doesn't work again remove the emulator and reinstall again with a high API.

https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?pivots=windows

Upvotes: 0

Mehrshad Zakerian
Mehrshad Zakerian

Reputation: 391

I almost tested all solutions in this topic and other pages. Finally after lots of searching I found the issue!

I had to enable Hyper-V on my system (If your system does not support Hyper-V you need to install HAXM instead).

In this link you can read about enabling Hyper-V and HAXM: https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?pivots=windows

Upvotes: 0

LIU YUE
LIU YUE

Reputation: 1997

try to change this solved my issue, you may other graphics options, and change to a lower resolution model enter image description here

Upvotes: 2

Shivam Sompura
Shivam Sompura

Reputation: 135

Sadly none of the solutions worked for me! I solved my problem by uninstalling existing APK from my phone and it all started working perfectly!

This started happening after I've updated android studio to latest version.

Upvotes: 0

Mathieu
Mathieu

Reputation: 1713

Restarting ADB server works for me, but no need to go for it from command line.
Ctrl + Maj + A -> Troubleshoot Device Connections -> Next -> Next -> Restart ADB Server

enter image description here

Upvotes: 0

Liker
Liker

Reputation: 2267

I had the same problem. I removed virtual device and run app on my phone - worked well. To remove virtual device: Click icon "AVD Manager" in Android Studio, select virtual device and in context menu click "Delete". Then turn on on the phone "Developer mode". Connect phone via USB to the laptop.

Upvotes: 0

Matthew Wilcoxson
Matthew Wilcoxson

Reputation: 3622

These are the steps I took (I'm on Linux).

  • Switched to Software rendering (works but is too slow)
  • Tried running on commanline and an error displayed.
  • Forced emulator to use the system graphic drivers.

First, as @jlars62 suggested, I tried using Switching the Graphics to "Software" and this DID work. However, the performance is far to slow so I dug a little deeper.

Then I tried running the device from the console, as @CaptainCrunch suggestion. (My device was created in Android Studio; emulator in the Sdk may be in a different place on your system)

$ ~/Android/Sdk/emulator/emulator -avd Nexus_6_Edited_768Mb_API_23

For me this produced the following error:

libGL error: unable to load driver: i965_dri.so 
libGL error: driver
pointer missing libGL error: failed to load driver: i965 
...

Which I tracked down (on ArchLinux) to mean it's using the wrong graphic drivers (Android Sdk comes with it's own). You can force the system ones on the commandline with -use-system-libs:

$ ~/Android/Sdk/emulator/emulator -avd Nexus_6_Edited_768Mb_API_23 -use-system-libs

To force Android Studio to do this you can intercept the call to "emulator" like so (See Mike42) :

$ cd ~/Android/Sdk/tools/
$ mv emulator emulator.0
$ touch emulator
$ chmod +x emulator

In the new emulator file add this:

#!/bin/sh
set -ex
$0.0 $@ -use-system-libs

Upvotes: 1

Emiliano Sangoi
Emiliano Sangoi

Reputation: 921

I had the same problem. I'm using Android Studio 2.3 and Debian 9.1 Stretch 64 bits. In my case, the problem was in default settings established in graphics aceleration configuration. To solve the problem I opened the AVD Manager, then I selected the device and I opened config file (config.ini) selecting "Show on disk" option whitin "Actions" column. Within the file, I changed the value setted in hw.gpu.mode variable from mesa to swiftshader. After saved the changes, the emulator started without any problems. More options availables could be found on this link.

Upvotes: 1

jlars62
jlars62

Reputation: 7353

The solution for me was setting the Graphics option on the Android Virtual Device to Software instead of Automatic or Hardware.

I believe this was the solution because I am working on a windows machine that did not have a dedicated graphics card.

Upvotes: 82

pchaitat
pchaitat

Reputation: 159

My problem went away after I shutdowned VirtualBox on my machine.

One thing I know is that Linux KVM can't get along with VirtualBox well.

Upvotes: 10

Zon
Zon

Reputation: 19880

Android API Version for application and device should match. Check if minSdkVersion and targetSdkVersion in Gradle Scripts - build.gradle (Module: app) correspond device API.

Also low versions (e.g. API 15) result in ide-emulator link failure, inspite of applicatrion and device versions match.

Upvotes: 0

Mario
Mario

Reputation: 2639

Also something that can go wrong: Make sure you exit Docker for Mac (possibly all other kind of docker installations as well).

Upvotes: 10

Shankar
Shankar

Reputation: 150

I found a workaround even though I am not sure why this is happening.

Go to Menu->Tools->Android and uncheck the option Enable ADB Integration Run the application. Now the emulator will be launched, but app will not run. Once the emulator is fully launched, check the Enable ADB Integration option and re-run the app. Now the app will be launched in the already running emulator.

Upvotes: 8

Ayodeji Jayeoba
Ayodeji Jayeoba

Reputation: 31

I experienced a similar issue with android studio 2.2. Re-installing a new system image didnt resolve for me. Then found this solution on this link.

unchecking the Enable ADB Integration option and checking it back seem to resolve it for me. I hope this helps someone out there.

Upvotes: 0

CaptainCrunch
CaptainCrunch

Reputation: 1403

You could try :

  • run the emulator from the console manually and see whether adb can connect("see") it from android studio. Does it run at all?
  • delete avd , recreate a new one for testing, always a good idea in 2.0. lot's of stuff is changing ( instant run etc.)
  • what does adb say from console ? adb kill-server , adb start-server, start an emulator, then adb devices does it list your emulator ?

Upvotes: 4

BOGI VINAY Kumar
BOGI VINAY Kumar

Reputation: 11

I have faced the same issue you have mentioned and could solve it by just deleting the current avd and creating a new one.It's working perfectly well now.

Upvotes: -1

Robert Ruxandrescu
Robert Ruxandrescu

Reputation: 667

Usually, deleting the current emulator that doesn't work anymore and creating it again will solve the issue. I've had it 5 minutes ago and that's how I solved it.

Upvotes: -1

Saman Salehi
Saman Salehi

Reputation: 1034

This error is gone for me by remove the AVD and create a new one.

after some compile and clean, the error was gone away.

Upvotes: -3

Kirill Chatrov
Kirill Chatrov

Reputation: 832

You might have forwarding enabled on adb. You can try this: Quit Android studio and launch terminal. Run these commands:

adb kill-server
adb forward --remove-all
adb start-server

Now you can launch Android Studio and try again.

Upvotes: 27

Bond James
Bond James

Reputation: 33

Upgrade to the latest SDK, for the android emulator:

  • use 512MB RAM
  • 256MB heap

You can leave the default disk space.

Upvotes: 1

Deen Adam
Deen Adam

Reputation: 61

Go to Android Studio Command Line, and follow these steps:

  • __> cd /Users/your_root_name/.android/avd
  • __> ls
  • __> rm -r Nexus_5X_Edited_API_17.avd There are two avd files.

Rerun the app.

Upvotes: 4

Related Questions