I'm curious as to what kind of GPS accuracy are you getting on your Nexus S. Please let me know what's the average and best accuracy you're getting.
I'm getting around 30-50m accuracy while in my house. My Nexus One on the other hand (placed side-by-side with my Nexus S) gets around 3m accuracy!
The best accuracy I had on my Nexus S is 10m, and it doesn't stay at 10m for long.
My Nexus One also locks on much quicker than the Nexus S. The Nexus S usually takes up to 1 minute for it to lock on, sometimes it takes like 10-20 secs if I'm lucky. The Nexus One only needs a few seconds to get a lock
How did you check that?
Well, I used my NS with Sygic Aura this morning, just for testing.
And it worked well
GPS fixed in seconds!
I used an app called GPS Status & Toolbox to check the accuracy
i m asking how long the device take to detect the gps signal ??
i remember some say 10 seconds "thats good " others say abou 30 sec to one minute ??? "thats bad"
give ur experience
xdafun4all said:
i m asking how long the device take to detect the gps signal ??
i remember some say 10 seconds "thats good " others say abou 30 sec to one minute ??? "thats bad"
give ur experience
Click to expand...
Click to collapse
Usually less than 10 seconds on mines.
Sent from my HTC Sensation 4G using XDA Premium App
I get a lock within 20 meters of where I am within 5 seconds.
I get a 20 meter range instantly and that generally cleans up to 4m within another 20 seconds or so...
5min sometimes for me outdoors on 3rd ave in nyc..................................
13m lock in 5 seconds
indoors usually around 30 seconds to a minute.
outside, pretty much instant.
same here, 30sec to a min when indoors... outdoor less than 5 sec for initial lock and then refines to 4-10m in 10 secs.
Normally locks are within 10 secs, with good accuracy.
Sometimes it either won't see sats or sees them but won't lock for long enough that I give up. I end up using GPS Test and clear the A-GPS data, and that fixes it. Seems like the ephemeris gets corrupted sometimes and clearing it resets things.
Overall it's a huge improvement over my Vibrant, so not complaining so far.
I'm looking to buy this watch but one of the key factors for me is using it as a standalone for running.
I'm not too concerned with HR or having a map for the exact route I ran but it is crucial that the distance is pretty accurate and therefore my pace per km is accurate. Is the Gear 3 able to deliver on that front? Also does S Health have the feature where a voice-over will alert you at each completed km and update you with your pace for that km and overall average pace per km?
I've tested the LTE Frontier version against a Garmin Vivoactive on a 5 and 4 mile run, so far. Both runs were within .03 of a mile difference. I did have it tethered to my phone because AT&T hadn't gotten NumberSync worked out yet. I'm not sure if the watch refers to the phone during workout while tethered, but now that NumberSync is straightened out, I'll test it again this weekend.
A few things I've discovered:
- It seems to begin recording before the GPS has locked. To work around it, I paused it as soon as it started and gave it a few moments to lock on. This worked but it's little things like this that Samsung should address if it wants to be taken a little more seriously in the fitness world.
- I don't use always-on display so it takes a second or two for the distance display to catch up to the current number. It's usually no more than .05 off for that couple of seconds.
-I don't do interval notifications and I track miles instead of km, but there are options for "Guide at interval every..." .5 mile, 1 mile, 5 miles, 5 minutes, 10 minutes, 30 minutes, hour.
- The heart rate max has been way off but the average is fairly close. I kept it strapped pretty tight during runs. It's convenient but I'd prefer they allow connecting to chest straps, etc. Wrist based HR is tough to do right.
- Heart rate is not imported into Strava when S Health has been set to automatically import. You can manually export the data but I haven't tried that, yet.
- Many of the activities in the phone version of S Health are missing on the watch. Skiing is a big omission in my opinion and seems like a no-brainer with onboard barometer\altimeter.
- For a short time the display would not turn off after starting a run. It eventually did. Also, it has gotten "confused' several times with auto-brightness level but rights itself after the display has turned off and back on again.
Techradar's 50k run review on YouTube was helpful in deciding. I can't post links, yet, but search: "Samsung Gear S3 vs Apple Watch 2 vs Garmin Forerunner 735XT: Battery and GPS 50k test"
tracycm55 said:
I've tested the LTE Frontier version against a Garmin Vivoactive on a 5 and 4 mile run, so far. Both runs were within .03 of a mile difference. I did have it tethered to my phone because AT&T hadn't gotten NumberSync worked out yet. I'm not sure if the watch refers to the phone during workout while tethered, but now that NumberSync is straightened out, I'll test it again this weekend.
A few things I've discovered:
- It seems to begin recording before the GPS has locked. To work around it, I paused it as soon as it started and gave it a few moments to lock on. This worked but it's little things like this that Samsung should address if it wants to be taken a little more seriously in the fitness world.
- I don't use always-on display so it takes a second or two for the distance display to catch up to the current number. It's usually no more than .05 off for that couple of seconds.
-I don't do interval notifications and I track miles instead of km, but there are options for "Guide at interval every..." .5 mile, 1 mile, 5 miles, 5 minutes, 10 minutes, 30 minutes, hour.
- The heart rate max has been way off but the average is fairly close. I kept it strapped pretty tight during runs. It's convenient but I'd prefer they allow connecting to chest straps, etc. Wrist based HR is tough to do right.
- Heart rate is not imported into Strava when S Health has been set to automatically import. You can manually export the data but I haven't tried that, yet.
- Many of the activities in the phone version of S Health are missing on the watch. Skiing is a big omission in my opinion and seems like a no-brainer with onboard barometer\altimeter.
- For a short time the display would not turn off after starting a run. It eventually did. Also, it has gotten "confused' several times with auto-brightness level but rights itself after the display has turned off and back on again.
Techradar's 50k run review on YouTube was helpful in deciding. I can't post links, yet, but search: "Samsung Gear S3 vs Apple Watch 2 vs Garmin Forerunner 735XT: Battery and GPS 50k test"
Click to expand...
Click to collapse
Thanks a lot for the response, will check out the YouTube video. If you did get round to testing the watching as a standalone this weekend, can you let me know how well it worked?
4 mile run with the Gear S3 on LTE (Not connected to a phone), Garmin VivoActive with Scosche Rhythm+ HRM, and Galaxy S7 Active
- The final average pace between all 3 devices was within 10 seconds of each other. The VivoActive was in the middle and the Gear S3 was 5 seconds more and the S7 Active was 5 seconds less.
- Throughout the run, the Gear S3 always read the pace at 1 to 2 minutes more than the Garmin. But, the final results of the Gear S3 basically matched the Garmin so I'm not sure what is going on there because it was displaying a pretty big incorrect pace.
- For the first 5 minutes of the run, the heart rate on the Gear S3 read a consistent 40 bpm less than the Garmin with the Scosche Rhythm+ hrm. After that 5 minutes, it was never more than 2 or 3 bpm different from the Garmin. Looking at the S Health app, I'm not seeing those consistently low numbers for that 5 minutes. While S Health shows an incorrect hr for only a couple of minutes, the watch was definitely showing an incorrect hr for a full 5 minutes. The final average is very close to the Garmin, though.
Gear S3 Garmin VivoActive (Scosche Rhythm+ HRM) Galaxy S7 Active (Strava)
Start Bat % 99% 100% -
End Bat % 89% 88% -
Distance 3.98 mi 4.03 mi 4.0 mi
Avg hr 147 bpm 150 bpm -
Max hr 165 bpm 165 bpm -
Avg Cadence 83 spm ??? 160 spm ???
Max Cadence 167 spm 168 spm
I hope someone can shed some light on the below.
I use the Gear S3 Gps and s health app to track my runs however i am realising that the GPS is not at all accurate. I ran a 21 km half marathon the other day and the Gear S3 said that i had run 26 km. I understand maune being out a couple of hundred meters but 5 km seems to much. Any nody experienced the same issues and is there a fix. My wife has a series 3 iwatch and she ran the same distance and it measures within 20m of the race length
Hi
Is there any app or method to get better gps signal in our Huawei Watch 2? I use it with a sim card but it takes a lot of time to take a good signal (5 minutes more or less) and with no obstacles.
Thank you