https://forums.garmin.com/sports-fitness/running-multisport/en-USTelligent Community 13https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-265-series/435703/garmin-265-bluetooth---music-constant-cutout-tried-3-different-earbuds-time-to-return/2029604Tue, 05 May 2026 14:41:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:cb45eac7-be77-45a0-9fea-f89777694271chris_in_cal[quote userid="1206260" url="~/sports-fitness/running-multisport/f/forerunner-265-series/435703/garmin-265-bluetooth---music-constant-cutout-tried-3-different-earbuds-time-to-return/2029457"]JBL[/quote] My cheap JBL's work with my old 265 and my new 570. It is always, 100% of the time, the earbuds. (well 99% of the time.)https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-570/435796/new-570Tue, 05 May 2026 14:38:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:02c4e949-a921-4155-907f-a2467db128a7chris_in_calHello Folks, I configured my new 570 last night. I expect I'll be around from here on out. I felt my FR265 was the best Garmin I've ever used. It wasn't broken, confounding, and had useful features. Nowadays I'm mostly running, but I've used Strength, OWS and cycling in the past. A tiny bit of yoga (It is not good for me to have a watch on whilest doing yoga poses) and a tiny bit of the breathwork/meditation apps. I wish I could have a more text-based less cartoonist watch face, I was looking around at them last night. The 'make a face' was pretty good, except the complications data were tiny, while the clock font was large. That's it so far. Enjoy your 570 ya'llfr570https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-970/435757/bug-artificial-jump-with-track-detection-feature/2029585Tue, 05 May 2026 14:04:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:e4d23710-3676-4d2e-b59e-6268122ab7absantosI think this is a different case. That Garmin article is about choosing between the Run activity profile and the Track Run activity profile for warm-up, track workout, and cooldown. In my case, I was not using the Track Run activity profile . I was using the normal Run profile . The issue happened with the Track Detection feature inside the Run profile: I started the activity in the normal Run profile with Track Detection disabled. Before the track intervals, I enabled Track Detection. After the intervals, I disabled Track Detection again for the cooldown. Exactly when I disabled Track Detection, the FIT file recorded an artificial jump of around 3.9 km in about one second. So this is not about Garmin’s recommendation for using Track Run vs Run profiles. The problem is that disabling Track Detection during an ongoing normal Run activity appears to introduce a corrupted distance correction/jump into the FIT file. The final activity distance became around 14.5 km, while the corrected distance should be around 10.6 km. The difference matches the artificial jump. That is why I still believe this is a bug, or at least something Garmin should handle more safely when Track Detection is turned off mid-activity.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-970/435757/bug-artificial-jump-with-track-detection-feature/2029586Tue, 05 May 2026 14:04:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:d15670df-a618-43fb-bd01-3b3e6cb71f66santosUpdate: I checked the original FIT file again and noticed something important. The artificial jump is not random. The jump is around 3925 m , and that is almost exactly the amount of distance that had already been accumulated before/around the point where Track Detection became active during the activity. In the FIT file, the distance suddenly jumps from around 8860.73 m to 12786.01 m in about one second, which is an increase of 3925.28 m . Earlier in the activity, around the Track Detection transition, the accumulated distance was also around 3925 m . So it looks like when I disabled Track Detection later in the activity, the watch may have incorrectly added/reapplied the pre-Track-Detection distance offset again, creating a duplicated distance correction.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-970/433076/970-dims-in-sunlight/2029581Tue, 05 May 2026 13:51:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:ed4a1fd2-3c7d-4a1d-867e-a2cd8deb0bf8PaulThis was my exact issue. Garmin said it sounded like the "ambient light sensor" was the issue but wouldn't know for sure until they tested my watch.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-970/435757/bug-artificial-jump-with-track-detection-feature/2029565Tue, 05 May 2026 12:49:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:70367835-169c-4cb7-9d6d-74724b313989dubteeI suspect this is not a bug. https://support.garmin.com/en-AU/?faq=eH8V1VwjN338uo8C5PgDJ7&identifier=1462801&tab=topics When performing a warm-up and cool-down before and after your track workout, Garmin recommends one of the following, based on your preference: If your workout includes a warm-up and cool-down as you run to and from the track, we suggest you record your workout as three separate activities. Start an activity with the Run activity profile and warm up on your way to the track. Save that activity, then start a 2nd activity using the Track Run activity profile. Complete your track workout and save it. Then, to cool down, start a 3rd activity using the Run activity profile as you leave the track. If your workout includes a warm-up and cool-down on the track, you can complete the entire activity using the Track Run activity profile.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-570/435525/feature-request-heart-rate-zones-history/2029558Tue, 05 May 2026 12:16:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:16f43467-7ed5-4116-8eed-f1e42767bbb6JacquersShare Ideas | Garminhttps://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-965/435622/smart-recording-option-causes-poor-pace-accuracy/2029556Tue, 05 May 2026 12:04:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:df84eb16-5877-45c2-ad3f-33b09b86ae3eJacquers" Smart Recording captures key data points as changes occur in direction, speed, heart rate, or elevation. This method is recommended as it saves space on your device and has no negative impact on GPS accuracy. This setting will also be the most beneficial to your battery life." Which is not really true as you can see differences in tracks recorded with smart vs 1s. I'm not too surprised that pace data might be different too.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-965/435764/progress-training-status-week-mileage-wiped-out-after-recording-corrupted-walk-activityTue, 05 May 2026 05:41:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:ae5415e1-873d-4250-a371-f24ef9ef95baaka_wintermuteBriefly. Garmin Forerunner 965, software version 27.09. Walking activity is recorded during which recording was paused, and after resuming the pause, there were GPS issues (poor reception, jamming). After saving this activity, the watch resets its training data for the past four weeks — the status changes to "detrained," weekly mileage is reset, total and peak load are zero. Consequently, the predictor goes crazy, and the training recommendations are based on the assumption that I haven't done anything for four weeks. Moreover, all running workouts remain in the activity list on the watch. This issue occurred four times, and one of them even affected the current time and daily step count. So, I have some questions. Has anyone else encountered this? Is there a way to avoid this (other than not pausing walking tracking)? Is there any way to restore my fitness data other than waiting a few weeks for the watch to collect training data again?https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-970/435757/bug-artificial-jump-with-track-detection-featureMon, 04 May 2026 22:46:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:dcaae7e6-7f0e-4fbe-9fdc-1db12cac58d5santosHi, I would like to report a bug related to Track Detection during a running activity. Here is what happened: I started the activity with Track Detection disabled . Before beginning my intervals on the track, I enabled Track Detection . After finishing the intervals, I disabled Track Detection again for the cooldown. The issue happened exactly when I disabled Track Detection. At that moment, the activity produced an artificial jump in the recorded data: the total distance suddenly increased by around 3.9 km in about one second . Because of that, the activity distance became much higher than it should have been. The incorrect activity distance was around 14.5 km , while the corrected distance should be around 10.6 km . The difference matches the artificial jump introduced when Track Detection was disabled. I cannot provide the original Garmin Connect activity link because I manually edited the FIT file to fix the issue and reuploaded the corrected activity to Garmin Connect. However, I can upload the original unmodified FIT file somewhere for analysis if needed. Could you please investigate this? It looks like disabling Track Detection mid-activity can introduce a corrupted distance correction/jump into the activity. Thanks.Forerunner 970trackbugbug-reporttrack detecthttps://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-265-series/435703/garmin-265-bluetooth---music-constant-cutout-tried-3-different-earbuds-time-to-return/2029457Mon, 04 May 2026 19:40:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:e31cd70b-c929-489b-8611-b9fe6cc900aeRumiKJBLhttps://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-970/435596/fr-970-bought-2-weeks-ago-for-the-first-time-i-had-a-corrupted-registration-after-a-normal-trail-run/2029451Mon, 04 May 2026 18:51:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:9fbbfdfc-2c17-442a-8413-d9b3df2bbe1c9212880Thanks... Still... it's embarrassing, never heard such an issue with other competitors which are much cheaperhttps://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-970/435596/fr-970-bought-2-weeks-ago-for-the-first-time-i-had-a-corrupted-registration-after-a-normal-trail-run/2029443Mon, 04 May 2026 18:31:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:41fd5674-cfda-4b6f-a6b6-e495cefbbaf2AetlesCorruption can happen, I've had some on my 910XT and on my 965, as well but what I find more embarrassing is that you have to search for third party tools to do the job of repairing. Since the need to repair FIT files has been around for ages (and the tools to fix them, as well) Garmin Connect should have this built in as a basic service when their watches fails.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-255-series/432197/27-09-battery-drain-reproducible-problem-proof-and-battery-graphs/2029400Mon, 04 May 2026 16:40:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:8984f516-8bb5-47d8-b6a9-857bcc14bc1c9675967I have the same problem with my Forerunner 255. It is a very noticeable increase in battery drain after indoor cycling.https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-965/434996/track-run-with-all-miltiband-it-s-a-joke/2029386Mon, 04 May 2026 15:47:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:9b880f9f-9ace-4a9f-b59b-880fca4422a3socorsuHi for your information, FRx55/x65 have - GPS version - 13.00 Same chipset on these models/family (but did not saw this type of report with 13.xx when in use) Regarding Fenix 7 Series (all models) GPS version - 14.01 Regarding Fenix E (from F8 Series) GPS version - 16.01https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-970/435742/body-battery-101Mon, 04 May 2026 14:44:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:23fc759c-b461-4157-9c50-84d1adeafdc2BerndToday I woke up with an overnight load of 101 points body battery in the morning report.. So I will be the new superman. Anybody else had this Garmin error?https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-165-series/435728/ultra-trac-lost-track-single-pointMon, 04 May 2026 11:31:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:bcded24b-3c7a-4f44-a864-d5afd9d4bc3e7104730Hi Garmin, I have sometimes a bug by using UltraTrac as satelite system: the activity (f.e. walking) starts without issues and also showing the track. but: once I save the activity it is then showing only a single coordinate point and this activity is not loadable into the Garmin App. All other satelite systems (f.e. GPS) I did not observe this. May also effect other Garmin watches. Thanks!bughttps://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-165-series/435726/count-hike-activities-as-walkingMon, 04 May 2026 11:26:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:d3034058-c5c0-4848-8090-17bd454dba147104730Hi Garmin, pls. also count all hike activities in your walking challanges & badges -> there is no reason for not to track&count them into this challanges and badges. Is affecting all watches. Thanks!updatehttps://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-165-series/435725/stepper-km-tracking-missingMon, 04 May 2026 11:22:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:566ee542-b2a4-407f-9d04-fb2b6ac0544c7104730Hi Garmin team. SW request : please add for stepper activity the tracking of the distance. this can be done easiliy by add step lengt as a config param in a the activity config. thanks!updatehttps://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-165-series/435724/garmin-coach-lapcounter-not-tracked-for-running-tracksMon, 04 May 2026 11:14:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:4c5a69fb-9520-4e01-876f-9b44a811b01a7104730Hi Garmin SW team: Here is a sw request: please enable the lapcounter and lapstatistics for running track (german "Laufbahn") also for activities started via Garmin Run Coach. Currently it is just giving all stats only for the full activity but its not separated by laps as it is for non Garmin Coach activities. I guess this topic is for update on all Garmin watches. Thanks!Garmin run coachrequest