How BoxPhone Works: A Deep Dive into Controlling 1 to 1000+ Devices

The Big Picture

BoxPhone is built on four layers, each with one clear job. Splitting it up this way means you can grow the system without rewriting it every time you add more phones.

1. Hardware — the phones, the USB hub, the power, the cooling
2. Connection — ADB over USB, or ADB over Wi-Fi
3. Automation — the script engine that fires commands across the whole fleet
4. Dashboard — what you actually look at to watch the system and send commands

Hardware

Inside one rack, the phones are arranged so air can flow between them and power reaches every device evenly. Sikrid designs and assembles every rack in Thailand.

The pieces that matter:

• Powered USB hub — feeds enough 5V to each phone while moving data through
• OTG / USB-C splitter — keeps each phone's data path separate from the rest
• Active cooling — fans placed so heat doesn't pile up on the bottom row
• Separate power rails — one phone tripping doesn't drag the others down

Connection Layer (ADB)

ADB (Android Debug Bridge) is the main way a computer talks to Android. Two flavors:

ADB over USB

Plug in a USB cable, done. The most stable option with the least lag — good when you need things to happen right now.

# enumerate devices
adb devices -l

# connect to a specific device by serial
adb -s SERIAL shell input tap 540 1200

ADB over TCP/IP

Over Wi-Fi or LAN through port 5555. You can pull the USB cable once it's running — the phone sits more steady, but you pay a bit in lag.

# enable tcpip on device first (via USB)
adb tcpip 5555

# then connect over network
adb connect 192.168.1.42:5555

BoxPhone uses both modes together — USB for jobs like batch installs, TCP/IP for long-running automation.

Automation Layer

This is the part that turns one person into a fleet of fingers.

What it handles:

• Schedules tasks by time or condition
• Runs in parallel, retries when something fails
• Tracks the state of every phone (logged in? which account? which proxy?)
• Randomizes delays and wording so the phones don't act in lockstep
• Pulls results together and alerts you when something goes sideways

Roughly what a script looks like:

open_app("com.tiktok.android")
wait(3..6)            # human-like delay
tap_xy(540, 1200)
swipe_up()
sleep(2..5)

Underneath, this all becomes ADB shortcut keys wrapped by a script.

Network Layer (Proxy)

Every phone needs its own identity on the internet. Without that, the platform sees a herd and treats it as one.

Three ways to give each phone its own IP:

• One SIM per phone — IP comes straight from the carrier
• 4G proxy farm — real mobile IPs, scaled up
• Residential proxies — real home IPs piped through a tunnel

Which one fits which job? See the Proxy Selection Guide

Dashboard Layer

The Sikrid BoxPhone dashboard does this for you:

• Shows the state of every phone — online, offline, working, error
• Fires batch commands — "run task X on these 50 phones"
• Lets you take over one phone's screen when you need to check something
• Keeps logs and stats — so you know which task succeeded how often

Scaling from 10 to 1000 Phones

The headaches change shape as the fleet grows:

Summary

A good BoxPhone is one where every layer is built to talk to the next — solid hardware, steady connection, flexible automation, and a dashboard that shows you the whole picture.

Design it wrong and the whole thing falls apart around the 50-100 phone mark — and you end up rebuilding from scratch.

Sikrid builds all four layers in Thailand, and keeps tightening them. Have a look at our products on the Product page.