08-11-2018 14:07 - edited 09-12-2019 10:48
08-11-2018 14:07 - edited 09-12-2019 10:48
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:
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!
Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.
Answered! Go to the Best Answer.
11-08-2018 12:21
11-08-2018 12:21
11-08-2018 12:25
11-08-2018 12:25
Can you at least take the time to summarize all of the 1000 workarounds in this mega thread into a comprehensible article, not the the generic help article that you linked that's not adapted for such a fiasco.
11-08-2018 15:50
11-08-2018 15:50
11-08-2018 22:44
11-08-2018 22:44
@Schuss send it to me please as I don't have any problem at all. I'll pay the shipping cost.
11-09-2018 06:42
11-09-2018 06:42
Does Fitbit sync on pie yet?
11-09-2018 06:52
11-09-2018 06:52
It depends on your phone model and which Fitbit device you are using. Some work and some do not.
11-09-2018 07:04
11-09-2018 07:04
I have the OG pixel.
11-09-2018 07:11
11-09-2018 07:11
@Slyd If I was in your place, I won't buy any Fitbit product until I hear the issue is resolved and sync is stable. Fitbit is not able to resolve the issue in three months. Nobody knows what happens to the devices when next version of Android comes in picture. We will have a 50-60 page thread again with the title, "Android 10.0 not able to sync". Decision is yours.
11-09-2018 11:38
11-09-2018 11:38
I already have a very old One. I rolled back to the 2.75 version of the app . I can sync on that version in a round about way ... Try to sync, then pair, then sync again... It's awkward but it works. And I won't update the app. What in the world is taking Fitbit so long to fix this???
11-09-2018 13:07
11-09-2018 13:07
I can't believe that my Charge 2 is once again not syncing with my Pixel 2. What the hell? Enough already FitBit. I am not pleased. What a waste of money and time. Give us our money back. Ugh... Such a waste!! GOOGLE PLEASE MAKE A WATCH/FITNESS TRACKER!
11-09-2018 14:24 - edited 11-10-2018 08:05
11-09-2018 14:24 - edited 11-10-2018 08:05
Upgraded my Nokia 6.1 to Android 9 yesterday (11/8/18). Still unable to sync my Fitbit Charge HR.
Edit 11/10/18: reset my charge (connected it to charger and held button for 10 sec), force stopped the app and then opened it, and the sync took place on the first go. I'll post another update in a few days indicating whether the fix persists.
11-09-2018 23:01
11-09-2018 23:01
11-10-2018 03:06
11-10-2018 03:06
I can only speak for NOKIA 6.1, but maybe other phone owners problems could be solved with this. after the Android update to 9.0 Pie, and the restart of the phone , the Fitbit charge 2 app was opened and bluetooth connection was not possible anymore, so no sync.
Tried several times to restart, and dis- and re-connect the bluetooth, but it did not work anymore.
Mailed Nokia support, and after a 15 min got an answer.
I switched bluetooth to forget Fitbit charger 2.
Go to settings, App & notifications, All apps, Options 3 dots in right upper corner, Show system, Bluetooth, Storage, Clear cache & Clear data.
Go to settings & notifications, All apps, Options 3 dots in right upper corner, Show system, Bluetooth MIDI, Services, Storage, Clear cache & Clear data, after this perform a soft reset, press Power & volume button simultaneously for 10 sec, when phone vibrates release, you see Android start up, it takes a while; Make shure the phone is not on a charger; Reinstalled the Fitbit charger 2 with the Fitbit app.
Everything works as before now.
11-10-2018 04:06 - edited 11-10-2018 04:09
11-10-2018 04:06 - edited 11-10-2018 04:09
I attempted these steps on the Pixel 2 with Fitbit Flex and still no luck. Thanks though.
11-10-2018 04:29
11-10-2018 04:29
11-10-2018 19:38
11-10-2018 19:38
My Fitbit has not synced for 11 day. Before that it would only sync on Thursday.. Please help. Would like to track my progress and enter challenges.
11-10-2018
19:41
- last edited on
11-11-2018
10:07
by
FerdinandFitbit
11-10-2018
19:41
- last edited on
11-11-2018
10:07
by
FerdinandFitbit
Got my refund today - can buy in the future if they ever fix the problem -
Horrendous customer service
--
Ed Meehan
Moderator edit: Removed personal information
11-10-2018 20:31
11-10-2018 20:31
In Bluetooth settings I removed the device by selecting Forget and synced again. This time it synced.
11-11-2018 04:08
11-11-2018 04:08
I have Android 7.1 I have not had a software update on my phone in 6 months at least. the new Fitbit software update has prevented me from being able to add my new charge 3 to my account. I have followed all steps that are recommended to make it link, nothing worked, I even uninstalled my other devices, reinstalled the app and now I can't get any of my devices to link to my account.. I have been patient it has been 3 days already and I still cannot link, it's not tracking my sleep or any of the other things I needed to track. Any update on what is going on please.
11-11-2018 06:50
11-11-2018 06:50
@Lorac280 I'd suggest you post your issue in a new thread. This thread deals with Android 9, and some issues that were related that cropped up in 8. 7.1.1 is really old, so your issue is almost certainly different than the one being discussed here.