mirror of https://github.com/meshcore-dev/MeshCore
Browse Source
Bootstrapping companion RTC from contact lastmod time meant that if/when the companion clock strayed into future time because of clock drift, contacts would get a future/corrupted timestamp -- which the companion would happily restore upon reboot. And since the firmware rejects setting time backwards, it could never be fixed even when rebooting, causing the companion clock to ever drift further ahead. Resolves #3050pull/3061/head
3 changed files with 4 additions and 18 deletions
Loading…
Reference in new issue