Profiles no longer save all settings?

Hello.

I short question. I observe since the last update 9.20 the behavior that some settings are no longer saved in the profile. Example: Typically I use two profiles. One for biking and one for hiking. Many settings are profile based and change when I switch profiles. But not the “Auto Lock Screen” setting (witch is useful for hiking, but not for biking in use with the bicycle mount). Can anyone confirm this behavior? I am of the opinion that it had still worked before the last update.

Best Regards

Chris

Top Replies

atlas_cached over 3 years ago in reply to Aussie-Muzza +1

Known issue, for a very long time, Garmin is not interested in fixing it.

All Replies

0 ConiKost over 3 years ago

Yes. I had this issue too and needed to do a full master reset. After that, the profiles where working correctly.

0 Maingray over 3 years ago

If I change profiles with different Routing methods, I have to manually reset the destination for the routing to work as per the profile.

0 Chris-Bayern over 3 years ago in reply to ConiKost

Thanks. I was afraid that a reset would be necessary.

0 Chris-Bayern over 3 years ago in reply to Maingray

Good to know. I was not aware of that. Thanks

0 Chris-Bayern over 3 years ago

Hello

a short update. I made an full reset. But is still the same. And it looks like only this parameter (“Auto Lock Screen”) is affected. For example the setting „Battery Save“ is saved in the profile. Can anyone confirm this?

0 Aussie-Muzza over 3 years ago in reply to Maingray

I am having the same problem. I have one profile to point directly to the geocache and another for automobile navigation. If I change from my Geocaching profile to my driving profile, it changes to turn by turn routing. But once close to the cache, when I change back to my geocaching profile, the turn by turn routing remains. To get back to direct routing, I have to select the cache again. I have only recently noticed this behaviour.

0 atlas_cached over 3 years ago in reply to Aussie-Muzza

Known issue, for a very long time, Garmin is not interested in fixing it.