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
Start by identifying which link is failing: the Android app on the phone, the Wi‑Fi path to PhoneBot’s onboard computer, the onboard computer’s connection to the robot, or a feature such as ARCore SLAM. The PhoneBot paper confirms the first two parts of that chain, but it does not publish a complete reset or support procedure. The checks below therefore separate documented facts from a careful diagnostic method inferred from the platform’s architecture.
Do not assume that any old Android handset, Bluetooth pairing method, router band, permission toggle, or app version is officially supported. Capture the exact symptom and device details before changing anything, then use the project’s current documentation or maintainer channels for settings the paper does not specify.
How PhoneBot’s connection is organized
PhoneBot is an open humanoid-robot platform that reuses an Android smartphone for sensing and computing. In the design described by Ruochen Hou, Quanyou Wang, Daniel Koh and Dennis W. Hong, the phone runs the PhoneBot application, exchanges high-level commands and telemetry with a small onboard computer over Wi‑Fi, and the onboard computer communicates with the robot’s actuators. The authors describe the current application this way: “The current PhoneBot application is an Android app that uses these built-in devices directly.” Read the PhoneBot preprint.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →That arrangement creates several different failure points. A phone can be running the app correctly while the wireless path is unavailable. The app can discover the robot while a control process on the onboard computer is stopped. Basic control can work while a feature that depends on a particular phone service fails. Treating every symptom as “the old phone is incompatible” sends troubleshooting in the wrong direction.
#1 Best Overall
- 【Strong Adsorption】The inspiration of the silicone phone suction case comes from the adhesive force of the octopus. Each suction cup phone mount is 3.15 inches long and 2.17 inches wide, with 24 independent suction cups providing a stronger and more stable suction force, so you don't have to worry about your phone falling during use.
- 【Back of Phone Suction Grip】Remove the adhesive film on the phone suction cup and stick it on the phone case. You can then fix the phone on any smooth surface, which is very convenient. (The phone suction cup cannot be removed and reused after being attached to the phone case. It is recommended to attach it to a regular phone case, not a valuable one.)
- 【Widely Used】Our non-slip silicone phone sticky grip mount attaches to almost any flat phone case and make it compatible with common mobile phones such as iPhone and Android.You can shoot, watch videos or video calls in the kitchen, gym, dance studio, bathroom and other places.
- 【Capture the Wonderful Picture】Whether you are a TikTok creator or just like to share videos and photos, this phone suction cup can help you hands-free capture wonderful videos and photos for sharing with friends.
- 【Note】You can fix the phone suction cup on a smooth surface such as a mirror or glass. If necessary, wipe the suction cup with a damp cloth to obtain stronger suction. Before releasing your hand, make sure the phone is firmly fixed. (Not applicable to rough walls, wooden surfaces, and other uneven surfaces)
The preprint presents PhoneBot as a compact, open platform for education, research and rapid prototyping. Its reported design has 13 actuators and an approximate hardware cost of $400 excluding the smartphone; those figures describe the robot build, not a support requirement or a price for a replacement phone.
First, define what “won’t connect” means
Write down the first observable failure instead of using a general description. The symptom usually identifies which layer deserves the next check.
| Observed symptom | Most useful first question | What it does and does not prove |
|---|---|---|
| The PhoneBot app opens but never shows the robot | Is the phone communicating over the documented Wi‑Fi path with the onboard computer? | It points to discovery or network communication, but does not prove that the phone model is unsupported. |
| The app shows a robot, but commands produce no movement | Is the onboard computer running the control software and communicating with the actuators? | The phone-to-computer link may be working; the fault can be downstream. |
| Connection appears briefly, then drops | Does the failure coincide with loss of Wi‑Fi, an app error, a computer restart or a power problem? | An intermittent link needs timing and error details, not an immediate handset replacement. |
| Walking or another core function works, but mapping fails | Is the failing function ARCore SLAM or another feature-specific dependency? | A feature exception does not mean that the entire PhoneBot application is incompatible. |
| The app will not install or will not launch | What Android version, app build and installation error are shown? | The published paper does not state a minimum Android version or required app version. |
Use the narrowest description you can: “app opens, no robot appears,” “robot appears, command times out,” or “control works, SLAM fails.” That wording is far more useful to a project maintainer than “my old phone cannot connect.”
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 reinstallCrashes, 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 minuteCollect a diagnostic record before changing settings
Make a short record while the failure is reproducible. The paper does not prescribe a support form, but these details let someone distinguish an application problem from a network or robot-side problem.
- Phone manufacturer and exact model name, including the regional variant if shown in Android settings.
- Android version and security-update level.
- PhoneBot app version or build identifier, if the app displays one.
- Whether the app installs, launches, discovers the robot, connects, and accepts a command.
- The exact error text, including capitalization, and a screenshot if the project permits screenshots.
- Whether the failure affects every function or only a feature such as mapping.
- What the robot and onboard computer do at the same moment: power state, restart, visible status and whether other control paths respond.
- Date, location or region when a service-dependent feature is involved.
Do not paraphrase an error that can be copied verbatim. Also note whether the same symptom occurs after closing and reopening the app, but avoid repeatedly resetting equipment before you have recorded the original state.
Step-by-step troubleshooting
1. Confirm that the handset is the right type of device
The documented PhoneBot application is Android-based. Confirm that the handset is an Android phone and that the project’s application is installed from the project’s current distribution channel. If the app is absent, cannot be installed, or closes immediately, record the Android and app versions rather than assuming that a generic Android update will solve it.
Rank #2
- SUPERIOR COMFORT — Unlike traditional circular ear buds, the design of EarPods is defined by the geometry of the ear. Which makes them more comfortable for more people than any other ear bud–style headphones.
- HIGH-QUALITY AUDIO — The speakers inside EarPods have been engineered to maximize sound output and minimize sound loss, which means you get high-quality audio.
- BUILT-IN REMOTE — EarPods with USB-C plug also include a built-in remote that lets you adjust the volume, control the playback of music and video, and answer or end calls with a pinch of the cord.
- COMPATIBILITY — Works with all devices that have a USB-C port.
- INTEGRATED MICROPHONE — A built-in microphone precisely captures your voice while you’re on the phone, taking a FaceTime call, or summoning Siri — so you’re always heard loud and clear.
Open the app with the robot in its normal powered state and observe the first screen that fails. A launch failure is different from a discovery failure. If the app opens and can display local sensor information, that shows only that the application is running; it does not establish that the wireless link or robot-side software is available.
The authors say the app uses the phone’s built-in devices directly. That makes the exact handset and its available services relevant to some features, but the paper does not publish a universal minimum specification, Android-version floor or permission checklist. Do not present an unverified permission change as an official PhoneBot fix.
2. Check the documented Wi‑Fi path without inventing a network recipe
PhoneBot’s phone-to-robot exchange is documented as Wi‑Fi communication with the onboard computer. Verify that the phone’s Wi‑Fi is enabled, that the onboard computer is powered, and that the network arrangement being used matches the project’s current setup instructions. The paper does not state whether a particular installation must use the same home network, a direct access point, a specific frequency band, a fixed address, or a particular discovery protocol.
Because those details are unresolved, do not label a router-band change, Bluetooth pairing, firewall rule or factory reset as a PhoneBot requirement unless a current project manual explicitly does so. You can make a controlled observation: note the network name or connection state shown on the phone, note whether the onboard computer reports a network connection, and record the result when the app is opened. Keep the observation separate from an assumption about how the project must be configured.
If you manage the network yourself, avoid changing several variables at once. A simultaneous router change, app reinstall and phone reset destroys the information needed to identify the original fault. Change only a setting that the project documentation names, then record the result and any new error text.
Recommended Free Tools
3. Separate phone-to-computer communication from robot control
If the app displays the robot but a command does nothing, the phone may already be communicating successfully. The next diagnostic boundary is the onboard computer’s control software and its connection to the actuators. Check the computer’s power and status indicators and use only the project’s documented logs or status commands. The available PhoneBot paper does not publish a universal command sequence, log location or recovery reset.
Rank #3
- Secure Hold: Our PopSockets adhesive phone grip gives your cell phone a secure, comfortable hold in hand to help prevent drops while texting, taking photos, or scrolling on the go. Designed to stick firmly to most phone cases and devices.
- Hands-Free Made Easy: Easily turn your PopSocket into a phone stand to prop up your phone anywhere, perfect for watching videos, video calls, or following recipes. A must-have phone holder that keeps your device secure and ready for anything.
- Compatibility: Works with all phones, tablets, and Kindles. Sticks best to smooth, hard plastic cases and may not adhere to silicone or textured cases. Easily swap your PopTop to change up your style.
- Black PopSockets: Simple, refined, and endlessly versatile. A timeless essential for any phone.
- Travel Must-Have for People On the Go: A must-have travel accessory for flights, flying, airports, air travel, airplanes, planes, international trips, cruises, and long travel days. Key gadget for your airport haul, travel accessories and must-haves.
Look for a consistent pattern:
- If every command is ignored and the onboard computer shows no active control process, the fault is likely on the robot side of the link.
- If some commands work and others fail, capture the command names and timing; that pattern is more informative than testing a different phone immediately.
- If the robot restarts when a command is sent, investigate power or actuator faults rather than treating the symptom as Wi‑Fi incompatibility.
These are diagnostic interpretations of the documented architecture, not results of a published PhoneBot support test. Confirm the appropriate recovery action with the project maintainers.
4. Treat feature failures separately from basic connection failures
A working connection does not guarantee that every sensing or perception feature works on every handset. In the four-phone evaluation, the authors reported that all tested phones handled core application functions. They also reported a specific exception: ARCore SLAM did not work on the Honor 9 in the United States because Google services were unavailable on that Huawei device.
If walking, standing or another core function works but mapping fails, record the feature name and region before replacing the phone. The Honor 9 result is device- and region-specific; it is not evidence that all Honor phones, all Huawei phones or all PhoneBot functions fail. Conversely, it does not establish that installing an unrelated service or changing a permission will restore SLAM.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Ask the maintainer whether the requested feature has a documented platform dependency. Keep “the app cannot connect” and “one feature cannot initialize” as separate tickets or messages so that a feature limitation is not mistaken for a network outage.
5. Try a demonstrated handset only as a controlled comparison
A second phone can help isolate a handset-specific issue, but it is not a guaranteed cure. Use one model at a time, keep the robot and network arrangement unchanged, and record whether the symptom changes. Do not infer that a newer or more expensive phone is automatically supported.
6. Stop and escalate when the missing detail is not documented
The preprint does not specify the minimum Android version, required app version, exact router configuration, common error messages, permission sequence or reset/re-pair procedure. When your symptom depends on one of those details, stop guessing. Check the project’s current documentation and contact its maintainers with the diagnostic record. Include the exact model, Android version, app version, symptom stage, error text and what the onboard computer was doing.
Rank #4
- [360 ° Flexible Rotation Design] Comes with a rotatable lanyard ring that supports 360 ° free rotation, effectively solving the problem of twisted and tangled lanyards
- [Wide compatibility] The ultra-thin 0.02-inch design does not block the charging port at all, and both wired and wireless charging can be used directly without removing the pad. Compatible with most smartphones such as iPhone, compatible with various wristbands, lanyards, crossbody straps, and keychains
- [Durable and Portable Material] Premium rust-resistant stainless steel material with good flexibility, which not only avoids scratching the phone case, but also has excellent anti rust and anti fading performance
- [Multi scenario Practical] Paired with a lanyard or wristband, hands-free use can be achieved. The phone is within reach and not easily dropped, ideal for daily commuting and outdoor activities. Suitable for full coverage phone cases, does not support half coverage phone cases
- [Quality Service] If you find any damage or other issues with the product upon receipt, please contact us immediately. We will handle it quickly
Which old Android phones have actually been tested?
The published compatibility evidence is a four-phone evaluation, not a complete support list. The authors reported core application use on these models:
| Phone named in the evaluation | What the report establishes | Important qualification |
|---|---|---|
| Honor 9 | Core application functions were handled in the evaluation. | ARCore SLAM was unavailable in the United States because Google services were unavailable on that Huawei device. |
| Moto G 2025 | Core application functions were handled in the evaluation. | A test result, not a universal compatibility guarantee. |
| Samsung Galaxy A16 5G | Core application functions were handled in the evaluation. | A test result, not a universal compatibility guarantee. |
| Moto G 2024 | Core application functions were handled in the evaluation. | A test result, not a universal compatibility guarantee. |
The source names four devices and does not establish support for all older Android phones. It also does not provide a complete matrix of Android versions, regional variants, app builds or individual sensors. A handset not listed above is neither confirmed incompatible nor confirmed compatible.
If you are comparing a replacement, the useful questions are whether it is Android, whether the current PhoneBot app can run on it, whether the specific feature needs Google services or ARCore, and whether the project has documented that model. A model appearing in the table is evidence that it was tested, not a promise that a handset purchased today will behave identically.
A practical decision tree
- Can the app install and open? If no, record the installation or launch error, Android version and app version. Seek project guidance because the paper gives no minimum-version rule.
- Does the app show the robot? If no, verify the phone’s Wi‑Fi state and the onboard computer’s power and network state, then consult the project’s documented network arrangement. Do not assume a particular band or discovery method.
- Does a visible robot accept a command? If no, inspect the onboard computer and control process using documented project diagnostics. The fault may be after the phone link.
- Do core functions work while one feature fails? Identify the feature. For ARCore SLAM, check whether the handset and region have the services that feature requires; the Honor 9 result is a documented example of a regional/device-specific limitation.
- Does a controlled comparison with another documented test phone change the result? If yes, send both device records to the maintainers. If no, focus on the robot-side or network-side evidence rather than buying another phone.
Common assumptions that can waste time
“Any old Android phone should work.”
There is no evidence for that broad claim. Four models were evaluated, and the sample does not establish a universal minimum or maximum age.
“A Bluetooth pairing reset will fix it.”
The documented architecture describes Wi‑Fi exchange between the phone and onboard computer. It does not publish Bluetooth pairing as the required connection method, so do not substitute generic Bluetooth advice for project instructions.
“Changing the router to 5 GHz is the official fix.”
No required Wi‑Fi frequency is stated in the preprint. Treat any band recommendation as unverified until current PhoneBot documentation confirms it for your build.
Best Value
- 【PKYAA Double Sided Silicone Suction Phone Case Mount】PKYAA With Double Sided 40 Strong and Reliable individual suction cups, PKYAA provides a thicken and upgraded universal silicon suction mount for your phone.
- 【Friendly to Content Creators】If you are a content creator or an online influencer, you can create videos anywhere with this suction mount completely hands free with this silicone cell phone mount for cases.
- 【HANDS-FREE & Adhere to Mirrors】This Double Sided silicone suction phone case mount allows you to stick your phone to the mirror easily. No longer holding your phone in one hand to watch video tutorials while making up.
- 【Strong Grip on the Smooth Surface】You can easily hang your phone anywhere with a smooth surface. All you do is you clean off your phone and smooth surface. It is STURDY and it not only sticks to mirrors, it also sticks to windows, it sticks to refrigerators, tiles and other clean, flat surfaces.
- 【Press Down Firmly Every 30 Minutes】Use your palm or fingers to press the phone down firmly and check it's secure before letting go. Apply even pressure for a few seconds to allow the suction cup to adhere properly. To maintain the grip and prevent accidental falls, it's a good practice to periodically reapply pressure to the suction cup.
“The phone is broken because the robot does not move.”
A command can reach the app and still fail in the onboard computer, control software, power system or actuators. Check which stage responds before blaming the handset.
“An ARCore failure means PhoneBot cannot connect.”
Feature initialization and basic communication are different tests. The reported Honor 9 exception concerns ARCore SLAM in the United States, not every PhoneBot function.
What to send when asking for PhoneBot help
Make the maintainer’s first reply actionable by sending one compact report:
Phone model and regional variant: [model] Android version: [version] PhoneBot app version: [version or not shown] Robot/onboard computer state: [powered, status observed] Failure stage: [launch, discovery, connection, command, or feature] Exact error text: [copy verbatim] Reproduction steps: [short sequence] Result with any documented comparison phone: [result or not tested]Replace each field with your actual value; the bracketed text is a template, not a PhoneBot command. Attach logs or screenshots only as permitted by the project. Mention the country or region when a Google-service or ARCore behavior is involved.
When replacing the phone is reasonable
Consider another handset only after you have established that the app can run, the Wi‑Fi path is configured according to current project instructions, and the failure follows the phone rather than the robot. A replacement is more defensible when the project confirms that your requested feature depends on a service unavailable on the old device, or when maintainers identify your model or Android build as unsupported.
Do not buy a phone solely because it is newer, because it appears on an unrelated compatibility list, or because a robot-side command failed. The four tested models provide comparison examples, not a guarantee for every production batch, regional variant or future app release. Ask the project for current compatibility guidance before spending money.
What the published evidence does—and does not—establish
The technical source is a preprint posted on 6 October 2026, not a consumer support manual. It establishes the Android application, Wi‑Fi exchange with the onboard computer and the four-phone evaluation. It does not establish a universal phone specification, a complete setup sequence or a standard recovery procedure. A contemporaneous report also notes that current movement control was trained for flat terrain, that the robot has no arms, and that speech recognition and language processing rely on an external laptop; those are project capabilities and limitations, not demonstrated causes of a phone connection failure. See the 8 October 2026 report.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsUse the architecture to isolate the failing layer, preserve exact evidence, and defer undocumented settings to the project’s current instructions. That approach avoids turning a small compatibility sample or a feature-specific exception into a false promise about every old Android phone.
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.
