Skip to content

Havne v0.5.1

Choose a tag to compare

@github-actions github-actions released this 06 Nov 23:17
· 1165 commits to main since this release
c6067c5

Havne 0.5.1 is a patch: a recording replays with the signal file it was recorded with, a signal its module refuses says so, and a vehicle's signal file can be saved out of the app, after a run of 0.5.0's own signals on the test car. Read DISCLAIMER.md before connecting it to a vehicle.

Downloads

For Download
Windows (x64) havne-0.5.1-windows-x64.zip
Linux (x86_64), the app havne-0.5.1-linux-x86_64.AppImage
Linux (64-bit ARM: a Raspberry Pi 3 or later), the app havne-0.5.1-linux-aarch64.AppImage
Android 12 or later (64-bit ARM) havne-0.5.1-android-arm64-v8a.apk
Linux (x86_64): havne-cli and core alone, for your own programs havne-core_0.5.1_amd64.deb (Debian, Ubuntu) or havne-core-0.5.1-linux-x86_64.tar.gz
Linux (64-bit ARM): havne-cli and core alone havne-core_0.5.1_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.5.1-linux-aarch64.tar.gz

The other files under Assets check a download or debug one: SHA256SUMS.txt, the build provenance (.intoto.jsonl) and the SBOM (.spdx.json), described below under Verifying the downloads; the Windows PDBs (-symbols.zip) and havne-cli's Linux debug info (-dbgsym deb, -debug tarball). GitHub adds the source code archives.

Try it

Windows

  1. Download havne-0.5.1-windows-x64.zip and unzip the whole folder.
  2. Run havne.exe. The program isn't code-signed, so SmartScreen may stop it the first time: choose More info, then Run anyway.
  3. In Settings, tick Developer mode under Display, then press the mock://demo preset under Adapter and Connect.

The zip's README.txt covers adapters and what each file is. havne-cli.exe is beside havne.exe: havne-cli stream mock://demo --values --count 20 prints a simulated car's frames and values.

Linux (x86_64 or 64-bit ARM, glibc 2.39 or later: Ubuntu 24.04 and newer, Debian 13 and Raspberry Pi OS 13, Fedora 40 and newer, Arch)

  1. Download havne-0.5.1-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system) havne-0.5.1-linux-aarch64.AppImage.
  2. chmod +x it, then run it.
  3. In Settings, tick Developer mode under Display, then press the mock://demo preset under Adapter and Connect.

It takes OpenGL, fonts and FUSE from the system; a minimal install may lack them. docs/linux.md says what to install, how to reach an adapter (serial permissions, Bluetooth, SocketCAN) and where Havne keeps its files.

For havne-cli and the core alone: sudo apt install ./havne-core_0.5.1_amd64.deb (./havne-core_0.5.1_arm64.deb on ARM), or unpack havne-core-0.5.1-linux-x86_64.tar.gz (havne-core-0.5.1-linux-aarch64.tar.gz) anywhere.

Android 12 or later (64-bit ARM)

  1. On the phone, download havne-0.5.1-android-arm64-v8a.apk and open it. Android asks to let your browser or file manager install apps the first time; Play Protect may offer to scan an app from outside Google Play.
  2. Open Havne. In Settings, tick Developer mode under Display, then press the mock://demo preset under Adapter and Connect.

A later release installs over this one and keeps its settings and recordings. A Havne built by CI or from source carries another key, so uninstall it first.

What's new since 0.5.0

Your own signals, as they were recorded

  • A replay decodes with its recording's own signal file: a recording holds the file it decoded with, and its replay uses that copy, in the app and in havne-cli stream replay://, so a recording replays as it was recorded after the vehicle's file has changed or been removed, or on another machine. A copy that no longer matches its hash isn't used, and the replay says why (docs/signal-files.md).
  • A refused signal shows as refused, not blank: Live's row reads "Refused: requestOutOfRange (7F 22 31)", the negative reply's code by name, and havne-cli stream --values writes a refused line naming each such signal with its request, the reply and the code's name. A module that leaves PIDs out of its supported-PID bitmaps still has its refusals named, and past the eight a module's report lists, Live's status line and the refused line say how many more it refused. A refused signal gives its place among the chart's default signals to the next. On a phone, a row too narrow for the words reads "Refused (7F 22 31)" and the name keeps its room. A replay shows no refusal: the recording keeps it only as an activity line.
  • Save a copy: Settings' Vehicle section saves each of a vehicle's signal files out of the app, through the desktop's save dialog or Android's document picker, byte for byte, so a file made in the form can be shared or given to havne-cli --signals. docs/signal-files.md walks through a DID scan, Read once, the file, a recording holding it and sharing it.
  • The form and the vehicles: each box in the form for a vehicle's own signals has its name above it; a Request ID left empty keeps the module's, and a typed one that differs moves the module's other signals too, the note naming them. When the connected car's VIN picks another saved vehicle than the one picked, the Vehicle section says so until you pick one yourself. Picking another vehicle, or New, or the end of a session in which the VIN picked another, puts What to read back to Default when it named the last vehicle's file, and a vehicle the VIN adds keeps no other vehicle's file in its connection.
  • The viewer's Replay view is Replay in Settings: it fills Settings' field with the part in view for Connect, and it's off while a session runs.

