1. PhoneRun
  2. Guides
  3. Phone farm setup

Phone farm setup: the parts, the steps for each phone and what to test

A phone farm setup needs five things: phones, powered USB hubs, a host computer, control software and a room that stays cool. This page is the plan for the first PhoneRun rack: the parts, the budget and the checklist for each phone. The first phone went onto the host on November 16, 2026. So some of this is now tested on one phone and the rest is still a plan, and each section says which.

Updated November 16, 2026 by the PhoneRun team. PhoneRun is not open yet: we are setting up the first phones.

Phone farm parts list and budget

PartOur planBudget
PhonesNew, unlocked Moto G Play (2026), all one model$169 each
Powered USB hubsOne hub with its own power supply for every 10 to 12 phonesAbout $50 per phone for all three, shared
Host computerOne small Linux PC for every 10 to 15 phones
Cables, shelves, fansShort data cables, open shelving and fans
Backup battery, router, rackEnough battery to ride out a short power cutAbout $800 once, with company setup
Carrier linesOne SIM and one unlimited plan per phoneAbout $25 a month each
SparesOne extra phone for every ten$169 each

For ten phones that is about $3,160 to start and about $250 a month. Four notes on those numbers:

  • $169 is what we paid for each of the first two phones. It is also the price 9to5Google reported when the Moto G Play (2026) launched in November 2025, so a sale would bring the budget down.
  • The hub and host ratios are a plan. We have not loaded a hub with twelve phones yet.
  • The host for the first phones is a 2018 Intel Mac mini we already had, not the Linux PC in the plan.
  • DistrictDroid published its own list for ten phones: $1,500 for the devices, $200 for a hub or charging rack, $700 for a computer, $300 for cables and hardware and $400 to set up the SIMs. That is about $3,100, close to ours.

Buy one model and stick with it. Mixed phones mean mixed settings, mixed cables and surprises.

On hubs, GeeLark's build guide puts it well: "Passive hubs usually cannot power many phones reliably. This is not the place to save money."

We saw why on the first day. Plugged straight into the Mac mini's own USB-A port, the phone drew 500 mA and reported "Charging slowly", with more than eight hours to full. That is fine for testing one phone. It is not a way to keep a shelf charged.

Phone farm rack or box

A rack is whole phones on shelves. You can see every screen, pick a phone up and swap one in a minute. The cost is space, and batteries that need watching.

A box is a case built for the job. ToyBox's guide describes boxes made from phones "where the battery and screen are completely removed, meaning that only the motherboard itself remains". Cellhasher says its kits let you "operate phones without batteries, directly powered by the unit's PSU". For scale and price, TechRadar reported in September 2025 on a box that holds 20 phones, at $700 empty or $1,900 with the phones, and a rack of 21 boxes that holds 420.

We are starting with whole phones on shelves and have not used a box. Our reasons are simple: at ten phones a shelf is enough, and we want each phone to stay the stock handset it was sold as.

Setting up each phone

This is the checklist from our setup notes. We have now run it on the first phone, a Moto G Play (2026) on Android 16.

  1. Unbox the phone, charge it and install the pending system updates.
  2. Put in the SIM and check that mobile data works.
  3. Open Settings, then About phone, and tap Build number seven times. That switches on Developer options.
  4. In Developer options, turn on USB debugging. Also turn on Disable adb authorization timeout, so the phone does not forget the host after a week. Once the phone is connected, the host can set the same thing with adb shell settings put global adb_allowed_connection_time 0.
  5. Plug the phone into the host, unlock it, tick Always allow from this computer and accept.
  6. Turn Wi-Fi off if the phone should use its carrier line.
  7. Turn Auto-rotate off. With it on, a rotate command from the computer snaps back.
  8. Decide on the screen lock. We set it to None for now. A phone with no lock is open to anyone who can touch it, so the room has to be the lock.
  9. Turn on the charge limit if the phone has one. On the Moto G Play (2026) it is under Settings, Battery, Overcharge protection, and it was off on ours.
  10. Run adb devices -l on the host and make sure the phone is listed.
  11. Open its screen from the host and tap around.
  12. Label the phone and its cable with the same number.

Three of those steps deserve a reason.

Step 5. On our first phone the prompt never appeared. We tried other USB-C ports and a second USB-C to USB-C cable. The phone charged every time, and the computer saw nothing at all. The phone had taken the host side of the link: its USB Preferences screen showed "Connected device" with "Couldn't switch" under it. A USB-A to USB-C cable in a USB-A port fixed it at once. That screen went on saying "Couldn't switch" after the fix, so trust adb devices -l and not the screen. Test one phone with the exact cable and hub before you buy a dozen of either.

