eTrex 22x, 32x (Gen 1) Firmware Update 2.80

[asprin624]

Garmin have published eTrex x2x (Gen 1) Firmware version 2.80:

Changes made to version 2.80:

• Improvements to display of text and pointer for right-to-left languages.
• Fix issue with address search.
• Fix auto-populate of track name when saving.
• Fix issue with navigation recalculation/restart.

Please report your observations about this firmware release, good or bad, here!

original post

I just received an update to my Etrex 22x (Gen 1) via Garmin Express.

Gen 1 HWID: 3445

All seems to be OK with the update.
Will test t later today or on the weekend.

[987]

Hi.
I tried the 2.80 update on a Gen 1 etrex 32x, the routing is working better i judge. It takes less time for it to understand when to recalculate and less time to adjust the remaining distance, especially when walking slow.

[987]

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.

[GPSrChive]

Unable to reproduce at this time, will continue to monitor.

[987]

Now observed the issue again.
It might be that it happens if navigation is started while a bit away from a road or path, such as in a forest or on a field.

Settings.
routing: pedestrian but prompted guidance method. lock on road = no.
walk some 50 m away from the nearest road or path on the map (such as in the forest or on some field, a football field or inside of a running track may work (if not too small).
Select some point to navigate to (does not need to be far away, but at least some 300 m and that would follow some road on some portion of the path), i selected from recent finds, but i cannot say if that impacts. When it shows on the map, press Go and then select on road for time.
Now go to settings - routing and check if lock on road is = yes.

[GPSrChive]

Tested multiple routes, never switched for me. Getting closer, but not quite there yet...