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

Edge 520 / iPhone x Connection Freezing Device

Since the latest Garmin Connect app update, whenever my phone (iPhone X) connects to my Edge 520, the 520 freezes and becomes unresponsive. The only way I can rectify is to remove the device from my Garmin Connect profile, disable Bluetooth on my phone and hard reset my Edge 520. Tried reinstalling the app but not helped. Anyone else having this issue?
  • Former Member
    0 Former Member over 6 years ago
    Before I had this issue my Garmin Edge 520 was saying the Incident Detection had not been set up even though I had set it up and had emergency contact saved. Initially I ignored this issue, then today my Garmin started freezing when the phone connected, I tried restarting it and it did fix once.

    Then when I tested it again (turned it off then back on) to see what would happen it froze once again when the phone connected. I thought maybe there is a connection between the incident detection issue and the garmin freezing issue. With this in mind I deleted all the contacts I had on my Garmin Connect app (I only had the 3 emergency contacts) thus deleting the contacts from the Incident Detection. I then reset the Incident Detection by re-adding the contacts to my garmin connect app and adding them as emergency contacts.

    Since then I have tested my garmin 520 and it no longer says that the Incident Detection is not set up and it has not frozen when the phone connects. (I have switched it on and off a number of times now to see if it freezes again but it appears to be working fine fingers crossed).

    Nevertheless it should be in Garmin's interest to provide a proper fix to this issue, especially given the number of users moving to other bike computer suppliers.

    I hope this helps (It seemed to work for me, can't guarantee this will work for everyone)




    If the Forum Moderator is reading this, they need to pass this along to the IT bug fixers at Garmin!

    I posted in page 1 of this forum string that I too had the freeze up issue with Bluetooth. I tried what EddMH suggested above and it no longer freezes up. The good news is I am now able to connect with bluetooth to my Apple 10x.

    Thank you EddMH!
  • Just did this and now it’s working fine!! Many thanks!!


    Thank you tested now on my iPhone Xs and it seems to be working. Tested on my Huawei Mate 20 Pro and it worked. Moved back to iPhone (You have to re-pair the device) works 100%
    Multiple on and off switch of the Garmin and still all is fine.
    Thanks for sharing this
  • Former Member
    0 Former Member over 6 years ago
    Can confirm that the EddMH fix appears to have worked for me. Haven't tested it on a ride yet though. I would like to see a proper fix from Garmin before I start using incident reporting again though.
  • Former Member
    0 Former Member over 6 years ago
    Tested today on the road the EddMH solution. No problem, all works very well. Problem resolved. Thanks to EddMH again!
  • Former Member
    0 Former Member over 6 years ago
    Same issues here iPhone 8 plus. Trying the emergency contact removal !
    :)

    Yep all working !!! GARMIN SORT THIS !!!!
  • Before I had this issue my Garmin Edge 520 was saying the Incident Detection had not been set up even though I had set it up and had emergency contact saved. Initially I ignored this issue, then today my Garmin started freezing when the phone connected, I tried restarting it and it did fix once.

    Then when I tested it again (turned it off then back on) to see what would happen it froze once again when the phone connected. I thought maybe there is a connection between the incident detection issue and the garmin freezing issue. With this in mind I deleted all the contacts I had on my Garmin Connect app (I only had the 3 emergency contacts) thus deleting the contacts from the Incident Detection. I then reset the Incident Detection by re-adding the contacts to my garmin connect app and adding them as emergency contacts.

    Since then I have tested my garmin 520 and it no longer says that the Incident Detection is not set up and it has not frozen when the phone connects. (I have switched it on and off a number of times now to see if it freezes again but it appears to be working fine fingers crossed).

    Nevertheless it should be in Garmin's interest to provide a proper fix to this issue, especially given the number of users moving to other bike computer suppliers.

    I hope this helps (It seemed to work for me, can't guarantee this will work for everyone)


    Brilliant EddMH! Problem solved! Many thanks.
  • Former Member
    0 Former Member over 6 years ago
    Same issue too iPhone XS Max (iOS 12.1.4) and Edge 520 (12.90)
  • Former Member
    0 Former Member over 6 years ago
    THX for the fix EddMH; pure genius!

    Note to Garmin tech: I had 3 contacts + 3 emailaddresses stored in my contact list . Maybe this was caused by a cross sync resulting in a violation of the Max 3 contact rule stated by the app?
  • Thanks for the fix EddMH. In my case (maybe because I'd already reset everything and incident detection was already off) all I needed to do was remove all the contacts. My 520 was still freezing with incident detection switched off, so it must be some sort of contact conflict as fondph says. I note that the app update re-syncs these, that may cause the issue.
  • Former Member
    0 Former Member over 6 years ago
    I've been having the same issue for about 10 days. For a couple of weeks prior, I couldn't get my mac to recognize my Edge 520 when plugged in for an update. Then the freezing started. I could only then get my 520 to reset by deleting the Garmin Connect app on my phone and then doing a hard restart while plugged into my computer. It worked for one ride, but then when I added Connect back onto my iPhone 7 to try to upload my ride, it went right back into the freeze. I will try deleting contacts in incident detection. I looked online when it first happened and not again until now - glad to know I'm not the only one, but super frustrating waste of time.