New Products · Brief de sourcing

Humanoide PhoneBot da UCLA reutiliza celulares Android antigos como cérebro de robô de US$ 400

Pesquisadores da UCLA constroem um bípede open-source de 19 polegadas que usa um smartphone para computação e sensoriamento, trocando por aparelhos mais antigos para reduzir custos.

Publicado Atualizado 4 min de leitura ✓ Pronto para IA Compartilhar

TL;DR — três frases

  • UCLA researchers released an open-source PhoneBot humanoid that uses an Android smartphone as its compute and sensor stack. (S1)
  • The reported build is ~19 inches tall, weighs 4 lb, and costs about $400 excluding the phone, driven by 13 DYNAMIXEL XL430-W250-T servos. (S1)
  • Validation used four Android phones, including a 2017 Honor 9 and three $50-$80 budget handsets, all running a TensorFlow Lite control app. (S1)

Extraído de key_takeaways (campo real, máx. 3 entradas). Fato e análise são rotulados separadamente.

Humanoide PhoneBot da UCLA reutiliza celulares Android antigos como cérebro de robô de US$ 400 — New Products news briefEditorial cover for a New Products brief. Chip motif; headline "Humanoide PhoneBot da UCLA reutiliza celulares Android antigos como cérebro de robô de US$ 400". Reported key numbers: 4 lb. 1 cited source. Static cover (no animation).NEW PRODUCTS · NEWS BRIEFHumanoide PhoneBot da UCLA reutilizacelulares Android antigos como cérebrode robô de US$ 400REPORTED KEY NUMBERS4 lb1 sourceXAIPART
Cover image generated from data already shown on this page: the category motif, the headline, and reported key numbers. No decorative illustration; no third-party image.

Você chegou de uma resposta de IA — este é o original verificável

Um resumo de IA pode ter omitido a base de suas afirmações. A previsão original, as peças afetadas e todas as citações estão nesta página, cada uma rastreável à sua fonte.

Previsão XAIPART

Este brief traz uma previsão falseável.

Peças afetadas

Nenhuma correspondência no catálogo para esta história — nada é exibido em vez de inferir uma correspondência.

Reported by Hackster.io News on 2026-10-10. Summarized and analyzed by XAIPART Editorial.

What happened

Researchers at UCLA have released PhoneBot, an open-source humanoid robot that uses an ordinary Android smartphone as its main computer and sensor suite. S1 The platform is positioned as a low-cost reuse of consumer-grade hardware that already integrates a processor, camera, inertial measurement unit, and wireless connectivity. S1

The reported build stands approximately 19 inches tall, weighs four pounds, and costs around $400 to build excluding the smartphone. S1 PhoneBot does not include arms or a head, but the source states it can walk on two legs, track people with its camera, and recover after falling. S1

The lower body has 12 degrees of freedom across three joints at each hip, one at each knee, and two at each ankle, plus a thirteenth torso joint that rotates the phone mount without moving the feet. S1 All 13 joints use DYNAMIXEL XL430-W250-T servo motors, and a small onboard computer relays Wi-Fi commands from the phone to the servos. S1 A custom Android app runs the control and movement networks with TensorFlow Lite. S1

The researchers validated the design with four Android phones, including a 2017 Honor 9 and three budget models costing approximately $50 to $80 each. S1 For locomotion, they trained a controller with reinforcement learning in simulation and added a sagittal-mirroring technique that cut left-right joint-angle asymmetry from 0.254 to 0.003 radians. S1 Conversational AI processing still requires an external laptop, and the walking controller was only trained on flat terrain. S1

Key numbers
MetricReported valueSource
Height~19 in[S1]
Weight4 lb[S1]
BOM cost (ex-phone)~$400[S1]
Degrees of freedom13 (12 legs + 1 torso)[S1]
Servo modelDYNAMIXEL XL430-W250-T[S1]
Test phones4 Android units, ~$50-$80 budget, plus 2017 Honor 9[S1]
L-R asymmetry after mirroring0.254 to 0.003 rad[S1]
Payload capacityNot disclosed[S1]

Background timeline

  1. - Honor 9 Android smartphone released, later used as one of PhoneBot's test handsets. [S1]
  2. - UCLA PhoneBot project published as an open-source humanoid using a smartphone as its brain. [S1]

XAIPART take

Technical impact

The architecture is a practical validation that an off-the-shelf smartphone, paired with a small Wi-Fi relay board and DYNAMIXEL XL430-W250-T servos, can close a real-time perception-control loop for a 13-DoF biped. XAIPART analysis Running TensorFlow Lite on the handset and offloading only motor comms to the onboard MCU is a clean split that lets designers swap phones without reworking the electronics. XAIPART analysis

Market impact

The reported $400 BOM excluding the smartphone, plus the use of $50-$80 budget Android handsets, frames PhoneBot as a hobby and education platform, not an industrial SKU. XAIPART analysis For procurement, the relevant part families are the DYNAMIXEL XL430-W250-T servos, an Android-compatible MCU board for the servo bridge, and any phone-mounting hardware; lead time risk is concentrated on Robotis servos, which have historically run multi-week lead times. XAIPART analysis

Action

Designers prototyping low-cost humanoids should budget for one DYNAMIXEL XL430-W250-T per joint, a Wi-Fi-capable MCU (e.g., an ESP32-class board) for the servo relay, and a 3D-printed phone mount sized for the target handset. XAIPART analysis Procurement teams should confirm XL430-W250-T stock and lead time before committing to a PhoneBot clone build, since 13 units per robot are the dominant cost and availability variable. XAIPART analysis

