Related
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

Bluetooth reconnect issues

Josh9216
over 7 years ago
Hi

Picked up my Vivoactive 3 yet encountered Bluetooth issues straight away. The main issue is whenever the Bluetooth disconnects it doesn't automatically pair back up with my phone and just stays as 'waiting'. So when the watch updates, I have to go into the Connect app. Remove my device. Re-add my device and pair up again manually. Same if I put my phone on airplane mode.

My phone isn't on the list of BLE devices as it's a Wileyfox Swift 2 Plus but meets the compatibility standards.

I've tried reinstalling the app etc no luck. Still doesn't reconnect.

Any help is much appreciated.

Thanks
Josh
  • 0 over 7 years ago
    This always works for me when I have your issue (which, for me, is really only from time to time).

    Go to the devices list in Mobile Connect, then pull down the notification bar and turn off bluetooth. Then close the notification display. Your phone should say that Connect wants to turn on bluetooth. Do that and wait maybe 10 or 20 seconds. It should reconnect.

    The only caveat is that a lot of people seem to have problems with Nougat.
  • 0 over 7 years ago
    Thanks Phil. I think a variation of your fix solved it.

    I had re-paired so many times and when it asks for the pair code, it would always ask via Android which would pop up in the notifications bar. For some reason, and I don't know how, This single time...it asked for the code via the Connect app and since then I've had no issues.
  • 0 over 7 years ago
    You can also pair via Android and then define your watch as a trusted device in Android. If you do pair via Android, you can go to the Connect ap, long press on the VA3, and choose update the connection.
  • 0 over 5 years ago

    I know this is an old thread but I'm just going to put this here because, even now, I'm on the Fenix 6 and was having the exact same issue.

    Whenever I left bluetooth range the watch and phone would never reconnect automatically. The quickest way to reconnect was just to unpair in the bluetooth settings of the phone and reconnect the fenix once it was found (almost instantly), enter the code and we were back in business....until I went out of range again. 

    What I think fixed it for me was reconnecting this way and then restarting my phone straight after. Very simple but now my watch reconnects automatically after being out of range Slight smile Hopefully this helps someone because it's so frustrating!

  • 0 over 4 years ago in reply to Bwilliams94

    After more than two years without any connection issues, my watch just stopped to reconnect after an update on Garmin Connect App on Android Phone (1-2 days ago). I tried several tips and tutorials, but none worked until I tried this simple path.
    Thank you, very much!

  • 0 over 4 years ago in reply to Andre Ribeiro

    When I receive a new text message, my phone shows 2 or 3 old messages (including my replies so it reads like a conversation) and the new message is always at the very bottom of the thread so there was a lot of scrolling to go through to get to new message. Support had me remove device from The Connect app, and add it back. Still have the bizarre text issue and now, every time I go out of range of my phone and come back into range, I am told to re-pair my watch to my phone. This is new as it used to automatically reconnect. The device was/is paired through the Garmin app. Any suggestions? I have tried uninstalling and reinstalling the Garmin Connect app and that has not fixed anything. My phone is a Samsung A71 5G run Android 10 and thr Garmin Connect app is version 4.36.3 I don't want to add my watch as a trusted device because then my phone will never lock when I am in range and I would prefer for my phone to lock. 

  • 0 over 4 years ago in reply to Andre Ribeiro

    Hi, this just started happening with my Forerunner 45 a few days ago. It's driving me mad. Has anyone had any response from Garmin on this incredibly frustrating issue? I'm close to taking a hammer to my piece of crap watch.