Step 9. Read the screen on your own phone and not the manual. On our Moto G Play (2026) the setting says: "To keep your battery healthy, charging will be limited to 80%. Once a week, your battery will charge to 100% to keep it calibrated." Motorola's help page for the 2026 Moto G describes a different rule, "limiting its charge to 80% if it's been plugged in for three days", and we could not find the setting in the help pages for the Play at all.

Step 10. A cable can charge a phone and carry no data. Coronium's hardware guide says it plainly: "A phone displaying a charging icon is not evidence that the host has a working data channel."

We have budgeted 20 minutes for each phone. The first one took far longer because of the cable. We will time the next ones and put the figure here.

The software

adb is Android's own tool for talking to a phone over USB. scrcpy is a free, open source program that shows a phone's screen on your computer and sends your mouse and keyboard to it. With those two you can run a phone farm from one desk. The remote Android phone guide has the commands.

Reaching the phones from somewhere else is harder. Something has to send each screen to a browser, and it has to sit behind a login, because anyone who reaches the host can use every phone. Coronium's advice is the right instinct: "Do not expose debugging access merely to make remote scheduling easier."

For PhoneRun we wrote a small program that runs on the host. It starts scrcpy's phone side server, takes the video the phone has already encoded and passes it to the browser, which decodes it. The host does not decode or encode any video. With one phone streaming, our host spent about 5 percent of one processor core on it. We have not loaded it with ten phones yet. Our plan is also that the rack accepts no incoming connections: each host dials out.

What works in the test build: opening a phone in a browser, tapping, dragging, typing, pasting, rotating and up to four people watching one phone. What is not built yet: accounts, team seats and the activity log.

What we have measured, and what is left

Every one of these is a question a parts list cannot answer. These are the results from the first phone on November 16, 2026. The remote Android phone guide has the full numbers.

QuestionResult so farStill to test
Is the delay acceptable?On the host's own network, 73 to 85 ms from a quick click to the changed picture, and 121 to 130 ms with a click held for 60 msA home connection and a phone hotspot
Does it hold up on a poor connection?On a good connection, an hour of scrolling ran at about 49 frames a second with no restartsA poor connection
How many phones can one host carry?One phone took about 5 percent of one processor coreEvery phone at once
Do the phones cope?After an hour of streaming a scrolling list, the battery went from 23 to 24 °CA full day, and a heavier app
Does typing work in real apps?Emoji, accents, Japanese and a pasted link arrived intact in the phone's own search boxThe social apps, on a test account

The room

  • Cool and dry, with air moving across the shelves.
  • Phones laid out side by side, never stacked.
  • A smoke detector above the rack.
  • A backup battery for the host, the hubs and the router.
  • Wired internet for the host.
  • A door that locks.

Power draw is modest. Multilogin estimates about 200 to 300 watts for 50 phones.

Upkeep

Our plan is to check battery temperatures every day and to pull any phone that runs hot or whose back is lifting, with a spare going in the same day. Expect to restart frozen phones, replace a hub now and then, and take system updates in batches so that one bad update does not hit every phone at once. DistrictDroid puts the upkeep of ten phones at 5 to 15 hours a week. We will report our own hours once we have some.

When a phone farm setup is not worth it

If you need fewer than ten phones, or you do not have a room and someone to look after it, the setup can cost more in time than it saves in money. The phone farm guide works through the build or rent maths. PhoneRun will rent the same phones described here, already set up, for $100 per phone per month.

Questions

How many phones can one computer run?

We do not know yet for our own setup. One streaming phone took about 5 percent of one processor core on our host, a 2018 Intel Mac mini. Our plan is one small host for every 10 to 15 phones, and we will test it by opening every phone at once. For a PC that mirrors phones in scrcpy windows, GeeLark's build guide suggests 16 GB of memory as the baseline and estimates 150 to 300 MB for each window.

Do the phones need to be rooted?

No. scrcpy's README says it does not require root access or an app installed on the device. USB debugging, turned on in Developer options, is enough.

Does each phone need a SIM?

Not for testing an app, where Wi-Fi is enough. If each phone should be on its own carrier line, then yes, one SIM and one plan per phone. The PhoneRun plan is a SIM in every phone.

What does a ten phone setup cost?

Our budget is about $3,160 to start, counting one spare phone and the shared gear, and about $250 a month for ten carrier lines. DistrictDroid's published breakdown for ten phones comes to about $3,100.

Should the phones stay awake all day?

They do not need their screens on. Android has a Stay awake switch in Developer options, but scrcpy can keep a plugged in phone awake by itself, and it can mirror a phone with the screen turned off.

Sources

Each page below was read on November 16, 2026. Prices and features change, so check the page itself.

The products and publications named here belong to their owners. PhoneRun is not affiliated with any of them.