Connected GPS - won't stay connected

[Reading_Tim]

Charge 2 & OnePlus 6 running Android Pie & Jan 19 security patch level - since app version 2.87 connected GPS just won't stay connected - the app closes and stops logging location after a minute or two.  HR data seems unaffected, and I don't bother with notifications on the charge 2. 

I've tried clearing the cache, resetting the tracker, uninstalling and reinstalling the app. I've enabled all-day synching and always connected, and ensured the app isn't battery optimised, all to no avail.  

Any further suggestions as to fixes; is this a known issue, and will Fitbit do their usual trick of blaming the user for having a non-supported phone whereas it's the shortcomings of their own app which is the problem?  

[LanuzaFitbit]

Welcome to the Forums @Reading_Tim.

Thanks for bringing this up and sharing all of the steps that you have tried to get the GPS to connect. I'd like to take a closer look at what is going on. 

In this case I'd like to recommend that you try to update the app to the 2.88 version. You can click here to read more about it. 

In addition to that I'd like to ask when did it start happening? 

Look forward to your reply.

[Reading_Tim]

Lanuza,

I am on version 2.88 - the problem started with the download of version 2.87 and has remained broken into the latest version.  It hasn't worked properly since v. 2.86.  My phone (a OnePlus 6) got an update to its OS, including the January 2019 security patch in late February, but the problem preceded that - it hasn't stayed connected properly since 15th February 2019.  

[LanuzaFitbit]

Hello @Reading_Tim.

Thanks for that clarification and further details on the matter. I apologize for the delay in my response.

There is currently a new version, 2.89, out so please update to that in case you have not. Let me know if it is already in that version. 

In the meantime I'd like to ask some questions:

• Are you experiencing other syncing issues of any kind?
• What about notifications? 
• Was your phone running a previous Android version in the past? If so, did the issue start about the same time it updated to Android 9?

Look forward to your reply.

[Reading_Tim]

Hello @LanuzaFitbit 

I have upgraded to v.2.89, but the problem remains.  

To answer your other questions:

• I'm not experiencing any other syncing issues - everything else seems to work fine
• I don't bother about notifications so can't comment.  
• The phone's been running Android 9 since last October.  The problem began with v.2.87 of your software, not my phone's software.  

It's now been broken for a month, and it's getting really boring - I trust you can appreciate this frustration.

[LanuzaFitbit]

Hello @Reading_Tim.

Thanks for answering those questions! 

It is possible that this is happening because of some know issues with Android 9. It is possible that one of the updates caused the issues to start and thus the connection with the phone is not stable so this happens with the Connected GPS. 

In the meantime I'd like to recommend that you try enabling notifications and checking if the connection is stable during the GPS activities with them turned on.

Look forward to your reply.

[Reading_Tim]

Hello @LanuzaFitbit 

Notifications enabled, but no success - the app disconnected from the tracker and shut down after approximately 6 minutes, which is the average time it stays running before it shuts down.  

This problem is solely related to the app, and not any android updates - it arrived with v2.87, and has persisted to this day.  

Perhaps fitbit need to consider a way of making old app versions available, so users can deliberately downgrade to an older version of the app which they know works?  

[Reading_Tim]

Hello again @LanuzaFitbit 

So, another month, and another app update later, and the problem is still here.  It hasn't worked for the best part of 3 months.  

This is pretty poor, don't you think?

[joe337]

Having the very same problem!.  Stopped using Charge2 altogether.

Running version 2.92 on Onplus 6 with Android 9.

[userkv8031]

I have been having a similar issue with the OnePlus 6t. It will log for about 10 minutes then lose the connection. I changed the battery settings so that the app is not optimized. Changing this helped the tracking as it would stop after 2-3 minutes when it was optimized. It almost seems like an issue the app is having with a keep alive command to keep the phone/fitbit connection alive while doing an exercise with connected GPS. I have noticed if I keep checking the app and forcing a sync, that will keep the connection active and GPS working.

[hkbikee]

Are newcomers allowed to add? I just do, feel free to delete.

I have a Charge 2 for a few years, but so far only did jogging - without phone. So no tracking. A few weeks ago I switched to 'Bike' mode - with phone.

App is Android 2.92. phone is Xiaomi Mix 2s. What I like is the GPS map, here is what I had so far:

20/4 - perfect tracking

21/4 - perfect tracking

22/4 - perfect tracking

27/4 - 0.07 km 01:38:01 mins - half map map ok, rest many errors, should be 10+ Km

28/4 - 0Km 59:28 mins - Looks like only 2-3 spots got logged

Phone settings:

BT ON

app is ON (do I need to?)

Not sure this is relevant, on 27 + 28 I stopped and took pictures. My pictures are with GPS location.

[Reading_Tim]

Glad it's not just me, and yes, this seems to be the problem - there's something which doesn't keep it alive and running in the foreground, so as a result, the gps connection is terminated.  Reawakening the phone restarts the app, and the gps connection, although your track leaps from the last known location to where connection was re-established.  

