LONG save time?
-
@Salasrocks I think you mean the same problem like this: https://forum.suunto.com/topic/4210/syncing-hr-data/17
-
@paata They are related but not the same. Very often the long save is triggered without an HR sync… But it always happens when an external HR sensor is involved. This has been going on for about a year now. All recent Spartan and Sx builds contain have this issue.
-
@NickK Thanks for your response. I have recently switched to a non-Suunto HR monitor (Wahoo). The new HR monitor is so much more reliable…but it does seem that the long save time happened when I made that switch. Good to know. Thanks a bunch!
-
@Salasrocks I have never had issues with my Wahoo Tickr (the very basic one). What model do you have?
-
@isazi Yes, I have an old basic Tikr too that I still use occasionally and it seems to behave.
-
@isazi I have the new ArmBand version of the Tickr.
-
I have same problem with my Spartan Sport WHR with lastest update software. This morning when I finish a 60 minutes running, the watch can not save the move, It keep on saving … for more than 1 hr until now.
This is second time I got this problem. The first time happend with 30 minutes workout (a week ago, and after that it work properly). I have to force restart the watch and the workout was not saved.
I do not use HR belt or any external sensor
Please help -
@vietpq do you have feelings enabled at the end of the activity?
-
@isazi I disabled the feelings option
-
first few runs with SSU and Suunto Smart HR belt, longest one 2hrs: so far moves save very fast. no difference between feelings enabled or disabled for me
-
@vietpq try enabling it.
-
@isazi Thank you, can you explain why do we need to enable it? I has disabled the option for nearly 2 years
-
@vietpq I don’t know. I only know that it is a workaround against this bug, and I learned about it on this same forum.
-
Are the workouts always lost or is there any way to get them back?
-
@JonasJ
Well, the answer is yes and no. It depends. I have SSWHR Baro and Wahoo Tickr FIT (OHR armband). From time to time it happens to me that watch are saving the activity veeeery long. However, it happen to me only once that activity was not saved and lost. When you occur this very long time saving issue, be patient. Wait for the watch restarts itself. It can take several (tens) of minutes. Once the watch restarted, it is very likely that activity is saved and you only need to sync it manually from the SA. If you are not patient and do a soft reset, it is very likely that activity is not saved. That exactly happen to me once.On the other side I have developed a workaround which is not very convenient, but till now works at 100%.
- when finishing activity, press the pause button
- TURN OFF OHR arm band
- press the finish button on watch to end and save activity.
With this procedure, I have never experienced long saving time.
It is not very convenient, I know, but I rather be sure and for single activity it does not really matter when you turn off the arm band.
(me personally, I am doing very often several activities in a row and multisport is not always an option…and for races and some interval trainings I am using Smart Sensor on chest strap) -
I got this problem third time today (1st time was about 2 months ago). The watch has been ”saving” for 60 minutes now. Two times before I have used force restart button and lost the last exercise.
This time I decided to look the forum for other options. From what I have learned there are now other options! Force restart is the only option.I have had Suunto Spartan Ultra since March 2017 with original HR belt. I use feelings and have done over 1000 moves with this watch and these are the first saving problems. I have been Suunto user since 2013 and used Quest and Ambit3 before. I have never had this kind of problems! If this is a bug then fix it!
-
This is happening with my Spartan Sport with the new Polar Verity Sense. The wait it out workaround works, but would very much like to have this fixed. I now the Spartan line is no longer being enhanced and I’m fine with that, but please release a patch for this one issue.
