09-30-2022
06:22
- last edited on
10-14-2022
10:03
by
LizzyFitbit
09-30-2022
06:22
- last edited on
10-14-2022
10:03
by
LizzyFitbit
Calories bar graph on clock screen not updating correctly. This is on 3rd party clocks and Fitbit clocks. At 900 of 3000 calories, I would expect 1/3 of a bar or so. I have almost nothing. And yesterday when I checked at 2700/3000, I had not much more.
Moderator Edit: Clarified subject
Answered! Go to the Best Answer.
10-11-2022
11:52
- last edited on
07-25-2023
03:54
by
MarreFitbit
10-11-2022
11:52
- last edited on
07-25-2023
03:54
by
MarreFitbit
Hi everyone!
Thanks for bringing this to our attention, and for the steps tried on your own. Please note the Forums are designed to provide a place for our members to seek and receive help from other Community members. Nevertheless, your feedback is truly appreciated and it'll help us to keep improving.
Regarding the Sense 2, because this is affecting the clock faces, I went ahead and escalated this to our team so they can investigate what may be occurring. I'll update this thread once I receive more information from them.
09-30-2022 07:40
09-30-2022 07:40
The Fitbit clock screen is "Pleat", the third party one is one of the stats ones developed by Jason Olsen.
09-30-2022 08:36
09-30-2022 08:36
Yes, I am seeing the same thing. Only the graph bar on the clock face is wrong; swiping over to the "Today's Activity Screen" (where it shows as a round graph) the graph there is correct. Seems an easy to fix bug as the steps graph on the clock face works fine. But definitely a bug.
09-30-2022 09:09
09-30-2022 09:09
Jason Olsen's clock uses a round graph. It's just as wrong. I don't think bar or circle makes a difference. It's almost like the max of the graph is 10x what you set. So instead of 0-3000, the graph is displaying 0-30000. Probably a programmer divided by 1000 instead of 100. But it's not the clock, but somewhere in the OS to generate the percentage that the clock grabs and displays.
10-03-2022 12:52
10-03-2022 12:52
The complete lack of any "official" response from anyone remotely "official" is rather telling. Clearly, we (as a community) are on our own.
This sense 2 is absolutely a downgrade from a Sense or Versa 3.
-zero support. Not even acknowledging clear bugs, lack of advertised features, no time table for when they might deliver on these promises, etc.
-zero third party apps
-next to no third party clocks
- poor and restrictive implementations of the features they did deliver on.
cEDA is not worth the BS this company is putting us through. I am about 2 days from boxing this **ahem** up and shipping it back to them. If it comes to that, I will never again purchase a Fitbit or even consider a Pixel watch. I am even to the point of reconsidering buying that new Pixel phone. I realize I am a single customer and Google has thousands of even millions, so I doubt they will notice. Eventually if enough of us do this they might even get the message, but I doubt it. They are getting as bad as a fruit company.
10-09-2022 14:57
10-09-2022 14:57
The bar that shows your daily progress to reaching your calorie goal on my watch never fills. I burned over 3000 calories today and my goal is set at 2500 but it still only shows approx. 10% filled. My step and floor goals do fill properly. Is there some update necesarry or something I can do? I have already tried changing watchface but still get the same problem.
10-11-2022 01:08
10-11-2022 01:08
Does anyone know of a way to report bugs directly to Fitbit? As long as things keep getting ignored, they will never be fixed. However at this rate, I doubt they will get fixed anyway.
10-11-2022
11:52
- last edited on
07-25-2023
03:54
by
MarreFitbit
10-11-2022
11:52
- last edited on
07-25-2023
03:54
by
MarreFitbit
Hi everyone!
Thanks for bringing this to our attention, and for the steps tried on your own. Please note the Forums are designed to provide a place for our members to seek and receive help from other Community members. Nevertheless, your feedback is truly appreciated and it'll help us to keep improving.
Regarding the Sense 2, because this is affecting the clock faces, I went ahead and escalated this to our team so they can investigate what may be occurring. I'll update this thread once I receive more information from them.