Update of Duration and recording indicator

[klausr64]

Description

If a recording is stopped and later continued, the duration in the widget (and maybe other quantities) is not updated but stays at the time the recording was continued the first time.

Steps to reproduce

• start a recording by tapping the REC widget
• wait until distance and duration are updated (this is sometimes delayed very much! Why?)
• stop the recording by tapping the REC widget
• note the indicated duration
• continue the recording by tapping the REC widget
• note that distance is updated (if you move) but the duration not

Actual result

duration (and maybe other values displayed in the widget) are not reflecting the actual state when a recording is continued

Expected result

all values displayed in the widget should reflect the actual state in a synchronous manner

Your Environment (required)

Warning: Logs may contain information you deem sensitive.
Review this carefully before posting your issue!

OsmAnd Version: 5.0.2 (5021)
iOS version: 18.4.1
Device model: iPhone SE

[yuriiurshuliak]

When a track recording is paused and then resumed, the duration value in the widget does not update and stays frozen at the value it had when the recording was resumed.

I tried to reproduce this on both iOS and Android. Here are the steps I followed:

1. Start a track recording by tapping the REC widget.
2. Wait until duration and distance appear.
3. Tap REC again to pause/stop the recording.
4. Note the duration shown.
5. Wait a bit and walk some distance.
6. Tap REC again to resume recording.

iOS Result:

The track is split into two segments:

• First segment: from the start of recording to the pause.
• Second segment: from the start of recording to the current time.

Android Result:

The track is not split into segments. Instead:

• The recording continues as a single segment.
• The duration is calculated and shown correctly from the original start time to the current time, without gaps or freezes.

Conclusion

Your report is valid — the iOS behavior differs from Android and appears to be a bug in how duration (and possibly other values) are handled after resuming a recording.

OsmAnd 5.0.3 (5021)
OsmAnd~ 5.1.0#5150m, released: 2025-05-07

iOS	Android

[klausr64]

But even when the track is split, the duration should be updating as the recording continues.
Preferrably, the value should reflect the total time since the start of the recording (as it seems to be the case with Android). Similar for other values (like e.g. distance, which seems to be correct).

I.o.w. the splitting is not the problem (it seems even adequate to split at an user triggered interruption, different to how Android seems to handle this), but updating the values is the problem.

[klausr64]

FYI, I just started a recording with the phone lying on the desk.
While the distance is updated (due to positioning errors) the duration is not. It is stalled at 10:12. Without stopping and restarting the recording!

[DmitrySvetlichny]

#4703