Firmware 2.14.16
-
@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.
-
@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
-
@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…
-
@freeheeler @NickK @Stefan-Kersting I had confirmation the bug will be fixed in the next (coming very soon) release
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@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?
Instagram: https://www.instagram.com/helgelandsbukken/
https://www.instagram.com/suunto_adventures/
IG: Helgelandsbukken, suunto_adventures
Vimeo: vimeo.com/helgelandsbukken
Blogg: https://turblogg.midnattsola.com -
@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.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@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.
-
@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
living sideways
-
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.
-
@freeheeler and I lost 700 meters of ascend I statistics
Instagram: https://www.instagram.com/helgelandsbukken/
https://www.instagram.com/suunto_adventures/
IG: Helgelandsbukken, suunto_adventures
Vimeo: vimeo.com/helgelandsbukken
Blogg: https://turblogg.midnattsola.com -
@stefan-kersting
I’ve lost almost 500m, but that’s life as a gamma tester
-
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.
Compasses: M-311, A-10, SK-7
Diving: Finnlight Navy 90, Vyper
Sports: Metron, S7, S9B and Vertical -
@brunoh compass calibration
Community Manager / Admin @Suunto
Creator of Quantified-Self.io
youtube.com/c/dimitrioskanellopoulos
https://instagram.com/dimitrioskanellopoulos
https://www.strava.com/athletes/7586105 -
@hristijan-petreski no it didnt fix it, i still have the same issue
-
@brunoh I actually also had problems with my HR belt, but thought it’s on the belts part.
I get sometimes too low of a value like 120 instead of perceived 150-160 and this for like 5min, then its fine again. -
@dimitrios-kanellopoulos I don’t have sound enabled in my watch, but are you saying that compas calibration is occurring during activity recording and not only in the compass calibration menu?
-
@surfboomerang that is correct. Many movements that you do naturaly could have enabled compass calibration
-
@dimitrios-kanellopoulos thanks, I was wondering this too. I thought it was a bug of some sort
