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: 

After last update my Charge 2 stops syncing with my phone

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

‎10-06-2019 10:26

‎10-06-2019 10:26

I dont have count on how many times i have had to reinstall my Charge 2 because the app cant find it. Never had Any trouble with this until the New dashbord and firmware in the watch was updated... 

Best Answer
0 Votes
1 REPLY 1

‎10-07-2019 05:50

‎10-07-2019 05:50

There seems to be a raft of problems arising from either the firmware update, the Android app update, and/or Android 10.

 

I have a Charge 2 syncing against a Pixel 3 running Android 10 (there's a whole thread on the Pixel). I am acquainted with the "looking for device" message on sync, although mine usually gets found.

 

Issues I experience include no text message notifications (common issue) and mine can lose time - like 2 minutes in 12 hours - if I don't open the app and force a sync.

 

I have not seen any responses from Fitbit that makes me think they understand the issues, much less have a clue on fixing. 

 

Personally, I think there is a bug in the new app working with Android 10, but that's a guess. 

 

Good luck!

Best Answer
0 Votes