iOS 3.0.0
-
Strange 441h recovery time with my cycling of this mornings all other metrics are ok (143tss, calories and hr are ok…)
Just checked : another one strange on my very easy 2h30 trail run last Friday night : 141h
All other activities seem to be ok
-
@Tieutieu there is an issue with the last FW update. Some have strange recovery time. I had 729h for a 18km hike and today 110h for 38km of bike. I wrote to Suunto support that has yet responded.
-
@valeR ok ; I reported that through iOS beta program
-
@Tieutieu for users on this and other forums it happened with the FW 2.44.52 nothing about the App itself.
-
Do the awards work in your Suunto Apple app? Mine have all been set to 0 since the beginning. Except for the Suunto usage time milestones, of which I have a few.
-
@Sportsfreund yes, they do work… got some of them, including OCC Challenger, although the time frame and distance did not really match. But they pulled these awards before the end of the time frame…
-
In my App all are one zero.
-
These are mine so far… iOS only…
-
I’ve just seen within personal records that my best time for a half marathon is connected to an activity that is shorter - only 20.07km. It doesn’t even has a tag “half marathon”.
-
In my app, all awards remain at 0. Only membership is honored with 6 years.
Use the Vertical 1 and iOS.
-
iOS and Race 2, badges work, I have 11 in total.
-
Version 3.5.0 available for download.
-
-
@OutdoorMan I’m looking but I haven’t seen any difference yet (with 3.4.0)
-
@safari found one - if you click one View more in an activity it will show you all details in a new design
-
@OutdoorMan nicely spotted;)
-
@Josaiplu and then I noticed new bugs, which I have also reported : ) For example one widget is broken. When you scrollt through the sleep data graph, it is moving around, so it’s impossible to scroll. Other graphs don’t do that.
-
@OutdoorMan You re a way better beta tester than me
thanks 
-
I Also noticed this nice evolution after my first run after update yesterday.
I reported that “speed” ascent is visible in two regroupements, close one to another (“elevation” section and a dedicated “speed ascent” section).
IMHO not useful to have it twice.
-
@Tieutieu Data values in regroupements?! Great!
