yashsingh1/xdaforums huggingface dataset:
[Amazfit] fzelle:
After the Watch has acquired the satellites and shows you that it is ready, you press the button.

Then you see the count down 3..1.

Unfortunately Android needs longer on an unassisted device to really get the correct position.

Try to wait an additional 10 seconds after the satellites are found, maybe you have better distances then. ( at least we know it's that ).

And by the way, just because Endomode shows you a distance, doesn't mean that is true.

Have you tried to use something else to verify the distance?
[Amazfit] frofa:
Guys, I have read the whole thread, but I just cannot believe it. You are complaining about a measuring error of around 2 to 2.5%. I am a scientist, and often would be happy to have 2.5% measuring error only, even with professional equipment that costs thousands and thousands of Euros. So, instead of complaining, wouldn't your life be much easier and comfortable if you started to live with minor measuring inaccuracies? Especially when you compare two different devices, just consider that BOTH contribute to the final error, and yes, sometimes the device that costs one third of the price of the other one might contribute a bit more. That doesn't mean it "cannot be used", does it?
[Amazfit] RaVek:
I always wait longer then 1minut after get 'fix'.

I compare pace to endomondo on 2 phones and Garmin watch, always -200/300meters on 10km on Pace.

1 more thing, If I take part in the competition for 10km, like my friends and only i have ~9.75km at the finish, rest of the friends have 10.02/10.05/10.01 And that looks like that after all the competition, it's probably something is not so good.

But you are not a runner from what I see. 200 to 300 meters this is a big difference. Even in comparison to old garmin Pace in this aspect falls worse. So plz dont tell me about price, cut distance on bends - this is bug on Pace.
[Amazfit] 2fast78:
I can confirm this issue. On my last run I had 14,1km on the TomTom Runner and 13,7km on the Amazfit. When I compare the tracks I see the Amazfit cut the edges and drifts a lot. So I stay with my TomTom for running [emoji20]

Gesendet von iPhone mit Tapatalk
[Amazfit] chenrp:
please upload the GPX file and/or send it to AMAZFIT team so they can fix it in the next FW...

maybe upload it to there facebook account aswell...
[Amazfit] RaVek:
I do this. Send to amazfit gpx file from garmin, android and pace, i got answer ' Our developer team has already known this issue and they will keep optimizing GPS accuracy.'
[Amazfit] chenrp:
Cool!maybe they will fix it before I’ll get my new watch!
[Amazfit] RaVek:
I did yesterday test Pace vs Garmin vs Lenovo android phone in the stadium, one lap has exactly 400m.

I ran 5km, about 12.5 laps

Pace 4,6 km

Garmin: 5.01 km

Lenovo: 5.03 km

400meters on 5km is a great difference, lots of bends, so could be expected.

But I have a thought, I attach a training screencast, gps track looks great, so maybe it is not a problem in gps, but in the algorithm that calculates the distance?

I send this info to Amazfit.
[Amazfit] chenrp:
No solution for this? This watch is useless if this issue won’t be solved soon.
[Amazfit] steekyjim:
You're a scientist eh? Well, there are several devices and software applications that do not have this issue. We are looking to improve the software by finding bugs and helping improve our devices. Comparing data from other devices is a good way to do that. I run measured races, where people physically go out and measure the length of the race beforehand. My Samsung Europa, S4, J6 and my Xaomi Redmi 4X all give me distances very close to the actual distance, usually at most .1 km out after a 10 km or 5km run. My amazefit is nearly .3 km out after a 5km run. That's about 30 seconds off if im running really fast, more if im you know, on a 5 or 10k race. I may not claim to be a scientist or a mathematician, because my head is not up my arse, but I would like to get my amazefit as accurate as my other other devices. Part of software development involves finding and removing bugs, as well as improving performance. That's the point of this discussion.
[Amazfit] steekyjim:
I'm on strava. I run a 5km race every saturday. Adidas Micoach (old version) and Strava both usually say it is either 5.0km or 5.1km. Amazefit today (18 Nov 2017) says it is 4.76km.

https://www.strava.com/athletes/16226978

These runs are all labeled as parkrun. Amazefit was parkrun 49. I have attacheed a GPX of the run from today. Will see if I can get anything from the other times I've run it.

Also, there were many other people running it it, so we can see what distances their devices were showing it as.
[Amazfit] chenrp:
we need to compare two GPX files... one from the watch and one from other device and compare the files and see where and why we get different measurements.
[Amazfit] frofa:
Steekyjim, you obviously didn't get the point. The point is not that I have anything against reporting bugs, in fact I am constantly reporting bugs in apps and devices myself. The point is that a consumer grade device such as the Amazfit is not "totally useless" just because it has a measuring error of 2% (which is pretty good for any kind of complex measuring device, by the way).
[Amazfit] steekyjim:
This thread is for people to share their data and try and help fix the bugs. Stick with the programme.
[Amazfit] plouprou:
My experience on Amazfit GPS accuracy is not so bad. Last Sunday I ran with Amazfit Pace and a smartphone executing "Endomondo". At the end of the run, Amazfit calculated distance was 7.3 km while phone (Endomondo) was 7.39 km.

Exporting both tracks to google maps gives a little difference on this data. Google Maps says Amazfit track is 7.33 km long while phone track is 7.31 km.

Endomondo calculates a different distance (7.39 km) than Google Maps (7.31 km) over the same gpx track stored by the phone.

For sure there are more factors (Endomondo calculations for example) in addition to GPS accuracy when comparing both devices.

Anyway, differences (7.33 vs 7.31) are pretty small (I believe).

Amazfit ROM version: 1.2.44 (chinese ROM)

Here you have a link to the map with both tracks (blue amazfit, red smartphone)

https://drive.google.com/open?id=1j4RHHBbpibaCT4pvoaC6paKgpyKKUZ_I&usp=sharing
[Amazfit] fzelle:
If the blue route is really the amazfit one, it is way more accurate then the phone.
[Amazfit] plouprou:
Yes, the blue line is amazfit track, and yes, it seems more accurate than phone track.
[Amazfit] fzelle:
I have the same, although like you I very seldom have houses or a forest around.
[Amazfit] Bentzia:
Also having this issue

Any solution?
[Amazfit] RaVek:
Describe your problem and send it here: support@amazfit.com I am asking for anyone who has this problem, maybe Amazfit will fix it sooner.
[Amazfit] ndhakara:
Hi,

I run with amazfit pace in first time I can tell it measured almost -100m per 1k. My aim was 13K and I run in stadium that s why I know my correct distance. As you see red lines in maps, it is so messy. My watch's rom version is 1.3.5. I m going to run 19,5K on Sunday both sony z5c and amazfit. I will see differences.

BTW what about custom roms?
[Amazfit] ndhakara:
After my last post I run twice and those runs' gps measurements are so good. Only diffrence was that I changed the watch from left to right wrist. Have you ever tried different at different arms?
[Amazfit] denzl.flash:
Users from EUROPE .... Are you enabling GPS + GLONASS satelite on your Amazfit smartwatch?

In GPS + GLONASS mode track must be much more precise???
[Amazfit] fzelle:
As you can't enable or disable that, who should know?
[Amazfit] Proxor-s:
I found GPS in my Amazfit Bip much better, than in my Lenovo A606.

I made a run with both devices. Blue line is Amazfit, yellow line is recorded by the phone.

Amazfit shows my track around the building more accurate:

[IMG="5-stage building"]https://cs5-2.4pda.to/11830079.png[/IMG]

Phone ignores small loops I made:

[IMG="Run arount fountains"]https://cs5-2.4pda.to/11830076.png[/IMG]

[IMG="Small loop"]https://cs5-2.4pda.to/11830077.png[/IMG]

There is a problem: Amazfit dosen't record correct timestamps for first 30 points, or near there. When you export data to gpx and open with any other GPX-viewer, you see, that time starts only after 30-60 sec. part of your training. Total time will also not be the same.

It seems not to be an export problem, I tested two different exporting apps. So the problem should be solved in firmware.
[Amazfit] Shadowravenn:
GPS all over since last update

Hey guys,

My Amazfit Pace watch has been really awesome for the last year that i've had it, but since the latest ROM update 1.3.6d my GPS has been terrible. Had trouble getting it to sync and got that AGPS out of date error for a while, but finally got that to work. Now when I run, every run I do the GPS is totally inaccurate regarding my pace and distance etc.

I don't know that's going on, but it's frustrating to me as it is a nice watch, but now one of my most important features is not working properly... What's going on???

P.S: Tried to put my GPX in here, but I can't find any attachment button...

Thanks,

Francois
[Amazfit] xaametz:
I'm also having GPS accuracy issues with Amazfit Pace A1612, ROM version 1.3.6d. Everytime I go running it misses some hundreds of meters. I usually run in open areas, not surrounded by buildings and I always wait until the satellites are found.

I've tracked my run with two different GPS. In blue you can see the Amazfit track, and in yellow it's an Android smartphone. I've run the same path in this part of the run, which makes it easier to detect the Amazfit's GPS accuracy problems.

You can see it in here: https://imgur.com/a/Jjln3

Has anybody managed to solve this issues?

Thank you so much in advance.
[Amazfit] Shadowravenn:
What you're saying is exactly the same for me, 'cept my avg. time does seem off too. It's highly frustrating as i'm also checking my current pace regularly with specific training methods whilst jogging. It seems like we're running very similar speeds to, around that 5:45/km mark. I don't know that to do either dude...

I've read somewhere that you can flash the current ROM and upload an older version, but not sure how it works and don't want to screw up my watch. It's been awesome since now.
[Amazfit] dsaft:
Is the latest ROM 1.3.6d fine for your runs?

Hi,

I have already reported in this thread my bad running experience with the latest ROM 1.3.6d.

It seems that some people is having the same.

But a good question is:

Is anybody running with ROM 1.3.6d having a normal behavior: good and responsive instant pace feedback, good average pace, good distance, good HR, good GPS stability, ...?

Please share!
[Amazfit] gabrielcatalan:
It works fine for me, version 1.3.6d
[Amazfit] dsaft:
Did you just update your watch or did you also perform a factory reset after the update?

How is your watch configured?

Mine has:

Lap alert = OFF

Safe HR alert = OFF

HR alert = OFF

Run auto pause = ON

Riding auto pause = OFF

Target time = OFF

Target distance = OFF

Pace alert = OFF

Data screens = 6 fields

Continuous HR = OFF

Thanks!
[Amazfit] gabrielcatalan:
I just updated.

Lap alert = ON

Safe HR alert = 190

HR region alert = OFF

Run auto pause = ON

Riding auto pause = On

Target time = OFF

Target distance = OFF

Pace alert = OFF

Data screens = 6 fields

Continuous HR = OFF
[Amazfit] toto1988:
Hi guys,

I have the same issues with the gps accuracy. gps accuracy is realy realy bad on my Amazfit Pace. missing distance on a 10km track is 250 - 400m. It´s terrible and not possible to compare running tracks and trainings with friends or to start a run based on the pace / km.

Every smartphone and other running watch (Polar) has a much more better GPS accuracy
[Amazfit] dabgergo:
Hi,

I received my Amazfit Bip a week ago and have tested the GPS for running and cycling. While I like a lot of thins about the watch, the GPS is pretty inaccurate, and it makes the whole watch useless for me.

My problems:

1) It needs about 30sec at least to get GPS signal.

