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 issues unacceptable - Why isn't this high priority and deemed critical ?

I am well aware that there are several other posts about the current state of Livetrack on the Android platform, but I have intentionally created a new thread.

As a software engineer and architect of 25 years who has worked on both desktop and mobile platforms I am well qualified to comment on the current situation, and I find it unacceptable.

Lets analyse the situation as it stands, point form:

1. A system that was working perfectly for months, if not years, previously is now suddenly completely broken in multiple different ways.

LiveTrack refuses to start at all for many users, sometimes it will only start manually and not automatically, and sometimes it will start both manually and automatically, but then it refuses to stop automatically if it started automatically.

That's 3 separate and distinct issues with LiveTrack that have now appeared at the same time, out of nowhere, directly related to recent updates to the Garmin Connect app for Android.

2. A multitude of different users are all reporting the same issues, all of whom did not have these problems previously, which clearly indicates to me that the problem lies squarely with the Garmin Connect software on Android (or possibly compatibility issues between that software and the latest version/s of the Android OS), and it has nothing to do with customers hardware or customers doing something wrong.

Re-installing the Garmin Connect app does not fix the problems permanently or properly.

Deleting all application data for the Garmin Connect App does not fix the problems either.

3. Having re-installed the Garmin Connect software on my Samsung Galaxy S7 Edge, which has never had any problem running Connect or Livetrack before, 4 times in the last 3 days, and observing that re-installation only temporarily fixes the problem, I can safely say that re-installation is NOT a solution to the current issues, certainly not with the current version of the software.

I haven't trained for several months due to medical problems, but when I stopped training everything was working perfectly my side, with the SAME phone and the SAME Garmin Edge 520.

Now I come back a few months later, install all the pending updates, and suddenly things that were working, literally for years, simply do not work anymore and are completely broken and unusable?

I find this state of affairs to be completely unacceptable for several reasons, namely:

1. First rule of deploying software updates live is: You do not remove functionality unless you plan to replace it with something better and you NEVER introduce changes that break backward compatibility or are considered breaking changes in any way.

2. LiveTrack is a SAFETY feature that many people rely on, and is one of the best things that Garmin have done on their platform, and yet there appears to be no sense of urgency to fix this problem? Why not?

I fail to understand how these current LiveTrack issues are not deemed to be Critical Severity A issues that warrant an emergency hot fix. Where I currently work, something this damaging to the company's reputation, having this much of a negative impact on users, would immediately be escalated to our highest severity level and our developers would basically LIVE at the office until this was resolved and a hot fix was released to patch this ... WITHIN 48 HOURS maximum.

3. If Garmin know that it's their software causing this, and I think we can all agree that it's patently obvious that it is at this point, but they don't know how to fix it and are battling to pin down the root cause, then they need to ADMIT that and COMMUNICATE with their user base properly, instead of ignoring all of us and refusing to deal with the issue.

Have they never heard of public relations?

Having spent the last 3 days of my life fighting with the Garmin Connect app and LiveTrack, having LiveTrack work when it feels like it (in different ways, apparently depending on the time of day, the phase of the moon, and who knows what else), or not work at all, I am now at the end of my tether.

This is not new software and not even a new feature in existing software. This was working perfectly, for a very long time, and somebody did something to break it, and Garmin need to figure out who did what, and fix it. And they should do so as a matter of urgency, not take 6 to 8 weeks to maybe release a patch, while they refuse to communicate.

Furthermore, this is not even difficult to reproduce. I've managed to get it to break multiple times in the last 3 days, in multiple different ways, without even trying to break it. In fact, I was trying NOT TO break it.

