09-28-2016 20:32
09-28-2016 20:32
Recently, at some point after Sept. 7, following a FitBit for Android update and a system update to Android N on my phone, I discovered that I could no longer begin an exercise distance entry with any numeric characters other than *1 through 9*; i.e., no initial zero or decimal point. On Sept. 7 I had been able to enter 0.4 miles for a 10-minute session on the treadmill, and that number is still showing as entered in the log. Now the closest number I can enter in order to proceed to the calories-burned entry -- the only one I care about -- is 1. This needs a fix, of course, but the better solution would be to make the distance entry optional rather than required. Remove the "please enter a valid distance" prompt that prevents entering a calorie figure alone. Distances reported by stationary bikes and rowing machines are not uniformly meaningful anyway. Times and calories expended are sufficient.
09-29-2016 04:49
09-29-2016 04:49
Hi there @rkillings, welcome aboard to our Community and thank you for bring this up. I will make sure to pass this information and our team is already working on this, this issue most of the times affects custom food, but is due to the app does not allow to enter decimals.
Nonetheless there is a workaround for this. When you want to enter an exercise if you go straight to enter a decimal it wont let you. Lest pretend you want to log 0.5 as distance; so instead of this, enter 1.5 in the distance field and once you have that number, go back and delete the first number and enter 0. You will see it will allow you to log now distances less than 1.0. Once you have done this press done and you will have your exercise logged with the distance less than 1.0
Hope this helps in the meantime and let me know if you need more help.
"Great things are done by a series of small things brought together.” What's Cooking?