Forerunner 955 Series - Recent Threads

RE: [BUG][29.05] TSA field is wrongly mapped. TSA is showing "TSA to the next waypoint" instead

Garmin - DK — Fri, 06 Nov 2026 15:24:32 GMT

Thanks 7419217 . I just sent you an email to follow up on this further.

Others who may be experiencing the same thing, please comment, then follow and bookmark this thread as we will post meaningful updates here as they become available.

[BUG][29.05] TSA field is wrongly mapped. TSA is showing "TSA to the next waypoint" instead

7419217 — Sun, 27 Sep 2026 22:06:41 GMT

TSA field is wrongly mapped.

I discovered that TSA field is showing "TSA to the next waypoint" instead, so you never know the Time scheduled arrival.

Can you please fix it?

You just need to map TSA to the right field.

RE: [BUG][29.05] TSA field is wrongly mapped. TSA is showing "TSA to the next waypoint" instead

5767025 — Fri, 06 Nov 2026 11:06:45 GMT

I think you mean ETA (estimated time of arrival)?

If so, this has been broken for years across many Garmin devices. See for example:

ETA calculation still wrong during activity

[BUG][21.19] Time to destination ETA calculation not working

Forrerunner 970 v18.29 problem with ETA, bug?

RE: Forerunner 955 LOOSE bluetooth connection on lap change (headphones + HR chest strap)

Garmin - KS — Thu, 05 Nov 2026 21:18:05 GMT

Thank you for following up, 7419217. At this time, I don't have any updates to share regarding this behavior. We were unable to move forward with an investigation because we did not receive the requested diagnostic information and logs. Those items are necessary for us to properly review what may be occurring.

If you're still experiencing this issue and would like it investigated further, please reach out to your local Garmin Italy Support office directly by using the contact information listed at the bottom of that page. They can work with you to collect the diagnostic information and logs needed to further investigate this behavior.

Forerunner 955 LOOSE bluetooth connection on lap change (headphones + HR chest strap)

7419217 — Wed, 21 Oct 2026 14:30:50 GMT

As per title, quite often the bluetooth driver crashes when a new lap trigger in and bluetooth connectivity is lost.

I have bluetooth headphones (with mp3 playing) and chest strap connected. No phone.

Headphones restore the connectivity and keep playing after a sudden stuttering.

The chest strap is dead forever.

Sometimes the connection drop while changing lap.

Found a bad workaround to solve the issue: STOP the activity and START back again the activity, in a matter of 1-2 seconds.

Doing this the connectivity is restored.

Dear Garmin devs, can you please prompt the AI and save our beloved running smartwatch?

I'm available to pay money to see the firmware code. You close me in a white room, with a monitor and a mouse and you let me read the bloody code.

RE: [BUG][29.05] TSA field is wrongly mapped. TSA is showing "TSA to the next waypoint" instead

7419217 — Thu, 05 Nov 2026 17:02:40 GMT

Video uploaded.

The field is called ETA but in the past I think it was TSA (time scheduled of arrival).

RE: [BUG][29.05] TSA field is wrongly mapped. TSA is showing "TSA to the next waypoint" instead

Garmin - DK — Thu, 05 Nov 2026 15:17:30 GMT

Thank you for those links, 7419217 . I am looking into this now and will circle back here once I have some meaningful information or may reach out via email to gather additional info, if needed.

In the meantime, please use our Secure File Uploader page to upload the video of what you're experiencing.

**

RE: Forerunner 955 29.05 - crash after starting measurement of sport activities

pw — Wed, 04 Nov 2026 23:44:54 GMT

I’m a bit disappointed that no one helped me,

but I found out there is a new beta version: Public Beta Version 29.52 - Pre-Rollout

Here is what I did:

I joined the beta program.
I backed up the Garmin folder.
I installed the 29.52 beta version.
I started a Run activity and it worked. No restart!
I found out that all my stats had been reset.
I copied the Garmin folder back.
The stats seem to be back.

The issues with starting activities have been resolved by installing the 29.52 beta version.

I can finally train with my watch again 🎉

Forerunner 955 29.05 - crash after starting measurement of sport activities

pw — Mon, 26 Oct 2026 15:16:06 GMT

After installing version 29.05, the watch was functioning normally. However, after several days, I went for a run, and when I stopped the Run activity and tried to start it again, the watch crashed and restarted.

I tried starting the activity once more, but it crashed and restarted again. After that, I just used the watch normally and forgot about the issue.

Today, I wanted to go for a run. I started playing music over Bluetooth and waited for a GPS signal. Once the GPS indicator turned green, I started the RUN activity. All OK. The timer began, but within one second, the watch froze, began vibrating continuously, and restarted after a few seconds.