2) When cycling it has a huge latency: when I stop it shows for like 10sec a higher speed than 0. It makes the av.speed and miving time calculation totally wrong.

3) When running it misses about 150-400m in 10km.

Do you think there will be a fix for these?

The interesting thing is that a lot updates were downloadod automalically but the GPS accuracy hasn't changed :(
[Amazfit] goTouch:
I guess what we all want is a cheap watch to be as good as a Garmin watch. I've been running with my Fenix 3 and Stratos together for almost two months, 10km to half marathon . Stratos does a good job and I think I could replace my Fenix 3 for running. But put them side by side, it is noticeable the GPS accuracy of Stratos isn't as good as Fenix. I configure Garmin to record second by second. Opening GPX file from Stratos, I figure it out that it records every 2 seconds, which is still good and very impressive considering how long battery can last during activity.

Taking all this into account, I could say:

1) It is a beautiful all day use watch with an excellent price.

2) If you like to compete and make real training, buy a professional watch

3) For casual runners, Amazfit Stratos does a good job. Buy one and do not compare with a Garmin or other professional watch. Use it and you will see it is good enough.
[Amazfit] RobbH:
I used to use a Garmin Forerunner 305 running watch. Several years later, I think it's still considered one of the most accurate GPS watches ever made. BUT, in order to get that accuracy, it was necessary to leave it outside for several minutes, usually on top of a car, so it could get a solid GPS lock.

