Saving exercise....

Saketo Nemo · 20 Aug 2020, 07:28

The only time that has happened to me is just when I inadvertently turned off the feelings.
What band are you using?
Have you already tried with a soft or hard reset?

paata · 20 Aug 2020, 09:21

I’m using Polar OH1. Soft reset was done after each freezing. Hard reset about two weeks ago so I will see if it will help.

JonasJkp · 20 Aug 2020, 10:49

@Saketo-Nemo yes i Have.
Bit sometimes the watch seems to change settings such as pool leangth etc. it may also change feelings but I’m not sure.

However the response from Suunto is not too notch anymore.

zadow · 27 Sept 2020, 19:00

Dears, any update on this? I was reporting logs few times for this issue. Today it happens to me again. Unfortunately, today everything went wrong and my activity was lost.

Yes, I have feeling enabled
Yes, I entered feeling when activity finishes.
Yes, I did turn off belt (Wahoo TICKR FIT) before actually ending the activity (this is recommended way as I learnt previously)

When it happens previously, usually, watch restarted themselves after few minutes and activity was saved and I was happy. Today, watch were saving for more than 3 hours. I restarted them by myself and activity was lost.

Today it was just easy run, but if I would lost some of my races or key training, that would really hurt me…

Watch - SSHWR Baro
Belt - Wahoo Tickr FIT

So, any (good?) news, please?

Thanks and have a good time!

P.S.
It’s a pity that this topic is discussed in about 4 or 5 threads, it’s hard to decide which is the right one then…mentioning this just to be on the safe side, because - yes, I did search the forum…

grantdoug · 28 Sept 2020, 14:11

@nseslija There is some kind of bug regarding HRM straps. My bug was a different bug, but it seems related. When I use a Suunto HRM Movesense strap on my Suunto 9, and I manually turn off the watch HRM while recording an exercise, the activity will not sync to the Suunto app. It turns out that I have to leave the watch HRM set to ‘on’ and it will sync. The watch software automatically turns off the watch HRM if an external strap HRM is paired. So I am just guessing your error is in the same ‘family’ as the error I experienced - the watch software / app is not able to accommodate certain patterns in HRM data.
\

Dimitrios Kanellopoulos · 28 Sept 2020, 15:34

@grantdoug what platform ? IOS / Android ?

Can you tell me the steps to reproduce this one with the latest software ? Thanks.

Dimitrios Kanellopoulos · 28 Sept 2020, 15:34

@zadow I understand

nseslija · 28 Sept 2020, 15:48

@grantdoug Maybe, but after enabling feeling in all my custom sport modes I never experienced the issue…

aroo7 · 17 Nov 2020, 12:51

In my case (Spartan Ultra), enabling feeling screen doesn’t solve the problem. I used to custom sport mode and H10. In the last month, I have had several such cases.

paata · 17 Nov 2020, 15:25

@aroo7 It is never ending story and big lottery, if it will be saved correctly without stuck. However, leave it spin for very long time helps in most cases (SSU).

Mff73 · 17 Nov 2020, 16:38

@aroo7
could it be a corrupted custom sport mode issue ? (not sure, just idea)
could worth the try to delete your sportsmode and recreate it.

aroo7 · 18 Nov 2020, 16:12

thanks for reply @paata & @Mff73
@paata last time this error appeared I left my watch for 4 hours but it didn’t help but once in a long time this loop is actually over. It looks a big lottery as you wrote.
@Mff73 I will try to recreate the sportsmode

zadow · 18 Nov 2020, 16:22

@aroo7 the only 100% solution what worked for me on my Spartans, was to turn off external HR BEFORE ending the activity. So I pressed the pause, turned off HR belt and then saved the activity. That worked well.
On S9 I havent experienced this problem yet. But I have my S9 first week only, so it is too soon to evaluate…

CHRGBR · 11 Jan 2021, 09:48

@CHRGBR said in Saving exercise....:

Hi, same problem for me. It happened twice, after a custom activity, with Polar hr belt. Feeling was on and I indicated it. The second time, I wait for 2 or 3 hours but it didn’t help. I had to reboot and loose the activity.

Did it happened to someone with a standard activity ? I can come back to basic activities while waiting for a fix…

Never experienced this issue since march … until today
Custom activity, wrist hr. After an hour, I needed to reboot.

Frederic · 30 Mar 2021, 19:16

Had this issue for the first time today

Has anyone tried to wait until the saving is finished ? If yes, did that get resolved by itself ? How long did it take ?
I only waited 1h but maybe I should have waited 10h+ to see ? Curious to see if anyone has any experience. Hoping it was just a one-off issue.

paata · 30 Mar 2021, 19:41

@frederic
I had this issue very often with my SSU. If feeling on or off it doesn’t matter. Actually the one thing that helps is turn off the ohr before ending activity. In case of watch stuck sometimes help leave it for long time, more than one hour, but not everytime.
However, I thought that S9 doesn’t have this bug.

Frederic · 30 Mar 2021, 21:25

@paata said in Saving exercise....:

@frederic
I had this issue very often with my SSU. If feeling on or off it doesn’t matter. Actually the one thing that helps is turn off the ohr before ending activity. In case of watch stuck sometimes help leave it for long time, more than one hour, but not everytime.
However, I thought that S9 doesn’t have this bug.

Actually, I didn’t use OHR and never use it but thanks for the tip.
I wish S9 didn’t have this bug but unfortunately I had to experience that today… really bummed

Frederic · 30 Mar 2021, 21:30

Today, after this issue I updated to the latest firmware just released so maybe that was fixed in this new v 2.14.12 ? To be continued…

sealion.hr · 31 Mar 2021, 04:36

@frederic This issue was fixed in previous firmware update already (2.13.xx). I never experienced it again

Frederic · 31 Mar 2021, 14:45

@sealion-hr said in Saving exercise....:

@frederic This issue was fixed in previous firmware update already (2.13.xx). I never experienced it again

I wish you would be right but my watch was actually using the 2.13.18 firmware so I don’t think that issue was fixed unfortunately.
Unless you have an official source/documentation that shows otherwise ?