j14 changed the date to 01/01/2006 by himself
hi, same here, devices changed date to 01/01/2006 and now their location is messed up, some in russia, some in poland and so on
Edit: seems there was a global gps Jam affecting some areas, https://www.flightradar24.com/data/gps-jamming
I got the same problem with WanWay S20. It seems like it is GPS week number rollover problem.
https://en.wikipedia.org/wiki/GPS_week_number_rollover
Date 2006-01-01 is 1024 weeks before 2025-08-17
In my case time is OK, only date is wrong (1024 weeks before now)
hmm, any workarounds or solution?
Did not find any solution yet.
Other devices seems to have this problem also:
https://www.reddit.com/r/cycling/comments/1mssnjl/wrong_date_on_wahoo_activity/
reports not working for devices with different date, no data
i think server needs a small patch for this date issue
Devices still show year 2006 but i fixed my DB to generate reports properly with
UPDATE positions
SET fixtime = DATE_ADD(fixtime, INTERVAL 1024 WEEK),
devicetime = DATE_ADD(devicetime, INTERVAL 1024 WEEK)
WHERE YEAR(fixtime) < 2018;
I think we would need to see some logs to understand what the root cause of the problem is.
Seems like there's a hardware issue with certain chips. See this ticket:
we use time server for gt06 in configuration.
- but it make device with normal date got problem with internal storage (send data FIFO/ first in first out to server)
- device who have internal storage (FIFO) when send data to server, server detect as new data (not old data) so when we playback. many line that we see in map.
All my j14 trackers crashed on the platform and I discovered that the problem was that they all somehow changed to the date 01/01/2006. I can't understand how this happened. I thought it was a problem in the system, but soon after I realized it was the j14 trackers. I would like to know if anyone knows any command to configure the tracker's date? My j16 were normal, only the j14 presented this problem.