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! 

[BenInTx]

Yes, I need to get an RMA number for return. I've only had mine since Saturday and already sick of trying to get it to work reliably. I've removed it from my devices and using my old Blaze until I decide where to go next. Calling the help line was useless, since they only tell you to try the same steps you find online for the issue.

I'm looking at alternatives. The Apple is too expensive and the 18hr battery life is a joke. The problem with Fitbit communication isn't new or unique to this model, so I'm not inclined to go that road again.

[Lynnp1]

So fitbit tell us they're working on a fix and will update when they have something.......well that response just isn't good enough........many people have spent their
hard earned money on an item that you, as a company, marketed and it isn't
fit for purpose you knew of this issue yet continued to sell it without warning android users .......so this response isn't really a response at all. I'd
like to know if I return my Fitbit to you, as it's not fit for purpose,
will I get a refund for it?

[biddu]

Is there any other way out for syncing dear Fitbit community moderators? I want a different answer that does not include the following terms: reset, unpair, force stop, not compatible, reboot, Bluetooth battery settings, patience, working on a fix. 

N.B.: charge 3 is not syncing even with the Fitbit dongle on my MacBook Pro. I am using a Xiaomi Mi 8 phone which is not on the distinguished list of compatible devices, but still, it used to sync when I bought it in October 2018 until last Thursday. Save me from this ignominious abyss of despair and disability, please  

P.S.: to add insult to injury, because of not getting synced or some other reasons, the clock time on my charge 3 is not accurate, it is slower than the actual time! 

[reggert]

While this issue is not the least bit funny, your response sure is!!! IT person by trade, there is NO WAY if they were sincerely interested in fixing this problem this should take months. We can put men on the moon but cannot fix a smart phone to Fitbit sync issue. What a joke.

[daitcs55]

Here is a fun fact.  Exactly one year ago today the first full beta version of Pie was released.  One year that Fitbit could have been checking for issues if they didn't access the developer version that was available earlier. 

[biddu]

I wish I were in the 1970s now. 

[reggert]

Perhaps the fitbit technology behind the scenes is from the 1970s. 

[BenInTx]

70s were great. No PCs. Booted computers with punch cards. 8" floppy was new, stored something like 160k. Worked via dumb terminal, sometimes hardwired and sometimes acoustic couplers (think old movie War Games). Programming was machine and assembly language for some things, FORTRAN for science and COBOL for business. Programming was judged on efficiency. Now we have Windows, which continues to prove Bill Gates never met a processor he couldn't bog down.

Now we have Fitbit that cannot execute simple communication with a Android device, yet it is sold for that purpose... You make sure things work BEFORE you market them.

[reggert]

Remember those days as well. Did fortran, cobol, assenbler. Mainframes were king. Simpler days. Heck i may be retired before fitbit fixes a simple bluetooth sync issue!!!

[ZINZIN]

There is a forum page where people were complaining about the new dashboard. I said something about I wish I could complain about a new dashboard, my fitbit couldn't sync and this is a problem they've known about for 7 months. About 1 day later, I got an email letting me know my post had been removed bc it was on the wrong forum page.

THAT'S some serious customer service right there!

I also contacted fitbit on their facebook page. I got bot after bot response. I stated I just wanted an actual person to deal with. 

[kentpenney]

Another update with additional facts.  For my Moto Z3, I have connected by bluetooth a Whistle 3 for tracking our dog, Monster Earbuds, LG earbuds, and connectivity to our Jeep Renegade.  All were working with Android 8.0 and were working after getting Android 9.0.  The only thing that is not is my Fitbit Zip.  My only fix is to remove the battery each morning so it syncs information from the previous day.

It should be easy for Fitbit to see the magnitude of the problem.  Look at all your users and see how many are no longer syncing.  I would bet the results are astounding and have been getting higher and higher as the months continue from August when this discussion started.

If I were Fitbit, I would completely stop all my staff from doing anything else except trying to solve this problem.  As the Android 9.0 rolls out to different phones the result seems to be the same.  Fitbit not syncing.  2000 plus posts so far should be something that is screaming to Fitbit that this is a big problem.

[Kamleman]

Well, it's been a week or so in Garminstan for me. I needed something which would do notifications and couldn't wait for Fitbit any longer. Which is a bit of a shame. I actually think the Fitbit dashboard and exercise tracking is better. But how long to wait?

My new device paired seamlessly and syncs perfectly to my Android 9 phone. Notifications work. There has been some talk on this forum that the problem is as much a Google issue as a Fitbit one. Why then does my new device work perfectly with pie and my Fitbit does not?

It's squarely a Fitbit problem that they can't be bothered to prioritize a fix for. Clearly a judgement call has been made that they would prefer to lose customers than spend money on fixing the problem. So...I would suggest that further complaining is futile. Either put up with the crap service or walk.

[biddu]

Fitbit is becoming the soul reason for my degrading mental fitness, I might jump from the top of a tall building soon!

[Roy_Bergen]

Please understand that patience is running low. 

[spatula]

FWIW, the May Android update does not fix the issue with sync with the Ionic either.  It was good for about 2.5 days, and this morning I'm right back to "tracker not found."  At least it isn't the stupid "Bluetooth issues" message, but it is still just as useless.

Sync is still broken.

[Paulzip]

Pixel 1 ZIP.
I have been doing the daily ritual of taking the battery out of my ZIP to
reset it so I can sync each evening before I go to bed since August of last
year.

FITBIT are a joke. I wouldn't invest money in this company.
Paul

[spatula]

FWIW, since Google closed the previous bug report as fixed, and getting them to reopen a bug report that hasn't actually been fixed is like pulling teeth, and because the symptoms now are just slightly different, I've opened a new issue:

https://issuetracker.google.com/issues/132312906

If you have an account you're using with the tracker, it wouldn't hurt to go and "star" the issue to draw attention to it.

One thing that's kind of interesting is that last night Beacon Scanner & Huan weren't working while Fitbit was, then this morning Beacon Scanner & Huan were working while Fitbit wasn't.  And then toggling airplane mode got them all working at the same time.

IMO Android's Bluetooth stack is still buggy as hell, and they haven't really shown much interest in fixing it.

[biddu]

So any words of hope? Any magician here?Helloooooo!!

[mattdm]

So, there is some hope: I finally got a support person who offered me an RMA even beyond the 45 day period (because the only reason I held on was because of the "be patient!" messages posted continually here). If you have a Zip you purchased after last August but more than 45 days ago, I suggest you ask for the same.

Is there hope for this device to ever work? I doubt it!

[BenInTx]

My Blaze works, but has taken a beating and goes nuts when wet. Was hoping Versa was the solution, rather than the problem it is.