01-05-2018 11:37
01-05-2018 11:37
I am not certain if my problem is caused by the same issue as in other posts I have read. I am using an Android phone. I have tried all the fixes that have been suggested. I thought some screen shots would describe the problem better than I could in words. This is frustrating.
Answered! Go to the Best Answer.
01-30-2018 10:03
01-30-2018 10:03
Hi there @ridgerunner51, thank you for providing me more details about the issue you are experiencing. My apologies since I haven't post any update recently. So I'm wondering how it goes, is the issue still persisting?
I'm asking this since there is a new version of the Fitbit app: Android app version 2.65.1 is now available - 1/25. Make sure you have this new version installed on your phone.
To see what version of the Fitbit app is installed on your device:
If the Fitbit app keep showing the same behavior, please try to reset your phone in the following way:
Log out from your Fitbit app and go to your phone settings. Access to the App manager option and look for the Fitbit app in your downloaded apps list. Once you are there, clear the app cache and data and proceed to "Force Stop" the app. Finish the workaround by restarting your phone. When your phone has initialized, go back to your app and try again.
See you later if you have more questions.
"Great things are done by a series of small things brought together.” What's Cooking?
01-08-2018 04:29 - edited 01-08-2018 04:32
01-08-2018 04:29 - edited 01-08-2018 04:32
Hi there @ridgerunner51, good to see you are visiting the Fitbit Community! Thank you for sharing your screenshots, however I'm still wondering what exactly is the issue you are experiencing? I would like to know more details of your concern?
Note that the "Time Asleep Goal" and the "Target Sleep Schedule" are independent, so if you change your target time, make sure it matches the sleep goal you have configured.
Nonetheless this is just basic information, so I would like you to let me know what is the behavior of the app and the relation of the screenshot? Also if is possible let me know which post have you seen that shows the same behavior? Whit this I can give you a better response to find a solution.
I'll be looking forward to your reply. see you soon!
"Great things are done by a series of small things brought together.” What's Cooking?
01-08-2018 05:53
01-08-2018 05:53
My target bedtime is 11:00 pm and my target wake up time is 8:00 am. Two screen shots show that. The "Target Sleep Schedule" shows bed time 4:00 am and wake up time 1:00 pm, which is totally wrong. It would take some time to go back and find the similar posts, but if you still need that I can look for them.
Thanks
01-10-2018 08:11 - edited 01-10-2018 08:13
01-10-2018 08:11 - edited 01-10-2018 08:13
Here is a link to a thread with sleep problems. Not exactly the same problem as mine, but I thought they might be related.
01-30-2018 10:03
01-30-2018 10:03
Hi there @ridgerunner51, thank you for providing me more details about the issue you are experiencing. My apologies since I haven't post any update recently. So I'm wondering how it goes, is the issue still persisting?
I'm asking this since there is a new version of the Fitbit app: Android app version 2.65.1 is now available - 1/25. Make sure you have this new version installed on your phone.
To see what version of the Fitbit app is installed on your device:
If the Fitbit app keep showing the same behavior, please try to reset your phone in the following way:
Log out from your Fitbit app and go to your phone settings. Access to the App manager option and look for the Fitbit app in your downloaded apps list. Once you are there, clear the app cache and data and proceed to "Force Stop" the app. Finish the workaround by restarting your phone. When your phone has initialized, go back to your app and try again.
See you later if you have more questions.
"Great things are done by a series of small things brought together.” What's Cooking?
01-30-2018 12:39
01-30-2018 12:39
Thank you RobertoFitbit. I had the new app version. I followed the instructions at the end of your post and the problem is fixed!