The Step Count is Very Wrong

[SunsetRunner]

I took a walk Wednesday night. I forgot to end the walk. On Thursday, I drove a couple of places.

When I went to walk on Thursday, I realized I forgot and tapped finish. 

Before I tapped finish, my step count on the widget was about 5,000. 

After I tapped finish, my step count on the widget was over 50,000.  

The app said I walked 25.4 miles. I probably walked 5 miles from the time I started the walk until I ended it.

It was ABSOLUTELY my fault for NOT ending the walk. But...

In general, the app ignores the actual distance. It just takes the number of steps and calculates bases on my stride length.  There was day I did a number of walks.  My total distance for that day was WAY more than the total of my walks.

In this case, the app was tracking my distance and calculating the number of steps from that. So the 20 miles or so that I drove (taking no steps at all) were converted to steps.  THAT IS HORRIBLY WRONG.   The step count is the actual number of steps I took.

When I use Samsung Health, I can see the step count change on every step. So I know it's accurate (or VERY close).  On days when I don't forget to end my walk, the step count on Fitbit is way below Samsung Health. 

Fitbit allows me to download my monthly stats which neither Google Fit nor Samsung Health do. That's why I'm using it.

1) The app needs to use the actual steps it registers. And ONLY use those when tracking steps.

2)  It "should" use the actual distance when a walk is tracked, and use the step count/stride calculation when it's not tracked. I'd be okay if it always used the stride, but whatever it is doing now is fairly useless.  I can download my stats, but my stats are garbage, so what's the use.

Moderator edit: Clarified subject

[LanuzaFitbit]

Hello @SunsetRunner.

Thanks for bringing this up and sharing those details on the matter.

The first thing I'd like to bring up is how the Fitbit tracks your activity. You can click here to read more about it and why additional steps might be counted, specially for when you are driving.

In addition to that I'd like to ask what Fitbit is it that you are using to track your walks and activity.

It is important to also mention that if you are not tracking a GPS activity then the Fitbit and the app will only use your steps to determine your distance and never the other way around.

Having said that,  please do know that we appreciate your feedback on the matter and we are always looking for ways to improve the overall Fitbit experience.

Please let me know if there are any other questions I can help you with.

[SunsetRunner]

Lanuza,

I am not using a Fitbit device. I am using the phone (Samsung Galaxy S8+).  I realized I should have said that after I posted. My apologies.

I read the article. It's possible that the count would be better if I were using a Fitbit device, but as it stands, the app had to be calculating my steps based on my distance, not on actual motion. Based on how far I drove, the distance makes sense. The road was not bumpy. Certainly not THAT bumpy.

As far as a normal step count, it is still way off from Samsung Health.  It is possible that Samsung Health is wrong, but when I hold it in my hand and watch in Samsung Health, I see the step count go up one step every time I take a step. It's possible it's not as good when it's in my pocket, but since the Fitbit app and widget don't update real time, I have to go with Samsung Health being more correct, and they usually end up around 2000 steps different each day (with Samsung Health showing more).

I loved the app, and was gong to buy a Fitbit because of it, but I don't like wearing things on my wrist.

Can you explain why the two apps would be so different, and how, if the app works as the article said, it registered 25 miles?  I need to remember to end my walks. That was absolutely my fault, but either there is additional setup I am missing, or there are issues with the app that should be addressed. 

To my mind, the app really does not work with the phone sensor.  If I am doing something wrong, I'd like to know what that is.  If the app really doesn't work well with the phone sensor, I'd like that corrected. I realize I haven't paid anything for this, so I really shouldn't complain. I'm just frustrated.

[LanuzaFitbit]

Hello @SunsetRunner.

Thanks for that further explanation and I'm sorry to hear about the frustration you have experienced.

I wouldn't be able to tell for sure why there is a difference in there. Given that the Samsung app and Fitbit app probably use different algorithms to calculate steps it would be hard to explain. Those differences in algorithms could also explain why the car drive gave you a lot of steps from Fitbit and not on Samsung.

Perhaps you could try going for a short walk and test the results on both of the apps after the fact.

As for a Fitbit that you do not have to wear on your wrist, perhaps you could look into the Fitbit Inspire. It has the option to be worn with a Clip and not necessarily with a wristband.

Let me know if there are any other questions on the matter or if I can help you in any way.

[SunsetRunner]

Lanuza,

I've put in a request to support.  I don't know how the app works when used with the Fitbit, but it's really wrong when using the phone sensor.

I came downstairs this morning.  Samsung Health said I took 28 steps.  Fitbit said I took 0.

I appreciate you time and attempts to help.

Dana

[LanuzaFitbit]

Hello @SunsetRunner.

Thanks for bringing this up and letting me know that you have reached our team.

I am sure that our team will be more than happy to help you figure out what is going on and possible find a solution.

If you ever have the time, maybe you could visit one of our Discussion boards. Lots of different topics to talk about with other users and maybe something in there will pique your interest.

Let me know if there are any other questions on the matter.