XAIPART Forecast

XAIPART expects that within 9 months of this brief (by 2027-07-11), at least one community fork of PhoneBot will publish a bill of materials that replaces the DYNAMIXEL XL430-W250-T servos with a lower-cost alternative while keeping the 13-DoF kinematics; if no such BOM appears by that date and Robotis-published XL430-W250-T prices do not drop below $40 per unit, this forecast is wrong. XAIPART analysis

Facts are as reported by the cited source. The design-in, sourcing and forward-looking statements above are XAIPART's analysis, not the source's claims. Payload capacity, battery runtime, and torque limits were not disclosed by the source.

Corrections: none at publication. This brief will be updated with a timestamp if the source corrects its report.

Alternativas e ciclo de vida

Alternativas registradas — escopo do catálogo, não um ranking de mercado
PeçaRelaçãoCiclo de vidaBase
— Nenhuma alternativa registrada FALTAM DADOS — Requer match_type antes que qualquer rótulo de antecessor possa aparecer

Os rótulos “predecessor” e “alternativa” vêm apenas de um tipo de correspondência registrado, de um status de ciclo de vida ou do texto da fonte. Quando nenhuma correspondência é registrada, nenhum rótulo é exibido. Nossos próprios anúncios não são referência de mercado.

O que observar

Previsão falseável — limiar, janela e status atual. Previsões refutadas permanecem visíveis.
AfirmaçãoLimiarPorStatus
XAIPART expects that within 9 months of this brief (by 2027-07-11), at least one community fork of PhoneBot will publish a bill of materials that replaces the DYNAMIXEL XL430-W250-T servos with a lower-cost alternativ... no such BOM appears by that date and Robotis-published XL430-W250-T prices do not drop below $40 per unit Pending

Previsões que se revelam erradas permanecem visíveis e marcadas. Não as excluímos.

Peças afetadas

Nenhuma correspondência no catálogo. Esta história não corresponde a nenhuma peça atualmente listada na XAIPART. Não inferimos correspondências e não exibimos uma lista de espaço reservado.

Pressão de custos por dimensão

Source: FRED · Generated · reference output z and composite are algorithm outputs, not a fetch snapshot

Cost pressure by dimension — composite stateDiverging bars for three dimensions around a zero midpoint. Input Cost has no reading; Supply Demand z -1.4711, notable; Fx Energy z 0.4541, neutral. Composite index -7.6, band neutral.0Input costno readingSupply/demandz −1.4711 · notable46 dFX & energyz +0.4541 · neutral6 dcomposite −7.6 · neutral−100 · −40 · −15 · 0 · +15 · +40 · +100
Underlying values — copyable for verification.
DimensionFRED series IDUnitLagAs of
Input costPCOPPUSDM, PALUMUSDM, PNICKUSDMUSD/mt96 d
Supply/demandPCU334413334413, IPG3344Sindex(1982=100) / index(2017=100)46 d
FX & energyDEXCHUS, DCOILBRENTEU, DHHNGSPrate / USD/bbl / USD/MMBtu6 d

No free authoritative interface for: gold · silver · rare earth · polysilicon · lithium carbonate · market share — listed rather than approximated.

Como isso foi produzido

Evidências do processo — coleta, sanidade da fonte, modelo e filtro
Trilha de auditoria deste brief
Source fetched Hackster.io News · www.hackster.io · 3,531 chars · fetch status success
Source sanity (S1) ok — passed before any model call (no s1_ block recorded)
Model / prompt MiniMax-M3 · prompt Blog Agent - News Summary (v2.8-final) · 6,604 tokens · 25.6s · run completed
Gate verdict pass · 6/6 applicable checks passed · spec v2.9 · C10 ratio 0.032523 · C10 rounds 0
Time contract 2 <time datetime> values in this brief — 0 violations (+08:00 or date-only)

Cada linha acima é produzida pelo pipeline, não escrita à mão.

Pontuação editorial

Resultado do filtro determinístico — PHP puro, sem envolvimento de modelo no veredito
Detalhamento da pontuação do filtro 6 verificações aplicáveis, 6aprovadas: 100 %. No hold items or mandatory failures. Gate spec: v2.9 (S0 + S1 + C1–C20) · Source affinity (C20): 0.8308. Verificações aplicáveis aprovadas 6 / 6 = 100% · veredito: pass No hold items or mandatory failures Gate spec: v2.9 (S0 + S1 + C1–C20) · Source affinity (C20): 0.8308 O filtro decide a publicação. A pontuação da auditoria independente é apenas consultiva.
Encontrou um erro? Conte-nos o que está errado — as correções são publicadas junto com o texto original e registradas. Não editamos artigos silenciosamente.

Comentários

Seja o primeiro a comentar.

Fontes

  1. Don't Throw Away Your Old Phone — Build a Robot Instead — https://www.hackster.io/news/don-t-throw-away-your-old-phone-build-a-robot-instead-392de07d053a · rss · acessado em

Os fatos são marcados como S1/S2 e remetem à fonte vinculada. Trechos rotulados como análise são o raciocínio da própria XAIPART, mantido separado dos fatos reportados. Os links das fontes são seguidos em vez de nofollow — a atribuição é intencional.