TCFDONMEZandClaude
2fd7b2dde1
A fork of malys/EVABRPUploader (itself a fork of Leon Kernan's ABRP_Uploader) carrying the changes that make it work on this car. History starts here: the tree is what matters, and the upstream projects are where the earlier work belongs. EVHardware is vendored rather than tracked as a submodule, so one clone builds. Telemetry. SOC, battery power and range read as unavailable on SWI69 because the vendor fallbacks were gated to SWI68 alone, while the property ids they use are the ones this car publishes — the gates now admit SWI69. Tyre pressure, the odometer and charge status come from the vendor block too, since the generic properties for all three are declared here and never publish. Tyre pressure is confirmed on the vehicle; the other two are not yet. Vehicle page. Every signal the car answers, in a table. One that it does not publish shows a dash: an unimplemented VHAL property returns zero, and "0 °C" would read as a measurement. Wi-Fi page. Joins a network the unit already has saved, so a phone hotspot does not need a trip into Settings on every drive. Tried on the upload tick and from a button, skipped while already associated. This leans on the unit being API 28 and the build being platform-signed — getConfiguredNetworks and enableNetwork are closed to ordinary apps from API 29 — and fails quietly where that does not hold. The OTA updater points at this repository. An APK from upstream is signed with a different key, which Android will not install over a platform-signed build. Co-Authored-By: Claude <noreply@anthropic.com>
4.2 KiB
Public energy-signal candidates
Reviewed 2026-08-28 for CP-004. This review uses only public AOSP catalogues and the project's existing runtime read seam. It does not use proprietary artifacts or non-public property catalogues.
Safety and validation boundary
Every entry below is read-only and starts with validated: no. A public property number proves
only that AOSP assigned a number and semantics; it does not prove that an MG4 VHAL implements or
publishes it. No candidate may enter EnergySnapshot, a production fallback or a stable UI until
CP-003 records availability, unit, scale, sign and update cadence for every supported firmware
generation. An unavailable or non-finite read stays null.
Public catalogue findings
| Signal | Public declaration | Type / area / unit / mode | AOSP coverage | EVSuite disposition | validated |
|---|---|---|---|---|---|
EV_CURRENT_BATTERY_CAPACITY (291504909, 0x1160030D) |
AOSP snapshot c80b787 |
Float / global / Wh / on-change / read-only | Public post-AAOS 9 API; the declaration requires Car UDC with Android 13 or later | Highest-value new candidate: status-aware probe in unstable evidence capture only | no |
EV_BATTERY_AVERAGE_TEMPERATURE (291504910, 0x1160030E) |
AOSP change 5b96f99 |
Float / global / °C / continuous / read-only | Added to the public API in December 2023 | Already read by the CP-001 baseline as nullable battery temperature; CP-004 adds no duplicate candidate | no |
EV_BATTERY_INSTANTANEOUS_CHARGE_RATE (291504908, 0x1160030C) |
Android 9 AOSP snapshot 8686c86 |
Float / global / mW / continuous / read-only | Android 9 public catalogue | Existing CP-001 battery-power input; its live scale and sign still require CP-003 evidence | no |
All cited files are Copyright Android Open Source Project and licensed Apache-2.0 at the cited commit. The review records public declarations, not copied implementation code. Vehicle coverage remains unknown for SWI68, SWI69, SWI131, SWI132, SWI133 and SWI165 until CP-003 runs on each one.
Explicit negative results
| Requested quantity | Public catalogue result | Consequence |
|---|---|---|
| HVAC, compressor or PTC electrical power | No Android 9 or reviewed later public vehicle property. HVAC_POWER_ON is only a boolean subsystem state. |
Climate energy can only be estimated from validated pack power and controlled trials. |
| Battery-heater power | No public power or energy property found. Battery temperature is a temperature, not heater consumption. | No direct measurement candidate. |
| DC-DC or accessory load | No public power or energy property found. | No direct measurement candidate. |
| Cumulative battery discharge | No public cumulative counter found. EV_BATTERY_LEVEL is current stored energy. |
Integrate validated instantaneous power, retaining uncertainty and gaps. |
| Cumulative regeneration | No public cumulative counter found. Later regenerative-braking properties describe a state, not recovered energy. | Integrate only after CP-003 proves the power sign convention. |
| Per-trip energy | No public per-trip energy property found. | EVSuite trip totals remain derived from validated samples. |
The search deliberately stops here: sweeping arbitrary property ids would produce ambiguous data and broaden the runtime surface without provenance.
Probe wiring
EV_CURRENT_BATTERY_CAPACITY is read through the same status-aware reflected
CarPropertyManager.getProperty path as existing telemetry. The read is explicitly branched over
the supported firmware generations and returns null for unknown firmware, unavailable status,
negative values, exceptions and non-finite values. It is exposed only by
EnergyTelemetryReader.readEvidence() and recorded as
candidate.evCurrentBatteryCapacityWh; ordinary read() and EnergySnapshot are unchanged.