Adding distance (km) does not allow decimals

[skallinen]

When adding distance while adding activity manually the decimal (dot) gets parsed out so that 3.75 km becomes 375 km. Input does not accept the comma. On Google pixel 4 using/trying Finnish, Swedish and English keyboards.

[RicardoFitbit]

Hi @skallinen, welcome to the Community Forums! Sorry for the delay in responding.

Thanks for bringing this to our attention and for the details that were shared in your post. To better assist you with this, can you please let me know if this occurs with a specific language or with all of them? When was the first time you experienced this and how many times since then? In the meantime I receive your answers, please try the following steps:

1. Force quit the Fitbit app.
2. Uninstall the app from your mobile device.
3. Make sure that the Android version is up to date.
4. Reboot your mobile device.
5. Reinstall the Fitbit app.
6. Login using your account credentials.

Keep me posted.

[Chywan]

Hi it affects both my Charge 2noting decimal figures and 4 .

It is not possible to insert distance in decimal figures.

This has been going on for years already 😑

and nobody except you seems to mention it. So annoying.

The thing is that the distance measured by the device is capable though of generating AND noting decimal figures in the distance field.

How can that it doesn't work manually?!

Strange at least, I use a Xiaomi Mi 9 with Android version 9

[Chywan]

It stilll isn't looked after by the engineers, though in my opiniion the problem resides in the distance unit you use.

If you use miles the field accepts decimal figures. Not so when using km (kilometers).
Even so the comma still isn't accepted when using miles.
So the km is still treated as an orphan, not taken seriously, even though it is the unit accepted by IUPAC

TWO things have to be considered WHEN USING KM:

1. accept the COMMA as the decimal point and

2. accept decimal figures in the KM UNIT