Android Hardware I/O

hardware_io.android contains hardware-facing access to sensors supplied by the OpenRoadCode Android sensor bridge. The bridge listens only on the phone’s localhost interface, currently at http://127.0.0.1:8766.

The layering is intentionally:

flowchart TD
    android["Android hardware / bridge"] --> adapter["hardware_io.android"]
    adapter --> domain["Controllers / services"] --> consumers["Messaging / applications"]

    classDef orcApp fill:#dbeafe,stroke:#2563eb,color:#172554;
    classDef orcService fill:#ede9fe,stroke:#7c3aed,color:#2e1065;
    classDef orcController fill:#dcfce7,stroke:#16a34a,color:#14532d;
    classDef orcMessage fill:#ffedd5,stroke:#ea580c,color:#7c2d12;
    classDef orcAdapter fill:#fee2e2,stroke:#dc2626,color:#7f1d1d;
    classDef orcExternal fill:#f3f4f6,stroke:#6b7280,color:#1f2937;
    class android orcExternal;
    class adapter orcAdapter;
    class domain orcController;
    class consumers orcMessage;

AndroidSensorBridgeClient is the low-level bridge client. Its IMU snapshot contains accelerometer, linear acceleration, gyroscope, magnetometer, and barometric-pressure data when those sensors are available on the phone.

AndroidMagnetometer is the hardware-facing magnetometer device. Navigation code should adapt this device to its own contracts rather than reading Android sensor payloads directly.

Magnetometer component test

Start the Android bridge application, then from the OpenRoadCode checkout in Termux run:

python -m hardware_io.android.component_test.magnetometer_cli

Rotate the phone through several orientations. The X/Y/Z magnetic field values and field magnitude should change continuously. Ctrl+C stops the test.

Sensor bridge diagnostic

The bridge can be checked independently of Python with:

curl http://127.0.0.1:8766/health
curl http://127.0.0.1:8766/imu

The /imu response is diagnostic/raw bridge data. Application code should use hardware_io interfaces and adapters instead of depending on the HTTP schema.