Forerunner 965 - Recent Threads

FR965 after 29.05: optical HR sensor dead (no LED), battery 100→0% in under 24h, backlight dims randomly — factory reset does not fix

3600480 — Mon, 07 Sep 2026 09:06:09 GMT

Device: Forerunner 965, software 29.05

Symptoms, all starting immediately after the 29.05 update and none present before:

Optical heart rate sensor does not work at all. No green LED on the back of the watch, day or night. Wrist HR shows "--" continuously. Verified: Settings > Sensors & Accessories > Wrist Heart Rate is On, no external HR strap is paired, watch is worn correctly.
Battery drains from 100% to 0% in under 24 hours. Prior to the update I was getting 14 days on the same usage: always-on display on, no music, gesture backlight, 5 activities/week without GPS, with GPS 1-2. No settings changed. Battery was normal on the previous firmware for 2 years of ownership.
Backlight dims unexpectedly during normal use — the display dims to low brightness while I am looking at it and the wrist-gesture timeout should not have triggered.

What I have tried:

Full power off (hold Light button until shutdown) and restart — no change.
Factory reset (Settings > System > Reset > Delete Data and Reset Settings) — no change. HR LED still does not light on a freshly reset watch, before pairing to the phone.
Checked for further updates — watch reports it is up to date on 29.05., no beta updates available either

RE: FR965 after 29.05: optical HR sensor dead (no LED), battery 100→0% in under 24h, backlight dims randomly — factory reset does not fix

1618730 — Sat, 24 Oct 2026 14:02:01 GMT

Hi everyone, I’m wondering if anyone else has experienced this issue with their Forerunner 965.

I bought mine in 2023, and over the past few weeks, I’ve noticed a significant decline in battery life despite using it the same amount as usual to record my workouts.

Previously, the battery lasted around two weeks on a single charge. This gradually dropped to one week, then needing to charge it twice a week. Now, the battery barely lasts a day.

Yesterday, the optical heart rate sensor suddenly stopped working while I was sitting at my office desk. There are no green sensor lights whatsoever on the back of the watch, and it no longer measures my heart rate.

I’ve already tried performing a factory reset three times, but nothing has worked. The sensor remains completely unresponsive, and the battery drain issue persists.

I recently came across reports from other Forerunner 965 owners experiencing almost identical symptoms after software version 29.05. Some reported that their heart rate sensors stopped working, their green lights remained off, and their batteries began draining within a day. Apparently, factory resets and even reinstalling or rolling back the software didn't resolve the issue for some users, with warranty replacement being the only reported solution.

I can't confirm whether my issue is related to this software update, but the similarities are concerning.

Honestly, I’m really disappointed. I bought Garmin expecting a premium fitness watch to last more than three years, especially with normal use.

Has anyone else experienced this recently? Did Garmin acknowledge the issue or offer a repair or replacement? I'd also be interested to hear from anyone who managed to fix it without replacing the watch.

Any advice would be greatly appreciated.

Training Plan

wolli188 — Sat, 24 Oct 2026 08:34:09 GMT

