Flutter says 'Emulator didn't connect within 60 seconds'
Failed to launch emulator: Error: Emulator didn't connect within 60 secondsShort 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.
Fix it fast
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> -verbose2Match what you see, then jump to its fix
- 1
emulator -accel-check does not report a usable hypervisor, and the emulator is very slowHardware acceleration is not availableFix - 2
The emulator crashes or shows wrong images while bootingThe graphics mode does not work on this computerFix - 3
The 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
- 1
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-check2Fix
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-ok3Verify
emulator -accel-check reports a usable hypervisor, then the AVD boots in the Device Manager.
emulator -accel-checkConfirmed by developer.android.com
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 software2Fix
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 software3Verify
The AVD reaches the home screen and adb lists it.
adb devicesConfirmed by developer.android.com
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-check2Fix
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 devicesConfirmed by developer.android.com
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:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
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 fixMobile apps
Gradle cannot find com.google.firebase:firebase-analytics-ktx
Required by: project :app
Firebase moved the Kotlin extensions into the main modules and stopped releasing the -ktx modules in July 2025.
2 causes, each with a fixMobile apps
Gradle cannot create LibraryVariantBuilderImpl in a Flutter Android build
Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl
This error appears when the Android Gradle plugin (AGP) cannot run in the Gradle or IDE you use.
3 causes, each with a fixMobile apps
Flutter release build cannot open the keystore: HmacPBESHA256 not available
Algorithm HmacPBESHA256 not available
The keystore is a PKCS12 file protected by a newer algorithm than the Java that is reading it understands.
3 causes, each with a fixMobile apps
Android install error: the package conflicts with an existing package of the same name
The package conflicts with an existing package by the same name
Android allows only one app per application ID, and an update must be signed with the same certificate as the installed version.
3 causes, each with a fixMobile apps
Android resource linking fails with resource android:attr/lStar not found
error: failed linking references.
The lStar attribute exists only from Android API 31.
2 causes, each with a fix