Activities do not retain assigned maps following a power-cycle
Posted: Tue Nov 04, 2025 2:53 am
Unit: eTrex Touch (Gen 2, 2025 model), Software Version 4.09
When setting up an activity and a specific map (assuming multiple mapsets are on the unit) is assigned to that activity and the activity is selected, a power-cycle will change that activity's assigned map to a different mapset on the unit, other than the one that was originally assigned.
Example:
I have two mapsets on the unit, both in the Garmin folder on the device
#1: TopoActive US 2025.10 (the unit's default map)
#2: Topo US 24k West
I have TopoActive US 2025.10 as my selected map for the "Walk" activity
I have Topo US 24K as my selected map for the "Hike" activity
The "Walk" activity is selected when I power down the unit
When the unit is powered back on, the "Walk" activity is still selected, HOWEVER the Topo US 24k map is now showing in the "Walk" activity
Changing the activity from "Walk" to "Hike", then back to "Walk" corrects the issue until the next power-cycle where it will repeat
This issue has been reported to Garmin via email. I'll update with their response
When setting up an activity and a specific map (assuming multiple mapsets are on the unit) is assigned to that activity and the activity is selected, a power-cycle will change that activity's assigned map to a different mapset on the unit, other than the one that was originally assigned.
Example:
I have two mapsets on the unit, both in the Garmin folder on the device
#1: TopoActive US 2025.10 (the unit's default map)
#2: Topo US 24k West
I have TopoActive US 2025.10 as my selected map for the "Walk" activity
I have Topo US 24K as my selected map for the "Hike" activity
The "Walk" activity is selected when I power down the unit
When the unit is powered back on, the "Walk" activity is still selected, HOWEVER the Topo US 24k map is now showing in the "Walk" activity
Changing the activity from "Walk" to "Hike", then back to "Walk" corrects the issue until the next power-cycle where it will repeat
This issue has been reported to Garmin via email. I'll update with their response