03-08-2021
05:39
- last edited on
12-18-2022
20:47
by
MatthewFitbit
03-08-2021
05:39
- last edited on
12-18-2022
20:47
by
MatthewFitbit
Attention Google Fitbit software bug fixers:
My Garmin has ZERO problems getting & keeping a Bluetooth connection (Bluetooth Vers 4 & 5, Android Vers 8 & 10)
You need to fix the problem Versa has with Bluetooth & the quirky "Versa Controls.". The problem is not with the varying phones, it is the software & it needs to be fixed PRONTO. Frustrating.Thank you, UX
Moderator Edit: Clarified subject
03-10-2021 08:38
03-10-2021 08:38
Fully agree, that especially for Android user the experience is not fully plug and play. Does a support forum indicated that there are big issues? I don't think so: Would you be here wrting questing if everything works fine? No. How many questions do you see here releated to that issue? How much percent of the sold devices are represented by these questions?
So a fair question: Are just here to share your frustration and you are already done with Fitbit or are you honestly looking for help?
If you would like to have the issue fixed, I ask you again to share some screenshots of the settings you have configured as every Android vendor has some different settings / naming conventions. Hence, we can get deeper into your settings to solve the issue. A said, I would much appreciate if you can attach pictures of the different settings:
It doesn't help that you compare the Fitbit smartwatch with a headset which will run for several hours instead of 6 days+and don't require any app to be fully connected. As said, the issue is neither related to your Bluetooth nor your smartphone OS version. I am running also Android 10.
03-10-2021 08:46
03-10-2021 08:46
I am trying to share my comments & frustration with the new developers (Google). As far as I can discern, there is no direct path to air these connection frustrations which are everywhere on this forum. I am a longtime Fitbit user, 1st time with this particular model (Versa 3) as I thought I wanted to "upgrade" from my current Garmin.
03-10-2021 08:58
03-10-2021 08:58
Ok, you may submit a feature suggestion to get that done:
https://community.fitbit.com/t5/Feature-Suggestions/idb-p/features
Back to your issue: Are you interested in solving it or would you like to wait several months until the new owner will may fix the issue in an upcoming app release? I would assume that still the same developers are running the app development. Hence, if you are looking to "upgrade" from your current Garmin watch you could actively assist to get your issues fixed.
03-10-2021 09:05
03-10-2021 09:05
It may be in everyone's best interest the developers dispatch a universal fix. Thank you very much for all your offers of help! 🙂
03-10-2021 11:10
03-10-2021 11:10
@sancho90 Simply stated - you are wrong. The issue IS with Fitbit bc I have similar problem. The Bluetooth setting on an iPhone absolutely indicates if it’s connected or not. The issue comes when as you say the Verse disconnects and then tries to automatically reconnect. The reconnection then spins and never completes. You then have to actually go into Bluetooth devices and Forget the devices - both. And re pair them back to your phone. This should not be the case period.
03-10-2021 11:37
03-10-2021 11:37
Simply stated, you must be wrong as well. I have no clue of the iOS implementation, but with proper settings for Android 10 I don't have any issues so fsr with my Huawei P30 Pro. Believe it or not.
I have my Sense since relase in September 2020 and haven't it unpaired yet. Synchronizing it permanently in the background every day. Have the mobile not in distance during night and notification come at the morning passing by the mobile very smoothly.
At least for Android you cannot see the Bluetooth connectivity status of your Fitbit watch at all. One and only option you have is to unpair the device, nothing else. You have to fully manage the connection within the Fitbit app.
05-12-2021 14:15
05-12-2021 14:15
Reading this feed. I have the exact same issue with the on wrist calls. Called fitbit today they talked me through the steps and it worked whilst on the phone. Had someone else call my mobile afterwards and BOOM back to connection error. Not too happy. My ring doorbell notifications also dont appear on my watch. No impressed - only day 2.
05-12-2021 19:15
05-12-2021 19:15
Fitbit versa 3 is the worst one i have had yet 😒
05-12-2021 19:31
05-12-2021 19:31
05-16-2022 11:58
05-16-2022 11:58
For me it's completely loss of connection, like for answering the phone on my watch. Interestingly enough, it still sinks my steps to the phone. But I can't make phone calls. When I turn on and off the Bluetooth. It doesn't reconnect it. Sometimes. I'll even see the phone disconnect symbol on my watch. And my phone is right next to my watch at the time. Still have everything figured out what's going on. When this used to happen with my versa One, I could just turn on and off the Bluetooth and that would fix the problem. Looks like I'm not the only one with this issue. It's so annoying.
05-17-2022 12:26
05-17-2022 12:26
For phone calls @Mukti79 the Versa 3 Controls need to be paired, and notifications have to work.
When it comes to seeing the connection icon, I usually open the fitbit app. The first thing that happened is a sync.
05-17-2022 21:41
05-17-2022 21:41
Hi Rich, thanks for replying back. My watch was paired initially and had no issues answering calls. Sometimes it works and sometimes it doesn't.
I0 have noticed, I'm not able to connect to my watch speaker for talking on watch after my car Bluetooth used prior. Other times I can still use my watch to answer calls. Is there anything else that I can do? When I did test notification, it worked fine though