My current GPS watch is a Polar M600. The GPS is almost as accurate as the 305, and I really like being able to walk outside and get GPS lock within seconds. Still, my experience is that every GPS watch will tell you it's got GPS lock as soon as it finds the minimum number of satellites (probably three), but it needs more time before it can achieve any sort of accuracy. With the Polar, about 30 seconds more after the initial lock is usually enough.

I tried leaving the Bip outside this morning for a full five minutes while it acquired satellites, and its GPS performance was much better than I had seen before. It's still not going to compare to watches costing three times as much, but I think it's usable.
[Amazfit] ljuba_dude:
https://xdaforums.com/showpost.php?p=79203153&postcount=4
[Amazfit] cumbrianrunner:
This is the worst GPS accuracy I ever had - just a few days ago - a 4.4 mile cycle ride was reported as starting out in the middle of the sea!

[IMG="Stratos GPS"]https://drive.google.com/file/d/1WRvBgYwEDGczOXyDpSSUm8Jf2J5zCZZA/view?usp=sharing[/IMG]

https://drive.google.com/file/d/1WRvBgYwEDGczOXyDpSSUm8Jf2J5zCZZA/view?usp=sharing
[Amazfit] Hexxer:
Im wearing the "Verge" and im happy with that. But, i wont go up in fire if there are missing 1 or3% from 10.000m .

