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

Forerunner 235 not finding Bluetooth after 8.10 update

Former Member
Former Member

I updated the software on my forerunner 235 today and the up and down arrows stopped working. I had to reset the factory defaults and now the watch won’t find Bluetooth. I tried on my iPhone 7 that is running iOS 13.5 and on an older iPad mini. The Bluetooth pairing just keeps spinning and eventually says it failed. I restarted the watch and the phone. I removed the watch from the garmin connect App too. Now I have a nice watch that connects to nothing. And it is incredibly frustrating.

  • Former Member
    0 Former Member over 5 years ago

    It's a breath of fresh air to read this post and know I'm not going crazy. The same thing happened to me after the most recent software update. I had to reset my Garmin 235 to factory default settings and uninstall and reinstall the Garmin connect app. Now in order to get it to connect to bluetooth I have to reset my phone and turn off and on my garmin device to get it to sync. Also, the Garmin has been showing me the incorrect time and even after a 12 mile run.. it says I've walked only 9,000 steps for the day. I've never had any issues with my watch until this last update. I'm beyond frustrated.

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    I have the exact same issues with my garmin forerunner 230 since I‘ve installed the latest software version 8.10 (ba3b68e).

    It is showing me a wrong time and connecting to my iphone (13.5.1) and latest garmin connect app is a mess. I pretty much fail to connect the watch everytime I try. I already reset the watch and got it connecting successfully only one time. At the moment I am not able to use it properly. GPS is also not working for me.  

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    I have exactly the same issue... My 235 doesn't connect to GPS and the date and time are wrongs...