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?
  • Just updated to 4.10 from Play store.
  • For those who are seeing this a few month later as I am, after being royally frustrated with Garmin for months, rolling back to 4.8 works. I tried some of the early 4.9.x versions and they fail. Gotta go back to 4.8. Most recent release of 4.13 still fails. Like others, I'm dumbfounded that Garmin can't fix this. It is so consistently failing. They are rolling out software releases as often as 4 days apart. Do they not test them?

    As for those who mention that Garmin does not listen to it's customers - that has been demonstrated repeatedly over the years. A wealth of customers can express their opinion in these forums, even call customer support to discuss the problem and point them to the forum for more examples, and they don't care. Good products, but horrible as meeting their customer needs and even work developing user interfaces. It's a shame :(
  • mtsarpilot, curious if you tried GCM Android v4.13.5. Since I updated, LiveTrack has worked every time.

    Others have reported similar success...

    There was an update to 4.13.5 yesterday. and I have had 2 Livetrack sessions working, and ending when they should (for the first time in ~2-3 weeks). Happy! :)
  • mtsarpilot, curious if you tried GCM Android v4.13.5. Since I updated, LiveTrack has worked every time.

    Others have reported similar success...



    seilogramp, yes I was running 4.13.5 this morning and LiveTrack had the same failure of not transmitting any data after starting. Sounds like they finally made some progress if some of you are seeing success, but still have not nailed the issue as others are still seeing the failure. At the rate Garmin is tossing out updates, I'm guessing there are more updates coming as they continue to address this issue across all the phones I'm running a Samsung Galaxy S7, don't know what phones folks are having success with, may be different products. I'll give it a little more time for more updates then step back up to a modern version to check it out. Until then I'll run 4.8 as it at least works.
  • mtsarpilot my setup is Forerunner 920XT running 9.90 (updated last week), Samsung Galaxy S9+ running Android 8.0, GCM for Android 4.13.5. Not sure if that is the magic combo or not, but since the 920 and GCM were both updated around the same time, I couldn't pinpoint which, if either, was the fix or if it was the alignment of the moon and the stars.;)
  • Former Member
    0 Former Member over 6 years ago
    I'm having a weird problem where livetrack starts ok then stops showing on the map after 2.3 miles every time in the last few weeks. My phone says its still running and when i finish the ride the Edge 1000 say livetrack has stopped ok but its still runnning in the app - needs to be terminated manually.

    I'm running a Samsung J5 with Connect 4.13.5 - last few updates have not fixed this issue. It's frustrating as it looks like i've stopped to anyone checking on the map.

    I had the blue screen issue with 4.9 but it appeared fixed with 4.10 - now broken in a "new and exciting way"

    Wondering if its worth going back to 4.8 apk file.
  • Jazzy_B I don't have a fix for you, but that issue was reported here.
  • seilogramp, yes I was running 4.13.5 this morning and LiveTrack had the same failure of not transmitting any data after starting. Sounds like they finally made some progress if some of you are seeing success, but still have not nailed the issue as others are still seeing the failure. At the rate Garmin is tossing out updates, I'm guessing there are more updates coming as they continue to address this issue across all the phones I'm running a Samsung Galaxy S7, don't know what phones folks are having success with, may be different products. I'll give it a little more time for more updates then step back up to a modern version to check it out. Until then I'll run 4.8 as it at least works.


    Same here. Just tried to livetrack a bike ride with my Edge 25 and GCM 4.13.5 on a OnePlus6 and it fails. When you go to the tracking page it says something about no signal.
  • "Livetrack Failed" this morning.

    Which was the first time in a week or two the Edge 520+ has even acknowledged that it was supposed to be auto-starting livetrack.
  • Former Member
    0 Former Member over 6 years ago
    Well, after Livetrack having worked for a couple of rides, it's now back to the previous problem of reporting "No signal. Trying to reconnect." when my wife tries to check where I am on a ride. No changes at my end - same version of GCM, same FW on my Edge 1030. This feature is getting so unreliable as to be pretty damned useless. Before this "No signal. Trying to reconnect." problem, which has been happening on and off for several weeks, Livetrack was managing to report a position at latitude 0 longitude 0 in the Atlantic Ocean off the west coast of Africa...