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! 

[SunsetRunner]

As of last week, my fit bit ionic does NOT recieve notifications from my phone at all.  The new update has changed how I feel about fit bit completely.  It saddens me I paid so much for this Adidas ionic and it no longer gets ANY notifications from my Samsung Galaxy Note 8 AT ALL.  I've tried everything and spoke to technical experts TUESDAY and still nothing. I give up. 😞

[kurtisblaze]

I think it's the app for fit bit. Since I've done this reset I haven't
experienced a problem yet. Fingers crossed.

[SunsetRunner]

Good for you. I'm so in love with my watch and when it does not act properly I get all hurt about it. I have to pair it with my phone all day for it to receive notifications.  I refuse to get rid of it, I just want it to work... these last two updates hurt my soul though.  Keep your fingers crossed for me too. 

[Henk_B]

I want to update on this issue, because since yesterday morning everything works smoothly again on my oneplus 5 and fitbit charge2. 
What I did was, like many of us: read the posts, pick logical solutions, try almost everything, and start thinking to say goodbye to fitbit. 

But I also mentioned this problem in the Oneplus forums, the bughunter team came with a tip to remove the fitbit app(s), remove the pairing in bluetooth, and reinstall. 
I had to repeat this process twice, with a (not sure if needed) phone reboot before the reinstall of the app, but after setting everything up again, I have no issues at all so far after more than 24 hours.
Maybe this could help somebody else too.

[SunsetRunner]

Since the new update, I've had to restart my bluetooth 5 times a day just to receive notifications on my ionic.  EVERYDAY? 5 TIMES A DAY?  I know it just a bug, but 5 times a day.. it's like it falls off and I have to put it back on.. 😞

[mahava]

---

@tessierp wrote:

Turning Adaptive Battery off, then rebooting the phone and my watch and pairing the watch with the phone through the application worked for me.. I enabled Adaptive Battery after and all works. There are obvious issues now.. Is it Android, OnePlus or Fitbit? Part of a new bug with Android 9.0

---

Great, thanks for sharing. This solution worked for me on my OnePlus 5T updated to 9.0

[tombadog]

Unfortunately this didn't work for me, Mr Puma. I've got a Oneplus 5T on Pie stable with a fitbit charge 2. I like many people here unpaired my fitbit. I, however have not problems with the fitbit being discovered by the app. I get to the paring stage where I put the number in and then it just says connecting but nothing happens! Infuriating! 

[IanD2]

Hi there, I have the same phone and Fitbit as you. Can you please clarify what you did with the Fitbit? Did you restart it at all?

Reinstalling the app and removing the Bluetooth pairing made no difference to me but am not sure I've done it correctly!

Thanks

Ian

[mahava]

---

@IanD2 wrote:

Hi there, I have the same phone and Fitbit as you. Can you please clarify what you did with the Fitbit? Did you restart it at all?

Reinstalling the app and removing the Bluetooth pairing made no difference to me but am not sure I've done it correctly!

Thanks

Ian

---

This is what i did exactly: removed the tracker from app, restarted the tracker and made a few attempts to connect, then rebooted phone, tried again, not working,  started googling, first I found that one should go into the bt settings and pair while app is trying to pair but that did not work,  then i  found this thread and applied tessierp  s solution but did not connect tracker yet, i rebooted once more (just to be sure setting applied) and then i paired, got code , paired and it still syncs now after after few hours, , 

My tracker is the Blaze but one should think the same solution / workaround would work 

[tombadog]

I've just fixed my above issue. Turns out it was because of another wifi connectivity bug in pie. Used VPN and works but am still facing some syncing issues. Restarting bluetooth seem to help

[mhall1957]

My last sync date was 12/24/2018 (Firmware Version 32.32.10.15). Today I see an option to "Update Tracker Software" on my Android OnePlus 5 phone, which was just recently updated to Pie 9.0. The Fitbit Firmware will not sync or update. Is there a solution available?

[tessierp]

Hi,

I restarted both the watch and phone after disabling Adaptive Battery mode in the phone's settings just to be clear of any bluetooth issues / glitches. After both the watch and phone are restarted, I proceeded to pair the watch with the phone using the fitbit application and it worked for me where it wasn't working with adaptive battery. After the pairing was done, I enabled Adaptive Battery again and all was fine.

[tessierp]

Hopefully that works for you too. It is kind of a shame that Fitbit didn't do more tests with Android 9.0 and testing various situations like people getting an android update from 8.0 to 9.0.. The problem could be with Fitbit just like it could be because of something new in Android or even something OnePlus did which introduces a glitch. All that to say, I was not looking forward to changing my watch for something else.  I'm glad I found a way. Hope it works for you too.

[mhall1957]

Thanks! I was able to get the two synced but the new firmware update will not install.

Fitbit has a lot of opportunities.

[mhall1957]

Thanks! I was able to get the two synced but the new firmware update will not install. 

Fitbit has a lot of opportunities. Grr!

[fred67]

Has anyone downloaded the new firmware?  I downloaded the firmware and Android app, removed my Versa from my device list, then did a new set up device, and was worked great ever since.  No syncing errors what so ever, everything seems to work great. Using a P20 Pro with EMUI 9 (Android 9)

Hope this helps

[Birgit1964]

Hi,  it is now 12-30-2018 and there is still no fix in place.  Please advise ho much longer this may take.  Thank you

[Birgit1964]

Yes I am replying to myself.  LOL   After approx. 3 weeks of the phone not syncing.  I finally contacted Fitbit support.  with Marc's help we not only cleared all data from the Fitbit app on my phone but also on the Charge HR 3.  I was advised to swipe left, go to settings, find about, and clear all data.  my fitbit now syncs with the phone.  yes my data was lost but I can still get some of it back from my running app Mapmyrun.  Have a Safe and wonderful New Years everyone.  Please remember, if you had to much to drink, please call SOMEONE, ANYONE, to get you back home.  Your children and or pets will not understand why you didn't come home.

[lodette]

You are a lifesaver. I have a oneplus 5 and a charge 2, and your suggestions did the trick. I'd been futzing with this for about 4 hours now.

[lodette]

You are a lifesaver. I have a Oneplus 5 and a Charge 2, and your suggestions did the trick. I'd been futzing with this for about 4 hours now.