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

Date of Birth not saving

After a bike ride this morning, I've discovered both the Connect Android app and the Connect website are no longer saving/registering my date of birth.

I was born in 1966 and the closest year I can get to save on either platform is 1970. Measures up some of the performance data, such as VO2 Max. However I can set the correct year of birth on my Forerunner 735.

Any other 'oldies' got this issue?

0 jim_m_58 over 7 years ago

Jan 1 1970 00:00 UTC is the unix/linux epoch. It's when the # of seconds is zero. The way unix/linux track the time is counting seconds since that point, and is often called "unix time". Seems whoever built/tested this was born in 1970 or later :(

0 Bit over 7 years ago

Maybe I'll get that "born at Unix time 0" tshirt after all.. In any case, things are better than last week when I was -95 years young!

0 am50em over 7 years ago

Fixed with this mornings update.

0 Bigaldoal over 7 years ago

Today's update to the Android GC app, (v4.7), and presumably a con current update to the web based Connect application, appear to have fixed the problem as a pre 1970 year of birth is holding on both.

Thanks for everyone's input, help and suggestions.

0 Former Member over 7 years ago

Yep, mine appears to be fixed as well after last nights update.
Only problem I have now is the VO2 thinks I run rather than walk and constantly has me as 'Poor' although I am more active than 99% of other users in my age group (60 - 69).