yashsingh1/xdaforums huggingface dataset:
[Amazfit] alexinc:
Are you serious? GPS inside buildings for sure isn't working!
[Amazfit] Noramas:
Amazfit show me GPS as available inside the building because of large windows. BTW, if signal is low why Amazfit distance is jumped so much? I saw that distance on the screen was counted and increased almost every second without any watch movement.

I did the same test at home. If Amazfit is located near the window then distance is not counted and stuck on 0.00km. If I try to walk inside the room the the distance start to count and after few minutes show 300-400 meters. Strange.
[Amazfit] Beleriand:
It is not strange. GPS works by measuring the time signals from different satellites take to reach your device. Then your position is calculated by triangulation.

It is only accurate if you receive direct signals from satellites all over the sky. Inside a building you have no sky view so all the signals you get are reflected by objects like buildings, mountains. If they are reflected they travel a longer distance and so the calculation loses precision. That causes jumping positions and therefore creates some mileage.

Older, less sensitive GPS devices only used direct signals and were much more precise but they also completely lost position in dense forests and between high buildings.

All modern GPS consumer oriented modules on the market are optimised for a quick fix, even under worst condtitons, then comes power saving and price.

Precision is the least of the requirements as you can adjust your position to a map when using it for navigation. (Lock to road)

Good for all the smartphone manufacturers and Google Maps users but bad for all outdoor enthusiasts.
[Amazfit] js_online:
same issue

Hi!

I got the same issue. Amazfit CN version. Firmware Rel 9 (1.2.14) from XDA.

Running in forest, orienteering. Amazfit watch in Trail run mode always reports 400-500m less within 7-9km distance. Difference is confirmed by 5-6 runs.

For example today Amazfit watch: 7.97km, Endomondo (Samsung S7): 8.42km.

I see also issues with max speed, its unreal on Amazfir watch (crap should be filtered out).

I plan to do test using Amazfit and my old Garmin Forerunner 300 in next weeks to prove test results.

Kind regards,

J.
[Amazfit] vactirio:
Hi J.

After opening this thread I did get in contact with Huami.

I informed them about the GPS accuracy problem and they were kind enough to send me a new watch.

Unfortunately this did not help. The new watch had exactly the same bad behavior.

So I stopped using the amazfit. I found also to have more than 200-300m less at a 9Km run.

As you probably know that's too much for such a distance.

Below is the mail I did send to Huami.