Bevor i wear a Garmin Forerunner 235 - the distances are pretty much the same. Sometimes this, sometimes the other. After that: Vivoactive 3. Worst Garmindevice i ever wear.

Im not that sportman to wear a 400€ Fenix or so. So you can wear a 120€ Verge or a 450€ Garmin.....you pay 350% more or deal with a lost of 3% steps.

A Jacket on the arm is a problem for the Verge, also for the garmin. And if you like realy to be pissed? Try one of the Samsung "Sport" devices.
[Amazfit] ljuba_dude:
Yes. But error of almost 1 km in 5 km is not 1 or 3%.
[Amazfit] Gosmo:
I just did a test with my Stratos, latest firmware version. I set it to Outdoor Cycling and moved around with my car, for exactly 6.7km on car's odometer, keeping the watch on the front left side window. At the end, I had on Stratos 6.64km trip, that means 60m difference, that means less then 1%, in my situation.

1. Of course, the car has it's standard wheels, so there are no wrong measurements.

2. I had no other devices that I can compare with, except my phone, which I'm sure it's not the most accurate device

3. yes, the GPS doesn't show me on the road all the time, so this is a minus if you are running or hiking where are no roads

4. still, I can say I'm satisfied with it, because I'm not a professional runner.

5. I have the watch since 3 weeks, I updated to the latest firmware and full reset after

6. I had until now just a small battery issue, but it was a faulty watch face
[Amazfit] Gosmo:
Did the same test going back home, this time having also the Strava started on my old Note4 phone, placed on the dashboard and the Stratos on the same left window position:

1. Car's odometer - 6.6km

2. Strava on Note4 - 6.58km

3. Stratos - 6.55km
[Amazfit] cumbrianrunner:
That is very acceptable performance - any slight differences are probably down to the accuracy of the first fix.

I find distance is usually OK and always repeatable over multiple runs- often the map will show me running off a road (through houses!) or path rather than on it, but the distance I find is OK, I have a route I do along a river path, and Fitbit Surge, Garmin Fenix 5 Plus, Strava app and Stratos all report this run 3.4 miles - too be honest I do not really look at distance past the first decimal place, I don't think its important.
[Amazfit] jbod403:
Bad GPS map

I am having an ongoing issue with bad GPS map data. For example, today I ran 4 miles on a known route. The Stratos watch shows 4 miles, the Amazfit App shows my 4 mile spilts, but when you look at the actual map it shows my endpoint about a mile short of where I actually stopped. When the run syncs with Strava, the distance shows as 2.9 miles. Has anyone else experienced this?
[Amazfit] Archenan:
yes, me too, check this thread

https://xdaforums.com/smartwatch/amazfit/amazfit-stratos-finish-problem-t3911792

Right in these days I'm having an exchange of emails with amazfit support for this problem.
[Amazfit] jbod403:
Thank you! I too have a message into support but have not yet received a response.
[Amazfit] redlee007:
Unfortunately, I have the same experience. The Stratos is cca -4% off. On a 8k run it shows 300 or 400 meters less than Garmin Foreruner (I have teste multiple times). As I have read this thread, it appears that this inaccuracy is ongoing since 2017.... so not sure if it is a software issue and if it will ever get resolved. I may have to return the watch, since with this inaccuracy it is useless.
[Amazfit] RaVek:
I also have problems with gps. For the first 12 seconds of the run, it does not count the distance.

