Lock on Road enabled without user input [Bug 8]
Posted: Sun Sep 24, 2023 7:42 am
Unfortunately there seems to be a bug added in 2.80 for the Gen 1 etrex 32x.
The setting for Lock on road enables itself (setting = yes) at seemingly random occasions.
(MENU - MENU - Setup - Routing - Lock on road = YES/NO)
I never use lock on road, but was surprised at least 3 times since the update to firmware 2,80 that suddenly the map showed that i was on some road or path, when in fact i was on some yard or in the forest. I checked the setup and for no reason the Lock on road was enabled.
I tried reproducing it, so far failed.
Settings are pedestrian, and prompted method (time, distance or off road).
I have tried. turn off and turn on unit, start a direct (off road) navigation and stop it, start an on road navigation and stop it.
I also tried to navigate to the target so that navigation stops by it self and also stop the navigation and then resume it (instead of making a calculation).
For now none of these seemed to have no impact on the setting.
I also tried changing profiles and changing back, but so far the settings sticks.
For now the only thing i can report is that it does happen, i only don't know when.
I can also mention that it never happened with 2.70 firmware.
The setting for Lock on road enables itself (setting = yes) at seemingly random occasions.
(MENU - MENU - Setup - Routing - Lock on road = YES/NO)
I never use lock on road, but was surprised at least 3 times since the update to firmware 2,80 that suddenly the map showed that i was on some road or path, when in fact i was on some yard or in the forest. I checked the setup and for no reason the Lock on road was enabled.
I tried reproducing it, so far failed.
Settings are pedestrian, and prompted method (time, distance or off road).
I have tried. turn off and turn on unit, start a direct (off road) navigation and stop it, start an on road navigation and stop it.
I also tried to navigate to the target so that navigation stops by it self and also stop the navigation and then resume it (instead of making a calculation).
For now none of these seemed to have no impact on the setting.
I also tried changing profiles and changing back, but so far the settings sticks.
For now the only thing i can report is that it does happen, i only don't know when.
I can also mention that it never happened with 2.70 firmware.