945 Latest Firmware Bugs, Issues and Missing Features

Good questions:

re: Altitude.  I live at about 300' ASL and mine triggers at 3000' or more.  Many times it has done this.

re: Pulse Ox.  I think we can eliminate this as I have mine turned off as well.

re: Manual calibration of Altimeter.  I have tried multiple settings for this, including turning auto-cal off etc.  (I haven't tried manual calibration though as I don't usually know the precise elevation I am at when I do these runs.

It took awhile but I/we finally deduced it is the TWO CIQ data fields that triggers it (along with the elevation).  One CIQ data field works just fine, so the workaround for now is to remove the second data field from the activity before starting it.  Are you using two CIQ fields when you're at 3800-3900'?

I use Stryd Power and I'm complimenting it with Run Power by FlowState. I'm trying to find common denominators. PulseOx has been eliminated. Maybe trying manual calibration prior to your next activity?  By no means is it a fix, but if it works for you and others it can give Garmin a little more to work with. On my next trip into the hills, I'm going to forego manual calibration and see if I can get crash. 

That would be great if you could try that as I won't be back in the mountains again for several weeks.

One other thing I'd like to throw out there even if it's a little far fetched. I just went back and reread the original thread. Some said they weren't having the problem, but what stood out to me was only one person referenced meters instead of feet. All locations mentioned were in the US. Maybe the one is from Canada and the North American maps with DEM is somehow related? 

Not sure about that.  I know for me I'm US and I've experienced the issue in the Southeast Appalachians, the Pacific Northwest (Mt Hood specifically), and on a plane several times.  All elevations were 3000'+.

Absolutely zero issues with this particular bug at any other time.

So when is the update being released? 2.50 appeared on June, 7th and since then nothing but a GPS beta and beta 2.62. I changed from 935 to 945 to be in a constant update cycle and begin to be disappointed.

So as 2.70 is out, time for an update?

Does anyone know a free bugtracking site we could use to make tracking the bugs more comfortably?

runningfan97

have some knowledge about a bugtracking site, but those are alive 

you could suggest Roland to start a new thread

happy & safe sporting

There is a bug by which the 945 "double counts" activity minutes when wearing a Vivosmart fitness tracker at the same time.  I don't ever take off my Vivosmart unless I am charging it (it's my primary tracker device per Garmin Connect) so I run/bike with it.  The activity minutes are doubled in the GC app when I do this.  Trueup should not allow double counting if I understand the purpose correctly.

I get the feeling 2.70 and sensor hun 2.32 really messed up my FR945! Or is it just my watch that is broken I’m wondering?

- Deep sleep is not tracked anymore, only light and REM sleep. 

- The on the watchface displayed heartrate doesn’t match the current heartrate in the app or widget, looks like the refresh rate on the watchface is lower

- OHR is unreliable and lags more behind. And OHR is now completely useless when cycling (40-50 beats too low), so my stress tracking, body battery and activity minutes are all messed up.

Really unhappy with my watch right now! And I’m considering reverting to 2.50.