Waykeep v1.0.0-beta.3

Debug-signed installable APK (irreproducible flavor, package com.waykeep.app.debug).

Third beta — GPS acquisition and distance fixes. Highlights since v1.0.0-beta.2:

See what the GPS is doing

• New journal events: gnss_status (satellites visible / used in fix, max SNR, throttled to changes), gnss_first_fix (engine-reported time-to-first-fix) and gnss_assistance (whether the ROM accepted each A-GPS command).
• The status strip and notification now say "Searching for satellites (used/visible)" instead of a generic "Waiting for GPS signal".

Start where you started

• A fresh network location is stored as the provisional first point while GPS is still acquiring, so the first few hundred metres are no longer missing from the track. The first GPS fix connects to it within 1 km; beyond that the segment breaks rather than drawing a long straight line.
• While only that coarse fix exists, the UI says "Approximate location (±N m)".

Standing still is standing still

• A receiver keeps reporting positions while stationary. The chip's own speed uncertainty is now used to detect that (measured here: 0.49 m/s with ±3.18 m/s), those positions are no longer stored, and the distance stays at 0 m. Real walking is unaffected.

Diagnosis behind it

• On 2026-10-31 the app registered with the GPS provider 88 ms after start and received no location callback for 201 s; the accuracy filter rejected nothing. Both A-GPS commands returned accepted=true on the test device and the fix still took 201 s (Codeberg #2410 / PR #2411), so the network-provider start is the practical fix.

Verification

• 62 unit tests, 0 failures.
• Device-verified on a POCO 25028PC03I (Android 15): sitting still indoors → 0.00 m and "Approximate location (±100 m)"; satellites logged as 1–4 visible, 0 used in fix, 22–27 dB SNR; the provisional start connects to the first GPS fix.

Known limitations

• The standing-still filter needs the chip's speed accuracy; on devices that do not report it, drift still counts.
• Debug-signed: Play Store / F-Droid builds need a release keystore.