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'm (again) back to the older version!!

    Go here:
    https://forums.garmin.com/forum/into-sports/garmin-connect-mobile-application/garmin-connect-mobile-android/1296103-gcm-previous-versions-download-link
    I've got the idea ... they only try to develop new things from dreaming persons...
    they
    don't care about current users and there problems (I know programming can be tough...but be backwards compatible!) Don't change things which were working wel ...(ex. Default MusicPlayer)
    I'm happy with my VivoActive HR, I'm happy with my Car Navigation ... but before I buy a new watch .. or update Garmin Connect for Android .. I don't know ...
  • Today I tested with 4.3.18, before I deinstalled the old version of Garmin, then I rebootet my mobile phone and reinstalled Garmin again. At beginning Live Track not worked, only error message "No Signal", but after 45 min. LiveTrack worked at last, but can't see recorded track before, just after 45 min. appear. For me after 45 min. starting too long, it seem 45 min. looking for signal.
  • My test with 4.13.8 today: Autostart worked, email received, working track on the webpage.. for 3 minutes. Then "No signal.." for 30 minutes until the Bluetooth stack on the phone crashed. Rebooted phone, manually started Livetrack again, webpage was updated to current position, tracked for 2 minutes and back to "No Signal".
    Back to 4.8 *again*. BTW I had not correlated my phones' BLE stack crashes with the newer GCM versions, but it does appear 4.13.x GCM plays a role. With 4.8, BLE is rock solid. Hope 4.8 keeps working for the lifetime of my Garmin devices.
  • Former Member
    0 Former Member over 6 years ago
    I've given up on Livetrack for the time being - it's just too unreliable to be of any use. I now use LocaToWeb on my phone to enable my wife to track where I am while out riding, and it's worked flawlessly since I installed it.

    Garmin seem pretty incapable of releasing new versions of software without breaking functionality that previously worked. Livetrack used to work without any problems.
  • I just did a chat session with Garmin Support individual named Jay. I gave him the URL for this and a number of other threads screaming about this issue and that it has been going on for over 6 months. He said there is a ticket in with the engineering team. Here is his exact words "I found a ticket for this issue with our engineers. Looks like they are expecting a fix to be released in early to mid February, barring any setbacks. " Let's see what we get.

    I like my Garmin products and have been a Garmin proponent for a long time, Like many of you, I have an engineering background and go out of my way to seek out solutions (that's why we are on these forums). I hope they get this absurdity nailed soon, as they are damaging their user base, loyalty, and future sales with this kind of absurdity.
  • I did another ride yesterday OnePlus 6, Android Pie, GC 4.13.8 with Livetrack. As in my previous post, it showed where I am like it should. It doesn't show the expected route (even though riding a preset course) like it used to. The other thing to note is that if you take a break (i.e. pause the timer) it only shows the route from after the break. So if you stopped after 5 miles of a 20 mile ride it would only show the route from 5-20 and not the first 5. Seems a bit odd, but at least it IS now showing where I am when out and about, which is the most important thing. Looks like we might be getting there :) It has the total ride distance and stats correct, but only shows the route after the last 'break' (I had to stop to wipe the lens of my rearward dashcam which got splashed).ciq.forums.garmin.com/.../1448101.png
  • Did you or someone else check to see during the first miles before the break if there was a track, or did the tracking only start to work after your break? If there was a track displayed of the first part but was then later erased, this might be meant as a kind of privacy feature.

    Edit: Just now starting to wonder, what position information does LT 4.13.x use? From the Garmin device or from the phone? I always assumed the location is from the device because other data from the device (heart rate) is included in the livetrack data, but if it was changed in later versions to use the phone's location data instead, it is no wonder that it almost never works for me (my phone's GPS is not that good). BTW I am still using 4.8.
  • Did you or someone else check to see during the first miles before the break if there was a track, or did the tracking only start to work after your break? If there was a track displayed of the first part but was then later erased, this might be meant as a kind of privacy feature.

    Edit: Just now starting to wonder, what position information does LT 4.13.x use? From the Garmin device or from the phone? I always assumed the location is from the device because other data from the device (heart rate) is included in the livetrack data, but if it was changed in later versions to use the phone's location data instead, it is no wonder that it almost never works for me (my phone's GPS is not that good). BTW I am still using 4.8.


    I certainly hope it is not using the phone's GPS data, that would deplete the phone battery by using it's GPS unnecessarily. Why do that when GPS data is already known on the watch which already has to send to the phone all the rest of the parameters you mention.

    I did a quick test using my VA3 and Samsung Galaxy S7 running GCM 4.8. It is NOT using the phone GPS. The phones GPS indicator has not come on in the 5 minutes the test is running yet LT is showing my location. Maybe this is a change they made in the later versions of GCM that are having the problem, I can't tell that as I'm not willing to update my GCM until this darned bug is confirmed fixed.
  • I did a quick test using my VA3 and Samsung Galaxy S7 running GCM 4.8. It is NOT using the phone GPS

    Thank you for testing!
    Maybe this is a change they made in the later versions of GCM that are having the problem,

    It was a very unlikely idea, but I still wanted to test it with both 4.8 and 4.13.x. But then changed my mind, wanted to avoid another update + downgrade cycle.
    Anyways, it was an illogical thought - LT should work no matter if people have location services on or not.
  • Former Member
    0 Former Member over 6 years ago
    Add me to the list of unhappy users. I'm using a Garmin 810 and Samsung Android Galaxy (Verizon). I believe it quit working about October or November of 2018. I uninstalled and reinstalled the Garmin Connect Android app on my phone. Re-paired the phone with the 810. No help.