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

GCM stopped displaying movement for sleep

For the last two nights GCM has stopped showing the movement chart in the Sleep data. The data is displayed on the chart in the GC Web but not in the App. The last time it was displayed in the app was on the June 17th. Has anyone else experienced this?

Update: I find the issue occurs when you correct the sleep times in the app after your sleep has sync'ed from the watch to the app. If you don't correct the times the movement data is displayed

0 pshare over 4 years ago

That doesn't happen to me at all and I always edit the start and end times.

Perhaps the thing to do is to go into android app settings and delete the cache for the Connect app.

0 hotdogpartysausage over 4 years ago in reply to pshare

Hi I tried clearing the cache but it had no effect. I have GCM installed on a phone & tablet & neither show the movement data but GC web does. It worked fine up until 3 days ago. Another user on the Fenix 6 forum is also seeing this. Are you using the IOS or Android version of the app?

0 pshare over 4 years ago in reply to hotdogpartysausage

I'm using Android.

0 trux over 4 years ago

Are you telling you do not have the Movement button under the graph for toggling the movement on/off, or rather that the Movement graph does not show up when you tap the button?

0 hotdogpartysausage over 4 years ago in reply to trux

The movement button is there & the movement chart data is displsyed when I sync my Fenix. If I correct my sleep time the movement chart flatlines

0 hotdogpartysausage over 4 years ago in reply to hotdogpartysausage

Looks like this had been fixed with the release of v4.32 today

0 hotdogpartysausage over 4 years ago in reply to hotdogpartysausage

Oh well Garmin giveth back and Garmin taketh away again. After working fine for 2-weeks; With the last 3 nights sleep the issue has started happening again

0 9083484 over 1 year ago in reply to hotdogpartysausage

looks like the problem is ba k 4.63.1 ️