Garmin Forerunner 965: GPS not locking and inaccurate heart rate sensor

⚠️ SAFETY WARNING / FIRE HAZARD. This device contains lithium batteries. Improper puncturing or bending during disassembly can cause explosions or flames. The intervention requires precision and the assistance of a specialized technician is recommended. ReeFix provides this diagnosis EXCLUSIVELY for educational and informational purposes.

MAIN CAUSE

The dual anomaly of the Garmin Forerunner 965 (GPS not locking, inaccurate heart rate sensor) suggests a problem beyond a single component, pointing to:

1. Software Corruption or CPE Data (High probability: 60-75%): Often, expired or corrupted orbital prediction files (CPE/EPO) prevent quick GPS lock. Simultaneously, corrupted firmware can affect the calibration or operation of the heart rate sensor. This often happens after failed updates or if the device does not sync regularly.
2. Moisture Ingress / Internal Oxidation (Medium probability: 20-30%): Prolonged exposure to sweat, chlorinated water, thermal shocks (e.g., hot shower post-workout), or a small impact can compromise the seals. Saline moisture can oxidize the GPS antenna contacts and create micro-short circuits on the power lines (PMIC) that serve both the GNSS module and the heart rate sensor (AFE), making them unstable or inoperative.
3. Heart Rate Sensor Lens Deterioration / GPS Antenna Contacts (Low probability: 5-10%): Less likely to occur simultaneously, but deep scratches on the PPG sensor lens or misaligned/corroded GPS antenna contacts can cause their respective malfunctions. This is more of a mechanical problem.

VERIFICATION

Here are quick steps to try and isolate the cause:

1. Quick Software Check (DIY):
   • Connect your Garmin Forerunner 965 to a PC with Garmin Express or sync it via Bluetooth with the Garmin Connect app. Ensure CPE/EPO files are updated.
   • Check in Settings > System > About if the CPE file is "Current".
   • Perform a "Soft Reset" (usually by holding the Light button for 15-30 seconds until it turns off and on again) to clear temporary blocks.
   • If the problem persists, consider a "Master Reset" (factory data reset, you will lose unsynced data), often a solution for more deeply rooted software issues.
2. GPS and Heart Rate Test (DIY):
   • After the reset, go outdoors, to a place with a clear sky, and start a GPS activity (e.g., Run) for at least 10-15 minutes. Check for signal lock and stability.
   • During the activity, monitor the heart rate sensor. If it continues to show anomalous readings or "cadence lock" (heart rate equal to steps), a hardware problem is more likely.
3. Visual Inspection (DIY):
   • Carefully examine the heart rate sensor lens on the back of the Garmin Forerunner 965 for scratches, cracks, or obvious opacity.
   • Check for traces of moisture or corrosion around the edges of the case back or bezel.

OPERATIONAL OUTCOME

The decision depends on the outcome of the verifications:

• If the software solution resolves the problem (High probability): Great! You can continue using the device. Cost: 0€.
• If the problem persists after the software reset and inspection reveals no obvious damage (Medium probability):
  • Consult a technician. The cause is likely moisture ingress or a PMIC/RF chipset issue. A technician can open the device, clean the contacts with 99% Isopropyl alcohol electronics and check voltages with a Precision digital multimeter.
  • Estimated cost for technical intervention (diagnosis + cleaning/contact restoration): 50-120€. If the motherboard is damaged, repair might not be cost-effective.
• If visual inspection reveals severe damage to the heart rate sensor lens or signs of extensive ingress/corrosion (Low probability):
  • Consider replacing the device. Repair might require replacing the Garmin Forerunner 965 rear sensor housing (part cost 40-80€ + labor) or, in the case of logic board damage, exceed the value of a new device.

Output for technician: "The Garmin Forerunner 965 exhibits GNSS lock failure and PPG inaccuracy. CPE files updated and Master Reset performed unsuccessfully. Moisture ingress or PMIC instability is suspected. Verify antenna contacts, sensor lens integrity, and power supply voltages on GNSS/AFE modules."