Date of Birth not saving

RE: Date of Birth not saving

Former Member — Sat, 02 Jun 2018 12:24:48 GMT

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).

RE: Date of Birth not saving

Bigaldoal — Fri, 01 Jun 2018 20:37:34 GMT

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.

RE: Date of Birth not saving

am50em — Thu, 31 May 2018 21:10:24 GMT

Fixed with this mornings update.

RE: Date of Birth not saving

Bit — Wed, 30 May 2018 09:06:31 GMT

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!

RE: Date of Birth not saving

jim_m_58 — Tue, 29 May 2018 12:49:41 GMT

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 :(

RE: Date of Birth not saving

Bit — Tue, 29 May 2018 11:47:52 GMT

I can enter a b'date < 1-1-1970 in the user settings under Device Settings, but not in the overall user settings in the user profile. That takes only dates later than 1-1-1970, and that date then overrides the date under the Device Settings, which is synced to the devices and messes up every calculation that uses the DOB. Currently have to enter DOB in all the devices' settings and leave the overall-userprofile-DOB alone, then the devices will work correctly.
Edit: never mind, apparently the order in which you change things in the mobile app and/or the web inteface affects the net results after syncing. No idea what the logic is.

RE: Date of Birth not saving

Former Member — Tue, 29 May 2018 07:38:46 GMT

.....hang on. Garmin connect on line now thinks I'm 40 - 49 despite entering correct birthday. Garmin mobile app works OK. Hopefully will catch up with itself.

RE: Date of Birth not saving

Former Member — Tue, 29 May 2018 07:36:48 GMT

My date of birth now accepted. Had to go to online and enter birthday again, but once I did that it accepted that I was 61 and not 16!

RE: Date of Birth not saving

Former Member — Mon, 28 May 2018 14:38:33 GMT

Just to say that in my case (edge 820 and F5) it took me a while, but then I realised that setting the age needs to be done on GC web, for each device, in the settings page reached from "devices and sync status", under the user settings tab. The phone GC app will not take changes, and something gets messed up if they don't match.
My suggestion would be to have birth date under the user account, instead of under the devices, because the logical assumption is that a user's age does not change whether he/she has one or several devices.
Anyway, once I had made sure both the edge, and the F5 device/user settings had my correct birthdate, there was no issue anymore, I've synced several times since, and it's all stable.

RE: Date of Birth not saving

Bit — Thu, 24 May 2018 20:41:03 GMT

I added a Forerunner 935 to my Connect account and set all user settings for it; DOB 1-1-1970. There was already an Epix in use that had my correct birth year (< 1970). After syncing, the user settings on the Forerunner listed birth year 2113.

RE: Date of Birth not saving

Former Member — Wed, 23 May 2018 01:50:38 GMT

This is happening to me too! My VO2 max went from superior to poor because the app thinks i’m 16 instead of 65!! Also Intensity minutes are not saving for Mondays.

RE: Date of Birth not saving

Bigaldoal — Mon, 21 May 2018 20:26:05 GMT

The Garmin Support Centre have acknowledged that the issue we've all experienced did exists and have passed it onto their Software Engineers. How long a resolution will take I haven't been told though I suppose that's to be expected, however it's good to know they agree there is a problem.

If I hear anything I'll let you know though I suppose we may only see a fix once there's an update to the apps and website.

RE: Date of Birth not saving

Bit — Mon, 21 May 2018 09:27:22 GMT

For now I've entered 1-1-1970, the "oldest" the app allows. So using this app can be rejunevating. And it's sortof an honour to be born at Unix time 0. Always wanted this t-shirt with a positive number on it: https://geeksta.net/tools/born-at-unix-time/
Joking aside, I hope it will be fixed soon!

RE: Date of Birth not saving

Former Member — Mon, 21 May 2018 08:57:47 GMT

The Same here. I wasn't able to save my date of birth. Set date works without any problem, but after leaving the date-setting the date wasn't shown and on reentering the date-setting i saw May 2002 as date again.

RE: Date of Birth not saving

Former Member — Sat, 19 May 2018 13:25:38 GMT

I have the same problem.
Before 1970.01.02 I am not able to set birthday.

RE: Date of Birth not saving

Bigaldoal — Wed, 16 May 2018 08:00:42 GMT

I was contacted by Garmin Support yesterday and sent them through a couple of files, hopefully they'll be able to sort out out. I'll send them through a link to this thread as well so they can take on board everyone's experience.

Will keep you updated.

RE: Date of Birth not saving

Former Member — Tue, 15 May 2018 19:50:57 GMT

Exactly the same for me. Cannot enter anything to do with date of birth.....God knows why. When I try to edit my profile via pc the little drop down menus just Don't work. My watch (forerunner 230) has correct details but won't synch with phone.

RE: Date of Birth not saving

Former Member — Mon, 14 May 2018 13:56:46 GMT

I managed to roll back to v4.5.1 as 4.6.3had the same problem. I will leave it there until they fix the issue. I had to use the program that I got from the APKPURE.com is site - use at your own risk as I am not sure that it is completely good but I have not seen anything bad about it.

RE: Date of Birth not saving

Former Member — Mon, 14 May 2018 12:43:56 GMT

Entering the correct date in the web works until you open connect on your phone - which wipes it out again. The phone app needs to be fixed. If I could roll it back or stop auto updates on that app I would as it often breaks something and there is little indication that a fix is in progress. I love the features of Garmin but they really don't test their software updates well - we are all their test subjects. Overall though it is a great product when it is working right.

RE: Date of Birth not saving

Former Member — Sun, 13 May 2018 19:54:09 GMT

Same thing for me - 735XT and Garmin Connect 4.6.4 Sadly they consistently seem to botch an upgrade but there is no way to roll it back until it is fixed so we will have to wait it out again. I was able to enter the correct date in the web interface but whether or not it will keep it is unknown for now.

RE: Date of Birth not saving

Djij — Sun, 13 May 2018 07:20:47 GMT

Same issue F5S 8.0, GConnect 4.6.4.

RE: Date of Birth not saving

Bigaldoal — Fri, 11 May 2018 22:25:59 GMT

Glad it's not just me. I emailed Garmin Support just after initially posting this, so hopefully they'll come back to me soon.

I'll update you if they do.

RE: Date of Birth not saving

a1a2 — Thu, 10 May 2018 21:04:40 GMT

Me too

RE: Date of Birth not saving

Former Member — Thu, 10 May 2018 12:37:10 GMT

I have the same problem after a recent GCM update, can't enter a DOB before 1/1/1970. The only difference I can see is that GCM now 'Remove Data' at the side of the Age line rather than just 'Remove' as on the other lines. Hopefully this will be spotted by Garmin and fixed on the next update.

RE: Date of Birth not saving

hkskoglund — Thu, 10 May 2018 10:20:29 GMT

Yes, it seems like something has happened to registering the weight in the app. I'm trying to configure a garmin index scale and it won't accept birth date in november 1942. "Something went wrong. Try again" error. I tried to enter a date in garmin connect web site user profile and i am unable to set anything older than 1.1.1970.