My Versa GPS won't connect to Pixel3 XL

[SunsetRunner]

So, I am superfrustrated because my  Versa is in a constant state of "connecting" to my phone's GPS. I love to hike and I upgraded to the Versa from the Blaze because of the GPS feature. It would appear that this was a silly sales gimmick and after reading the boards, this is a huge problem! Come on Fitbit, figure it out and fix it please. I really don't want to have to go to Garmin to get a decent GPS tracker. 

I am running a Versa with Firmware version: 32.33.1.30, app version 2.84(201213341) on a Google Pixel 3XL.

Help please!

[SunsetRunner]

Hi, AFAIK the Versa does not have GPS on it's own but uses the GPS of you phone, just like it does with WiFi. 

[SunsetRunner]

Hi...i know that..that is why it is in a constant state of "connecting" so
all my GPS related activities don't get recorded with any sense of
accuracy. I have to run "map my hike" along with my fitbit to get some info
about time, cadence and distance. It is silly, when its a sold a feature.
Thank you...if you have a solution, please let me know.

[SunsetRunner]

Hi, might be a problem with your phone's GPS. Try this:

1. Turn off GPS on your phone.

2. Restart your phone

3. Turn GPS on again and see if that solves your GPS problem.

4. For certainty: Reboot your Versa after the above also by pressing and holding the left and right lower buttons untill you see the Fitbit logo flashing and release the buttons. 

Good luck.  

[nicoleproudft]

I'm having the same issue. Recently upgraded to Pixel 3 and now have issues with versa connecting during running. Starts off connected bit then loses connection. So frustrating when trying to monitor pace and distance while running!

[SunsetRunner]

hi...yes, it is frustrating. And I am getting zero help from them. I will
try again tomorrow. good luck.
you would think that they are constantly upgrading to work with new phones.

[Marrrmaduke]

@nicoleproudft @SunsetRunner Make sure your Versa syncs before starting GPS exercise. Also, make sure the Fitbit mobile app is not being optimized in your phone Android Battery Settings (Settings>Battery>Optimization). Also, make sure that Always Connected and Keep Alive Widget are enabled in the Fitbit mobile app. Finally, starting with Android Oreo I believe, any greedy processes and apps are getting killed by OS. Please lock Fitbit mobile app in the Foreground using Screen Pinning when you're using GPS during your workout.

[Quaz]

have the same issue and have tried all these. Its just constantly in the "connecting" stage. It'll finally connect, but minutes later it's at "connecting" again and that's where it stays

Its causing havoc with tracking. Did a hike Saturday - 7.35 k. Did exactly the same one today and it's 6.57k . That's a fairly significant difference .

There's soooooo many issues with this watch, it's actually quite flabbergasting how poor it is, not to mention the lack of acknowledgement from Fitbit.

Sad to say, but first and last fitbit

[SunsetRunner]

Hi!! I feel you! Seriously considering a Vivofit for the GPS aspect because
so much of my workout is GPS related. Fitbit is great for the gym but
anything requiring a GPS read is not working for me, my Versa or my Pixel 3.
Julie

[nicoleproudft]

Thanks for these suggestions. Unfortunately I have tried and they do not work. I feel like my only options are to use my old phone when running or to move on from Fitbit. So disappointing .

[Marrrmaduke]

@nicoleproudft When you go to Battery>Battery Usage and tap on Fitbit, is it marked as Not Optimized?

[nicoleproudft]

@Marrrmaduke@     As far as I can tell, battery optimization is not an option on the pixel 3 .

Edit: I found it and it is not set to optimize. My Fitbit syncs all day and steps are constantly updated. Go for a run and it connects at the beginning and then sporadically throughout. My steps also do not sync during the run, but has no problem syncing when I'm not in Run mode .

[SunsetRunner]

what isn't an option, GPS??? Its a google phone...has the best GPS
features. For some reason its not on the list of compatible phones.

[nicoleproudft]

@SunsetRunner sorry I meant battery optimization wasn't an option on pixel 3. But it is, just not in the main settings. Isn't the source of the issue anyways cause it wasn't turned on.

I also don't understand how the versa isn't compatible with pixel 3. I think it is a compatibility issue with Android Pie in general. But all new phones are going to have this OS so they really should be working on a fix for this

[Marrrmaduke]

@nicoleproudft did you pin the app to the screen after gps connected?

[nicoleproudft]

@Marrrmaduke Yes, I did. I might try disabling screen lock. 

[Marrrmaduke]

@nicoleproudft I second that idea. I just got my Pixel 3. Will try to test GPS tomorrow. Quick question, when you start your hike and gps is connected, then you lose the connection with Versa obviously, but, when you finish your hike how does the map look like in the Fitbit mobile app? Can u post example? I'm asking because Versa relays only what phone feeds it. It basically tells Fitbit mobile app to start gps tracking. So if you're getting a full map even tho versa says connecting that would mean it's a matter of relaying back the data to Versa for display aka BT connection and not Location Services getting killed by Android. 

[nicoleproudft]

@Marrrmaduke So it's very strange, the proper route does not show on the app (but the mile markers are along the route). But if I go to the actual website it does show the proper route - see pictures below. The proper route also uploads to strava. However distance and pace are not accurate on the app or on the website - both underestimated. I am training for a race otherwise wouldn't care all that much. From reading in the forums it seems like a lot of people have this issue. 

Hope you have more luck with your pixel!  

This is the map that shows on the appThis is the map that shows on the website

[Marrrmaduke]

@nicoleproudft interesting very interesting. So, it seems Fitbit mobile app map needs to be refreshed. I have already seen issues with maps not loading properly. Since the route gets recorded when started on your Versa, then location services are running. It seems tho the info is not getting calculated properly and fed back to Versa. My best guess would be it's Fitbit mobile app bug. Nothing wrong with your Versa nor phone. It's the app or the way it communicates with servers and back with Versa. Just to verify, you are receiving notifications during your run and you have a decent wireless coverage for the internet? No net no calculations.

ETA: What's the proper length of the route? And what's the running stride length in your Fitbit app? I think the distance you might see comes from rough estimate based on steps and whatever running stride length is in your presets. It should be based on GPS. It gets recorded but not calculated.

[nicoleproudft]

@Marrrmaduke that run was off by about 0.5 km. Which doesn't seem like that big of a deal but makes a huge difference for pace. Since switching to pixel my "pace" has slowed enough to cause my cardio score to drop by 3 pts!

By i am fairly certain that the main issue is with Bluetooth though. My phone and Fitbit sync perfectly fine in general, but do not sync in exerice mode (i.e., steps do not even update when I am running for over an hour). And usually after finishing the run when i look at the app it says there is a Bluetooth error (or connectivity error, not sure the exact wording). I'm really not sure if the issue is even on fitbit's end - I've been reading that there are known Bluetooth issues with pixel 3 (not sure if it is Android Pie in general). For example, pixel 3 has problems connecting to 2 Bluetooth devices at once .