07-11-2019 10:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-11-2019 10:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I'm used to the Charge 3 sometimes failing to get the correct sleep onset and wakup times. But until today, I've never seen it mangle it after I've edited it! Clipping 4+ hours off the start of a sleep period the next time the app is started after editing is a serious bug.

07-14-2019 17:39
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



07-14-2019 17:39
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hello @Conser666 it's nice to see you again participating here in the Community Forums, let me give you a hand with your sleep data concern. My apologies for the delay in responding your post.
Seems odd that you're experiencing such situation after the Fitbit app update, thanks for your patience with this. To better assist you, can you please let me know when was the first time you experienced this situation and how many times after editing your sleep information? Also, which Android mobile device you're currently using? In the meantime I receive your answers, can you please try the following:
- Force quit the Fitbit app
- Uninstall the app
- Reboot mobile device
- Make sure that your Android OS version is up to date
- Reinstall the Fitbit app
If possible, please provide me a screenshot of this situation for a better understanding of it.
Looking forward to your reply. Let me know if you have any additional questions.

07-15-2019 19:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-15-2019 19:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
If you look at the bug I am describing, there is nothing to take a screenshot of. It is a problem on the Charge 3, not on the phone.
I'm not going to do the uninstall/reboot/reinstall because that doesn't actually fix the problem, it masks it. I already have a workaround, which is to simply turn off notifications. When there is some evidence that the software has been fixed (whether on the Charge 3 or on the phone), it will be worth trying notifications again. I am reporting this bug so that, hopefully, someone who understands the product is reading this and will investigate.