I did not get yet an answer to that and I think I will not get one :(

---------------------------------------------------------------------------------------------------------------------------------------------------

Got yesterday the new Pace. Pretty exciting I must admit.

I did a 9,5km run on purpose last night in order to test it.

On my left hand both Amazifit Pace and Garmin 405.

Unfortunately the results were not better and much disappointing :(

So to start I should say that I run in rural areas but in open space.

I attached to this email two GPX files in order to get examined by your team.

One from my old Garmin and One from Amazfit.

On the 9,5km run I got a liithe more than 200m of difference.

This difference is translated in 6 seconds of pace difference which is vary big for a runner.

Pace difference is shown bellow:

(strava is from amazfit and runkeeper is for garmin)

So I uploaded both GPX files on http://www.mygpsfiles.com/app/ in order to visualize them and the findings were interesting.

It seems that though Amazfit gets much more points than my old Garmin, those points are often very inaccurate.

Please find bellow some examples.

Orange trace is Garmin.

Blue trace is Amazfit Pace.

Amazfit (in blue) seems really off road.

Here it seems to loose distance. I did run as Garmin says to the roundabout

I must emphasize that its really an open space run with a very good GPS signal reception.

So it seems that its something going wrong with the GPS of the Amazfit.

I am wondering if there is a calibration problem with Europe/Greece.
[Amazfit] js_online:
Thanks for explanation and visualization. Unfortunately I can't link my workouts with street as there are no streets in forest :)

I am little bit surprised about this: Endomondo makes less measurements and counts more, Amazfit makes times more measurements and counts less.

I was searching answers and found this article online (type: www dot fellrnr dot com/wiki/GPS_Accuracy), must read... Explains many issues from technical perspective.

I believe and hope that issues are related to software (firmware) of GPS chip and post processing and will be solved in the next firmwares.

Please also note: "AMAZFIT includes the world's first 28 nm Sony GPS sensor". As you know first is always first and requires debugging :)

"Sony – GPS (with 1/10th the power!) now sampling.

You know how using mapping apps on your smartphone kills your battery? Well now there’s hope. Sony’s getting some super impressive results with their new GPS using 28nm FD-SOI technology. These GPS are operated at 0.6V, and cut power to 10x (!) less than what it was in the previous generation (which was already boasting the industry’s lowest power consumption when it was announced back in 2013)."

You can find more info online.

I completely agree that for running numbers are important. Especially for high pace 4.30 and below, because each seconds counts. I will take Amazfit to my next street workouts for marathon training to do the same gps data analysis as you did above.

My strategy is to wait for firmware updates and hope issues will be resolved.

Thanks.
[Amazfit] vactirio:
Hi J.

I used http://www.mygpsfiles.com/app/ to visualize both Garmin and Amazfit Pace paths. I think its useful.

Also I highly recommend that if you after your investigation you get also bad results to contact Amazfit support so that they know that the problem is serious.

When I first contacted them they said that they are not aware of any gps problems :(.

Attached are my GPS trace files for future reference.

Amazfit Support email: support "at" amazfit.com

Andreas
[Amazfit] js_online:
Yes, I will contact for sure. This is the plan. Thanks for for info.
[Amazfit] js_online:
I used gps tracks to compare. The most interesting is that GPS tracks shows same distance 8.1km

Endomondo (Samsung S7) shows 8.42km (320m difference). MiFit 7.97km (130m difference). From this perspective looks like issue is related with gps data post processing.

I see that Endomondo is also not doing post processing for Amazfit TCX file during import and export GPX file is exactly the same (this is good).

On the map I see that Amazfit curve looks more precise (at least by eyes), more smooth curve, more measurements, but Endomondo places points more far way and getting more distance even with cut. This is probably the reason how Endmondo calculates more distance with less points and cutting lines.

Somebody on this forum mentioned good visualization for this case - man walking with dog. In this case story is the following: dog running around man during walk have less distance than man :D Unbelievable? How this is possible?

View attachment 4117734

View attachment 4117735

View attachment 4117736
[Amazfit] lucas_max:
Yesterday I made a run for testing. I worn Amazfit on left and Garmin Vivoactive on right hand, connect to the heart rate strap on my chest. Here are some result:

[IMG="GPS 1"]https://c1.staticflickr.com/3/2891/34004197431_232d5b0468_c.jpg[/IMG]

[IMG="GPS 2"]https://c1.staticflickr.com/3/2813/33291930414_34b94ec4ba_c.jpg[/IMG]

The speed graph, the Amazfit record always jump weird (the same when i import file the Garmin site), but on Strava the graph is ok:

[IMG="Speed Graph"]https://c1.staticflickr.com/3/2948/34004196051_3dff2a3fb0_c.jpg[/IMG]

Heart rate graph:

[IMG="HR Graph"]https://c1.staticflickr.com/3/2889/33291930754_8eb9c4ae16_c.jpg[/IMG]

[IMG="Latitude"]https://c1.staticflickr.com/3/2812/34004197581_7e98044e63_c.jpg[/IMG]

[IMG="Longtitude"]https://c2.staticflickr.com/4/3942/33291930844_fff201ba25_c.jpg[/IMG]

I think the watch is good enough for use, note that the first time after change to the new rom or update, you should connect to phone to get correct location from phone, then go outsite to get GPS signal. The next GPS time must be good.
[Amazfit] vactirio:
Thanks for the info Lucas.

- Did you get same distances for both Garmin and Amazfit?

- Can you post a bigger image of the track? Cant see details and how far is one trace from the other.

Andreas
[Amazfit] lucas_max:
- When I was running, the garmin watch always alerted first for each 1km (mean amazfit need more distance). At the last lap (lap 10) I must run more ~50m than garmin for 10km enough on Amazfit.

- You can open from the attachment file.
[Amazfit] vactirio:
I will try to follow that tomorrow and make a new test though I am not expecting miracles.

Also is there a possibility that the GPS works well in some continents (Asia for example) and bad in some others (Europe for example)?

Andreas
[Amazfit] lucas_max:
I have no ideas, before buying this watch I saw on Strava Amazfit Club there are a lot guys at Europe and their track records are very well.

Visit here: www.strava (dot) com/clubs/amazfitpace

Look on Recent Activity Tab
[Amazfit] js_online:
trail run, huge difference

Thanks for detailed info and analysis. According to link I posted previously Amazfit watch seems from the same category as (type www dot fellrnr dot com/wiki/GPS_Accuracy) Garmin VivoactiveHR with up to 40-50m per km deviation from ideal world, so there is no surprise that they found each other in perfect match :)

Yesterday I got biggest difference during my trail run. I see that Amazfit watch curve is more smooth and realistic, but result interpretation counts less distance.

Amazfit watch and MiFit calculated 6.86km. This is not realistic, I was doing orienteering, ideal track (straight lines between control points) was 6.74km. Endomondo with Samsung S7 measured 7.79km which is also not realistic.

I did extract of TCX file from Amazfit and GPX from Endomondo and looked up in MyGPSFiles tool and I see 7.2km for Amazfit and 7.4km for Endomondo which makes sense and looks real.

My conclusion is that Amazfit is 200m more precise than Endomondo with Samsung S7 during my 7km run, but interpretation of results is crap on both.

I plan to do test with old school Garmin 300 soon to see one more perspective.

Thanks.

View attachment 4119431

View attachment 4119432

TCX - Amazfit (red), GPX - Endomondo Samsung S7 (blue)

View attachment 4119433

View attachment 4119434
[Amazfit] lucas_max:
Not sure that the GPS on phone is correct or not, I had time using Samsung Galaxy S1 and S3, and their GPS are very bad. I think around 10km, 100-200m is not much important.
[Amazfit] vactirio:
No the contrary.

Every medium to average runner will affirm that it is a HUGE difference.

Andreas
[Amazfit] js_online:
one more case

I completely agree with this. 4min/km and 4:30min/km is huge difference. 4:30 and 5:00 requires also a lot of effort :)

