As per title. When I use the watch in GPS mode (not connected to a phone) to measure distance in a workout it is fairly accurate. However, the total daily distance doesn't match. For example I went on a 5km run as measured as a workout but my daily total distance is only 4.18km? It seems like only part of the workout is counted in my total daily distance. The wrong daily value is shown on the watch, mifit and notify and fitness.
I have seen elsewhere on the forum issues with distance during workouts calculated from steps but not when using GPS. As above I'm sure it is the daily total that is wrong because the workout distances match my phone.
Anyone else have this issue or a solution? cheers
Related
Hi all,
Just putting this out to see if I could get other user opinions about the calorie counting of the Amazfit Pace.
In my experience it seems like the Pace only counts calories from activities.
If I look back at my activities from the past day, week, month in the app or on the watch itself I'm seeing extremely low calorie counts. For example, the average calorie burned figure from the last week is showing 459 kCal at the moment on the watch. The weekly total kCal burned for the 10th - 16th of December is showing 2970 kCal.
Can anyone confirm this, or let me know what watch / firmware they're if they are seeing normal calorie burn i.e. BMR + activity to give a total figure.
For what it's worth, my fitbit and garmin have both placed me at around 2000 - 2700 calories a day and as far as I can tell both of these devices have added BMR and activity calories together to form a total.
The pace doesn't count calories, it tries to calculate them.
Sure, the use of the word count probably wasn't spot on at the time of writing. But the sentiment remains.
Other devices I've used in the past for example, calculate / estimate / count, calories as a total of BMR + active calories. In my experience I'd see figures range from 1800 - 3000 calories burned per day depending on activity. Over the month I'd expect to see an estimate of about 60,000 - 80,000.
My Pace however, if I'm lucky shows 600 - 700 calories per day, typically lower, and over the last month has seen less than 10,000 calories burned.
I've attached screenshots from Amazfit, Fitbit, Garmin to show the kind of discrepancy I'm talking about. I'm just wondering if this calorie estimate I'm seeing is normal.
some problem in the mi fit app with amazfit bip. for reference, you also can type in data (steps, distances, time, elevation, ...) from activities into your runtastic account, and see it translated.
the mi fit app (if not crashing, as for 3.3.0, algo 1.1.09, as of 2018-03-27) seems far behind everything. e.g. i keeps calorie totals from steps separate from calories burned in each individual bicycle activity. no way of accumulating calories burned. while the sensor data seems accurate (steps, pace, gps) the app only shines with sleep and regular step data, the calculation and views on calories are rather catastrophic. pity
hello i have been using the amazfit bip for a couple weeks now the first week i it recorded 18.19 miles walked 8 hours 57 mins time spend walking but it says i only burned 1388 calories im a 324lb male most of the calorie trackers says i burned close to 4100 calories does anyone have a fix for this
Hi, I have a problem with the calorie counter when cycling.
I set the bike activity on the watch.
I do the same on Endomondo on my phone.
I covered over 10 km and the watch shows 80-100 kcal burned,
and on the same route Endomondo shows 270 kcal.
It's a big difference.
The device loses meaning, if calories counter is wrong.
Has anyone encountered such a problem
For some reason unknown to me, it seems that all Amazfit devices underestimate calories burnt. If your device is an international model, I suggest that you fill a suggestion for improvement in their official website:
https://support.amazfit.com/hc/en-us/requests/new
OK thanks, so I did.
Hey, this actually started happening to me too, on Amazfit Pace. Only thing I can confirm is that it started with 2.6.0.12 WOS update..
I believe that this problem is related to incorrect heart rate counting.
The heart rate is permanently undervalued.
I tested it on cross trainer. When the cross trainer shows 135, the watch shows max 100.
Rough estimate I know, I have the amazfit bip with 12000 steps daily average and my calories are v always in 200s it's almost as if they are doing a different unit not calories because Google fit has me in the thousands not even a close comparison between mi fit and Google fit. Would like to clarify this issue as well.
Faun777 said:
Hi, I have a problem with the calorie counter when cycling.
I set the bike activity on the watch.
I do the same on Endomondo on my phone.
I covered over 10 km and the watch shows 80-100 kcal burned,
and on the same route Endomondo shows 270 kcal.
It's a big difference.
The device loses meaning, if calories counter is wrong.
Has anyone encountered such a problem
Click to expand...
Click to collapse
Hi, I have same problem with the calorie counter when walking-
I set the walking activity.. covered 3.48 km and watch shows 455 kcal burned..
I do the same activity on realme watch... covered 7.57 km and watch shows 231 kcl burned
It's a big difference.
The device loses meaning, if calories counter is wrong.
Has anyone encountered such a problem
swap4118 said:
Hi, I have same problem with the calorie counter when walking-
I set the walking activity.. covered 3.48 km and watch shows 455 kcal burned..
I do the same activity on realme watch... covered 7.57 km and watch shows 231 kcl burned
It's a big difference.
The device loses meaning, if calories counter is wrong.
Has anyone encountered such a problem
Click to expand...
Click to collapse
Yes, I am having the same problem. Samsung health says 223 cal for 5.44 km of walking, but Amazfit Band 5 says 127 kcal for 5.34 km of walking. The variance is too large for Amazfit to be accurate.
I am using STRATOSfied rel 14 | 2.0.32.0 and I'm having the same problem as I had with the original ROM. In long distance races, a certain km altitude has an error. The marking is lost, that is, I am climbing and the marking is as if I had descended and with that even after re-marking right the difference between altitude gets very large.
GiovaniM said:
I am using STRATOSfied rel 14 | 2.0.32.0 and I'm having the same problem as I had with the original ROM. In long distance races, a certain km altitude has an error. The marking is lost, that is, I am climbing and the marking is as if I had descended and with that even after re-marking right the difference between altitude gets very large.
Click to expand...
Click to collapse
Stratos has bad reputation for resulting altitude reporting. Turning on 3D Data in activity setting and syncing to the phone to refresh AGPS might help but I personally don't bother with it anymore. In Strava you can correct altitude after upload or fix it with DEM data on your gpx file before upload (e.g. gpsvisualiser.com).
EDIT: You might try to check following things https://forum.xda-developers.com/showpost.php?p=77315879&postcount=6
I just came back from my holidays. Every morning, I was riding my bicycle and a large part of the course was at sea level. And, every day, I got constantly different altitude readings on my Stratos: from -60 to -10 meters, while at sea level. I also use a Garmin Edge 705 on my bike, which I noticed that it corrects to altitude reading. I suspect that Stratos is just calculating the altitude only using the barometric pressure sensor and not taking into account the GPS data.
keneva said:
I just came back from my holidays. Every morning, I was riding my bicycle and a large part of the course was at sea level. And, every day, I got constantly different altitude readings on my Stratos: from -60 to -10 meters, while at sea level. I also use a Garmin Edge 705 on my bike, which I noticed that it corrects to altitude reading. I suspect that Stratos is just calculating the altitude only using the barometric pressure sensor and not taking into account the GPS data.
Click to expand...
Click to collapse
Actually it depends on the activity: some will use GPS and some will use the barometer. And as you cannot calibrate barometer so far, don't expect a precision lower than -50m/+50m.
Hello,
I'm wondering why the calories burned during an elliptical session monitered by the Pace vary so much. It's crazy. I did the exact same program for all these sessions, a 30-minute with 30-35 seconds at high intensity every 2 minutes, with maximum incline.
Heart rate was pretty much the same every time, but the calories count make no sense. My Schwinn 470 is way too optimistic I think, giving me always 420-440 calories burned for 30 minutes, but the Pace values are out of this world (from 68 to 316)... I'm thinking a realistic value would be around 250 so the Pace was right only once out of 6 sessions?
Anyone noticed these variations while doing elliptical?
See attached pic:
https://imgur.com/a/F53Qy03
Check the HR graph, it's where the problem is. Calories burned calculation is heavily based on HR, but optical PPG used in Pace/Stratos (only one sensor) isn't reliable when you move your arm a lot, for better results use a chest or arm strap.
Ok, but how can you explain then that there is a session where the HR was higher and still showed way less calories burned than an another one with a lower HR?
Average value doesn't matter, without the graphs I can't say anything about the results...
Well, it seems that the last software upgrade changed things a lot. My last 2 elliptical sessions, same routine as before when my Schwinn machine always gave me around 420-430 calories burned while my Pace gave only around 100-130, now, the Pace gives almost the same as the Schwinn, around 420-450 calories burned. Anyone noticed that much of a change in other activities? I read that the last upgrade improved the heart rate detection. Must be the explanation.
Both were improved: HR algorithm (more stable when recording activities) and calories burned estimation (finally they are not underestimated anymore, they are now closer to the values from other sources).
Hi All,
I just replaced my stratos 2 with a strstos3 (the old one died). The watch is what I expected but my surprise is that with the strstos2 the vo2 data was correct but with this one I always see the same value 27 and performance very poor. In addition, the heart rate was ok but when I check my activities and the breakdown for the heart zone, I don't have any time on V2 max or anaerobic. The weird thing is that I do see these values on the watch screen when I'm running or cycling and when I check the heart rate in the app, the values seem to be correct. Anyone facing the same issue and with a solution?
Thank you very much for your help
I use a bluetooth belt since all devices (no exception) do not deliver accurate optical sensor HR data - If you do the same you will have more accurate resutls - My Stratos is giving 54 Vo2 which is almost accurate (my best when I was an athlete was 69
Thanks for your response but I always get the same constant value which is incorrect... On top of it, I have updated the watch to the next version of the firmware and now after 2 min recording the activity it crashes.... A disaster.... Very unhappy about it