IssueTracker

I am also facing the same issue

I am also facing the same issue...any solutions?

I have the same error

05/25 16:14:42: Launching app
Error while waiting for device: Timed out after 300seconds waiting for emulator to come online.

No solution yet,getting same error,how to get this resolved?

Any solution for this problem please.

Same here. When I create a new emulator it works.. most of the time.

Recently I created a new emulator, run the project and it worked.
Then after a few runs it hung with message "waiting for emulator to come online". Then I closed the emulator and run the same project in debug mode (I pressed the "bug" icon instead of the triangle) and it worked !
But that's not a constant behavior, sometimes it works  and sometimes not.

Same for me.  I'm on a Mac 10.11.4 with tools 25.1.7 using Android Studio 2.1.1

"Error while waiting for device: Timed out after 300seconds waiting for emulator to come online."

Also, as mentioned in previous bug report, it takes a very long time to simply build.  4 or 5 minutes it seems.  When I build and run on my device it does it pronto.  I'm running the LoginActivity that you can create with a brand new project.

Have the same error...I would highly appreciate any help

I have the same error.. can't launch the emulator at all :(8658

Same here..... Any one can solve it?

same error in windows and mac. :-(

I too am having this problem.  No solution yet.

Hello, I have the same isssue. In Windows 10 and Fedora 23. SDK tools is version 25.1.7

#15 Me too I having this problem.

I have the same problem

possible workaround?
after starting device from device manager, it shows up as a 'connected device' when running the project.

Same issue here.
Simple apps that do not require a more advanced build.gradle will work well, those apps that need gradles with these dependencies will crash with a 300minutes timeout error:

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    testCompile 'junit:junit:4.12'
    compile 'com.android.support:appcompat-v7:23.2.0'
    compile 'com.android.support:design:23.2.0'
    compile 'com.android.support:support-v4:23.2.0'
    compile 'com.google.android.gms:play-services:8.4.0'
    compile 'com.google.android.gms:play-services-maps:8.4.0'
    compile 'com.google.android.gms:play-services-ads:8.4.0'
    compile 'com.google.android.gms:play-services-identity:8.4.0'
    compile 'com.google.android.gms:play-services-gcm:8.4.0'
    compile 'com.google.android.gms:play-services-analytics:8.4.0'
    compile 'com.google.maps.android:android-maps-utils:0.4+'

}


I get this problem after upgrading to 2.1.2.

Since then, I've de-installed A/S2.1.2 and deleted SDK then re-installed and downloaded fresh SDK and installed tools from scratch.

Still crash with a 300minutes timeout error.

Am using my Android smartphone instead of AVD, at least that works.

I _may_ have reproed this with Studio 2.2 Preview 5, emulator 25.2.0-3037468 and sysimg: API 23 Google API 2872745

I still got this problem after refreshing SDKs and recreating AVDs twice. I have installed following APIs, I do not know why API21 shows "Partially installed", possibly because I left out obsolete revisions.

My SDK Tool detail:
Android SDK Tools 2.1.7         25.1.7  Installed

I will try and attach a logcat output shortly

Name            API     Rev     Status
=====================================
Android 6.0     23      3       Installed
Android 5.1     22      2       Installed
Android 5.0     21      2       Partially installed
Android 4.2     17      3       Installed
                16      5       Not installed

Same issue here. On MAC 10.11.5, Android Studio 2.1.2, SDK Tools 25.1.7

Sadly, this is _not_ reproduced on a tip of tree build of studio using canary release of emulator (25.2.0-3037468).
So, may not have any debugging ability from the studio side right now.

Some progress, and a workaround.

This error occurs only (on a studio-2.2  ToT build, as well as on the Preview 5 release) when Tools > Android > "Enable ADB integration" is turnd off.

So, the workaround (or the fix?) is to enable this feature.
If you're using "Instant Run", you'll have this feature turned on anyway since Instant Run needs it.

Talked to vsiva@, this is just a case of bad messaging to the user.
ADB integration should be on in this use case. We do warn the user in some other flows. Need to do that here as well.

