Firmware 2.14.16

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.

A Former User

@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

Argonaut330

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

DMytro

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

surfboomerang

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

Dimitrios Kanellopoulos

@surfboomerang that is correct. Many movements that you do naturaly could have enabled compass calibration

Likarnik

@dimitrios-kanellopoulos thanks, I was wondering this too. I thought it was a bug of some sort

DMytro

Also I’ve noticed ‘training soon?’ reminder pops up during charging. This may have already been present since last few release.

isazi

@дима-мельниченко the “training soon” reminder to charge is there since the first release I think.

DMytro

@isazi during charging too? Isn’t it redundant, since I’m already charging?

isazi

@дима-мельниченко I have never had that message during charging

Dimitrios Kanellopoulos

@дима-мельниченко yes and no.

You might wanna charge a little the watch and the message comes to remind you that you will be needing some juice (IT analyses your trends).

For example if the watch knows that during the weekend you usually spend 50% battery , if the current battery is <50% (or chaged less) and its friday or something the message should come.

EzioAuditore

@isazi Yup. Had it yesterday when I put the watch to charge at 0% After a while it said: Training soon? Charge your watch.