10-02-2016 16:41
10-02-2016 16:41
I'm attempting to get my Charge to pair with a Galaxy S3 and it just isn't finding it or seeing it. I've restarted the Charge, I've made sure the phone isn't in power saving mode, is visible, etc. and it will not recognize the device. I just had this Charge paired to my Core Prime Android without issue.
Any suggestions?
Best Answer10-03-2016 06:32
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
10-03-2016 06:32
It's great to see you around @RegionalGirl. Thanks for troubleshooting this inconvenience by yourself. Since the tracker is already paired, you don't need to set it up again. You just need to download the Fitbit app, have the bluetooth and internet connection on and it will sync without an inconvenience. But you can try our syncing troubleshoot from the device that is not syncing with your tracker.
Let me know how it goes. ![]()
Best Answer10-03-2016 15:02
10-03-2016 15:02
I have the app downloaded on the phone (A current version of it) and I've turned on Bluetooth in an attempt to do just that. Still not connecting. Doesn't see the device or pair with it. As I said, I had this same device connected to a different phone without issue and the S3 just isn't seeing it.
Best Answer10-05-2016 04:11
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
10-05-2016 04:11
Thanks for the information @RegionalGirl. At this point, since you have tried this troubleshoot, I recommend getting in touch with our support team, I know they will be glad to help you out. For a faster response you can contact them via phone or chat.
Let me know how it goes. ![]()
Best Answer10-05-2016 09:15
10-05-2016 09:15
At this point, we have no idea what the issue could be. Still having the same problem 😞
Best Answer