Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Version 6.10 Fixed an issue with auto lock not locking instead overfixed auto lock not during activity

ErnstBk
over 4 years ago

Since update to 6.1 auto lock, set to lock not during activity, locks the phone after selecting a walk activity while waiting for GPS to lock in. Once GPS has locked in the vivoactive has to be unlocked first to be able to start the activity.

  • 0 over 4 years ago

    I am considering to scrap the vivoactive 4 because it seems that Garmin does not care about this buggy firmware release. Everytime I start my activity I take one step while pressing the start button to be reminded that I have to stop to unlock the phone first. This is a greatly dissatisfactory experience.

  • 0 over 4 years ago

    Indeed, another unnecessary change they made. Hope they roll this one back along with al the other changes.

  • 0 over 3 years ago

    FW 6.2 has come and gone, now FW 6.3 has come and the problem still exists. Doesn't anybody at Garmin care about customer satisfaction ?

  • 0 over 3 years ago in reply to ErnstBk

    I like the lock during normal usage as my settings used to get changed frequently during showering with my Vivoactive 3, but it is annoying having to double stop each workout.  Glad I don't use the 4 for laps as that would really drive me nuts.

    Hopefully they will fix it in 6.4 

  • 0 over 3 years ago in reply to ErnstBk

    Even 6.33 did not bring any improvement, did report this problem to '[email protected]' but that was a waste of time because 6.40 still has this fault. I will think twice getting another Garmin based on this experience.

    As a reminder, the problem is that the phone automatically locks while waiting for GPS to lock in with auto lock set to "not during activity" causing the need to unlock before the activity can be started. This was not a problem before 6.10.

  • 0 over 3 years ago in reply to ErnstBk

    Same problem with 6.42