Phone Box Farm FAQ & Setup Guide

Phone Box Farm (also called Phone Farm Box) is a free Windows desktop application for managing large-scale phone farm operations. It lets you control up to 20 phone channels simultaneously, switch between USB and OTG modes per channel, monitor power voltage / fan current / case temperature in real time, and configure hardware parameters like fan speed and boot mode. It officially supports A20, P20, P30, and X80 phone farm controller hardware.

Yes. Phone Box Farm is 100% free software — often called freeware. Every feature on every release is fully unlocked with no license key, no activation, no trial period, and no hidden in-app purchases. You may use it for personal or commercial phone farm operations without restriction. Download the official version only from www.phonebox.farm to ensure you have a clean, unmodified copy; third-party download sites sometimes bundle adware.

Phone Box Farm runs natively on Windows 7 SP1, Windows 8.x, Windows 10, and Windows 11 — both 32-bit and 64-bit editions. We officially test on Windows 10 22H2 and Windows 11 23H2. Linux and macOS users can run it inside a Windows VM (VMware, VirtualBox, Parallels) with USB passthrough enabled. A native Linux build is on our long-term roadmap but has no release date yet.

Three easy steps: 1) Download the installer from www.phonebox.farm/download.html. 2) Run PhoneBoxFarm_1.0.6_Setup.exe and follow the setup wizard (accept license, choose install directory, click Install). 3) Launch the app via the desktop shortcut. That's it — the Phone Box Farm driver package is bundled into the installer so there's no separate driver step unless the auto-install fails on a very locked-down corporate PC.

Use Serial Connection (USB/COM) when the PC is physically close to the Phone Box Farm hardware (same desk, same rack). It's zero-configuration and has the lowest latency. Use Network Connection (TCP/IP over Ethernet or Wi-Fi) when you need remote management — e.g. the control PC is in an office and the phone farm is in a dedicated equipment room. Both modes use the exact same control panel interface, so switching between them won't require re-learning anything.

First connect via Serial Connection. Once the device is listed in the Device List (left panel), click the System Info main tab. Locate the IP Address, Subnet Mask, and Gateway rows — each has a blue Edit pencil icon next to it. Click Edit, type in the values assigned by your network administrator, then press Enter or click elsewhere. The device will apply the new network configuration and briefly reconnect.

Phone Box Farm officially supports four hardware platforms sold under the A/P/X product line: A20 (entry-level 20-channel controller), P20 (mid-range with USB 3.0 and Gigabit LAN), P30 (premium 20-channel with smart power regulation and enhanced cooling), and X80 (flagship 80-channel rack-mountable chassis with redundant PSUs). The header inside the app explicitly reads "Software supports A20 P20 P30 X80 devices" — those are the four we validate against every release.

Yes, for individual control: each unit will show up as a separate entry in the Device List with its own COM port (serial mode) or IP address (network mode). Click the connect button on whichever one you want to control right now. For simultaneous control of multiple 20-channel units from one interface, our recommended setup is to use X80 chassis, which natively stack up to 4 units (80 ports each) and expose them as a single logical device to Phone Box Farm software.

The controller itself (A20/P20/P30/X80) idles at around 5–12 W depending on fan speed — very low. Power draw is dominated by the phones you plug in. Count roughly 3–7 W per idle smartphone and 7–15 W per phone under load (screen on + CPU active). A fully populated 20-channel Phone Box Farm with mid-range Android handsets idles around 100–150 W (plus enclosure fan overhead) and peaks at 250–400 W during heavy workloads. We recommend the 5V power setting (Settings tab) for most deployments.

In the Phone Box Farm control panel, each channel has three colored buttons: USB Mode (green) sets the port to standard USB client/host mode — use this for adb/fastboot, MTP transfers, and standard app testing. OTG Mode (blue) switches to USB On-The-Go, letting a phone talk to USB peripherals (dongles, card readers, another device). OFF (red) fully de-energizes the channel for a hard power reset without physically unplugging the phone. Use the top row of big buttons (All USB Mode / All OTG Mode / All Power Off / All Restart) to apply to all 20 channels at once.

Top cards are instant readouts: Power Voltage should sit close to 11.70 V for a 12 V rail or 5.00 V if you've set 5 V output; Fan Current (0.500 A typical) shows how hard the fans are pulling — higher means higher speed; Case Temperature (25 °C idle is normal) tells you the enclosure temp — anything above 55 °C for extended periods warrants high-fan mode or better room cooling. Below, the Detailed Status Monitoring table adds MIN / MAX / AVG columns, and the History Data Trend chart visualizes the last 10 / 30 / 60 / 1440 minutes for any of the three parameters.

