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! 

[Sylvie60524]

Please be more clear: update of what, Android 9.0, windows,Ios or Fibit apps.

[THX11384EB]

This thread is specifically about Pie. No other desserts

[Kyral]

I know this hasn't helped a few others, but the google April security update seems to have fixed things for me. Pixel 3 with inspire HR. Before the update, I'd have to completely unpair the fitbit and redo setup within the app. Since the update, I've had no issues with sync, at all. Knock on wood...

[SunsetRunner]

Thanks and glad all is well with your Inspire HR - but the April Google
update didn't fix my Pixel Zip sync issue.

[Kyral]

Sorry about your Pixel and Zip. I know you mentioned trying everything in this thread, but out of curiosity, have you tried changing your Bluetooth AVRCP version? Not sure it's been mentioned in this thread. But it seems to be a fix for people in other threads. I'm running v1.6, which is not default, so perhaps that's making a difference. If it doesn't work, sorry, but maybe worth a shot if you haven't tried it yet.

See the solution here for instructions: https://community.fitbit.com/t5/Ionic/Ionic-won-t-sync-to-Google-Pixel-2-XL/m-p/2681101#M51502

[spatula]

I haven't seen changing the AVRCP version elsewhere in this thread yet, but I'd be somewhat surprised if it made any difference.  I'll try it out just the same... it's easy enough to try, and easy to go back if something else breaks.

[daitcs55]

I have tried resetting the AVRCP to no avail.  Your mileage may vary.  Bit concerned that it might mess up the other 2 Bluetooth devices I regularly connect to so went back to the default.  Zip  S9 9.0.

[mattdm]

Yeah, no good here either.

Also, I feel sadly obligated to repeat the refrain: if it were this easy, surely Fitbit could have done this very basic testing themselves and provided it as an actual solution.

[Kyral]

Never meant to imply it was that easy. I'm just a user simply trying to
help by giving new information from my setup that is now working post April
security update. I thought it may have been possible that changing the
AVRCP version in conjunction with the April update for Pixels was doing
something (specifically because this update has improvements to bluetooth
and was rumored to potentially fix sync issues - see a few pages back).
Furthermore, since AVRCP version has certainly been a solution for some
people in the past (on fitbit forums and elsewhere for both Pie and Oreo)
and was not mentioned in this thread, I thought it was worth noting since
it's easy to try.

Even if it doesn't solve your or a particular users case, it may help
someone (it's working for me at the very least!), and I'd imagine more info
can only help both us and Fitbit. I'd rather have positive, constructive
discussion rather than assume small "easy" fixes are futile under the
premise that Fitbit 'should' have already done it. When there are so many
permutations of fitbit device/app version/phone/android version/patch, this
is probably not that easy.

Absolutely no offense to fitbit, but I would be surprised if they've done
actual testing on an approximately 1 week old update available to a subset
of phones.

[SunsetRunner]

Thank you for offering to help, but unfortunately this proposed method
wasted more of my time. My Fitbit Zip will not sync with my Pixel 1 at
either the AVRCP Bluetooth setting of 1.6 or the default setting of 1.4.
I've tried all the suggestions on the forum since August 6, 2018 and NONE
have provided a permanent fix, including a full factory reset of my phone.
Fitbit and Google need to fix this issue ASAP. Eight (8) months have
passed and I'm still waiting. And you know what I would like to say to
Fitbit and Google about that!

[SunsetRunner]

I am right there with you. I have tried everything over the last 8 months to fix my Pixel 1 and Zip. Nothing works for more than one sync.

[Paulzip]

I also have a Pixel 1 with ZIP and I have to take the battery out of my ZIP
each evening for a few minutes of syncing before it stops working again.

Don't you think that Fitbit are just going to turn around at some point and
say the Pixel isn't supported any more?

Paul

[Shultgren]

I do the exact same thing and I'm on Samsung S9+. Pop the battery out of my zip for 30 seconds to a minute and then it will sync once. Then I do it all over again a couple days later to not lose my data. It's the only workaround I've gotten to work. I'm not confident that there is ever going to be a solution. I have yet to find a better smart pedometer on the market, but the day I do is the day I leave my Fitbit behind. I will never buy another Fitbit product after this debacle. I understand bugs happen, but considering Android is a massive marketplace you'd think they wouldn't conveniently "forget" about us and not push this along with Google. 

[Sylvie60524]

For myself I sync with Ipad until fitbit update their software.

But it’s a shame Fitbit didn’t find a apps solution since 8 months.

[Sylvie60524]

Think if your pixel 1 is running Android Pie 9.0 the problem is fitbit software.

[Sylvie60524]

The problem is the Fitbit software, not the phone.

[SunsetRunner]

Pop out battery from Zip every time you sync? You have too much time on
your hands.

[SunsetRunner]

Causes extra wear on the Zip battery cover and not the way the Zip was
designed. Also a waste of time.

[LM3K]

Although this is NOT a solution per say, if you happen to have another phone or tablet that is not running android Pie, your Fitbit should still be able to sync with it if you have the app installed.  I have an extra phone at home that syncs to my Zip. This then updates the information on my main phone (galaxy 8).

[THX11384EB]

You could also do this with a PC.

BUT to me, it's not about STEPS!

It IS about NOTIFICATIONS.