Suggestion for others, you have problems with gps, please write here: https://support.amazfit.com/hc/en-us/requests/new
[Amazfit] lfom:
Latest firmwares for all watches (Pace/Stratos/Verge) introduced "Activity reminders" (also called Sports reminders on Verge) that are supposed to auto-start and auto-stop recording activities, but they have a bug (besides the fact that I don't think they actually work as of now): even if both are disabled by default you must enable and then disable both options in watch Settings -> General or your activity most probably will miss the first initial and final minutes of GPS data. Simply enable both, quit settings then go back and disable them again and it should be fine.
[Amazfit] jcms69:
[/COLOR]

This. I went for a run and I noticed that it took the watch about to 5 seconds to show the dashboard after clicking on the start button, and then it took another 10-15 seconds to start counting distance (but the time was ticking from the beginning). As a result, the pace is completely wrong due to the missing distance.

However, when the track is transferred to strava, some of the initial lost meters are more or less recovered, and the pace and distance are different than the summary shown by the watch.

I really hope they fix this. This issue is really annoying because the average pace shown by the watch is wrong by several seconds while you are running.
[Amazfit] diegojama:
I am reading this forum for a few months, and then I decided to buy a stratos. In addition to this watch, I also have a Garmin Forerunner 35, my wife has a Forerunner 25, and I have a Tomtom Runner as well. I decided to do several tests using the 4 devices and I can say that amazfit stratos has the accuracy of gps completely similar to the analyzed garmins and tomtom runner. I did at least 10 different tests using all these devices and I can say that the marking at the end of a 5 km run had a divergence of only 10 to 20 meters, which for me is excellent. sometimes the stratos marked 10 meters more, sometimes the forerunner or tomtom also missed. One observation is that I ran several miles in places that I know the exact distance marking, and the watches behaved really well. I am using the latest stratos firmware and did the tests this month of September and October, in several different places with the known partial and final distance and everything went very well. As the forerunner 35 also has heart rate measurement, I was able to compare both and realized that they are very close to running, with no differences over 5 or 10 bpm maximum between the two devices. so I concluded that it would be better for me to keep stratos with me as it is more complete, I am already arranging to sell my garmin 35 from tomtom runner and I will only have the same stratos, in my use it is perfect for open sky runnings.

---------- Post added at 06:51 PM ---------- Previous post was at 06:42 PM ----------

complementing the post above....

would like to add that all the data was uploaded to strava and that in the app everything was fine with me, the pace and the distance and the uptime, besides the heart rate. so, in my case, everything worked very well and I am really pleased with the results. I'm in Brazil and I ran in open places, roads through trees and also with a few buildings around and everything worked very well
[Sony Xperia M4 Aqua] mic1986:
Hi.

I'm fighting for some time with the Sony E2303 (Xperia M4 Aqua) where the manufacturer has applied (horror of horrors!) only 8GB of memory...

Unfortunately for the user is available less than 2GB which is absurd nowadays!

I tried to use Adaptive storage on my micro sd card but 1) apps run very slowly (facebook) and 2) few apps can be moved like this.

To get each MB of memory I reflect on the performance of the root to remove the software preinstalled by Sony. It is not even branded to the operator because the soft installed is Central Europe.

It's about removing applications that do not use, and which occupy a lot of space (the effect of AR, spotify, playstation, etc). Root would allow me I think to uninstall such software.

However, after uninstalling the applications I would go back to the situation before the root account by doing unroot.

I think the root of this model is mainly based on the change the recovery. Is it possible to return to the stock recovery without full flashing?

Thanks in advance,

BR, Michael.
[Sony Xperia M4 Aqua] r.itvik:
No, I am afraid that's not possible. There's no way to do it without having to flash the firmware. However, try using the Xperia Companoin or move to sd card feature to make a backup.
[Sony Xperia M4 Aqua] srdjanLeo:
You can unroot by flashing stock boot.img, but TWRP will stay there. So you would only lose SuperSU.

And if u use Sony Companion, make sure to relock bootloader before repairing software or you may brick your device.
[Sony Xperia M4 Aqua] mic1986:
Hello.

Can anybody will help me to unlock the bootloader?

I have the possibility to do this:

but when I try to do this by fastboot then the command is not executed:

I tried on three different machines with Windows 10/Windows 7 and MacOS without success. Always is the same.

I'll be very graceful for help.

BR, Michael.
[Sony Xperia M4 Aqua] r.itvik:
Under Settings> Developer Options> Enable OEM Bootloader Unlocking and

then see the guide at https://developer.sonymobile.com/unlockbootloader/
[Sony Xperia M4 Aqua] mic1986:
Hi.

Thanks for interest.

This option is ON as debugging USB.

I tried with the manual from Sony but still I can't execute this command :(
[Sony Xperia M4 Aqua] mic1986:
Case solved.

I reflash the phone using flashtool and Central Europe 1 firmware.

After that I could execute the command oem unlock but only without "-i 0x0fce".

All done.

Thanks.