Garmin Forerunner 955 crashes when Bluetooth headphones connected

8053393 23 days ago

Hi All,

I Have a weird issue with my Forerunner 955. When I connect the BT Headphones and also my Garmin HRM Pro to the watch, it always Starts to lag and some point of the activity, sometimes after 30 min, sometimes directly at the beginning of the workout.

This Happened with my old headphones, but with the new ones as well. Lagging means that Audio starts to interrupt every 5 Seconds, and also the HR on the Watch going crazy, suddenly to 200 bpm or to 50 bpm. If I turn off the headphones, everything is going back to normal. Does anyone experience the same?

Happened with all Firmwares so far, current FW on the watch is 24.12.

Basically, the watch is not usable with Music and HR Strap. I use spotify as source for music.

Any Support appreciated.

Thanks

Top Replies

global_local 23 days ago +1

Try to use your HRM as an ant+ device, not a BLE one.

All Replies

0 global_local 23 days ago

Try to use your HRM as an ant+ device, not a BLE one.

0 8053393 23 days ago in reply to global_local

How can I configure that? I thought it uses ant + as default

0 global_local 23 days ago in reply to 8053393

The ant+ name will be added as a row of digits - something like "39195". BT connection shows something like "HRM Pro" You can try to delete existing/paired sensor and add another type.

0 YSGOH411 10 days ago

Mine having same issue after 24.12 FW update. i guess its memory issue, where playback and running activity at same time consume too much memory to a point it clash. Because in my case, the freeze/clash happened mostly when i start play the music, lap trigger during activity with prompt, ending the workout, which is exactly memory usage in watch will spike

0 8053393 10 days ago in reply to YSGOH411

Yeah, that are exactly my thoughts. That would also explain that it affects other parts like correct bpm measurement from hrm pro.

But i had this also with older fw Versions. I've now opened a case with Garmin Support and they are now deperatly trying to push this in the direction that my "no name" bt headphones are the cause, despite they're working fine with my smartphone and i had same issues with my soundcore x20 as well.

0 8053393 10 days ago in reply to global_local

Mine was connected with ant +. I tried changing it to BE, but no improvements, so i changed back to Ant+

0 nowster 9 days ago

I tried (once) connecting the watch to my Openshokz Aeropex, and the beeps were so loud it broke one of the transducers, which meant I needed a warranty replacement on the headphones. I've never connected the watch to any headphones in the three years since.