Dates are wrong in Norwegian clock faces

[Chris8519]

The dates i wrong in multipliced Watch faces in Norwegian how to fix?

Moderator edit: subject updated for clarity

[jfe]

The "Slashed" clock face, my initial choice, has Mon, JAN 01 showing up in the app picture on top of the display. In my Norwegian language set up Charge 5 it reads Tirsdag, Sep 2. Problem is that there is not enough space on display so the actual day date can't be viewed. This seems to be the case for other clock faces as well with the same top-line look ("Retro", "Energy", "Target", "Ripple", and "Progressive".

Have high hopes that this issue can be fixed relatively easy 🙂

[jfe]

[DavideFitbit]

Hi, thank you for sharing this information about your Charge 5, @Chris8519. 

Could you please provide a few extra details about this problem?

If possible, please share some screenshots showing the problem with the dates as well so this can be reviewed with more detail. 

I'll be around.  

[Chris8519]

 

The number shold be 20 all Watch faces is like this. Is it posible to change it to Englich

[Chris8519]

 

[Wibby]

It is possible to change to English, but then everything will be in English, not just the watch face.  

On your phone, click your profile.  Scroll down to App Settings, click. Select location.  Then scroll down to an English speaking country of your choice and click it. A green arrow should show up.  Then you will have to update your Charge 5 again to change to the new language.

It's annoying we don't have the option to have 2 languages and switch between the two...

I hope that helps.

[Knuty]

@DavideFitbit it seems like the day is spelled out in it's full name in Norwegian. For example Wednesday is shown as "Onsdag" which is correct but according to the example screenshots for the watchfaces they only show "wed" , the first 3 letters when it is in English. So it should be "Ons" in Norwegian. Having the full name seems to push the date out of the picture. Would be nice to have this bug fixed, makes date unusable

[DavideFitbit]

Hi, thank you for taking the time to share all this information and screenshots, @Chris8519 @Knuty!  

I've shared this information with the team, and this will be of great help to improve the way that the date is shown with the the clock faces in Norwegian. Thank you again for sharing all these details.

In the meantime, please let me know if you continue to have the same problem after completing the latest firmware update for Charge 5 and try to complete a restart as well. This has been useful for other users experiencing problems with the display.  

Have a great day. 

[Bjørnar]

6 months later and with latest firmware installed and the Charge 5 restarted - the problem lingers on.  Ought to be a rather easy solution to the problem, since it's a matter of wrongful data collection.
The location array "Mon, tue, wed, thu, fri, sat, sun" has a Norwegian equivalent "Man, tir, ons, tor, fre, lør, søn", but instead of fetching the abbreviated location array, the clock faces fetches the full location array "Mandag, tirsdag, onsdag, torsdag, fredag, lørdag, søndag".

I presume all fitbit Charge 5 owners in Norway (and presumebly elsewhere as well) would appreciate your programmers effort in a one line of code change to refer to the abbreviated location array.  Because being able to display the correct date is a rather essential thing for a gadget telling time 🙂

[runemart]

The last digit of the date is clipped. 

Date is in reality written as "07", but only the first digit is visible. In other watch faces i can see a small slice of the last digit.

Screenshots from watch face section in app shows that day names are shortened, but on my Charge 5 it is displayed in full. Guessing that is related to this issue somehow.

(Phone, Galaxy S22 Ultra, is set to Norwegian locale).

Other watch faces with the same problem:

https://photos.app.goo.gl/uQK6p1XAitEo1D2d9

[Sollid]

Just got my Fitbit Charge 5, but many of the watch offers won’t show the date. Like for example today June 08 it just shows June 0. It’s like the screen is too small for the last digit to show. I have tested out a few of the watch options and most several have the same issue. Anyone else that has experienced this?

Moderator edit: format

[Rich_Laue]

Which face. It also may have to do with the choice of language. 

[DavideFitbit]

Hi, welcome to the Fitbit Community forums, @Sollid. 

Thank you for sharing this information about the problem you mentioned with the Charge 5. 

Before considering other options, could you please share a picture showing the issue you described? In addition, let me know if this is happening if you select a specific language or if it's happening when you have your device in English. In the meantime, please try the following troubleshooting steps that have been helpful for other users with similar problems: 

1. Restart your device using the charging cable following these steps. 
2. Set up your Charge 5 as a new device in your account. 

Hope this helps, I'll be around. 

[Sollid]

I am using Norwegian on the watch. It seems to have gotten better, now it’s “just” cutting the edges on the day and date. On Wednesday the day showed fully, but the date just said Jun 0. I have done the troubleshooting you suggested, but does not seem to change anything. 

[Rufous44]

Regardless the watchface and the language Charge 5 is fully coded by Fitbit that has to be therefore take responsibility for the bugs.

Fitbit really lacks a proper beta testing procedure and a bug tracking and resolution system.

[runemart]

Same problem on my Charge 5, also Norwegian user: 

https://community.fitbit.com/t5/Charge-5/Date-in-watchface-is-too-long-to-display-correctly/td-p/516...

Problem occurs on all watch faces that display day name. 

[Sollid]

That’s exactly how my Fitbit charge 5 displayed the date Wednesday June 05.  

[DavideFitbit]

Hi everyone, I appreciate all the feedback that you've provided about this so far and for the screenshots showing the problem with the dates in Norwegian. 

This information has been reported to the team so they can look into it but we haven't received other updates for the moment. Any other information about this will be shared in this thread as soon as it's available.

Thanks again for all your patience and for sharing your feedback with us.