[Amazfit] dsaft:
RUN activity is a nightmare

I'm using Pace since October 2017 and my main interest is to use it as a sports watch to track my running training. I am not sure but I believe it came from factory with ROM 1.3.3 or 1.3.4.

I was satisfied with the cost/benefit of this watch. I could do all kinds of training (fartlek, sprints, tempo runs, progressive runs,...) and the measuring feedback during the activity was ok. The instant pace used to be reactive to speed variations (intentional or not).

The problem is that the running experience is becoming worse each new update released.

I have training plans to follow and I need to run on specific paces during certain distances or time intervals.

With the new ROM 1.3.6d it became a nightmare for me.

1. The instant pace is not responsive anymore. Sometimes it looks to be frozen. The first time I noticed I stopped running and started a new run activity. I paid more attention to instant pace and the response was slow and after a short time the pace looked to be frozen again. I started to run faster and the pace kept frozen. Then a slowed down the speed and after some time the instant pace changed to a slower but probably wrong pace. I increased the speed again and after some time it showed a faster pace. I have done a lot of runs with the latest ROM and it happens all the time. The amount of time that the instant pace is frozen varies. Sometimes it feels like some kind of averaging or sampling period. The distance, cadence and HR fields keep updating while the pace is frozen. The truth is that it almost impossible to follow training plans with this issue.

It is interesting that the average pace doesn't look to be off.

2. The instant pace is off most of the time. I have also noticed that when the instant pace updates after a frozen period it uses to show a wrong value. For example, I am running in a place where I know the lap distance and based on the total elapsed time I know my real average pace. I try to keep my speed as constant as possible (I'm running for 3 years and I know what I'm doing!). In a lap where my real average pace was 5:35/km I see the instant pace freezing and showing a lot of different values like 4:14/km, or 9:00/km, or 5:10/km, or 5:40/km, ... But the average pace and distance values shown by the watch look good.

My impression is that there is a problem with the instant pace software of the watch.

3. Total elapsed time / auto pause bug . It happened two times with me. The first time happened in my 2nd run after the ROM update. I was running for ~30 minutes and stopped to talk with a friend. The auto pause was initiated. After ~9 minutes I restarted running and the total elapsed time jumped to ~58 minutes when the correct would be ~39 minutes. I stopped again and waited for a few seconds while in auto pause mode and then restarted running but the total elapsed time continued wrong. I stopped again but this time I paused the activity by pressing the button instead of using he auto pause. When I resumed the activity the total elapsed time started to show the correct value (~42 minutes).

The second time happened yesterday. I was running for ~25 minutes and stopped for less than 5 seconds just to answer a question of somebody and resumed my running. I did not notice if the watch paused the activity. Less than 1 minute later I checked the tracking values and the total elapsed time was totally wrong (~44 minutes). I manually paused the activity using the button and resumed right after and the elapsed time came back to the correct value (~27 minutes).

This problem did not affect the average pace even when the total elapsed was wrong and way greater than the real time.

Anyone having the same "experience"?