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 Auto Start - THE working solution

Former Member
Former Member
I know that this (iOS) solution is wiping garmin's *** but it actually works.
Go to "Settings" > "Privacy" > "Contacts" and disable "Connect".
Now go to your watch and enable "AutoStart".
Next time you'll start your session, LiveTrack will finally work.

EDIT: It doesn't work :( ciq.forums.garmin.com/.../1469240.jpg ciq.forums.garmin.com/.../1469241.jpg
  • Thanks, great solution.
    Can you also point me to an app that does incident detection and emergency notification?
    Also great to take an additional battery with me. But no problem, only inconvenience.

  • Thanks. Now I have a solution for the spring and summer time until the problems are fixed.
  • Former Member
    0 Former Member over 6 years ago
    I have another solution that seems to be working ...so far.
    Yesterday I clean restored my iPhone Xs with the latest firmware. Here is what you should do to make it work:

    1. After installation, set your iPhone as a new iPhone (DO NOT COPY YOUR BACKUP FILES back to your iPhone!!) and manually install all applications from the AppStore (Connect, Strava, ..).
    2. Restore all default settings on your Garmin 935 device (this deletes all user-entered information and activity history from your watch).
    3. After pairing your device with iPhone, DO NOT ALLOW Connect.app to have access to your Contacts.app. When asked, just cancel it! VERY IMPORTANT, DO NOT SKIP THIS!!
    4. Now you can enable Auto Start and LiveTrack in Connect.app, set contacts that are already in the Contact.app and go for a run. If asked for the access to Contacts.app, cancel it!

    Today I did the test and it worked just like before. Automatically!
  • Has anyone heard from Garmin on this issue. This is getting old real quick especially when you add on the audio prompts not working and we shouldnt have to do some stupid workaround.
  • Former Member
    0 Former Member over 6 years ago
    I read today in another forum someone found the issue happened if they started while connected to Wi-Fi and then switched to Bluetooth. Starting off with Bluetooth caused no issues. Could this be the issue people in this thread are experiencing?
  • Has anyone heard from Garmin on this issue.


    No. But as the experts suggested, Garmin should not be bothered with this issue. There is a working solution which is using your smartphone for Livetracking and emergency contact notification.
  • Former Member
    0 Former Member over 6 years ago
    But as the experts suggested, Garmin should not be bothered with this issue.


    What "experts" suggested that Garmin shouldn't be bothered and why would you follow and recommend such foolish advice? By all means 26.2man_ contact Garmin if you haven't done so already.
  • I contacted GS today. They acted like they knew nothing about the issue. Asked for some diagnostic reports from the phone app. What a joke!
  • Former Member
    0 Former Member over 6 years ago
    26.2man_ You contacted Garmin today? Where are you located? Was it by email or did you contact them on the phone? I'm interested to know where Garmin responded to you on a Sunday. Unfortunately, Garmin Support is closed on weekends in the US. Anyway, I've found a phone call works much better as emailing has a tendency to go through the typical "What FW are you on?", and "Have you tried restarting your watch?", nonsense.