alex/pi-car-companion
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add direct car telemetry management

Browse Source
This commit is contained in:
Alex
2026-07-31 23:14:40 +02:00
parent 530162cbf7
commit e347a581e1
16 changed files with 447 additions and 57 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PLAN.md
+5 -5
View File
@@ -229,7 +229,7 @@ reference, not proof for other model years, trims, regions, or software builds.
- Car UX restrictions are enforced while moving. Version 1 is parked-use software
unless a later native activity is explicitly designed, declared, and validated as
distraction optimized.
- The Pi is the only intended ADB host. The bridge targets either one configured
- The Pi is the only intended ADB host. The integration targets either one configured
serial or exactly one automatically discovered device, refuses ambiguous multi-device
connections, uses argument-array process execution, enforces timeouts and output bounds,
exposes unavailable/unauthorized/offline states, and registers every operation in a
@@ -237,14 +237,14 @@ reference, not proof for other model years, trims, regions, or software builds.
or an unrestricted file path. Package and component targets are accepted only through
strict Android-name validation and fixed `am` or `monkey` argument arrays.
- Device identity, connection health, display, package inventory, bounded APK install,
validated app launch, the three confirmed ArcSoft vehicle properties, and the typed
read-only MG Utility battery bridge are in scope.
validated app launch, the three confirmed ArcSoft vehicle properties, and direct
read-only factory vehicle-service telemetry are in scope.
State-changing ADB actions are authenticated, CSRF-protected, rate-limited where
appropriate, audited, and intended for parked use.
- Do not use ADB or the exported SAIC vehicle service to actuate vehicle hardware in
this project. Vehicle telemetry remains read-only. Battery, range, voltage, consumption,
and charging state pass through MG Utility's typed content provider; additional SAIC
signals remain a research track until their semantics are documented and tested.
and charging state come from fixed getter transactions made by the non-installed ADB
probe; additional SAIC signals remain a research track until documented and tested.
### Web experience