The Android Emulator runs well on my Linux desktop. Its windows don't. I use a tiling Wayland desktop (Noctalia with Umbriel) across two monitors, and the emulator's toolbar is a separate window from the device screen. The compositor tiles them apart, the toolbar drifts to the other display, and closing the toolbar of one virtual device could close the toolbars of the others too.
The emulator was never the problem. The problem was how its UI is split into windows and how those windows meet the compositor. So I built Android Emulator Dock: one normal window that holds every running emulator, with the controls inside it.
The idea
The Dock doesn't replace the emulator. The official emulator still runs Android, graphics, audio, sensors, networking and snapshots. The Dock starts it with its own window hidden, then draws the screen and sends input through the emulator's gRPC API.
emulator (AVD 1) emulator (AVD 2) emulator (AVD 3)
│ │ │
└──── gRPC ────────┼──── gRPC ────────┘
▼
Android Emulator Dock
one Wayland windowThere is no window embedding: no XEmbed, no reparenting, no nested compositor. Those tricks break in different ways on every desktop. A gRPC client and a drawing surface don't depend on the window manager at all.
What it does
- Run several emulators side by side: single, two columns or an adaptive grid. Drag slots to reorder them, focus one, or pop one out into its own window.
- Simulated multi-touch: hold Ctrl and drag to pinch, add Shift for a two-finger pan, Ctrl and the wheel to zoom. The fake fingers are drawn on the screen so you can see them.
- Drop an APK on a device to install it, or any other file to copy it to
/sdcard/Download. The clipboard syncs both ways. - Per device: screenshot, screen recording to MP4, a filterable logcat panel, snapshots, fold postures, battery, network speed, and location from presets, pasted map links or a GPX route.
- Broadcast mode repeats your input on every running emulator.
- Create, edit and delete AVDs, cold boot, wipe data, set RAM and cores. The workspace comes back the way you left it.
It doesn't need Android Studio, only the Android SDK with the emulator and command-line tools.
What broke on the way
- GNOME wouldn't snap the window to half the screen. Each slot's toolbar pushed the window's minimum width past half of my laptop screen. A fixed minimum size on the slot fixed it.
- The UI froze when an emulator stopped. The app waited for the frame thread while the thread was still blocked on the stream. Closing the stream first, then waiting, fixed it.
- A slow emulator froze the whole window. Input was sent from the UI thread. It now goes out on its own thread.
- Logcat came back empty. The parsed logcat mode returns empty entries on current emulators, so the panel reads text mode and parses it itself.
How I tested it
- 83 unit tests run without an emulator: AVD and SDK discovery, the launch state machine, keyboard, touch and gesture mapping, workspace layouts, location parsing, and the gRPC client against a fake emulator running in the same process. CI runs them, with a linter, on Python 3.11, 3.12 and 3.13.
- A second set needs real AVDs on the machine: one emulator's full lifecycle and streaming, two emulators at once without crossing input or frames, and the toolbar and controls. CI can't run these.
Limits
- Linux only. It is built for Wayland and also runs on X11.
- The README asks for emulator 34.0.0 or newer, and the gRPC flags it relies on can change between emulator releases.
- There is no release or distro package yet. The repo has an AUR
PKGBUILD, but it isn't published, so you install from source. - It is an independent project, not affiliated with Google, Android or Android Studio.
Try it
You need Python 3.10 or newer, uv, and the Android SDK. The Dock finds the SDK from ANDROID_HOME, ANDROID_SDK_ROOT, your PATH or ~/Android/Sdk.
git clone https://github.com/KrunalSM/android-emulator-dock.git
cd android-emulator-dock
make installThen run aed, or open Android Emulator Dock from your app launcher. Pick an AVD, press + Add, then Start.
It is Apache 2.0 licensed. If it misbehaves on your desktop, open an issue with your compositor and emulator version.