Android
froog new NAME --os android (API: "os": "android") starts Ubuntu 24.04 with an Android 14 phone running in it from boot. It's Redroid: Android in a container on the sandbox's own kernel, not an emulator, so it needs no nested VM and answers about 2-3 times faster than the Android emulator in the same sandbox. Everything else on the sandbox is as on Ubuntu (the same tools, desktop, agents and froog commands). It needs a small sandbox or larger (Android itself uses about 600 MB of memory); lite is refused. It boots fresh rather than from the pre-booted pool: measured on November 19, 2026, Android was usable about 2 minutes 10 seconds after froog new (the sandbox is running well before that; froog-android wait waits for the rest).
$ froog new phone --os android --size small
$ froog ssh phone
user@phone:~$ froog-android wait
Android 14 ready on localhost:5600
user@phone:~$ adb install app.apk
user@phone:~$ adb shell am start -n com.example/.MainActivity
adb. The phone is localhost:5600 to adb, which is installed, and ANDROID_SERIAL is set, so plain adb shell, adb install, adb logcat and Gradle's installDebug reach it. adb listens only inside the sandbox (127.0.0.1): to use it from your computer, froog forward phone 5600 and adb connect localhost:5600. adb matches serials as text, so name it localhost:5600 (or leave -s out): adb -s 127.0.0.1:5600 says the device isn't found unless you adb connect 127.0.0.1:5600 first, which lists it twice. Its screen is 720x1280 at 320 dpi.
Managing it. froog-android wait blocks until Android has booted (up to about two minutes after the sandbox starts), froog-android status says whether it runs, and froog-android reset wipes its apps and data and boots it as new (about a minute). It runs as the froog-android system service (sudo systemctl restart froog-android). Its data is on the sandbox's disk (/var/lib/froog/android), so installed apps and their data stay through stop, start, snapshots and forks. Each new sandbox's phone is a device of its own, with its own Android ID (a fork keeps its source's, like the rest of the disk; froog-android reset gives it a new one).
For agents. On an Android sandbox the agents' computer tools include phone_state (a screenshot and the screen's UI tree in one call: each element's text, id, whether it can be tapped or typed into, a ref and its center), phone_tap (by ref or point, or a long press), phone_swipe (a direction or exact points), phone_type (into the focused field or one it taps first, optionally clearing it or pressing Enter), phone_key (home, back, enter, app_switch and the rest), phone_launch, phone_open_url, phone_install (an APK in the sandbox) and phone_apps. They work over adb and don't start the desktop. A screenshot and a UI tree take 1-2 seconds each (phone_state takes both at once), so refs from the tree are cheaper than repeated screenshots. Right after a sandbox starts, a tool may answer that Android is still booting: call it again a little later.
Watching it. froog desktop phone shows the phone as a window on the sandbox's desktop (scrcpy, installed the first time the desktop opens), live while the agents use it. Click and type in the window to use the phone yourself. Closed, it stays closed until the desktop is opened again; it comes back by itself when Android restarts. froog-record-desktop records it with the rest of the desktop.
Limits. It's AOSP: no Google Play Store or Google Play services, so apps that need them (Google sign-in, Maps, Firebase Cloud Messaging) won't work fully. For those, run the Android emulator with a Google APIs system image in any sandbox (/dev/kvm is there for nested VMs; slower). Graphics are rendered in software (no GPU), there's no camera, sensors or telephony, and only x86_64 apps and apps without ARM-only native code run. adb types only ASCII text.