Temporary PKJS watchPosition() speed feed

robert commented

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

(Migrated from git.butzei.de)

Goal

Give the watchapp real speed immediately, so it is genuinely useful before any Android work exists.

Acceptance criteria

PKJS navigator.geolocation.watchPosition() with enableHighAccuracy: true, maximumAge: 0
Error handler and timeout present on every geolocation call
Speed and position forwarded to the watch using the shared message keys
Distance and average accumulated on the JS side for now
Known limitations documented (background reliability, no BLE sensors)

Files

watchapp/src/pkjs/index.js

Notes

This is scaffolding, replaced by the companion app in Phase 2 and kept only behind a fallback flag.

## Goal Give the watchapp real speed immediately, so it is genuinely useful before any Android work exists. ## Acceptance criteria - [ ] PKJS `navigator.geolocation.watchPosition()` with `enableHighAccuracy: true`, `maximumAge: 0` - [ ] Error handler and timeout present on every geolocation call - [ ] Speed and position forwarded to the watch using the shared message keys - [ ] Distance and average accumulated on the JS side for now - [ ] Known limitations documented (background reliability, no BLE sensors) ## Files - `watchapp/src/pkjs/index.js` ## Notes This is scaffolding, replaced by the companion app in Phase 2 and kept only behind a fallback flag.

robert added a new dependency

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

#7 shared/message_keys.json plus C and Kotlin codegen

robert added a new dependency

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

#21 Retire the PKJS feed behind a fallback flag

robert referenced this issue from a commit

2026-09-05 12:19:20 +02:00

Add temporary PKJS speed feed (issue #13)

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

2026-09-05 12:19:52 +02:00

Temporary PKJS watchPosition() speed feed (issue #13) #110

robert closed this issue

2026-09-05 12:21:32 +02:00

robert referenced this issue from a commit

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

Merge pull request 'Temporary PKJS watchPosition() speed feed (issue #13)' (#110) from area/pkjs-speed-feed into main

robert commented

2026-09-05 12:21:50 +02:00

Owner

Closed by PR #110 (merged). Plain-ES5 PKJS speed feed using watchPosition() with enableHighAccuracy/maximumAge:0/a real 15s timeout, both error and success paths handled (all three W3C PositionError codes send the SPEED_MMS sentinel rather than a stale/fake value). SPEED_MMS/AVG_SPEED_MMS/DISTANCE_M come from PROTOCOL.md section 2.2, hand-copied into package.json's messageKeys since tools/gen_message_keys.py (#7) has no JS output target yet -- flagged as a real, undetected second copy of those three integers, and extending the generator to a JS target is a reasonable follow-up. Deliberately does NOT port SpeedPipeline/StopDetector's real machinery (GPS-quality gating, wraparound, dwell/hysteresis) -- reuses only the 0.8 m/s stopped-speed number, not the class, since this file is scaffolding #21 will delete. Fallback flag: localStorage['pkjsSpeedFeedEnabled'], default enabled since Phase 1 has no other speed source yet.

Real end-to-end verification, a first for a PKJS feature in this repo: pebble build clean on all three platforms, then a live emery emulator run confirmed watchPosition() getting a genuine fix through pypkjs's actual IP-geolocation path, the resulting AppMessage arriving at the watch's C inbox handler, and the ack returning to PKJS -- via pebble logs, not just compiled. Honestly unverified: multi-fix accumulation (pypkjs's watchPosition() fires its success callback only once, an emulator limitation) and the error/timeout path (network never failed in this sandbox) -- both verified by reading the logic instead, stated as such rather than claimed.

Closed by PR #110 (merged). Plain-ES5 PKJS speed feed using watchPosition() with enableHighAccuracy/maximumAge:0/a real 15s timeout, both error and success paths handled (all three W3C PositionError codes send the SPEED_MMS sentinel rather than a stale/fake value). SPEED_MMS/AVG_SPEED_MMS/DISTANCE_M come from PROTOCOL.md section 2.2, hand-copied into package.json's messageKeys since tools/gen_message_keys.py (#7) has no JS output target yet -- flagged as a real, undetected second copy of those three integers, and extending the generator to a JS target is a reasonable follow-up. Deliberately does NOT port SpeedPipeline/StopDetector's real machinery (GPS-quality gating, wraparound, dwell/hysteresis) -- reuses only the 0.8 m/s stopped-speed number, not the class, since this file is scaffolding #21 will delete. Fallback flag: localStorage['pkjsSpeedFeedEnabled'], default enabled since Phase 1 has no other speed source yet. **Real end-to-end verification, a first for a PKJS feature in this repo**: pebble build clean on all three platforms, then a live emery emulator run confirmed watchPosition() getting a genuine fix through pypkjs's actual IP-geolocation path, the resulting AppMessage arriving at the watch's C inbox handler, and the ack returning to PKJS -- via pebble logs, not just compiled. Honestly unverified: multi-fix accumulation (pypkjs's watchPosition() fires its success callback only once, an emulator limitation) and the error/timeout path (network never failed in this sandbox) -- both verified by reading the logic instead, stated as such rather than claimed.

Rows
Columns

Temporary PKJS watchPosition() speed feed #13

Goal

Acceptance criteria

Files

Notes