iTechGuides 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
You cannot turn a phone into a walking robot by installing an app alone. In the current PhoneBot research platform, an Android smartphone becomes the robot’s camera, inertial sensor, wireless interface and high-level computing unit when it is mounted on a purpose-built 13-actuator humanoid body. A separate onboard computer still handles actuator communications, and the mechanical structure, power system and servos must be built around it.
What “turning an old smartphone into a PhoneBot” actually means
PhoneBot is the name of a humanoid research platform presented by Ruochen Hou, Quanyou Wang, Daniel Koh and Dennis W. Hong in an arXiv preprint submitted on October 6, 2026. The project’s central idea is to reuse a commodity Android phone’s existing camera, inertial measurement unit (IMU), wireless networking and processor instead of designing those systems from scratch.
The phone is therefore one subsystem in a distributed robot. It does not contain the motors, motor power electronics, structural frame or actuator bus. A successful build combines the handset with a compact bipedal body, 13 actuated joints, a small onboard computer and a battery. The paper describes the platform as open-source, but that label should not be confused with a finished retail kit or a beginner-tested assembly package.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What the phone contributes
- The rear camera supplies visual input for perception tasks.
- The built-in IMU supplies motion and orientation measurements.
- Wi-Fi provides the communication link to the robot’s onboard computer.
- An Android application runs perception and locomotion-policy inference on the phone’s CPU or GPU.
- The phone can act as the user-facing interaction and telepresence interface.
What the phone does not replace
- A 13-joint mechanical body and its structural parts.
- Thirteen servo actuators and the wiring or bus hardware needed to control them.
- A small computer that receives commands and forwards them to the actuator network.
- A battery, power distribution and safe voltage regulation.
- A secure torso mount that keeps the handset’s camera and sensors usable while the robot moves.
The PhoneBot control chain
The documented architecture is easiest to understand as a command path:
#1 Best Overall
- This kit gives kids a simple, fun, and customizable introduction to robotics that lets them build eight motorized machines.
- Using the app interface, you can program the robots you build to behave based on the feedback coming from the ultrasound sensor.
- A full-color, 64-page step-by-step illustrated manual helps kids assemble all of the models and teaches them about robotics in the real world.
- The ultrasonic sensor works on the same principle as Sonar.
- Requires a tablet or smartphone running iOS or Android (not included).
- Phone sensors: The torso-mounted Android handset captures camera frames and IMU data.
- Android application: The app performs perception and runs a TensorFlow Lite actor for the locomotion policy on the phone CPU or GPU.
- Wireless command: The app sends joint-position targets over Wi-Fi using UDP.
- Onboard computer: A separate small computer receives those targets and handles actuator communication and command execution.
- Actuator bus: The computer sends the joint targets to the servos.
- Humanoid body: The 13 joints move the legs and rotate the torso, producing the requested posture or gait.
This split has practical consequences. A phone with a good camera but weak graphics performance may not deliver the intended inference rate. Conversely, a powerful phone cannot compensate for incorrect joint wiring, an unsuitable power supply or an unstable wireless link. Mechanical, electrical, networking and software setup all have to work together.
How the 13-joint humanoid is arranged
PhoneBot’s lower body has six actuated joints in each leg plus one torso-yaw joint. Each leg is described as having:
- Hip yaw
- Hip roll
- Hip pitch
- Knee pitch
- Ankle pitch
- Ankle roll
The extra actuator turns the torso. The paper reports an assembled height of 483 mm and dimensions of 483 × 183 × 125 mm, with a total mass of 1.8 kg including the phone, actuators, structure, electronics and battery. Those figures belong to the paper’s described assembly; they are not a promise that a home-built version will have identical dimensions or weight.
Free tools Windows power users keep installed
One-click scans. No signup required.
What kind of old phone can you use?
The paper says the integrated platform was validated with four old or low-cost smartphones. It does not establish a universal compatibility list, a minimum Android release, a supported chipset range or compatibility with every handset sold as “old.” The current design is explicitly described around an Android application, so do not assume that an iPhone can run the same software.
Check these capabilities before designing around a handset
- Android app access: Confirm that the project’s current application can be installed on the exact phone and Android version you plan to use.
- Camera access: The app must be able to obtain the camera stream in the intended orientation and lighting conditions.
- IMU access: The handset needs working motion sensors; a phone with a damaged or unavailable accelerometer or gyroscope is unsuitable.
- Wireless networking: The phone must maintain a reliable Wi-Fi connection to the onboard computer.
- Compute headroom: The processor or GPU must run the app’s TensorFlow Lite inference workload without excessive throttling.
- Battery and physical condition: A swollen, overheating or rapidly discharging battery should not be enclosed in a moving robot.
- Camera clearance: The mounting design must leave the camera unobstructed and hold the phone firmly during walking.
These are functional requirements implied by the published architecture, not a guaranteed model list. Check the project’s live software and design documentation before purchasing actuators or fabricating a mount. The available project-site material identified with the paper shows a project title and a joint-configuration image caption; it does not, by itself, establish a complete beginner-ready bill of materials.
Rank #2
- BUILD, CODE & DRIVE YOUR OWN ROBOT CAR: Turn coding, electronics and engineering into a working programmable robot car you can assemble, program and drive; ideal for weekend family projects, STEM classrooms, coding clubs, robotics lessons and maker challenges
- EXPLORE FPV, LINE TRACKING & OBSTACLE AVOIDANCE: Control the robot with the ELEGOO app or IR remote, view live FPV video through the onboard camera, follow black lines, avoid obstacles with the ultrasonic sensor and explore multiple interactive driving modes
- BEGINNER-FRIENDLY BUILD WITH GUIDED WIRING: Keyed XH2.54 connectors help reduce wiring mistakes, while the illustrated tutorial and example programs guide beginners step by step from chassis assembly and module connection to programming and the first successful run
- GO BEYOND ASSEMBLY WITH CREATIVE CODING: Program with Arduino IDE to explore movement, sensors and control logic, then modify example code to create custom routes, reactions and robotics experiments that develop coding, problem-solving and engineering skills
- COMPLETE RECHARGEABLE STEM ROBOTICS KIT: Includes an ELEGOO UNO R3 controller board, ESP32-WROVER-based camera and Wi-Fi module, line-tracking and ultrasonic sensors, motors, IR remote and a 2000 mAh rechargeable lithium-ion battery; recommended for ages 8+ with adult guidance for first-time builders
Parts you need to plan for
The paper identifies the key components, but it does not provide a current shopping cart with live stock, regional pricing or a guaranteed supplier for every supporting part. Separate exact-model requirements from fabrication and integration choices.
| Subsystem | Documented requirement | What you still need to verify |
|---|---|---|
| Actuators | 13 ROBOTIS DYNAMIXEL XL430-W250-T servos, one for each actuated joint | Current price, stock, connector and bus accessories, shipping region and whether alternatives are supported |
| Phone | Android smartphone providing camera, IMU, Wi-Fi and enough inference performance | Supported Android version, exact app compatibility, battery condition and mounting dimensions |
| Onboard computer | Small computer that receives Wi-Fi/UDP targets and communicates with the actuator bus | Exact model, operating image, interfaces, power budget and project software |
| Mechanical body | Humanoid structure with six actuators per leg and one torso-yaw actuator | Verified CAD/design files, print or fabrication materials, fasteners, tolerances and assembly sequence |
| Power system | Battery and electronics are included in the reported assembled mass | Battery chemistry, voltage, capacity, regulation, connectors, fusing and safe charging procedure |
| Phone mount | Torso mounting structure that exposes the camera and holds the handset during motion | Holder geometry, retention method, vibration control and access to the charging or power button |
The paper reports $23.90 per XL430-W250-T unit. That is the authors’ stated figure in the 2026 paper, not a current store quotation. Multiplying it by 13 gives a paper-reference actuator subtotal of $310.70, before shipping, taxes, cables, power hardware, structure, computer or phone. It should not be treated as the present cost of a complete robot.
A responsible build sequence
Because the current platform is a research build rather than a retail kit, treat the following as an integration workflow. Do not order all 13 servos until you have confirmed the project files, software and phone requirements that apply to your region and handset.
1. Confirm the current project materials
- Locate the authors’ current design files and Android application associated with the 2026 PhoneBot paper.
- Check whether the files include the body CAD, joint dimensions, wiring information, firmware, calibration procedure and software installation instructions.
- Record the supported Android versions, processor requirements and any required network settings.
- Confirm that the published design is still the revision you intend to build; a research repository can change after the paper’s submission date.
2. Test the candidate phone on a bench
- Install the documented app before modifying the phone or fabricating a mount.
- Verify camera and IMU access, Wi-Fi connectivity and stable operation while the phone is charging or running continuously.
- Observe heat and battery drain during the inference workload. A phone that becomes too hot or shuts down cannot be treated as a reliable robot controller.
- Disable notifications, automatic updates and screen-lock behavior that could interrupt a motion-control session, while retaining the ability to stop the robot quickly.
3. Acquire the actuator set and bus hardware
Plan around 13 XL430-W250-T actuators because that is the model named for all joints in the paper. Verify the required cables, connectors, power distribution and communication interface from the current design files. Do not substitute the parts list from another project called “phonebot”; its motors and control electronics belong to a different small wheeled robot.
4. Fabricate or obtain the body
Build the legs, torso and phone mount from the verified design revision. Check joint orientation and mechanical stops before installing electronics. The six joints in each leg are not interchangeable in software merely because they use the same servo model: their axes and zero positions differ.
Rank #3
- Hands-On STEM Robot Learning---This STEM robot kit combines coding, electronics, and robotics into a fun, hands-on learning experience. Powered by an ESP32 controller and guided by 16 story-based tutorials, this robotics kit for kids helps children ages 8–12 and 12–16 build real-world STEM skills. Ideal for robotics for kids, classroom teaching, or at-home learning.
- 3 Programming Languages for All Skill Levels---This coding robot kit supports Scratch, Arduino, and Python, making it suitable for beginners and advanced learners alike. Scratch block coding is perfect for younger kids and first-time coders, while Arduino and Python support deeper learning for teens and tech enthusiasts. A flexible programmable robot designed to grow with students.
- Mobile-Friendly Coding – Learn Anytime, Anywhere---Unlike many traditional robot kits, this robotics kit supports programming on computers, laptops, tablets, and mobile devices like smartphones and iPads. Kids can code directly on mobile devices, making it especially suitable for schools, training centers, and self-learning at home. A practical STEM kit for kids in modern learning environments.
- Build Your Own Robot – Beginner-Friendly DIY---This robot building kit includes HD videos and illustrated step-by-step instructions, allowing kids to assemble the robot independently or with parents. No soldering required. The building process strengthens hands-on skills, patience, and confidence—making it a strong choice among STEM toys for kids and engineering kits for kids. Tutorial path: ACEBOTT Official Website → Resources → WIKI & Assembly Video Note: Batteries not included.
- App & Remote Control for Interactive Learning---Control the robot using the smartphone App (iOS & Android) or the included IR remote. Kids can instantly see how their code affects movement and behavior, reinforcing core coding logic. This robot kit keeps learning engaging while remaining easy to use for beginners.
5. Install and label every actuator
- Assign each servo the ID expected by the control software.
- Label left and right sides and record the physical joint represented by every ID.
- Route cables so they cannot be pinched at the hip, knee or ankle.
- With power removed, move each joint through its safe mechanical range by hand and check for binding.
6. Add the onboard computer and power system
Mount the small computer securely and connect it to the actuator bus according to the project’s wiring instructions. Size the battery and regulators for simultaneous computer and servo loads; the paper’s 1.8 kg mass figure does not reveal the required voltage, current reserve or runtime. Add strain relief, an accessible power disconnect and protection against accidental short circuits.
7. Configure the network
- Connect the phone and onboard computer to the same Wi-Fi network or the project’s specified access point.
- Set the computer’s address and UDP port exactly as required by the app.
- Confirm that packets arrive before enabling torque.
- Keep the robot supported on a stand during initial communication tests so a bad command cannot make it fall.
8. Calibrate with the robot restrained
- Place the robot on a stable support with its feet clear of the floor.
- Apply the documented zero offsets and direction conventions.
- Command one joint at a time at low speed and verify that positive and negative targets produce the expected physical movement.
- Check that both legs mirror the intended left-right geometry and that the torso-yaw axis is correctly identified.
- Only after single-joint tests pass should you test a complete standing pose.
9. Test locomotion conservatively
Use a tether, support frame or another fall-mitigation method for the first walking trials. Keep people and fragile objects outside the robot’s fall zone. Start with low-amplitude commands and a clearly tested emergency stop. A phone application can issue high-level targets, but it cannot prevent injury or hardware damage if the mechanical calibration, power system or command limits are wrong.
Capabilities reported by the paper
The authors report walking and perception-driven demonstrations that include vision-based human following, conversational interaction, filming and mobile telepresence. These are claims about the platform’s reported validation, not independent testing of every build or every phone. They should be read as demonstrations of what the integrated research system can do when its hardware and software are configured as intended.
The phone’s placement is important to these functions. A torso-mounted camera gives the robot a forward-looking viewpoint, while the IMU contributes motion data during walking. Wi-Fi allows the phone to remain the high-level compute and interaction device while the onboard computer performs the lower-level actuator communication.
PhoneBot cost, size and evidence boundaries
| Figure | Meaning |
|---|---|
| 13 actuators | The number of powered joints in the described humanoid body. |
| $23.90 per actuator | The per-unit figure stated by the 2026 paper for the XL430-W250-T; it is not a live quotation. |
| $310.70 reference subtotal | 13 multiplied by the paper’s stated per-unit figure, excluding every other component and purchase cost. |
| 483 × 183 × 125 mm | Assembled dimensions reported in the paper. |
| 1.8 kg | Reported assembled mass including phone, servos, structure, electronics and battery. |
| Four phones | The abstract says validation used four old or low-cost smartphones; it does not define universal compatibility. |
No independent market-wide estimate for a complete PhoneBot build is established by the available sources. The final cost will depend on fabrication, electronics, battery, shipping, taxes and whether you already own a suitable phone.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Rank #4
- This kit gives kids a simple, fun, and customizable introduction to robotics.
- Build and program your own Robots using the kit’s 197 building pieces.
- Kids code the programs using an easy, visual programming app on a tablet or smartphone.
- 60-Page step-by-step illustrated manual helps kids assemble all of the models and teaches them about robotics.
- Requires a tablet or smartphone running iOS or Android (not included).
PhoneBot versus other projects called phone robots
Search results can combine several unrelated projects. The name alone is not enough to identify the hardware.
| Project | Robot form and phone role | Source-backed distinction |
|---|---|---|
| Current PhoneBot | Humanoid research platform; Android phone mounted on the torso for sensing, inference, wireless communication and interaction | 13 actuators, six joints per leg plus torso yaw, separate onboard computer and reported 1.8 kg assembled mass |
| OpenBot | Small electric vehicle using an Android phone as its robot brain | Documentation describes a build-your-own body, Arduino firmware, Android apps, a controller, programming resources and a body figure of about $50. That figure is specific to OpenBot and is not a PhoneBot price. |
| jgrizou/phonebot | Older small smartphone-controlled self-driving wheeled prototype | Its repository lists geared motors, a dual TB6612FNG motor driver, a LiPo charging/boost board, a 3.7 V 1 Ah battery and an Espruino MDBT42Q breakout, plus CAD models. Those parts are not the humanoid PhoneBot bill of materials. |
The meaningful comparison is not which name sounds more advanced. Wheeled platforms generally avoid bipedal balance and use a different actuator and control stack. PhoneBot is aimed at humanoid locomotion research, interaction and telepresence, so it demands more mechanical alignment, calibration and fall management. OpenBot and the older wheeled prototype should be selected only when a car-like mobile base matches the intended project.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common failure modes and fixes
The app installs but cannot control the body
Check that the phone and onboard computer are on the same network, the configured IP address and UDP port match, and the computer is actually forwarding commands to the actuator bus. Test packet reception before enabling servo torque.
The robot moves in the wrong direction
Recheck servo IDs, left-right assignment, joint-axis orientation and zero offsets. A correct model can still move incorrectly if one actuator is mounted with reversed geometry or assigned to the wrong joint in software.
The phone loses connection during walking
Reduce wireless obstacles, keep the access point within reliable range and prevent the phone from entering a power-saving state. Also investigate thermal throttling or battery protection shutdown; a network symptom can originate in the handset’s power or temperature limits.
Best Value
- Hands-On STEM Robot Learning. This STEM robot kit combines coding, electronics, and robotics into a fun hands-on learning experience. Powered by an Mirco:bitV2 controller and guided by 16 story-based tutorials, this robotics kit helps children ages 8–12 12-16 build real-world STEM skills while sparking creativity. A perfect introduction to robotics for kids ages 8–12 12-16, ideal for science fairs, classroom use, or at-home projects.(Note: AA Batteries not included）
- Build Your Own Robot – Parent-Child DIY Fun. This Makecode-compatible coding robot kit includes HD videos and illustrated step-by-step instructions, making it easy for kids and parents to assemble together. Great for family STEM bonding, the process boosts confidence and critical thinking skills. A wonderful option for building sets for boys and robot kits for kids age 8-12 12-16. Tutorial & code path: ACEBOTT Official Website → Resources → WIKI and Assembly Video.
- Expandable Robot Kit – Extension Port: (1)Sensors Extension: We can do more experiments through 3PIN port. (2)Building Block Extension: This microbit robot is compatible with LEGO building block, We can create various cases. It better improves their interest in programming, and making it one of the most engaging STEM toys for boys age 8-12 12-16.
- App & Remote control & Wireless controller. This programmable robot car supports infrared remote control and smartphone apps (compatible with iOS and Android systems), plus wireless controller operation, allowing you to control it with ease and flexibility both indoors and outdoors. Whether kids are coding or just playing, it enhances confidence and excitement while exploring technology—an excellent robotics kit for independent learning.
- Learn by Exploring: Rich Makecode graphical programming blocks allow micro:bit beginners to learn programming from the simplest to more complex.They can achieve distance tracking, obstacle avoidance, line following, Light Following, etc.
A leg binds or draws excessive current
Remove power, inspect cable routing and mechanical alignment, and move the joint through its range by hand. Do not compensate for a physical obstruction by increasing torque limits. Binding can damage a servo, overheat wiring or destabilize the robot.
The phone does not fit the mount
Do not force a different handset into a fixed holder. Confirm camera position, thickness, connector clearance and retention before revising the mount. The sources do not specify a universal holder dimension, so this is an integration choice that must follow the phone and verified CAD.
Who should build this platform?
PhoneBot is a good fit for a robotics student, researcher or experienced maker who wants to study low-cost humanoid control while reusing a phone’s sensors and compute. It is not the shortest route to a ready-to-use consumer robot. Expect to work with CAD or fabrication, servo-bus wiring, embedded computers, Android software, networking, calibration and safe testing.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Before buying the 13 actuators, confirm five things: the current design files, the Android app and its supported devices, the exact onboard computer and bus electronics, the power and battery specification, and a safe calibration procedure. If any of those remain unavailable, the sensible next step is to wait for verified project documentation rather than treating the paper’s component names as a complete shopping list.
The key statement from the authors
“This paper presents PhoneBot, a low-cost, open-source humanoid robot platform that repurposes commodity smartphones as its primary sensing and computing unit.”
This sentence comes from the abstract of the October 6, 2026 arXiv preprint by Ruochen Hou, Quanyou Wang, Daniel Koh and Dennis W. Hong. It accurately describes the project’s design goal; it does not claim that every old phone is compatible or that the platform is a finished retail product.
The Bottom Line
An old Android phone can become PhoneBot’s eyes, motion sensor, wireless link and high-level processor, but only as part of a complete 13-actuator humanoid system. Verify the current app, design files, electronics and power requirements before purchasing parts, and treat the paper’s actuator price and capability claims as dated, attributed research figures rather than a guaranteed complete-build specification.
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.
