GPX ride recording including heart rate

robert commented

2026-08-31 17:14:41 +02:00

(Migrated from git.butzei.de)

Goal

Record the ride so it can be exported and re-imported into komoot or Strava.

Acceptance criteria

Track points written incrementally, so a crash loses at most a few seconds
Heart rate from HR_BPM embedded using the standard Garmin TrackPointExtension namespace
Elevation included where available
Paused segments handled sensibly (separate track segments)
Resulting file validates and re-imports into komoot cleanly

Files

companion/.../ride/GpxRecorder.kt

Update — 2026-09-01: heart rate arrives batched, and gaps stay gaps

Heart rate now reaches the phone as a batched HR_SAMPLES message every 5 s, with a watch-side
buffer that survives a Bluetooth dropout (#66, D31).

Decode batched samples using their base_timestamp, not arrival time — a drained backlog is
minutes old and must land at the right point in the track
Dropout gaps written as gaps, never interpolated
Backlog arriving after the ride has been paused or stopped still lands correctly

## Goal Record the ride so it can be exported and re-imported into komoot or Strava. ## Acceptance criteria - [ ] Track points written incrementally, so a crash loses at most a few seconds - [ ] Heart rate from `HR_BPM` embedded using the standard Garmin TrackPointExtension namespace - [ ] Elevation included where available - [ ] Paused segments handled sensibly (separate track segments) - [ ] Resulting file validates and re-imports into komoot cleanly ## Files - `companion/.../ride/GpxRecorder.kt` ## Update — 2026-09-01: heart rate arrives batched, and gaps stay gaps Heart rate now reaches the phone as a batched `HR_SAMPLES` message every 5 s, with a watch-side buffer that survives a Bluetooth dropout (#66, D31). - [ ] Decode batched samples using their `base_timestamp`, not arrival time — a drained backlog is minutes old and must land at the right point in the track - [ ] **Dropout gaps written as gaps, never interpolated** - [ ] Backlog arriving after the ride has been paused or stopped still lands correctly

robert added a new dependency

2026-09-03 19:01:17 +02:00

#15 Foreground location service: permissions, notification, battery exemption

robert added a new dependency

2026-09-03 19:01:23 +02:00

#47 Export and share the recorded ride GPX

robert referenced this issue from a commit

2026-09-05 12:34:35 +02:00

Record rides to GPX, including HR embedding capability (issue #20)

robert referenced this issue from a pull request that will close it,

2026-09-05 12:35:09 +02:00

Record rides to GPX, including HR embedding capability (issue #20) #111

robert closed this issue

2026-09-05 12:36:27 +02:00

robert referenced this issue from a commit

2026-09-05 12:36:28 +02:00

Merge pull request 'Record rides to GPX, including HR embedding capability (issue #20)' (#111) from area/gpx-recording into main

robert commented

2026-09-05 12:36:44 +02:00

Owner

Closed by PR #111 (merged). GpxWriter (pure, :companion:core) writes incrementally, embeds heart rate under Garmin's real TrackPointExtension/v1 namespace and element shape (verified against the published XSD, BeatsPerMinute_t enforced as a real range constraint), and GpxRecorder turns MovementState.STOPPED/MOVING transitions into real track-segment seams -- a stop closes the current trkseg, the first moving fix after opens a new one.

Honest gaps, not silently faked: elevation support is fully built and tested in GpxWriter/GpxRecorder, but GpsFix/LocationFix (#17/#19) carry no altitude field at all despite Location.getAltitude() existing on the platform -- a real, separate gap flagged for those types, not fixed here. HR stays nullable end-to-end since nothing in companion/ produces a live bpm yet (confirmed via grep) -- the capability is real and tested, just unfed, matching #65's own pattern.

Real round-trip validation: a two-segment, elevation+HR-bearing recording written by GpxWriter and re-imported through the project's own GpxImporter (#24), asserting lat/lon/elevation/timestamps match exactly -- a genuine consistency proof between the read and write sides, not just well-formed-XML checking.

Verified for real: ./gradlew :companion:core:test (20 new tests, 0 failures), ./gradlew :companion:assembleDebug (RideService/RideGpxFiles Android wiring compiles).

Closed by PR #111 (merged). GpxWriter (pure, :companion:core) writes incrementally, embeds heart rate under Garmin's real TrackPointExtension/v1 namespace and element shape (verified against the published XSD, BeatsPerMinute_t enforced as a real range constraint), and GpxRecorder turns MovementState.STOPPED/MOVING transitions into real track-segment seams -- a stop closes the current trkseg, the first moving fix after opens a new one. Honest gaps, not silently faked: elevation support is fully built and tested in GpxWriter/GpxRecorder, but GpsFix/LocationFix (#17/#19) carry no altitude field at all despite Location.getAltitude() existing on the platform -- a real, separate gap flagged for those types, not fixed here. HR stays nullable end-to-end since nothing in companion/ produces a live bpm yet (confirmed via grep) -- the capability is real and tested, just unfed, matching #65's own pattern. Real round-trip validation: a two-segment, elevation+HR-bearing recording written by GpxWriter and re-imported through the project's own GpxImporter (#24), asserting lat/lon/elevation/timestamps match exactly -- a genuine consistency proof between the read and write sides, not just well-formed-XML checking. Verified for real: ./gradlew :companion:core:test (20 new tests, 0 failures), ./gradlew :companion:assembleDebug (RideService/RideGpxFiles Android wiring compiles).

robert referenced this issue from a commit

2026-09-05 17:04:48 +02:00

Export and share the recorded ride GPX (issue #47)

robert referenced this issue

2026-09-05 17:05:12 +02:00

Export and share the recorded ride GPX (issue #47) #112

robert referenced this issue

2026-09-05 17:06:16 +02:00

Export and share the recorded ride GPX #47