GO Discover time is suddenly incorrect

[ABBAbear]

A week ago, I noticed that the arrival time to my destinations on my GO Discover are suddenly one hour faster than the correct time. I thought this problem would fix itself, but it has now been going on for a week. The same problem occurs on the TomTom GO app on my iPhone. The arrival time for all of my trips is an hour faster than the actual time. I’m not sure what to do or why this suddenly started a week ago. Anyone else seen where the time is incorrect?

 

[canderson]

Does it appear to be off by exactly one hour? By ANY chance do you see a tiny +1 to the right of the arrival time? If so, the device and phone are confused about time zones for some reason.

What happens if you set up a trip that is close enough to your current location such that it should take LESS than an hour? What arrival time is displayed then?

 

[ABBAbear]

There is no +1 indicated next to the times. And yes, they are exactly 1 hour off. And all of my trips that I have been taking since this started are all less than one hour long. My drive home in the afternoon should take 20 to 25 minutes and it indicates that it’s going to take an hour and 20 or 25 minutes, I cannot figure out how to change this time. It seems like it’s gotta be something with Tom Tom servers as that’s where the time is pulling from I guess.

 

[canderson]

There is no +1 indicated next to the times. And yes, they are exactly 1 hour off. And all of my trips that I have been taking since this started are all less than one hour long. My drive home in the afternoon should take 20 to 25 minutes and it indicates that it’s going to take an hour and 20 or 25 minutes, I cannot figure out how to change this time. It seems like it’s gotta be something with Tom Tom servers as that’s where the time is pulling from I guess.

Nope - the time comes from the satellites. What you have is a misinterpretation of your current time zone by the TomTom. It seems to be creating a differential of your current time and the time of all of your destinations of 1 hour in the displayed ETA.

It would be tempting to perform a factory reset just to see if that resolves the issue. Annoying to have to change the device configuration to just the way you like it, though. Do you have your routes and/or favorites, if any, already on the MyDrive web where they will automatically repopulate to your device when it connects again?

 

[Willy875]

There is no +1 indicated next to the times. And yes, they are exactly 1 hour off. And all of my trips that I have been taking since this started are all less than one hour long. My drive home in the afternoon should take 20 to 25 minutes and it indicates that it’s going to take an hour and 20 or 25 minutes, I cannot figure out how to change this time. It seems like it’s gotta be something with Tom Tom servers as that’s where the time is pulling from I guess.

It's just to know your icon which indicates your position would it not be grayed out?

 

[canderson]

It's just to know your icon which indicates your position would it not be grayed out?

Seems he's been making a lot of trips with only the ETA being incorrect, so would have to imagine that he's getting a GPS signal.

 

[Willy875]

The map is installed on the GPS so in my opinion it can navigate from A to B with information that is false.

 

[canderson]

The map is installed on the GPS so in my opinion it can navigate from A to B with information that is false.

Not without a GPS fix. If the chevron is gray, he won't be going very far... and the GPS fix that he evidently has to navigate should be giving him a proper current time.

 

[ABBAbear]

The GO app on my phone has continued to be one hour off but the Discover unit actually had the correct arrival time two nights ago. Then this morning I programmed the Discover and it showed the correct arrival time. I looked away for a minute and the arrival time changed to one hour later.

I don’t really mind doing a full reset as all my stops should be cloud stored in MyDrive. BUT I shouldn’t have to do that as this problem shouldn’t be happening IMO.

 

[Niall]

@ABBAbear I note that you are in Western KY, how close are you to the border between EDT and CDT as defined here https://www.time.gov/
as illustrated here

 

[ABBAbear]

Answering your question, I am in far western KY. BUT... the problem resolved itself last week one day. Suddenly the arrival time was correct. THANKS for all who replied with your help/suggestions.