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

Architecture Overview

BoxPhone runs on four main layers — each layer with a clear separation of responsibility, so the system can scale without rewriting itself every time you add devices.

1. Hardware layer — phone array, USB hub, power, cooling
2. Connection layer — ADB over USB or ADB over TCP/IP
3. Automation layer — the script engine that orchestrates commands across the system
4. Dashboard layer — UI for monitoring and dispatching commands

Hardware Layer

Each rack contains smartphones arranged in a layout designed for simultaneous heat dissipation and power delivery — Sikrid designs and assembles every rack in Thailand.

Key components:

• Powered USB hub — supplies sufficient 5V to each device while transmitting data
• OTG / USB-C splitter — separates the data path of each device
• Active cooling — fan layout designed for thermal balance
• Power rail — separated circuits to prevent cascading failure

Connection Layer (ADB)

ADB (Android Debug Bridge) is the main protocol for communicating with Android from a host computer. It has two modes:

ADB over USB

Direct connection through a USB cable — the most stable option with the lowest latency, ideal for real-time work.

# enumerate devices
adb devices -l

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

ADB over TCP/IP

Connection over Wi-Fi / LAN through port 5555 — frees the USB connection so the device sits more steadily, at the cost of higher latency.

# 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 some workloads (such as batch installs) and TCP/IP for others (such as long-running automation).

Automation Layer

This is the layer that lets one person command 1000 devices

Core responsibilities:

• Schedule tasks by time or condition
• Parallel execution + retry on failure
• Per-device state management (login state, account, proxy)
• Variable substitution (random delay, random wording)
• Result aggregation and alerting

An example script command:

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

These commands run through ADB shortcut keys plus a wrapper script.

Network Layer (Proxy)

Each device must have its own identity — otherwise the platform will flag them as a group.

Ways to give every device its own IP:

• Use a separate SIM per device — IP comes directly from the carrier
• Use a 4G proxy farm — real mobile IPs at scale
• Use residential proxies — real home IPs through a VPN tunnel

Which option fits which workload — see the Proxy Selection Guide

Dashboard Layer

The Sikrid BoxPhone dashboard is responsible for:

• Showing the status of every device — online / offline / working / error
• Dispatching batch commands — "run task X across these 50 devices"
• Remote screen / single-device control when an issue needs investigation
• Logs + analytics — so you know the success rate of every task

Scaling from 10 → 1000 Devices

The challenges shift as device counts grow:

Summary

A good BoxPhone is a system in which every layer is designed to communicate — durable hardware, stable connections, flexible automation, and a dashboard that gives you the full picture.

If the design is wrong, the system breaks at 50–100 devices — and has to be rebuilt from scratch.

Sikrid designs all four layers in Thailand, and continues to refine them. See the products on the Product page.