07-26-2019
05:37
- last edited on
09-08-2020
14:11
by
MatthewFitbit
07-26-2019
05:37
- last edited on
09-08-2020
14:11
by
MatthewFitbit
I have been unable to syc my charge 2 now since the 24th July 2020. I have tried all the trouble shooting and I have tried to chat with fitbit. Their answer was my phone is not compact able with fitbit. I have had my phone for 2 years now and never had a problem until Wednesday. Before i could explain this on chat i was disconnected. I now have a watch that will not connect with my phone. My blue tooth will not find my watch. As i was told to disconnect it.
Any one have any ideals to help please
07-26-2019 05:59
07-26-2019 05:59
Unfortunately, @JulieB2019 , it sounds like an update on your phone may have pushed the incompatibility to a critical point. Or perhaps they made a change to their bluetooth. I’m sorry this did not work out for you.
07-26-2019 06:14
07-26-2019 06:14
Thanks.
I thought it was my phone but i have just tried it at work with two more newer phones than mine and there blue tooth cant find my watch
07-26-2019 06:29
07-26-2019 06:29
Were those two phones on the list of compatible devices?
07-26-2019 06:42
07-26-2019 06:42
Yes they are both on there,
Huawei P20 Pro and Samsung Galaxy S9+
07-26-2019 07:24
07-26-2019 07:24
I'm sorry JulieB2019. I'm not replying to your message (just can't seem to write a message of my own) However, you have just written the exact problem as I have with my Charge 2. I haven't been able to sync for over a week now and I also have tried all the suggestions. Were you able to get your Fitbit to sync?
07-26-2019 07:45
07-26-2019 07:45
No still not sync. I can not find now on any blue tooth devices.
07-26-2019 08:07
07-26-2019 08:07
This is my third (and last) Fitbit. I have had a problem with all of them. This one I have now, had to have the band replaced (kept falling off...a common problem I'm told). I find this all very time consuming. A friend suggested I should try the Garmin when buying a new tracker. Very frustrating.
07-26-2019 08:19
07-26-2019 08:19
I'm having the same problem except mine started on Tuesday 24th July. My Charge 2 will not sync with my Samsung J3 (2013) or with my Windows 10 desktop. Is just not visible in Bluetooth.
07-26-2019 08:22
07-26-2019 08:22
Phone the helpdesk and follow through to the end of all the checks they will want you to do. If your Charge2 is with in warranty they will offer you a free replacement or 50% off a new one. Try an Iconic for £133.00
07-26-2019 08:29
07-26-2019 08:29
I have had mine 2 years and i have had to change the strap a few times. But thought it was just me been heavy handed. My hubby son and his partner all have blaze and never had a problem with the strap all the watch. I went for a run on Wednesday and wanted to check my map time etc and had and still have nothing. I have tried fitbit chat - but they are no use. Fed up now. I don;t know if it is my watch or phone. Fitbit are blaming my phone, however two phones that are on their list can not find my watch via blue tooth
07-26-2019 09:07
07-26-2019 09:07
I'm discouraged also. I have done all the checks. My Samsung phone is on the list, etc, etc. I guess I just won't worry about syncing. My real goal is just getting my steps in each day. When this Charge 2 no longer works I will be buying from a new company. All of you with the same problem, please let me know if you get yours working.
07-26-2019 12:17
07-26-2019 12:17
My Charge 2 quit syncing on Tuesday, July 23, 2019. I am a senior citizen and not very tech savvy, but I am fearless when I'm trying to figure out why something no longer works. I read the troubleshooting suggestions and could not sync. I did notice when I went into Settings, that there was another device that I did not recognize ( can't remember what it was called) linked to Fitbit so, I deleted it. I'm happy to say I am now synched.
07-26-2019 12:24
07-26-2019 12:24
I have just spent 90 mins on the phone to fitbit to be told it is my watch and it was out of warranty on the 23rd July and it would not syc on the 24th
if it wasn't for bad look i would have no luck at all
07-26-2019 12:25
07-26-2019 12:25
Good job troubleshooting, @JulieB2019 ! Thanks for letting us know.