Wrong total distance for activities longer than 167.76 km [Bug 10]

[gps_techie]

I record from the start - testing with recording disabled is left as a homework for the interested readers.

Does exceeding 167.76 km affect the current speed and distance to the destination?

Current speed and current distance to destination are updating correctly (distance to can be >2000km, i.e. not capped to 167.77km). Only TRIP ODOMETER, MOVING TIME, MOVING AVG, ETA and similar are affected.

When hiking or driving on a road route, distance and a constant, instantaneous speed (not average speed) are used to determine the current ETA.
Similarly, when hiking according to the route on off-roads, the constant, instantaneous pace of the march is taken into account.

Are you sure that eTrex SE uses current speed for ETA? eTrex SE uses MOVING AVG to determine ETA (if MOVING AVG is not available, ETA is field is empty).
Hiking/driving/... modes change only icon and not much else.

[Przekątny]

Are you sure that eTrex SE uses current speed for ETA?

With Garmin, you can't be sure of anything until you check.

This is how ETA worked in previous devices, so there is a high probability that Garmin hasn't changed anything in this regard, but there is never any certainty.

ETA is determined during navigation, activity registration is not required in previous devices.

eTrex SE uses MOVING AVG to determine ETA (if MOVING AVG is not available, ETA is field is empty).

Is the ETA field also empty when hiking or driving?

The ETA for off-road navigation is determined only during movement, until movement is initiated it is empty.

[gps_techie]

I checked carefully that ETA on eTrex SE is most likely [current distance to destination] / [MOVING AVG]. Current speed is not relevant for ETA.
IIRC eTrex 10 ETA worked similarly.

eTrex SE uses MOVING AVG to determine ETA (if MOVING AVG is not available, ETA is field is empty).

Is the ETA field also empty when hiking or driving?

Hiking/driving mode has no effect on ETA. ETA is only empty when MOVING AVG is empty, i.e. MOVING TIME is empty. This happens only when GPS is not locked yet after turn on (or when activity is reset after 167.77km bug as mentioned before).

[gps_techie]

167 km distance limit bug persists in the newest eTrex SE FW 4.22. Also, device needs to be turned-on/off to reset "distance" calc (otherwise after saving activity with >167 km, next activity is capped at 0 km distance), same as with previous FW.

[Hardrock100]

167 km distance limit bug persists in the newest eTrex SE FW 4.22. Also, device needs to be turned-on/off to reset "distance" calc (otherwise after saving activity with >167 km, next activity is capped at 0 km distance), same as with previous FW.

Have you already reported the problem with FW4.22 to Garmin Product Support?
If not, everyone who is affected should do so!
I have had a developer ticket created via Product Support since 20.11.2024 (with FW 4.20)
I have submitted evidence to, and the developers in the USA were able to reproduce the problem. I was confirmed that the problem will be fixed with FW 4.22.
The changelog for FW 4.22 also contains an indication of this: "Fixed possible issue where navigation ends too early".

I received written confirmation from Garmin that I can return the device for a refund if the error persists.

Unfortunately, I have not yet had the chance to test it myself. But I will do so in the next few weeks.

If the error persists, I will consider canceling the purchase contract

[gps_techie]

167km bug is known by Garmin, anyone reporting can link this thead. How did you contact Garmin developers?

[sim_v]

hi,

I've just registered because I try to supply 2 bugs on my Etrex SE. Garmin France answered me that problems are relative to a memory size issue ! I contacted first France's support but with no update, I contacted international support (product.support[@]garmin[.]com) and got an update from France that explained me....

etrex 30x had no support, limited memory, etc.

Even If Garmin France switched to Etrex 30x, I am very surprised by the announced memory limits because these limits do not seem to affect: my old gpsmap 60csx, my old etrex 30, the old Montana and the newer gpsmap 66S (all in smart mode for logs).

The first bug I've noticed, you knew it : bad summary of long activities :

I have the latest firmware version (4.22) in place. For an actual route of 650 km, the summary of the Etrex, the Explore application and Basecamp display 168 km and totally false average speeds.
To create the track, I clicked “track control” then “delete” to erase the current data.
The recording then starts.
I complete my journey, unaware that the displayed distance doesn’t exceed 167–168 km. Upon arrival, still in “track control,” I clicked “save” to generate the dated file.
This file indicates 168 km, but it includes 650 km of roads. The summary is incorrect on the GPS, on Basecamp, and on android Explore. All average speeds are false.

But I spotted another problem :

If “auto-pause” is enabled, it is impossible to “delete” the current tracking data.

How to escalate to Garmin development team ?

[Przekątny]

The Etrex SE records a current track beyond 167.76 km, but the device does not display the actual distance beyond 167.76 km.

Even If Garmin France switched to Etrex 30x, I am very surprised by the announced memory limits because these limits do not seem to affect: my old gpsmap 60csx, my old etrex 30, the old Montana and the newer gpsmap 66S (all in smart mode for logs).

The GPS 60csx device had a simplified recording (It did not contain all the data); the full log was saved on the card.