Related
Hello,
my gps has no right position i think the difference is between 25 to 50 m
Is there a tool to correct this issue ?
Thx
Nochmal in deutsch falls mein Englisch nicht so gut zu verstehen ist
Mein GPS im Artemis hinkt etwa 25 bis 50 m hinterher was sehr nervig ist
Kennt jemand dieses Problem und weiß wie man Abhilfe schafft ?
From what I recall no civilian GPS is precisely correct.
Only Military GPS is precise to the metre.
Not sure what the exact varience is though.
Regards
i have navigation systems before the p3300 and on all when the street cross comes it brings exactly the position when it says turn left at 50m then it was correct, i believe the military difference is only 1m or lower not 50m ???
For external PC gps receiver there is a software for correct some options for the inbuild gps.
I have no glue for a in built gps.
Sorry for the English this not my normal language, i hope you can understand what i mean thanks
Also, better accuracy depends on the number of satellite signals the device can get. Signal strength is weaker in the urban areas.
What software application are you using when you notice the discrepancy? I have found my Artemis GPS position to be equal to some of my other units. For example using a topographical map when out walking the unit is very good, certainly not 25 to 50 M out. It could be low signal strength and reflections off other building that is causing a problem (if in built up area)
One other consideration, how many other applications do you have running at the same time as your Nav software, your device might be struggling under load, check settings/ system tab Memory icon/ running programs and stop all before trying the nav software Mike
My device, which is still the Magician is running the ROM 1.13 with BS. Additional software which are all installed in the Storage are; Pocket Informant, Photo Contacts Pro, Resco Suit, SK Tools, TT6, WorldMate Pro, Ring tones. All TT maps (WEU, USA+Canada), voices, schemes, zip codes, POIs and IE Temporaty files are installed in a 2GB SD. What's left in available memory are Storage = 0.7 of 26.72 MB, Storage Card = 105 MB of 1935GB.
The programs that are running (being memory resident) while TT6 is active are Photo Contacts Pro and Pocket Informant. I have BT on all the time since I use a BT headset for calls while driving. TT audio is via my Seidio active car holder.
The programm ist TT6 and only jetware, and ilauncher active nothing more, the area is no big city good sight to the air.
I checkt this with tt5 and a hp2210 with bluetooth sirfIII this combination is near perfect
I've never used those programs. The inaccuracy might come from any of the two.
Civilian GPS is officially (from the provider of the GPS System - US Forces) something about 10 metres unexact. Of course this number can be smaller if you have more satelites "in sight" However, GPS Navigation Programs do not need accurate positions, they calculate the position on the map with old data and then extrapolate it, showing the dot where you should be now, according to your speed and heading 1 second or two seconds ago. Of course it can control its calculation because more data streams in. It is funny to see Navigationsoftware Confused, when you ride a train. It gets a signal in a certain direction, with a certain speed, so it puts the dot on the street next to the Rails, because this is the only logical position where your car can be so it says "turn left now" but the train goes straight. Then it searches another street you could be on. just funny
But in short: GPS Software compensates missing GPS accuracy, mostly well, sometimes not so good. Try using another Software or newer map ,maybe that will fix the problem. On my MDA Compact III The Built in Receiver works just great together with TT6. Maybe there is a way to shorten the interval between two data sets. That would give the Software more information, resulting in a more accurate position. But i don't know if a program like GPS Maus can manipulate Built-In receivers that easy.
I once reprogrammed a T-Mobile Receiver with this program, so it received also NMEA data and the intervall between two data sets could be set randomly.
In the UK, the BBC send out a spoiling signal which reduces the accuracy of the GPS. It is also sent out from National stations in other Countries. I heard it was sent out with the atomic clock signal. This is to stop "undesirables" buying civilian GPS units and fitting them to military equipment and sending something directly to your letterbox - the same way a US military GPS unit can if they want to! You used to be able to buy a box that would correct the error signal, but that got stopped ages ago.
The GPS also becomes slightly more inaccurate depending on the speed you are travelling, travel under 30 mph / 50 kph and the "you have arrived" will be within a few yards/metres of the real arrival point. Travel at 70 mph / 120 kph and the "take the exit in 200 metres" is very inaccurate - maybe by a couple of hundred metres - you can work out why!
Also GPS signals are "secondary" and can be turned off at any time in the event of a military requirement - which is why you can use the signals free of charge.
Jeff
jthspace said:
In the UK, the BBC send out a spoiling signal which reduces the accuracy of the GPS. It is also sent out from National stations in other Countries. I heard it was sent out with the atomic clock signal.
Click to expand...
Click to collapse
Where did you get this gem of knowledge from?
jthspace said:
This is to stop "undesirables" buying civilian GPS units and fitting them to military equipment and sending something directly to your letterbox - the same way a US military GPS unit can if they want to! You used to be able to buy a box that would correct the error signal, but that got stopped ages ago.
Click to expand...
Click to collapse
Are you confusing the selective availability that was used to degrade the GPS accuracy up to a few years ago? - The US reserve the right to switch it back on again should they need to, but under normal conditions the signal is not de-graded any longer. If you want to send something to a letterbox the Post Office offer quite a good service
jthspace said:
The GPS also becomes slightly more inaccurate depending on the speed you are travelling, travel under 30 mph / 50 kph and the "you have arrived" will be within a few yards/metres of the real arrival point. Travel at 70 mph / 120 kph and the "take the exit in 200 metres" is very inaccurate - maybe by a couple of hundred metres - you can work out why!
Click to expand...
Click to collapse
The issue of position inaccuracy relative to speed won't give a major difference to position - the software maybe responsible for the apparent degradation though.
jthspace said:
Also GPS signals are "secondary" and can be turned off at any time in the event of a military requirement - which is why you can use the signals free of charge.
Click to expand...
Click to collapse
As I mentioned before the US reserve the right to turn on the Selective availability (positional accuracy degradation), if they turn it off their own planes and other civ/ mil products would be useless - Mike
mikealder said:
Where did you get this gem of knowledge from?
Click to expand...
Click to collapse
When I worked on the original GPS launches a while back
Jeff
Static Navigation in Artemis
In Artemis is a Sirf-III-Chipset. One of the "features" of this chipset is a Parameter called "Static navigation".
This gives a more or less "static" position if the device is moving rather slow, like a pedestrian does.
Useful for car navigation because your car is not "dancing in front of the traffic light".
But it gives a more or less not accurate position when standing or moving rather slow. You need to move with 5 Km/h at least.
No tool for switching off "Static Navigation" in Artemis seems to be working.
BBC jamming the gps signal..?
Selective Availability:
"SA works, for the most part, by intentionally dithering the clocks in the 24 satellites that make up the GPS system. The clocks are steered by an algorithm, known to the control station and military receivers and transmitted in encrypted code over the satellite signals."
http://www.exn.ca/FlightDeck/News/story.cfm?ID=20000502-53
The BBC does what??? I don't believe that for a moment!
The GPS signal I get on my Orbit and previously on my Fortuna Clipon has been extremely accurate, using different software Tomtom 5 & 6, pocket streets and Vito all have been down to a couple of meters at most.
I have also used in the US, Cyprus and Spain all with the same accurate results.
Yes the US can turn off civilian GPS if they wish, which is why the EU is building Galileo.
duh... SA has been switch off 7 years ago!
interesting to see people still talking about SA, it has been switch off since year 2000!
http://www.ngs.noaa.gov/FGCS/info/sans_SA/
According to Google Maps 4.0 my gps is never accurate within more than 20-30 meters. usually when im driving i am on the wrong side of the road or in a ditch somewhere.
on my girlfriend's droid her accuracy is about 1-3 meters at best and is never any greater than 10 m.
same goes for my friends blackberry storm...about 5 meters.
So i am wondering if you guys are having better accuracy with the phone.
is it a hardware or software issue? and any idea on how to make this better??
Thankss
No my gps is very accurate. It could be due to the radio version you are using. You didn't mention witch version you use, but try some different radio's and see if you get a better gps signal.
HD2 GPS is a joke!
My HD2 GPS is very, very lousy - when I record my path (on feet) with e.g. RunGps or NaviCompiter, I am getting an ugly zig-zag line with position errors of 20-40 meters! (In city or in open field - does not matter). Unbelievable P.o.S! My radio is now 2.09.51, was 2.07.51 - same s..t.
My old Samsung i780 draws very smooth line with errors within 1 meter, seriously.
HD2 GPS works with Tomtom though, sometimes turning map around when pausing at a crosing or recalculating, but generally OK.
Unless one is seriously geocacheing or needs absolute precision, I regard 20 meters to be fairly decent, 10m to be fantastic when using google maps. But then again I use GPS and map software as a guide not an absolute... I've always taken the stand that map software doesn't know everything about a location, nor does it know the best way to get there.
I do agree the gps accuracy is dependent on the radio though and some are better than others at getting a good signal
My TP2 accuracy is very good. As good as my Garmin handheld GPS I use for geocaching. I went for a jog the day before yesterday, and tracked my progress with SportyPal (http://sportypal.com) and when mapping my route on Google Maps my position was good to within 3 meters (and usually significantly better). I ran up and down some bleachers and it showed my proper position right up and down the isles.
I've also used it for geocaching, and it usually brings me to within spitting distance of the cache.
The reception is also better than any other GPS I've used. It will usually pick up my position in my office, which is half way underground with an entire second story above me.
So is the GPS receiver on the Touch Pro 2/Tilt 2 better than what is used on the Touch Pro/Fuze? I assumed it was probably the same since most everything else (hardware) is the same. Although you would think that HTC would have fixed it after all of the complaints with the Fuze.
I'm thinking of upgrading from the Fuze, but so far the only advantage is the screen. If the GPS has been improved, that will make a difference.
Hello, for about 2 weeks my gps has been working and has been taking a little bit longer than normal to lock. but thats not the problem.
the problem is when it does lock the position will be off by 1/4th mi to about 3 miles and its usually connected to 8 or 9 sats and says position within 10-20 meters
im not very good with the metric system but im pretty sure that 20 meters does not equal 3 miles and the little blue circle is not that big
and keep in mind this is outside clear weather and no big buildings around
i was wondering because i heard that there will be no more funding for the gps sats and would slowly start failing because they wont get the upgrades they need and also i heard about a month ago that there will be some big solar flares that could mess up the sats
another thing is using gps test. is showing that the sats that are connected are lower signal than they usually are. mostly in the yellow. but i see no reason for that...
this only started happening for about a week or 2.
anyone else having this problem? can a radio update fix this? if so which would be the best one for t mobile usa (link if you can)
Radio ver: 4.49.25.57
thanks for your support,
Darian
turn off your agps, as it uses cell tower signals to locate you, and can over ride the gps signal you are getting. the agps is triangulating your position and is generally only accurate to 300 to 1300 meters.
i thought agps was only used to get a faster lock on the sats
Hi all,
I got an used Galaxy Nexus (unrooted, stock everything) a few months ago, with plans to use it as an outdoor gps for hiking, biking and maybe paragliding (so I wanted a barometer in it).
I live in Florida (that as you may know is all very flat... maximum altitude is about 100 meters above sea level), and I was very pleased with it (the phone, not the flatness of Florida!) until I took a trip to Colombia in December. There, I had two "bad" experiences with the Google Nexus GPS:
- I took a hike that brought me to an altitude of about 4800 m. Around an altitude of 4000 m (the last recorded point is 3992 m), the GPS lost fix and would not get it again, although GPS Status would show plenty of satellites (9 or 10) all green (that according to GPS Status help means "satellite is used while determining the location"). After rebooting and starting GPS status (but I've tried other programs too, in case you wonder) the GPS will display that it had a fix for just a second or less (coordinates would appear in the GPS Status screen, and one single point woudl be recorded, with aan altitude of 4400 m although I was probably at 4800 m) and then loose it again, never to be reacquired.
- On my flight back, I tried to record the flight. I got a fix while just before takeoff and maintained it until... 3995 m! Then, fix was lost, again never to be reacquired again (actually, I did try again when the plane was at about 1000 m, and I was able to get a fix and record the landing with no problems)
Now, for someone that likes mountaineering, 4000m is a pretty low limit! I really don't care about recording commercial flights, it's just for fun, but a GPS that stops working above 4000m while you are hiking in the mountains could mean trouble.
I've searched around the internet (including this post on XDA), but I haven't find anyone complaining about this issue at this level. Many people complain/discuss about ITAR limits, but those are much higher than what I experienced.
So, I'm wondering if is it a problem with my unit, a problem with the Galaxy Nexus, or just a coincidence? Anyone had a similar experience?
BTW, I had an T-Mobile G-2 (HTC) that worked very well both for flights and mountaineering.
Giacomo
That would explain why the gnex won't get a fix while at cruising altitude..
Beamed from my iPad Mini
Hi,
I had the same issue with my galaxy SII i9100g.
I had a mountain climbing with a summit of 4500 meters, in the beginning we really didn't need gps tracking because there was signs showing the track in the mountain. I checked the device and everything was fine the first day the signals were ok and I had my position on the phone. but in the second day when it got foggy we were in trouble as I wanted to know our altitude. and gps signals wouldn't fix. I had ten or so satellites in view but the message said "waiting for gps fix" and it didn't fix at all. I also restarted the device but it wouldn't help.
in another trip on a plane I started recording the route with gps, and I noticed last recorded point was at an altitude of 3985 meters. and when the plane reached higher altitudes i lost the fix.
I think they should give us warning about using such devices in hiking trips. it could make real trouble for me.
It might be a problem specific to the GPS receiver used in Google Nexus. Giving that I've noticed GPS late fix problems with my Nexus (compared to a Galaxy S3), I'll try checking out the internet myself too.
Have a good day!
I find it remarkable that high-tech companies such as Google or Samsung keep managing to put in design flaws or outright defects that can easily kill people. The one described here is an outstanding example. If using the GPS with good success while hiking, nobody in his right mind would ever get the idea that the GPS would suddenly stop working above a certain altitude. So some programmer has intentionally put in a deadly trap (unless you want to believe that a command like "if (altitude >= 4000) return null;" can be written inadvertently). This is sabotage of a very dangerous kind.
Another less obvious example is the design of the power button, which can easily be activated inadvertently. If somebody needs the phone to navigate and survive in the wilderness and decides to power the device down until the next critical point to keep the battery charged for a long time, the device can easily lose all power just because of an inadvertent power push in a bag or pocket. The obvious solution here is a recessed power button or, in a cinch, that the device automatically powers down again if no user action happens within reasonable time after power-up.
The rule is generally that the design is stupid, the defect is obvious, at least one solution is also obvious, and even when the flaw or defect is brought to their attention, it is not fixed. Dangerous idiots at work. Perhaps they reckon if somebody actually dies, it will be impossible to prove that the smartphone design defect was a contributing factor. It is the responsibility level of a school child.
I am sure there are more examples for this behavior.
I am not saying that people should hang their lives on their smartphones. If the smartphone is the only thing that keeps you alive, then you have already made a planning mistake. But we all know that one can get into situations inadvertently where several things go wrong in unlikely ways. In such a case you can get into a situation where your life depends on the GPS in your smartphone, and then either of the defects described above could conceivably seal your death.
My screenshot from the plain
Sent from my Nexus 5 using XDA Free mobile app
giacomociani said:
Hi all,
I got an used Galaxy Nexus (unrooted, stock everything) a few months ago, with plans to use it as an outdoor gps for hiking, biking and maybe paragliding (so I wanted a barometer in it).
I live in Florida (that as you may know is all very flat... maximum altitude is about 100 meters above sea level), and I was very pleased with it (the phone, not the flatness of Florida!) until I took a trip to Colombia in December. There, I had two "bad" experiences with the Google Nexus GPS:
- I took a hike that brought me to an altitude of about 4800 m. Around an altitude of 4000 m (the last recorded point is 3992 m), the GPS lost fix and would not get it again, although GPS Status would show plenty of satellites (9 or 10) all green (that according to GPS Status help means "satellite is used while determining the location"). After rebooting and starting GPS status (but I've tried other programs too, in case you wonder) the GPS will display that it had a fix for just a second or less (coordinates would appear in the GPS Status screen, and one single point woudl be recorded, with aan altitude of 4400 m although I was probably at 4800 m) and then loose it again, never to be reacquired.
- On my flight back, I tried to record the flight. I got a fix while just before takeoff and maintained it until... 3995 m! Then, fix was lost, again never to be reacquired again (actually, I did try again when the plane was at about 1000 m, and I was able to get a fix and record the landing with no problems)
Now, for someone that likes mountaineering, 4000m is a pretty low limit! I really don't care about recording commercial flights, it's just for fun, but a GPS that stops working above 4000m while you are hiking in the mountains could mean trouble.
I've searched around the internet (including this post on XDA), but I haven't find anyone complaining about this issue at this level. Many people complain/discuss about ITAR limits, but those are much higher than what I experienced.
So, I'm wondering if is it a problem with my unit, a problem with the Galaxy Nexus, or just a coincidence? Anyone had a similar experience?
BTW, I had an T-Mobile G-2 (HTC) that worked very well both for flights and mountaineering.
Giacomo
Click to expand...
Click to collapse
Which model is you GN?
Sent from my Galaxy Nexus
Jar3112 said:
Which model is you GN?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
It's a Samsung Galaxy Nexus I9250.
I should also mentioned that in the meanwhile I have found on various forums a (very limited) number of users reporting the same problem with the same phone, but no one reporting that it works for him. So I start to be confident that it is a problem of this particular model...
Hi people,
I have recently bought a Galaxy Tab 3 7.0, brazilian version T211M with 3G and digital TV.
The idea was to use it as an in-car multimedia and GPS device using Waze. I made some tests using my Nexus 7 2013 for this purpose, and it worked flawlessly. So I bought the GTab 3 to be a dedicated tablet for this.
The thing is: the GTab 3 GPS is nowhere near the Nexus 7 GPS performance. My N7 is able to find three or more GPS satellites and lock position in a couple minutes inside my car's garage (which, BTW, is not underground, it's the building's third floor). And without A-GPS (it doesn't have 3G connection, it's the wifi version). In the same situation, the GTab 3 keeps looking, looking... and nothing. Yesterday I went out driving, and it took 15 minutes for the GTab 3 to finally lock GPS position.
Another funny thing that happens is when I stop, for example, in a traffic signal. The GTab 3 GPS gets confused somehow, it's not sure if I'm moving or if I'm stopped. Its speedometer marks 0 km/h, then 2 km/h, sometimes even 10 km/h, then 0 km/h again, the speed keeps going a little bit up, then down. Again, different from my N7, which was very precise.
As a last test, I put both tablets in my place (I live on the 9th floor), over my sofa, right beside a window and a door to the balcony. Using GPS Status (you can get it from Google Play), I tried to find GPS satellites and lock position. The N7 could do it in a couple minutes. The GTab 3 couldn't do it. I had to go outside to the balcony, stood in its end, and then finally the GTab 3 got a GPS lock. But when I go back inside, it loses the GPS signal.
I'm very disappointed about GTab 3 GPS performance, it really ruined my car tablet experience. But before I sell it and lose some money, I have to ask: is there a way to improve it's GPS performance, so that those issues are gone? Or that's the way it is, and I can't do anything about it?
I recently bought one too, haven't tested the gps yet, but comparing with my Note 3 with AGPS, it´s surely much worse.
This post talks about a gps bug?: http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=138317