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

Incorrect time while uploading acitivty

Former Member over 7 years ago

Hello.

I know there are other posts on the subject but I want to add my own to the list as I consider this to be a major inconvenience. As I record an indoor acitivty the time is shown correctly on the Forerunner 235 but as it is uploaded to Garmin Connect the time is abused. This is a problem with Garming Connect forcibly inserting time zone data to the activity and doing a poor job at it. I live in Finland, GMT+2 with daylight saving time currectly being applied. I have selected the upload time zone as GMT+2 EET and my location is set at Finland. Every indoor activity I upload is +1 hours ahead, so If I start recording an acitivty at 20:06, Garming Connect shows 21:06. What makes this really sad, is that the value is subject to change depending on something. As I refresh the web page or the mobile phone client, the time will show 20:06 and the next moment it will show 21:06 and then show 20:06 again few refreshes later. Even manually changing the time is difficult and it will be off by some other view. For example, I managed to modify one activity to show 17:30 correctly on my phone and the web page activities view, BUT when changed to the daily summary view in the web page, the data is way off in the timeline chart.

Is it so difficult just to relay on the Forerunners clock as it is in correct time all the time? Why do you have to manually assume a time zone for the data? Garmin, please fix this. I've rummaged around the forums quite a bit and it is clear that time handling in Garming Connect is an issue.

0 tmk2 over 7 years ago

Is it so difficult just to relay on the Forerunners clock as it is in correct time all the time? Why do you have to manually assume a time zone for the data?

I guess this approach comes from devices that had no GPS and no notion of time zone, like for example the Garmin Swim. For activities regsitered with those devices it was impossible to deduce the time zone, so it had to be defined manually in Garmin Connect. Most modern devices are GPS-enabled and even for non-gps (like indoor) activities could register the correct local time zone, but apparently Garmin didn't bother to support such special case properly.

Garmin, please fix this. I've rummaged around the forums quite a bit and it is clear that time handling in Garming Connect is an issue.

You have put it very mildly by calling it an issue. Garmin's time handling is one huge mess. After seeing unfixed bugs for years, I am quite convinced that they have no idea how to make it right without making things worse.

0 pshare over 7 years ago

Markus,

Since this is your first post, I'm going to assume you're relatively new so I'll ask a basic question. Is your timezone setting in web Connect correct? Check under the profile icon, account settings, display preferences.

Also, how did you set the time on your watch - manually or automatically? Setting it manually can cause all sorts of issues.

0 Former Member over 7 years ago

Hello and thank you for the responses,

You have put it very mildly by calling it an issue. Garmin's time handling is one huge mess. After seeing unfixed bugs for years, I am quite convinced that they have no idea how to make it right without making things worse.

As pshare pointed out, I am new to these forums so I was trying to be tactful.

Markus,

Since this is your first post, I'm going to assume you're relatively new so I'll ask a basic question. Is your timezone setting in web Connect correct? Check under the profile icon, account settings, display preferences.

Also, how did you set the time on your watch - manually or automatically? Setting it manually can cause all sorts of issues.

The Forerunner is set for automatic time adjustment. What comes to the web Connect, I spent one whole evening logging new indroor activities with different time zones selected from the web Connect and received very inconsistent results. GMT+2 EET (Which is the correct time zone) resulted in the closest thing to a correct time with the previously described shifting of time in already saved activities. That really doesn't make much sense as with the other time zones the time wouldn't shift in already saved activities. It would just be wrong. With GMT+2 EET it feels like Garming is trying to discern something on the fly out of the upload time zone data which results in random transponation of the time (+-1h) by random. I will reproduce the bug and post screenshots of it later today.