One more trail run case from today. Running with Amazfit watch only (phone left in car). White forest on orienteering map (can run it on full speed).

Ideal distance (straight line between control points): 7.190km - this is measured track, workout should not be less than this number. Not possible in real life as different paths are selected during workout.

Amazfit watch (MiFit): 7.55km, avg pace 6.22min/km

Endomondo (TCX import from Amazfit Watch): 7.81km (+260m), avg pace: 6.08min/km so this proves that Endomondo is doing correction of source GPS files (last time I concluded opposite).

MyGPSFiles tool (same TCX file from Amazfit watch): 7.9km (+350m), avg pace: 6.07min/km
[Amazfit] vactirio:
Guys you don't get it.

Check this image.

Blue is amazfit - orange is garmin!!!

GARMIN is on the road.

Amazfit is ELSEwhere!!!!
[Amazfit] js_online:
you point is clear :)

You point is clear ;)

Few more questions.

Is Garmin TCX/GPX file raw file from watch? Maybe Garmin app doing kind of post processing during reading file thru Garmin app... Disconnect from Internet while reading file???

Please try the same workout in "Trail Run" mode with Amazfit to see the difference.

PS I sent email with my finding to Amazfit support. Waiting for reply ...
[Amazfit] lucas_max:
Sorry my words, I mean sometime 100-200m difference for 10km is ok, but if it happens often its a big deal.

What is the defference in "Trail Run" mode with Amazfit?
[Amazfit] js_online:
I saw somewhere comments during my searches that this Trail run mode is more precise on Amazfit. I just want to check is this real or not.

Theoretically more measurements are done, altitude etc., but I will not be surprised if this mode is also more precise on this device.

Thanks.
[Amazfit] vactirio:
Will try trial mode tonight and will let you know.

Andreas
[Amazfit] vactirio:
Trail Mode did not ameliorate the results....
[Amazfit] js_online:
confirmed

Hi! Thanks for updates.

Yesterday I finally did my test with 3 devices: Garmin 305 (old school), Samsung S7 (Endomondo) and Amazfit Watch.

Garmin 305 and Samsung S7 were completely in sync in open areas. Amazfit was loosing 20-50m each kilometer in open areas from the begginning.

From 5km until 10km I was running in park (open road thru forest) and entered to forest for 50-100m as road was closed. After entering forest Garmin 305 started to lose distance and Samsung S7 worked better - I believe assisted GPS (A-GPS) did work here. Amazfit was loosing more in forest and also during turn around etc. I noticed 200m difference after 10km and it was increasing until 330m at the end of the workout. I analyzed route and even Samsung S7 (Endomondo) cut corners during the turns, so actual distance was longer ...

Results:

Samsung S7 (Endomondo) = 14.77km

Garmin 305 (Old School) = 14.69km (80m difference) - this is OK, I expected the same from Amazfit watch

Amazfit watch = 14.44km (330m difference)

Distances according to MyGPSFiles app. Found only few places where devices went out from sync. Most distance they are in sync.

View attachment 4129422

Avg pace, speed:

Samsung S7 (Endomondo): 4.46min/km, 12.6km/h

Garmin 305 (old school): 4.48min/km, 12.5km/h

Amazfit watch: 4.53min/km, 12.3km/h

View attachment 4127817

Post updated. File contains gps files from all 3 devices.

