You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 185a0fe
Browse filesBrowse the repository at this point in the historyBrowse files
feat(diagnostic): read-only probes for radio, OEM screens, vendor surface and power cycle
The 2026-10-13 triage of CR-020, CR-030, CR-045/046 and RI-004 left each
ticket waiting on one fact only the car can give, and the owner installs
stable builds only. Every probe here reads; none writes to the vehicle.
- CR-020: ALLOWED on a radio action only says the binder call returned.
The radio actions now read SaicRadio.currentStation() before the call
and 1.5 s after it, on the rule's worker thread, and the history detail
carries both. Diagnostic row RADIO_STATE does the same read on demand.
- CR-030: Diagnostic row OEM_SCREENS lists the exported activities of the
installed com.saicmotor.* packages, capped at 150 lines. Nothing launched.
- CR-045/046: the capture tool sat in EVProfile unstable only. The stable
Diagnostic tab now calls EVHardware's VendorSurfaceProbe.capture()
(getters only, setters refused by VendorSurfaceRules) through Capture
before / Capture after, and Export carries VendorSurfaceRules' diff.
- RI-004: the vehicle service stores the last ignition-off and a 30 s
heartbeat on its existing sampling handler (no wakelock, no alarm,
apply() into app-private prefs). A heartbeat gap closes the previous
cycle; row POWER_CYCLE prints its off, last heartbeat and the gap, which
is the head unit's post-off run window.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments