08-28-2019 12:16
08-28-2019 12:16
Hi. I can't input decimal in distance while adding previous walking distance. I experience this problem on android app. I use fitbit charge 3. If I press comma ( , ) on the keyboard nothing happens in the input field. If I press period ( . ) on the keyboard it appears and I can enter the decimals, but when I save record, the period disappears and the number changes from 2.3 km to 23 km. Both android and Fitbit app are up to date. The only solution I found was to input data on fitbit website.
08-29-2019 17:58
08-29-2019 17:58
Hi @Martula. Welcome on board!
Thanks for bringing this to my attention, as well for making sure to have everything up to date. It sounds strange that it doesn't work on the app, but it seems fine on the on the fitbit.com dashboard. I'd recommend to try the following troubleshooting steps:
If the issue persists please provide me with your phone's model so I can further investigate this situation.
Keep me posted!
11-21-2019 06:36
11-21-2019 06:36
I have the same.
I cannot enter decimals. If I enter 8,5km, it looks like it works but when I press "log it", it saves 85km...
I've tried to change language, keyboard, reset the app, reset cache etc etc.
I have a Samsung S9, with latest Android.
Please help, this is superannoying! (the only thing more annoying with the Fitbit is the even worse GPS-tracking)
11-26-2019 10:24
11-26-2019 10:24
Hi @ONS-n. Welcome to the Forums! Sorry for the delayed response.
Thanks for the steps tried and I'm sorry that the Fitbit app is still not allowing you to enter decimals. I understand how you're feeling about this situation and let me help you out. While you've worked on this, I'd recommend to give a try to the following steps:
If the issue persists, please provide me with your phone's model and Android version. Also, take a screenshot of the incorrect distance displayed on the Fitbit app. To attach it in your reply, see the steps described in this post.
Keep me posted.
11-26-2019 11:27
11-26-2019 11:27
@ONS-n, I would try entering the measurement using a decimal point (full stop/period) first, before all the other hoop jumping. If you are using a comma it may be further confusing the issue as that is not generally the accepted format.
11-28-2019 02:04 - edited 11-28-2019 02:16
11-28-2019 02:04 - edited 11-28-2019 02:16
Hi,
I've followed your tips without success.
My phone is a:
Samsung S9
Android 9
Kernel 4.959-16947752
Build number PPR1.180610.011.G960FXXS7CSJ3
I am in Sweden but the phone is in "full" US English to reduce the risk of any Fitbit-localisation bug (I do have the same problem when on Swedish).
The keyboard is Gboard to reduce the risk of incompatibility between Fitbit and Samsungs keyboard (I do have the same problem when using the std Samsung Keyboard).
See enclosed pictures showing how 5.5km is logged as 55km..
NOTE: The GPS is also (since a few months) totally useless and is now as an average 20% off (was previously 2-5% off), could it be related?
12-03-2019 12:53
12-03-2019 12:53
Hi @Lilbiddy and @ONS-n. I'm glad to see you here and I'm sorry for the delayed response.
@Lilbiddy, thanks for taking the time to stop by and help our friends.
@ONS-n, thanks for the screenshot and sharing more details about this situation. I also appreciate your efforts while troubleshooting the app to get it working correctly. I've reported this unusual behavior to our team so they can work on the Fitbit app and bring a solution as fast as possible. While there isn't a time frame, make sure to keep the Fitbit app updated to the latest version. If there's anything else I can do for you, please keep me posted.
Hope to see you around.
02-19-2020 06:40 - edited 02-19-2020 06:43
02-19-2020 06:40 - edited 02-19-2020 06:43
Any news?
I and some other users seems to have both problems with decimals AND how the GPS data is logged in the app. What I can read it seems like most users having both these problem are using a Samsung phone (mostly S9).
Is it so that Fitbit is not compatible with Samsung? IF so, why not inform us and let us go in with alternative products?
02-20-2020 06:40
02-20-2020 06:40
I gave up yesterday and bought the Garmin Vivoactive 4.
A bit too pricey (especially as I have paid for a Firbit Charge 3 before...) BUT it works!
Had a 7,2km run that was accurately reported! (almost a strange feeling...)
Shame on Fitbit for pushing their customers to jump ship to get a working product!
I'll never buy a Fitbit product again (btw, I'll be surprised if the company is around a few years from now).
Now my biggest problem is to get rid of the Fitbit Aria scale as it does not work with the Garmin software...