Update

I use my Garmin Descent MK2s after purchase in summer last year almost daily. I appreciate its versatility and multi-purpose functionality. However, after this time I realized that GPS accuracy really need to get enhanced. For a while, my regular 8.5 km runs (and I also did „measure“ it by mapping apps) will be recorded up to 250m lower with GPS+GLONASS and GPS+GALILEO. That has certain impact on calculate sport metrics. I also realised, that last update of FW occured 6 months ago. For such an expensive watch this rather low attention is disappointing, one may ask what the new models such as EPIX or Fenix 7 will experience. Dear Garmin, please rethink your engagement towards your top models.

  • Sorry seems it can't be adjusted. I was thinking of my aeris F11.

  • I don't know why I am even bother to try help here, as this as I will only get more hate.

    But in settings -> System -> Data Recording - change it from "Smart" to "Every Second".   This will improve your GPS accuracy.  An detailed explanation of why/how it will improve GPS accuracy can be found here:

    www.youtube.com/watch

  • I‘m sorry you felt being bashed here, which shouldn‘t be! It‘s ok you feel fine with your device. However, other aren‘t and complain about the lack of support for their product. The complaints are likely not critical but annoying and are opposite to what Garmin advertise. It‘s probably only a minor effort for Garmin to fix inaccuracies in GPS or dive detection etc. But not even showing a response is ignorant and hard to understand as this scratch against Garmins reputation as a reliable manufacturer, seller, etc. 

  • 1. There is a big difference between D4i and Mk2, the D4i is only to dive, it is a dive computer only! The start diving of the D4i or another models, obvious, works fine, however, we talk about the smartwatch/dive computer that we use for many activities and the start diving must be different than other dive computers.
    2. I don`t want sell my MK2i! I want the Garmin fix the erros and update some functions the the many users talked about:
    a) Set deep start diving
    b) Safety stop (after DECO don`t show)
    c) Sleep score don`t show on Garmin connect.

    d) GPS accuracy 

  • There is a big difference between D4i and Mk2, the D4i is only to dive, it is a dive computer only! The start diving of the D4i or another models, obvious, works fine, however, we talk about the smartwatch/dive computer that we use for many activities and the start diving must be different than other dive computers.

    This is exactly the point.  It is supposed to be a "smart" watch that you wear all day.  It should be able to correctly detect non-dive activities.  It shouldn't start a dive activity if I dive into a pool or even reach down to grab a dropped fin.

    This behaviour has already caused some serious problems for some people.

    Let me give a fictitious but entirely possible scenario (which isn't all that different from what some people have reported).

    You plan 10 day trip on a Liveaboard in a tropical location where you will be diving 4 times a day.  A month before the trip you do a tech course which requires you to set the Descent to Gauge Mode.  This was your last dive before the trip. You fly half way around the world.  You get on the boat which sets sail.  It stops on the way for some lunch.  After lunch everybody goes for a swim.  You dive into the water and this triggers the Decent into dive mode.  Because the last dive you did was Gauge Mode, that's what starts.  You are now stuck in Gauge Mode for 24 hours, even though you haven't actually dived in a month and the first dive of your trip is only 18 hours away.  You now have an expensive dive computer that is nothing more than a bottom timer.

    I have seen reports very similar to this and the people were not happy at all.

    A few years ago, I documented a very simple method Garmin could use to accurately determine if a dive was actually a dive.  They said they'd look into it, but that was the last I heard and nothing had been implemented.

  • So you are saying that the Smart mode is not that smart and shouldn’t be used as default. They should totally fix the Smart mode if it causes a 10% distance error on your typical run GPS recording.

  • If you cannot understand the difference between the "Smart" and "every second" mode after watching the video explanation of it - Then there is nothing I can say that can help you. So we can stop here. I knew it was a waste of time to post that solution anyway, believe me.

    My watch has never had any GPS issues, nor do the other 3 garmins (1 fenix6 solar and another decent)  we have in the house here. I always Smart. I have about 100 runs are always accurate (except maybe once of twice during big storms). last night i used "per second" and also accurate, though I can see gps track is far more detailed. 

    I have provided now 2 solutions for runs

    1. building a course if you know the exact track (to remove all varibility in the nature of GPS)

    2. Using per second, (if more data points would make you track more accurate).

    However those suggestions seem wildly ridiculous here. So ridiculous even dive diction and who knows what else will be used as an excuse on a topic about GPS track? 

    I apologies deeply for posting on this thread. Looking back I was stupid to suggest those solutions. "yes, garmin bad, garmin must fix"  - got you guys, agree with you all. Thanks 

    Good bye!

  • I’ve read the manual before and I’m pretty sure I knew what it means. Smart mode means it should record when parameters (speed, altitude, location, etc) change. Inaccuracies happens when the watch doesn’t record even when parameters change, which is stated as when it should record.
    Well of course there might be some tiny trade offs and it might not be 100% smart. But I always get 5-15% shorter distance when I compare the recordings on Garmin vs my iPhone and Apple Watch, especially if I hike forest terrains, or run around the block clockwise as opposed to counterclockwise.

    Issues can be worked around, as you mentioned. But they are issues anyway. Workarounds involve unnecessary burden on the user to create routes in advance or accept more battery drain and much larger file size for very long exercises.

  • Also I don’t know why you are so upset with other users posting about their dissatisfaction. You are happy with your devices, fine; you haven’t seen the need to call for more improvements, also fine. There are users who have run into issues, and would like to see issues addressed. It’s okay to feel differently towards the gadgets you purchased.

  • Is it still stuck in Gauge mode if you reset your tissues?

    Descent Mk2/Mk2s - Resetting Your Tissue Load (garmin.com)

    I'm not aware of any tech courses which would require you to set the Descent to Gauge mode. You can use the Multi-Gas activity. (Although that activity has a defect in the CNS% load calculation which causes some annoying false alerts.)