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! 

[ZINZIN]

I don't believe that. I only have 4 bluetooth items to synch
Fitbit
Car
Ear phone
Frontier S3
The only thing that is continually on bluetooth is my watch. However, it
charges at night in a different level in my house.

[Zeldaw]

I'm only paired to two devices, my phone and a speaker. The speaker is rarely on - used twice in the last year and this caused no problems. The problem started as soon as I upgraded to Android 9.
I have found that leaving my phone on constant sync seems to allow syncing to occur (I've probably jinxed it now). However the notifications element still does not work.



Sent from my Samsung Galaxy smartphone.

[ScottKilbo]

I have two devices paired to my phone as well - a Fitbit One and my Ionic.  Two points I'd like to make:

1. My Ionic worked perfectly (well, mostly) up until the day that my phone decided to update itself to Android P.
2. It is ridiculous that how a device works is partly based on having other devices paired. I mean it's a phone.  There's a lot that you can pair to it and you should be able to pair whatever device you want.  It severely limits the ability to use the phone.  I'm surprised more people don't bring this up as a fatal flaw in your product.

Every morning I get up and I have to restart bluetooth to get my watch to sync.  It will sync for a while, and then it stops.

[BenInTx]

I have a new Versa that will not sync. Not on my desktop, laptop, or Pixel XL! No matter how many times I pair, unpair, enable Bluetooth or disable Bluetooth, reinstall the app, etc.!! This is the singularly most useless device I have ever gotten from Fitbit, and I've owned several. It will sync up randomly only, but you can't make it sync! I got this to replace my Blaze. I walk to improve my weight and blood pressure, yet it's done nothing but ramp up my blood pressure!! Calling Fitbit for N RMA, as I am fed up!! Don't buy this!!

[spatula]

Return it for a refund before your 45-day window is up.  It's never going to sync correctly.

[ScottKilbo]

---

@spatula wrote:

Return it for a refund before your 45-day window is up.  It's never going to sync correctly.

---

I agree completely.  As a long time Fitbit user/sufferer, I can say with absolute certainty that you are making a mistake if you keep it.  It will never work right and on the off chance that they do manage to get it working, they'll eventually screw it up again.  Save yourself the trouble and time and find something more reliable.

[spatula]

FWIW, the May Android security update is out today, and the Pixel update includes a quarterly Android OS update.  Still installing mine, and in any case it may be a few days before it is possible to tell whether sync is any better after the update (in my case it works for hours or days first before going back to "Bluetooth Issues").

If in fact problems were caused by https://issuetracker.google.com/issues/123997469, which was marked "fixed" on March 7, it's plausible that this is the first quarterly OS update (the last one was in February) that could potentially include that fix.

[ScottKilbo]

---

@spatula wrote:

FWIW, the May Android security update is out today, and the Pixel update includes a quarterly Android OS update.  Still installing mine, and in any case it may be a few days before it is possible to tell whether sync is any better after the update (in my case it works for hours or days first before going back to "Bluetooth Issues").

---

I'm envious of you PIxel owners.  It'll likely be six months or more before my Note 8 sees this update, if it ever does.

[spatula]

---

@ScottKilbo wrote:

---

I'm envious of you PIxel owners.  It'll likely be six months or more before my Note 8 sees this update, if it ever does.

---

It's one of the major reasons why I chose the Pixel.  I hate waiting around 6 months for security and other OS updates.  Another reason was that I hate unwanted carrier and manufacturer bloatware that I can't remove.

[MattJ71]

My wife installed the May update for her Google Pixel 3XL today.  The sync problem still exists.  It has gotten to the point that her Fitbit Versa is useless.  It doesn't sync or tell the correct time, so it's not even functioning as a watch anymore.

My Fitbit Ionic on my BlackBerry KEY 2 running Android 8.1 works flawlessly.  There is something in Android 9 and/or the Fitbit app that is causing this problem.  Fitbit needs to fix this ASAP as the problem will only get worse as more and more devices are updated to Android 9.

This makes me hesitate to update my KEY2 to Android 9 when it is released (coming months).  Doing so will give me a nice new OS but probably render my Ionic useless as a tracker and watch.

[ZINZIN]

DO NOT UPDATE!

Fitbit is ignoring this issue. They say they are"working on it" but this
has been a known issue since August. I have emailed, called, sent
messages on FB and the standard response "we are aware of the problem".
I have even asked for a direct contact person, and their reply - crickets!
I even asked if they are going to offer a refund, again, nothing.

[LanuzaFitbit]

Hello everyone.

Thanks for all of your feedback on the situation and all of the details that you have shared.

Please know that we are aware of the situation and we will be sharing details with everyone as soon as there are any news to share. 

Thanks for your patience and understanding.

[spatula]

---

@LanuzaFitbit wrote:

Please know that we are aware of the situation and we will be sharing details with everyone as soon as there are any news to share. 

It's extremely difficult to believe that in NINE MONTHS there have never been any details to share.

[BenInTx]

So, we continue with nothing done after all these months. You need some new programmers. Some of the time I can force a sync by rebooting the Versa and attempting to sync while it is coming up. If I were to make a guess, I suspect there is an issue with the interrupt handling. Either the Versa isn't sending the correct input, waiting for the interrupt, processing the interrupt correctly, not processing the response, etc. The fact that it will randomly sync tells me your problem is programmer skill. When I added by Versa, it confirmed the communication by giving me the four digit code, which I entered, and then it told me it couldn't connect to the Versa that IT JUST SENT THE CODE TO!!! Seriously, get some good programmers!

[BenInTx]

So, we continue with nothing done after all these months. You need some new programmers. Some of the time I can force a sync by rebooting the Versa and attempting to sync while it is coming up. If I were to make a guess, I suspect there is an issue with the interrupt handling. Either the Versa isn't sending the correct input, waiting for the interrupt, processing the interrupt correctly, not processing, etc. The fact that it will randomly sync tells me your problem is programmer skill. When I added by Versa, it confirmed the communication by giving me the four digit code, which I entered, and then it told me it couldn't connect to the Versa that IT JUST SENT THE CODE TO!!! Seriously, get some good programmers!

[reggert]

Same issue as everyone else regarding syncing. Also have to take out battery for it to work. Crazy!

[varun_kumar]

This issue cost me my Versa. How can you guys let the app go out without the fix?
My versa got stuck on `Unlock with your phone` error. I tried to connect it to phone so I can unlock it but my phone wasn't recognising at all so I thought reconnect might help. I removed the versa from my account in order to reconnect just to realise that Versa is completely bricked now. Instead of displaying the pin, which is required to successfully connect your versa to your phone, it shows `Unlock with your phone` error. I tried performing hard factory reset using 3 buttons combination but seems like even that's not working anymore. I am following the instruction step by step but all I am seeing is black screen.

I would say just hide the app from Play Store for Android9.0 so other people don't end up bricking their devices.

[punk4funk]

Same issue with my fitbit zip & sony xperia xz1 compact.

When phone was upgraded to 9.0.

Syncing stopped.

Sync works the 1st sync attempt after a zip reboot via removal of battery.

Been living w/ this for many months.

Will be switching to different brand if not fixed soon.

[ZINZIN]

Are you going to ask for a refund? I mean, at this point I have a
pedometer that has no memory after midnight.

[punk4funk]

I won't be asking for a refund.

I've had my zip forever and up until now have been very happy with it.

It's just not worth the trouble now.