03-06-2022 06:16
03-06-2022 06:16
Apologies if this is already posted somewhere
I've encountered this bug probably 6 times now, where after I wake up I go to use the stopwatch, only to find that swiping to that app page jumps ahead to looking at a timer. Usually you could swipe to the page, tap "timer" or scroll a little and tap "stopwatch". When the fitbit is in this state, I also am unable to swipe from the clock face to look at any settings.
I haven't tested if I can still start a workout or not, but I do think it continues to track biometrics successfully.
The fix I've found is to just hard restart it by pressing the power cable button 3 times but it's really annoying that it happens and it means I always have to bring the charger with me in case it happens.
Has anyone else encountered this issue?
03-09-2022 05:55
03-09-2022 05:55
Hi, welcome to the Fitbit Community forums, @Agnarr.
I appreciate all the information that you've shared about this inconvenience with your Charge 5 and the troubleshooting steps that you already tried.
I've seen that some users have experienced something similar with the timer function. If you haven't done so already, please try setting up your Charge 5 as a new device in your account. In addition, please try completing a three pulse restart again:
If you're still having this problem, try changing to a different clock face.
I'll be around.
06-20-2022 21:34
06-20-2022 21:34
After restarting my device from the settings menu I could again access stopwatch and timer, as well as scroll through. I noticed that my stopwatch had counted to approximately ~65535. My guess is that at some point I forgot to stop a stopwatch and it counted high enough to hit a 16-bit unsigned integer wraparound that caused a crash in the stopwatch and that caused unusual behavior that immediately dumped you into timer without the selection screen.
Forgetting to turn off a stopwatch should not cause a software crash at any level, that should be an expected scenario and I'm surprised this passed QA.
06-30-2022 12:09 - edited 06-30-2022 12:09
06-30-2022 12:09 - edited 06-30-2022 12:09
@Zabo It's good to know that your device started working again.
Thank you for taking the time to share your feedback and comments. The team continues to work to improve the Fitbit experience and your feedback is a big part of that process. Let me know if you experience any similar problems again.
See you around.