Android Oreo GPS Issue

[jdvp]

On Android Oreo, 8.0.0, I have an issue using GPS tracking for walks and runs with my Charge 2. Syncing seems to work and I can see the connection icon on my fitbit when I start the app. However, when I lock the device, the charge shows the phone not available icon and only recconnects to GPS when I unlock and open the app

[fadhly]

Open fitbit app -> sync with charge 2 -> activate "run" mode on charge 2->after a few hundred meters the charge 2 no longer connected to phone..

I've read in forums that this is caused by Android 8.0 "Background Execution Limits", the only way forward is Fitbit needs to update their app to adhere to Google's new 'rules'.

[SunsetRunner]

Yes, I do understand the issue as far as syncing the two during the run. But my question was, what if you don't set the tracker itself to track it, but the app on the phone?

So what if you set the app itself to track your run on the phone and do the run. If you do that (as a temporary workaround), will it accurately track your run? Then when you get back it should sync with the Fitbit regarding steps, heart rate etc. That's how I use it at the moment. But I'm on Nougat still.

[JasonAnder]

I went for a bike ride this morning, and my Fitbit only recorded the first .08 miles. I've tried all the workarounds in this thread (changing notification settings and battery optimization settings) but they all don't work - or work temporarily for a ride or two and then break soon afterwards.

@AlessFitbit this has been broken for months now, when can we get a fix?

[SunsetRunner]

Does it track if you just use the app on the phone?

[timvdalen]

I just went for a walk and kept the app open and constantly saving at some times.

After I got back and looked at the activity, I had GPS logs for the times I had the app open and I didn't have GPS logs for the times the app was closed/my phone was locked.

This, again, seems to suggest that the Fitbit app just hasn't been updated for Android 8.0.

[SunsetRunner]

I can just set the app to follow me and shut the phone (it is set not to lock when on my body) - I can use other apps as well - and I never look at the Fitbit app until I get home, don't know how you would 'save'. On Nougat it tracks till I get home and hit pause then stop.

[Asphodel]

---

@SunsetRunner wrote:

I can just set the app to follow me and shut the phone (it is set not to lock when on my body) - I can use other apps as well - and I never look at the Fitbit app until I get home, don't know how you would 'save'. On Nougat it tracks till I get home and hit pause then stop.

---

I didn't have any issues with Nougat either. All of my issues (and, as far as I know, all of the issues in this thread) are with respect to Oreo. Android changed something in the way it handles running apps, probably for "battery" reasons, and the Fitbit app does not seem to work with that system.

[SunsetRunner]

Thanks for confirming that the app itself doesn't work with tracking. I wanted to make sure that it didn't work either way, so that if I am offered an update to Oreo I will have to decide what to do.

I have had to use the phone to track for ages since connecting the Fitbit to the app failed me too many times to bother with it. If it worked like that with Oreo I could handle it. 

What is up with Fitbit not fixing the app to deal with this issue when it's been ongoing for some time?? Maybe they are trying and just can't fix it. Surely otherwise it would be a priority. I wouldn't recommend a Fitbit now, at least until they get this fixed.

[Asphodel]

---

@SunsetRunner wrote:

What is up with Fitbit not fixing the app to deal with this issue when it's been ongoing for some time?? Maybe they are trying and just can't fix it. Surely otherwise it would be a priority. I wouldn't recommend a Fitbit now, at least until they get this fixed.

---

Same boat. Poor timing on Fitbit's part too, since a number of family and friends have asked me for recommendations as the holiday season approaches. It seems that this is the year of wearable fitness trackers for my family, and they're all going with other brands instead based on my recent experiences with Fitbit.

[JasonAnder]

Agreed - I'm definitely not recommending Fitbit to friends and family as long as this is broken, and no one is getting one for Christmas. I'm wondering if we can return them for being defective? On my bike ride tonight, it only logged the first .44 miles. I feel like since it's been a few months, we've been patient enough to get a fix.

[JasonAnder]

There's no option to track bike rides on the phone - only run, walk or hike, so that workaround won't help.

[SunsetRunner]

Track using Strava, it's your only option at this point.

Unless you can return it.

[SunsetRunner]

@AlessFitbit

People are beginning to be very unhappy. Can the team not fix this? 

Fitbit are losing sales at a critical time because bad news (and personal recommendations not to buy) travels fast.

[GST49]

I appreciate the frustration, as I was there for many weeks with my Blaze
when my Google Pixel XL was upgraded to Android 8.0. I believed at that
time and sort of still do, that the Fitbit App team failed to get on the
Android 8.0 changes needed when Android announced those to all those
running apps on the Android platform. However, I have had no GPS problems
for several weeks now, and hope that continues. I realize there can be many
nuances based on different devices, firmware and software versions, but
that is what testing is for. So, shame on the Fitbit App team if they
failed to cover all the bases. Anyway, since I have had some success here
is my configuration and my routine when I start my bike ride in the event
some others may have success.

Fitbit Blase firmware version 17.8.402.1
The physical Fitbit device settings are:
1. I have notifications turned on,
2. I have not paired the Bluetooth Classic since it is for controlling
music, and I do not need or use this function.
3. Since I use the GPS tracking when I ride my bike, (approx 4 - 5 times a
weeks for 12 - 15 miles each time), I have set the bicycle setting to Use
Phone GPS to On, and Secondary Stat is Distance.

Fitbit App, version 2.62.1, setting are:
1. Always Connected is On
2. Notifications - I use Text Messages and Calendar Events, and Enable
Notification Widget is turned On.

Pixel phones were/are notorious for bluetooth trouble, so I always turn off
bluetooth then turn it back on until I see all the paired devices
connected. Then I go to the Fitbit App and wait until the app syncs with my
Blaze (steps match). Then I select the Exercise option, then Bike, and wait
for the message "Lets Go". If I get a "Couldn't connect to phone" response,
I go through the process again. This has worked with accurate GPS tracking
for many weeks, I think back to Fitbit App version 2.59. While the extra
steps should not be needed, and maybe with this latest version of the
Fitbit App I might not need to go through some of the routine, things are
working for me.

[AlessFitbit]

Hey, everyone! Thanks for sharing your recent experiences with connected GPS while on Android Oreo. I appreciate everyone's patience and would like to reassure you our team has been looking into this on a deeper level. They are working on a fix and I will continue to update this thread when I have more information. Thanks for your cooperation! 

[Asphodel]

Hi @AlessFitbit, thanks for the follow-up. Just to be clear, my patience was exhausted several weeks ago and I have given up relying on my Fitbit. I am now actively researching a replacement from another manufacturer.

I don't mean to be rude, I just think it is important that Fitbit understand what this issue has cost them.

[CKTHONG]

I walk funny.

[fitz1j]

2018.... problem is still on going.

[SunsetRunner]

I decommissioned my Fitbit last week and bought a Garmin FR235. Works perfect.

[fitz1j]

Yeah, I just sent an email to Fitbit requesting a refund. It's unfortunate.