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

Resume Later crash 15.74

I use Resume Later from time to time. I tried it today for the first time on a Fenix 7 on 15.74 and although it returned to the watch face ok, I could not resume it. The start/stop button was not responsive so I could not get to the activities list. I eventually restarted the watch, but it hung on the copyright screen and on the second attempt on checking maps. I eventually had to do a restore results. The paused activity has gone. (At least I found that the restore backup works.)

A new bug or just a one off? I'm not very keen on trying it again?

  • I am sorry you had the issue. Please update to the newest v15.76 software just released as soon as possible. To test whether the issue continues, it can be done by stepping outside, acquiring GPS after selecting the same outdoor activity profile APP you were using, start the activity, then stop and select Resume Later. If the issue replicates, please update this thread and highlight my name and send me a Private Message. In general, the type of issue you had is one-off and restarting your watch or soft resetting your watch will be enough.

    Before testing, please soft reset your watch:

    Soft Reset - hold down your top left button until your watch shuts off then let go of the button.

  • The start/stop button was not responsive so I could not get to the activities list.

    The underlying  problem could be to do with the top right button. Is is working normally other times? FWIW, I've had no problems with 15.74 and just tested with 15.76 and not had any problems.

  • Thanks. I am pretty sure it is not the button itself - the watch is only a couple of weeks old and I have no problems with the button before or after the incident. I have updated to 15.76 now.

    I will test out the resume later function later today.

  • I have updated to v15.76 and testing resuming later a few times without problems, so I assume that this was a one-off issue.