Failed to launch emulator: Error: Emulator didn't connect within 60 seconds

173,785

Solution 1

i had same problem, i tried to stopping emulator based on Answer of Rahul Shukla:

Steps:

Open Android Studio Tools -> AVD Manager Virtual Device -> Actions (Refer Image) Click On Stop Now Start Emulator Now it's working fine :)

but it not work for me. i test another way. i use these steps:

  • Open Android Studio Tools -> AVD Manager Virtual Device -> Actions Click On Wipe data

Now Start Emulator and Enjoy it!!

Solution 2

Steps:

  1. Open Android Studio
  2. Tools -> AVD Manager
  3. Virtual Device -> Actions (Refer Image)
  4. Click On Stop
  5. Now Start Emulator

Now it's working fine :)

enter image description here

Solution 3

I've added a user environment variable:

  • Name: ANDROID_HOME

  • Path: Your android folder path, personally it was D:\Android

and restart.

Hope it ll work for you.

Solution 4

enter image description here

  1. Open Android studio and go to AVD manager.
  2. Click on stop
  3. Click on wipe data
  4. Click Cold boot

Solution 5

Adding the following variables to $HOME/.bash_profile solved my problem

export ANDROID_HOME=$HOME/Library/Android/sdk
export PATH=$PATH:$ANDROID_HOME/emulator
export PATH=$PATH:$ANDROID_HOME/tools
export PATH=$PATH:$ANDROID_HOME/tools/bin
export PATH=$PATH:$ANDROID_HOME/platform-tools
Share:
173,785

Related videos on Youtube

f1t3
Author by

f1t3

Updated on July 13, 2022

Comments

  • f1t3
    f1t3 almost 2 years

    I'm unable to debug using VSCode for Flutter. I'm using Windows and I'm trying to use an Android emulator.

    I have attempted to reinstall Flutter, Android SDK and VSCode to fix the issue, as well as tried setting environment variables.

    This is the error that I get when launching debug mode. Failed to launch emulator: Error: Emulator didn't connect within 60 seconds

    Are there any better emulators that I can use for both Android and IOS, because I don't even know where to begin with IOS emulators. I'm new to app development and want to get started making applications for both devices.

    • Ethan Hunt
      Ethan Hunt almost 5 years
      flutter emulators to see available devices
    • Hammad Khan
      Hammad Khan over 2 years
      1. Restart 'terminal' windows 2. Restart Android Studio, stop emulator, wipe data, run again 3. Make sure you are getting some output or error in terminal windows, if not start with step 1 and 2.
  • f1t3
    f1t3 about 5 years
    It doesn't say any devices are connected despite having like 5 emulators.
  • Rob Mascaro
    Rob Mascaro almost 4 years
    I'm not sure why this was marked down? For anyone else like me who could not get the emulator to start - it would hang at the popup loading screen about 30% through and the qemu process would also hang - this was the solution. In my case I didn't have HAXM installed at all.
  • Marcelo Rebouças
    Marcelo Rebouças almost 4 years
    If you is using linux, you should give the user permission from the directory /dev/kvm.
  • Rvy Pandey
    Rvy Pandey over 3 years
    This could have been a comment on the question, not an answer.
  • Lutti Coelho
    Lutti Coelho almost 3 years
    I'd same problem and "Cold Boot Now" option works fine. No need to wipe device data.
  • Boaz
    Boaz over 2 years
    This is a valid answer. While not an ideal solution, this is the only thing that currently works for me whenever VS Code fails to connect to the emulator, with the message "Emulator didn't connect within 60 seconds"
  • MJ33
    MJ33 over 2 years
    worked well for me when other solutions couldn't
  • Suj
    Suj about 2 years
    I killed qemu process from task manager :D seems easier
  • Fly
    Fly almost 2 years
    Where do you run the command (2)? My standard windows terminal does not know adb.
  • Patrick Geyer
    Patrick Geyer almost 2 years
    Why can't flutter launch hardware accelerated devices?
  • Merritt
    Merritt almost 2 years
    @PatrickGeyer In general Flutter can and does, this just happened to be an issue. I haven't had this problem myself in some time now.