I'm soooo going to beat yesterday tomorrow (weird 'records')

And so for the 1 EM, 5 K. In milliseconds, this is just about the max value of an unsigned long.

(Un)fortunately, these 'records' did not stick:

Just hoping that this isn't a problem with the internal storage of the watch.

There were some other weird things going on ('new records' every day, all the time, rebooting when connecting to Tempe sensor, some spontaneous reboots at other times). So I'll do a master reset now and install a newer FW (was on 12.00).

0 -- over 4 years ago

Me the OP again (deleted account & created a new one in the course of troubleshooting this).

The watch is just fine. It was caused by syncing. When Device Upload is set to Off, the records from the watch are not sent to Connect (as intended). I just had not expected that they would be deleted (in this weird way) on the watch as a result.

I reset the watch fully, never connected it via phone or wifi again, and it's been working perfectly for two weeks. No spontaneous reboots, unwanted voice prompts or suddenly altered settings anymore either. Maybe there's just not a lot of testing being done for usage scenarios with device upload disabled.