Skip to content

v2.4.0

Choose a tag to compare

@github-actions github-actions released this 07 Sep 17:51
· 19 commits to master since this release

EVLauncher v2.4.0

This build has no auto-updater and no silent installer. The EVSuite screen
checks allowlisted GitHub releases only after the user opens it, shows the
changelog, and exports verified APKs for manual installation.

Install

Copy the APK to a USB stick, open the car's Files app and tap it. Then set it
as the default home from Android settings.

Note

Signed with the EVSuite platform key. If you are coming from a build signed
with the old author key, uninstall the previous version first — Android refuses
an in-place update across a key change.

Changelog

Removed

  • Twelve vehicle metrics that could never answer on this car: speed, cabin temperature,
    odometer, charge port, the four tyre pressures, and battery power / energy / capacity /
    temperature. Each is a standard AAOS property behind a car permission this launcher does not
    hold — and, for the dangerous ones it does declare, does not request at runtime either, so
    a manifest line was never a grant. They were offered on the argument that a dash saying
    unavailable on this car is an honest answer; on the vehicle it is noise, since nothing in
    the picker told the driver which entries can never fill in. EVTasker's diagnostic reports the
    same signals unreadable there, for the same reason. Reasoning:
    docs/CR-011-metrics-page.md.
  • The charging card's port-flag caption. It read EV_CHARGE_PORT_CONNECTED, which needs
    CAR_ENERGY_PORTS — held by no app in the suite — so the flag was never once non-null and
    the caption always fell back.

Changed

  • The picker now offers thirty-one metrics: the eighteen head-unit ones, unchanged, and
    thirteen vehicle ones that answer through the SAIC vendor services — charge, range, charging,
    outside temperature, the eight climate signals — plus the gear position, which EVHardware
    reads through the vendor condition manager rather than CarPropertyManager. None of them
    needs a car permission, which is why they work.
  • A metric card a driver had already chosen and that this build dropped is skipped on the next
    page build, as any unknown key already was. Nothing else on the page changes.

Car permissions are unchanged: still CAR_ENERGY and CAR_VENDOR_EXTENSION, read-only.