Android 9.0 (Pie) not able to sync

[AlessFitbit]

Fitbit Update: 3/6/19

Hello everyone! 

We have some updated troubleshooting suggestions we'd like for all of you on Android Pie (9.0) to try. 

First, turn off Background Restrictions/Limitations: Phone settings > Apps & Notifications > Fitbit app > Background restrictions or Background limits.

Then, disable battery limitations:

1. Go to Settings > Apps > Fitbit app > Advanced > Battery > Battery optimization
2. Change view to All apps
3. Search for Fitbit app
4. Choose Not optimized

Please give the steps above a try to improve syncing with your Fitbit device and Android 9.0 OS. We're still researching and testing out long-term solutions to this ongoing syncing issue. We thank you for all your patience while we continue to work on this effort.

---

Fitbit Update: 2/14/19

Hi everyone!

Thanks for all your reports and patience with these Android 9.0 syncing difficulties. We’re aware of this ongoing issue and have been working to identify a resolution as quickly as possible. 

We're sorry for any trouble. We appreciate your patience and look forward to getting you back on track as soon as possible. 

I'll let you know if I receive any additional information on this matter. 

---

Fitbit Update: 10/3/18 

Hey Everyone!

Our team is still working on implementing a longterm fix for syncing with Android devices on Pie (9.0). 

For the background syncing issue, I have posted an update in the other floated thread which you can find here. 

We released Fitbit for Android version 2.80 today which contains improvements for that syncing issue. 

I'll make sure to keep you all updated with more information, as soon as I have it available. We're still working on this and I really appreciate everyone's patience. 

---

Fitbit Update: 9/26/18

Hey everyone! 

Thanks so much for your patience and cooperation. We are aware of the issue and working with Google on a solution.

I will continue to provide updates here, so keep an eye on this thread. 

---

Fitbit Update: 9/10/18 

Hi, everybody! 

Thanks for your patience while our team continues to work on improving syncing for those on Android Pie (9.0). They are actively working on this and for the time being, I recommend you keep the Fitbit app updated on the latest version for best syncing results. Right now that is version 2.78, so if you're not on this version please update! Also, another troubleshoot we recommend is performing a restart on your phone. 

When there are more improvements made in the future I'll announce them here. Stay tuned and subscribed to this thread. 

---

Fitbit Update: 8/19/18

We have escalated these syncing issues for those who are now using Android Pie (9.0) to our team for investigation. There aren't any updates at the moment, but rest assured we will keep you informed in this thread when more information is available.

Thanks for your patience! 

---

Fitbit Update: 8/11/18 

Hi, everyone! Thanks for stopping by the Community Forums. 

Seems like many of you who updated to Android Pie (9.0) are now having trouble syncing your Fitbit trackers. I'm going to escalate this to our team so they can look into it.

In the meantime, please update the Fitbit app to version 2.76.1 if you haven't yet. Let me know if that changes the syncing behavior. Please follow this thread for updates. I'll keep you all posted here! 

[DeppJones]

Hello everyone. Greetings from germany. I'm new to the community. Got my charge 3 two weeks ago. I'm using a Nokia 7 plus. Everything worked fine with Oreo 8.1. Three days ago got updated to Pie 9.0 and right away no more syncing. After several disappointing attempts I successfully tried the workaround suggested by @fluo75 and  @TimSimsalabim:

Step 1 uninstall the app

Step 2 remove the charge 3 from the list of devices in the BT settings

Step 3 re-install the app without opening it

Step 4 search for nearby devices in the BT settings and couple with the (hopefully found) charge 3. You may need to restart your charge 3 to switch on BT and make the device visible for your phone.

Step 5 open the app, login - done

Step 2 seems to be the crucial step, as apparently there the information is stored that causes the syncing to fail. I'm not sure about the validity of Step 3, but that's how it worked for me. At least, that's how I recall the steps done. I fiddled around for quite a while.

But please be aware that this is merely a partial workaround. Syncing works for steps, floors climbed, and sleep tracking. No live HR measurement, though. That used to work with Oreo 8.1. So, it is stll unsatisfactory.

I still don't understand, why it seems to be impossible to get a fully functioning system from the developers. I'm working in the health sector. If I'd do my my job like they do their's I'd get either fired right away or sued by some furious patients.

[jolly_old_elf]

I managed to do about the same thing as @DeppJones and have my Charge 2 syncing with my N7 Plus on 9.0.  As he indicates, it's not complete.  Mine appears to be syncing the same bits.  No heart rate tracking and no active minutes tracking.  Fwiw, I turned the phone off and set up sync with the Windows 10 native app on my Surface Book and syncing began immediately BUT...same is true, no heart rate or active minutes data is synchronizing through that connection either.

[Praxticus]

Works on Nokia 7 plus.... heart rate and active minutes syncing too. Takes
a few minutes to start...

[DeppJones]

