I own a Bolt v1. In addition to the GPS issues, I noticed that my time switches back and forth between the correct local time and being 1 hour behind (I’m located in Germany and thus, use CEST with daylight savings). Is that related to the GPS issue or is it a separate issue?
1 Like
Problem with all version one units. Wahoo are aware and they are trying to fix the bug
2 Likes
Now that you mention it, I realize that I had an issue which sounds quite similar, yet I am unable to say whether it is related:
After finishing my VO2 max session today, I noticed my ELEMNT display „flipped“ display language from German to English, and later back to German. I found that quite weird but wasn‘t really bothered, but soon after found that my recording was missing - or so I THOUGHT, because I did clearly remember that I saw the ride simmary screen after ending the activity, and looked a bit further: It turned out that for some reason my ride has been recorded with a date of January 4th 2006 (!). I found this out by scrolling over to the beginning of my ride history, and of course with that date it was the earliest ride. And on this occasion I found that also the time of day it has been recorded was 1 hour earlier than the local time - which is where the similarity to your issue lies.
This way I could also find the ride on Strava, download the .fit and correct date and time with fit tools on the internet.
Needless to say that this is also a major annoyance which urgently needs fixing. Not sure if it is really the same or even related issue.
But both, the weird problem with non-functional routing and this I have only experienced just recently with this very firmware.
I really hope these issues get ironed out soon, or otherwise it renders this platform completely unusable!
1 Like
It keeps doing this (see picture) - the activity has been recorded today, August 21 starting 7:31
Language was English this morning. Swichted back to German when restarted and connecting to the companion app BEFORE I started the recording. It also showed the correct time of day during the ride. Obviously that didn’t help to avoid this weird issue
1 Like
comment removed
This behaviour is explained by the root cause of the error being a 10 bit date counter that is reverting to 1024 weeks before the current date. 1024 weeks ago it was January when the is no daylight savings time, whereas we are actually in August and daylight savings time means the time is 1 hr later than it displays on the device.
The Millenium Bug finally strikes!
1 Like