Repository navigation
Havne v0.4.1
Havne 0.4.1 is a patch: its pages fit a phone, upright or on its side, with the chart able to take the whole page, and replies through a J2534 adapter reach the session as they arrive. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.4.1-windows-x64.zip |
| Linux (x86_64), the app | havne-0.4.1-linux-x86_64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.4.1-android-arm64-v8a.apk |
Linux: havne-cli and core alone, for your own programs |
havne-core_0.4.1_amd64.deb (Debian, Ubuntu) or havne-core-0.4.1-linux-x86_64.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
- Download
havne-0.4.1-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 Display, then press the
mock://demopreset 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, glibc 2.39 or later: Ubuntu 24.04 and newer, Debian 13, Fedora 40 and newer, Arch)
- Download
havne-0.4.1-linux-x86_64.AppImage. chmod +x havne-0.4.1-linux-x86_64.AppImage, then run it.- In Settings, tick Developer mode under Display, then press the
mock://demopreset 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.4.1_amd64.deb, or unpack havne-core-0.4.1-linux-x86_64.tar.gz anywhere.
On ARM Linux (a Raspberry Pi, aarch64) there is no download yet (0.5.0 brings them): the core and havne-cli build from source (docs/development.md), as they did on the Raspberry Pi 3 under "What's verified".
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.4.1-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 Display, then press the
mock://demopreset 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.4.0
The pages on a phone
- Denser pages: on a phone, upright or on its side, and in a window as small, margins, spacing, buttons, the toolbar and the sidebar shrink and Live's rows are shorter, so more of each page fits at 100 %. Upright, the Dashboard's tachometer and speedometer sit side by side.
- The chart takes the page: Live's chart and the Recordings viewer's fill the page at a press of Chart, a double-click or
F, and give it back the same way; on a phone on its side they start that way. The viewer then shows the values at the cursor once you tap one, beside its chart, or below it on a page taller than wide (a phone upright), and a button folds them away and opens them again, kept between runs. A handle below Live's list, and one below the viewer's chart, sets each part's share, kept between runs. - A pinch on Live's chart, or the mouse wheel over it, steps its window: fingers spreading show less time, closing show more.
- Charts that hold still: a noisy trace's peaks stay where they are as Live scrolls and as the viewer pans, instead of shifting at every update.
- Log rows copied: the Log page's frame table copies the rows you pick, a tap or a shift-click, with Copy or
Ctrl+C(Cmd+Con a Mac), as tab-separated lines with a header. Paused, it says where new frames still go. - In developer mode, a corner badge counts the frames the window draws each second.
Listening beside another tester
- An ELM327 session that only listens (
?profile=raw) turns the adapter's flow control off, so it never answers another tester's first frame with one of its own. Through an OBDLink MX+ it hears only replies that fit in one frame (STATUS.md's Known Issue #41).
Fixes
- Through a J2534 adapter, replies reach the session as they arrive: on the OBDX Pro VX a reply that took longer than 10 ms came about 50 ms late, and the others waited out the rest of a 10 ms read. A read that fails right after frames were lost reports the failure at once, and messages a driver returns beyond those asked for count as lost.
- A tap on the viewer's chart puts the cursor on the nearest sample of the first signal plotted, with a dot on each trace at the sample its value comes from, so the value read always matches the line.
- The viewer zooms a notch per notch of a high-resolution wheel or a touchpad, a sideways scroll doesn't zoom it out, and on a phone a double-tap on a chart lands when the two taps fall a little apart, and when the viewer's chart has the page and takes a moment to draw. On a phone upright, Live's 120 s button stays on one line.
- For bench and car sessions: with
ECUIO_SUR_LOG_FRAMES=1, the J2534 session log gives each driver read its own line, with how long the driver held it (docs/j2534.md). - 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, the load test on Windows and Linux, and a check of the C ABI and its headers' declarations against 0.4.0's; a GCC or Clang warning fails it. The Android and iOS apps are cross-built there; their tests don't run on a device. On Windows the suite is 1018 cases, all passing but two that need a local build tree or the car's raw recordings, and the 101 cases of the 32-bit driver path pass through the x86 helper too.
- On Linux bare metal: an x86_64 desktop with Ubuntu 26.10 and a Raspberry Pi 3 (aarch64, Kali Linux), each building with no warnings: the whole app's suite (877 cases) on the desktop and the core's (728) on both, passing but for the locale case and the real-car recordings' diff; on
vcan0with the kernel's ISO-TP, the simulated bus's 63 cases but for the one that needs root, andhavne-cliend to end on both: a replay, the mock car played onto the bus and heard, and the simulated ECU answering anobd2session while it recorded, the recording then passinginfoandview(docs/linux.md). - Against the fakes: a J2534 read through the fake as the VX ends at its reply, 6.7 to 7.2 ms after a request answered in 4, and never asks the driver to wait 0 ms.
- One reply on two clocks: two recordings of one virtual bus line up to about 0.3 ms on one machine, and on a desk bus the VX's recording of the simulated ECU's replies against Linux's
candumpto 10.4 ms at the median, the adapter's delivery and the two clocks' offset together (2026-11-04). - On the test car (a development build from before this release's J2534 and listening changes): both of the car's ECUs in one session, through the VX over J2534, each ECU's requests waiting only for their own replies, and through the OBDLink MX+ on the test phone, taking turns; recorded by the laptop's app, the phone's and
havne-cli, each recording's check clean; the MX+ and an Innomaker USB2CAN under SocketCAN listening beside the VX, the run that found what this release changes (2026-11-04). - The VX's latency, on the test car again: through the VX over J2534 on this release's J2534 changes, the latency per request at the median is 16.4 ms with packing and 4.6 ms without, where 0.4.0's car run measured 65.5-73.7 ms packed; each driver read held a median under 1 ms (2026-11-05).
- Listening beside another tester, on the test car again: through the OBDLink MX+ on the test phone, beside the VX asking, a listening session hears Single Frame replies only. The adapter's monitor misses every frame that follows another within about 1 ms, so a reply longer than one frame never completes; turning its flow control off, as 0.4.1's listening setup does, and six more setups tried through the phone's relay changed nothing, and the bus carried the frames (2026-11-05). A SocketCAN controller in listen-only mode hears them in full (Known Issue #41).
- On the test phone (Android 16, a development build): every page fits upright, the Dashboard's dials side by side, the chart taking the page on its side, a pinch, the splitters, and pausing and copying Log rows, and the viewer's values at the cursor beside its chart on its side and in a band below it upright, folding away and back, each tried by hand, with the badge reading 44 to 121 frames a second on Home and the Dashboard while they moved.
- Not yet run: 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.4.1.intoto.jsonl. Check them with the GitHub CLI:
sha256sum -c --ignore-missing SHA256SUMS.txt
gh attestation verify havne-0.4.1-windows-x64.zip -R erickramer42/havne
gh attestation verify havne-0.4.1-android-arm64-v8a.apk -R erickramer42/havne
gh attestation verify havne-0.4.1-linux-x86_64.AppImage -R erickramer42/havne
gh attestation verify havne-core_0.4.1_amd64.deb -R erickramer42/havne
Those read GitHub's attestation store; add --bundle havne-0.4.1.intoto.jsonl to check against the attached file instead.
The SBOM, havne-0.4.1.spdx.json, is attested to the zip, the APK, the AppImage, the deb and the tarball: 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.4.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.