- EmulatorConnectionListener tries to list some clients to verify that emulator is up and running: https://cs.corp.google.com/android/tools/adt/idea/android/src/com/android/tools/idea/run/EmulatorConnectionListener.java?type=cs&q=%22waiting+for+emulator%22&sq=package:android&l=155
- In case Adb integration is off, no clients are listed: https://cs.corp.google.com/android/tools/base/ddmlib/src/main/java/com/android/ddmlib/DeviceMonitor.java?type=cs&q=DeviceMonitor.java&sq=package:android&l=561

This causes studio to wait for the emulator to come up forever.

Instead, we EmulatorConnectionListener should complain loudly if adb integration is off.

ag/1248613

same issue with no solution

Solutions:

1. Use 2.2 Preview 7 or later, or:
2. First launch the emulator, then deploy.

I can see 2.2 preview 6 on canary channel. Tried but doesn't work.

This is not reproducible in 2.2 preview 7 with SDK Tools 25.2.0 , API 23 emulator

Android Studio 2.2 Preview 7
Build #AI-145.3111935, built on August 1, 2016
JRE: 1.8.0_76-release-b03 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

emulator: WARNING: Crash service did not start
The memory needed by this VM exceeds the driver limit.
emulator: WARNING: Decreasing RAM size to 4096MB
Hax is enabled
Hax ram_size 0x100000000
HAX is not working and emulator runs in emulation mode.
qemu-system-i386.exe: -drive if=none,index=1,id=cache,file=C:\Users\Manu_Dufresne\.android\avd\Nexus_4_API_23.avd/cache.img: could not open disk image C:\Users\Manu_Dufresne\.android\avd\Nexus_4_API_23.avd/cache.img: Could not open 'C:\Users\Manu_Dufresne\.android\avd\Nexus_4_API_23.avd/cache.img': Invalid argument

DOESN'T WORK.

This is not reproducible in 2.2 preview 7 with SDK Tools 25.2.0 , API 23 emulator

Android Studio 2.2 Preview 7
Build #AI-145.3111935, built on August 1, 2016
JRE: 1.8.0_76-release-b03 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

Error: Could not access the Package Manager.  Is the system running
Unknown failure (Error: Could not access the Package Manager.  Is the system running?)
Error while Installing APK

Closing this bug for comments because
(1) we believe this bug fixed
(2) The workaround and description of the problem in comment #26 and #31 are valuable, so should not get lost in follow up stream of comments.

If you still face an issue, please file a new bug referring to this bug. If we find that this bug is indeed not fixed, we'll reopen the bug and de-duplicate your bug to it.

Thank you for your continued feedback.

i have same issue " Timed out after 300seconds waiting for emulator to come online." help me

I have already given up. Google closed this issue without fix last year despite informing them it is not fixed yet. I tried  all the work around however no success. Still does not work for me.

I have same issue. No solution yet.

I have the same issue

I have the same issue. Finally, in AVD Manager, do not set to use the default devices(Target cannot be edited and with Google Play) in the list, I clone one of it and set the Target as Android 7.11, API 25 with Google APIs (it may not be relevant), it is OK now.

I have the same issue.... Android sudio 2.1 - Error while waiting for device: Time out after 300seconds waiting for ....

Please send me proper solution

Same problem.. cannot find solution

no solution?

Same issue. I tried to change the emulator but it didn't work. Any solution?

I ran these commands from terminal in the platform directory and it solved the issue.

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

I also am experiencing this error with android studio (I think it is version 3.3?)

I have the same issue

I have the same issue

Facing the same issue

Same problem here, Android Studio version 2021.1.1, Sierra.

Is there any solution to this? I got the same issue on all projects with Android Studio Chipmunk. It suddenly started. I already tried to reinstall it. The installing and launching works when I do it manually with gradle and adb.
And the problem exists with emulator and physical devices.

Same problem i am also facing, kindly resolve it

I'm facing same issue