This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Wrong time and date after GPS sync!

Former Member
Former Member

So this one is a weird issue that few people seem to have. Got a new Instinct Solar Surf edition. Right off the bat, when syncing time with GPS, got the wrong time, date and sunset/sunrise, moorise/moonrise data. Time is set to auto, am in an area with excellent GPS connectivity. When I go outside, start an activity or simply set time  to sync with GPS, I get a weird time for a time zone that is UTC+12.45 and a date that is 48 days in the future (the watch thinks it's Oct. 17 2020!).

Did quite a bit of troubleshooting but no luck: 1. verified am getting a good GPS lock. 2. checked that the GPS coordinates provided by the satellite are OK (my exact location according to other GPS readings + Google Earth). Tried many times - day, night, changing location and even during a 2 h surf session (watch had wrong time and date after more than 2 h of soaking GPS signal with 5 GPS bars showing!). Of course, am running the latest version of the software...etc. through Garmin Connect + also tried multiple resets.

I even tought the watch was a faulty one, so got a new replacement one from the vendor. Still the exact same issue!

So basically, the watch only shows the correct time and date when synced with the phone (am 100% sure of that because I played with the time setting on my phone and the watch displays the phone's changed time when it syncs...). Quite frustrating as I bought the watch to get tide, sunrise, sunset data and moon phase data for surfing but all I have now is a watch that needs to be connected to a phone to show the exact time! For $450, quite a bummer...

Anyways, just trying to see whether someone can help:

1. Is it normal that the watch syncs the time with the phone? Am wondering whether this is not creating confusion within the software. Garmin support on the phone told me the watch syncs time with GPS only not the phone but I have ascertained with 100% certainty it reads the time from the phone (cf. above).

2. What could possibly explain a wrong display of time/date after a successful GPS sync and GPS indicating the correct position? It can't be an issue with the GPS signal - I checked 10 times and I have about 21 satellites overhead (GPS + Glonass), most of them with excellent signal (used a separate phone app to validate that), and am in suburban area with very few obstructions.

3. I saw on the forum that another user had the exact same issue, and surprise surprise, in Morocco as well!

Am not sure how the GPS sync. is implemented in the Instinct Solar. But if I had to guess, the GPS module is probably decoding the GPS signal properly (hard to see how it could not). So could this be an issue with the GPS module getting the proper GPS UTC time from the satellites but then failing to identify the right timezone and by default showing some totally improbable time and date as a result? Where does the Instinct watch look up the proper timezone it should pick up - is this done in  the watch itself based on position (in which case, there could be some coding error) or is this done through the phone where the Instinct Solar attempts to read from the phone what the right time zone is (and possibly try to fetch the date from an incomplete database or failing to read properly from the phone)?

At this stage, am guessing that probably the watch reads the UTC time from the GPS, then attempts to find the right timezone am at (UTC + 1) either in the internals of the watch or through the phone, does not find it and then simply displays a random time and date by default?

Any enlightened views on this? Would immensely help as am not sure when I can leave Morocco (plus, surfing season starting so might as well stay a bit more).

Thanks! Nico.

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    Humm. The plot thickens. Followed your advice / instructions. So the watch did try and get a new gmatz file and installed it. Indeed, it deletes after installation. But that did not solve the issue. I then redid this but changing the gmatz file with the files you kindly shared - so 24 and 22 do not work (i.e., I get the same wrong time and date). In both instances, the watch did install them but the time from the GPS was still wrong. Will try 23 tomorrow morning to see if that works by any chance, but not too hopeful. 

    On the positive side, in the service menu I do get the proper UTC time (now triple checked and sure as I did another reset and did not pair the watch with my phone to be super sure). Ironically enough, I can get the right time (not sure about the date) through the alternative timezone widdget - so the main watch face displays 8.55 AM on Oct. 21, 2020 but the alt. timezone widget gives me the right time for the US East Coast and for the UTC+1 timezone...Really bizarre...

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    Former Member

    hi,

    so, the watch has the correct time, verified in the service menu

    it only refuses to show correct on the watchface

    it shows correct time for some time zones in the alternative timezone widget

    alternative timezone widget corrects the time but not the date

    timezone reinstall does not help

    something is causing the discrapency between internal correct and watchface wrong date

    this watch is behaving identical as the first watch

    not much further to do I guess ?

    am out of ideas at the moment Slight smile

    continue tomorrow Thumbsupbut not hopeful

    happy & safe sporting

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    Thanks so much again! Indeed that sums it! Same here. Going to sleep over it and see whether I can think of something else! Cheers. Super appreciated - really!

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    Former Member

    no problem

    very enlightening journey Slight smile

    happy & safe sporting

  • Hey 2996522.

  • Former Member
    0 Former Member over 5 years ago in reply to sspanak

    Thanks sspanak! Yes, tried that. What happens is that when I do that, I get a GPS lock + correct position, but then it shows the completely wrong time and date. So don't think it's the watch face. Thanks to OnlyTwo, in the service menu, it's clear that the watch has the right UTC time somewhere in its internals. Where it's coming from I don't know since, oddly enough, the watch can also get the proper time from my phone. So am left with 2 hypothesis:

    a) The watch does not properly decode the time and date from the GPS signal. or

    b) There's an issue with the time offset for my location.

    On a) am a bit hesitant: if this was the issue, 1. many more people would have it, but it does not seem to be the case - as mentioned, only found 1 other user reporting the issue, and he happens to be in the same location as me; 2. I spent some time understanding the GPS signal in details - what I understand is that the satellites simply send their time from their atomic clock and their position in space. With 4+ satellites, the GPS module solves for both location and time offset with the receiver watch simultaneously (it's complicated but it's a triangulation). Am not really 100% sure (need to dig more in the details) but I don't think the GPS module can solve for the correct position without knowing the actual time.

    On b) that's my main hypothesis, but then OnlyTwo gave me the right timezone map offsets file (actually, many versions) and when trying all of these, none worked. It could be that that the files are all wrong from my location (just found that the country am stuck in now - Morocco - has played a bit with its timezone in the recent past, but also saw on the gmpatz files version available on Garmin that actually Garmin was aware of that and did release a new version to account for that. As of now, I tried the gmaptz.img files versions 22, 23 and 24 and none works.

    I can't make much more progress as I did not find a way of reading these files (it's a .img file) so could still be that there is is glitch in these - am not sure how the file is set up but must be some lookup of some sort based on position I'd guess and it could be that where I am refers to nothing in the lookup time (I triple checked and it's not like the watch returns the time from a different timezone, it just returns a really super weird time and date).

    I'll pester the Garmin support team....

  • Former Member
    0 Former Member over 5 years ago in reply to trux

    Haha! Maybe!!!! Mystery solved: Area51 is somewhere in Morocco...Who knows, I may get something out of this whole fiasco...But more seriously, am now mostly in the country's capital, which, save for the face masks, seems pretty ordinary...

  • Former Member
    0 Former Member over 5 years ago in reply to Eddy Jones MTB

    Aha. Is your issue of  the same magnitude? Meaning that the watch returns a completely wrong time and date or is it more of a minor offset issue? Interesting...