Following that restart, I tried starting a Walk activity instead. The same thing happened, even with no GPS, no Bluetooth, and no music connected. I just started the Walk activity, the watch beeped as ususally, the timer advanced to 1:08 (one second and 80ms), and then the watch vibrated and restarted.

I am completely unable to start any activity now as it seems. I have never experienced an issue like this with any of the previous software versions.

Do you have such an issue with this version?
What can I do to fix this?

RE: [BUG][29.05] TSA field is wrongly mapped. TSA is showing "TSA to the next waypoint" instead

7419217 — Wed, 04 Nov 2026 23:36:32 GMT

Garmin - DK check this Forrerunner 970 v18.29 problem with ETA, bug?
ETA calculation still wrong during activity

RE: [BUG][21.19] Time to destination ETA calculation not working this is me one year ago.

I have a video of the bug but I don't know how to upload here on the forum.

But anyway, the ETA field it's possessed by daemons.

RE: [BUG][29.05] TSA field is wrongly mapped. TSA is showing "TSA to the next waypoint" instead

Garmin - DK — Wed, 04 Nov 2026 21:16:20 GMT

7419217 - I'm not seeing any other reports of this, but would love to investigate.

Can you post some screenshots of what you're seeing so we can look into this? Please also include if your 955 always shows the time to next waypoint instead of the estimated arrival, or if it only does so on occasion.

RE: [BUG][29.05] TSA field is wrongly mapped. TSA is showing "TSA to the next waypoint" instead

7419217 — Wed, 04 Nov 2026 14:48:13 GMT

Garmin-Kevin can you please have this bug fixed in the upcoming firmware release?

It's a very easy bug, you just mapped the wrong field.

You mapped the TSA to the next waypoint instead of the TSA to the end of the itinerary.

RE: Forerunner 955 LOOSE bluetooth connection on lap change (headphones + HR chest strap)

7419217 — Wed, 04 Nov 2026 14:46:05 GMT

Dear Garmin Garmin - KS we need to have this bad bug fixed.

This is affecting other model also, I read the same on the 965 forum.

All my HR data is broken by this bug. You can access all my running activities and see naked eye the holes on the HR chart and download the FIT file.

Are you working on it? Is it included in 29.52 ?
I'm sorry I can't join the beta program as I feel too much instability already with the stable firmware and as already said I need reliable data.

RE: Incorrect time after permanent DST in BC

MilA — Tue, 03 Nov 2026 18:38:37 GMT

I will update if someone from BC can confirm that it is working fine.

Incorrect time after permanent DST in BC

MilA — Mon, 02 Nov 2026 02:01:00 GMT

In British Columbia, Canada, permanent Daylight Savings Time was adopted. But my watch changed the time last night. GPS sync also sets it to incorrect time. I am on old version 17.23 because it is working perfectly for me. Sunrise and sunset are also wrong, which is important to me.

Any ideas how to solve this? For those in BC on the latest firmware, can you confirm that it's working fine .

RE: Incorrect time after permanent DST in BC

Garmin - DK — Mon, 02 Nov 2026 17:39:48 GMT

Hi MilA - we would ask that you first update to the latest version of software, as 17.xx is several years old. The current software version is 29.05, which was released 08/27/2026.

RE: Incorrect time after permanent DST in BC

kochmans — Mon, 02 Nov 2026 10:17:09 GMT

You need to update the timezone map. Not sure if this is possible without updating the firmware.

RE: Has anyone noticed any changes or improvements following the updates?

5738509 — Mon, 02 Nov 2026 04:51:46 GMT

Ja mám 22.22 ,niekedy je nepresná gps ale ostatné funguje, tak radšej nejdem na iný firmware

Has anyone noticed any changes or improvements following the updates?

9621463 — Thu, 29 Oct 2026 08:40:39 GMT

hello

i can see a lot of people having some issues after the updates.

But my question is, has anyone noticed any changes or improvements following the updates? or what concret improvements?

My 955 solar is still on 21.22 firmware, i have some battery drain sometimes, but restarting the watch solve the issue, my gps reception is sometimes very slow to start, except that i am happy with my watch.

so i wonder if i start an update if i can have best battery or better gps reception, others nice improvements...etc

Thank you

Repair barometric sensor

cathleen — Thu, 29 Oct 2026 18:51:20 GMT

The altimeter on my Garmin 955 stopped working about 2 weeks ago. Before that it was fine, tracking hills during runs perfectly. Now it either registers flat elevation or crazy high spikes. When I try to recalibrate, it seems to be able to find the right altitude by GPS, but if I try to walk or run the altitude read an ever changing number -21,000 or higher but just keep changing. I have rinsed and soaked the port. I have turned it on and off. I have recalibrated many times using all 3 options. I bought the watch 9/23. Can you help. Where in the Garmin app can I find help. I am traveling in Nepal and would love to have this feature working.

