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?
  • 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...


    After speaking with support and getting the "turn your edge off and on again, I went from "no signal" to a track that shows me riding in the middle of the Atlantic.
  • And after about 2 weeks and over 10 perfect sessions, it's back to "No signal, trying to reconnect", and the livetrack session does never stop unless I end it manually. Is there really no way to fix this? It is perefctly fine with me to make it less automatic or less user friendly, it is a safety thing, it should just work every time.
  • Former Member
    0 Former Member over 6 years ago
    I have been chatting with support and let them know about my findings. I wonder if it will make it to the developers. When chatting with the support I went through different scenarios to show him when and why it stops sending data to livetrack. He actually tried the same (on exactly the same phone that I had) and sad that for him it worked fine. So I wonder if it is just me or if he had a newer version (I hope he had a newer internal version giving me hope).

    If the app is kept open when starting and the screen never turns off (garmin livetrack screen always the one visible) then it continues working correctly! But as soon as one switches to another app or the screen turns off, livetrack stops working.

    My devices:
    - Phone: Google Pixel 2, Android 9.0, Garmin Connect 4.13.5
    - Watch: ForeAthlete 935 (Japan version of Forerunner 935)
    - Internet connection on Phone is through a pocket wifi router. Phone is connected, but it is through WiFi instead of Mobile Data. Not sure if this makes a difference though.

    I really hope they get this fixed soon. For now I just use Glympse which does the job as well. Even though I would like the graphs including heart rate and pace.

    And like most, I use this for emergencies. When my wife notices that I am not running anymore (maybe fell, passed out, ...) she will try reaching me, and if she can't, call an ambulance.
    So having an emergency feature just stop working is REALLY BAD!

    ------------------------------------------------------------------------

    Now as an Android developer, I am guessing the following could be a reason. Of course there could be other reasons as well. The one below seems the obvious one to me though because it is can easily happen when a developer does not read documentation of Android correctly when upgrading the app to run on newer devices (which is required now on google play).
    But because the app does not work for me even on version 4.8, this might not apply to me. But maybe this here is still the reason for why so many others have problems with LiveTrack.

    Now why this behaviour?
    Why? Android starting with Android Oreo handles BACKGROUND apps and FOREGROUND apps differently. As soon as the screen turns off or the app is not visible anymore, the app goes into BACKGROUND (unless a service with a notification keeps it in the foreground). When in the Background, gps location updates do not get sent anymore (or only very rarely).
    For more information on this behaviour (and how to fix it): https://developer.android.com/about/...ocation-limits and https://developer.android.com/about/...reo/background

    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 :).
  • Since the latest update I was no longer getting the "Livetrack Failed" message at the device, so has it been fixed at last?

    Nope... It was sending my wife a map of the mid-Atlantic ocean again and a "connection lost" message, even though it looked like everything was fine at my end.

    Not cool. It it doesn't work, tell me. This is on Android-M, FWIW.


    So.... still longing to re-live the technological achievements of 2015.
  • Sorry, please disregard this post. It was total nonsense. All my Livetracks are titled Live Activity 12/6/18.

    The app reverts to a default name Live Activity 12/6/18 if I leave it blank.

    Leaving the original text of my post in for reference and my own embarrasment.

    The only thing I still find strange is that the message "activity expired" is displayed already after 30 minutes, whilst I have "extend livetrack on" (24 hours) enabled.


    --------------------------------------
    New issue with Livetrack: the activity starts, watch displays Livetrack has started, email is generated, but the email contains the text "Live Activity 12/6/18" and a link to a (of course) expired activity. The page initially displays a map (no coordinates, so no location on it) and contains this text in the top left corner of the screen: [my name] (Live Activity 12/6/18) Started at 3:05 PM GMT+0100. The time is OK, that's when I started my last attempt.
    Subsequent attempts to access the page after the activity has ended, result in an error page "expired activity".

    The actual links are all different, it is just that they all refer to the same activity from December.

    BTW I had adb logcat on a laptop and could not see anything obviously weird in either the connection between Forerunner and phone, or from the mobile app to the Garmin servers.

    I'd like to know (just curious) if others that have this issue with world map displaying without a location, and/or see the "trying to reconnect" message, have a correct date on the page and in the email.

    Yesterday I did have a link to a valid activity, but only one location point was recorded before the "connection lost" occurred. This seems to be something else.
  • Haven't been using livetrack for a while. Tested with f5, f5s and 1030 today. Nothing works :(
  • Former Member
    0 Former Member over 6 years ago
    According to https://forums.garmin.com/forum/into-sports/garmin-connect/1430825-no-signal-trying-to-connect-live-track?p=1441051#post1441051 LiveTrack was down yesterday. But seemed down even afterwards (and maybe still down)? But even when he wrote that it seems to be up again, it didn't work for me. I got the e-mail, but nothing got tracked (even with screen on and everything).

    PS: https://connect.garmin.com/en-US/status seems to not say anything even though it clearly doesn't seem working for multiple users.
  • pboos Was referring to Garmin Connect. You can now upload activities, etc. LiveTrack is not working.
  • Installed connect 4.8 and livetrack works.....
  • Installed connect 4.8 and livetrack works.....


    Nothing new since 6th December 4.13.5. Hoping this will get fixed soon.