How much battery drain is there when using this (I know it's hard to generalize, but even specific examples would be helpful). Garmin live track isn't perfect, but because it shunts the GPS responsibility to their hardware, the phone battery impact is pretty minimal (or at least minimized). That would be my biggest worry with any fully on phone option - draining the battery too much so that I can't use my phone in an actual emergency.

The dead man switch feature is interesting, although I think I'd want the cancel/pause when I reach a destination, otherwise I feel like I'd probably forget to turn it off a bunch. Is there some audible/vibration alert with a cancel window before the alert fires off on your smartphone? If Garmin's incident detection didn't have that I'd have sent out a bunch of false positives from hard braking when they were first rolling it out (fwiw it seems better these days).

Battery: The battery drain is about the same as if you just had your navigation running, with the screen off. The biggest factor is actually screen usage. I dim the screen quite a bit, but the user can further reduce brightness so that the screen is almost off. I'll try to take some data over the next few days and add something to the FAQ.

Alerts: I do have a pre-alert setting that defaults to 5 minutes, but you can change it to whatever you like. When that alert is hit, the phone will vibrate. I also send you a pre-alert message as a email. (Delay on sending email is usually less than about 30 seconds; I.E. pretty fast.) That will cause you to get a notification on your phone, smartwatch, etc., that you have an email.

And I agree with the need for auto-cancel, because I don't want to send false alerts.

---

2015 USAT Long Course National Champion (M50-54)