I can`t see a Forecast in the Garmin Portal when i create my Training for Swimming

power chart as datafield is not available in bike (neither outdoor and indoor)

Luko79 — Sat, 24 Oct 2026 05:41:15 GMT

as user manual says:

but it is not available: (only speed, hrm, elevation and barometer)

and as i read, it is missing in fenix 9/8 , FR970 and in other models too. (i tried it with active power meter, no difference)

so, why is it missing, or if it is removed, why is it in the actual user manual/s/? (in every user manuals of mentioned devices above)

Bluetooth Connection unstable, audio stuttering Firmware 29.05

7385615 — Wed, 14 Oct 2026 16:46:57 GMT

Since the last Update to Version 29.05 Bluetooth Connection with Beats earbuds is unstable and frequently disrupted. Additionally heart rate monitoring is much more unreliable with jumping heart rate during sessions with setting of false resting heart rate. Further availability of aerobic and anaerobic indices have been cancelled in some activity profiles. Before that update everything was fine.

Tried every hardware reset, reconnect etc.

Anyone else with these problems?

RE: Bluetooth Connection unstable, audio stuttering Firmware 29.05

7419217 — Fri, 23 Oct 2026 14:34:25 GMT

Same on 955.

I analyzed the fit file with fitfileviewer dot com and there's something logged on it.

timestamp(s)	device index	device type	manufacturer	serial number	product	software version	battery status	ant network	source type	battery level(%)
21/10/202606:54:56	creator	-	garmin	3501154661	fr955	29.05	-	-	local	-
06:54:56	1	barometer	garmin	-	fr955	29.05	-	-	local	-
06:54:56	2	gps	garmin	-	ag3335m	13.00	-	-	local	-
06:54:56	3	heart rate	-	39644	-	-	good	antplus	bluetooth low energy	56
06:54:56	4	accelerometer	-	-	-	-	-	-	local	-
06:54:56	5	sensor hub	garmin	-	4025	35.10	-	-	local	-
07:22:12	creator	-	garmin	3501154661	fr955	29.05	-	-	local	-
07:22:12	1	barometer	garmin	-	fr955	29.05	-	-	local	-
07:22:12	2	gps	garmin	-	ag3335m	13.00	-	-	local	-
07:22:12	3	heart rate	-	39644	-	-	good	antplus	bluetooth low energy	58
07:22:12	4	accelerometer	-	-	-	-	-	-	local	-
07:22:12	5	sensor hub	garmin	-	4025	35.10	-	-	local	-
07:23:24	creator	-	garmin	3501154661	fr955	29.05	-	-	local	-
07:23:24	1	barometer	garmin	-	fr955	29.05	-	-	local	-
07:23:24	2	gps	garmin	-	ag3335m	13.00	-	-	local	-
07:23:24	3	heart rate	-	39644	-	-	good	antplus	bluetooth low energy	58
07:23:24	4	accelerometer	-	-	-	-	-	-	local	-
07:23:24	5	sensor hub	garmin	-	4025	35.10	-	-	local	-
07:25:02	6	whr	-	-	-	1.00	-	-	local	-
07:25:13	3	heart rate	-	-	-	-	unknown	antplus	antplus	-
07:25:25	3	heart rate	-	39644	-	-	good	antplus	bluetooth low energy	58
07:52:43	3	heart rate	-	-	-	-	unknown	antplus	antplus	-
07:52:56	3	heart rate	-	39644	-	-	good	antplus	bluetooth low energy	59
07:53:00	creator	-	garmin	3501154661	fr955	29.05	-	-	local	-
07:53:00	1	barometer	garmin	-	fr955	29.05	-	-	local	-
07:53:00	2	gps	garmin	-	ag3335m	13.00	-	-	local	-
07:53:00	3	heart rate	-	39644	-	-	good	antplus	bluetooth low energy	59
07:53:00	4	accelerometer	-	-	-	-	-	-	local	-
07:53:00	5	sensor hub	garmin	-	4025	35.10	-	-	local	-
09:02:44	creator	-	garmin	3501154661	fr955	29.05	-	-	local	-
09:02:44	1	barometer	garmin	-	fr955	29.05	-	-	local	-
09:02:44	2	gps	garmin	-	ag3335m	13.00	-	-	local	-
09:02:44	3	heart rate	-	39644	-	-	good	antplus	bluetooth low energy	61
09:02:44	4	accelerometer	-	-	-	-	-	-	local	-
09:02:44	5	sensor hub	garmin	-	4025	35.10	-	-	local	-

07:23:24, event, session, start

07:25:02, whr, reset, 1.00

07:25:13, sensor, heart rate, unknown, antplusantplus

07:25:25, sensor, heart rate-39644, good, antplus bluetooth low energy

[FIT Log Analysis - Device: Garmin Forerunner 955 (Firmware 29.05)]

- Session State (06:54:56 - 07:22:12):
Stable simultaneous connection of BLE sensors (COOSPO H6M chest strap, REDMI Buds 8 Active) and wrist heart rate (WHR).

- Subsystem Crash / Hard Reset Sequence (07:23:24 - 07:25:25):
07:25:02 : whr --- 1.00 (Wrist Heart Rate subsystem reset/crash)
07:25:13 : heart rate ---- unknown / antplusantplus (BLE stack drop, sensor driver hard reset rather than signal loss)

- Recovery Phase (07:25:25+):
07:25:25 : heart rate-39644 -- good antplus bluetooth low energy (BLE stack re-initialization and successful reconnection)

Raw FIT Event Log Entry:
07:25:13 : heart rate ---- unknown / antplusantplus

Garmin - KS

RE: There is no animation on the Garmin Coach power plans

netchow — Wed, 21 Oct 2026 07:34:57 GMT

Exercise animations do not work in custom workouts created by the user. It only shows in premade workouts, like you said yourself. It is a big disappointment in my opinion too, but this is the reason why you don't see them.

There is no animation on the Garmin Coach power plans

1266365 — Thu, 15 Oct 2026 07:08:03 GMT

In Garmin Coach strength workouts, exercise steps cannot be opened to view instructions or animations, while the same exercises are interactive in premade workouts. Device: Forerunner 965, iOS.

Barometric sensor broken.... Again

Michiel193 — Mon, 14 Sep 2026 16:07:29 GMT

Recently I noticed that again the recorded height during activities is not correct. The watch calculates to much height differences. Also at night during sleep the height differs with tens of meters.

I got a replacement for this exact reason in December 2025, this replacement is now doing the same.

I’m wondering what could be causing this. I wear the watch 24/7 and have a close relationship with it, do 4–6 cycling and running activities per week. The watch also goes to the shower with me, but I don’t participate in any water sports.

Is the barometer in the Forerunner 970 or a Fenix of better quality?

RE: Barometric sensor broken.... Again

micchei — Tue, 20 Oct 2026 13:51:09 GMT

I don't know. Alti/baro sensor of my 955 stop working after two years. In my 945 after 2 years again. I never used my 970 in the swimming pool and it's ok after 15 months, but I don't use it in the water because I'm scared about mic/speaker. I want buy 965 for this reason

RE: unable to get GPS signal Ethiopia

wojciech.urbanowski — Tue, 20 Oct 2026 09:29:58 GMT

Have you tried this? https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-965/439054/forerunner-965-issues-after-update/2055739
Works for me in every location affeted with "can't get fix in normal way" issue.

unable to get GPS signal Ethiopia

paleita73 — Wed, 14 Oct 2026 08:17:58 GMT

Since yesterday I cannot get the watch to fix the GPS signal.

I tried resets and changing satellite configurations but nothing is happening, it seems it is not even trying to get the singal: bar is not moving.

Do you know if there is any problem with the satellite preloading file?

any suggestion?

Headphone stutter after 10 minutes, even with 29.05

foobarbaz123 — Thu, 27 Aug 2026 16:12:17 GMT

---

I have a brand new Forerunner 965, updated to the latest software version (29.05) and am experiencing severe bluetooth headphone audio stuttering after 10 minutes. The only "solution" seems to be to disconnect/reconnect the headphones, which temporarily resolves the stuttering, only for it to return 10 minutes later.

I'm using Soundcore Life A1 (TWS) earbuds that are up-to date software-wise. I have used them for over a year without issue with my old Forerunner 645M. I've never had connection issues with the buds pairing with my phone or laptop, or my old Forerunner, so the 965 or its software is the obvious suspect.

I've been able to somewhat reliably reproduce the issue in an isolated environment: with the watch on my desk in front of me (~ 30cm from my earbuds) and all other bluetooth devices disabled. If I disconnect/reconnect the headphones from the watch, then listen to music, I get stuttering at around 10 minutes.

My testing has involved listening to the same few albums over and over and combinations of the following:

1. Hard-resetting the headphones
2. Placing the headphones back in their case between tests
3. Toggling off/on the headphones via the watch between tests
4. Using only one earbud with the other in the case

and nothing seems to consistently reproduce/not the issue, but I am getting stuttering in the majority of my tests.

Are there any effective solutions been found to this issue? I'm happy to try whatever troubleshooting Garmin can advise.

RE: Headphone stutter after 10 minutes, even with 29.05

9309247 — Tue, 20 Oct 2026 07:09:11 GMT

Exactly the same issue for me. Just to add that when 965 is connected to my phone, there are no issues with playback. Turn phone bluetooth off it comes back exactly as you describe.

RE: Headphone stutter after 10 minutes, even with 29.05

foobarbaz123 — Mon, 19 Oct 2026 21:49:51 GMT

The FAQ steps do not resolve the issue.

Yes, I've tried two - Soundcore Life A1 and Soundcore P20i and both have the same issue
As above
Yes
No, they remain connected
Both
Both

I have been able to reproduce whilst sat inside (i.e. no activity) by disconnecting/reconnecting the earbuds, starting playing a (Spotify) album and waiting - I reliably get stuttering just before 10 minutes, typically with a single stutter around 9 minutes and gradually increasing in frequency around 10 minutes, until the music becomes unlistenable.

I was hoping for some lower-level technical diagnosis assistance - can I somehow create and share a bluetooth log captured while the problem is being reproduced?

combining multiple activities

5042168 — Mon, 19 Oct 2026 16:44:06 GMT

During a marathon run why sleave must have activated the screen to stop the activity tracking halfway and I started a new activity quickly after. How can I combine these 2 activities to be the complete marathon run I had started?

Serious PacePro malfunction during marathon – Forerunner 965 – race strategy fundamentally compromised

ciczack — Mon, 19 Oct 2026 13:59:21 GMT

Device: Garmin Forerunner 965
Software version: 29.05
Activity: Uppsala Marathon, Sweden, October 17, 2026
PacePro setup: Distance- and target-time-based plan, NOT linked to a GPS course

I experienced a serious PacePro malfunction during Uppsala Marathon. The problem fundamentally undermined my race strategy, which was built around using PacePro to manage my pacing throughout the race.

This was not a minor display inconvenience. PacePro failed to provide the essential feedback I was relying on to execute my marathon pacing strategy. After months of preparation, I discovered during the race itself that the feature could not be trusted.

What happened

The PacePro plan was loaded, and several functions worked correctly:

The target pace for each split was displayed correctly throughout the race.
Notifications appeared at every new kilometer/split.
The watch recorded distance correctly.
The planned split progression was therefore functioning.

However, several critical PacePro functions malfunctioned:

1. Ahead/behind time remained at zero

As far as I recall, the ahead/behind indicator remained at 0:00 throughout the race, regardless of whether I was running faster or slower than the planned pace.

This made it impossible to assess my accumulated time difference relative to the race plan.

2. Actual split pace appeared to show instantaneous pace

The large pace field on the PacePro screen fluctuated rapidly with changes in running speed, rather than showing the average pace for the current split.

These fluctuations occurred within individual splits, not merely when transitioning between kilometres (not caused by unreliable average calculations at the beginning of a new lap).

As a result, I could not reliably assess my actual performance against the target pace for each split.

3. Split progress bar failed during the first kilometre

During the first kilometre, the split progress bar did not advance as expected.

It started working from the second kilometre onwards.

The target pace and split notifications nevertheless continued to function correctly.

Why this is a serious issue

PacePro is specifically designed to help runners execute a predefined pacing strategy.

In a marathon, pacing decisions are critical, particularly during the early and middle stages, when small deviations can have major consequences later in the race.

I had deliberately structured my race strategy around PacePro. Its malfunction fundamentally compromised my ability to execute that strategy.

The problem could not simply be corrected once the race was underway. I was left without the accumulated time feedback and reliable split-average pace information on which I had planned to depend.

For a feature intended for race-day use, this is a serious reliability issue. A malfunction during a training run is inconvenient; a malfunction during a marathon can invalidate months of race-specific preparation and planning.

Subsequent test: same settings worked correctly

I subsequently tested PacePro again using the same settings.

On that occasion, it worked normally.

In particular, the displayed split pace behaved as an average: when I slowed down to walking speed, the displayed value did not immediately change to my walking pace.

This strongly suggests an intermittent malfunction rather than an incorrect understanding of the display or a persistent configuration error.

I cannot confirm whether the precise sequence used to select the running activity and PacePro plan differed between race day and the subsequent test.

Similar reports in Garmin's forums

Other users appear to have reported closely related problems:

Forerunner 965 – PacePro screen not updating correctly:
https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-965/345780/why-is-fr-965-pacepro-screen-static-and-not-updating-during-an-activity/1678136

Forerunner 265 – first PacePro segment skipped and ahead/behind not displayed:
https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-265-series/375718/pacepro-skipped-first-segment-and-did-not-show-ahead-behind

The apparent similarities raise concerns that this may be a recurring PacePro software issue rather than an isolated incident.

Questions for Garmin

Is Garmin aware of an intermittent PacePro bug in which split targets and notifications work correctly, but ahead/behind time remains at zero and actual split pace is not calculated or displayed correctly?
Could this be related to the initialization of PacePro when starting an activity?
Is this a known issue in software version 29.05, or has it been reported in other versions?
Is there a reliable workaround or pre-race procedure that can prevent this problem?
Can Garmin investigate the underlying cause and provide a software fix?

Most importantly, how can runners be confident that PacePro will work on race day when it can function perfectly in training but fail during an actual marathon?

I would appreciate a technical response from Garmin, rather than generic troubleshooting advice. Given the potential consequences for runners who depend on PacePro in major races, I believe this issue deserves serious investigation.

RE: Headphone stutter after 10 minutes, even with 29.05

9309247 — Mon, 19 Oct 2026 13:24:58 GMT

I am using earphones I27 with latest software. 965 playback stutters severely after a short time. V29.05

tried all the recommendations but still happening

RE: Headphone stutter after 10 minutes, even with 29.05

9309247 — Mon, 19 Oct 2026 13:21:03 GMT

I also have this problem on my new 965 using earphones on bluetooth I27 and software 29.05

RE: Bluetooth Connection unstable, audio stuttering Firmware 29.05

tekguy1 — Sun, 18 Oct 2026 14:05:08 GMT

I have been having issues with my 965 ver 29.05 - all the sudden my HR spikes above 170 even though the watch HR graph shows Blue and the words Easy - but HR spiked for several minutes. I took it off and cleaned the sensor and moved to other wrist - same issue - then I took it off waited for 0 HR and then asked my wife to wear it same went from 90HR and spiked to 150 right away.

RE: unable to get GPS signal Ethiopia

Luko79 — Fri, 16 Oct 2026 09:18:55 GMT

btw with best accuracy (multi-multi) or with the standard SatIQ setting in your case?

RE: Headphone stutter after 10 minutes, even with 29.05

Garmin - KS — Thu, 15 Oct 2026 17:43:51 GMT

For anyone experiencing the headphone stuttering behavior with their Forerunner 965 as described in this thread, please review the following FAQ: Troubleshooting Bluetooth Headphone Connections on Garmin Watches

If the issue persists, please let us know:

Have you tried recreating this issue using different models of headphones?
What model headphones are you using?
Are the headphones running the latest firmware/software available from the manufacturer?
- If you are unsure how to check for headphone firmware updates, please contact the headphone manufacturer for assistance.
When the issue occurs, do the headphones show as disconnected in the watch's Sensors & Accessories menu, or do they remain connected?
Does the issue occur indoors, outdoors, or both?
Does the issue occur during an activity, outside of an activity, or both?

Any additional details you can provide will help us investigate further. **

RE: Bluetooth Connection unstable, audio stuttering Firmware 29.05

Garmin - KS — Thu, 15 Oct 2026 16:57:57 GMT

Thanks for the post, 7385615! The Bluetooth audio interruption concern that you're experiencing appears related to the issue discussed here: Headphone stutter after 10 minutes, even with 29.05

In an effort to keep these concerns separate, please comment on that thread and we'll continue tracking the Bluetooth issue there.

With regard to the heart rate concerns, optical wrist heart rate can occasionally be affected by movement, wrist flexing, fit, sweat, or how the watch is positioned during higher-intensity workouts. Making sure that the optical sensor on the back of the watch is clean, and that the watch is being worn snug but comfortably, slightly above the wrist bone, may help. Additional suggestions to help improve optical heart rate accuracy can be found here: Garmin Wearable Optical Heart Rate Accuracy Tips

Lastly, when you mention that the aerobic and anaerobic indices have been cancelled in some activity profiles, could you clarify which metrics are missing and from which activity profiles? A screenshot of what you're seeing would be very helpful. **

RE: Bluetooth Connection unstable, audio stuttering Firmware 29.05

Jacquers — Thu, 15 Oct 2026 16:07:01 GMT

I haven't tried the new firmware. Maybe try downgrading. There are links to older versions. Search for 26.08 or 27.09

RE: unable to get GPS signal Ethiopia

paleita73 — Thu, 15 Oct 2026 11:34:34 GMT

GPS version is 13.00

my collegue with Fenix 7 pro has the same issue and also my Edge 530 cannot find the signal.

it is probably due to GPS signal jamming due to security concern.

strangely enough GPS on telephone is working or at least the services which should lever GPS signal work, but as far as I know they use a combination of data from GPS and "phone-cells" to get the position.