another quick trip for gas... red track is Duraforce, purple is Oregon 450. I stopped at a gas station briefly, and both units were recording tracks. when I remembered they were recording, I created waypoints where I sat. they weren't too far apart, so I won't fault either one for being so wrong that I couldn't navigate to them. I created 3m radius circles around those points with my phones geocaching plugin, I don't think it's possible to do it on Garmin devices.... red circle Duraforce, purple circle Oregon: upon downloading the Oregon's track at home ( it can't be used with usb-otg cables and none Wi-Fi isn't available, or Bluetooth, gah!) I saw something odd. the green (highlighted) track shows the Garmin is very poor at "GPS bounce" or "GPS hop" that happens when sitting still for a moment/minute. its firmware isn't smart enough to realize it's just sitting still, and instead of recording a smooth track, records every change in GPS coordinates, even though they are inside it's error range. this track could still be followed of course, but if you're going to share tracks, you'll probably rib into the "my Garmin has track point count limits" and of course have to screw with the point count in basecamp to fix the errors and reduce count. sigh. the phone, however, didn't record extra points. the frequency settings for the Garmin were "auto" and for the Duraforce "3m and 3 sec". next up, a uturn. the highlighted track is the Duraforce, the purple track is the Oregon. I know everyone talks about poor accuracy in cities with Garmins, but dang, it really went off reservation. in not sure why it recorded all those hops for a two second uturn, but it did. it was between two tallish buildings, so maybe the multi path interference isn't handled very well in the Garmin firmware, or they just don't consider it an issue. either way, I'm curious to see how bad this becomes in the woods when I'm trying to record good gpx tracks riding single track. I'm betting it won't be usable if this is the result of a uturn.