Firmware 2.14.16

[surfboomerang]

@j-dominguez For S9 Baro?

http://firmware.geo.movescount.com/production/Ibiza-fw_2.14.16.3857-F.zip

[j.dominguez]

@surfboomerang Thanks!!!

[j.dominguez]

@surfboomerang is for S9 (no baro), but i think the one you posted works.

[isazi]

@j-dominguez the non baro version is called Lima, not Ibiza.

[j.dominguez]

@isazi ok thanks for the reply, i didn´t know. So if anyone could share S9 non baro last firmware i appreciate it.

thanks in advance!

[toothless]

@tuxella Did the update this morning at a charge of over 80%…nothing recorded today and in the evening had 20% left Did a soft reset and charging now. Hope it’s not one of these updates that make the watch go awry

[surfboomerang]

@toothless I don’t have the same experience with my S9baro after the update. Hopefully yours will be ok after the soft reset. Otherwise let it run dead and then charge it to 100% to see if that helps.

[toothless]

@surfboomerang So far it looks like soft reset helped…but I’ve turned off permanent HR monitoring after reset and will turn it on again to see if still draining fast.

[surfboomerang]

@toothless Good to hear!
I don’t use 24/7 HR or sleep analysis myself but I believe they are a big battery hog.

[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

[A Former User]

@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.

[A Former User]

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?