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

Sleep info in app has been broken for months now (Forerunner 935 to Samsung Note 9)

As the title states, sleep tracking has been really messed up for months now. I don't know the exact date, but it's been broken for 3-4 months now. The sleep range is all over the place. Sometimes it is interpreting me asleep hours before I actually go to bed, sometimes it has me waking up 3 hours after I actually woke, sometimes it's both sides that are off. There is no pattern, some days it is just fine, but those days are in the minority.

I don't have a clue as to what's doing it, nor do I know how to manually reset it either in the watch or in the app so it might correlate properly. I never changed my normal range for sleep in the app (it's been the exact same for the last three years across multiple watches). Does anyone have a troubleshooting solution for this, or know where to send either a log from the app or from the watch? I've dealt with troubleshooting problems before, but normally in beta testing software updates in the watch, never in the app.

0 Schnarpfi over 6 years ago

Same effect with my Fenix5s and a Samsung Galaxy S7. Detected sleep often begins 1 to 2 hours before bedtime. The usual sleeping and wakeup time is set correctly. Yesterday I have been to the Cinema and sleep time was recorded at 5pm though I finally went to bed at 10pm. Annoying...

0 JSRUNNER_ over 6 years ago

jstpassaro - why do you think that it is the app rather than the watch ? I have a Note 9 and Fenix 5+ and experienced no problems. What does Garmin connect on a PC show are you saying that gives different figures from the app?

0 Schnarpfi over 6 years ago

I also so not see the problem at the watch. I think it only gives the sensor information about movement, pulse etc to the Server where the information are interpretated. Nevertheless its interesting that its working for some users...

0 2goBeyond over 6 years ago

From what I've gotten back from other users dealing with this problem (but on different watches) is the data hand-off between the watch and how the app interprets it. The Sleep table (my parameters) have not changed at all. 10-1 I am syncing data through the app from the watch rather than flowing that info via the GC-PC. That info online then is matching what's showing up on the app (since the flow of data is coming that way). I guess I can test by cutting the watch sync off and uploading the info to the PC version and see the results (which I am remiss to do for personal reasons involving message flow to the watch).

I've had this particular watch for almost two years now, and it's never done before so. Giving the benefit of the doubt something about the watch might have changed (physical wear down of components), or something in the latest software update might have changed how it interprets sleep (and that issue was then coming for the prior beta since I know this has been happening before the most recent live update, just not in detail). But if it isn't the watch and is the app, where do you send issues? I don't think I've ever sent info to the app team before and I can't find anything in the app to send a log. Maybe I'm just missing it or glossing over it in the app.

0 JSRUNNER_ over 6 years ago

jstpassaro I guess that it is just conceivable that a different implementation of Android might corrupt the data transfer in some way but it seems unlikely. I'd be very surprised if the data that ends up stored on the server is different if uploaded via PC or Mobile, It is worth carrying out the experiment though then if you found a difference you have a very focussed issue to report.

You could also try reverting to an earlier software version on the watch - if you search the forums you'll find instructions to do this - if you revert to the SW at a point where your sleep was correct then that will eliminate (or not) the watch sw as a cause.