Repository navigation
Beta v0.4.0
opendash 0.4.0 — a recording that is not cut, and the first output worth commanding
Context: four days, 21 to 25 September 2026, on top of 0.3.0. Four commits in
opendash, three inopendash-plugins, four inscanmatik-bench. One session at the
vehicle — an Opel Astra J 1.7 CDTI (A17DTJ, Denso ECU) — to declare the new round and
sweep the EGR valve against the oxygen sensor, followed by the drive that tested
everything: 160 km, two hours and eight minutes, 20.3 million readings, one file,
with the engine switched off for a refuel in the middle.Theme: 0.3.0 said of its recording fixes that "the next long drive is the test".
That drive happened. This release is what it took for the drive to pass, and for the
app to open the file afterwards.Deliverable:
android-arm64-v8a-release.apk, versionCode 4, versionName 0.4.0,
minSdk 26, three languages (en/es/de). Signed with the same key as 0.3.0, so it installs
over it and keeps its data. From this version on, the app finds and installs its own
updates.
1. The headline
| 0.3.0 | 0.4.0 | |
|---|---|---|
| Engine switched off mid-recording | the run gave up after three revivals | resumes on its own, same file |
| Opening a two-hour recording | the app closed | opens, 78 MB of memory |
| Actuators | a list with a padlock | their own screen, gated by risk |
| Updates | download by hand from GitHub | offered by the app |
2. A recording that is not cut
0.3.0 closed with two recordings that had died, at 65 and at 32 minutes, and two fixes that
were certain to help without being a cause that is understood. Instead of looking for
the one cause, this release removes every way a recording could end that is not the user
pressing stop:
- Frames a request reads past are kept for the stream reader. Every polled
parameter, heartbeat and declaration used to throw away the packets that arrived while
it waited for its own answer. - The run ends only after twenty minutes without a single frame, never after a count
of attempts. Three revivals per run was not enough for a long drive, and an engine
switched off to refuel is exactly a module that goes quiet for minutes and comes back.
The link is retried on the same clock. - Heartbeat every second from the reading thread, and silence detected after two
seconds instead of three. - One bad slice no longer ends a run. It is reported and skipped.
- The file is written on its own thread. A content provider that blocks could hold
up the thread that sends the heartbeat, and the module drops the session about five
seconds after the last one. A failed write now carries on in a new file instead of
ending the recording. - The recording belongs to the process, not the screen. A rebuilt or reclaimed
activity — a rotation, the system reclaiming memory with the screen off — used to stop
it. - A high-performance Wi-Fi lock beside the low-latency one, which does nothing with
the screen off.
The test: Coruña to Cangas on 24 September, 2 h 8 min, 20.3 million readings in a
single file. Halfway, the engine was off for 221 seconds at a petrol station; when it came
back the app declared the packets again and kept writing to the same file. Nobody touched
the phone.
3. And a recording that opens
That file then closed the app when it was tapped. Twenty million readings across 33
channels, twelve bytes each and twice that while an array grows, is past what Android
gives an app.
Each channel now keeps at most 50 000 points, thinned as the file is read. A chart on
a phone is a few hundred pixels wide, so that is still more than a hundred points per
pixel. It keeps the extreme of each stretch, not whichever reading happens to fall on
a stride. A boost peak, a rail dip or the limiter is usually why the file is being opened,
and striding throws exactly those away.
The file is also streamed from storage instead of loaded whole first. Measured on the
drive above with the memory capped at 256 MB: 1.27 million points kept, 78 MB used.
The summary still counts the file's readings, not the ones kept. If memory runs out
anyway, the screen says so instead of closing.
4. Actuators, behind a gate that grows with the risk
Actuators have their own screen, reached from the Live header. The list comes from the
catalogue (actuators.tsv), so a newly captured command is a row in a plugin, not a
release. Each row carries what it does, when to use it, how, and what can go wrong.
| Tier | What it takes |
|---|---|
| Harmless — horn, wipers, door locks, lamps, gauge sweep | fingerprint |
| Low — EGR valve, window, cooling fan, glow plugs | the warning read, fingerprint |
| Engine | + a checklist, 0 km/h read from the car before every command, the screen lock instead of a fingerprint |
| Learn / reset | + the actuator's name typed, ten seconds' wait |
| Do not touch | + a sentence typed, thirty seconds, and the screen lock again before every command |
A held output is released when the panel closes, and AE 00 (give everything back to
the module) is never behind any gate. Requests are serialized across threads, so a
command works while the live view keeps streaming. The panel charts what the live view is
reading, so you can see the effect of a command: EGR against air flow, rpm and fuel.
One row is commandable today: the EGR valve (CPID 0x1C, 0–100 %), verified at the
car. The Opel catalogue lists 44 outputs across the five tiers. The rest are shown with
their warnings but can't be commanded yet: their command numbers are in the
manufacturer's own data package, and each one gets a button once it has been tried at the
car.
5. What is being recorded, from outside the app
- The notification says it: rows written, rate, and the last problem, if there was
one. - A Mark button, on the notification and on the Live header, writes a marker row into
the recording, to find later the moment something happened without stopping the car to
write it down.
6. Updates from inside the app
Ported from Rustify. On start, and from Settings → About, the app asks GitHub for this
project's releases, including betas. It compares versions numerically and downloads the
APK for the phone's architecture. If more than one installer is on the phone, it lets you
choose which one opens it. The check can be turned off.
This is the first version that has it, so 0.3.0 cannot find 0.4.0 by itself. Install
this one by hand; the next one will be offered.
7. The rest
- Live header in two rows. On a phone held upright, the module name got whatever the
header had left over, which was nothing. It now has its own row and opens the setup
when tapped. - A catalogue whose profiles changed replaces its presets on update. Before, the new
profile arrived and the old copy stayed in the list. - Host tests for the new parts: the recorder writing on its own thread and recovering
from a failed write, version comparison and APK choice for updates, the actuator table,
and a spike that must survive thinning four times over the cap. 35 in total. - No dependency changes.
8. Upgrading
- Install this APK by hand once. It goes over 0.3.0 and keeps presets, scans and
recordings. - Update the
opel-vauxhallplugin. It brings a new single-round profile — 33
magnitudes, 49 of 49 bytes, nothing rotating — and the actuator table. Its presets
replace themselves; apply the profile again if it was the one in use.
Measured against an Opel Astra J 1.7 CDTI (A17DTJ): the new round and the EGR sweep with
the car parked on 24 September 2026, and the 160 km drive that evening, recorded through
the app in one file of 20.3 million readings. Release APK built from the tagged commit and
checked against 0.3.0's signing certificate.