OpenVitals 2.0.2

Released 2026-07-12.

A fix release for the first Flutter version: the numbers a watch records but writes beside the activity rather than inside it, the charts a ride records, and three crashes-or-near-misses reported against 2.0.1.

Fixed

• A walk or run recorded by a watch showed no steps, distance, calories or elevation. A watch writes an activity as a session record carrying little more than a duration, and puts its steps, distance, calories and elevation in separate Health Connect records covering the same window. Reading the session alone therefore reported "Not available" for numbers the watch had in fact recorded - directly above a chart of that same activity's step cadence, and splits that added up to a distance the page refused to show. Those records are now read back over the activity's own window. A device that records speed but no distance at all (a treadmill, some watches) gets a distance derived from its speed, by the same arithmetic the splits already used, so the two can no longer disagree.
• The speed and cadence a ride or run recorded were never shown, and the metrics list advertised figures the activity was never going to have - "Wheelchair pushes" and "Floors climbed" on a bike ride, permanently "Not available". Speed, cadence and heart rate now get their charts, and the list shows a metric when it has a value, or when its absence is worth reporting for that kind of activity. A value that was actually recorded is never hidden: a device that somehow counts steps on a bike ride still gets a Steps row.
• The recording screen left a large empty gap above and below the live dashboard - about a fifth of the screen - which in outdoor mode's black background read as a broken screen rather than a loose one.
• Importing an offline map pack crashed the app. The file picker read the entire file into memory before the import began, so a 205 MB pack against a 256 MB heap ran out of memory before any of our code ran. The same picker feeds the Apple Health import, where an export is routinely gigabytes and never stood a chance either.
• Adding a home-screen widget went wrong three ways: adding a metric widget opened the beverage picker (and vice versa), the picker could crash after a selection, and when it did complete the widget was sometimes never created. All three were one cause - every widget pointed its configuration screen at the app's main activity, so Android handed the request to the already-running app instead of starting the picker.

The app keeps the same package name and signing certificate, so this installs as a normal update.

Distribution flow:

• Codeberg release with signed APK and signed Android App Bundle assets.
• Direct Google Play production upload from the approved Woodpecker deployment.

---

Generated from docs/releases/2.0.2.md. Edit it there; changes made here are overwritten.