All articles
TroubleshootingEmulatorInstallation6 min

Android Emulator Download Stuck on Mac: Wait, Retry or Resume

Updated on · The MACOS EMULATOR team

You clicked “Install game engine”, and the bar seems frozen. Before starting over, look at what the MACOS EMULATOR launcher does during this download, what it keeps when the connection drops, and when another click actually helps. The full walkthrough is in the guide to installing an Android emulator on Mac.

What the screen shows during the download

It starts with a line that sets expectations: “Starting setup - this downloads about 3.5 GB from Google’s servers.” After that, the screen shows three things:

  • The current stage, in the form “Step 1/4 - Device bridge”. The four stages always come in the same order: Device bridge, Emulator engine, Android system, then Virtual device.
  • A single bar for the whole installation, not one bar per stage.
  • Under the bar, the current file: its percentage, then the megabytes received so far out of its total. If the server does not announce the file size, only the megabyte counter shows.

No speed and no time remaining: the launcher does not display them. To tell whether it is moving, watch the megabytes: as long as the number keeps climbing, the download is running, even slowly.

Why the third stage takes so long

The four stages do not weigh the same. The Android system is the bulk of the download: the bar gives it 86% of its travel, against 11% for the Emulator engine and 3% for the other two combined. A bar that races to stage 3 and then slows down sharply is normal: the big file is arriving.

How long it takes depends on your connection, and the launcher shows no estimate. If you go through your phone’s hotspot, those gigabytes count against your data plan, and a new attempt counts part of them again, as you will see below. The guide to the emulator offline lists everything else that needs internet.

The line stays at 100%

Once a file has fully arrived, the line can sit at 100% for a while without the bar moving. The launcher is not frozen: it checks the file, then unpacks it before moving on to the next stage.

The Emulator engine and the Android system are compared against their expected fingerprint: a file damaged on the way is never used, and the next attempt fetches a fresh copy. A half-unpacked Android system is not accepted either.

When the connection drops

The launcher does not restart an interrupted download on its own, and it does not resume a file where it left off. A dropped connection stops the installation: an error window appears. Take a screenshot of it if you need to write to support, then close it: the screen goes back to the install button.

Nothing that was finished is lost. Every completed stage stays on your Mac, and the next click picks up at the first missing piece. As soon as at least one stage is done, the screen shows “Some components are already installed.” followed by the size of what is left, and the button becomes “Update installation”. Only the interrupted file starts over from zero: on a hotspot, it downloads again in full.

Quitting the launcher or letting the Mac sleep

Quitting the app during the installation is the same as a dropped connection: completed stages stay, the current file is lost. When you reopen it, the “I accept the Android SDK Terms & Conditions” box is still ticked, and one click on the button picks up where it should.

Nothing in the launcher stops the Mac from going to sleep during the installation. For a download this size, plug your Mac in and keep it awake until the last stage.

When to wait, when to retry

  • The megabytes are climbing: wait, even if it is slow. The button disappears during the download, and a second click would not start a second one anyway.
  • An error window appeared: close it, check your connection, then click again. Completed stages are not redone.
  • The button stays grayed out: the Android SDK Terms box is not ticked, or a line of the Mac check is red, such as a disk with less than 12 GB free. After freeing up space, quit and reopen the launcher: the Mac check only runs at launch. The guide to an emulator’s disk space says what to remove.

No need to uninstall to start from scratch, and never delete the app’s folder by hand: you would lose the stages already done, and the launcher would download everything again. Your license key plays no part here: the engine install button does not ask for it.

Still stuck: what support needs

The setup screen has no gear icon: during the installation, Settings are out of reach, and so are the Logs row and “Free up space”. And the launcher’s log does not record this download. What helps support: a screenshot (Shift + Cmd + 3) of the stage on screen and, if there was one, of the error window, plus your Mac’s model, its memory and its macOS version. The guide to contacting support shows where to send it.

Frequently asked questions

Why does the Android emulator download take so long?

The launcher downloads about 3.5 GB from Google’s servers, most of it for the Android system, in the third stage. How long it takes depends on your connection, and it only happens once.

The connection dropped during installation: do I have to start over?

No. Completed stages stay on your Mac, and the next click picks up at the first missing one. Only the interrupted file starts over from zero.

Can I quit the launcher during the download?

Yes, but the current file will be lost, as with a dropped connection. When you reopen it, the stages already done are kept, and the button only downloads what is missing.

The line stays at 100% and nothing moves: is it stuck?

No: the file has arrived, and the launcher checks it and then unpacks it before the next stage. As long as no error window appears, let it run.

Do I need to uninstall the emulator to retry a failed installation?

No. Click the install button again: it only downloads what is missing. And never delete the app’s folder by hand either.