Repository navigation
Havne v0.7.4
Havne 0.7.4 follows up the Dashboard and the viewer: a layout saved to a file and loaded back, more gauge colors, steady trends on the Dashboard and Live's chart, every plugin variant offered for a vehicle, Compare's difference trace, the demo car under obd2, and Android's own document picker. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.7.4-windows-x64.zip |
| Linux (x86_64), the app | havne-0.7.4-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.7.4-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.7.4-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.7.4_amd64.deb (Debian, Ubuntu) or havne-core-0.7.4-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.7.4_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.7.4-linux-aarch64.tar.gz |
| Python wheel (Windows x64, Linux x86_64 and arm64, macOS arm64 13+) | pip install havne-0.7.4-py3-none-<platform>.whl; Python 3.11 or later |
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). The AppImage runtime's sources, fuse-3.15.0.tar.xz and type2-runtime-20251108.tar.gz, are there as LGPL-2.1 asks: the runtime links libfuse statically (the AppImage's notice says more). GitHub adds the source code archives.
Try it
Windows
- Download
havne-0.7.4-windows-x64.zipand unzip the whole folder. - Run
havne.exe. The program isn't code-signed, so SmartScreen may stop it the first time: choose More info, then Run anyway. - Press Demo data on Home, then 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)
- Download
havne-0.7.4-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.7.4-linux-aarch64.AppImage. chmod +xit, then run it.- Press Demo data on Home, then 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.7.4_amd64.deb (./havne-core_0.7.4_arm64.deb on ARM), or unpack havne-core-0.7.4-linux-x86_64.tar.gz (havne-core-0.7.4-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.7.4-android-arm64-v8a.apkand 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. - Open Havne. On Dash, press the Demo data row, then 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.7.3
Live and the Dashboard
- A layout in a file: Export layout and Load layout on Dash's Page row save a page's gauges to a file and load them back. The phone's and the desktop's layouts stay apart, never scaled into each other, and a load says which of the signal files the layout reads this vehicle lacks.
havne-cli layout check <file>checks a layout file with no app (ADR-0057). - Five more gauge colors (red, blue, yellow, green and light blue; the green before them is Light green), or one of your own from red, green and blue under Custom... in the panel's Color row.
- Steady trends: the Dashboard's sparkline and Number tile keep their trace while you visit another page, Settings or Live, and a short spike (lambda through a fuel cut) keeps its height and its place as the trace scrolls. Live's chart holds still as it scrolls: a signal that swings keeps its shape from frame to frame, a trace's scale widens at once and narrows only when the trace has shrunk well inside it, and the plot keeps its width when a value gains a digit or a minus sign.
- On a phone, a gauge's panel gives its size as Columns and Height, both in columns.
The viewer
- Compare's Difference switch draws, for each plotted signal both recordings hold under one name and unit, the compared recording's value less this one's in a pane of its own (ADR-0056).
- The chart keeps its detail further out: it reads samples or per-second summaries by the signals plotted, so two short logs lined up on a pull draw sharp from the start.
- Closing a recording stops its pull and cruise search where it is and doesn't wait for a span's statistics. On a phone, the pane seams and the chart's splitter take a touch anywhere within a finger's width.
Vehicles, plugins and the demo
- Every imported plugin's variants are offered on Settings' Signals page for the picked vehicle, its VIN known or not. The variants a VIN covers come first and stay marked with the vehicle after the session ends; nothing asks for a VIN, and nothing is picked for you (ADR-0052).
- The demo car answers OBD-II under the
obd2profile from its drive cycle, so theobd2Dashboard, Boost included, shows values with no car;havne-cli sim's simulated car answers the same PIDs (ADR-0039). - A car whose supported-PID list ends early shows the signals past its end as not sent, and
mock://gives each ECU a signal file or plugin reads a channel of its own.
Android
- Android's own document picker opens Load layout, Import a log, a column map, a signal file, an OBDb set and a plugin, and reads the file picked, a name with parentheses ("name (1).json") included. An export to a name already taken writes the "(1)" document, a folder export through the picker works, and a save that is refused or fails removes only the empty document the picker made.
- Paired headsets, watches and health devices sit under Other paired devices, not among the adapters. In developer mode the display line gives the phone's form and orientation alone, never its size.
Accessibility, Python and the C API
- With a screen reader on, Live's rows and the Log's By ID list read as one item each.
- Python's
Recording.stretches,find_thresholdandfind_markerstop at Ctrl+C and takecancel=; the C API addsecuio_recording_stretches_withandecuio_recording_find_with.havne-cli viewends at Ctrl+C with the interrupted end line.
Fixes: SocketCAN's close waits for a read under way before it returns each module to the default session (ADR-0060), a drag after pressing Live, the Stretches panel's levels across a change of units and under a comma locale, a frame table's place, an import's words over the next recording, a recording row's signal count, a short CSV's column map, havne-cli export --rows saying when an interval thins nothing, a relay that can't start, and keepalive_ms across a change of address kind. CHANGELOG.md lists each.
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; a GCC or Clang warning fails it. Dev's CI run 43620355468 passed on this release's tree, and the release pull request's run on this release's commit gates the tag.
- Locally the full verify at dev's tip passed 2232 of 2232 tests; the skipped cases are the ones gated on what a Windows machine lacks (Linux, Wireshark's
tshark, the car's raw recordings) or that the cross-arch step runs, and the cross-arch (x86) step passed 108 of 108. - On a phone: the release APK of v0.7.4-rc1 on the test phone (Android 16) under
mock://demo: Live's chart through the demo's rev-limiter pulls, its bands holding their edges as they scroll; the Dashboard's trends across page switches; two layout exports under one name, the second "(1)", and each loaded back, a cancel changing nothing; the signal file, OBDb and plugin imports refusing a layout file in their own words; a CSV saved to a cloud provider online and offline. Development builds before it ran each of the six open dialogs with a file named "name (1)", a plain one and a cancel; a folder export; a cloud save made offline, which uploaded once the network was back; a layout's export, an uninstall and its load; and the viewer's seams by finger. The connect list's Other paired devices has not been looked at on a phone. - On a car: nothing new in 0.7.4 has run on a car. SocketCAN's close is tested against the simulated bus only.
- Not yet run: the published downloads haven't connected to an adapter or a car, and the iPhone app has not run on a device.
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.7.4.intoto.jsonl. Check them with the GitHub CLI:
sha256sum -c --ignore-missing SHA256SUMS.txt
gh attestation verify havne-0.7.4-windows-x64.zip -R erickramer42/havne
gh attestation verify havne-0.7.4-android-arm64-v8a.apk -R erickramer42/havne
gh attestation verify havne-0.7.4-linux-x86_64.AppImage -R erickramer42/havne
gh attestation verify havne-core_0.7.4_amd64.deb -R erickramer42/havne
gh attestation verify havne-0.7.4-py3-none-win_amd64.whl -R erickramer42/havne
Those read GitHub's attestation store; add --bundle havne-0.7.4.intoto.jsonl to check against the attached file instead.
The SBOM, havne-0.7.4.spdx.json, is attested to the zip, the APK, the AppImages, the debs, the tarballs and the wheels: 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.7.4-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 core's packages ship and every download's notice repeats, 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.