Speed

  • On Windows, a session that asks waits out the request engine's 20 ms floor on a high-resolution timer instead of Windows' 15.6 ms step: against an adapter whose empty reads return at once, each module is asked about every 21 ms, from 31, however many modules. Through the OBDX Pro VX the pace stays the adapter's own, about 27 ms.
  • The charts draw their traces on the GPU: on the test phone, a tap on the Recordings page's chart with every signal plotted holds the app about 50 ms instead of 150, and a drag moves the chart as it goes.

Fixes

  • A plugin whose data files hold a number in its shortest 17-digit form, as Python and most tools write one, loads; it was refused. Every number a signal file, a plugin, an OBDb import or a recording holds reads as the double nearest it.
  • On Windows, havne-cli takes a path with a character outside the system's code page, so a replay, a recording, view, info, a signal file, an OBDb import and a plugin under a folder named with an accent or in Greek work.
  • Importing a newer version of a plugin that couldn't be kept left neither version loaded; the loaded version stays until the new one has loaded in its place.
  • The full list is in the CHANGELOG.

For programs that use core

  • No ABI change. A channel's support report (ecuio_channel_support_t) lists in dropped_list the requests a negative reply refused before those the bitmaps left out, each in set order; before, all were in set order.

Known issue

  • Through the OBDX Pro VX, with requests out to two modules, the second module's reply can be lost while the first's longer reply is in flight: 22% of one module's requests on the test car, 1.1% with ?pack=0 on the URI, the workaround for a two-module session through the VX (STATUS.md's Known Issue #42). The OBDLink MX+ lost none.

What's verified, and where

Havne's claims are tiered (docs/testing.md):

  • Every build runs the full test suite on Windows, macOS and Linux in CI, plus sanitizers, fuzzing, clang-tidy, CodeQL and the load test, and a check of the C ABI against 0.5.0's; a GCC or Clang warning fails it. The Android and iOS apps are cross-built there, and the 64-bit ARM Linux files are built and smoked on an ARM runner. On Windows the suite is 1271 cases, all passing but three that need a local build tree, the car's raw recordings or Linux, and the 102 cases of the 32-bit driver path pass through the x86 helper too.
  • Against the fakes: a two-module session through the fake J2534 driver and the fake ELM327 asks each module at the engine's floor, a median of 20.6 and 20.5 ms, by the fakes' own stamps; a refused DID reads Refused on Live and in havne-cli, through the fake on Windows and the simulated ECU on Linux.
  • On the test car (a development build from before this release's review fixes): a signal written in Settings' form and checked with Read once, a signal file's DIDs on two modules, a DID the module refuses shown as refused, an enumeration and boost, read through the VX over J2534 in the app and havne-cli, and through the OBDLink MX+ on the test phone; each recording replayed through its own copy, in the app and havne-cli, after the file was removed from the vehicle; the file saved out of the phone with Save a copy passed havne-cli signals check (2026-11-06). The run found Known Issue #42 and the phone, vehicle and viewer changes above; those changes, and the review's fixes, are checked by the test suite, not on the car.
  • On the test phone (Android 16, a development build): the car run's file in the app through the MX+, recorded, and saved out through Android's document picker.
  • Not yet run: plugins against a real ECU (each so far is the simulated car's); SocketCAN requests through a real controller (no controller on hand offers one-shot mode); the iPhone app on a device. This build itself hasn't connected to an adapter or a car.

Verifying the downloads

SHA256SUMS.txt holds every download's SHA-256, the debug files' and the SBOM's. One signed build provenance from this repository's release workflow covers every download, attached as havne-0.5.1.intoto.jsonl. Check them with the GitHub CLI:

sha256sum -c --ignore-missing SHA256SUMS.txt
gh attestation verify havne-0.5.1-windows-x64.zip -R erickramer42/havne
gh attestation verify havne-0.5.1-android-arm64-v8a.apk -R erickramer42/havne
gh attestation verify havne-0.5.1-linux-x86_64.AppImage -R erickramer42/havne
gh attestation verify havne-core_0.5.1_amd64.deb -R erickramer42/havne

Those read GitHub's attestation store; add --bundle havne-0.5.1.intoto.jsonl to check against the attached file instead.

The SBOM, havne-0.5.1.spdx.json, is attested to the zip, the APK, the AppImages, the debs and the tarballs: add --predicate-type https://spdx.dev/Document/v2.3 to check it.

The APK is signed with Havne's release key, whose certificate SHA-256 is fb4f415a1f6c0dc56ee54dcd454c29d2226bc293c7b4c978a9b9bc8e74c4210f (packaging/android/release-cert.sha256). With the Android SDK's build tools, apksigner verify --print-certs havne-0.5.1-android-arm64-v8a.apk prints it.

Third-party data

Havne's core carries data from others, each under its own terms, listed in core/THIRD_PARTY_NOTICES.txt, which the Windows zip and core's packages ship, and compiled into every binary:

  • Trouble-code titles: SAE J2012's generic powertrain and network codes, from Wal33D/dtc-database (MIT).
  • Vehicle makes: the manufacturer codes of NHTSA's vPIC, a work of the US government.