feat: add direct car telemetry management

This commit is contained in:
2026-07-31 23:14:40 +02:00
parent 530162cbf7
commit e347a581e1
16 changed files with 447 additions and 57 deletions
+7 -6
View File
@@ -239,12 +239,13 @@ If the device is disconnected, offline, unauthorized, partially readable, or ADB
missing, the dashboard reports that state without substituting generated data. APK
installation and app launches are administrator actions intended for a parked vehicle.
The Car page refreshes the three verified live properties from the captured MG4 unit:
`arcsoft.avm.mCurCarSpeed`, `arcsoft.avm.mCurCarGear`, and
`arcsoft.avm.mCurCarWheelAngle`. The property dump does not expose traction-battery or
range values. Those fields remain unavailable until a read-only Android bridge binds to
SAIC's exported vehicle service; head-unit battery data is deliberately not presented as
the car battery.
The Car page refreshes the verified live properties `arcsoft.avm.mCurCarSpeed`,
`arcsoft.avm.mCurCarGear`, and `arcsoft.avm.mCurCarWheelAngle`. Traction-battery and
range values are queried directly from the factory SAIC vehicle service using a small
read-only DEX probe run through ADB. The probe is pushed to `/data/local/tmp` and run
with `app_process`; it is not installed as an Android app and does not depend on MG
Utility. Android's head-unit battery status is deliberately not presented as the car
battery.
### System controls and shell