This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Livetrack discards course already ridden after extended stop

Former Member
Former Member
Since the upgrade to GCM 4.15.1 (Android phones) I've now noticed on multiple occasions that if we make an extended stop (30 minutes or more, say) during a ride, when I look at the Livetrack output when we finally get home, it only shows the track from where we resumed the ride after the stop. This happens for both my wife (Edge 1000, Sony XZ2 compact phone) and myself (Edge 1030, Google Pixel 2 phone). Both phones are running GCM 4.15.1. Both Edge units have auto sleep disabled, so that they don't power down during the stop, and they don't lose connection with the phones, which remain mounted on the handlebars next to the Edge units. This used not to be a problem - when I first purchased the Edge 1030 about a year ago, I could make a lunch stop during a long ride and Livetrack was not affected in this manner. The problem doesn't happen if we make a shorter stop - say 10 minutes or so.

Here's a screenshot of the Livetrack map from this morning's ride - nothing prior to our morning tea stop at the 66km point appears. Both the Edge 1000 and 1030 Livetrack have this problem - both units indicated that Livetrack commenced when we commenced the activity at kilometre zero.

https://photos.app.goo.gl/a4e4jXanHZtdoTaB9
  • last weekend : (Android 9.0/Samsung S8, Connect 4.16.1, VivoActive HR, Mobile Internet Active)

    Saterday :
    - Automatic start,
    - Email is send,
    - Live Tracking is working well... even with 1 hour pause.
    - 24 hours visible NOT working

    Sunday:
    - No automatic start …
    No Live Tracking!!!

    All setting were the same ….
    Questions (to GARMIN):
    - why isn't the Live Tacking started on Sunday (this is not the first time not working)?
    - why still no 24H visibility?

    are there items I should look after?

  • Former Member
    0 Former Member over 6 years ago
    Well, I had a request from Garmin support for some logs from the 1030 and an example Livetrack with the problem, which I duly sent, and the further response I received said that they had been able to duplicate the problem themselves, so hopefully a fix will appear at some stage.
  • This was resolved with the Garmin Connect App version 4.18. For further inquiries or issues, please create a new thread.