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

Why the restriction of bluetooth pairing with 1 phone only

Hello,

I use two phones - a big Samsung s22 Ultra as my main phone. But, while running/biking/gym, I keep a small iPhone 13 mini. I was able to pair with both the phones - ofcourse active connection is only with one phone at a time. I found keeping bluetooth off of the other phone works the best in case both the phones are in the vicinity of the waatch. The watch connects with the app and data is synced without any issue. It was the same with my earlier device - Forerunner 245.

But, on Venu 2 Plus - the voice function does NOT switch. I was wondering why? It is like a blutooth headset in terms of voice function, isn't it? I can pair my blueooth headset with any number of phones. Then why this watch does not connect with whichever active phone it finds for the voice function?

I know the official Garmin stand is to pair with only one phone. But, why the restriction/limitation?

Garmin Support: please ask dev team to support multiple phones - we can live with 1 active device at a time - but, all the functionality (data sync and voice) should switch

Thanks

- a new venu 2 plus user

0 Garmin-Inder over 2 years ago

Hello,

This is a great question! I'd like to gather a some additional information to look into this. Do you mind if I email you to follow up on this?

0 DesiRunner over 2 years ago in reply to Garmin-Inder

sure. anytime

0 Scott over 2 years ago

As a workaround, I found if I "forget" the watch and pair it again to the phone I want to use, the voice and phone functions will work (data sync seems to work all the time). But you'll have to do that every time you switch phones. Not great, but it may work for you.

0 DesiRunner over 2 years ago in reply to Scott

Thanks Scott.

Right, pairing it again every time will be a pain. But, may be necessary unless Garmin fixes it.

AFAIK there is nothing in the bluetooth specs which mandates this kind of behaviour. Perhaps it is Garmin's own interpretation