A repurposed Android phone displays PC system stats and controls on a desk beside a Windows monitor.
PhoneBox is a free, open-source project that turns a retired Android phone into a touchscreen desk panel for a Windows, Linux or macOS computer. MakeUseOf describes it as an app that turns an old Android phone into a touchscreen control panel for your computer. The practical question is which old phones actually work, what setup involves, and what to check before installing an unsigned Windows agent. The project's own documentation answers most of that.

A repurposed Android phone displays PC system stats and controls on a desk beside a Windows monitor. What PhoneBox is​

PhoneBox pairs a full-screen Android app with a small desktop agent. The agent gathers data and runs actions on the PC. The phone displays the panel. PhoneBox is an independent project, not a Microsoft product, and Windows is one of three supported desktop platforms.

The project lists several uses:

  • PC monitoring: CPU, GPU, RAM, disks, network and ping, plus charts, GPU details and process controls.
  • Touch controls: App and URL shortcuts, key combinations and macros, plus application audio, microphone, media, OBS and system controls through Control Deck.
  • Layouts: You start from a template such as Home, System, Music or Automation, then adapt a 12 × 6 grid to your phone.

The 124-widget figure is current. The project's live demo also cites 124 widgets and a visual layout editor. That demo runs version 0.9.21 with made-up data, so you can try the editor in a browser before installing anything.

Widget availability varies by machine. The README says widgets depend on the host's hardware, installed tools and permissions. On Windows, GPU data comes from Windows counters, with NVIDIA cards read through nvidia-smi. Extra sensors need LibreHardwareMonitor. The project says its native audio and display controls are Windows-only. So the per-app volume trick MakeUseOf highlights is a Windows strength. It is not a guarantee on every platform.

Which old phones work​

This is where MakeUseOf's report needs care. The project's changelog says version 0.9.19, dated November 17, 2026, extended installation to Android 5.0 and 6.0. Before that, the minimum was Android 7.0.

  • Android 6: Widgets scale fully, because its WebView updates go up to version 106. The maintainer tested a Galaxy Tab S on Android 6.0.1 and reports that Wi-Fi pairing, every widget and page swiping work.
  • Android 5: The last available WebView is version 95. The panel runs, but widgets don't scale as well and a WebView notice stays on screen. The maintainer says this had not yet been tried on an Android 5 device.
  • Very old WebViews: A WebView older than Chromium 80 can't run the panel. PhoneBox now says so on the phone and in Settings, with how to update it, instead of showing a black screen.

The README says Android 5+ is required, with Android 6 or later recommended. Treat Android 5 as "installs and runs" rather than "polished."

You may see older write-ups with stricter requirements. A Lockergnome piece from about five days ago says Android 9 or later. That matches earlier versions of the project, and the README now says otherwise. When guides disagree, trust the current repository.

Setup: USB or Wi-Fi​

Whichever route you choose, you install the desktop agent first. The README gives a PowerShell one-liner for Windows 10/11 x64 and a shell script for Linux and macOS. It describes setup as downloading the latest release, checking its SHA-256 checksum, offering missing dependencies and start-at-login, and opening the settings page. Release agents bundle .NET, so you don't need to install the runtime separately. Windows on ARM and musl-based Linux such as Alpine have no release builds.

The project also tells you to read the setup scripts before running them. That is sensible advice for any pipe-to-shell install. Manual download and Scoop installs are also offered.

USB route:

  • Enable Developer options and USB debugging on the phone.
  • Connect a data-capable cable.
  • Accept the phone's authorization prompt.
  • Let setup install the app, or use the "Install the phone app" option in Settings → General.

The README notes this route wakes and opens the panel on connection and supports app updates over adb. It also advises authorizing USB debugging only on computers you trust.

Wi-Fi-only route:

  • Install the APK from the project's latest release. It is not in any app store, so you sideload it.
  • Wi-Fi is off by default. Open the settings page from the tray icon or at the local address 127.0.0.1:8765.
  • Turn on General → Wi-Fi & Tailscale → "Let the phone connect without the USB cable".
  • Click Save, then Restart to apply.
  • Choose "Pair a phone over Wi-Fi", scan the QR code and confirm the matching check code.

This route needs no adb or developer options. The trade-off is that you must install app updates manually unless you later configure USB.

Windows security and privacy​

The main caveat for Windows readers is that the release agents are currently unsigned while the SignPath Foundation application is pending. SmartScreen or antivirus software may warn about or block them. An unsigned binary triggering a warning is expected behavior, not proof of malware. It is still a reason to be careful:

  • Download only from the project's official releases.
  • Let setup verify the checksum, or compare it yourself if you install manually.
  • On managed PCs, check with your administrator first. The changelog says an AppLocker or similar policy block points you to the administrator.
  • Smart App Control is stricter. The changelog says setup now reports that PhoneBox is installed but can't run until the agent is signed.

Disabling SmartScreen globally, as MakeUseOf's article hints, is a heavy-handed response to one app. Weigh that choice yourself.

On privacy, the README says the settings server listens only on the loopback address 127.0.0.1:8765, and USB reaches it through adb reverse. Optional Wi-Fi uses HTTPS on port 8766 with a pinned certificate and a paired key. The phone sends IDs only, and commands stay on the computer. The project says it has no telemetry, analytics or accounts of its own. It also says optional widgets contact external services for data such as weather, quotas and GitHub, and the agent checks GitHub for updates. So "no cloud required" is accurate, but the setup is not fully offline.

Our take​

An old Android phone can make a convincing desk monitor and macro pad with no extra hardware cost. The best fit is a phone on Android 6 or later, running current Windows 10/11 x64, used mainly for live stats and shortcuts. The project is young: the version history shows rapid releases over a few weeks. Expect fast fixes, and also expect some churn.

MakeUseOf's Android Auto comparison and its claim that monitoring is the best use case are the outlet's own experience. The project's documentation doesn't corroborate them, so treat them as opinion. If you try it, start with Wi-Fi pairing and one System page. Then add shortcuts once you're comfortable with the unsigned-agent trade-off.


Correction (November 20, 2026): An earlier version of this article said the Android 5.0 and 6.0 support arrived in version 0.9.20, dated November 18, 2026. It arrived in version 0.9.19, dated November 17, 2026.

 

References

  1. Your old Android phone can become a PC control panel MakeUseOf 2026-11-20T11:27:12+00:00
  2. GitHub - ersinkoc/phonebox: Turn an old Android phone into a customizable desk panel and touch control deck for Windows, Linux and macOS. 124 widgets and 30 templates for system stats, AI coding, media and automation, in 13 languages. USB or paired Wi-Fi. No cloud required. · GitHub github.com
  3. CHANGELOG.md github.com