View attachment 4129421

Conclusion: if manufacturer will not fix lost distance issue (resulting to incorrect pace etc) this watch is not good for running because its important to see correct numbers on Running Watch and it will not be nice to end up half marathon/marathons with missing 100m :D

I can leave with this issue at this moment, use multiple devices during workouts and hope issues will be fixed in new firmware, but this is sad ...

PS2 Heart rates zones also should be configurable, because aerobic and anaerobic zones can be defined by runner only using conversation on different approach.

Thanks.
[Amazfit] ktulu73:
Is this what the watch shows or is this from strava?

I did a walk yesterday, and my girlfriends p9 lite measured 3.93 km, the watch 3.91km but strava shows only 3.8km.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[Amazfit] js_online:
This is directly from watch. I have Chinese version, so no Strava only Mifit. Amazfit watch an MiFit show exactly the same numbers.

As I found earlier, if I export TCX file and load to other tool (Endomondo, MyGPSFiles app etc) I see higher numbers, so part of the issue is definitely watch software and how Amazfit performs calculations based on received GPS data... This should be fixed ...

My point here is that I want to see correct numbers on Amazfit watch during workout, not at home after exporting TCX file and loading to external tool :)
[Amazfit] vactirio:
For me, the difference is on the watch not on Strava.

When I finish my run I get 200 to 300m diff on the watches.

Andreas
[Amazfit] js_online:
Updated my previous post with workout GPS files from all 3 devices.

MyGPSFiles app calculated distances differently. So this confirms again that GPS data is acceptable (I hope so) and issue is related with the way how device software interprets GPS data.

All devices are mostly in sync during workout except few places. Amazfit lost track on the picture below in city. Garmin 305 lost track in the park (forest).

View attachment 4129442
[Amazfit] js_online:
gps firmware update 1.2.17

Installed new firmware yesterday (1.2.17, permanent install). According to release notes GPS firmware is updated. So time for new tests :)
[Amazfit] lucas_max:
This morning I had a ride with new firmwware 1.2.17

Amazfit: 21.35km

Export to Strava: 21.4km https://www.strava.com/activities/968317473

Strava export to Garmin: 21.38km https://connect.garmin.com/modern/activity/1711420660

Strava export to GPS Visualizer: 21.385km (picture attachment)

I rarely have trouble with distance recording but the route, gps always drift out of the road (about 5-10m), and now with the new firmware it seems the same.
[Amazfit] js_online:
Today I tested Amazfit with new firmware 1.2.17 in Oslo on the same route I used previous time (Amazfit Watch vs Samsung S7 Endomondo).

I really feel improvement. First 10km completely in sync. Sometimes AMazfit was reporting little bit faster. Amazfit watch lost little bit mileage in park (forest) and during turns in the second half of workout, but difference was minimal an this was not critical for mileage and pace calculation.

Final results:

Amazfit Watch (1.2.17):

Time:1:12:14 Distance: 15,11km Pace: 4.46min/km

Samsung S7 Endomondo:

Time: 1:12:10 Distance: 15,17km, Pace: 4.45min/km

I believe results are now completely acceptable.

I will do more testing during my next workouts.
[Amazfit] vactirio:
Is it the English or Chinese version?
[Amazfit] lucas_max:
With me everything now seem to be ok but the track (see the attachment picture). It seem not about gps-lost but I dont know the reason... I ran on the road not on the pavement and not through the building.

Distance - OK

Pace responding and calculation - Ok

Tracklog on maps - Quite good but need more more improvement

More: Laps split (now dont have)
[Amazfit] js_online:
Chinese Amazfit Watch with XDA permanent firmware 1.2.17.

---------- Post added at 11:19 AM ---------- Previous post was at 11:09 AM ----------

I see your point and hope this will improve in next firmware versions.

For me this is minor thing as long as pace and distance is correct. For example for orienteering any software attaches (moves) you track to control points (for example RouteGadget, LiveLox) even if your track is 1km away (so position is fixed) and you can replay workout and compare performance with other runners.
[Amazfit] berimbadas:
Hello I have the US version and it already came with 1.3.2b so I can't use the pace field firmware. I saw that there was 2 gps firmware updates, can anybody compare it with garmin or suunto watches to see if it's more usable now for running?
[Amazfit] lucas_max:
You guys can see, if we ran on the strange way, the gps route is very good, but if there are alot of turn or round place, the route would drift away from the road.
[Amazfit] vactirio:
Yes this drift is a big problem. I usually run with other runners an I get more than 200-300m (in a 10k run) less distance compared to the others.

