Syncing Issues on Android 3.37

[KateFitbit]

Update 2/1/2021: This issue was resolved with the release of android app version 3.37.1. We appreciate your reports and patience as we worked on a resolution.

---

Update 1/29/2021: We've released Android app version 3.37.1 to address syncing issues. Please update your device if you are experiencing issues syncing. Thanks again for your patience as we worked to resolve this issue. 

---

Update 1/28/2021: We are still working on this issue and hope to have a fix real soon. We will update this thread as soon as we have more information. Thanks again for your reports and patience. 

---

Our team is aware of a syncing issue on Andriod 3.37 and is currently working on a fix. Thank you very much for your reports and patience. Please stay tuned to this thread for updates. 

[Jmce203]

I tried all these things, and it still won't connect. It says it found the device and is connecting, but then goes to a screen that says it didn't work. Dozens of us are having problems since the last Android app update. Hopefully the developers are working on a fix and we'll get a new update ASAP.

[Dynamitedon]

Most of us have Android phones, so that is not an answer. Been wearing the
Charge 4 since it first came out and it has not had this problem.

The last FITBIT update needs to be removed back to the previous version.

Since Google owns FITBIT now maybe they want us to buy Google phones.

[mclopez]

I've had the Charge 4 for a few months and never had any issues with syncing until yesterday night, at 2:10am. I've followed absolutely all the troubleshooting steps, except removing the device from my account, because I don't want to loose unsynced data, and nothing worked. It definitely sounds like there is an issue with the latest app update.

[BernadetteS]

you're a superstar, thank you Tammy 😊 

[muddyfoot]

There are several posts that mention phone incompatibility....for refrence to those having this problem, this is what fitbit says about phone incompatibility.

https://www.fitbit.com/global/us/technology/compatible-devices

My phone  Galexy A10e is updated to version 10 android should be compatible, has been since I got my Charge4 until the last updste broke bluetooth connection 

[TammyKinPA]

You're welcome!  😁

[SamRules]

I definitely do not recommend removing it from your phone; I did that and reset the data on the tracker as a last-ditch attempt to fix the sync problem and the tracker is stuck in the setup stage so I can't even use it as a watch or alarm clock. Can't get it to work at all on my Android phone anymore.

Interestingly, I tried to set it up on my laptop (Windows 10) using the Windows Fitbit app and got much closer; it will pair and give the 4-digit code to complete the setup, but when I put in the code to the computer, the tracker displays an "x" with a circle around it and goes back to the factory setup screen. The Fitbit app, however, thinks it succeeded but when it gets to the "which wrist do you use it on" it gives an error about this feature not being available or something. I can then sync the Charge 4 in the app and it registers as successfully synced, but the tracker still remains in the setup screen. Bafflingly, the time is now corrected when it was not before the failed setup. So there is some sort of partial sync happening here but not enough to get the tracker off the setup screen. Maybe my problem is different from others', but the timeline is similar (mine stopped syncing over the weekend after working fine previously).

[SunsetRunner]

Mines stopped about the same time, nothing wrong with my bluetooth everything else is working fine, tried everything they suggest but nothing works, not even 5 days old

[horse]

Tried removing and now it will not pair with my phone.

[horse]

I do not see the instructions mentioned in your post.

[IowaGuy23]

Tried this and no help. Rebooted the charge 4, restarted my phone multiple times and no help. The update seemed to kill communication.

[Rich_Laue]

Yes removing the tracker from the phones Bluetooth is one of about 10 steps to try. 

However once removed, the user will not be able to pair through the phones Bluetooth, the tracker should be expected to reject every attempt. 

When the Fitbit app is opened, and the tracker syncs, the Fitbit app will request permission to pair the tracker. 

[Pcre]

Same issues with samsung phone and tried all suggestions.

Work around was added app to ipad and it connected and updated on ipad.

Ipad was next to phone and pushed ipad info to phone. Phone still wont pair but can see more current info.

During this process watch reset calorie data and went down about 1,000 calories for today. Other watch data seemed ok.

Also phone will partially update calories within few of watch.

[AJMack]

Affecting me too. I have spent 2 hours trying to get my Samsung phone to pair my charge 4. This has all started after the update earlier today.

[SunsetRunner]

I had this issue when I first got a fitbit hr and had to reset the fitbit back to factory settings so I will probably try it but will lose today's tracking.

[D.D]

I have the same issues as you have....exactly what you had done, i have done likewise. I just finished chatting with a customer rep and she told me to follow all the steps that you mentioned ...and nothing. I am pretty much annoyed and wonder if this is because they did something with an update? I have to take a breather from all of this and cool down...what a waste of time...anyone have an ideas as i am at a loss. Also, i dont have steps or stairs showing on my phone....on the watch, yes...but NOT on the phone. I did Edit and it doesnt even show there...!

[SuzHolly]

Mine is exactly the same ! Nothing since Friday morning ive followed all the same "fixes" as you ....nothing ! 

[MGMaryann]

Had it 10 months so I know what to do. Restarted phone 3 times. Nothing!  Battery charged. HELP!

[muddyfoot]

Dont factory reset....it will lock you out with an endless cycle of not
being able to connect with bluetooth

[Doomlux]

My app started working again yesterday. At first my Fitbit and the app still wouldn't pair, but today that worked, too!

Edit: Spoke too soon. We're back to nothing working. It was a nice day and a half lol.