---
title: "Android images with the machine executor"
description: "Use the Android machine image on the Linux machine executor with the Android orb or manual configuration, and review resource classes and preinstalled tools."
platform: "Cloud, Server"
doc_version: "Server"
last_updated: "2026-10-26"
---

> For current CircleCI product defaults, deprecated patterns, and Cloud/Server differences, see [AGENTS.md](https://circleci.com/docs/AGENTS.md).
>
> For the complete documentation index and site structure, see [llms.txt](https://circleci.com/docs/llms.txt).

# Android images with the machine executor

## Overview

You access the Android machine image through the [Linux Machine Executor](https://circleci.com/docs/reference/configuration-reference/#available-linux-machine-images-cloud), like other Linux machine images on CircleCI. The Android machine image supports nested virtualization and x86 Android emulators, so you can use it for Android UI testing. It also comes with the Android SDK pre-installed.

## Using the Android machine image

You can configure the Android image in your configuration using [Orbs](https://circleci.com/docs/orbs/use/orb-intro/), or manually. The Android orb simplifies your configuration. More complex and custom configurations may work better with manual configuration instead of the orb. This document covers both use cases. Refer to the [Examples](#examples) section below for more details.

## Available resource classes

### Gen1

| Class | vCPUs | RAM | Disk Size | Cloud | Server |
| --- | --- | --- | --- | --- | --- |
| `medium` | 2 | 7.5 GB | 150GB | **Yes** | **Yes** |
| `large` | 4 | 15 GB | 150GB | **Yes** | **Yes** |
| `xlarge` | 8 | 32 GB | 150GB | **Yes** | **Yes** |
| `2xlarge` | 16 | 64 GB | 150GB | **Yes** | **Yes** |
| `2xlarge+` | 32 | 64 GB | 150GB | **Yes** | **Yes** |

### View resource usage

To view the compute resource usage for the duration of a job in the CircleCI web app:

1.  In the CircleCI web app, select your org from the org cards on your user homepage.
    
2.  Select **Pipelines** from the sidebar and locate your pipeline from the list. You can use the project, branch, date, and status search options to help.
    
3.  Select the job you want to access by selecting the job name.
    
4.  Select the **Resources** tab to view CPU and RAM usage for the duration of the job.
    

You can use these insights to decide whether to make changes to the job’s configured resource class.

> **Image:** Resources tab

Figure 1. Resources tab in web app for a job

## Pre-installed software

View the latest update announcement on our [Discuss](https://discuss.circleci.com/c/ecosystem/circleci-images/) page for a list of current pre-installed software.

## Examples

The following examples show how to use the Android machine image, both with and without orbs.

### Using the Android image

Android machine images are only available on server installations on Google Cloud Platform (GCP).

To use the Android image in your projects, set the `image` key to `android-default` in your jobs.

```yaml
version: 2.1

jobs:
  my-job:
    machine:
      image: android-default
    steps:
    # job steps here
```

You can also use the Android orb. Your server administrator needs to import the orb first. You also need to define the `android-default` image for the machine executor, as shown in the example below, rather than using the default executor built into the orb. View the [CircleCI Server Orbs](https://circleci.com/docs/server-admin/latest/operator/managing-orbs/) page for instructions on importing orbs.

This example shows how you can use granular orb commands to achieve what the [start-emulator-and-run-tests](https://circleci.com/developer/orbs/orb/circleci/android#commands-start-emulator-and-run-tests) command does.

Make sure to replace any placeholder versions in the example.

```yaml
# .circleci/config.yml
version: 2.1
orbs:
  android: circleci/android@x.y.z
  # https://circleci.com/developer/orbs/orb/circleci/android for latest version
jobs:
  test:
    machine:
      image: android-default
    steps:
      - checkout
      # Create an AVD named "myavd"
      - android/create-avd:
          avd-name: myavd
          system-image: system-images;android-29;default;x86
          install: true
      # By default, after starting up the emulator, a cache will be restored,
      # "./gradlew assembleDebugAndroidTest" will be run and then a script
      # will be run to wait for the emulator to start up.
      # Specify the "post-emulator-launch-assemble-command" command to override
      # the gradle command run, or set "wait-for-emulator" to false to disable
      # waiting for the emulator altogether.
      - android/start-emulator:
          avd-name: myavd
          no-window: true
          restore-gradle-cache-prefix: v1a
      # Runs "./gradlew connectedDebugAndroidTest" by default.
      # Specify the "test-command" parameter to customize the command run.
      - android/run-tests
      - android/save-gradle-cache:
          cache-prefix: v1a
workflows:
  test:
    jobs:
      - test
```