I can confirm that. But only now. I managed the workaround on my Nokia 7 plus 10 hours ago. One or two hours ago it still did not track HR. Now it does. Life tracking. That's quite a long time. What happened in between? Someone from the moderator team please comment.

---

@Praxticus wrote:
Works on Nokia 7 plus.... heart rate and active minutes syncing too. Takes
a few minutes to start...

---

[Waydrunk]

When you add the charge 2 or 3 back as a BT device, does a code show up on your Fitbit that needs to be entered on your phone? My charge 2 display stopped working a few months ago and I'm worried some info will be displayed that I need. Thanks 

[DeppJones]

---

@Waydrunk wrote:

When you add the charge 2 or 3 back as a BT device, does a code show up on your Fitbit that needs to be entered on your phone? My charge 2 display stopped working a few months ago and I'm worried some info will be displayed that I need. Thanks 

---

No, it doesn't. At least, not on the charge 3. But in your case I would suggest that you restart your charge 2 prior to searching for it again on your phone (after deleting it first)..

[GJO323]

I'm not even sure how people are are doing the workaround method when I've never been able to manually pair my Versa through the Bluetooth menu. 

[Gusthy]

No, it is not the point. 

All the sentences beginming with "Bluetooth is intended to be .." are problematc. It is very hard to determime  what BT is intended to  be.

BT is an old and ugly protocol which is "intended to" replace the RS232 serial port in a wireelss way, and nothing more. Later it has been patched by different features, but it is nothing more  really  

[Gusthy]

Why do you say there is no support? Your fitbit is working now. It didn't fix itself without support. 

[DeppJones]

---

@Gusthy wrote:

Why do you say there is no support? Your fitbit is working now. It didn't fix itself without support. 

Support from the community - yes. Support from the FitBit team - not really very much. Rather disappointing perspective for the future. 

[Gusthy]

I guess it wasn't the community who fixed the app on your phone..  

[DeppJones]

Did I say that? If yes, where and when?

---

@Gusthy wrote:

I guess it wasn't the community who fixed the app on your phone..  

---

[SunsetRunner]

So my watch isn't syncing on my OnePlus 6 for four weeks now, and now I get an email to buy the Charge 3? Is this serious? Won't buy anything again at this point.

[Gusthy]

Sure, I mixed up the comments here  that wasn't you, sorry. 

[mr-Navarath]

Since Android is typically slow to be adopted by the phone makers - unfortunately there's only a small minority of us using Android Pie. For the record, I have an Essential PH-1 with Android Pie's latest update, and I use bluetooth regulary with 5-6 devices. The fitbit flex is the only one that can't handle it and won't work.

[jwildstr]

@Gusthy  I'm not sure what your background is; given what you're saying, I'm guessing it's computer engineering in some form. That being said, Bluetooth IS a standard, put out by the Bluetooth SIG. There are core standards to follow, shown at https://www.bluetooth.com/specifications/bluetooth-core-specification. If Android decides to violate these specifications, that's a bug in Android. If FitBit doesn't comply, that's on them. Given that this seems to have only affected FitBit in this way (I know there were some various Bluetooth car units that didn't work, and Android fixed that issue over a month ago), I'm leaning toward FitBit violating the standard. I looked through the reported issues on Google's issue tracker, and they all dealt with headphones or cars, and those were fixed in the September security update. Clearly, this is a different issue.

[tracymckibben]

This is 100% on Fitbit. Bluetooth sync to my car still works, Bluetooth sync to my laptop still works, Bluetooth sync to my headphones still works - only my Fitbit(s) are broken. Android 9.0 was available for developers to work with in March of 2018, over 6 months ago. This sync issue was reported to Fitbit in August of 2018, over 2 months ago.

Fitbit failed to test their app with Android 9.0.

Fitbit has failed to communicate on the status of the issue, acknowledgement of the issue, or a timeline for a fix.

Why isn't there a notification being displayed in the Android app alerting users of the problem?

Oh, and thank you for your patience, no updates are available at this time.

[Gusthy]

The fact that your car, your whatever works doesn't mean that everybody else's stuff also works. Tha fact is that some of the BT devices don't work properly with Pie. You are lucky with your other BT devices.

One of my friend has a tronsmart BT loudspeaker that has problems. Also a guy known by me has problems with his Renault car BT. 

[Gusthy]

Those were fixed partially. 

[jwildstr]

yes, and from that thread:

"They have a fix.  Not released yet.  https://issuetracker.google.com/issues/112272747"

That was on AUGUST 13. The acknowledged issue with Bluetooth you keep trying to pin on Google was fixed 2 months ago and released one.

I'm not entirely sure why you insist on blaming Google here. I'm thrilled for you that YOUR device works. Mine hasn't for 2 months, and FitBit has told us nothing. If they said they were in contact with Google, I'd be willing to trust that information. But they haven't said even that.