This is the reason I stopped using this watch.

There is a relative discussion room is strava site.

https://www.strava.com/clubs/284069/discussion

Andreas
[Amazfit] lucas_max:
I never have any problem with distance, but the track route make me feel uncomfortable, and sometimes it miss the segments on strava
[Amazfit] berimbadas:
Looks like there is an update coming in the next 10days for the US version.... Let's see if solves gps problems. The GPS firmware will be 3.something... We still have 2.85...
[Amazfit] neometaller:
Hello,

First run with my Amazfit (latest PACEfield rom 1.2.12) and to try, I kept my iPhone with runtastic

iPhone : 795 GPS points => 5.91 km

amazfit : 942 GPS points => 5.65 km

by analysed the 2 tracks I can say the iPhone add some distance and the amazfit cut some

in globality, the iPhone seems to be more accurate

example : in pink the iPhone track and in blue the amazfit
[Amazfit] js_online:
I believe this rom is too old and for me results changed starting from 1.2.17 GPS firmware update.
[Amazfit] neometaller:
my mistake, I'm on last PACEfield rom based on 1.2.22
[Amazfit] AngelEbratt:
Hi, I ordered an Amazfit pace and I would like to know how is the gps doing so far.

Thanks!

---------- Post added at 07:03 PM ---------- Previous post was at 06:59 PM ----------

How is your gps doing after the update?
[Amazfit] mumfordfan:
In this thread the Chinese firmware update probably fixed the problem.

I 'm running the stock rom, hoping/waiting for the English update.
[Amazfit] NothingCtrl:
Hello,

Any update about this, does GPS are fixed? I'm going to buy this on mid of this month.

Thanks.
[Amazfit] LiFe_sTyLe:
Hello !

I dont want to start new trhread - just one question:

Does Xiaomi Huami Amazfit has auto pause - when I stop cycling/running does it pause automatically or you have push touchscreen?
[Amazfit] js_online:
Pacefied firmware Version 1.2.37

I ran the same track I messaged long time ago.

GPS accuracy is significantly improved now. I got max 0.05s pace difference between S7 (Endomondo) and Amazfit watch.

Workout consisted of many different elements: city (open), city (close buildings), open areas, park, forest, long lines, rounded corners (like on stadium) etc.

Endomondo: Time 1:05:05, Distance: 13.50km, Avg Pace: 4.49min/km, Max Pace: 3.29min/km

Amazfit Watch: Moving Time: 1:05:03, Distance: 13.43km, Avg Pace: 4.50min/km, Max Pace: 3.30min/km

---------- Post added at 10:19 PM ---------- Previous post was at 10:10 PM ----------

If you install latest Pacefied firmware (I have Pacefied firmware Version 1.2.37) there multiple option now.

In Activity Settings there are two options: Run Auto Pause, Riding Auto Pause. These options are turned off on my Amazfit (not good for orienteering).

During running session today I stopped in the mid of the distance (turned around before returning home) for 10-15 seconds and in the workout I see exactly the same: Total Time: 1.05.18, Moving time 1.05.03. As I understand Avg Moving pace is also calculated from Moving time. I assume with Auto Pause turned on Total Time will be equal to Moving Time.

Last option is pause manually by pressing button.
[Amazfit] mumfordfan:
There is a new firmware for the English version, 1.3.4f.

Has anyone tested if the GPS sync to strava accuracy is better now?
[Amazfit] m0j0.j0j0:
Still inaccurate gps

Hi mumfordfan,

I tested yesterday with my English version and firmware 1.3.4f. And the gps tracker still inaccurate.

I walked with dog's with Pace in walk mode and the phone Zenfone 3 ze552kl running Endomondo in walk mode too.

The activity started after Amazfit Pace sync with GPS.

The results are:

Amazfit pace/Strava: distance -> 4,0km, duration: 56m:16s

Endomondo: distance -> 4.60km, duration: 56m:37s

I'm really frustrated with these results. Any help will welcome!
[Amazfit] orenfl:
I fully agree - up until this version of the firmware I had quite accurate height measurements.

With this new one, the height measurement are obviously inaccurate, such a pity.
[Amazfit] benna:
Hi All. Just to make sure. Does the GPS on the BIP work WITHOUT a phone?

I see a BIP Lite version on presale on gearbest. Is this also a GPS one that works without a phone? I want to buy one but I get mixed inputs. Thanx !
[Amazfit] RaVek:
I have a huge request.

Report a problem with GPS here: support@amazfit.com

I hope they fix it, I already have no patience, I run 10km (according to endomondo and Garmin), and Pace shows 9.75km ...