Custom sport modes no longer visible on App
-
Hi all,
I’ve just noticed that I can no longer see or edit the custom sports modes that I had previously set up on the Suunto App. When I select Sports Mode customisation now the app is unresponsive and eventually displays the message “Oops! Something went wrong”. I have tried deleting and reinstalling the app, and performing a soft reset on my watch.
I’m running Suunto App 4.38.1 on Android 11 with a Suunto 5 watch on 2.14.14.
Any ideas? -
@epictetus
Try using the last beta version -
@epictetus did you have any corrupted sport mode, especially the trail running one? Did you do a hard reset after installing the latest version of the firmware?
-
@isazi
The sport modes that I use (both custom and standard) work fine. I just can’t edit the custom ones or create a new one. I don’t use the Trail running sport mode. I didn’t do a hard reset on the watch when I last updated the firmware. Should I have? -
@epictetus check this thread and see if it is the same that happened to you.
-
@isazi
I can’t remember if the process was interrupted when I performed the 2.14.14 firmware update, but I seem to have the same symptoms as in your linked thread. I need to check if I have a record of my custom sport modes so that I can reproduce them, then I’ll try a hard reset. -
@epictetus do you by any chance have something like “unspecified sport” on your watch, when you go looking at the activity types available? If so you need a reset.
-
@isazi
No I didn’t see "unspecified sport"on my watch.But I’ve now performed a hard reset, and after some initial problems, it seems to be working. I’ve been able to re-create my custom sport modes, and they appear in the watch.
I did get an error message “name too short” when I set up the name for each new sport mode, although it saved successfully. I got this message regardless of the length of the name.
By the way, is there a way of viewing the screens for the standard sport modes? They’re not available to view under “Sport mode customisation”, and I can’t find any documentation for them.
-
@epictetus so this error should not happen again with your firmware version. But post if it happens again because it may be something else in that case.
-
@isazi
Thanks for your help. Much appreciated. -
@sartoric
Thanks for responding.
As I’ve now managed to fix the problem with a hard reset of my watch, I won’t need to try the current beta. I’m wary of running a beta anyway as it’s likely to give problems with new or existing features.
