08-10-2016 04:13
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-10-2016 04:13
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
While I have seen this topic in the recent past (c.April 2016), my Charge HR worked fine with my S7, up until 4 Aug 2016. Having had an online chat with a Fitbit agent, the response was that the Fitbit engineers are working on this compatibility problem, without any guidance as to how long a solution would take and she recommended acquiring a compatible device.
The response from Fitbit help has not been helpful, but I am hoping that by using a community forum any others with similar experiences can join up and we can exert some pressure on Fitbit to rectify this problem.
Answered! Go to the Best Answer.
Accepted Solutions
08-10-2016 09:22
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
08-10-2016 09:22
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Have moved this thread from the Charge HR to the Android App section.
Your post will get more attention here.

08-10-2016 09:22
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
08-10-2016 09:22
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Have moved this thread from the Charge HR to the Android App section.
Your post will get more attention here.

08-10-2016 12:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-10-2016 12:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@jnbridglalsingh wrote:While I have seen this topic in the recent past (c.April 2016), my Charge HR worked fine with my S7, up until 4 Aug 2016. Having had an online chat with a Fitbit agent, the response was that the Fitbit engineers are working on this compatibility problem, without any guidance as to how long a solution would take and she recommended acquiring a compatible device.
The response from Fitbit help has not been helpful, but I am hoping that by using a community forum any others with similar experiences can join up and we can exert some pressure on Fitbit to rectify this problem.
What exactly is the problem? You only stated that worked fine until 8/4...

