Bluetooth Keeps Disconnecting and Reconnecting to Phone

The issue is still not resolved for me. But observed that the watch looses the connection faster and longer when battery of the watch is at low charging level (<25%). This does not mean that the watch does not loose connection above this level. But when the connection is lost with charging level >25% the watch reconnects fast automatically. With charging level <25% the connection seems to get lost as soon as the display of the watch is switched off (quite sure about this). And reconnect only works when the displays of watch and phone are active (not so sure about this but it "feels" to be this way).

Quite annoying...

Is there anybody out there observing the same/alike behaviour?

I got my Vivoactive 5 a few weeks ago and its been great but its taken to dropping the phone overnight when I'm in bed (the phone and watch are less than a metre apart).  The connection comes back with powering the watch of and on but I've selected to update the software and I'll see if that solves it.

They need to fix the bug.

Looking at all the Garmin and other forums where this is discussed and no real solution provided. The bug seems to happen:

- Across a range of watches - so unlikely to be the watch device. If it is the watch they should fix that for all models.

- Across a number of Android phones - so could be caused by an Android update.I have tried the fixes (BT Map version, exclude from power management, reverting to previous Android version, resetting everything to no avail).

- With Garmin Connect on a range of Android OSs - so could be caused by Connect update.

I think that it is Connect as my phone/tablet watch combination was working fine until a Connect update over a year ago.

Two probable fixes:

- Bose Soundtouch speakers had a similar problem a few years ago ie speaker inexplicably loses connection over wifi and then have to setup from scratch each time. It took them years to fix the wifi state and polling algorithm. So Connect on Android could be updated to maintain the last Bluetooth connection state and work out how to connect again when Connect is run rather than saying its lost and then having to setup again.The aim is to make the app more robust and overcome any OS issues that may be introduced.

- If they can't fix the connection then update Android Connect so you don't need to step through the very clumsy setup process (I say no to just about every option). eg Was this watch previously connected - Y, then type 6 digit code.