# Coding agents in cloud sandboxes can’t run an Android emulator.

The emulator needs hardware virtualization (KVM), and cloud sandboxes don’t have it. Developers write that into the files their coding agents read. Here are 24 of those lines, word for word, each linked to where it stands.

Quoted from public AGENTS.md and CLAUDE.md files, read 14 November 2026. Their authors aren’t affiliated with Mobilebox.

## No KVM, so no emulator

Cloud sandboxes rarely expose hardware virtualization, and the Android emulator needs it.

- there is no emulator here (no KVM), so it is only run on real devices.
  [mariuz/castle-doom · CLAUDE.md L72–73](https://github.com/mariuz/castle-doom/blob/ab8e6ce35d0c6a6395913854d5e388838fa735e1/CLAUDE.md#L72-L73)

- There is no emulator there (no KVM): device tests run in CI.
  [Seafloor-Studio/newspaperss · CLAUDE.md L38](https://github.com/Seafloor-Studio/newspaperss/blob/571fc2a5ec261b8d75ab2e9749c32e5811e11372/CLAUDE.md#L38)

- No KVM in the cloud container, so no emulator; verify with unit tests and the JVM screenshot tests
  [crockalet/haunt · CLAUDE.md L33](https://github.com/crockalet/haunt/blob/bc2eea6df797a9dd3e6faff42da292544b98a813/CLAUDE.md#L33)

- There is no `/dev/kvm` and no virtualization CPU flags, so the Android emulator cannot run — this one is hardware, not policy.
  [tag1consulting/lagoon-app · CLAUDE.md L156](https://github.com/tag1consulting/lagoon-app/blob/47748c1df75bf09cec7ea37fa63ad8ddce907f70/CLAUDE.md#L156)

- Claude Code on the web has no Android emulator (no KVM).
  [abhiabhi94/arrow-game · CLAUDE.md L122](https://github.com/abhiabhi94/arrow-game/blob/22793ae9151e052d2e87200648db8d8e12450adb/CLAUDE.md#L122)

- the Android emulator cannot boot and the app cannot be launched with a UI here.
  [amirmohebalinezhad/Kheyr · AGENTS.md L35–36](https://github.com/amirmohebalinezhad/Kheyr/blob/e8adc9a79844ee5ef5726e70ae6a2f85952b7ef9/AGENTS.md#L35-L36)

- The Android emulator requires KVM hardware acceleration, which is unavailable in the Firecracker-based Cloud Agent environment.
  [jamesleekko/ZB_Canteen · AGENTS.md L26](https://github.com/jamesleekko/ZB_Canteen/blob/1749d1d5ae4b65846ee6cfd531ecd2d0bbf76f1b/AGENTS.md#L26)

- Orbs have no KVM: do not install/start Android emulators.
  [patrickrb/sstvaf · AGENTS.md L29](https://github.com/patrickrb/sstvaf/blob/b20f2d0d1e837119e253479487903cce55c2fbe1/AGENTS.md#L29)

## The emulator is too slow

Without KVM it runs in software: boots take minutes and every step crawls.

- The emulator has no KVM there, so a page takes about 13 minutes to detect (0.2 s natively)
  [snonux/comicredr · AGENTS.md L337–338](https://github.com/snonux/comicredr/blob/d4ca0062bf6b8b1b7fa9e0255e445f39b794e2bd/AGENTS.md#L337-L338)

- Boot takes 10 to 15 minutes; wait for `adb shell getprop sys.boot_completed` to print 1, then another minute.
  [danielphingston/metro-launcher · CLAUDE.md L61](https://github.com/danielphingston/metro-launcher/blob/094ab94e3f82f27a8cfd794eb04acef077f36e7f/CLAUDE.md#L61)

- Cloud VMs typically lack `/dev/kvm`, so the emulator runs in software mode and boots very slowly (10+ minutes).
  [Vitorr32/umavpn-connect · AGENTS.md L49](https://github.com/Vitorr32/umavpn-connect/blob/3ab969ee3b11286195b1594aba5a34a9ef0501c1/AGENTS.md#L49)

- Expect a slow boot (~10 min) and a sluggish but usable guest.
  [BenItBuhner/Cesium · AGENTS.md L92–93](https://github.com/BenItBuhner/Cesium/blob/094f5aacc45ab81bc30e55055e28f76ea31eeda3/AGENTS.md#L92-L93)

- On an unaccelerated host expect several minutes to boot and ~14 s per screenshot
  [Sabeel-Institute/sabeel-institute-kanban · CLAUDE.md L775–776](https://github.com/Sabeel-Institute/sabeel-institute-kanban/blob/a79af566b2795109b98f22480378ce1735d1f695/CLAUDE.md#L775-L776)

- Maestro does not run on every push — it needs a booted emulator, which is minutes rather than seconds.
  [ahmedsaed/Peace · AGENTS.md L237–238](https://github.com/ahmedsaed/Peace/blob/60a840c456fb7ce8e3c2425121e8162f80f0bb03/AGENTS.md#L237-L238)

- `adb shell input text` drops characters on the slow emulator
  [khaidarsafarov-droid/MyFinance · AGENTS.md L52–53](https://github.com/khaidarsafarov-droid/MyFinance/blob/2149124aa517c729d9b779db0eaa203ab28204a3/AGENTS.md#L52-L53)

- UI interactions can trigger a spurious "isn't responding" (ANR) dialog — this is emulation slowness, not an app bug.
  [pepper-candy/NotiGuard_RAISE · AGENTS.md L31–32](https://github.com/pepper-candy/NotiGuard_RAISE/blob/e645e5e0d94a692c974223013d3a1ed281aee7ef/AGENTS.md#L31-L32)

## Nothing to test on

Reviews ask for evidence from a running app, and the agent has no phone to get it.

- User-facing Android/terminal/SSH/tmux/agent/setup/release-gate work needs reviewer emulator evidence
  [PocketShell-io/pocketshell · AGENTS.md L57](https://github.com/PocketShell-io/pocketshell/blob/8c032add8531af1dfde72a524e965f6a30a8f44a/AGENTS.md#L57)

- Any PR that adds or changes UI must include screenshots and a screen recording of the change running on a device or emulator
  [jesserockz/little-videos · AGENTS.md L36–37](https://github.com/jesserockz/little-videos/blob/00bfa9f8b6557819e97fd4bd439073b4c41d7c98/AGENTS.md#L36-L37)

- On-device / emulator runs are not covered by the dev container (no adb device, no KVM).
  [cobarx/pubnet-tools · CLAUDE.md L199–200](https://github.com/cobarx/pubnet-tools/blob/7e8c61b6f97b35b895da81932b244df745e31cc1/CLAUDE.md#L199-L200)

- If it is unavailable, report the blocker rather than trying to emulate inside the orb.
  [thekorn/network-audit · AGENTS.md L14–15](https://github.com/thekorn/network-audit/blob/28dfee937985090b2e80b145172d3d282f5f3550/AGENTS.md#L14-L15)

- Docker Desktop on macOS has no KVM, so a local run is unsupported — not a skipped pass.
  [joemast/shared-shopping-list-mobile · AGENTS.md L42](https://github.com/joemast/shared-shopping-list-mobile/blob/79691c27a8ef94cbb0fea3fcf67390d6d5cec37f/AGENTS.md#L42)

## Black frames

When it does run, the screenshot an agent checks can come back black.

- The same emulator draws nothing but black for a Flutter app on Impeller (the default) with `-gpu swiftshader_indirect`: frames are made, the screenshot is black.
  [snonux/comicredr · AGENTS.md L343–345](https://github.com/snonux/comicredr/blob/d4ca0062bf6b8b1b7fa9e0255e445f39b794e2bd/AGENTS.md#L343-L345)

- The display frequently fails to composite (screencap returns an all-black frame).
  [sal0-h/charuco-calibrator-android · AGENTS.md L34–35](https://github.com/sal0-h/charuco-calibrator-android/blob/6aab4ab04144b9bf2d075aac56c9d964f9dd75d9/AGENTS.md#L34-L35)

- On that emulator every PNG fails to decode, in any Flutter app
  [snonux/comicredr · AGENTS.md L340–341](https://github.com/snonux/comicredr/blob/d4ca0062bf6b8b1b7fa9e0255e445f39b794e2bd/AGENTS.md#L340-L341)

## A phone instead of an emulator.

Mobilebox gives your agent a cloud Android phone over MCP: ready in 19.4 s in our November 2026 benchmark, $0.01 a minute. Your agent installs the build, walks the flow and screenshots it, from inside the same cloud sandbox.

[Get started](https://mobilebox.dev/docs) [See which apps run on it](https://mobilebox.dev/apps)

1. Add the MCP server
   One URL, `https://mobilebox.dev/mcp`, in Claude Code, Codex, Cursor or any MCP client.

2. The agent starts a phone
   It installs your APK and reads the screen as numbered elements.

3. It checks the flow
   Taps, types, takes screenshots for the pull request, then deletes the phone.

## Read more

[No KVM in CI? Run the APK on a remote Android phone Why the Android emulator stalls without KVM, three ways around it, and a tested curl script that installs an APK on a cloud phone from any runner. Guides4 min read](https://mobilebox.dev/blog/android-emulator-without-kvm) [Test your Android app with Claude Code on a cloud phone Give Claude Code a hosted Android phone over MCP, install your APK from a URL, check the first screen and delete the phone, with the tool calls we ran. Guides3 min read](https://mobilebox.dev/blog/claude-code-android-app-testing) [Screenshots in every pull request: let your agent test the app on its own phone Each agent on a PR starts a cloud Android phone, installs the build, walks the flow and posts a proof comment with screenshots, time and cost. The GitHub Action, the MCP prompt, before and after, and what is kept. Guides5 min read](https://mobilebox.dev/blog/screenshots-in-every-pull-request)

## Try it in your agent in 60 seconds

Paste this into Claude Code, Cursor, Codex or any agent that can read a web page. It asks for your email, gets its own key at once and adds the phone tools; the 6-digit code from your inbox keeps the workspace.

```
Set up Mobilebox for me: read https://mobilebox.dev/setup.md?via=why and follow it.
```

[What your agent reads](https://mobilebox.dev/setup.md?via=why)

## Next questions

- [Mobilebox or BrowserStack?](https://mobilebox.dev/blog/mobilebox-vs-browserstack?via=next-browserstack)

- [Cloud phone or a local emulator?](https://mobilebox.dev/blog/mobilebox-vs-local-emulator?via=next-emulator)

- [Mobilebox, Limrun or Mobilerun?](https://mobilebox.dev/blog/mobilebox-vs-limrun?via=next-limrun)

- [How do I add it to Cursor, Codex or VS Code?](https://mobilebox.dev/blog/android-mcp-cursor-codex-vscode?via=next-setup)

- [Can my agent run 50 phones in parallel?](https://mobilebox.dev/blog/run-android-phones-in-parallel?via=next-parallel)

- [Can my agent use an iPhone?](https://mobilebox.dev/ios?via=next-iphone)

- [Can each phone get a residential IP?](https://mobilebox.dev/blog/residential-ip-per-phone?via=next-residential-ip)

- [Does my agent stay logged in between runs?](https://mobilebox.dev/blog/park-resume-android?via=next-logins)
