Repository navigation
Havne v0.7.3
Havne 0.7.3 is for reading your recordings: the viewer's chart in panes with two cursors and a span's statistics, a Jump row between a recording's pulls and cruises, Live's pause, and first-run words that find the way without the guide. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.7.3-windows-x64.zip |
| Linux (x86_64), the app | havne-0.7.3-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.7.3-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.7.3-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.7.3_amd64.deb (Debian, Ubuntu) or havne-core-0.7.3-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.7.3_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.7.3-linux-aarch64.tar.gz |
| Python wheel (Windows x64, Linux x86_64 and arm64, macOS arm64 13+) | pip install havne-0.7.3-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.3-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.3-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.7.3-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.3_amd64.deb (./havne-core_0.7.3_arm64.deb on ARM), or unpack havne-core-0.7.3-linux-x86_64.tar.gz (havne-core-0.7.3-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.7.3-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.2
The viewer
- The chart is in panes, one for each unit, stacked on one time axis, each with its own axis. A pane's range zooms with Ctrl and the wheel or a vertical pinch, and a drag on its axis pans it; dragging the line between two panes sets their heights (ADR-0061).
- A second cursor (Shift+click, or a long press) shows the span between the two: its length, and each signal's change, lowest, highest, mean and rate. On a phone the title row and the chart stay put while one list scrolls under them.
- A Jump row steps between a recording's pulls and cruises, with each drawn as a band on the chart. Stretches... sets the levels that make one; the app and
havne-clifind pulls as road logs drive them (ADR-0056). - Compare lines two recordings up on a pull you choose in each. It is a button beside Export.
- A recording opens with at most four signals plotted, and a trace keeps its own color.
Live and the Dashboard
- Live's pause: drag the chart to look back through the last two minutes while the values keep updating; Live (or Space) follows now again.
- Change a gauge's kind and pick its color in its panel; gauges warn below a level as well as above one, and a new gauge on a common signal starts with zones for a gasoline engine. The panel shows the gauge it edits.
- The demo vehicle is turbocharged, with boost that builds and vents, and says which signals it never sends.
Finding your way
- The Demo data row and the Log's raw frames are there for everyone, no Developer mode. Mark stands beside Stop log, and Live says what a log records.
- Settings says why a page is dim while a session runs, what Record sessions keeps and what a vehicle is for; Connection has an Extended session box.
- On a phone the status reads Connected, a connect from Other address... returns to the page that sent it, and Profile is three segments.
Recordings and import
- A recording's row says how long it is, whether it is a log or a whole session, and its marks. Import takes a label, opens its recording, and can be canceled; on Android its picker offers every file.
- A CSV with padded cells, a bare numeric time or rows with no time imports as the file means it, and a wide export no longer lets a sparse column set the pace (ADR-0054).
Signals, the extended session and the C API
- A signal file may replace one of OBD-II's signals by name, and OBD-II reads Boost. A signal set that repeats a name is refused, and a computed signal's input a file turns into text is named.
- The extended session's close waits for the module, so it is returned to the default session (ADR-0060).
havne-cli viewtakes--spanand--stretchesand aligns on a chosen pull with each column's mean and delta; Python'sRecordinghasstats,step,role_signalandstretches, and looks up a VIN and a trouble code offline. The C API addsecuio_recording_stats,_step,_stretchesand_role_signal.
Fixes: the Dashboard after Reset, a connect list's two recents on one adapter, Live's Space key, the viewer's keys and cursor handle, an aligned view's columns and the axis's end, a second Ctrl+C after a finished export, and more. 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. The release pull request's run on this release's commit gates the tag.
- Locally the full verify at dev's tip passed 2147 of 2147 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: development builds on the test phone (Android 16) under
mock://: Live's pause, the viewer's panes, cursors and statistics, and the Dashboard at phone width in four looks, then a build from dev's tip with CI's APK: the import picker offered a CSV, its format and column map were guessed, "Imported 25 values" and the recording opened in the viewer, and the viewer's Jump row and Stretches panel fit the phone's width. An import canceled on the phone left no recording, though its note wasn't caught on screen. The first-run words and the other Recordings changes have not been looked at on a phone, and the release APK itself has not been run. - On a car: the extended session ran parked on the test car through two adapters (2026-11-11-ext-session-car): entered, read in and held by tester present. The closes were changed afterward and are tested against the fakes only; a car run of them is planned. The pull rules were tuned against five road logs of one car read through a logger, not a live session.
- 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.3.intoto.jsonl. Check them with the GitHub CLI:
sha256sum -c --ignore-missing SHA256SUMS.txt
gh attestation verify havne-0.7.3-windows-x64.zip -R erickramer42/havne
gh attestation verify havne-0.7.3-android-arm64-v8a.apk -R erickramer42/havne
gh attestation verify havne-0.7.3-linux-x86_64.AppImage -R erickramer42/havne
gh attestation verify havne-core_0.7.3_amd64.deb -R erickramer42/havne
gh attestation verify havne-0.7.3-py3-none-win_amd64.whl -R erickramer42/havne
Those read GitHub's attestation store; add --bundle havne-0.7.3.intoto.jsonl to check against the attached file instead.
The SBOM, havne-0.7.3.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.3-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.