I recently went on a trail run and was surprised when I saw how far my battery level had drained only an hour or two into the activity. I realized I had forgotten to turn off LTE and was in a no-service area, so the watch kept searching for LTE signal and burning through battery. After I turned off LTE, the BatteryGauge widget confirmed that was the source of my high power drain.
Though this is a somewhat predictable issue and we can manually turn LTE on/off to prevent high drain, I think it would be a great feature for the software to manage this better, somehow. Perhaps during an activity (or certain kind of activity, like trail running, that may be more likely to occur in a service dead zone) if there is no LTE signal after 10 minutes it will auto shut off or prompt the user to turn it off. Or maybe it can auto turn off LTE when an inReach is connected.
Similarly, does anyone know how much battery is drained when the watch is looking for a paired inReach device? I only use my inReach occassionally so I get concerned about the battery hit when I don't use it but see the watch searching for it when I do a run without it. Should I be unpairing and re-pairing it each time I use it so my watch isn't constantly looking for it?
