Update*

I received an email from Suunto today. The watch is fixed and sent back to me today via DHL.

ohr chip, sensor flex and accumulator replaced according to the Service Note.

Roughly 2 week turnaround. Hopefully thats my only Suunto glitch and I can enjoy logging workouts again.

Many thanks for all the replies here with help and advice.

Best guess for next FW is mid to late April. Major updates has been as part of a new watch. Maybe we will see the FW together with Suunto 3 Fitness…

Suunto Spartan Sport Wrist HR - 2018/05/22

Software: 2.0.40 GPS - 5.7.10-P2.1-SNT.005 Hardware - 3040D4 Touch Screen- 2.0.30 Bluetooth - 2.3.32 Valencell - 6571

Thanks, @Andriy-Zarteskyy , but not of those steps solves the issue at all. It still remains there. The only difference is that mine (my TWO watches, both SST) has the same issue no matter what you do. In my case, if I connect at 40% and watch changes battery to 12% (this really happends), it does not come back to 40% even after reboot the watch.

I know this is not my issue, and I’m pretty sure it’s a SST general issue with this firmware, but I don’t see a solution and months pass…

@brad_olwin absolutely agree with you. My experiences from Germany are roughly the same. As soon as you have the ticket from support to send it back / to Suunto miracles happen.
Touchscreen in Spartan Sport WHR without function - sent to Finland, repaired and returned to my place in only 4 days, free of charge. Button no longer woirk ed on my 6d - 4 days, repaired and returned free of charge, writing for the buttons for scratched (too easily) of the watch - repaired and returned free if charge. Best support for hardware ever.
Parts of the support staff to communicate with at the beginning seem rather at least a little bit overwhelmed and not too knowledgeable about details after their helpfile/database ends.

@sartoric said in [Watch] Instant HR on new firmware 2.0.40 (spartan):

@yannis-belouris
30 sec is (maybe was ?) the time frame needed to have a valid HR sampling.

If I remember well (I don’t have one) it’s the same for hr belt

My opinion is that we are mistaking a valid engineering limitation (30 secs) with a possible solution like sampling every minute and displaying this until a valid current HR sample.
We need to strive for an excellent customer experience despite hardware limitations

@RiphRaph @Claymore Well, it took almost two weeks, but when I checked Movescount today the run had finally uploaded. All’s well that ends well. ☺

@soojong-moon Honestly, I don’t know. Since I’ve learned that watch is supposed to show 16 closest POIs (or 16 whichever POIs), I always tried to keep the amount lower than 16. So when I move to the location where I need new POIs, I delete the “old ones” from my watch. I am for sure limited by this relatively low number, but at least my watch seems to be predictable now and all my POIs are shown correctly.

I can test larger amount in different location during the weekend though 🙂

@Dimitrios-Kanellopoulos
I guess there’s something we never found before about this issue. So, maybe it’s something new/recent.

Today, I started a new trekking activity navigating a route already on watch and selected before starting. At a certain point I’ve seen that the graph was frozen. What a mystery!

While on the summit I decided to switch to a brand new route, so i created it, transferred it to the watch, did the BC trick and resumed the activity.
The graph was working as expected, but when my pal wanted to extend a bit the trip, we took a detour and at that point I’ve got the usual “off route” message and after a bit I’ve noticed that the graph froze.

So I reminded that at the beginning we took a shortcut so we went “off route” for a while.

My suspicion is that, if we stay for some time “off route” the altitude graph get stuck even if we go back on track.
The BC trick obviously works

@Fenr1r I never tried other GPS in the parking lot. I wasn’t used to running there. I only did it recently because of the Corona Virus.

But it’s an interesting thing to try!

Same model, same issue! Any bug fix available?

@DirkM ☹ ok, than - of course - that can’t be the reason at all …

@TELE-HO
I just mean “feeling chart” 😄

I think I will be leaving the Zwift Runpod as a footpod. Accuracy today was even better. Watch reported 3.74 miles on my run today. Typically I measure 3.70 to 3.73.

One both good and bad detail about my run today was (the bad first) the GPS reception cut out on my spartan halfway through. Not sure of the cause, but it never came back during the run. However (the good part) the zwift footpod carried on, pace/distances constantly refreshed and were typically what I expect to see. The only thing I’m missing in strava is the full GPS track.

One other note, I updated the firmware for the Runpod using the zwift app on my iPad. Not sure if that made a difference yet for better or worse.

@Shrek3k thanks for the info!

@lord_ru_1979 Have you tried it on a different laptop? I have had issues with one of my PCs and found a different HW solved it.

@ze-stuart yup afaik

@oli_ver I agree 🙂

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.