Bluetooth not staying connected

Same problem here. VA4 and iPhone 11

Same problem with an iPhone 8.

I have the same problem with VA4 + Lenovo P2 (on Android).

Can everyone reading this thread please comment if you have the same problem. Maybe we will then get enough arttention to get the problem solved.

Unfortunately this has been going on for months with zero help from Garmin. 

https://forums.garmin.com/sports-fitness/healthandwellness/f/vivoactive-4-series/218782/bluetooth-issues-after-latest-firmware-update

Mine still requires disconnecting, restarting the watch, restarting BT, etc, just to keep it connected. It is extremely disruptive, especially for someone like me who uses the watch for weather and notifications because I cannot carry my phone with me everywhere I go. So unreliable and I have missed messages due to the fault.

So if you don't have your phone with you, how do you expect to get the notifications you mention? They come from the phone via, Bluetooth which is a moderately short range connection (up to 100m outdoors, less depending on signal strength and obstructions to RF signals) Not trying to be rude, just curious.

I just mean I don't have pockets and carry it with me everywhere. At home, I leave it in the kitchen and am within range of it for getting messages if all is working as it should. At work, it is in my bag and again, not on my person but within range. I just don't have the opportunity (or desire) to keep it in a pocket or hold it where I pull it out at every notification, if that makes sense.

That makes sense, you obviously understand the limitations of the technology, which is an important part of reliability.

Have you contacted Garmin via their support channels?

Thanks. I have tried to make contact, and have gotten one canned reply about restarting and such, and after trying again, no reply. It is unfortunate.

I usually have my phone in range (in pocket). And only randomly I get the notification on Garmin, most times not. Also I expect that when the phone is out of range, it should reconnect automatically when it is in range again. This seems not happen. And what I have read the support always offers the reboot, reconnect options which are obvious solutions for me.