Support
Emudroid 1.0.1 · macOS 13 or later
How do I start?
Open Emudroid and press Install on the setup screen. It fetches a private Java runtime, Homebrew and Google's Android command-line tools — a few hundred megabytes, once. When the main window appears, press Add New, pick a phone, an Android version, how much memory and disk it gets, give it a name, and press Save and Continue. The first device also downloads its system image, which is the big one.
Setup is downloading a lot. What is it doing?
Emudroid deliberately keeps everything to itself rather than using an Android Studio installation you may already have. It downloads its own Java runtime from Adoptium, its own copy of Homebrew, Google's command-line tools, and the emulator. All of it goes into ~/.emudroid. The first Android version you create adds roughly 2 GB, and further versions add their own image.
Which Android versions can I create?
Android 9 (Pie) through Android 17 (Cinnamon Bun), each with the Google Play Store image, on both Apple silicon and Intel Macs. Emudroid picks the right image architecture for your Mac automatically.
Do I need Android Studio, or a Google account?
No Android Studio — that is rather the point. You do need a free Google account to accept Google's licence for the system images, and you sign in to Google Play inside the emulator, not in Emudroid.
How much disk space does it use?
Each Android version is a one-off download of roughly 1–2 GB, shared by every device using it. Each device you create grows only as you fill it: the data partition is allocated on demand rather than reserved up front, so a device set to 64 GB costs you about 2 GB until you actually use it.
A device I deleted is still taking up space
A device's data grows but does not shrink, so deleting files inside Android does not return space to macOS. Deleting the device in Emudroid does. If a device window is still open, quit it first.
The emulator is slow, or will not boot
- Try the Pixel 5 Optimized device. It renders at 720×1600, which is dramatically faster with no real loss on a Mac screen.
- Give the device at least 4 GB of RAM.
- If a device refuses to start after an interrupted run, delete it and create it again — it is quicker than repairing it, and your other devices are unaffected.
- Make sure you have several gigabytes free before first boot of a new device.
How do I install my own app?
Drag an .apk file onto the emulator window. Google's adb is included, so adb install MyApp.apk works too if you prefer the terminal — Emudroid puts platform-tools on the path for you while a device is running.
I want to test my website inside the emulator
Use adb reverse tcp:3000 tcp:3000 and your Mac's dev server becomes localhost:3000 inside Android. That way you test the real thing, on real Android, without deploying anywhere.
Google Play says my device is not certified
Play Store images are Google's and occasionally need a moment after first boot to settle. If an app refuses to install, give it a few minutes, then restart the device from inside Android. If it persists, recreate the device — a device that was interrupted mid-setup can end up in this state.
How do I remove Emudroid completely?
Quit the app, then delete it and these two folders:
~/.emudroid— the runtime, tools, emulator and system images~/.android— your virtual devices
Or use Delete All in the app's menu, which does the same thing for you.
Terms
Emudroid is provided as is, without warranty of any kind. Android, Google Play and the Android system images are Google's, and using them means accepting Google's terms. Emudroid is not affiliated with, endorsed by, or sponsored by Google LLC.
Contact
Nadenco Single Member P.C.
nadenco@outlook.com
naden.co