08-14-2018
07:32
- last edited on
08-15-2018
09:43
by
MarcoGFitbit
08-14-2018
07:32
- last edited on
08-15-2018
09:43
by
MarcoGFitbit
My Versa stopped being able to maintain a GPS connection over Bluetooth several weeks ago after an update. I tried every thing that Fitbit recommended to do and nothing worked.
I use the Pixel XL 2 and I always use Bluetooth headphones while running which is what I got the Versa for . I believe i have found a fix, at least for my phone and I've had no issues offer the past 5 days. It is a very simple fix.
Right before I did the fix I installed the Strava app and set it up to access my Versa however I don't think it has anything to do with the fix. What I did was turn off bluetooth and go into my Bluetooth app settings and DELETED it's data and cache. This basically resets the Bluetooth app itself and it deleted every Bluetooth device connection. I then turned bluetooth back on and went into the Fitbit app and accessed my Versa through it to start a manual sync. This made the Fitbit app automatically pair the Versa to my phone again.
Before this the Versa did not appear as a connected Bluetooth device but now it does. I have gone on several runs and my Versa no longer gets stuck on that "connecting" status that never actually connects. I think that somehow the Versa is not creating a properly configured Bluetooth connection during initial setup which causes all the issues.
I hope this fixed the Bluetooth issues for most of not all of you even if you're not on an officially supported device as I am.
Moderator Edit: Clarified Subject.
08-15-2018 09:46
08-15-2018 09:46
Hello @freddybigs10, I hope you're doing well, it's nice to see you around.
I appreciate your participation in the Forums and for having taken the time to share your experience and the troubleshooting steps you took in order to resolve the Connected GPS issue with the Versa on your Pixel XL 2. I'm sure your steps will be very helpful for many members of the Community facing the same situation.
Thanks again for sharing this information with us, please keep me updated about this situation. If there's anything else I can do for you, please feel free to reply.
08-15-2018 11:18
08-15-2018 11:18
No problem.
Anybody that tries this fix please reply to the thread so that the community can verify the effectiveness of it. Please add what phone you're using as well to see if it works even on currently unsupported devices.
08-15-2018 14:03
08-15-2018 14:03
For those not sure what I'm talking about.
08-16-2018 03:42
08-16-2018 03:42
Tried but it did not work
12-29-2018 14:24
12-29-2018 14:24
Worked for me! Thanks!
12-31-2018 08:15
12-31-2018 08:15
Hello @Emk616, have a warm welcome to the Fitbit Community, it's great to have you on board. Thanks for joining the conversation and let us know the instructions provided by @freddybigs10 were helpful for you, I'm very glad.
In case you have some spare time, I would like to invite you to visit our Discussions board where you will find great tips and encouragement from other members and if there's anything else I can do for you, please keep me posted!
01-06-2019 11:51
01-06-2019 11:51
Thanx a million!
This solved it for me on a OnePlus 3T with android 8.0.0.
This should be part of the official troubleshooter.
I lost hours ans hours resetting, unpairing, re-installing, etc. And the fix is so simple.
01-06-2019 13:38
01-06-2019 13:38
Installing the latest firmware update appeared to fix the problem. I have had good connection through several runs with no drops.