@pelo2 I never had this behaviour in Starva and I also have forgotten to un-pause the watch several times. In the track you see an straight line but all the metrics are correct.
BTW, what are the SA metrics?
Strava is what it is, not very reliable, not in positioning not in time. I mean, I am in some segments that I haven’t run, I’ve passed close by but not following the segment, in others I have run them with a friend and we have differences of 5/10 seconds in the same segment when the time should be the same. Don’t get me wrong, I use Strava and it is fun to compete for some segments, but considering what Strava really is.
@andrasveres I reset GPS and rebooted the watch… it seems to work OK now. But at that time the watch did not record the path, only the 3 minutes. Still it drew a straight line to the destination and the point I reached… And at that time I locked the buttons. Maybe it is a one time issue and is gone now? I am going to risk and keep the watch I think. Give it a chance.
I’m having similar issues. It can be stable for weeks and then jump from ~50m asl to 4000m while dropping temp to -50C.
E.g last week it was nice and stable (ski touring, alt. scale on the right, both profile and 1000-2000m range are correct):
A flat run back home few days later, real alt. diff should be in 10-15m range and it’s generally ~50m asl; bit challenging weather and trails in the woods, so some fused-alti shenanigans and baro drift is kind of expected:
And then this last night, real alt. diff should be in 30m range instead of 4000m. And when something like this happens, I always tend to get those choppy alt. charts in TP. Adjusted altitude before heading out but but it was rising from 50m to 1000m in like 5-10 minutes.
After that last run I soaked my A3P in warm water for an hour or so, turned off fused alti, reset gps,switched to baro mode and set ref. altitude. And it has been super-stable for past 20 hours. Last time it did something similar was about a month ago.
On a good day I still get something like this from my A3P for ~30m alt diff runs and this is almost identical of what I would get from 1m resolution DEM data provided by local land survey:
@andrasveres it seems, that new strap helped, I made a exercise and HR didn’t jump out of the range I think is OK, thank you for your advice @isazi I can confirm, that new belt arrived with white area around the connector
@Tom-Z , are you sure it happened after watch firmware update and it’s not related to MC app version or moving to Suunto App?
Latest FW is 2.4.17, released on 2017-06-26, one before was 2.4.1, released on 2016-12-01 . I wouldn’t be so sure if anything older than those two would even work with latest MC app or current SA, even stepping down to 2.4.1 might introduce some issues with mobile apps (though it does work with Suuntolink, tested). And downgrading to anything older would also mean loosing of quite a few features - https://moveslink.static.movescount.com/release_notes/SuuntoAmbit3_ReleaseNotes.html
But technically there’s no problem forcing a FW downgrade itself. Just be ready for update notifications in Suuntolink & Moveslink2 and possibly in mobile apps as well.
Replace <rev> with one from release notes (“2.4.17”,“2.4.1”, “2.2.16”, …) , you also need to provide required <appkey> yourself. If you are using Suuntolink on Windows, you’ll find it in %appdata%\Suuntolink\suuntoapp.log . Or look for production.json at Suuntolink installation folder.
Suuntolink uses a certain naming convention for FW files when it downloads those (e.g. uiservices.movescount.com-Emu-69.4.17414-2.4.17.sfi ), but it doesn’t seem to really matter. Once you have the file you just drag-n-drop it onto drop area somewhere in lower portion of Suuntolink window, you’ll notice when you’ve found it. And as always, use it at your own risk, yada yada yada …