Discrepancy between Mobilerun and Activity Tracker

[ncuneo]

I've posted this a couple places and have not gotten a response yet. Anyone have any thoughts on the discrepancy between the calories burned when tracking a run via the mobilerun on the app vs using the activity tracker on the device? I did the same run, same route and pace two days in a row. Burned 197 via mobile run one day and 411 via the tracker the next. Kinda frustrating as l like the the features of mobile run, but beings that I was not having any trouble losing weight a reduction in calories is not needed or wanted!

[slysam]

I agree I don't use the mobile tracker anymore (I tried it a few times). I tried it a few times and it reduced my calorie burn quite a bit. I don't know what the formula the mobile run is using but like any activity logging it overwrites fitbit's stats. I think it is based on GPS distance rather than steps.

[Heybales]

If you know distance and time of the run - you got pace. Perhaps it tells you elevation gain too?

You know your weight, so see which one is closer to best estimate.

These formula's for running between 4-6.3 mph were within 4% of lab measured, so more accurate than HRM or Fitbit (which is actually using similar formula).

http://www.exrx.net/Calculators/WalkRunMETs.html

Use the Gross option, which is what those apps would be reporting, and see which is closer to best estimate.

[Jmkuz]

In addition to the calories burned discrepancy, I've also noticed it doesn't count any of my "mobile runs" towards active minutes! I will go for a walk/hike/run for an hour or so and get anywhere from 45-60 active minutes, just depending on whether or not I stop etc. But when I log my route via the mobile run feature and go, for example today I did an hour and a half hike, I got 2 active minutes.... This is incredibly frustrating!

[Heybales]

---

@Jmkuz wrote:

In addition to the calories burned discrepancy, I've also noticed it doesn't count any of my "mobile runs" towards active minutes! I will go for a walk/hike/run for an hour or so and get anywhere from 45-60 active minutes, just depending on whether or not I stop etc. But when I log my route via the mobile run feature and go, for example today I did an hour and a half hike, I got 2 active minutes.... This is incredibly frustrating!

---

If the distance and time showed a slower pace than what Fitbit estimated, that would indeed be correct.

Can't help you there, because you didn't mention distance. It's time and distance, just 1.5 hr isn't enough info to help figure it out.

Basically write down the steps, mileage, and calories with what Fitbit shows.

Then sync in the MobileRun info.

Write down the new steps, mileage, and calories Fitbit shows.

The workout should show how many steps, miles, and calories the workout itself had that replaced what Fitbit already had - so now simple math to see what Fitbit had prior to replacement.

For instance from recent example.

Prior Fitbit - 14.68 miles

Logged - 13.11 per GPS

Post Fitbit - 14.85

Post 14.85 - 13.11 logged = 1.74 before workout.

Prior 14.68 - 1.74 before = 12.94 Fitbit logged for workout.

GPS was 13.11, Fitbit by steps estimated 12.94. Decently close.

Obviously GPS was more accurate, as was calories. Only Steps was more accurate by Fitbit, but sadly they are replaced with a manual walking/running activity, and that could lower or increase the steps.

But those Very Active Minutes is based on pace and time.

So if the GPS was more accurate (it likely was), then you didn't really go fast enough to get VAM.

So you need to speed up.

Or change the stride length so it's longer than reality, so Fitbit thinks you are walking faster than reality, and really get some VAM time. 

But if accuracy matters (and I'm guessing that's why anyone buys the Fitbit, to improve accuracy), then why not go for most accurate?