Low Speed: Quieter, recommended when room temperature is under 22 °C (72 °F) and under 50% channel load. Medium Speed: Default balanced profile — our pick for most 24/7 production farms. High Speed: Use when running all 20 channels at 100% load, or when the room runs warmer than 28 °C (82 °F). Always watch the Case Temperature sensor on the Device Status tab; if it creeps past 50 °C, bump up the fan speed.

Default Boot Mode (Settings tab, three options) determines the channel state immediately after the Phone Box Farm hardware is powered on or rebooted. Keep Off: Channels stay dead until you manually turn them on — safest for maintenance or shared setups. USB Mode: Our recommended default — channels come up ready for adb and standard use. OTG Mode: Only for specialized farms that need host/peripheral mode from the moment the devices boot.

When the app shows "No box found temporarily, scanning in progress", work through this checklist: 1) Wait the full 60 seconds; a large Install Driver button appears on timeout — click it. 2) Ensure the Phone Box Farm hardware is plugged into a motherboard-back-panel USB 2.0+ port (not a front-panel hub, monitor hub, or unpowered USB splitter). 3) Swap the USB cable for a known-good one (data not charging-only). 4) Open Windows Device Manager → expand Ports (COM & LPT) and Universal Serial Bus controllers; right-click any Unknown Device / yellow bang → Update Driver → Browse my computer → pick the Driver subfolder inside your Phone Box Farm install directory (usually C:\Program Files\Phone Box Farm\Driver). 5) For Network mode, verify PC and hardware share the same subnet, firewall allows outbound TCP on port 8080 (default), and the IP shown on the hardware's LCD is what you entered. Still stuck? Open the Communication Log tab and email a screenshot to [email protected].

"Disconnected" in the Channel Control & Status grid means the channel has no USB handshake — not that the Phone Box Farm controller is offline. Typical causes: the phone is in OTG-only developer mode (toggle Default USB Configuration in Android Developer Options), a faulty cable or damaged USB-C/micro-USB port on the phone itself, debris in the port, or that channel was set to OFF (red) — press the green USB button to try bringing it up. Also try swapping that phone into another channel to rule out a bad port on the Phone Box Farm hardware.

Try these, in order of effectiveness: 1) Ambient room AC — the cheapest fix; keep the farm room at 20–24 °C (68–75 °F). 2) Raise fan speed to High in Phone Box Farm → Settings. 3) Make sure the Phone Box Farm chassis has at least 10 cm of empty space on both intake and exhaust sides — never stack loose phones directly on the enclosure. 4) If running at 4.3 V output, verify the voltage is necessary; dropping to 5 V (or vice versa) doesn't inherently change thermals, but mismatched voltage and phones will waste power as heat. 5) For dense X80 deployments, rack-mount with dedicated front-to-back airflow and a 1–2 U spacer between chassis.

Rare, but here's the full recovery sequence: 1) Press Ctrl+Shift+Esc to open Task Manager → Details tab → end any lingering PhoneBoxFarm.exe or PhoneFarmBox.exe process. 2) Unplug the USB cable(s) from the Phone Box Farm hardware first. 3) Re-launch the app; if it starts cleanly, then plug the hardware back in. 4) If still crashing, delete the config file at %APPDATA%\Phone Box Farm\config.json and try again (this resets preferences to factory defaults). 5) Make sure Microsoft Visual C++ 2015-2022 Redistributable x86 + x64 is installed (see the download page help section). 6) Turn off Windows Defender Exploit Protection → Program settings → Add program to customize → Choose PhoneBoxFarm.exe → Override system settings → Disable CFG and Force ASLR temporarily to test.

Method A (easy): Visit www.phonebox.farm/download.html and grab the newest installer. Run it on top of your current install — all user settings and saved profiles are preserved. Method B (from within the app): Open System Info and compare the reported Software Version against the "Latest" badge on the download page. We don't yet have a background auto-updater because Phone Box Farm deployments often run on isolated PCs without internet — manual update guarantees the operator is in control.

Phone Box Farm is distributed as proprietary freeware. You may download and install it on any number of PCs for personal or commercial use, and you may mirror the installer internally for deployment purposes in your organization. You may not publicly re-host the installer on third-party download sites, bundle it with adware/malware, reverse-engineer it, or claim it as your own product. If you want to distribute it as part of a hardware sales bundle, contact us for partnership options — we love working with Phone Box Farm resellers.

Email us any time at [email protected]. Include these to get a same-day answer: 1) Your exact Phone Box Farm software version (System Info tab). 2) The hardware model (A20 / P20 / P30 / X80). 3) Windows version and whether 32- or 64-bit. 4) A screenshot of the error, plus the Communication Log export if relevant. We reply to every genuine email within 24 business hours — often much faster.