P0.4 · Design + electronics audit

The architecture is viable. The USB behavior is not proven yet.

Conditional go for EVTKeep BLE HID for the MVP. Prototype the always-inserted plug as a floating, replaceable bridge; never use USB hardware for structural alignment.
PHONEUSB-C male plugalways inserted · floating cartridge
→
CASEFlex + keyed contactsUSB 2.0 · CC · VBUS · GND · shield
→
DOCKIsolation + PD sourcedead until lock proven
→
POWERDedicated boostseparate from main charger path
Audit summary

What passes, what remains open.

This is a concept-level design review, not a completed schematic review, compliance result or physical test.

Concept pass

Mechanical load path

Full-width torque tube, double-shear towers and tapered receivers keep hinge and drop loads out of the phone connector.

Critical open

Phone-port protection

Official STEP/DWG now anchor nominal geometry. The always-inserted plug still needs a compliant floating carrier, hard stops and a replaceable cartridge; safe side-load and unit-to-unit tolerance remain unmeasured.

Critical open

USB role + charging

Android host mode normally makes the phone power the bus. Simultaneous wired HID and charging cannot be promised until tested on production Seeker.

MVP choice

BLE input transport

Keyboard and controllers stay BLE HID. USB initially handles controlled phone power and an experimental data path.

High open

Exposed contacts

Use recessed contacts, ground-first mating, VBUS isolation/discharge, ESD protection, dock detect and contamination testing.

Known compromise

USB-C stays occupied

No ordinary wired charging or accessories while the shell is installed. Seeker officially supports wireless charging; shell thermal/RF performance still needs testing.

Safe sequence

Power only after structure.

  1. AlignReceivers and spine locate the modules. USB parts take no load.
  2. GroundShield and ground contacts mate first; VBUS remains off.
  3. LockIndependent latch sensing proves full mechanical engagement.
  4. ConnectCC and USB 2.0 data become available after a stable mate.
  5. PowerPolicy may enable limited phone charging with thermal/current supervision.
  6. ReleaseStop data, open VBUS, discharge the bridge, then unlock.
Architecture choice

Two USB modes, neither assumed.

EXPERIMENT A

Phone as USB host

Standard keyboard/gamepad behavior is attractive, but Android documents the phone as the bus host and power source in this mode. Power/data role negotiation must be proven while the dock charges Seeker.

EXPERIMENT B

Dock as Android accessory host

The dock can power the bus, but Android accessory mode needs a companion protocol/app and does not automatically present as a normal HID keyboard or controller.

Released MVP: BLE HID for inputs, separately controlled USB-C charging through the bridge. Wired input stays behind an engineering flag until the Seeker role matrix passes.
Release gates

What must be built and measured next.

EVT0 · Interface
  • CMM/scan 3 production phones
  • USB plug carrier + flex coupons
  • Dock-contact supplier drawings
  • Instrument connector side loads
EVT1 · Electrical
  • USB analyzer role matrix
  • Partial-mate and backfeed faults
  • VBUS shutoff/discharge timing
  • ESD and signal-integrity tests
EVT2 · System
  • 10,000 dock cycles
  • Drop, contamination and moisture
  • Wireless charge/RF coexistence
  • Thermal chamber + power derating

Inspect the USB path in the 3D assembly →