Repository navigation
Havne v0.7.1
Havne 0.7.1 is for the phone in the car: a drive view that shows your gauges to the screen's edges with every bar hidden, Night as a one-tap switch in amber or red, a flatter look in Barlow type, and the Recordings viewer's Export, which saves a whole recording scrubbed through the system's pickers. Read DISCLAIMER.md before connecting it to a vehicle.
Downloads
| For | Download |
|---|---|
| Windows (x64) | havne-0.7.1-windows-x64.zip |
| Linux (x86_64), the app | havne-0.7.1-linux-x86_64.AppImage |
| Linux (64-bit ARM: a Raspberry Pi 3 or later), the app | havne-0.7.1-linux-aarch64.AppImage |
| Android 12 or later (64-bit ARM) | havne-0.7.1-android-arm64-v8a.apk |
Linux (x86_64): havne-cli and core alone, for your own programs |
havne-core_0.7.1_amd64.deb (Debian, Ubuntu) or havne-core-0.7.1-linux-x86_64.tar.gz |
Linux (64-bit ARM): havne-cli and core alone |
havne-core_0.7.1_arm64.deb (Raspberry Pi OS, Debian, Ubuntu) or havne-core-0.7.1-linux-aarch64.tar.gz |
| Python wheel (Windows x64, Linux x86_64 and arm64, macOS arm64 13+) | pip install havne-0.7.1-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.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 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.1-linux-x86_64.AppImage, or on 64-bit ARM (a Raspberry Pi 3 or later on a 64-bit system)havne-0.7.1-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.1_amd64.deb (./havne-core_0.7.1_arm64.deb on ARM), or unpack havne-core-0.7.1-linux-x86_64.tar.gz (havne-core-0.7.1-linux-aarch64.tar.gz) anywhere.
Android 12 or later (64-bit ARM)
- On the phone, download
havne-0.7.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. It opens on Dash: with no session, Dash lists the addresses that connected before, or Connect... opens Settings. In Settings, tick Developer mode under Advanced, then press the
mock://demopreset on Connection and Connect. Back on Dash, Drive shows the gauges full screen; a tap brings the controls back.
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.0
On the phone
- A drive view. Drive on the Dash page shows the gauges to the screen's edges, with the system's bars hidden and a one-line status. A tap brings the controls back for 2, 4 or 8 s, or until tapped away, as set under Settings, Display, where Android also sets which way the view holds the screen. It keeps the screen on, and comes back by itself the next time a session connects on Dash (ADR-0059).
- The tab bar has five labeled tabs: Dash, Live, Codes, Recs and Settings. Tap the status in the top bar for the Log. With no session, Dash lists the last five addresses that connected, replays and the demo left out, ready to connect.
- The Dashboard is laid out on 6 columns upright and 12 on its side, its gauges one flat panel with thin lines between the cells, and a gauge shorter than its neighbor fills the empty space under it. A layout you have already edited keeps its shape. Its tools share one row (Drive, Reset peaks, Edit and the Night switch), and the tab bar and top bar take the place of the page's title and link line.
- Android's Back reaches the app: it closes a Settings page, closes an open recording to the list, closes a Dashboard gauge's panel and then edit mode, and returns from the Log, or from Connection opened through Other address... or by a refused Replay, to where it came from. The screen stays on while connected, on external power or with Dash showing.
- Settings' title row stays while a page scrolls, with a back arrow at its left.
- With an accessibility service on, such as a screen reader or a password manager, Havne could stop answering for minutes after you left the Dashboard and came back during a session. Each gauge now reads as one line, its name, value and unit.
Night, and the look
- Night (Off, On or Scheduled) and a Night style (Amber or Red), under Settings, Display, in place of the Low glare and Night themes; a stored theme carries over. The Dashboard has a one-tap Night switch that, under a schedule, holds the opposite until the schedule's next boundary (ADR-0058).
- Neutral graphite with a light accent, squarer corners, flat gauge cards and Barlow type, with fixed-width digits for readings. Dials have no bezel and draw larger; needles, bars and traces are one flat color. Buttons have four ranks, and text fields and check boxes share one look; on a phone they and the Recordings page's controls are a touch's size. Blue appears only where it means cold, and one vocabulary runs through the app: "address", "Disconnect" and "No session".
Dashboard editing
- Press and hold a gauge, in or out of edit mode: let go for its menu (signal, size, Copy, Paste after), or move to drag it to a new place. Gauges copy and paste across pages, and a blank cell in Add holds a spot open (ADR-0057).
- A tall Digits gauge puts its unit under larger, centered digits, and takes its digit count from its range unless one is set.
Recordings and the analysis log
- Export in the Recordings viewer saves the whole recording as a CSV (wide or long), pcapng or a folder copy, scrubbed, with the file's size shown beside each row interval before anything is written, through the system's file and folder pickers (ADR-0056).
havne-cli export --format csv --estimateprints the rows and bytes without writing a file. - Replay connects in one tap and lands on Live, or on Settings with the reason when core refuses the recording. It reads "Disconnect to replay" while connected and "Stop the relay to replay" while the relay runs.
- The analysis log takes a minimum time between sweeps, for a slow adapter or a busy ECU: Settings' Advanced page,
havne-cli log --min-sweep <ms>and Python'sset_focus(signals, min_sweep_ms=...). - Quitting the app during a long export, or Android closing it, stops the export and leaves nothing half written;
havne-cli exportstops cleanly on Ctrl+C.
The extended session, for uds-generic
- Add
?session=03to the address and Havne asks each module to enter the extended diagnostic session before reading, keeps it there while it reads, and returns it to the default session at the end. A module that refuses is read in the default session, and the Log page,havne-cli'ssessionline and Python say which session each module was read in. Nothing but reads and the session's own requests is sent in it (ADR-0060).
For programs
- Append-only additions to the C ABI:
ecuio_session_set_focus_with,ECUIO_SESSION_INFO_REQUESTS,ecuio_export_withandecuio_export_estimate_with(an export and its sizing that a cancel can stop), and the session fields ofecuio_channel_support_t. A CMake consumer that uses them asks forfind_package(ecuio 0.7.1). - Python's
havne.Pluginloads a packed plugin file; it raisedArgumentError.
Fixes
- Imperial units show bar as psi. A SocketCAN session that asks requests no longer keeps a CPU core busy between reads. The Dashboard says only "Log ended" when your own Disconnect ends a log, and gives a reason for an end you didn't ask for. An export the app was closed in the middle of leaves no temporary copy: the next start removes it once it is a day old. A Shift lights gauge's Lights box shows the number of lights it draws, and a Number's trace keeps drawing when its signal gives a value that isn't a number. With no session, a gauge's signal list follows the profile chosen in Settings. Settings no longer brings back a replay or the demo (
mock://) as the address at the next start, and Dash's recent addresses leave both out (Recordings is a replay's way back); one an earlier version stored is dropped. 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. On Windows the suite is 1931 cases, all passing but six that need the cross-arch step, the car's raw recordings, Linux or Wireshark's
tshark, and the cross-arch cases pass through the x86 helper too. - On a phone: a development build on the test phone under
mock://: the drive view in both navigation modes, the Dashboard's panel and editing, Night, the Export through the document picker, and the accessibility fix with a service on. - Not yet run on a car at this release's code: the drive view, the minimum time between sweeps, the extended session (run against the simulated car only) and the viewer's Export; the iPhone app 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.1.intoto.jsonl. Check them with the GitHub CLI:
sha256sum -c --ignore-missing SHA256SUMS.txt
gh attestation verify havne-0.7.1-windows-x64.zip -R erickramer42/havne
gh attestation verify havne-0.7.1-android-arm64-v8a.apk -R erickramer42/havne
gh attestation verify havne-0.7.1-linux-x86_64.AppImage -R erickramer42/havne
gh attestation verify havne-core_0.7.1_amd64.deb -R erickramer42/havne
gh attestation verify havne-0.7.1-py3-none-win_amd64.whl -R erickramer42/havne
Those read GitHub's attestation store; add --bundle havne-0.7.1.intoto.jsonl to check against the attached file instead.
The SBOM, havne-0.7.1.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.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 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.
- The Barlow typeface, bundled in the app under the SIL Open Font License 1.1.