Firmware 2.14.16

freeheeler

I’ve had a weird experience today:
my watch stopped my running (mtb…) activity automatically (no accidetial press due to locked button) without any notification. I only noticed maybe 10min later and started another new activity.
The logbook entry is empty.
SA shows the track anyway and some weird values.
The total ascent is 0m.
Lowest point recorded: 85m (in fact 850m)
Highest point recorded: 110m (in fact 1’100m)

In QS and Strava the track and values are reasonable and maybe even correct.

Did anyone else ever notice this behavior on his/her S9B?

isazi

@freeheeler it crashed. How long ago it did happen?

freeheeler

@isazi
that was around 11am, why? never happened before

isazi

@freeheeler maybe worth to try sending the logs to Suunto. Can you do that and send me the time you sent logs in PM? Also where you following a track? Using S+? Waypoints? I can fill in a bug report.

freeheeler

@isazi
logfiles from what’s been synced to SA?
I will do that tonight with all details you need in pm thanks already

@isazi I had a similar crash the other day on this FW. I think the watch actually rebooted, HR history for the day/resources were lost, but the run up to the point was saved, though with some data like elevation summary fields lost as well.

I was following a TBT route created in the app and coming up on a the last turn if it helps. I think also had S+ enabled for TSS.

Stefan Kersting

@freeheeler yes had this issue some weeks ago. Contacted suunto support but they could not help. Because the watch synced with SA the was a problem to re download the activity again

isazi

@nickk Suunto is aware of this, I believe resources are scarse on the S9 and waypoints, navigation, and S+ all consume too much. I will report this to Suunto again, but if it happens again sending logs immediately after this happens would be great for debugging.

My wife had resources on 0% for two days, but thankfully a soft reset solved the problem…

isazi

@freeheeler @NickK @Stefan-Kersting I had confirmation the bug will be fixed in the next (coming very soon) release

Stefan Kersting

@isazi I remember that I used a suunto plus function and the navigation. So my thought was that the buck was related to the usage of this. Do you know when the buck occurs?

isazi

@stefan-kersting as I said in my previous response, there was a resource bug. Navigation and S+, especially if with waypoints, was too much for the S9 memory. But the bug seems fixed in pre production release.

@isazi Yeah, I thought it was related to the new waypoints/TBT features as I never had the issue before. Will send the logs if this happens again!

Though I think I won’t be running with navigation for at least the next 8-10 days. Not sure what the schedule is for June FW drop… The fix may arrive before I hit the unfamiliar trails again. Not that I’m against it.

freeheeler

@isazi
I’ve had TBT activated but no S+.
Interesting that @Stefan-Kersting and @NickK have had the same issue. At least I’m not alone and that soothes me

dulko79

Joaquin posted a nice comparison of S9 Baro and S9 Peak on Youtube. S9 baro has Ghost runner option in Suunto Plus section. More goodies on the way.

Stefan Kersting

@freeheeler and I lost 700 meters of ascend I statistics

freeheeler

@stefan-kersting
I’ve lost almost 500m, but that’s life as a gamma tester

BrunoH

Has anyone noticed any strange random beeps several times a day with this new FW version?

My S9B is randomly doing either single beeps or three beep series (low, higher, high beep). I try to look quickly but I never see anything on the watch display. I have disabled all notifications except incoming calls. These beeps are not activity related either because they happen outside of the exercise.

I did a hard reset because of HR belt also misbehaving. Still the belt lets me down and the random beeps keep coming. Any ideas?

P.S. The belt problems: 1. The watch finds the HR rate quickly (from belt) whenever I wait for the GPS fix. Still the HR field remains ‘–’ during the activity. 2. If I manage to see the pulse, the numbers vary from ridiculous to believable. It was showing over 200 when my real pulse was closer to 120 bpm. I have soaked the belt well and the battery is brand new.

Dimitrios Kanellopoulos

@brunoh compass calibration

Argo320

@hristijan-petreski no it didnt fix it, i still have the same issue