How we set up an Android farm
The provisioning sequence behind a PhoneFarm: sizing, images, network profiles, and handing over the console.
Standing up an Android farm is less about buying phones and more about deciding what “ready” means. This is the sequence we run before you see a login.
1. Size the farm
How many concurrent devices? Which Android versions? Do operators need remote control, ADB, or both? Starter farms often begin at eight devices. Working farms land around thirty. Enterprise farms start from the workload, not a catalog row.
2. Choose images
We ship current and recent Android images. If you pin a Play services level or a custom overlay, that becomes part of the farm profile. Images are applied per device or as a saved preset.
3. Draw network and app profiles
Low-latency office Wi-Fi is not the same as a constrained mobile network. Profiles let you switch without re-provisioning hardware. App sets install the packages your QA or automation expects on first boot.
4. Hand over admin
You get the console. Create devices, invite operators, open sessions, and read logs. We stay on the metal: power, density, and replacements.
If you already know the device count, request a farm. If you do not, start with the question the farm is supposed to answer — and we will size from there.