RE: Repair barometric sensor

kochmans — Fri, 30 Oct 2026 07:07:27 GMT

You need to contact garmin support. Just go to the garmin website and in the upper right corner you'll find "Support". Click it and select "Support center". Type in your watch model. Initially it will redirect you to some generic support advice. Scroll down and at the very bottom you'll find some support contact methods.

Anyway, since you bought the watch in 2023, I'm affraid it's out of warranty, and the support will provide you with some basic troubleshooting (like restoring factory defaults) and then possibly with a paid replacement at an unreasonable fee.

Garmin Forerunner 955 – Display corruption, heart rate sensor stopped working, now completely unresponsive

4549912 — Wed, 28 Oct 2026 05:08:55 GMT

Hello everyone,

I'm experiencing a serious issue with my Garmin Forerunner 955, which is less than two years old. I'm wondering whether anyone has experienced something similar and whether this could be a software or hardware failure.

Here is the timeline of what happened:

1. Initial failure during a gym workout

The problem started suddenly while I was doing strength training at the gym.

The screen froze during an exercise set. Some numbers and parts of the interface disappeared, although the watch initially continued responding to button presses.

2. Progressive display corruption

Shortly afterward, the display started behaving very strangely:

Parts of the image disappeared or became distorted.
Random pixels and horizontal lines appeared.
The screen occasionally displayed corrupted graphics.
Eventually, the screen went completely black.

At certain points, the backlight still worked, even though nothing was displayed.

3. The watch was still functioning internally

Despite the display problems, my computer could still recognize the watch via USB.

Garmin Express also detected it, and the watch was apparently still functioning and recording activities.

I connected it to Garmin Express and attempted to apply the available updates/changes. Unfortunately, the USB connection was accidentally interrupted during the process.

After reconnecting, Garmin Express reported that the device was up to date.

4. The display unexpectedly recovered

After several restarts and some time, the Garmin logo appeared again, initially with corrupted graphics.

Eventually, the watch booted normally, and the display completely recovered.

I could navigate through the menus, start activities, and use the watch normally again.

There were still occasional minor display glitches, particularly when starting an activity, but otherwise it seemed to work.

I wore the watch overnight, and the display remained functional.

5. Heart rate sensor stopped working

The following morning, I noticed that the optical heart rate sensor was no longer working.

The green LEDs on the back of the watch were not lighting up, and the watch had stopped recording heart rate data.

Around the same time, I noticed some minor display glitches again, including parts of the screen becoming darker.

6. Reset attempt and complete failure

Since the problems persisted, I decided to try the "Reset Default Settings" option.

The Garmin startup logo appeared, but the screen subsequently went black.

After waiting, I performed a forced restart.

The Garmin logo appeared again, followed by severely corrupted text and missing pixels.

Shortly afterward, the display went black again.

7. Current situation

Unfortunately, the watch now appears to be completely unresponsive.

The screen remains black.
The optical heart rate sensor is not working.
My computer no longer recognizes the watch when connected via USB.

I have photos showing the display corruption.

The watch had been working normally before this incident, and the initial failure happened suddenly during an ordinary strength training session.

Has anyone experienced a similar combination of display corruption and heart rate sensor failure on the Forerunner 955?

Could this be a firmware/software issue, or does it sound more like a hardware failure?

Is there anything else worth trying before contacting Garmin for warranty service?

Any advice would be greatly appreciated.

Thank you!

swim turns

AAP103 — Sat, 24 Oct 2026 00:30:02 GMT

i do not know how to do the swin turm how can I get accurate distance

RE: swim turns

Andy275 — Tue, 27 Oct 2026 19:21:36 GMT

Do not stop at the wall unless you push the lap button (and do so again when you restart). Push off the wall firmly and glide a meter or two before swimming. Do not stop and restart in the middle of the lane. If you slow down because someone is in front of you or speed up to pass mid-length, it will trigger a new length. Don't change strokes mid-length. See www8.garmin.com/.../GUID-F8057807-FC5A-45D1-BDA7-C62721206E00.html

RE: Forerunner 955 29.05

pw — Mon, 26 Oct 2026 20:25:25 GMT

Here are the results of my testing:

Activities that trigger the crash/restart:
• Run
• Walk
• Breathwork
• Health Snapshot

Features that work perfectly fine:
• Map
• Weather
• Music

It seems like the issue is directly related to sensor data measurement or the initialization of the FIT file recording or something like that.