@Garmin: What is going on? What are you doing to fix this? Why is this not being dealt with urgently as it should be? Why are you not communicating with your users properly?
  • I use Extend for 24 hrs. too, but when I open the link, it shows "User has ended LiveTrack already, not available anymore"!

    As far as I know it doesn't require any special user interaction to use the extended-Livetrack option (I always stop/start activities from my watch, and the extended tracks are always visible). I did notice that the extend option can revert to the default "off" after adding an email recipient for example, and that you have to enable the extend option for each device separately.

  • Does anybody know any device, not garmin, which can do the same?
    My family isn't happy when they can not track me ... (I ve a hart- condition)

    But then with a good working App and watch …

    Todays test:
    - automated start ... doesn't send any email
    - hand done strat ... does send any email
    - 24 Hour visible .. NOT! after ended the session the link is broken!

    I've virtually given up on Livetrack (even with the latest 4.15 GCM it's pretty flaky, and fails for me about half the time) and use the phone app LocaToWeb instead. It uses the phone's own GPS, taking the Garmin out of the equation, and is much more reliable.
  • What phone, android version and Garmin device are you using?


    520+ with with a Blackberry running Android M.

    My phone is way too old perhaps..... which is what has me nostalgic for 2015, when my 520 livetracked every time with zero failures on the same phone.

    I guess I'm willing at this point to peel off the money for a new phone, if there was indication it would definitely solve this problem.... which I'm not getting from this thread...
  • I use Extend for 24 hrs. too, but when I open the link, it shows "User has ended LiveTrack already, not available anymore"! I think I must end the LiveTrack at my mobile phone before the German device to keep the LiveTrack online for 24 hrs.? Usually I end the track at my Garmin device first, than the LiveTrack end automatically!


    It definitely should not be necessary to manually stop the LiveTrack in order for the "Extend for 24 Hours" to work.

    On Sunday when I did my most recent test I stopped my ride on the Edge 520 and LiveTrack was automatically stopped almost immediately, and I then saved the ride.

    Several hours later, back at home, I went to the LiveTrack link for that ride and the map and stats were still available with the entire routed plotted correctly.

    Try turning Extend off on your phone and then back on again, to make sure it sets it on properly. It might have been set on before the app upgraded itself, and then the upgrade has confused the settings and it LOOKS like it's on, but it's actually still off. Force it off, go out, go back in, and force it back on again.
  • Recommendation

    Looking at all the comments I notice quite a few that say something like "I have x turned on but it's not working and it's NOT on".

    When you update the Connect app on your phone, do yourself a favour and go into the app, go to the LiveTrack settings, and turn everything OFF manually. Then exit out, go back in, verify that everything is now off.

    Then turn whatever you need on back on again, go out, go back in, verify it's on.

    There have been a LOT of updates to the Connect app over the last 6 months and I'm wondering if sometimes the updates are corrupting the settings somehow and despite the fact that it looks like certain things are turned on, they actually are not turned on internally. As a software developer myself I've seen many examples of software that store a flag somewhere to indicate that something is turned on, but when that thing was turned on some other special code was run to configure and set various other things, but then later on an update gets applied which resets some or all of those various other internal things but does NOT set the flag to OFF, which means the app still thinks the setting is ON, and the flag says it's on, but all the internal things that were supposed to be configured a specific way are no longer configured that way.

    In other words, when you toggle a setting on in the app, you are not necessarily just flipping a software switch / setting a flag, you are actually probably also triggering the execution of certain (quite possibly complex) code that sets all kinds of other things internally and does who knows what else. And an update could very possibly be reverting the changes made by that code you triggered whilst NOT setting the relevant flag to off.

    If you turn everything off, then back on manually, you will force any weird and wonderful internal code / logic to execute again and set any and all internal things that need to be set.
  • Recommendation

    Looking at all the comments I notice quite a few that say something like "I have x turned on but it's not working and it's NOT on".

    When you update the Connect app on your phone, do yourself a favour and go into the app, go to the LiveTrack settings, and turn everything OFF manually. Then exit out, go back in, verify that everything is now off.

    Then turn whatever you need on back on again, go out, go back in, verify it's on.

    There have been a LOT of updates to the Connect app over the last 6 months and I'm wondering if sometimes the updates are corrupting the settings somehow and despite the fact that it looks like certain things are turned on, they actually are not turned on internally. As a software developer myself I've seen many examples of software that store a flag somewhere to indicate that something is turned on, but when that thing was turned on some other special code was run to configure and set various other things, but then later on an update gets applied which resets some or all of those various other internal things but does NOT set the flag to OFF, which means the app still thinks the setting is ON, and the flag says it's on, but all the internal things that were supposed to be configured a specific way are no longer configured that way.

    In other words, when you toggle a setting on in the app, you are not necessarily just flipping a software switch / setting a flag, you are actually probably also triggering the execution of certain (quite possibly complex) code that sets all kinds of other things internally and does who knows what else. And an update could very possibly be reverting the changes made by that code you triggered whilst NOT setting the relevant flag to off.

    If you turn everything off, then back on manually, you will force any weird and wonderful internal code / logic to execute again and set any and all internal things that need to be set.

    I really don't think the problems are related to that. When GCM 4.15 came out, I used the Settings app on my phone to delete cache and data for the GCM app, then I completely uninstalled GCM, re-installed it, and ran the setup in GCM again to connect and configure my Edge 1030. Livetrack still fails about 50% of the time that I try to use it. I'd also performed a reset on the 1030 when it updated to the current 7.00 FW, in an attempt to obviate problems on the Garmin device side of the connection.
  • AuldNick, which Phone do you have and which Android?
  • Livetrack still fails about 50% of the time that I try to use it

    50% fails almost makes me think the app didn't update, and makes me curious. Where does it fail? Livetrack never auto-starts, or does it start but never sends an email, or does it start+send email and displays the 'map of africa' with 'no signal, trying to reconnect'? Can you manually start Livetrack?
    BTW one of my devices didn't 'see' 4.15 in the Playstore, and when I manually updated it to 4.15 (via Google in a browser) it 'updated' to 4.13 instead. Somehow it took a couple of days before 4.15 was available for that device.

  • @Wuffi2015: The phone is a Google Pixel 2 running Android 9 with the Feb 2019 security update.

    @Twinaxx: Livetrack was definitely 4.15 when I had these failures - that's what the version information in GCM settings showed. See message #118 in this thread for a description of the problem: https://forums.garmin.com/forum/into-sports/garmin-connect-mobile-application/garmin-connect-mobile-android/1387509-livetrack-issues-unacceptable-why-isn-t-this-high-priority-and-deemed-critical?p=1453647. Livetrack starts ok and initially appears to be working ok, but at some point in the ride it gives up, at some indeterminate time later it may start working again, and draws a straight line between where it stopped working and where it started again. If you have a look at the map from Livetrack attached to that message, you can see that Livetrack stopped working shortly after the 20km point, started working again at the 58km point. So anyone tracking me would have thought for about an hour and a half that I had come to an abrupt halt for some unknown reason.

    I see that GCM on my phone has updated to 4.15.1, but I haven't been for a ride since it updated to see if there is any change.
  • AuldNik: Maybe Android 9 still has some problems, it's very new OS! It is still in development for app provider!

    But I found a problem too, I have Android 8 running on Huawei P8 Lite! The Livetrack works fine, I was cycling 52 km! But the last waypoint was at 42 km, but the Livetrack still worked.
    But the distance of 9.92 km and time of 0:32 hours is wrong! Normally it's 2.5 hours and 52 km together, I don't know why, see screenshots!

    " />">

    " />">

    But I have a conjecture, at waypoint 42 km I changed new batteries at my garmin device, maybe this is the cause?