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?
  • Besides LiveTrack finally working, can anyone detect any features or functionality that has been added since 4.8 (last time LiveTrack worked) that would cause me to want to leave the known stable 4.8 to move up to 4.15? What benefit do we get for the advancement?
  • I went on another ride of about 70km this morning, and this time the tracking worked without problem. However, I'll wait for successful tracking of a few more rides before declaring that the problem has been successfully fixed...


    Excellent. I just did a 33 miler and Livetrack worked fine for that. So that's a 50, a 2.5 and a 33 as my last three Livetracked rides. It's certainly a win as long as it keeps working reliably :) which as we now know, we can't take completely for granted. But I'm very pleased it seems to be fixed right now. Well done to the Garmin software devs for fixing it.
  • With latest app update:

    First attempt: "livetrack failed" notice
    second attempt: success
    Third and fourth attempts: nothing happens at all
  • With latest app update:

    First attempt: "livetrack failed" notice
    second attempt: success
    Third and fourth attempts: nothing happens at all


    What phone, android version and Garmin device are you using?
  • I went on another ride of about 70km this morning, and this time the tracking worked without problem. However, I'll wait for successful tracking of a few more rides before declaring that the problem has been successfully fixed...

    This morning's ride was yet another Livetrack partial failure.

    Here's the map from the activity upload to Garmin Connect, showing what we actually rode: https://photos.app.goo.gl/UVrb1PqoLq31eQmq9

    Here's the Livetrack map: https://photos.app.goo.gl/2D7XA12DwPmURTd97

    Livetrack gave up at about the 61km point, then re-established connection almost at the end of the ride (69km point), and draws a straight line between the two points.
  • This morning's ride was yet another Livetrack partial failure.

    Here's the map from the activity upload to Garmin Connect, showing what we actually rode: https://photos.app.goo.gl/UVrb1PqoLq31eQmq9

    Here's the Livetrack map: https://photos.app.goo.gl/2D7XA12DwPmURTd97

    Livetrack gave up at about the 61km point, then re-established connection almost at the end of the ride (69km point), and draws a straight line between the two points.


    That doesn't look so good.:( On my ride yesterday I did get a notification on my Edge 25 that Bluetooth connection had dropped, but it was on a straight road and about 1 minute later there was another one saying reconnected. This is the first and only time I've ever seen that happen. I wonder if the cause of yours could be related? If the two devices stop communicating, it just interpolates between the last known good point and now? Was your route properly recorded by the bike computer at least?
  • Today I testet my bike trip, arround 100 km. It worked fine, I'm happy now. But I still think it took too long time until the bug is fixed by Garmin.
  • Feedback: Connect v4.15

    My setup: Android 8.0.0 on Samsung Galaxy S7, Edge 520 (latest firmware)

    Ride Distance: 71km


    Tested 4.15 this morning and it looks like LiveTrack is finally working again.

    1. Auto started without issue and sent LiveTrack notification emails and Strava Beacon SMS's automatically as expected.

    2. I noticed that it took it a while to start showing my location initially. When I went to the link emailed by Connect or the Beacon link it didn't initially know where I was, but then after about a minute or so I refreshed both views and it suddenly showed my correct location. I suspect this has something to do with the fact that the location is uploaded to some remote service which then renders it and shows it and that initial upload is delayed. With something like Glympse it immediately shows your location when you start the track, but this isn't really a major problem, at least now it does lock on after a very short wait and thereafter it seems to keep tracking as it should.

    3. Multiple people who were sent the Beacon links via SMS reported that it worked correctly today each time they checked it, but it is necessary to manually refresh the view to see the location update correctly and see the very latest reported location.

    I also stopped and checked it myself a few times using the emailed Garmin link and the Beacon link, and both seemed to be tracking correctly, but I did also have to manually refresh those views.

    4. When I stopped the ride and saved it on the Edge 520, it immediately ended the LiveTrack session automatically, as expected.

    5. I have the "Extend for 24 hours" option ON and looking at the map it draws the route looks 100% correct with nothing missing, and the final distance (71.03km) and Total Time indicated above the map are correct.

    6. The waypoint markers on the final map are, however, NOT correct.

    For some reason it tracked correctly to the 10km mark where it created the 2nd waypoint marker, then it seems to have restarted from 0, and then tracked the remaining 61km correctly and set correct waypoints at 5km intervals for those remaining 61km, but I didn't stop the track at any point or stop the bike where it reset itself to 10km so I have no idea why it decided to reset to zero for no apparent reason.

    This may be a small bug in the waypoint generator or something. Ultimately the correct number of waypoints were created at the correct places on the map, at
    5km intervals, it just seems to have started counting from zero again at the 10km mark.

    The overall distance recorded is correct though.

    SUMMARY

    Apart from the minor weirdness with the waypoints on the final map when Extend for 24 hours is turned on, everything seems to now be working as expected again.

    Some significant progress has definitely been made and it looks to me as if the primary issues have been resolved properly now, but I'll need a few more rides to verify that.
  • Feedback: Connect v4.15

    4. When I stopped the ride and saved it on the Edge 520, it immediately ended the LiveTrack session automatically, as expected.

    5. I have the "Extend for 24 hours" option ON and looking at the map it draws the route looks 100% correct with nothing missing, and the final distance (71.03km) and Total Time indicated above the map are correct.


    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!
  • 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!