ok i know mini stumbler doesn't work since it hasn't been updated back in 2004.
i do alot of network readings for work. mainly net stumbler for the regular SNR readings not the snr+.
is there a program that i could use on my AT&T tilt to get SNR readings?
i would like to walk around with my phone then my laptop getting readings.
Apologies if you know this already, but WiFiFoFum can observe (& record to a file if reqd.) the RSSI - can you figure out the signal2noise ratio with that figure?
SilentlyScreaming said:
Apologies if you know this already, but WiFiFoFum can observe (& record to a file if reqd.) the RSSI - can you figure out the signal2noise ratio with that figure?
Click to expand...
Click to collapse
i like to just to do a quick look and record the SNR. I install wireless AP's in hotels and i have to test the signal in every room.
or what would be the quickest way to figure out the SNR with the RSSI?
It appears that the calculation may depend on the WiFi chip manufacturer.
Because the RSSI detector is a nonlinear detector, it changes the Signal to Noise Ratio (SNR) of the signal that goes into it. The key to the ASK sensitivity calculation is the SNRout vs SNRin curve of the RSSI detector.
Once we know the SNRout vs SNRin relationship, the steps to finding the ASK sensitivity for a given Noise Figure, IF Bandwidth, and Data Rate are given below.
1. Determine the Eb/No needed for a target BER (10-3 in this example) then calculate the SNR from the Eb/No by using
SNR = (Eb/No) * (R/BBW)
Where R is the data rate and BBW is the Data Filter bandwidth.
2. Reduce the SNR calculated from the previous step by the ratio in dB of the IF (pre-detection) BW to the Data Filter BW. For instance, a 600 kHz IF BW and 6 kHz Data Filter BW means a 20 dB reduction in the SNR. This is the SNR of the signal coming out of the RSSI detector before the Data Filter gets rid of the high frequency noise (assumed to occupy the IF BW). At sensitivity, this ratio is usually negative in dB.
3. Use the RSSI SNRout vs SNRin curve to find the SNR at the input to the RF or IF Amplifier and RSSI detector. You actually use the curve "backwards" to find SNRin given the SNRout you calculated in Step 2.
4. Use the SNR formula for the front end of a receiver to find the signal level at the receiver input. This is the sensitivity, S.
S = (SNRin) * (kTBIFFS)
Where kT is the noise spectral density at 290 K (-174 dBm/Hz) BIF is the IF (pre-detection) BW, and FS is the system (not just the front-end) noise figure of the receiver.
Because the RSSI detector is a logarithmic detector, the SNR input-output relationship can be expressed in a closed-form expression, albeit a messy one. An old paper published in the IEEE Transactions on Aerospace and Electronic Systems[1] derived the expression and plotted the SNRout vs SNRin curve. The curve in the article is small and doesnft have enough gridlines, but it is possible to evaluate the expression in an Excel spreadsheet and plot it in better detail. The curve appears below, plotted along with a simple SNRout = SNRin curve (linear detection) for comparison. Notice the threshold effect. Below the "crossover point" SNR of 3.7 dB, the SNR gets worse going through the detector. Above this point, it improves.
Click to expand...
Click to collapse
Taken from the 9th post here.
So, going from my brief skim reading, it may not be possible to get the SNR figure from an RSSI figure without a noise value at each point?
Could be wrong, I'm no expert at all, just hoped the program might be of use to you...
thanks for the help.
Hopefully there's a program out there that would work for me.
Shot in the dark, but if MiniStumbler - http://www.netstumbler.com/downloads/ works on a Kaiser, it might have the stats you need.
SilentlyScreaming said:
Shot in the dark, but if MiniStumbler - http://www.netstumbler.com/downloads/ works on a Kaiser, it might have the stats you need.
Click to expand...
Click to collapse
i tried it already, it doesn't detect the Wifi card. Maybe someone here can get mini stumbler to work on the kaiser?
thanks though!
Related
Hi!
I encountered a strange GPS behaviour and wanted to share this with you / maybe someone has an idea bout this one:
On a businessjourney i wanted to log my way with my kaiser, and everything went fine so far. But after several hunderts of kilometres, kaiser lost more and more satellites till only 1 was left and the values were unuseable (phantasy-koordinates, speed and altitude too).
I am 100% sure that it was not a problem with our jet or any kind of shielding in it - because after a softreset it could lock again on 8 to 12 satellites. I could approve this strange loss of statellites on longer flights and car etappes (lets say 500km+) now several times.
Any idea what could be the reason?
Did the airline crew know you were using a gps device?
unwired4 said:
Did the airline crew know you were using a gps device?
Click to expand...
Click to collapse
Who cares, GPS device is just a receiver, they use several of them in cockpit. Even GSM mobile phone intereference is exaggerated...
Well, since it was our own jet and pilot i guess that its ok
But back to the issue: A friend of mine could acknowledge that he has the same problem when traveling over a certain distance by car.
Is it possible, that this has something to do with QuickGPS where the receiver calculates extimated postitions of the satellites (and those triangulations will be false when moving too far)? Is QuickGPS postition-dependend?
Any ideas highly appreciated...
licht77 said:
Well, since it was our own jet and pilot i guess that its ok
Click to expand...
Click to collapse
Good answer
It could be, but quickgps only provides a pre-download of the ephemeris data so that the GPS unit does not have to download it from the satellites. If it does not have the quickgps data, it could download it from the sats (thats why a normal lock takes so long), so I would guess not, unless maybe download of new data from sats is turned off if quickgps is turned on.
I see no option to specify location in quickgps but then again it could look at the handset's country code or something. Surely though it is kilobytes in size at max so downloading the whole world's data via GSM/3G would be no biggie.
On a side note, I get the same issue on my Kaiser even if I stay local sometimes. I *think* it may be getting stuck on A-GPS (Using cell phone masts to get a rough fix) - maybe try and disable A-GPS as it would be no use in a jet?
I have experienced the same thing once - and that was after using the Kaiser in a jet for only a few minutes. Once I landed, I started TomTom and was placed over 700 miles from my actual position. A soft rest cured it; I was a bit worried that the high speeds of a jet might have confused/fried my GPS, but all was fine after a soft reset.
You may see what I mean here: xxx (username and password: test): Right above Toledo / Madrid the GPS readings go crazy... :-(
Could this be the mythical 'Barcelona Triangle' ?
Interesting, you might try posting this at GPSpassion.com forum. They are the experts in GPS. It's odd that it would loose sats as the view of the sky couldn't be much better and you'd think that it would be able to keep up things, even at jet speeds the number of visible satellites wouldn't change. I would try it with GPS ON and Phone radio OFF as this might rule out any cell tower issues.
RemE said:
Interesting, you might try posting this at GPSpassion.com forum. They are the experts in GPS. It's odd that it would loose sats as the view of the sky couldn't be much better and you'd think that it would be able to keep up things, even at jet speeds the number of visible satellites wouldn't change. I would try it with GPS ON and Phone radio OFF as this might rule out any cell tower issues.
Click to expand...
Click to collapse
Hi! I tried it with GSM off - with no improvement. It seems that this is some kind of bug in the GPS-receiver?
If you have an user in that forum - feel free to post this issue!
Thx, Licht
I do experience this problem too. I was thinking it is the problem of the chip, has anyone tried the external antenna and does the problem still persist?
ZorMi said:
Who cares, GPS device is just a receiver, they use several of them in cockpit. Even GSM mobile phone intereference is exaggerated...
Click to expand...
Click to collapse
Might be exaggerated... but considering how much interference a normal GSM signal has with household electronics (and yes, commercial jetliners are heavily shielded)... it's still kind of scary.
I actually discovered I left my phone on in my bag on a Frontier Airlines flight when the GSM modem started up at around 15,000 feet and the in-seat screen in front of me started flickering and I got that cool 'ch-ch-ch-ch' noise in my headphones.
Whoops.
It's probably safe to have the GPS on, but you really should turn off the radio.. there's no telling what wiring is running next to/under your seat, and there might just be an antenna above your head that you don't know about. It's just not worth the risk (plus, if you get caught.. well.. it's a federal offense).
If you just ask, some pilots will let you turn your GPS unit on in the plane (the flight attendants will ask him/her)... Delta Airlines doesn't seem to have any problem with this, while United and American do.
I think you'll find the answer to this thread is to do with the travelling speed and height.
Dedicated flight GPS units have a much faster baud rate for data transfer and the unit itself has virtually no other background tasks to take care of.
The 'Kaiser' GPS is primarily designed as a 'walkabout' unit and can just cope with vehicle speeds. If the data shows a marked change in position (due to say travelling at a few hundred kph) then the GPS firmware believes it has an erroneous sat lock and tries to re-aquire causing the confused output.
Also, Ephemeris data is incorrect for ionospheric distortion when you are at above 25,000 thousand feet so if it tries to use QuickGPS it will actually lengthen the acquisition time.
Try it next time with both A-GPS and QuickGPS off (QuickGPS auto disables if data is out of date so just disable downloads) and note what speed/height you are when is goes crazy.
As far as i know, there is no profen evidence that one single plane was downed by a gsm signal. Additionally, i have seen Boeings where all TFT Flatscreens started heavy flickering when the intercom was running - so dont mix up important avionic board systems with unimportant, unshielded secondary systems Here in europe all commercial planes have excellent shielding standards - and there are several commerical and private planetypes around which already come up with internal gsm-repeaters and satellite connections to the gsm-groundstations (the reasons for low usage are missing business models and - i guess annoyance). And - as i said - it was our own jet and pilot, and so its me who makes the rules in there :-D
So much for offtopic.
But I really would like to know what causes this "satellite loss" and "mis-positioning" problems... - this probably makes some killerapplications impossible
Does anybody know if a-gps is geographically influenced? Anybody has further informations about how our Kaisers keep the fix on the satellites?
Farsquidge said:
I think you'll find the answer to this thread is to do with the travelling speed and height.
Dedicated flight GPS units have a much faster baud rate for data transfer and the unit itself has virtually no other background tasks to take care of.
The 'Kaiser' GPS is primarily designed as a 'walkabout' unit and can just cope with vehicle speeds. If the data shows a marked change in position (due to say travelling at a few hundred kph) then the GPS firmware believes it has an erroneous sat lock and tries to re-aquire causing the confused output.
Also, Ephemeris data is incorrect for ionospheric distortion when you are at above 25,000 thousand feet so if it tries to use QuickGPS it will actually lengthen the acquisition time.
Try it next time with both A-GPS and QuickGPS off (QuickGPS auto disables if data is out of date so just disable downloads) and note what speed/height you are when is goes crazy.
Click to expand...
Click to collapse
Thx for your informations - your ideas sound plausible! But on the flight i posted before, u can see that we were travelling about 2.5 hours at 10.000 metres and 800 km/h before everything went crazy within 60 seconds (Placemark 273 is plausible, 275 insane)... but i turned GSM off to save battery... so a-gps and quick-gps should have been off too (correct me if i am wrong)...?
licht77 said:
Thx for your informations - your ideas sound plausible! But on the flight i posted before, u can see that we were travelling about 2.5 hours at 10.000 metres and 800 km/h before everything went crazy within 60 seconds (Placemark 273 is plausible, 275 insane)... but i turned GSM off to save battery... so a-gps and quick-gps should have been off too (correct me if i am wrong)...?
Click to expand...
Click to collapse
A-GPS would be disabled but QuickGPS would still be active as it is just a downloaded info table.
It would only need loss of signal for a few seconds, say your reception was detuned by a flight manouver or you moved the location of the unit within the plane (signal strength is poor within an aircraft body without external antenna) to cause it to get confused and at speed it takes ages for a lock. You can see a big difference just starting the GPS standing still against starting it in a moving car.
Consumer GPS devices misread at high speeds and altitudes. Government regulations keep them from functioning to prohibit their use in the construction of ICBM's since most devices use a version of a generic GPS chip. Think I'm nuts? Google it.
xconradx said:
Consumer GPS devices misread at high speeds and altitudes. Government regulations keep them from functioning to prohibit their use in the construction of ICBM's since most devices use a version of a generic GPS chip. Think I'm nuts? Google it.
Click to expand...
Click to collapse
Nope, I don't think you are nuts! You are perfectly correct!
There are 3 types, consumer, commercial and military. (four if you count the US who contol the network and have the best).
Farsquidge said:
A-GPS would be disabled but QuickGPS would still be active as it is just a downloaded info table.
It would only need loss of signal for a few seconds, say your reception was detuned by a flight manouver or you moved the location of the unit within the plane (signal strength is poor within an aircraft body without external antenna) to cause it to get confused and at speed it takes ages for a lock. You can see a big difference just starting the GPS standing still against starting it in a moving car.
Click to expand...
Click to collapse
OK I guess i will give this a try as i found out how to deactivate QuickGPS
@xconradx: No youre not nuts - i can confirm that there are regulations (thats why we are gonna send up Gallileo *g*) - but i can hardly believe that this was the bugger: The readings were accurate (too accurate to prevent abuse) for 2:45min - and then the readings were just insane.
I hope we can find a workaround...
Haha, I'm glad people dont think I'm a nutjob... I've tried to explain the regulated GPS to people before and was called "paranoid, crazy", whatever....
Thats weird that it read so well for a period. I just know that basics!
Hello,
In comparing the altitude reading of the internal GPS with two other GPS recievers (one WAAS enabled) and in knowing the true altitude (at several airports), it seems that the At&t Tilt is always reading about 100-120 feet low compared to the other two receivers and the actual altitude. Have any others noticed this?
I have never seen an accurate or high reading, it has been lower than the the other recievers at every location and test that I have done. I upgraded to the new AT&T HTC Rom as soon as I recieved the phone and do not have data before this upgrade.
Thanks,
John
Docj_Aero said:
Hello,
In comparing the altitude reading of the internal GPS with two other GPS recievers (one WAAS enabled) and in knowing the true altitude (at several airports), it seems that the At&t Tilt is always reading about 100-120 feet low compared to the other two receivers and the actual altitude. Have any others noticed this?
I have never seen an accurate or high reading, it has been lower than the the other recievers at every location and test that I have done. I upgraded to the new AT&T HTC Rom as soon as I recieved the phone and do not have data before this upgrade.
Thanks,
John
Click to expand...
Click to collapse
Sorry I only use the GPS for directions, but, what program are you using to get your reading? 100-120 feet of difference seems like a program issue. Tilt GPS should not be that inaccurate. Maybe you could try a different program and see if you get a different result.
I have used many different programs and they all give the same altitude (the same as that contained in the NMEA string). VisualGPS, NoniGPS, GPS Tuner, GPS Utilities, and others all give the same; hence the confusion.
John
Docj_Aero said:
I have used many different programs and they all give the same altitude (the same as that contained in the NMEA string). VisualGPS, NoniGPS, GPS Tuner, GPS Utilities, and others all give the same; hence the confusion.
John
Click to expand...
Click to collapse
I have seen the same results using a myriad of gps software. I dont have a fix either, just confirming your observations.
Has anyone either noticed this error, or can verify that their unit is in fact agreeing with other gps receivers?
I called tech; they were not much help.
I have the same problem.. I fly a powered paraglider, and I want to plot my path on Google Earth. All of the points end up being below ground, unless I am very high in the sky
I have a 8925 stock rom with APIC on it, I have matched the readings on it to a Garmin 430, now keep in mind the antenna on the 8925 does not have the same sensitivity nor size/location as the 430s. I would not shoot a approach with my 8925, though it's readings (GS, ALT, HDG) match up to the 430.
Also does anyone know if the 8925 can be WAAS enabled?
Altitude calculation is an issue with commercial GPS devices. You can read more here http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=10915
not true, aircraft shoot GPS approaches all the time, a cat II approach has a minimum decision height of 200', so if it is common for a WAAS GPS to be that off, planes would be lawn darting left and right.
That said I have noticed that the vertical navigation accuracy of my non-WAAS 8925 improves greatly when it is at altitude (500' + AGL), now if it was WAAS I would be accurate at low altitudes as well at any airports that supports a GPS approach.
From wikipedia:
The elevation display from the internal GPS will be inaccurate due to it using the WGS-84 Datum which can deviate from mean sea level in the range of +85 to -107 meters. The main reason for this is because the internal GPS uses the data it receives and references it to the Ellipsoid model of the earth which is a perfect shape. Standalone GPSes use the Geoid model of the earth which is lumpy version of an Ellipsoid. Then they apply a correction value based on the present location to supply the elevation.
Click to expand...
Click to collapse
This makes it sound as if it's a hardware problem that cannot be fixed.
Dave
right from the wiki for the htc tilt wikipedia site.... read through but your info will be in the last paragraph of this read.
GPS Compatibility
Users of this phone have successfully installed and used other GPS map software applications (such as ALK Technologies CoPilot Live 7, DeLorme Street Atlas USA 2009, Fugawi, Garmin Mobile XT, Google Maps Mobile, iNav iGuidance, Intrisync Destinator, Microsoft Live Search Mobile, TomTom, Tracky, and VisualGPS BeeLineGPS), which are either free or cost nothing beyond the original purchase price. The map applications are compatible with the built-in GPS receiver, provided users set the appropriate COM port for the map application. The built-in GPS receiver was intended by some wireless providers to be used preferably with Telenav, which is a service that charges users monthly fees or fees based on the amount of downloaded map data. It should be noted that Telenav can only provide map data in areas where applicable cellular phone services are available and that users must have a data plan with their wireless providers.
The GPS may not activate when the phone is used indoors (or without access to clear sky) or if the person is walking very slowly (< 1 mile/hour).[citation needed] External GPS antenna connection provision is provided for clear signal reception. It is important for the GPS to be activated for the various functions in the GPS software to be activated and used properly.
The elevation display from the internal GPS will be inaccurate due to it using the WGS-84 Datum which can deviate from mean sea level in the range of +85 to -107 meters.The main reason for this is because the internal GPS uses the data it receives and references it to the Ellipsoid model of the earth which is a perfect shape. Standalone GPSes use the Geoid model of the earth which is lumpy version of an Ellipsoid. Then they apply a correction value based on the present location to supply the elevation.
Click to expand...
Click to collapse
GPS on my Kaiser always worked fine until yesterday.
Now i only get a fix with 2 sats. I'm from Germany and GPS Tuner says my position is
48°51'59,000''N
13°2'36,237''E
-12426m haha... somewhere underwater?
speed sometimes over 600 km/h ...
Google Maps says it can't get my Position,
TomTom shows the worng Position above.
I updated QuickGPS data a few times with no errors, but still can't get it to work. Strange...
I will test my external GPS Mouse when its battery is full... still loading
xsmiler said:
GPS on my Kaiser always worked fine until yesterday.
Now i only get a fix with 2 sats. I'm from Germany and GPS Tuner says my position is
48°51'59,000''N
13°2'36,237''E
-12426m haha... somewhere underwater?
speed sometimes over 600 km/h ...
Google Maps says it can't get my Position,
TomTom shows the worng Position above.
I updated QuickGPS data a few times with no errors, but still can't get it to work. Strange...
I will test my external GPS Mouse when its battery is full... still loading
Click to expand...
Click to collapse
I read this before. Some guy was having the same issue but only when he was in cemetery. Really. Try to search and u will find his thread.
I got erroneous data from Tomtom once when I was walking near Eton College (tall buildings surrounding narrow streets). It said I was travelling at about 190 mph through some place that sounded French (cant remember the name). Shutting down Navigator and restarting it and a soft reset didn't make any difference. For a while I thought a hardware fault had developed with the device because it was just after I started using Bluetooth for the first time with it. As I have no customisation on my device other than the addition of Tomtom Navigator and Microsoft’s Date and Time update for Daylight Saving (my media files are on microSD as is Tomtoms map and voices), I performed a hard reset. All is now well and Tomtom is back to normal and hasn't posed this problem since. I haven't been back to Eton so I don't know if the location played a part in bringing on the problem.
Ok, today I walked around a litte bit and now it works! I did nothing. I think this is a problem of bad GPS reception. The Problem only occured when I was surrounded by buildings.
xsmiler said:
Ok, today I walked around a litte bit and now it works! I did nothing. I think this is a problem of bad GPS reception. The Problem only occured when I was surrounded by buildings.
Click to expand...
Click to collapse
Probably you where near some powerful RF transmitters with very close frequency of that one used by satellites.
Medical equipment also generate spurious harmonics that could make any GPS radio receiver crazy.
Hi, I face a similar issue at the beach in front of my house - it shows me as -44 m for the altitude at the beach. everywhere else, e.g. in cities, it shows up fine.
Ghost in the Tytn2? who knows...
i have tested this issue. i stood under high tension power lines and 100 feet from them (high emf field) this caused bad data, also had my tomtom with me (bad data as well). there are many variables that can cause incorrect data. emf field, signal blocked, use the htc gps tool next time and see how many sats your locked on, next time this problem happens. I personally have found that less than 4 fixed sat's will throw off gps data, since the kaiser/tilt dosn't have waas correction built in. I have a gps puck with waas correction and tested under to 100 feet from high tension power lines and recepion and correction was 60% better. i have even noticed in my car (metal all around) the fix is about 30ft off, wich isint bad for a gps non waas. experiment a little bit. But make sure you use quick gps.
also the resonant freq that gps uses is 1575.42 Mhz, so if there are transmitters in the area with a freq in the range you will be subject to interference. 1240.000 - 1400.000 mhz is in the amateur radio band, this could also throw off spurious harmonics, so if you have a amateur radio operator around you, this could also be a part of your problem. and if any of you seen my username you also might know that im a amateur radio operator, so when it comes to amateur radio and frequiencies i know what im talking about.
ohh yea forgot to ad 1.7-80mhz is in the ballpark for broadband over powerline (BPL) this has been known to interfear with damn near everything. so if your one of those unlucky people that live in a BPL enabled area this could also be a huge factor. read more about bpl (i am very against this). http://www.ntia.doc.gov/ntiahome/fc...portadobe/ntia_bpl_report_04-413_volume_i.pdf
Hi everyone,
Have anyone noticed the slow calculation/refresh rate of GPS once it's active and navigating? Hold it in your hand and walk, there will be no refresh rate at all ! Your speed will be at 0 km/hr and the co-ordinates will not change at all. If you are in a car and it's stand still or on a traffic signal, or if there's a traffic jam and you are standstill and very immediately you have to turn right/left, you are sure to lose your way since it takes some time after the vehicle is in motion already to calculate and refresh your actual position and speed. Even when you are driving, there's a constant slow refresh rate of around 4 seconds. i.e. say you are accelerating the speed of your car, notice the speed being shown on the GPS software, it'll show your actual speed at a delay of 4/5 seconds. Same goes when you apply brakes, your speed suddenly goes down but the GPS will take it's time to reflect the correct speed.
I must say I am very disappointed with the GPS performace since my last phone was Trinity, it's GPS chip is just normal/ no agps but it's performance is much better than diamond's GPS. Trinity's GPS is immediate refresh rate with no such delays at all.
Test your diamond GPS observing what I said in this post and please post results here.
Are u sure it`s GPS issue not an software one ? Which software do you use for navigation ?
It's not a software issue since I've used TomTom and Garmin MobileXT with same results.
Same issue here!
Plus, the serial port keeps disconnecting of the internal GPS receiver keeps on disconnecting...
Which radio version have you on your device? This for sure software related (firmware, GPS navigation software or drivers)...
HastaSSSS
Have you enabled the AGPS on tweak? I found with this on the port would consistently connect and disconnect. Plus the refresh rate on TomTom was very very slow either driving or walking.
Today I turned AGPS off as where I travel it's not really needed anyway and bam!
Refresh rate both driving and walking is as good as my TomTom unit.
Today I drove with them both on and they were virtually in sync on the maps and spoken directions all the way. Very pleased.
Oh and ensuring "Receive all beams" is off in connections can help with TomTom too.
My details in case this has anything to do with it...
ROM : 1.37.405.1
Date: 10/06/2008
Radio: 1.00.25.03
Protocol: 52.26a.25.09H
And can you change the gpx settings under WM settings?
Even if I try to change the baud rate, when I go inside the configuration file, it's back to 4800 again...
HastaSSSS
This is a common problem with modern GPS chipsets - the way that they reduce multipath interference (from tall buildings, etc.) means that they often ignore movements below a certain speed (which can be often higher than walking pace).
Assuming that the HTC Touch Diamond uses the SirfStar 3 chipset (does anyone know for sure), this problem could theoretically be reduced by altering the 'static navigation' setting (see point 4 in this post for more details on static navigation and why it results in poor low-speed accuracy). However, how you'd actually tell the chipset to disable this feature, I don't know...
On an unrelated note, I have to say I'm extremely impressed with the sensitivity of the GPS chipset in the Diamond - it's managed to get lock in the middle of the my house, which is an amazing feat, and not one I've seen either my MTK or SirfStar standalone receivers achieve.
I am also pretty satisfied with the GPS performance. Can't complain on that!
snoopstah said:
This is a common problem with modern GPS chipsets - the way that they reduce multipath interference (from tall buildings, etc.) means that they often ignore movements below a certain speed (which can be often higher than walking pace).
Assuming that the HTC Touch Diamond uses the SirfStar 3 chipset (does anyone know for sure), this problem could theoretically be reduced by altering the 'static navigation' setting (see point 4 in this post for more details on static navigation and why it results in poor low-speed accuracy). However, how you'd actually tell the chipset to disable this feature, I don't know...
On an unrelated note, I have to say I'm extremely impressed with the sensitivity of the GPS chipset in the Diamond - it's managed to get lock in the middle of the my house, which is an amazing feat, and not one I've seen either my MTK or SirfStar standalone receivers achieve.
Click to expand...
Click to collapse
It's a good theory, no doubt about that, but I think it's more a lag in the communication between the receiver and the phone, or a lag on the rendering of the map.
Your explanation doesn't foresee as well the reason why the connection keeps falling...
But I've learned already something with your post. Didn't knew about that "feature" or "characteristic" of the SIRF III receivers.
HastaSSSS
My experience with the Diamonds GPS is 100% better than on my HTC P3600.
I primarly use the GPS with google maps in Canada, and Jamaica and it gives me accurcy to about 15 feet.. where with the 3600 it was accurate to about 30-40 feet. Normally have about 7 to 8 stats connected. Didn't touch any of the default settings on the phone.
I also tested with Live Search and GPS tuner v5 and works perfectly. Fast lock times (5-10seconds)....
Chris
snoopstah said:
This is a common problem with modern GPS chipsets - the way that they reduce multipath interference (from tall buildings, etc.) means that they often ignore movements below a certain speed (which can be often higher than walking pace).
Assuming that the HTC Touch Diamond uses the SirfStar 3 chipset (does anyone know for sure), this problem could theoretically be reduced by altering the 'static navigation' setting (see point 4 in this post for more details on static navigation and why it results in poor low-speed accuracy). However, how you'd actually tell the chipset to disable this feature, I don't know...
On an unrelated note, I have to say I'm extremely impressed with the sensitivity of the GPS chipset in the Diamond - it's managed to get lock in the middle of the my house, which is an amazing feat, and not one I've seen either my MTK or SirfStar standalone receivers achieve.
Click to expand...
Click to collapse
If that's true according to the static navigation thing? how can we disable it on our diamond? Can somebody throw a clue?
About AGPS, I haven't enabled it, or it's enabled by default in the new rom? 1.37 one?
It's like this with even AGSP disabled so it's certainly not the AGPS which is causing this delay in reception.
After googling and studying, i've found out that it's indeed the STATIC NAVIGATION which has been enabled by default on the diamond chip. Somone have any idea how to disable it? Please share
nice to see that I m not the only one with that problem, I was asking myself if it was my device who was deffective. On my cruise there was no lag at all.
I took mine out walking today and noticed it was telling me I was stood still for about 30 yds.
So I took it and my standalone out and the Diamond is rubbish but my big tomtom unit is great!
What's the point of GPS in a handheld device if you can't use it walking?
I hope this is easy to remedy.
I'm pretty sure that they don't use SirfStar III which would present much better GPS performance. Most probably they just incorporated the GPS section in the Qualcomm processor. Of course you can buy a SirfStar III Bluetooth receiver, but it doesn't make sense if you already got GPS built-in the device. I can only say that I was using HTC Hermes with SS III BT receiver a lot (more than 8 hours daily) and when I heard that HTC Kaiser had GPS build-in I was very happy untill almost immediately after trying TomTom on my new device I noticed worse performance. With Diamond it's the same story. Unfortunately...
A-GPS.
When I got the phone I installed the advanced config tool to adjust soms settings.
I also noticed A-GPS was off.
So I was thinking that turning it on might be a smart move.
Which it wasn't. TomTom reception was bad, waiting minutes would give maybe 4 sattelites en losing them constantly.
After turning of A-GPS again.. Whitin secconds .. I got 8 sattelites with a steady signal.
TomTom works fine for me now.
Excuses for my bad english...
for "foot" navigation the igo8 has a special setup along with "car", "bicycle"' "public transportation" and so on...why blame the diamond? blame yr navigation software! how many ppl said their navigation is the best? best, my ass the best.
be cool, soon igo8 is going to be avaible for diamond also
as for the diamond's gps...it works inside my house, first floor !!!
I really feel for you guys. GPS is one thing I definitely want to be working perfectly, and I can say with the diamond so far that has been the case. I'm getting a lock in about 15-20 seconds with about 12 satellites. I'm also using QuickGPS with no problems. I have been using the new TomTom 7 and it is absolutely fantastic!!!!!! Best handheld GPS solution I've ever owned, and I don't see why it would not be identical to a TomTom PNA!
My GPS is also not accurate, I'm using Tomtom7 and its telling me my home address is atleast 30 metres away when I'm at my home address. What the hell!!!!
I have tried enabling and disabling the A-GPS option and still its the same result.
Hey all, just wanted to share a tweek that I found somewhere (not for diamond) that helped me out with my aqusition problems.
HKEY_LOCAL_MACHINE/Software/HTC/SUPL AGPS/
EnableAGPS = 1
GPSMode = 4
dont know what exactly it does but it fixed all of my getting a lock problems. (dont forget to update your QuickGPS with the latest data also)
The only thing I want to see fixed now is the horrible update delay that you get when you are walking, still havent seen any solutions. From my point of view it talkes about 30~40 second of walking time before the position "catched up" to you, then it work quite well for as long as you are walking and stop only for a few second, if you stop for longer it seem to go back into what ever mode it is in from start so another wait for it to catch up.
I am doing all this is OziExplorerCE. Tested it on Googlemaps as well, works fine but the follow delay is there too.
D.
GPSMode = 1 means Autonomous (Self Fix no Assistance Required, Pessimistic Approach, Very Slow but Very Accurate)
GPSMode = 2 means Assisted by Server (Less Optimistic, Somewhat Slow but Medium Accuracy Quality)
GPSMode = 4 means Assisted by Server with Extended Ephemeris (Very Optimistic, But Sometime we loose Accuracy Quality)
can you let us know what's the other setting on your SUPL AGPS? such as ServerIP, ServerPort as well as other setting. These attributes are crucial to get AGPS works.. Thanks in advace.
Could somebody to export
HKEY_LOCAL_MACHINE/Software/HTC/SUPL AGPS/
complete tree to this forum. I would like compare other values in this tree with my phone. Thank you very much.
I'd guess that AGPS is Assisted GPS and it can also be activated using the Advanced Config Tool
HKLM\Software\HTC\SUPL AGPS\GPSMode 00000001 REG_DWORD
This alone above registry key is the only tweak i've made, and it fixes pedestrian mode, great for caching! Thanks a lot!! i'm happy now