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

After losing a bluetooth connection I have to reboot my phone to reconnect to Garmin Edge or Vivosport

Hi,

I have a Samsubg J5 with the latest version of Garmin Connect installed. I have an Edge 25 and vivosport band both connected to the app. If a device goes out of bluetooth range the device disconnects. Bringing the device back into the range of the phone does not reconnect either device.

The only way I can find to reconnect either device is by rebooting the phone. After a reboot the devices reconnect perfectly. It's a pain having to reboot the phone to get them to reconnect.

I have tried turning bluetooth on/off in the phone, but that doesnt repair the devices.

Is there anyway to get the devices to reconnect without rebooting the phone?

Thanks

0 trux over 4 years ago

Try the tips from the Sync / Connection Troubleshooting Guide

0 2847966 over 4 years ago in reply to trux

Nothing in there sounds like my issue. The devices pair perfectly after rebooting the phone, and work correctly. It's just if the Bluetooth connection gets dropped they only way to repair is a reboot of the phone . They do not auto connect, restarting Bluetooth doesn't do it. Restarting the app doesn't. Only a reboot

0 trux over 4 years ago in reply to 2847966

That sounds exacly like the majority of cases that the troubleshooting guide is about. It does not speak about pairing only. If you saw only that, then you likely did not look at the guide carefully enough.

0 2847966 over 4 years ago in reply to trux

I have found that when they won't repair that if I stop and start Bluetooth on the Garmin device they will then repair.

But Bluetooth is still active on the Garmin as other devices can see it as a Bluetooth device.

When they are in the bad state if I go into the Android Bluetooth and click on the device it doesn't attempt a repair

0 trux over 4 years ago in reply to 2847966

And that's what the troubleshooting guide is coping with too, and that's why I pointed you to it.