help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Charge 2 no longer syncing with samsung A30

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎07-05-2019 09:18

‎07-05-2019 09:18

Last week I got a new phone a Samsung A30. I successfully installed the Fitbit app. All was working fine, syncing etc with my Charge 2 until this week. I no longer can sync my phone with my device since 4 days ago after it was working well even syncing workouts. Nor does the phone even find the device any more. Any suggestions?

Best Answer
0 Votes
2 REPLIES 2

‎07-05-2019 19:32

‎07-05-2019 19:32

Unfortunately this seems to be a very common occurrence and nothing seems to be working. I have been only able to force a sync twice in almost 2 weeks. I saw a post yesterday that said Fitbit will be rolling out fixes gradually over the next two weeks. I stopped using my Charge 3 because it couldn't even keep the right time. 

Best Answer

‎07-06-2019 07:26

In response to Maryejj

‎07-06-2019 07:26

Yup! It's a known issue that has been ongoing for quite some time. I've been having it as well. They keep saying they're working on it but 2 updates have been released and it hasn't been fixed yet.

Best Answer
0 Votes