help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Clock face parts disappeared after running ECG app

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎10-09-2023 08:50

‎10-09-2023 08:50

After running the ECG app this morning, parts of my clock face (Dawes) have disappeared. I tried changed to other clock faces, but they also seem corrupted. The Sense was working fine before I ran the ECG. I suspect I need to factory reset, but this isn't the first time display elements have gotten corrupted (e.g. the Alarm app showed times in black so they weren't readable). I suspect a software issue since the display seems to work fine otherwise.

Has anyone else seen this?

Best Answer
0 Votes
2 REPLIES 2

‎10-09-2023 10:48 - edited ‎10-09-2023 10:51

‎10-09-2023 10:48 - edited ‎10-09-2023 10:51

Never had that happen on my Sense. But I don't use that clock face, did you try a simple remove that clock face, shutdown, power on, install the clock face? If it happens on other apps, could be the flash is failing, might try a factory reset, but not sure if that would fix a failed flash chip. It would reinstall the software OS. Not sure if that helped or not. Could also be other hardware issues, like screen issues. 

Fitbit Ionic 72.1.15 (recalled), Fitbit Sense 128.6.17 and Pixel Watch 2 BP1A.250305.019.W8, March 2025.
Best Answer

‎10-09-2023 12:01

In response to Jdsenter

‎10-09-2023 12:01

It's happening on more than one clock face. I suspect a memory issue with the software that is causing data to become corrupted. One thing I noticed is that the 5-face limit on clocks loaded on the Sense has been relaxed, since I now have more than 5 faces loaded as a result of my testing today.

Best Answer
0 Votes