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?
  • LiveTrack worked perfectly for me today. GCM for android v4.13.7, Galaxy S9+, Forerunner 920XT. It had been consistently working with v4.13.5 until Sunday's server debacle (down for maintenance). Then I had a string of bad LiveTrack sessions until today, which is the first time with v4.13.7.
  • Former Member
    0 Former Member over 6 years ago
    Livetrack didn't work for me this morning - GCM 4.13.7, Pixel 2 with Android 9, Edge 1030 with FW 7.00. When my wife clicked on the invitation, the livetrack.garmin.com web page gave her a message about "no signal, trying to reconnect". And I also noticed that when I got home and stopped and saved the activity, the 1030 said "Livetrack ended" and then "ride uploaded", and the ride was there in GCM on the phone, so obviously still a connection between the two, but the livetrack screen in GCM didn't recognise that livetrack had ended - still had the stop livetrack red bar at the bottom of the screen.

    Conversely, my wife is running the same 4.13.7 version of GCM on a Sony XZ2 Compact, also with Android 9, and has an Edge Explore 1000. The livetrack invitation that I received from her this morning (we were riding at the same time in different directions) worked perfectly.
  • ------------------------------------------------------------------------

    Why did this start recently?
    Google started to require apps to target/targetApi (meaning it should behave like on being on this device even if on a higher version of android) at least Android Oreo since November 1, 2018 (https://developer.android.com/distri...lop/target-sdk).
    Up to version 4.8 the app had a targetApi of Android Nougat 7.1. With version 4.13.2 (first release after November 1, 2018) they started targeting Android Oreo 8.1. So even though running the app on Android Oreo before 4.13.2 would not have the same effect, because it won't have the behaviour of Android Oreo. But when switching the "targetApi" to Android Oreo 8.1, that behaviour starts to kick in. I actually checked the apk files myself to ensure this is the case, and I can confirm, that the targetApi changed from 25 (Android Nougat) to 27 (Android Oreo 8.1) between those versions.

    That as well is why livetrack still works on Version 4.12.3 should be the last version working correctly. I am now running on 4.12.3 and it seems to work :).


    This is excellent work from [pboos] and almost certainly explains exactly why LiveTrack is not working properly for the vast majority of users having issues with it at the moment.

    @GARMIN: I hope you are paying attention to these posts and have taken note of the information [pboos] has given you because it will probably lead you directly to the solution we need for this.


  • I reinstalled version 4.11 to have functional Livetrack.
    None of version 4.13 works
    It is urgent to correct, Livetrack is essential
  • When y'all experience "no signal" failures, do you only see that during the activity or does it also show if you look after the activity is complete?

    I'm asking because I'd like to know if I'm experiencing this issue, but most times no one looks at my Live Track while I'm out running. (I just track so my wife can find me if I disappear during a run. So far I've made it back every time. :)) After the activity is complete I see the track as expected.

    Thanks.

    -- Pete
  • P_W_P you'll see the no signal failure after the activity has completed. I use it for the same reason you do. Although, I asked that my wife to start wondering where I am sooner than 24 hours later. After that, the LiveTrack link is no longer valid. Then she'll need a search party and bloodhounds. My LiveTrack has been solid ever since the last update. I even checked it during the activity by installing an app that takes a screenshot of the LiveTrack site every 2 minutes or so. Then I can watch it later.
  • P_W_P you'll see the no signal failure after the activity has completed. I use it for the same reason you do. Although, I asked that my wife to start wondering where I am sooner than 24 hours later. After that, the LiveTrack link is no longer valid. Then she'll need a search party and bloodhounds. My LiveTrack has been solid ever since the last update. I even checked it during the activity by installing an app that takes a screenshot of the LiveTrack site every 2 minutes or so. Then I can watch it later.


    You are referring to 4.13.7 ?
  • Must have something to do with individual devices then . I am using a Forerunner 35
  • LiveTrack worked perfectly for me today. GCM for android v4.13.7, Galaxy S9+, Forerunner 920XT. It had been consistently working with v4.13.5 until Sunday's server debacle (down for maintenance). Then I had a string of bad LiveTrack sessions until today, which is the first time with v4.13.7.


    I had a partial success with Livetrack today.
    OnePlus 6, Android Pie, GCM 4.13.7, Edge 25. I was cycling a pre-prepared course. My wife could see where I was at any given time during the ride, but couldn't see the intended route (which used to be visible when riding a course.

    So YAY that it worked at all. This is the first success I've had with LiveTrack since late November. But it would be nice if it could also display the intended route like it used to.

    Will persist with further experimentation to see how stable it is.