S9 delay in start of activity
I seem to be consistently getting gun-times of 2 to 3 seconds over what is shown on my S9, and having kept a closer eye on display today - it seems that the activity duration doesn’t start until the display has transitioned over from the first face (battery option / start with middle button screen) to the activity face.
i.e - the seconds between start being pressed (at gun), and the activity display (duration, distance, hr etc… coming up, are not actually recorded…
does everyone have this issue ?
Even if the user interface can lag the gun time is correct. Record a slow motion video with a timer (normal stopwatch) side by side with your watch.
I have a few vids if needed.
@Dimitrios-Kanellopoulos - that’s what I thought, which is why I’ve been keeping an eye on it… just tested it with stopwatch on iPhone - and the first activity I started, did like I said… S9 was a good 2.5 seconds behind iPhone…
bizarrely when I tried it a second time they were in sync !
will try it a few more times in the coming days…
First noticed it when I did a run with S9 on one wrist, and A3P on the other… despite pressing start pretty closely together, the distance and time were out in a few metres.
Dimitrios Kanellopoulos Community Manager last edited by Dimitrios Kanellopoulos
@Richard-Francis wait let me get this right…
You pressed start there was a delay of 2.5s (on the interface) but the timer (duration) was right. Correct?
no… the duration is wrong, that’s the issue. I’m not bothered about a bit of delay in screen change; the elapsed time itself is wrong… it starts at 00:00 when it gets to the activity screen (which is 2 to 3 seconds after pressing start.
It seems to even do it on activities that don’t have any HR OR GPS on… Such as indoor cycling (with HR set to off).
@Richard-Francis I don t think that is correct what you say. I have just tested this and the duration is correct. only the UI lags.
@Richard-Francis wait. I just flashed back the production FW and you are right.
@Richard-Francis From the previous FW that was not the case (or the next I am using) . I will report this now. Thanks for keep arguing with me ;-D
I’ve noticed this on my Spartan too, but since I’m not a “gun-started” guy I’ve never tought about possible implication on measurement.
But screen loading doesn’t take 2 sec as on @Richard-Francis S9
This is absent or hardly noticeable on “non gps” activity like weightlifting