This helped me too, I haven't updated Android. My Fenix 5 stopped synchronising and I unpaired it. Was unable to pair after that until I tried to clear bluetooth cache.
So I've had the Fenix 5 Sapphire for a few weeks now and enjoying it. Last couple of days it hasn't been connecting and therefore not syncing to or showing notifications from my Galaxy S7 edge though (which is up to date and running latest available build of Android Nougat 7.0). I tried to reconnect from the garmin connect app but and I had to key in the code showing on the watch (like usual), however it still wouldn't sync. So I deleted the watch from my phone's list of bluetooth devices as well as from my devices in the Garmin connect app and tried to re-connect the watch as a new device - still no luck. It sits on the "Connecting your Fenix 5" screen for a while with the progress bar at around 5 percent before it suddenly says "pairing failed" and giving me the option to retry.
I've reinstalled the connect app, and now even factory reset the watch, but it still wont connect to the phone via the garmin connect app. And yes the watch is in pairing mode when I try to connect.
Watch software is 2.90, Garmin connect app is version 3.17. After working fine previously, wifi also stoppet working, and obviously hasn't been working after the factory reset either as I can't connect to the phone.
Any help is appreciated.
Thanks! This fixed my issue for a fenix6...
Thanks, fixed my pairing issue!
Cheers!
This helped me too, I haven't updated Android. My Fenix 5 stopped synchronising and I unpaired it. Was unable to pair after that until I tried to clear bluetooth cache.
Mike22's method fixed it for me as well with some minor changes, the full steps I did:
1. Switching off BlueTooth
2. Going to , Settings -> Apps -> Show System Apps -> BlueTooth
3. Force Stop BlueTooth
4. Go to Storage -> Clear Data & Clear Cache
5. Switching On BlueTooth
6. Restart your phone
7. Then once again pair the device
I have needed to do this 2 times, after going on holiday to a different timezone, so the plane ride / network / timezone change may be causing this issue.
This. Can't thank you enough