Has anyone else noticed this bug/feature?

[SunnyAndShare]

I want my money back.

If I hold the H1 in one place, the position (lat/lon) does not change. Odd? If I do the same with my other 4 Garmins (and 3 Pixel cell phones) the lat/lon can change upwards of 5 meters over the course of a few minutes because the satellite configuration is constantly moving. But not on the H1. The position does not change. So, ever so slowly, I moved the H1 to see how far I need to go before it detects movement. So far, the max is 47m, and that's only because I reached the edge of my property. Once I jolt the H1 by waving the arm that's holding it, it snaps out of its trance. The key here it to walk slowly. Baby steps. It took me 6 minutes to walk 47m whereas it normally takes me about 30 seconds.

Personally, I think this is intentional. The H1 doesn't think its moving if the movement is very slow. If the H1 does not detect movement AND it keeps presenting the same lat/lon, users are bamboozled into thinking that the position is accurate. If you walk away at a normal pace for five seconds and return to the same spot, the lat/lon is different when you get back. It only stops changing when it thinks it is not moving, but the lat/lon is seldom the same as it was the previous visit to the spot.

I'd compare it to the log of GPX data, but I can't find any GPX data being logged. In other Garmins, the GPX data is stores in a folder called "GPX". I have "Fit and GPX" set to "on", but I have yet to find any logged GPX data. Help, anyone? Anyone? Bueller?

My belief is that Garmin has shifted their priority to the watch market, handhelds be damned. I've purchased 18 Garmins dating back to the Garmin 50 in 1992. I think the H1 will be my last.

[GPSrChive]

I very much understand your frustration, and do not blame you for feeling the way you do.

Unfortunately, the current batch of code writers they are using at Garmin are the worst they have ever had.

I am simply unable to keep up with all the new bugs appearing on most of their recently updated outdoor handheld models.

But, we are trying to keep them on their toes with constant bug reports (you can do the same) and hoping for the best!

[LostAgain]

I'm not sure what it's called exactly, or whether my interpretation of it is even correct, but I think 'stationary speed' may be responsible for what you see.
Depending on how a device has been programmed, once it's speed drops under a certain amount some elements of the display may not register movement or update until that speed is exceeded again.
I believe it's implemented to stop 'creep' or appearing like the device is moving while actually stationary, as a result of satellite constellations moving slightly.

My Montana 700 and 276CX had a similar issue when I first got them years ago, though on those devices it was only the map display updating/rotation that was affected, under certain conditions until a speed of 7 kph was reached the map wouldn't update on the display.
Similar to what you see, after continuing at low speed sometimes many 10's of metres or more, all of a sudden it would wake up and the map display would 'catch up' to the actual location.
Thankfully Garmin fixed this issue on both devices with firmware updates and now as soon as those devices start moving the map display is updated to reflect any movement.

It may be worth contacting Garmin, especially if it's repeatable and causes issues for everyday usage, now is probably the time as they are still fixing things for those relatively new devices.

[JungleJim]

I want my money back.

If I hold the H1 in one place, the position (lat/lon) does not change. Odd? If I do the same with my other 4 Garmins (and 3 Pixel cell phones) the lat/lon can change upwards of 5 meters over the course of a few minutes because the satellite configuration is constantly moving. But not on the H1. The position does not change. So, ever so slowly, I moved the H1 to see how far I need to go before it detects movement. So far, the max is 47m, and that's only because I reached the edge of my property. Once I jolt the H1 by waving the arm that's holding it, it snaps out of its trance. The key here it to walk slowly. Baby steps. It took me 6 minutes to walk 47m whereas it normally takes me about 30 seconds.

Personally, I think this is intentional. The H1 doesn't think its moving if the movement is very slow. If the H1 does not detect movement AND it keeps presenting the same lat/lon, users are bamboozled into thinking that the position is accurate. If you walk away at a normal pace for five seconds and return to the same spot, the lat/lon is different when you get back. It only stops changing when it thinks it is not moving, but the lat/lon is seldom the same as it was the previous visit to the spot.

My guess: the device uses the accelerometer to detect movement and will only use GNSS positioning when it has detected movement. This saves battery and therefore results in the long battery life everyone wants.

It would be interesting to see if the recording frequency has impact on this. It’s by default set to “smart”, but you can also set it to “every second”. Not sure it will have any effect because I would expect the setting to influence recording frequency, but who knows.

I'd compare it to the log of GPX data, but I can't find any GPX data being logged. In other Garmins, the GPX data is stores in a folder called "GPX". I have "Fit and GPX" set to "on", but I have yet to find any logged GPX data. Help, anyone? Anyone? Bueller?

GPX files for your recorded activities are found in the GARMIN\GPXActivities folder.

[gps_techie]

eTrex SE has similar behavior - algorithm uses accelerometer in conjunction with GPS to estimate when device is "stationary" and "sticks" to the same GPS location. eTrex SOLAR (very similar to eTrex SE) has slightly different algorithm implementation and is more "jittery" when device is stationary.

Write to Garmin support for algorithms to be adjusted.

[SunnyAndShare]

My guess: the device uses the accelerometer to detect movement and will only use GNSS poitioning when it has detected movement. This saves battery and therefore results in the long battery life everyone wants.

O.P. here. But I do accelerate from zero to about 130 mm/sec (0.5 km/hr) so I doubt it is using the accelerometer. If it can't detect the acceleration from zero to 0.5 km/hr, then it can't detect should I slowly accelerate further. Cmon, why bothe with acceleration, just take use the satellites to produce another fix. I still believe it holds a position to give the illusion of accuracy. If I take five normal steps away and return, the device stops with a different reading that sometimes is several meters different.