Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
No—not every old smartphone is supported. PhoneBot is an open humanoid-robot platform that uses a mounted smartphone for sensing, computing and control. The published application test covered four Android phones, including a used 2017 Honor 9 and three inexpensive prepaid models. All four completed the paper’s main sensing, motor-communication, locomotion-inference, vision and interaction tests, but that small sample is not a universal compatibility guarantee. One feature, ARCore-based SLAM, was unavailable on the Honor 9 in the U.S. test context because Google services were unavailable on that Huawei device.
Use the tested phones as evidence that some older and low-cost Android hardware can work, not as a promise that your handset will. Check the current PhoneBot instructions and Android app requirements, then test every feature you intend to use before committing to a phone or a complete robot build.
What PhoneBot is and what the smartphone does
This article concerns PhoneBot, the low-cost humanoid robot platform, rather than an unrelated refurbished-phone retailer with a similar name. The paper by Ruochen Hou, Quanyou Wang, Daniel Koh and Dennis W. Hong describes it as “a low-cost, open-source humanoid robot platform that repurposes commodity smartphones as its primary sensing and computing unit.”
The phone is mounted on the robot’s torso and performs several jobs that would otherwise require dedicated electronics:
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
- Body motion sensing: the app reads the phone’s inertial measurement unit (IMU).
- Vision: the camera runs on-device detection and pose-estimation functions.
- Robot intelligence: a TensorFlow Lite locomotion policy runs on the phone’s processor. The paper says the tested application stack was CPU-bound, so it did not provide a GPU comparison.
- User interface: the phone is the operator-facing interface for interaction and control.
- Wireless control: joint targets, motor telemetry and gamepad inputs travel over Wi‑Fi between the phone and a small onboard computer. That computer forwards commands to the actuators.
The phone is therefore a real-time robot component, not merely a display or remote control. A handset can open the app yet still fail a particular function because of missing sensors, unsupported platform services, inadequate processing performance or network problems.
Which phones have actually been tested?
The published test covered four Android handsets. The authors report that each completed IMU sensing, UDP motor communication, locomotion-policy inference, on-device vision and human–robot interaction.
| Phone | Evidence reported in the paper | Important qualification |
|---|---|---|
| Honor 9 (used, 2017) | Completed the reported IMU, UDP, policy-inference, vision and interaction functions. | ARCore SLAM was unavailable in the U.S. test context because Google services were unavailable on this Huawei device. |
| Motorola moto g 2025 | Completed the reported application functions. | Successful testing is an example of compatibility, not a published minimum specification. |
| Samsung Galaxy A16 5G | Completed the reported application functions. | Successful testing is an example of compatibility, not a guarantee for every regional variant or future software release. |
| Motorola moto g 2024 | Completed the reported application functions. | Successful testing is an example of compatibility, not a published minimum specification. |
This is the strongest available compatibility evidence: one older 2017 handset and three low-cost Android phones ran the demonstrated stack. It does not establish that all Android phones work, that every regional model behaves identically, or that an old phone supports every optional capability.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why the evidence does not support “any old smartphone”
No universal Android version, processor, graphics, memory or storage minimum is stated in the published material. Because no threshold is documented, it would be misleading to turn the four successful examples into a specification such as “any phone newer than year X” or “at least Y GB of RAM.” Phone age alone is not a compatibility test.
Several independent conditions must line up:
- The handset must be able to install and run the current Android PhoneBot application.
- Its operating-system release and app-store or package-installation path must remain supported by the current project.
- It needs a working IMU, camera and Wi‑Fi radio for the functions that use them.
- The processor must sustain the app’s on-device policy inference and vision workload. The paper measured CPU use and characterized the stack as CPU-bound; it did not publish a pass/fail CPU score.
- Platform services required by a particular feature must be present. ARCore SLAM is the clearest example.
- The phone and robot computer must be able to exchange UDP traffic on the same usable Wi‑Fi network.
A handset can satisfy the first five conditions and still fail motor control because of network isolation, firewall rules or an incompatible robot-side configuration. Conversely, it can pass sensing and control while lacking a mapping feature. Compatibility is therefore feature-specific.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
What happened with ARCore SLAM?
ARCore-based simultaneous localization and mapping (SLAM) was the documented exception in the phone tests. The used Honor 9 ran the other reported functions, but ARCore SLAM was unavailable in the U.S. context described by the authors because Google services were unavailable on that Huawei device.
That result illustrates two points that are easy to miss:
- Running the app is not the same as supporting every feature. Core IMU, communication, policy and vision functions can work while a service-dependent mapping mode does not.
- Availability can depend on region and services, not only hardware. A model’s camera and processor may be adequate, yet the required Google service framework or certification may be absent.
Do not infer that an older phone supports ARCore SLAM simply because it completed the other PhoneBot tests. If mapping is important, verify ARCore and the required Google services on the exact handset and regional software configuration you plan to use.
How to check your own phone before building around it
The project materials available for this topic do not provide a complete, universal setup procedure or a minimum Android specification. The following is a practical compatibility check, not a claim that it reproduces an official installation guide. Use the project’s current instructions for exact app packages, robot firmware and network settings.
1. Identify the exact handset and software
Record the model number, Android release, regional variant and security or vendor software status. “Galaxy A16 5G,” for example, can refer to different regional configurations. Avoid evaluating a phone from a family name alone. Confirm that the current PhoneBot app is distributed for your Android release and that the device can install its required dependencies.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
2. Check the required sensors and radios
Verify that the phone exposes an accelerometer and gyroscope through Android, that the camera opens normally, and that Wi‑Fi can connect reliably to the network used by the robot. A damaged camera, disabled sensor, unstable Wi‑Fi radio or aggressive battery-management mode can break a function even when the model is nominally suitable.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
3. Confirm platform services for optional features
If you need ARCore SLAM, check ARCore availability and the required Google services on that exact device and in your region. Treat service availability as a separate gate from general app installation. The Honor 9 result shows why this check cannot be skipped.
4. Install the current app and exercise sensing first
With the phone off the moving robot, launch the app and confirm that live IMU readings change when you tilt the handset and that camera preview or on-device detection operates. This isolates sensor and permission problems before motors are energized.
5. Validate Wi‑Fi and UDP communication safely
Connect the phone and the robot’s onboard computer to the intended Wi‑Fi network. Follow the project’s documented addressing, port and safety settings, then confirm that motor telemetry arrives and that a test command is acknowledged. Do not enable unattended motion until you have a physical emergency stop and a clear way to remove power.
6. Run locomotion inference under realistic load
Measure whether the app maintains responsive inference while sensing and communication are active. Because the reported stack was CPU-bound, watch for sustained high CPU use, rising temperature, dropped frames or delayed commands. A phone that works briefly on a bench may become unreliable after it heats up.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
7. Test each intended feature separately
Make a pass/fail list for IMU sensing, motor communication, locomotion policy, vision, interaction and—if needed—ARCore SLAM. Record the Android version, app version, network and feature result. This prevents a broad statement such as “the phone works” from hiding a failure in the one capability you actually need.
How the tested phones compare with an untested handset
There is no published supported-device catalogue or benchmark table. The useful comparison is therefore between documented examples and the checks you must perform on your own phone.
| Compatibility axis | What the paper establishes | What you must verify |
|---|---|---|
| Operating system | The tested devices were Android phones. | Whether the current app supports your Android release and exact model variant. |
| Processing | All four completed locomotion-policy inference and vision; the stack was described as CPU-bound. | Sustained responsiveness and thermal behavior on your handset. No published CPU or RAM threshold exists. |
| Camera and IMU | All four completed the reported sensing and vision functions. | That Android exposes working sensors and camera permissions on your device. |
| Wi‑Fi and UDP | The tested application exchanged commands and telemetry wirelessly. | That your network permits the required phone-to-robot traffic without client isolation or blocking. |
| ARCore SLAM | Unavailable on the tested Honor 9 in the stated U.S. context. | ARCore support and Google services on the exact model, software build and region. |
| iPhone or iOS | Not established by the published tests. | Do not assume iOS support unless current PhoneBot documentation explicitly lists it. |
What an old phone can realistically do
A 2017-class Android handset
The Honor 9 is important because it demonstrates that a used 2017 phone can run the paper’s core PhoneBot workload. It is evidence against the idea that a brand-new flagship is automatically required. It is not evidence that every 2017 phone will work, nor that the Honor 9’s regional software supports ARCore SLAM.
A low-cost prepaid phone
The moto g 2025, Galaxy A16 5G and moto g 2024 show that inexpensive current-market Android hardware can complete the tested stack. Their inclusion is useful for builders seeking a low-cost donor phone, but the result applies to the tested models and configurations. It does not certify every prepaid handset, carrier variant or later revision.
A very old or unsupported phone
Phones that cannot install the current app, lack a usable camera or IMU, lose security updates, or cannot maintain Wi‑Fi should be treated as unsuitable even if they are physically mountable. The available evidence does not define an age cutoff, so a model-by-model test is safer than a year-based rule.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Does PhoneBot support iPhones?
The published tests and architecture description identify an Android application and list four Android test phones. They do not establish iPhone or iOS support. Do not buy an iPhone for PhoneBot on the assumption that an equivalent camera or processor will be enough; the app, sensor APIs, on-device model runtime and robot-network implementation would all need an explicitly supported iOS path.
Phone-side and robot-side requirements are different
Phone compatibility is only one part of a working build. The described platform has 13 actuators or joints, with DYNAMIXEL XL430-W250-T actuators specified in the paper. The phone sends targets over Wi‑Fi to a small onboard computer, which handles the hardware-facing command path. A compatible phone cannot compensate for incorrect actuator wiring, missing robot firmware, unsafe power, an unconfigured onboard computer or a network that blocks control traffic.
Keep these layers separate when diagnosing a failure:
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Phone layer: Android app, permissions, sensors, camera, processor and thermal behavior.
- Network layer: Wi‑Fi association, IP addressing, UDP reachability and latency.
- Robot-computer layer: receiving commands, forwarding them and returning telemetry.
- Actuator layer: powered and correctly configured joints responding to safe targets.
Troubleshooting by symptom
The app will not install or start
- Recheck the exact Android release and model variant against the current project instructions.
- Confirm that required permissions are granted for motion sensors, camera and network access.
- Remove aggressive battery restrictions for the app during testing.
- If the project distributes a package outside the standard app store, use only the project’s current, trusted instructions and verify the package identity.
IMU values are missing or unstable
- Test the accelerometer and gyroscope with another trusted sensor utility.
- Check whether the handset has a vendor setting that disables motion sensors.
- Mount the phone rigidly and align it as required by the robot’s calibration instructions.
Vision works but mapping does not
Check ARCore and Google-service availability separately. The Honor 9 example shows that ordinary camera vision can work when ARCore SLAM is unavailable.
Commands or telemetry do not arrive
- Place the phone and robot computer on the same Wi‑Fi network.
- Disable guest-network or client-isolation features that prevent device-to-device traffic.
- Recheck the project’s documented IP address and UDP port settings.
- Test with motors disabled so a network retry cannot create unexpected movement.
The robot becomes sluggish after several minutes
Monitor CPU load and temperature. The paper characterizes the stack as CPU-bound, so sustained inference can expose thermal throttling or background-process contention. Close unnecessary apps, keep the camera and phone vents unobstructed, and retest before changing hardware.
Before you buy or reuse a phone
- Confirm that it is an Android device supported by the current PhoneBot app.
- Check the exact model and regional software, not just the product family.
- Verify camera, IMU and Wi‑Fi operation.
- Check ARCore and Google services if SLAM is required.
- Run the app’s sensing, communication, inference and vision functions before mounting the phone permanently.
- Test the complete workload long enough to expose heat-related slowdowns.
- Keep a fallback phone or a way to restore the previous known-good configuration.
- Follow the current project documentation for robot firmware, network ports, actuator setup and safety procedures.
The four published Android examples make an older or inexpensive phone a plausible PhoneBot component, but they do not turn “old smartphone” into a compatibility category. The reliable answer for any specific handset is a feature-by-feature check on that exact device, software build and network.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
