Spartan update complains

Saketo Nemo

Mine SSU too. Tried saturday, GPS fixed after a few seconds

JonasJkp

@Brad_Olwin hi Brad. Great to get an answer. I’ve used the watch for 2years without this issue, it appeared after a software update q1 this year.

Yes I have hard reset the watch. If feelings are turned on it often works, with feelings of it freezes and I loose my workout. I have two big virtual competitions Coming up (Lidingöloppet and a marathon) and as of now it seemed that Im being forced to by a Garmin o Polar watch.

bbx100

I really miss that baro trend indicator on my SSWHR baro which finally a few days ago returned on watch face in s9 baro. I had it on my old core and missed it on my spartan baro. So it needed two generation of watches from ambit over spartan to return on the watch face os S9. Maybe Suunto will return other features from ambit watches which are missing, in some version of Suunto 11 watch in the future…

DRezvoff

The clock began to hang 1-2 times a month after the completion of training… write - preservation, but passes 2, 3, 4 hours, notifications come, but the clock continues to try to keep training… helps only soft reset, after which the clock saves the number of calories spent and steps taken, but the workout is removed…
Is that a firmware problem?

Mff73

@DRezvoff said in Spartan update complains:

Is that a firmware problem?

Maybe, but maybe not. If a FW bug was i presume it should have already raised, but …

If it worked for you and begin to fail, it could just be something now stucked in your watch. Either first soft reset it and see, and if not successful, contemplate to hard reset after complete sync to make the FW fresh.

DRezvoff

@Mff73 if there are no other options. then yes. hard reset only
and reconfigure hours, workouts, and more…: (

sartoric

@DRezvoff
I would start with a soft reset first.
I never had that kind of problem, maybe once in years.

DRezvoff

@sartoric well, I have to do a sotf reset all the time a month… :(((

Mff73

@DRezvoff
just to check : your issue is that your watch is blocked at the saving workout step ? Like never ending saving ?
If so, do you have enabled the “feeling” option ? it was a workaround for such issues if i remember well.
If already enabled, you still can try to connect it to SA right after soft reset and send logs to suunto (i guess).

DRezvoff

@Mff73 The feeling option is enabled.
if the problem is known and it is clearly a clock software problem, why is there no bug fix update???

sartoric

@DRezvoff
Did you contacted suunto support ? I would do it

DRezvoff

@sartoric I hope Suunto technicians read this forum and are aware of the problem…
if there are no changes, I will contact support directly

isazi

@DRezvoff better contact support, Suunto is not really monitoring this forum for bugs. There are a couple of developers here in the forum, sure, but it is better to let Suunto know.

DRezvoff

@isazi The Russian support service could not help me… they give a standard set of actions that are written on the Suunto website.
The clock began to lie at a climb of 20-50 m… that’s a lot. I have repeatedly thought about changing the clock to Garmin, they release updates regularly.

isazi

@drezvoff does your watch has a barometer? I don’t know the specifics it. Also, yes Garmin releases many updates, not too many for watches that are as old as yours though.

Mi_chael

@drezvoff

My fenix have many update but too many bugs…!!!

DRezvoff

@isazi no, my watch model without a barometer

DRezvoff

@mi_chael I compare climbing readings with other athletes who use Polar or Garmin watches. The total difference in climbing at a distance of 17km differs by 100-200m… That’s a huge difference.

DRezvoff

We all ran the same distance together…

Here’s the data from my watch, climbing 573m
https://www.strava.com/activities/5778881853

Here are the data from the clock Polar, climbing 838m
https://www.strava.com/activities/5778881853

Here is the data from the watch Garmin, climbing 825m
https://www.strava.com/activities/5779198526

The difference in climb is almost 300 m!!! And this is in an open area, without a forest.

Dimitrios Kanellopoulos

@drezvoff non baro devices have this issue on not constant climbs.