I have an Edge 520 and an iPhone SE. Incident Detection has worked perfectly on this for the last 18 months or so. It is now, fundamentally, broken.
It appears that, thanks to a recent update, in order for incident detection to work, your mobile device must have a network connection at the point at which you turn on your cycle computer. If your mobile device has no valid network connection at that point, the Edge reports that incident detection is being disabled because there are no contacts set. (When of course, there *are* contacts set, but for some reason the mobile device now has to read them from the network rather than locally from the device itself.)
This is, frankly, a stupid decision. I go mountain biking most weekends, and the car park where I leave my car - and where I turn on my Edge - is in a poor signal area, so 9 times out of 10, the Edge boots up, asks the mobile device for contacts, the mobile device can't find any, and I get told that incident detection is being disabled. Which then means I have no incident detection for the duration of that ride, the majority of which is in areas where there is a perfectly acceptable signal; so incident detection *could* work.
There is no sensible reason I can think of to require a network connection in order to store three contacts. I guess it might allow contacts to be synced between multiple phones, but most users surely have one phone and multiple Garmin devices (Edge, Fenix etc), which all sync with the same phone. Even if there is no mobile signal at one point on a route, assuming that there will be no mobile signal anywhere else on that route, and that it is therefore reasonable to disable incident detection completely, is a really bad idea.
Please go back to the way this worked before - this change has made incident detection far less useful than it used to be, and I cannot for the life of me work out what advantages it offers to anyone.