Anyway, the problem still isn't fixed, and another couple of months and app updates have passed.  Fitbit have basically stopped replying (calling @LanuzaFitbit - anyone out there...?!?), indicating they clearly don't care...make of that what you will.  

[Brandtair]

Got somewhat the same problem here, 

On my s10(officially not supported yet) when the screen is on i get around 30 seconds of connection. Then it stops until I unlock my screen again. And as long as my screen is on the connection holds. Apart from that, after cycling it showed me the map with a correct starting point and ending point and the correct time. Just the distance was 187 meter instead of several kilometers which it actually is.

They seem to me two bugs that are similar to the problems experienced by the others here.

I tried everything on three trips to keep the connection going but i can not get it to stay connected.

[hkbikee]

I had another try today. I used an old phone. wifi and data was OFF, BT and GPS was ON. Fitbit app is installed and paired. I don't recall if it was running or not. Phone has no SIM. 

Perfect tracking!

For me it's a good enough alternative till they get their act together again. 

BTW, no, I wasn't mad, I had my regular phone with me. 

[SunsetRunner]

Is the problem still there? I own a Oneplus 5 with Android 9 (Pie) and I just bought a Fitbit Versa.

If the connected gps feature won't work, I'm returning it.

[hkbikee]

---

@SunsetRunner wrote:

Is the problem still there? I own a Oneplus 5 with Android 9 (Pie) and I just bought a Fitbit Versa.

If the connected gps feature won't work, I'm returning it.

---

Not sure about the, but my problem is still there. Here is my temporary conclusion: The phone you use must be on the Fitbit compatible phone list. Just installing the app ain't good enough. I monitor the situation with my Xiaomi Mix 2S (not compatible), but for tracking I use my old but compatible Nexus 5 - and that works and tracks perfectly.

Beside tracking, or lack thereof the Mi has another problem, data dies from time to time when app and watch are connected, means no calls and no whatsapp. 

For now I will just use the Nexus 5. I bike, though having two phones with me isn't a big issue. For those that my consider getting an old Nexus 5 - they are lite and nice, but their battery life is rather poor. I would say max 5 hours - and that is WITHOUT SIM!

[Reading_Tim]

---

@SunsetRunner wrote:

Is the problem still there? I own a Oneplus 5 with Android 9 (Pie) and I just bought a Fitbit Versa.

If the connected gps feature won't work, I'm returning it.

---

I don't know to be honest, as I'd given up - Fitbit support don't seem to care, and had stopped bothering to reply to any messages. Make of that what you will in terms of their attitude to customer support....I think it speaks volumes, and it isn't good.  

However, I notice that my phone (Oneplus 6) has now appeared as an officially supported device, so will updated to the latest version of oxygen and the fitbit app and try again.  

In terms of whether you return your fitbit, it's up to you.  Unsupported devices might work, they might not.  Connected GPS on my Oneplus 6 worked perfectly from summer 2018 until the beginning of 2019, then something broke.  Whether it was the fitbit app, the phone's operating system, or a google/android thing, I don't know.  Prior to the Oneplus 6, I had a Oneplus X which had a similarly chequered past in terms of connected GPS working properly, but these corresponded exactly to fitbit app updates, making me suspect that each version of the app introduced more bugs than it fixed....  In its defence however, it was only Connected GPS which didn't work properly, the other stuff (heart rate monitoring, sleep tracking etc) worked fine, but I want to upload my exercise to Strava.  

So if you decide to keep it, it's basically a lottery as to whether Connected GPS works, and for how long.  It might, it might not.  It might stop for an app update or two, then start again.  It might not.  Fitbit won't care, and will hide behind the 'unsupported device' line, or simply stop replying to you.  Personally, if it was up to me: if I had my time again, and having got more into sport (especially cycling and triathlon), I'd buy a Garmin.  

[Reading_Tim]

ok, so whilst I'm probably talking to myself (fitbit sure as hell aren't listening), I have a potential fix for Oneplus/Oxygen users.  

My issue seems to have been fixed by disabling both "deep optimisation" and "sleep standby optimisation", which are advanced optimisation options within battery optimisation.  (battery>battery optimisation>3 dots>advanced optimisation).  Merely selecting "don't optimise" for the fitbit app doesn't seem to cover it.  I then "forgot" my charge 2 as a bluetooth connection and re-paired.  I also enabled day sync, always connected and notifications, even though I don't use any.  

Am on oxygen 9.0.6, fitbit app v.2.95.  

Hope this helps - I can't guarantee it'll work any longer than until the next app or oxygen update, but it's better than nothing, especially as my tracker has had limited functionality since the beginning of the year, with no assistance from fitbit themselves.  

[Cyclofe]

This might help as the problem is not solved, search on Google "fitbit en upto android download 1905109"

[Shosh]

Wish someone would find a similar fix for the xiaomi  mi9. I do have a work iPhone so could move my Fitbit app there... But would mean migrating mfp too honestly i don't like using the iPhone, I much prefer my android but this syncing issue is killing me. It's making the Fitbit almost useless.