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

Live Track not working, Garmin 510

Former Member
Former Member
For the last 2 weeks almost, I've had no luck with the livetrack. Everything looks fine when I start it, and get all the normal notifications on both the phone and the Garmin 510. However, when I get home, I try to save and upload the ride, and it shows "upload failed". I have to physically upload through the USB port now. I've been made aware that my livetrack shows "unavailable" for the entire ride as well. I have never had an issue with this unless for some reason the Bluetooth connection is lost which hasn't been the case. I'm running the most current update on the 510, and the most current OS on my Samsung Note 5. Getting frustrated with this as I need that safety blanket on my long rides so my wife can keep track of my progress.
  • Former Member
    0 Former Member over 9 years ago
    Live track

    I am also experiencing the same problem , it worked very well last year , but I have had no success in the last few weeks
    Please let me know if you find the solution,
  • Former Member
    0 Former Member over 9 years ago
    Live Track Garmin Edge 810

    I'm having exactly the same problem with my Edge 810. Live track worked perfectly last season and for my first few rides this year. Now the emails go out (but not always) and the email link brings up a map with a pin showing my start point and a message saying Live Track is trying to reconnect. Sometimes 20-30 minutes of my ride shows up on the map before it disconnects, sometimes it just shows the start point. This is very frustrating because my wife likes to know where I am on long rides. I have emailed Garmin tech support twice and got the same response both times, "Engineers are working to correct the issues with LiveTrack." This sounds like a brush off. I tried deleting the Garmin Connect app from my phone then reinstalling and reconnecting the 810 - this did not help at all, so don't try it unless you want to lose all your ride data. It would be great to hear if anyone comes up with a solution to this.