This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Runscribe Plus bluetooth running power meter sensor: the watch FR945 restart if I try to connect

I have a Runscribe Plus pod. The watch  connects correctly with the Runscribe Plus as a footpod via ANT+ or via bluetooth. The watch connects as a running power meter as ANT+ correctly. If I try to connect to the running power meter via bluetooth the watch restarts. It's a firmware bug?

  • Yep. It is not just the Runscribe, it seems to be something introduced from FW2.48 onwards (have a little search on this forum). Any BLE sensor connection crashes the watch and causes a restart. Good news is (for me at least) that with the latest firmware (2.5) and ANT/BLE/BT software (2.6) it all seems to work again. Doesn't take away from the fact that this is another embarrassing and annoying failure of Garmin's software quality control procedures.

  • I'm in firmware 2.5 ANT/BLE/BT 3.6. If I go to menu and select search power sensor, the watch finds the bluetooth sensor. When I connect, the watch  reboots and the sensor is in the list any more.

    I don't have this problem with ANT+ sensor, they remain in the list. I hoped that with the new firmware the problem showed in multiple other threads in the 945 and Marq forum were solved, but it's still quite impossible to connect to ANT+ sensors. The only solution is to restart the watch three or for times and then all is fine. I wish Garmin-Blake could add a word here because this problem is very very annoying and frustrating. I could stand to not use bluetooth sensors, but ANT+ sensor MUST function without problems.