@TELE-HO you’re right but how long can I wait. It didn’t make any sense for me since I’ve been waiting for 3 months and the only thing I get from Suunto support is the same question about my software version.
Also, I don’t know how you can define the suunto 9 and 5 battery like this. Suunto 7 is a smartwatch, not comparable to ambit. Your ambit2 does not reach more than 30 hours at maximum gps precision like suunto 9 and does not have endurance mode to push you up to 120h. It does not even reach Suunto 5’s 25h.
Notifications can be turned off and the navigation features of suunto 9 and suunto 5 are fantastic.
There are no apps for suunto 5 and 9, but they have a lot of features that ambit doesn’t have. I have also an ambit3, i know what i’m saying. They are two different watches, from two different families, as the different name suggests.
When you refer to a lifestyle watch, you are perhaps referring to suunto 7, which is a smartwatch. As you can see, suunto 9 and 5, which have nothing to do with a smartwatch, are still on the list and meet everyone like me and you who want solidity, reliability and indestructible materials from the watch.
On the forum we had many people in love with their ambit who, once they switched to suunto 9, said they were enthusiastic. I advise you to try.
I just discovered last week that a lot of moves were wrong in Ascent / Descent values once imported :
on Movescount, these moves are fine ;
on SA, they are wrong.
I think the problem is coming from moves that were on the two platforms (in 2018, i was using the two platforms and synced my activities on the two services) : the Ascent / descent bug on SA wasn’t solved last year and i always get wrong values. So i stayed on Movescount the time to get this bug solved.
I remember reading some information telling us that once the bug solved, all the old moves with incorrect Ascent / descent values will be updated ? Am i wrong ?
What is the solution to have some correct datas for Ascent / Descent which correspond to the right values that are on the Movescount platform ?
I’m trying to ask some assistance from Suunto :
nobody on French phone assistance ;
i don’t find any way to contact some mail assistance…
If I do this w/o the counter, it’s just a bunch of random data on the mountain, it includes the chairlift rides and everything, as one “big run”.
I guess you could manually use laps, to separate things, but remembering to do this (we are in 2019, right?) is inconsistent, and can be unpleasant, say if it’s 5-degrees-F, on a day (usually involves taking off a glove, shoving my coat and other layers out of the way, to push a lap button).
I have a couple of custom-screens in my Alpine Skiing, which is really handy for at-a-glance stats, for things like number of runs, descent-per, etc (which Suunto obviously excludes in the Alpine skiing screens, because it has no “run” concept on the Ambit3 skiing mode).
I use a similar set of screens, and an app, for group sprint sections on when riding (road cycling), so I can see how I’m doing, at-a-glance, on a particular day.
Removing all of this pretty much means my watches are non-functional, for my use, and they either become auction items, or landfill items (which it seems like the Ambit2 Sapphire is, regardless).
Edit: I should mention, too, that it took me over an hour, with SA, to get my Ambit3 to sync a handful of moves (about 10/20), at which point it failed outright, and said it was unable to sync further (despite multiple retries). This is on a VERY fast phone, with an 845 chipset, Bluetooth 5.0, screaming-fast data pipe, etc, that can sync my cheap-o Garmin tracker I wear to track daily stuff (Suunto resting HR is way too inaccurate to even consider for this), in maybe 20-30 seconds (syncing a couple of days of complete HR/activity/sleep data, in that example).
Edit2: I tried SA, again, and it restarted at activity/move 1/26, and was still there after 8 minutes, when I decided to shut it down. Something is gravely wrong with Bluetooth (sync) on the Ambit3, and it’s questionable as to whether or not this would be an app-side fix, IMO/IME. But apparently that’s about to become the “sync standard”, right, whenever the data-port happens, you’ll have to use SA, going forward?