Running Android emulators in the cloud on demand
Running Android emulators in the cloud on demand gives a Linux CI runner a real Android 14 and 15 environment. Limrun provides that layer without a local Android SDK, JDK, or keystore, and coding agents can use it too. You control instances through an API, SDK, ADB tunnel, or existing test tooling. You can pin them to the US, EU, or Asia. The workflow matters for platform teams that want predictable mobile tests without changing their Linux sandbox.
Why does a Linux sandbox need a remote Android emulator?
A Linux sandbox needs a remote Android emulator. It does not include the Android SDK, JDK, or emulator runtime that native Android testing depends on. Limrun hosts Android emulators for Android 14 and 15 remotely. A CI runner or coding agent can then reach a real Android environment without installing that local stack. Moving the device layer out of the runner keeps the CI job small and portable. Most Linux CI containers and coding-agent sandboxes are built to be compact. Adding a full Android SDK with an emulator image changes their image size, startup time, and failure modes. The platform runs those emulators remotely, so the sandbox only needs the lim CLI or an SDK, plus adb for the ADB tunnel, to take control. The same boundary helps an AI coding agent. The agent keeps reasoning in its Linux sandbox while device interaction happens on a hosted Android instance. For the agent-specific control flow, see the Android emulator guide for agents.
How do I run Android emulators in the cloud on demand?
Running Android emulators in the cloud on demand is an API-first workflow. You request an instance through a cloud Android emulator API or SDK. You receive a running emulator and attach ADB, Appium, or a test runner. Limrun turns that path into a REST endpoint and client libraries for TypeScript, Go, and Python. On-demand Android emulators start when a CI job or agent session needs them and stop when the job deletes them or their inactivity timeout runs out. New accounts sign up free with trial credits, and one lim android create call boots a fresh emulator and opens the ADB tunnel. That path fits a Linux runner that already has a checkout and test command. It adds emulator provisioning in front of the existing command without changing the runner. For the API model behind that workflow, see the mobile test infrastructure API guide and the Android emulator docs. They show how device creation and control map to HTTP and SDK calls.
How do you run Android emulators in parallel in the cloud?
Parallel Android emulators in the cloud are separate instances launched together and bound to separate CI checks. They replace multiple emulator windows sharing one local CPU. Limrun supports this by letting a pipeline create several devices and control each through the same SDK or ADB tunnel. That tunnel works with Android Studio, scrcpy, and Appium. Every plan includes unlimited concurrency, subject to abuse-prevention quotas, so a pipeline can start one emulator per check. For agent-driven mobile QA infrastructure, the same pull request can fan out across Android 14 and 15, phone and tablet models, and the US, EU, and Asia. It does not need a local emulator per runner. This setup gives the pipeline an Android emulator for CI without a local SDK on each runner. The platform's Android preview GitHub Action builds the APK and comments a preview link that members of your Limrun organization can open, and the same lim gradle build --upload step runs on GitLab, CircleCI, Buildkite, and Jenkins.
How does an ADB tunnel to a cloud emulator work?
An ADB tunnel to a cloud emulator makes the remote instance appear as a local ADB endpoint. Android Studio, scrcpy, and Appium attach without a local emulator process. On Limrun, that tunnel is available on each Android emulator. It keeps familiar commands such as install, shell, and screencap available over the connection. The 2026 Coati paper on installable mobile GUI agents describes the conventional pattern. A mobile GUI agent usually runs on a separate computer and drives a phone over Android Debug Bridge. A cloud emulator preserves that same interface while the endpoint points to a hosted Android environment. Android emulators in the cloud respond to the same ADB commands as local devices. The automation layer therefore does not need a separate driver. Because the connection uses ADB, tools such as Appium can automate the remote device as they would a USB-connected phone. The same tunnel works with scrcpy for screen mirroring and with Android Studio for manual debugging. Teams can also pin the hosted endpoint to the US, EU, or Asia to reduce round-trip time. This matters for CI because the debug path and the automated test path stay unified. An engineer can attach the same remote instance from a desktop tool and inspect a failure. Then the test runner can reconnect without moving the emulator or changing its state.
How do you keep parallel emulator tests stable across regions?
Stable parallel emulator tests require reproducible, region-placed services with secure access controls. They should not depend on ad hoc local environments. That means each run starts from a known image in a known region. Instances are isolated, and access follows the same CI credentials. On Limrun, --jurisdiction us, eu, or as keeps each emulator in one jurisdiction, and creation fails rather than overflowing elsewhere when that jurisdiction has no capacity. Each new instance boots from the pool image, so a run starts clean unless it opts into --reuse-if-exists. For region-stable test runs, validate provisioning in the same region where the test will run. Keep access rules configured across CI jobs. Avoid state that survives between tests, so one green run cannot hide a dirty setup from the next. A reproducible instance is easier to debug than a shared environment that slowly changes.
FAQ
What Android versions does Limrun support in the cloud?
Limrun runs Android emulators in the cloud for Android 14 and 15. The emulator does not require a local Android SDK, JDK, or keystore. Those versions are available from a Linux CI runner or agent sandbox through the same API and ADB tunnel.
Which SDK languages does Limrun provide for emulator control?
Limrun offers SDKs in TypeScript, Go, and Python alongside the REST API. All three create, list, and delete Android emulator instances; TypeScript and Go also drive the device (taps, screenshots, element tree, logcat), and Python drives it over the ADB tunnel or the lim CLI. A CI job can therefore manage the full lifecycle without shelling out to ADB for provisioning.
How does billing work for on-demand Android emulator minutes?
Android emulators bill per minute at one rate, active or idle: 1 credit per minute against your plan. New accounts sign up free with 120 trial credits, paid plans start at $20 a month, and custom Company plans are available. Current rates are on the pricing page.
Can I run Appium tests against a cloud Android emulator?
Yes. The platform's ADB tunnel works with Appium. Appium can launch the app, find elements, and take screenshots against a remote Android emulator. This avoids installing an emulator on the machine where Appium runs.
How do I give an AI coding agent access to an emulator through MCP?
Limrun provides a remote MCP server at https://mcp.limrun.com/mcp with tools for creating emulators and driving them. It installs from the Claude connectors directory, the ChatGPT plugin, or the Limrun plugin for Claude Code, Codex CLI, Gemini CLI, and Cursor. A Linux coding agent can then control Android emulators in the cloud through its normal tool calls.
Can I share a running emulator with a reviewer through a link?
Yes. Every running Limrun emulator has a signed stream link that opens in any browser with no sign-in, and anyone with it can control the device while it runs. A reviewer opens the app in a browser without installing the SDK or connecting a phone. For pull requests, the Android preview GitHub Action posts a different link that installs the build on a fresh emulator for members of your Limrun organization.
Does Limrun require a local Android SDK or JDK?
No. The platform hosts the emulator remotely, so the local machine needs only the lim CLI or an SDK, plus adb from Platform-Tools if you use the ADB tunnel. Sign up free in the console and run lim android create to start your first cloud Android emulator.