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 Autostart has ceased to work

Former Member
Former Member
[apologies for cross posting this, i put it in the wrong 'Connect' forum the first time]

I dont know what has changed but about a month ago(ish) auto start for livetrack stopped working, I have an Edge 820 use that feature everyday (so my Mrs knows when to put my dinner on :D).

Ive tried all the obvious stuff and and still no joy:

1. Uninstalled Connect (twice), wiped app cache etc and restarted, reinstalled.
2. Unpaired, repaired bluetooth
3. Rolled back firmware on device....

None of the above has worked. The Bluetooth connection is fine as the devices still connect and the rides autoupload to strava etc. The Autostart only ever works if the app is open AND it is on the Livetrack page. This isn't practical, the whole point is that the LIvetrack just (auto)starts as soon as you start your activity, thats what is use to do.

The fact that it appears to be dependent on the Connect App to work at the moment has led me to believe that the problems is with the app (or the phone) rather than the Garmin device itself. Ive run out of ideas and would welcome so tips/advice from anyone that has experienced similar issues.

Thanks in advance.
  • You're not alone. I usually have my music app in the foreground. I'll give it a try with Connect in front and report back.

    I haven't yet contacted Garmin Support, which is the only way to ensure that the developers are made aware. Have you been in touch with them?

    -- Pete
  • Former Member
    0 Former Member over 7 years ago
    I have the same problem with Connect Mobile and my Fenix 3 HR. For my wife it's a safety feature since I'm running late at night. That's why I ordered a premium account on STRAVA although I'm a runner. ;)

    I've sent an email to the support and wait for some support...

    Greetz!
    René
  • I also have this issue on my Fenix5S, it has not sent a notification in a week now. I have just sent a support email, I am wondering if it is tied to the current app update issues.
  • Former Member
    0 Former Member over 7 years ago
    Same problem here. I had been successfully using Livetrack with Autostart for months on my Edge 820 (with Connect on Samsung S7). About 3 weeks ago it stopped working. Been through the same diagnostic process and reached the same conclusion - only now works if the Connect app is open on the phone.

    Not totally sure but it may have stopped working around the same time as the latest upgrade of the Connect app for Android was pushed out.

    Logged a ticket with Garmin support but as yet no response.
  • I also have the problem with my Edge 1000 and a Sony XZ1.
    I will try the manual start, to see if it is a general tracking problem or only the autostart feature
  • After i started use HR Monitor for my VA3 livetrack stop working. But without sensors livetrack works. I mean starting bike activity without connecting sensors it works. Maybe you guys also try it without HR Monitor. I use Garmin's sensors.
  • Former Member
    0 Former Member over 7 years ago
    I've found live track to be more stable (with as many sensors as I want) if I start the activity out of range of my wifi....might occasionally take 500m, but it does start
  • I close the Wifi before i leave home and it's not work for me.Two times i see "livetrack failed" notification but right now (maybe it's about sensor's connected notifications) can't see "failed" notification. Also garmin connect stop notificate "livetrack failed" or "livetrack started".
  • I also have the problem with my Edge 1000 and a Sony XZ1.
    I will try the manual start, to see if it is a general tracking problem or only the autostart feature


    Manual start of live tracking works.
    At the time autostart worked, I had also the issue that I have to stop WiFi on my mobile before I start when I'm in the range of a known Hotspot.
  • Former Member
    0 Former Member over 7 years ago
    Looks like the release of GCM 4.3 might have resolved this.

    HOWEVER - to get Autostart working, I had to disable Autostart in the app, then re-enable it. Since then it has worked consistently (including without the GCM app needing to be open on the phone).