This is the 3rd-generation Garmin Instinct Solar that I've owned. I generally like the model; I keep upgrading as new generations of the model become available, in hope that its one significant flaw will have been remedied. That flaw? Well, I'm an open-water swimmer, and the Garmin has a lag in beginning to log distance (via GPS) after starting the watch at beginning of a swim. It only starts logging after I've swum about 30-50 yards. It never really catches up at the end of the swim If I delay pressing "stop" at the end-of-swim, it will continue to log more distance as I'm standing there -- so it, in effect, is trying to catch up. But what that means is the elapsed time for that swim is now in error because I've delayed "stop" to allow logged distance to more-or-less 'catch up.' So I have a choice: either correctly log elapsed time for the swim, or (sort of) correctly log distance swum. It won't do both. I've tried all the suggested remedies: I use the GPS setting that employs all three GPS systems, plus multi-band. I've waited 10 minutes after the watch has acquired my starting location, before beginning my swim. I've changed data acquisition frequency to 1-sec interval. None of this has solved the problem. I now wear two watches when I swim -- one to give accurate elapsed time, and the Garmin Instinct 3 Solar to log distance and route (I leave it running for a minure or so after I've finished my swim). There's just something lacking with the algorithm used to log distance for the open-water activity app. BTW: this lag in distance logging occurs if I use the open-water app out of water -- i.e., just walking down the street with that open-water activity running. It has nothing to do with difficulty in maintaining GPS contact while cyclically submerging the watch during swim-stroking. I'm just walking down the street with it, and finding distance-logging delay for which it never catches up.