Repository navigation
Havne v0.7.2
Havne 0.7.2 is for building your own Dashboard and scripting your recordings: the desktop's gauges on one panel with undo, a Light look for sun, a signal file's dial range and warning levels, Python's exports and health report, and a user guide. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.7.2-windows-x64.zip |
| Linux (x86_64), the app | havne-0.7.2-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.7.2-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.7.2-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.7.2_amd64.deb (Debian, Ubuntu) or havne-core-0.7.2-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.7.2_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.7.2-linux-aarch64.tar.gz |
| Python wheel (Windows x64, Linux x86_64 and arm64, macOS arm64 13+) | pip install havne-0.7.2-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.2-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. - In Settings, tick Developer mode under Advanced, then press the
mock://demopreset on Connection 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)
- Download
havne-0.7.2-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.7.2-linux-aarch64.AppImage. chmod +xit, then run it.- In Settings, tick Developer mode under Advanced, then press the
mock://demopreset on Connection 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.7.2_amd64.deb (./havne-core_0.7.2_arm64.deb on ARM), or unpack havne-core-0.7.2-linux-x86_64.tar.gz (havne-core-0.7.2-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.7.2-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. In Settings, tick Developer mode under Advanced, then press the
mock://demopreset on Connection 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.7.1
The Dashboard
- The desktop's gauges sit on one panel, with hairlines between them as on the phone, and a short gauge fills the empty space under it. The pages are tabs on the panel's upper edge, with a "+" tab in edit mode, and a long row of tabs scrolls sideways, by the wheel too (ADR-0057).
- Undo and Redo in edit mode, at the start of the bar, back to the first change since Edit (at most 50 steps). On the desktop Ctrl+Z undoes and Ctrl+Shift+Z or Ctrl+Y redoes, in edit mode or out of it. A change made from a gauge's panel outside edit mode shows a line for 5 seconds with Undo. A run of steps on one control, a stepper held or a switch flipped, is one Undo.
- A gauge's panel (a long press, or a tap in edit mode) has Remove, and Undo brings the gauge back. Edit mode's remove box draws as a button and stays inside a short cell such as the shift lights.
- A gauge whose value has stopped updating says "no new data" beside its dimmed value. The Number gauge has no status dot; it dims and says so, as every other kind does.
- The built-in layouts show Boost, Lambda and Battery in place of Throttle and Engine load. Boost reads on the demo (
mock://); OBD-II gives no boost value of its own, so on a car the Boost gauge waits for a signal file or a later release that computes it. A layout you've edited keeps its gauges. - Paste is in the "+" cell, beside the "+" while a gauge is copied, and no longer on the bar. Done is at the bar's end, and on a narrow screen Add gauge reads "Add". Edit mode's "Pages" button reads "Page".
- The demo connection reads a battery voltage: about 12.45 V with the key on, a dip while the engine cranks, and the alternator's 14.1-14.6 V once it runs. A Dashboard gauge added for Battery Voltage on the demo or on an OBD-II connection reads on the other too. A battery gauge added before 0.7.2 reads only on the connection it was added on, until its signal is chosen again.
- Holding a gauge opens its menu even when the finger drifts a little while it's held, as a thumb or a finger on a phone in a holder does.
The look
- A Light look, dark text on white for reading the screen in sun, chosen on Settings' Display page. Night still shows over it when it's on, and on Android the status and navigation bar icons turn dark to match (ADR-0058).
- A button that can't be pressed yet, such as Connect while it connects, draws as a dimmed ordinary button in every look, not as a gray block. At night, the red Clear codes buttons on Diagnostics keep their words readable.
On the phone, and the desktop's first screen
- The drive view's gauges fill the screen, and a tap brings the controls up from the bottom with the tab bar, leaving the top row and the status line in view. Start log, Stop log, Mark and Disconnect are there too (ADR-0059).
- Dash's connect list on a phone, and the desktop's Home, which is the same list, show your paired and plugged-in adapters beside the recent addresses, so a first connect takes a tap or two. On a phone, Bluetooth's permission is asked only when you tap Allow there.
- Home on the desktop shows the session once connected, with Dashboard and Disconnect. Its tachometer sweeps once when Home first shows, and stops while Home is hidden or the app is in the background.
- A Log row at the end of Settings' list shows the newest activity line and opens the Log. A connect that fails, on Dash's list or in Settings, offers Show log beside its words. The Log page has a back arrow, and in developer mode its Activity | Frames switch sits under the title so the row fits a narrow screen.
- On Recordings, the signal list stops at five rows, so a swipe above or below it scrolls the page.
Recordings
- The viewer opens onto a recording's chart and signals; what applies to the whole recording (its info, Replay and Save report, the decode choice, the baseline, Compare and the frames check) follows under an "About this recording" heading. Maximized, its side view follows the Values | Frames switch: Frames gives the frames table the page, Values the chart.
- The Export panel has a Cancel button while an export runs: it stops at once and leaves nothing half written.
- Quitting during an import, or while the log viewer writes a health report, no longer waits for it to finish: it stops, and nothing half made is left.
havne-cli import, andhavne-cli healthover a recording, stop cleanly on Ctrl+C, andhavne-cli export,importandhealthover a recording end at once on a second Ctrl+C, with the interrupted end line and exit 1. - A Save report or an export on a phone that fails, is stopped or can't start no longer leaves an empty document where you picked it, and a temporary folder an import or a report left behind is removed at the next start, as an export's was.
havne-cli logno longer ends a short replay with a values count of 0 (or short) in its end line; the recording itself was always whole.
Signal files, Python and the C API
- A signal file can give a signal a gauge: its range and its low and high warning levels, in the signal's own unit.
havne-cliand the Python package report it; the app's dials don't read it yet. A file that uses it needs Havne 0.7.2 or later. - Python writes what
havne-cliwrites:havne.export_pcapng,export_csv,export_folder,estimate_csvandhealth_report, andSession.health_reportfor a connected car. Each long call stops oncancel=or Ctrl+C with nothing left behind, and so doimport_csvandimport_candump.Plugin.requires_coregives the core a plugin needs as (major, minor, patch). - Append-only additions to the C ABI:
ecuio_signal_file_gauge(anecuio_signal_gauge_t),ecuio_plugin_requires_core,ecuio_import_withandecuio_health_export_with.ecuio_exportandecuio_export_withleavereportzeroed but forfailed_classwhen they fail or are canceled.
Documentation
- A user guide, task by task, and a reference of every address and option, each with its default and an example.
The full list is in the CHANGELOG.
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. CI ran green on dev at
f5451218(run 42962863417), and the release pull request's run on this release's commit gates the tag. - Locally the full verify at dev's tip passed 1982 of 1982 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 103 of 103. - On a phone: development builds of this release's code on the test phone (Android 16) under
mock://: the drive view's bottom sheet and Night red in it, Dash's connect list, the Log row, undo, the Light look and the Dashboard's thumb checks. The release APK itself has not been run on a phone. - Not yet run on a car at this release's code: the extended session (
?session=03, ADR-0060) has run only on the fake J2534 driver and the simulated ECU, and a car run is planned. Python's exports and health report have not run against a car either, and the iPhone app has not run on a device. The published downloads themselves haven'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.7.2.intoto.jsonl. Check them with the GitHub CLI:
sha256sum -c --ignore-missing SHA256SUMS.txt
gh attestation verify havne-0.7.2-windows-x64.zip -R erickramer42/havne
gh attestation verify havne-0.7.2-android-arm64-v8a.apk -R erickramer42/havne
gh attestation verify havne-0.7.2-linux-x86_64.AppImage -R erickramer42/havne
gh attestation verify havne-core_0.7.2_amd64.deb -R erickramer42/havne
gh attestation verify havne-0.7.2-py3-none-win_amd64.whl -R erickramer42/havne
Those read GitHub's attestation store; add --bundle havne-0.7.2.intoto.jsonl to check against the attached file instead.
The SBOM, havne-0.7.2.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.2-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.