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.
01-12-2019 19:48
01-13-2019 00:00
01-13-2019 00:00
@wjbot download the nRF Connect App from Playstore and follow the steps of (Pair-Connect-bond). I have also explained in the post the steps in detail. It'll work.
I have One Plus 6.
01-13-2019 01:57
01-13-2019 01:57
Hi,
Nokia 8 Sirocco, Pie and Charge 2 are working together, but I must
- remove the tracker in the Fitbit app
- remove the tracker from the Bluetooth devices in Android
- add the tracker in the Fitbit app...
01-13-2019 03:00 - edited 01-13-2019 03:03
01-13-2019 03:00 - edited 01-13-2019 03:03
Yes, @SunsetRunner, I got a new update - phone message popped up saying system update available. One of the updates was "Improved Bluetooth stability for better connectivity". After the update I went into the Fitbit app and when I selected to connect a previously paired device it worked - my steps etc updated. I can only assume it was this OnePlus system update that worked for me.
01-13-2019 06:32 - edited 01-13-2019 07:02
01-13-2019 06:32 - edited 01-13-2019 07:02
Agreed. They should have perfected the syncing process by now, but they have not.
01-13-2019 07:20
01-13-2019 07:20
I'm so happy for you.. after I saw your post I went to my android play store and there was the update for my Samsung Galaxy Note 8's fit bit update.. So I did it and nothings changed. Actually it got worse. Now I'm not receiving any notifications to the watch. So now I have to cut the bluetooth on and off ever several hours just to receive notifications to my watch. We should not have to force these actions, once we connect out watches to our phone that should be it.
01-13-2019 08:50
01-13-2019 12:19
01-13-2019 12:19
I'm with you Anita. Continues to be frustrating. I have even tried to buy a dongle online but there is a glitch there where country defaults to Australia and will not allow me to change (I live in New Zealand).
My wife bought a cheap version on one of the Chinese shopping sites and it works and syncs beautifully EVERY time for less than 10% of what Fitbit charge
01-14-2019 07:43 - edited 01-14-2019 09:54
01-14-2019 07:43 - edited 01-14-2019 09:54
Hello @SunsetRunner, @AGallo, @JulioD, @salonee, @Tanutamun. @SunsetRunner and @tessierp. Welcome to the Forums @SleepyCat and @Micksta.
@AGallo, @salonee and @JulioD, Thanks for sharing those steps and being around to help.
@SleepyCat Glad to read that it now seems to be working for you. Thanks for taking the time to let us know.
@SunsetRunner, In the case of the notifications, let's try following the steps listed in this help article. They should help the notifications to start working correctly once again.
@Tanutamun, Thanks for listing those steps. How often are you having to go through those steps?
@SunsetRunner and @Micksta, Have you tried all of the steps that have been suggested in the thread? Particularly what was suggested in this post and this post. The steps seems to have worked for some other users.
Feel free to reach out with any further questions.
01-14-2019 07:53
01-14-2019 07:53
What worked for me is that I deleted the tracker from the paired devices and when I added it again it started to sync.
After the system update it was completely dead by the way on the OnePlus 5t.
01-14-2019 10:15 - edited 01-14-2019 10:22
01-14-2019 10:15 - edited 01-14-2019 10:22
Ummmmm NO! I'm not following anything else. I have spoken to fitbit support so much they know my name. You have to understand we pay top dollar for these devices that do work properly. ( ionic Adidas edition $346 at that time I punched it)I should not have to turn on this, turn off that, resync this and resync that and bluetooth this device everyday while my APPLE friends laugh at me.......... I ordered a different device... Now what I might do is stick with fitbit cause it's all I know. I don't like learning a new device and fitbit is all I know. When the update get fixed and the bugs are out, I'll be back..
This community is funny, I cant let go!!!
01-14-2019 14:30 - edited 01-14-2019 14:30
01-14-2019 14:30 - edited 01-14-2019 14:30
Just noticed, my phone has just got an update to the Fitbit app v 2.85?
Mentions bug fixes, wonder if it's related?
01-14-2019 14:38
01-14-2019 14:38
After getting my new Pixel 3 phone and setting up the Fitbit app again, things actually worked as expected for almost a week. A couple days ago the battery ran out in my Ionic, and after charging it, today it's back to "Bluetooth Issues" and "Tracker not found" as usual. Cycling airplane mode still fixes it, whereas turning Bluetooth off and on never has.
I'm on the January 5 update of Pie.
Fitbit doesn't fix their bugs.
01-14-2019 16:25
01-14-2019 16:25
Version 2.85 did nothing for my situation (FitBit Zip on Pixel XL 2, Android 9, January Patch).
I've tried all the work around alternatives from prior posts and still nothing.
I think we're all dreaming to expect a fix at this point. They don't even list the Pixel XL 2 on the supported list. They simply don't appear to have an interest in supporting Android.
01-14-2019 16:28 - edited 01-14-2019 16:29
01-14-2019 16:28 - edited 01-14-2019 16:29
I updated the fitbit app today and went through the steps described here:
https://community.fitbit.com/t5/Android-App/Android-9-0-Pie-not-able-to-sync/m-p/3192019#M95200
The device was found but would not sync after several attempts. I closed the nRF App so it wasn't running in the background, opens fitbit app again and the sync was successful.
OnePlus 5T
01-14-2019 19:20
01-14-2019 19:20
Just updated the Android app. Said "bug fixes and performance improvements." When the app opened it immediately synced with my fitbit and the heartbeat appeared. Don't know if this will continue or just random. It was syncing on most days but would often say cannot find tracker or the heartbeat would not show. Using a Charge 2 HR with a Nokia 6.1 running Android Pie (9).
01-14-2019 19:28
01-14-2019 19:28
I got the update, and sadly, I immediately got "tracker not found" out of it. Cycling airplane mode got it to sync, but I shouldn't have to cycle airplane mode every time I want my smart watch to sync with my phone.
01-14-2019 20:48
01-14-2019 20:48
That's exactly what I said. Paid toooo much for this tracker to be reset and re-sync every 1..... not gonna do it!!!
01-15-2019 06:33
01-15-2019 06:33
After the update to 2.85, sync failed again. The main problem seems to be that the Versa isn't visible via Bluetooth LE. I was able to see the Versa again after I disabled Bluetooth on my PC, just as if the Versa could only be seen/used after it is unable to connect to a previously known Bluetooth device.
Maybe this problem is two-fold. One part of the problem is in the device (e.g. Versa) and the other part might be the way Android N detects available Bluetooth LE devices.
01-15-2019 07:58
01-15-2019 07:58
Updated my phone Xiaomi Mi A1 to Android Pie and lost the ability to sync my charge 2. I hope this gets fixed, I am very disappointed with Fitbit.