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

955 Sleep Tracking is broken after 21.22

F955. Samsung S23Ultra user. Based in Singapore ( my phone and watch are both purchased in Hong Kong if that helps)

Sleep tracking is broken after the update to 21.22. It detects 2hours of sleep from like 1am to 3am.

I have turned off Garmin Share. the sleep schedules are set up properly on the watch. I have restarted my watch multiple times. 

I'm not sure what else I can do other than to wait for the next update  (or think abt changing to Cronos...)

  • I'm not sure what else I can do other than to wait for the next update

    Contact support.garmin.com and tell them your watch is broken and you need a replacement!

    I can assure you, sleep tracking is not generally broken. I had 21.19. 21.20 and now 21.22 and sleep tracking works for me as expected.
    It might cause a problem with your specific watch, but don't expect that to be fixed with the next release!

  • As an update for everyone,  Im now getting the dreaded BMX 0.0.0 and WHR 0.00.00 error. Everything started after several failed(?) updates last week. 

    Garmin Support here isnt back until next Monday due to Chinese New Year. There's probably nothing I can do until then.

  • An update for everyone. My 955 is working again on version  21.22. 

    The problem persisted after the recent blue triangle of death even after I did a factory reset. 

    But after I did a combination of:

    • repeated updates via Garmin Express on pc,including a maps update
    • connecting my watch to a charging cable and updating the watch when it asked me to install an update . I did this several times.
    • Going into settings, about, press the light button 8 times to force a "reinstall update"

    Sleep Tracking is now fine again. My whr and bmx are not 0 anymore. My software version was previously 21.22* but it now shows 21.22 (without the asterisk). Watch is as good as new. Hope this lasts.

    I still believe all my problems were due to a botched update. 

    Putting this here for my own reference and also in case anyone has the same issue.