Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Flutter says 'Emulator didn't connect within 60 seconds'

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

Short answer

The editor gives up when the emulator has not come online in time. Start the same AVD from a terminal with -verbose to see what it does. The causes the official Android docs confirm are missing hardware acceleration, a graphics mode the computer cannot support, or running the emulator inside another virtual machine.

  • Applies to Android Emulator current stable, Flutter 3.3x stable
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Start the AVD yourself with verbose output. If it boots here, the emulator is fine and only slow; if it errors, the message names the cause.

    emulator -list-avds
    emulator -avd <avd_name> -verbose
  2. 2Match what you see, then jump to its fix

    1. 1emulator -accel-check does not report a usable hypervisor, and the emulator is very slowHardware acceleration is not availableFix
    2. 2The emulator crashes or shows wrong images while bootingThe graphics mode does not work on this computerFix
    3. 3The host is a VirtualBox, VMware or Docker guest, or another hypervisor tool runs at the same timeThe emulator runs inside another virtual machine, or clashes with other virtualization softwareFix

What does the error look like?

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

Cause 1 of 3

Hardware acceleration is not available

1Check

The emulator can tell you whether a hypervisor is usable on this machine.

emulator -accel-check

2Fix

On Windows turn on Windows Hypervisor Platform in Windows Features and restart, and make sure virtualization is enabled in the BIOS. On Linux install KVM and check your user may use it. On Apple silicon use an arm64 system image.

sudo kvm-ok

3Verify

emulator -accel-check reports a usable hypervisor, then the AVD boots in the Device Manager.

emulator -accel-check

Confirmed by developer.android.com

Did this fix it?

Cause 2 of 3

The graphics mode does not work on this computer

1Check

A graphics option your machine cannot support can cause crashes or wrong images. Software mode is the documented fallback.

emulator -avd <avd_name> -gpu software

2Fix

If that boots, set Graphics acceleration of the AVD to Software in the Device Manager (Additional settings, Emulated Performance), or keep starting it with -gpu software.

emulator -avd <avd_name> -gpu software

3Verify

The AVD reaches the home screen and adb lists it.

adb devices

Confirmed by developer.android.com

Did this fix it?

Cause 3 of 3

The emulator runs inside another virtual machine, or clashes with other virtualization software

1Check

VM acceleration cannot run inside another VM, and some virtualization software cannot run at the same time.

emulator -accel-check

2Fix

Run the emulator directly on the host computer, or close the other virtualization software while you use it.

flutter emulators --launch <avd_name>

3Verify

The AVD boots and flutter devices lists it.

flutter devices

Confirmed by developer.android.com

Did this fix it?

How do I stop it coming back?

  • Boot a new AVD once from the Device Manager before using it from VS Code, so the slow first start is done.
  • Keep the emulator and system images updated in the SDK Manager.
  • Leave emulator -accel-check output in your setup notes for each machine.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

Google Play says the app does not support 16 KB memory pages

check_elf_alignment.sh reports UNALIGNED for a library under lib/arm64-v8a

Google Play requires apps that target Android 15 or higher and ship native .so libraries to run on devices with 16 KB memory pages; from 1 February 2027 it will block updates that do not.

5 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.