@Chris-Wittwer , navigation works fine when recording is paused.
I had somewhat similar situation this weekend, used my A3P for nav during a race and had to glance at it quite often, at some point noticed it was on pause. Didn’t loose more than 15 minutes out of 30+ hours, but it still reminded me to lock those buttons - for me it’s really easy to accidentally hit a pause button when riding with gloves.
@awinkel there is a circular buffer, so space will be reclaimed when needed. I don’t have an ambit, so let’s wait for ambit users to chime in, but I’m pretty confident this is the case.
Is there going to be a firmware update or other way to suppress this annoying, unnecessarily alarming message? The problem is that if you DO NOT sync to the Suunto App, the message IS meaningful, but there is no way for the user to differentiate between real and false-positive messages!
@mlakis That’s not the issue in my case at least. I’m talking about cycling through the navigation screens using the lower left button. The behaviour of mine is identical to that in the query, including the double button press. It’s as if the watch has moved to the next screen but not actually displayed it.
In some post someone has said that the 4 first digits of the serial number are the year and week of production, I mean if the serial number is 1734XXXXXX… means that was produced the week 34 of 2017. Maybe you should keep the newer.
@Gregor-Tušar Which version of Moveslink2 do you have? I think 1.5.0 is the latest, but it is available for a while. You might check you HR belt contacts if you have been using for a long time, I just replaced mine (just the belt). Which mobile app do you use: Movescount App or Suunto App?
Never had issues with Moveslink2 on PC and Movescount App on iOS 13 is okay-ish (sport modes change not always sync at first time).
@Marcin-Byrtek yeah right, default is on, but what if you got your Vertical used or tested by someone (like mine) and wasn’t set up by you?
Maybe I could reset at some point my watch to see how is the default ON state 🙂
It seems not very intuitive to have to force the sync from the watch while plugged into the USB.
Did you made those Movescount changes while your watch was plugged in? Or perhaps you didn’t have internet connection at that moment you plugged in your watch? Or was your firewall concerned about Moveslink2 making connections?
There’s no active connection, polling from Moveslink2 side or pushing setting updates from Movescount. Thus Moveslink2 application starts it chat with Movescount service only after you’ve connected your watch to USB and it has synced data from the watch, it then checks just once with MC if there’s anything new to send to the watch. So you either make your Movescount changes before connecting to usb, reconnect your watch to trigger new sync or force sync manually. You also might just had a random glitch or there was some short term issue at Movescount side.
Autosync option in the watch menu only affects syncing with mobile app.
@isazi Thanks for the advice. Got back my old cable and it worked. The thing is that this old cable’s clip broke and i have to hold and press the watch against it while synchronizing. The new cable is form Suunto and just started malfunctioning. Going to see if warranty applies.