Hi -
I have a Venu 2 Plus. I wear hearing aids, and I also connect my Samsung Galaxy S22 Ultra cell phone via Bluetooth to my car to receive and make phone calls. My hearing aids are my primary phone call device, with my car as an available device when driving.
I will never use the Venu 2 Plus to make - or even notify me - of phone calls. So, I currently have all the Venu 2 Plus phone call related settings disabled.
Garmin has a defect in their Bluetooth Hands-Free Profile implementation, and I want to make sure that their Tech Support actively works to correct this issue. This is a defective implementation and not a "feature enhancement". I am trying to find out how to make sure this gets worked by Garmin, and not just put aside as a potential "enhancement" years from now.
These are the Garmin's Hands-Free Profile defects: If I have Bluetooth enabled on my Venu 2 Plus and I am on a phone call over my hearing aids (or the car), the V2P will constantly and actively disconnect the phone call from my hearing aids/car and force the call back to my phone mic and speaker. This forced disconnect occurs every few seconds, making the call connection to my hearing aids/car impossible to maintain. Since I have disabled all the phone related settings on the Venu 2 Plus, the V2P should not have any effect on phone calls. But, this is not the case. Additionally, if go to my phone's Bluetooth settings for the V2P and manually disable the "Calls" profile (which would be a last ditch, sledge-hammer fix for this problem that shouldn't be necessary), I will constantly see a "Can't connect to Watch" pop-up notification on my phone approximately every 60 seconds.
I have never seen this type of behavior with any of my other Bluetooth connected devices. When I have disabled the phone call related settings on other devices (for example, my previous Samsung Galaxy Watch 3), those devices become invisible to my cell phone, and have no impact on phone calling or phone connections to other devices. Additionally, manually disabling any of the watch profiles should not result in constant error message pop-ups. Manually disabling or enabling a specific Bluetooth profile is not an error, and it shouldn't be treated as such.
How do I get this issue raised up to Garmin's developers to make sure it gets the proper attention and gets fixed?
Thanks!
