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?
  • IIRC, Livetrack worked perfectly fine for me on every ride in December.... of 2015.

    I had a 13-hour ride on the winter solstice that year that I continuously livetracked. Same Phone. It worked perfectly.

    3 years ago.... we're going backwards here guys!
  • Former Member
    0 Former Member over 6 years ago
    All my rides since my last post have failed. I normally start LT manually, but that stops after a couple of miles, although my phone is convinced its still running - and my Edge 100 says its stopped at the END of the ride but thats not correct either. I tried autostart for a change but that didnt kick in until 30 miles into my ride! - looking at the map i was stuck in the sea off Africa again. I'm probably going to go back to 4.8 (again) although its a major pain to remove the app and data and set it all up. If that doesnt fix it then who knows............
  • I'm probably going to go back to 4.8 (again)


    Can you let know if that version consistently solves the issue for you?

    I was happy with the last version of Connect that seemed to solve this, but yesterday it was again "No signal. Trying to reconnect.", then 15 km into my run the Livetrack started to work.

    Livetrack has become a much appreciated safety feature. No doubt I'll figure something out as an alternative (some phone app or some other means of reporting position), but this was really convenient and easy to use. I really hope there is a Connect version that returns Livetrack to fully operational and reliable.
  • I've gone back to 4.12.3 which was the last version that worked ok for me and all is well again.
  • Can you let know if that version consistently solves the issue for you?



    I rolled back to 4.8 a couple weeks ago and it has been rock solid. I purchased a VivoActive 3 two weeks ago and went to 4.13.5 as a test case. LiveTrack failed for it as well as my Edge 520 and I see no added benefits in 4.13.5 so I'm back to 4.8 and happy with it.
  • Since I started this thread I thought I'd post and throw in a comment on my current experience with LiveTrack ... again.

    Yes, it's broken. Again!

    This is actually now beyond ridiculous. How is it that every 2nd or 3rd release of an update breaks LiveTrack completely?

    And yet, reverting to an earlier version of Connect solves it every time, which clearly indicates that it's not the hardware and it's something that the developers are doing to the connect app.

    I'm a developer, and I just outright fail to understand how they don't have a comprehensive suite of unit tests and test scenarios by now that can verify if they have broken LiveTrack or not BEFORE they release a new update.

    Come on Garmin, it cannot be this hard to stop breaking something that is working perfectly in several versions of the same app in a row.

    I had reverted to 4.8 and everything worked perfectly, then after a while I let it upgrade to a newer version, and it all still worked perfectly, and then just recently I allowed it to update to the very latest version, and everything blew up again and LiveTrack is once again a complete disaster and unusable.

    I've now resorted to installing Glympse again, and running that, just so I'm sure that my family can track me properly because I'm doing long solo rides and I'd like them to be able to find me if things go pear shaped while I'm out on a ride.

    Looks like it's time to revert to 4.8 yet again and see if I can get LT back online again, but really ... this should NOT be necessary anymore.
  • This is driving me nuts.

    Worst part is that the last word I could find from Garmin is from August: " This is a high priority issue and we will post updates in the forums when the issue is resolved."

    Thanks Garmin, but since this is a safety issue for me, it may be time to find a new watch to replace my 935 ... from a company that stands behind their product.
  • I've now resorted to installing Glympse again..


    Fun fact: Garmin uses (or used, page is from 2013) Glympse for their StreetPilotOnboard and NAVIGON apps: https://www.garmin.com/en-US/blog/au...-foursquare-i/

    (I was checking what Glympse's business model was before installing a free app that has no adds, wondering what they are getting in return).

    I have Glympse on my phone as a backup now, I start my run/ride and if I don't get a copy of the Livetrack email, or the Livetrack shows GPS location 0,0 again, then I can start Glympse. A bit of a hassle but well.. I guess it's worth it, for the peace of mind. Livetrack works about 50% of the time for me these days.

    Edit: Suddenly realized that Glympse, and all other apps that use the phone's GPS, drain the battery pretty quickly.. so all the more pressing need to get a real fix for this Livetrack issue.
  • Another quick update.

    I reverted to 4.8 of Connect on my phone and ..... viola!

    Instantly fixes everything again.

    LiveTrack worked perfectly immediately, and works perfectly every single time I trigger it now.

    At this point I think I'm just going to keep it on 4.8 permanently and never upgrade it ever again.

    I'll just manually update all apps on my phone from now on, it's worth losing auto update capability of all my other apps just to guarantee that Garmin doesn't break Connect on a regular basis!

    Reminder to all, go here to download older versions of connect for Android:

    https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=garmin+connect


    And go here for version 4.8 specifically:

    https://www.apkmirror.com/apk/garmin/garmin-connect-mobile/garmin-connect-mobile-4-8-release/


    NOTE: Others on this forum have reported that more recent versions than 4.8 do actually also work correctly, but I don't have the time or patience to figure out what the latest reliable version is for me and I KNOW that 4.8 is 100% reliable and is not lacking anything I require, so I'm sticking with that. Feel free to experiment with other versions since 4.8 to figure out how high you can go up the version chain before you encounter another epic testing fail on Garmin's part.
  • 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.


    I'm having the EXACT same issues:

    1. I start livetrack manually before my ride, then when my ride is done I save and upload the ride. THEN the livetrack is still running in the app even though I don't use the "extend livetrack" feature.

    2. The live track feature is just a wreck. I got it fixed once, nothing I did, it just started working again one day. But now it has just stopped, and my recipients can no longer see the tracking map.