I had just under the last 2 miles of my run this morning not recorded on the map. If you look in the pacing it happens right about 33:20. The activity keeps recording but the map stops. My experience with the 5X is after this point the pace becomes unreliable. Anyone else seen anything like this?
Hit another recording error. Oddly enough it happened right around the 33:20 mark as well. I stopped and resynced when I realized and didn't have any issues with it on the second half of the run. wondering if its some weird memory allocation issue?
Conditions: cloudy (my satellite TV had troubles getting a steady signal this morning), at the end of the run the sky cleared. My usual tree covered, canyon-like trail. FR935: GPS+Glonass, 1sec, HR on, BT on, software 3.30 iPhone SE/Runtastic: all network connections turned off, GPS only
Looking at the track the FR935 did a much much better job overall. The iPhone makes me drunk running in serpentines at a certain point and is continuously a couple of meters away from the actual path. Only when turning around at the southern point the iPhone got the turn better, the FR935 cut it somewhat short. However, the turn after 3/4 of the track (which is a sharp right turn) was perfectly captured by the FR935 and the iPhone got lost. As the iPhone wondered around quite a lot, it accrued also more distance than the FR935.
Did also 2 hikes on the weekend and the watch did very well, not perfect, but very well. I used WEBVAN's fix for recalibrating the altitude at the peak (as weather was quite unstable) and it worked flawlessly. Thanks for that :-) So, IMO a well-suited hiking watch for the occasional runner.
Won't do any more comparisons now. I am very happy with the watch.
The only downer is the fact that my down button experiences the "going-soft-problem". On the other hand, I bumped it a couple of times against rocks during my hikes, and the plastic bezel/case itself didn't show marks at all. Only happy I had applied a screen protector.
This is anecdotal so far since I just made the switch but all of the GPS errors I've had have been with the watch set to right wrist. I switched it back to left wrist and had no issues this morning https://connect.garmin.com/modern/activity/1781519026
My one question for people who have been happy with the recordings of their runs: did you enable 3d distance and speed?
This is anecdotal so far since I just made the switch but all of the GPS errors I've had have been with the watch set to right wrist. I switched it back to left wrist and had no issues this morning https://connect.garmin.com/modern/activity/1781519026
My one question for people who have been happy with the recordings of their runs: did you enable 3d distance and speed?
Both off for my runs. For hiking I have 3d speed enabled (though I am not sure what difference this really makes as I don't care about speed as I hike, only about vertical speed).
Logically GPS+GLONASS but there is no "rule". Best to see what works best for you although in forests any setting may not always look pretty.
Yeah, especially during races; I don't use a foot pod, but during trail races I *have* to do manual laps when I cross mile markers, because it can be very far off depending on cover.
