https://forums.garmin.com/sports-fitness/running-multisport/en-USTelligent Community 13https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-570/439617/how-to-make-garmin-run-coach-match-my-scheduleFri, 10 Jul 2026 02:10:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:fbfc54ee-6141-4dc9-bdd3-bc6d8439b40d6540963I am different from the group of people who work for five days and rest for two days. My schedule is as follows: on the first day, I need to work from 8am to 8pm; The next day is free during the day, and work lasts from 8 pm to 8 am on the third day, after which additional sleep is needed; The fourth day is free all over the sky. This cycle is repeated every 4 days. At present, I am running in the morning on the second day and at night on the third day. If I run at night on the the fourth day, I will lose sleep, which will affect my work on the next day. Garmin Run Coach requires at least 5 days of training per week, which has caused me to have many schedules that I cannot complete. Since using the 570, I have been training according to daily suggestion, but I truly want to improve my pace. Although its schedule is also dynamically adjusted, but daily suggestion cannot set a goal. Similarly, suggestion need to set training days, and I hope Garmin can provide a periodic option for people like me.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-255-series/439472/inaccurate-display-of-navigation-curve/2044350Thu, 09 Jul 2026 23:42:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:b7131b7d-4853-4cad-bace-16c94d0d4a7eLuděkThis would also correspond to my observations - I don't see any problems with navigation with the watch on shorter routes (either the route doesn't deform at all or only slightly). But on the mentioned route it was already clearly visible in several places. It's a shame that the GPX or FIT file in question cannot be attached here - I don't understand this limitation here either.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-255-series/439590/noisy-gps-day-doubled-length-of-ultratrac-activity/2044345Thu, 09 Jul 2026 23:03:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:73d3800c-4f77-4715-9447-e951cec95e156125703I'm aware of these basics and "theory". To be more explicit, I am wondering if anybody knows what in practice leads to such day-to-day qualitative change in the amount of GPS drift or inaccuracy for the individual location fixes. I walked the same route each day, with the same houses, yards, tree cover, etc. None of the explanations like urban canyons etc can account for the difference between one day and the next. And, the error seemed consistent through the entire walk, with 1 mile auto laps alerting steadily. Not some individual glitch or local source of interference like a house or vehicle. Is there some kind of global GPS jamming or spoofing happening these days? Or is there some other more natural explanation? The bad results was recorded yesterday evening 7/8 in local California time.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-255-series/439472/inaccurate-display-of-navigation-curve/2044334Thu, 09 Jul 2026 22:09:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:0642ba35-aa54-4697-8a1f-41f682fa0eb9LuděkThank you for your response Garmin, Czech support also told me something similar. But I don't understand: 1. Why can't the watch correctly draw the navigation route when it can correctly draw the actual route (black line), which in my case was a little longer than planned and with more points (5553 compared to 1671)? 2. Why is Garmin Connect unable to announce when preparing the route whether it will be reduced by the watch (and possibly show how) so that the user knows whether he can rely on the navigation, which can be a matter of life or death? 3. Why doesn't Garmin Connect adjust the route in some more intelligent way (e.g. Douglas-Peucker algorithm) than the watch probably does with the sampling mentioned above? Garmin Connect, whether web-based or as a mobile application, generally has more power than the watch for this. 4. And if you can't or don't want to fix any of the previous points, why don't you at least publish the exact criteria for when the watch will reduce the route so that the user can take this into account and possibly adjust the route themselves?https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-165-series/402035/black-screen-cant-get-watch-face-to-turn-back-everything-else-still-functions-heart-rate-sleep-tracking-ect/2044332Thu, 09 Jul 2026 22:03:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:45919f64-7f66-4b57-a550-8fe785884f276285536Black screen of death happened to me tonight. Started with battery needing to be charged after 3 days for the last week. Plugged in tonight made a few beeping noises and now nothing. Only bought it April 25! So annoyedhttps://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-255-series/439590/noisy-gps-day-doubled-length-of-ultratrac-activity/2044329Thu, 09 Jul 2026 21:32:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:9a658091-bea3-4c58-8cbf-f5ba11539c47Garmin - KSUltraTrac Mode is designed to extend battery life by reducing the GPS recording rate, and as a result, track detail and distance accuracy can be reduced compared to standard GPS recording. For additional information, visit Setting a Garmin Watch to UltraTrac Mode for Longer Battery Life GPS drift and other factors can also affect GPS signal quality and impact recorded tracks and distances, as explained here: Top FAQs About GPS Distance, Speed, and Pace Accuracy With Garmin Devices When GPS positions become unusually noisy, the reduced sampling rate used in UltraTrac Mode can increase the effect on the recorded activity. The map behavior you described is consistent with poor GPS positioning during the recording.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-255-series/439472/inaccurate-display-of-navigation-curve/2044321Thu, 09 Jul 2026 20:58:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:d7c70a68-a405-4a92-a25b-bf29a62cc3a7Garmin - KSLuděk The behavior you're seeing may be related to course limitations on the device. Garmin watches have limits related to course points and course calculation, and long or complex courses may require splitting into smaller sections. If you're working with a very detailed course, reducing its complexity or dividing it into smaller segments may help avoid course-related limitations.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-965/438228/sleep-measurements-are-terrible-rem-rem-can-t-be-0-for-a-human-being/2044312Thu, 09 Jul 2026 20:29:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:e0beca22-bbb4-435c-867a-891cc6b39f8fGogiFirst make a full BACKUP of the watch. Dowload zip file from my Google drive: https://drive.google.com/file/d/1xiQk43Ia3V9rSs3okcUn7c1pTxHgHI9Q/view?usp=drivesdk On your laptop or PC install Garmin Expres, connect with cable your watch to PC. Unzip downloaded file and then unzip version that you want to have on your watch and copy unziped files (force.tmp and gupdate.gsp) to main root folder on your watch. Unplug your watch from PC and the watch will prompt you to update your watch. When downgrade is finished the watch will probably factory reset... restore backuped data from backup that you made before this procedures.... When all is done, on your watch turn off automatic update.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-255-series/439472/inaccurate-display-of-navigation-curve/2044279Thu, 09 Jul 2026 19:46:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:783b9f22-81b5-4778-98af-5ebcfeaa59616125703FWIW, I downloaded my longest course (about 27 km) from Connect as a FIT file and used fitdump to look at it. This was one I created on Connect itself. This one worked nicely on my FR255 during the actual hike. It seems like it has about 839 "record" entries which I think are track points. Then just a handful of "course_point" entries which I think were waypoints I labeled on the course editor like water crossings. When I download the GPX version, it also has 839 "trkpt" records in it.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-965/438228/sleep-measurements-are-terrible-rem-rem-can-t-be-0-for-a-human-being/2044272Thu, 09 Jul 2026 19:26:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:bb568ebe-81c9-47bc-a0be-2632a372f4d27215583Hello, could you send me a guide to downgrade it? I couldn't find the correct software and step by step, thank you.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-255-series/439472/inaccurate-display-of-navigation-curve/2044270Thu, 09 Jul 2026 19:15:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:dc908ec8-e2b2-445f-9370-3c0ae9773df1LuděkI guess I didn't express myself completely clearly: Displaying only points from the GPX file connected by straight lines would be enough for me, so I don't see the source GPX file as incorrect or insufficient, just like the FIT file generated from it. I don't see any problems with shorter routes or with displaying them on the watch, I just came across the described problem now. Czech Garmin support confirmed this problem to me, but they said they can't give details under what exact conditions it occurs. That's why I'm trying to draw attention to this problem on this forum, because the watch manual is silent about it and Garmin Connect doesn't warn about route reduction in a specific case when preparing (importing) such a route, which I find annoying and in a sense even dangerous. Moreover, as a programmer, I don't really understand why the reduction has to occur.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-255-series/439439/charging-port-question/2044267Thu, 09 Jul 2026 19:08:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:0d1abe9b-899e-462a-a565-60fa63a292c46125703(I deleted my earlier post because I did manage to get some photos to focus here eventually...) The metal part in the middle looks like part of the retention system for the cable, not related to the interface with the watch plastic. What I see at the bottom looks like some molded plastic contours beneath or behind the metal port. It's hard to really imagine how it is mounted and what exactly penetrates versus being surface mounted?https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-970/438628/ghost-touches-when-scrolling-through-menu/2044262Thu, 09 Jul 2026 18:45:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:bafdd433-6fbc-4c40-8f51-6e481383e3433829612I’ve had multiple watches with this exact same issue. Same problem that OP shows in the video. After really looking into it and comparing it with a forerunner 970 that doesn’t have the issue (it’s from an older batch). I’ve noticed the defective watch picks up a touch even when the finger isn’t making contact with the screen, where the finger is hovering a couple CM above the screen. I believe this is what causes it to register a swipe as a touch because either when you’re going it for a swipe or pulling your finger away after a swipe, the watch picks up the touch of your finger without it making actual contact, it’ll register a false touch.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-970/415788/no-auto-lock-for-buttons/2044261Thu, 09 Jul 2026 18:43:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:aba4ffdb-8a89-43b4-b7c3-919c553c58139856557I dont just run. I NEED the start & laps buttons to not work during my workouts. At least let us choose the amount of time the buttons have to be held pressed or a specific combination of button. Not just "any button" for less than 2 seconds...preposterous.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-255-series/439590/noisy-gps-day-doubled-length-of-ultratrac-activityThu, 09 Jul 2026 18:28:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:8c3b3bea-f25c-4707-b127-5f610b9d250f6125703Had another one of those absurd days where my FR255 had really poor quality GPS fixes and over estimated distance. I walked the same course three days in a row using Ultratrac. It is very close to 3 miles and the first two days did well enough, measuring roughly 2.9 miles with little visible deviation in the map trace. The third day, I got 1 mile auto-lap alerts way too soon and it ended up measuring over 6 miles. The trace even on the watch screen shows crazy deviations. Like a drawing of the map from someone suffering severe tremors/seizures. Lots of back-and-forth and lateral scribbles. These were in suburban SF Bay Area in California, so nowhere near any contested zone where you expect GPS denial etc. I wonder what is the most likely explanation for such huge day to day difference in quality... FWIW, I was doing these to assure myself all was well with the watch after updating the firmware over the weekend. Since it worked normally the first two times, I doubt it has anything to do with the firmware update.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-255-series/439472/inaccurate-display-of-navigation-curve/2044253Thu, 09 Jul 2026 18:21:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:a57c874b-becd-410d-a261-be7f71de26a36125703The fact that it can display courses just fine tells me it is a problem with the initial data or the conversion process. Maybe the GPX points don't get translated into the right point type in the FIT file? Not all FIT files are equivalent. The FIT format is capable of storing points of different types, some defining the course line and others defining waypoints or adjacent landmarks. Also, I think traditional GPX file usage may be sparse and assume additional routing during display. So it is key waypoints along the way but expects the display to fill in the gaps with knowledge of terrain or trail networks. For a device like FR255, there is no supporting map. So it will only draw straight lines connecting the points. A good course is going to have a high resolution series of points quite close to each other to trace out the full shape of the route.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-955-series/439044/everyday-update/2044219Thu, 09 Jul 2026 16:07:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:382346bd-478b-4676-b55f-273563bbb3d3koZisI tried it, but result is still the same. Everyday update.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-55-series/439566/race-predictor-showing-no-data-for-past-6-weeks/2044214Thu, 09 Jul 2026 15:46:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:b69712fc-ea63-4ca7-ab9f-0b501af3e4d9Garmin - DKThanks for the post, 5328646 . There could be a few different things happening here. We recommend viewing this Support Center article, which outlines what all goes into determining race prediction times: How Are Race Prediction Times Determined on My Watch? You'll also want to be sure that your watch and Connect app are both up to date. If you've done a master reset at any time between April and now, that can also impact your race time updating.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-955-series/439577/firmware-28-05-bugs-on-garmin-forerunner-955-solarThu, 09 Jul 2026 13:15:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:f76bf2cf-ec91-459f-82a4-7ae545411c99MartinRASince installing firmware version 28.05 , I've encountered the following issues: During a Hiking activity, if I select Navigation → Use Map , the watch immediately restarts. (I'm using Freemap.sk maps, gmapsupp.img file ) The watch does not count steps while in Sleep Mode . For example, if I get up during the night to use the bathroom, my step count is still 0 after waking up. Every third or fourth day I have to recalibrate the compass because it no longer points to true north correctly. This never happened with previous firmware versions. Issues that were already present in previous firmware versions: Incorrect cadence detection while running. Very often during a run, when I look at the watch, it shows only half of my actual cadence (for example, 85 spm instead of around 170 spm ). After a few seconds it jumps back to the correct value. As a result, all cadence-dependent running metrics are also incorrect. This issue did not exist in firmware 19.18 . I already have a separate thread about this problem, but unfortunately nothing has changed since then... This is the same issue I reported quite some time ago, and unfortunately nothing has changed in the latest firmware. Incorrect cadence calculation on my FR955 Solar Pls Garmin....wake up and do something...https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-965/439575/is-there-a-way-to-force-forerunner-to-recalculate-load-focus-training-statusThu, 09 Jul 2026 12:33:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:8d17b30a-baef-4209-93d9-2c6808c5702caka_wintermuteAfter a crash ( Progress, training status, week mileage wiped out after recording corrupted walk activity ) , the device resets data on activity zones, training load, and the like. This disrupts all progress calculations, rest times, training zones, and so on. So I'm wondering if there's a way to force the watch to recalculate this data based on the workout history it has saved?