# How do you run Appium tests on a cloud phone?

> Run Appium tests on a cloud phone: Appium server, UiAutomator2 driver, adb connect, appium:udid set to host:port. Steps from appium.io, on Droidkeep.

- URL: https://droidkeep.com/guides/how-to-run-appium-tests-on-a-cloud-phone/
- Last updated: 2026-11-16
- Publisher: Droidkeep (https://droidkeep.com)

**Quick answer — How do you run Appium tests on a cloud phone?**

Install the Appium server and its UiAutomator2 driver on your computer, connect the cloud phone with `adb connect host:port`, then start a session with `appium:udid` set to that same `host:port`. A **Droidkeep** phone runs Android 12, which the driver supports from Android 8, and ADB is on every plan from $0.09 a day.

**In brief**

- **Server side**: Node.js `^20.19.0`, `^22.12.0` or `>=24.0.0`, npm 10 or later, then `npm install -g appium`.
- **Driver**: `appium driver install uiautomator2`, with the Android SDK, a JDK, `ANDROID_HOME` and `JAVA_HOME` set.
- **Device**: the cloud phone appears to Appium as an ADB device named `host:port`.
- **One session per phone**: two runners on the same phone will collide.

## How do you set up Appium for a cloud phone, step by step?

**Seven steps; commands from the Appium documentation and the UiAutomator2 driver page.** Run them on the machine that will run the tests.

1. **Check Node.js and npm** — Appium's requirements page asks for Node.js ^20.19.0 || ^22.12.0 || >=24.0.0 and npm >=10.
2. **Install Appium** — Run npm install -g appium.
3. **Set up the Android side** — Install the Android SDK and a JDK, then set ANDROID_HOME to the SDK folder and JAVA_HOME to the JDK folder.
4. **Install and check the driver** — Run appium driver install uiautomator2, then appium driver doctor uiautomator2. The goal is 0 required fixes needed.
5. **Connect the phone** — Run adb connect host:port with the values from your Support ticket, and check adb devices shows device.
6. **Start the server** — Run appium. It listens on http://127.0.0.1:4723/ by default.
7. **Start a session** — From your test client, open a session with the capabilities below, appium:udid set to host:port.

*Capabilities for a Droidkeep phone*

```json
{
  "platformName": "Android",
  "appium:automationName": "UiAutomator2",
  "appium:udid": "host:port",
  "appium:appPackage": "com.example.app",
  "appium:appActivity": ".MainActivity",
  "appium:noReset": true,
  "appium:newCommandTimeout": 300
}
```

## Which capabilities matter on a network device?

**Four capabilities do most of the work on a cloud phone.** Their meaning is quoted from the UiAutomator2 driver documentation.

*UiAutomator2 capabilities that matter when the test device is a cloud phone reached over ADB*

| Capability | Meaning (driver docs) | Value on a Droidkeep phone |
| --- | --- | --- |
| `appium:udid` | UDID of the device, as shown by `adb devices -l` | `host:port` |
| `appium:app` | Path to the app on the machine running the server | Your APK path, or leave out and use appPackage |
| `appium:noReset` | Skips the reset before the session if `true` | `true` to keep logins between runs |
| `appium:newCommandTimeout` | Seconds to wait for a new command | Raise it on a slow link, for example 300 |
| `appium:adbExecTimeout` | Milliseconds to wait for one ADB command | Raise it if commands time out over the internet |

## What changes when the device is in the cloud?

**Latency, and the need to reconnect.** Each Appium command travels over ADB to the phone and back, so a suite that takes 2 minutes on a USB phone takes longer over the internet. Raise `appium:newCommandTimeout` and `appium:adbExecTimeout` rather than adding sleeps.

If `adb` loses the phone, Appium loses it too. Start each CI job with `adb connect host:port` and `adb devices`, so the job fails early with a clear message. The [ADB guide](https://droidkeep.com/guides/how-to-connect-adb-to-a-cloud-phone/ "How do you connect ADB to a cloud phone?") lists the connection errors.

## How do you run Appium from CI?

**Install Appium and the driver in the CI image, connect the phone at the start of the job, then run the suite.** The phone stays on between jobs, so there is no device to boot. Keep the host and port in the CI system's secret store, not in the repository.

One phone serves one job at a time. For parallel jobs, rent one phone per runner and pass each its own `host:port`. The [testing devices page](https://droidkeep.com/android-app-testing-devices/ "Can a cloud phone replace Android test devices?") explains when a device farm covers more ground.

## Which Droidkeep size fits an Appium runner?

**Keep 8 for most app suites; Keep 4 for small apps.** The UiAutomator2 server runs on the phone next to your app, so a heavy app plus the driver needs headroom.

According to Droidkeep's survey of 16 November 2026, Genymotion SaaS billed $0.06 per minute per running device; Keep 8 costs $8.10 for 30 days, whatever the number of runs. The [8 GB phone page](https://droidkeep.com/8gb-cloud-phone/ "What do you get with an 8 GB cloud phone?") lists that size. Root is not included, so tests that need root will not run.

## Appium on a cloud phone: questions

### Does Appium need anything installed on the phone?

The UiAutomator2 driver installs its own server app on the device at the first session. No root is needed.

### Which Android versions does UiAutomator2 support?

Android 8 (API 26) and later since driver version 6.0.0, so Android 12 is covered.

### Can I use the Appium Inspector with a cloud phone?

Yes. Point it at your Appium server and use the same capabilities, with `appium:udid` set to `host:port`.

### Can Appium run on a server instead of my laptop?

Yes. The server must have ADB access to the phone; the driver also has `appium:remoteAdbHost` for an ADB server on another machine.

### Why does Appium see no device while adb does?

Appium may use another `adb` binary or server. Check that `ANDROID_HOME/platform-tools/adb devices` lists the phone.

**Verdict**

- **A cloud phone is an ordinary ADB device to Appium**: connect it, then set `appium:udid` to `host:port`.
- **Give each CI runner its own phone** and raise the timeouts for the network link.

## Sources

1. [Appium: system requirements](https://appium.io/docs/en/latest/quickstart/requirements/) — Appium (read 2026-11-16)
2. [Appium: install Appium](https://appium.io/docs/en/latest/quickstart/install/) — Appium (read 2026-11-16)
3. [Appium: install the UiAutomator2 driver](https://appium.io/docs/en/latest/quickstart/uiauto2-driver/) — Appium (read 2026-11-16)
4. [Appium UiAutomator2 driver](https://github.com/appium/appium-uiautomator2-driver) — Appium (read 2026-11-16)
5. [Genymotion pricing](https://www.genymotion.com/pricing/) — Genymotion (read 2026-11-16)

**A device for your test suite** Keep 8: 8 GB of RAM, Android 12, ADB on the plan. [Rent Keep 8 for 30 days](https://droidkeep.com/app/checkout/?plan=p8-30d&product=keep-8&from=guides-how-to-run-appium-tests-on-a-cloud-phone&lang=en) · [All guides](https://droidkeep.com/guides/ "Which cloud phone guides does Droidkeep publish?")

---

Droidkeep: Droidkeep rents Android phones in the cloud that stay on 24/7: apps, idle games and automation keep running when your own screen is off, with the screen in the browser and ADB over the network. 4, 8 or 16 GB of RAM, from 1 day to 365 days. Paid in crypto, no KYC.
