[FIX] Slow GPS fix
- Thread starter Claus72
- Start date
I think the correct nation value in gps.conf, along with a utility such as GPS Status & Toolbox helps best.
I have the value north-america.pool.ntp.org since I'm in the USA and using that with GPS Status & Toolbox I get a lock literally in seconds, less than 10. After you have the appropriate value and also install GPS Status & Toolbox. Open that program and from the menu select Tools -> Manage A-GPS state, click the Reset button, then go back into Tools -> Manage A-GPS state and click the Download button. After this you should get GPS locks very fast.
You'll have to open the GPS Status & Toolbox program every few days to keep the downloaded data current. But you'll only have to open the program and it should do the rest for you automatically after that initial setup, without you having to go through the entire process of Reset and Download manually. When you open it it will say it has downloaded the data again and then will get a GPS lock for you and tell you how long it took. The more current the data download, the faster the lock will be.
I have the value north-america.pool.ntp.org since I'm in the USA and using that with GPS Status & Toolbox I get a lock literally in seconds, less than 10. After you have the appropriate value and also install GPS Status & Toolbox. Open that program and from the menu select Tools -> Manage A-GPS state, click the Reset button, then go back into Tools -> Manage A-GPS state and click the Download button. After this you should get GPS locks very fast.
You'll have to open the GPS Status & Toolbox program every few days to keep the downloaded data current. But you'll only have to open the program and it should do the rest for you automatically after that initial setup, without you having to go through the entire process of Reset and Download manually. When you open it it will say it has downloaded the data again and then will get a GPS lock for you and tell you how long it took. The more current the data download, the faster the lock will be.
^^Yes, GPS Status Helps..I also feel..
I think this helps too..I'm not sure...could be just me...but fix seems faster after i changed it...
I think this helps too..I'm not sure...could be just me...but fix seems faster after i changed it...
Just tested ping response rates for north-america.pool.ntp.org versus lbs.geo.t-mobile.com.
lbs.geo.t-mobile.com was responding at a range of 135-155ms, while north-america.pool.ntp.org varied from 149-257ms.
So lbs.geo.t-mobile.com being on T-Mobile USA's network does seem to consistently respond faster. I thought about changing my own setting, but the difference is only about 0.1 second (100ms). So I doubt that 0.1 second is very noticable. It appears to be a very minor factor in my overall lock time given I am in the US. The redunancy of north-america.pool.ntp.org at the cost of 0.1 second seems better than relying soley on T-Mobile's server. And this all only comes into play when the A-GPS data is refreshed right?
I think the value may have more of an impact on people outside of the USA. But having the setting within nation (and the actual carrier's server does help a little) and a utility to download the A-GPS data (like GPS Status & Toolbox) probably is best.
Code:
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell ping
north-america.pool.ntp.org
PING north-america.pool.ntp.org (149.20.68.17) 56(84) bytes of data.
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=1 ttl=44 time=257 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=2 ttl=44 time=255 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=3 ttl=44 time=244 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=4 ttl=44 time=173 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=5 ttl=44 time=211 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=6 ttl=44 time=162 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=7 ttl=44 time=149 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=8 ttl=44 time=218 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=9 ttl=44 time=226 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=10 ttl=44 time=175 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=11 ttl=44 time=154 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=12 ttl=44 time=162 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=13 ttl=44 time=150 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=14 ttl=44 time=179 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=15 ttl=44 time=158 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=16 ttl=44 time=166 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=17 ttl=44 time=165 ms
64 bytes from pool-test.ntp.org (149.20.68.17): icmp_seq=18 ttl=44 time=154 ms
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell ping
lbs.geo.t-mobile.com
PING lbs.geo.t-mobile.com (10.176.29.225) 56(84) bytes of data.
64 bytes from 225.29.176.10.in-addr.arpa (10.176.29.225): icmp_seq=1 ttl=241 tim
e=155 ms
64 bytes from 225.29.176.10.in-addr.arpa (10.176.29.225): icmp_seq=2 ttl=241 tim
e=135 ms
64 bytes from 225.29.176.10.in-addr.arpa (10.176.29.225): icmp_seq=3 ttl=241 tim
e=144 ms
64 bytes from 225.29.176.10.in-addr.arpa (10.176.29.225): icmp_seq=4 ttl=241 tim
e=143 ms
64 bytes from 225.29.176.10.in-addr.arpa (10.176.29.225): icmp_seq=5 ttl=241 tim
e=142 ms
64 bytes from 225.29.176.10.in-addr.arpa (10.176.29.225): icmp_seq=6 ttl=241 tim
e=151 ms
64 bytes from 225.29.176.10.in-addr.arpa (10.176.29.225): icmp_seq=7 ttl=241 tim
e=141 ms
64 bytes from 225.29.176.10.in-addr.arpa (10.176.29.225): icmp_seq=8 ttl=241 tim
e=149 ms
64 bytes from 225.29.176.10.in-addr.arpa (10.176.29.225): icmp_seq=9 ttl=241 tim
e=148 ms
64 bytes from 225.29.176.10.in-addr.arpa (10.176.29.225): icmp_seq=10 ttl=241 ti
me=148 ms
64 bytes from 225.29.176.10.in-addr.arpa (10.176.29.225): icmp_seq=11 ttl=241 ti
me=147 ms
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>lbs.geo.t-mobile.com was responding at a range of 135-155ms, while north-america.pool.ntp.org varied from 149-257ms.
So lbs.geo.t-mobile.com being on T-Mobile USA's network does seem to consistently respond faster. I thought about changing my own setting, but the difference is only about 0.1 second (100ms). So I doubt that 0.1 second is very noticable. It appears to be a very minor factor in my overall lock time given I am in the US. The redunancy of north-america.pool.ntp.org at the cost of 0.1 second seems better than relying soley on T-Mobile's server. And this all only comes into play when the A-GPS data is refreshed right?
I think the value may have more of an impact on people outside of the USA. But having the setting within nation (and the actual carrier's server does help a little) and a utility to download the A-GPS data (like GPS Status & Toolbox) probably is best.
lbs.geo.t-mobile.com is not meant to replacement for ntp server URL...it is a recplacement for supl (agps) server...which is normally supl.google.com in gps.conf..
I don't know if they both do the same thing though..
lbs.geo.t-mobile.com is not meant to replacement for ntp server URL...it is a recplacement for supl (agps) server...which is normally supl.google.com in gps.conf
Correct .. And I thought I would give this a try .. and guess what ..
Seems to have knocked off about 30secs off COLD BOOT Times.
Correct .. And I thought I would give this a try .. and guess what ..
Seems to have knocked off about 30secs off COLD BOOT Times.
By the way, when the latest data is already downloaded via GPS Status & Toolbox, I can shut down, start back up, start the app and still get a fix in under 10 seconds. When the data is not current, it takes about 90 seconds. So the supl value being the carrier's server probably helps in cases when the data is not yet current. For those cases I'm going to adjust mine to the carrier's supl value.
I've been continually testing with lbs.geo.t-mobile.com in supl and it does help the GPS go from cold boot to lock at least 20 seconds faster. That is in cases where new assistance data has to be pulled. If the assitance data is already current, the GPS can lock even from a fresh boot of the device in less than 10 seconds. But in such cases the supl value does not come into play.
So the combination of the correct nation value in NTP_SERVER, carrier server in supl and a utility like GPS Status & Toolbox to keep assistance data current works best.
So the combination of the correct nation value in NTP_SERVER, carrier server in supl and a utility like GPS Status & Toolbox to keep assistance data current works best.
Working for every bulid..
Hey one noob question is that working for every android build... Have got also the slow gps prob.. ;-)
Thanks!
Hey one noob question is that working for every android build... Have got also the slow gps prob.. ;-)
Thanks!
Yes.
(I had to type more in this reply, because this board does not permit a post that is less than 10 characters
.)what about for those that can't get a lock within 10 minutes even after downloading GPS assistance data through GPS status & toolbox?
I've tried flashing several different roms (doing a clean factory/cache reset everytime) but to no avail.
I've tried flashing several different roms (doing a clean factory/cache reset everytime) but to no avail.
What finally worked for me...
Well, after reading and reading, I found out that there was too much guessing on the gps.conf settings. Still, these settings did solve my problem.
It appears that the ACCURACY THRESHOLD value is the key in achieving a quick GPS lock. Why? The less accuracy the more GPS satellites and the quicker the lock.
My gps.conf file is as follows:
By default, the ACCURACY_THRES parameter was not specified. I don't know if it defaults to 0. My lock times where +3 mins
Then I tried with ACCURACY_THRES=5000 and the GPS lock times went down to 1~3 mins
Now, with this setting ACCURACY_THRES=10000, I get GPS locks under 1 min and it's quite accurate (GPS Status indicates 2m error).
It would be great to get a description of all gps.conf parámeters, but if you google for "gps accuracy threshold" you will find that for faster locks, a higher number is required.
Hope it helps!!!
ps: Note that NTP_SERVER is configured to south america, since I am in that zone. change it accordingly.
Well, after reading and reading, I found out that there was too much guessing on the gps.conf settings. Still, these settings did solve my problem.
It appears that the ACCURACY THRESHOLD value is the key in achieving a quick GPS lock. Why? The less accuracy the more GPS satellites and the quicker the lock.
My gps.conf file is as follows:
Code:
NTP_SERVER=south-a
merica.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL = 1
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=1
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
ACCURACY_THRES=10000
################################
##### AGPS server settings #####
################################
# FOR SUPL SUPPORT, set the following
# SUPL_HOST=supl.host.com or IP
# SUPL_PORT=1234
SUPL_HOST=supl.google.com
SUPL_PORT=7276
# FOR C2K PDE SUPPORT, set the following
#C2K_HOST=c2k.pde.com
#C2K_PORT=1234
################################
# EXTRA SETTINGS
################################
# Wiper (wifi positioning), 1=enable, 0=disable
ENABLE_WIPER=1
#################################
##### AGPS Carrier settings #####
#################################
CURRENT_CARRIER=common
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
# TRUE for "User Plane", FALSE for "Control Plane"
DEFAULT_USER_PLANE=TRUE
REPORT_POSITION_USE_SUPL_REFLOC=1By default, the ACCURACY_THRES parameter was not specified. I don't know if it defaults to 0. My lock times where +3 mins
Then I tried with ACCURACY_THRES=5000 and the GPS lock times went down to 1~3 mins
Now, with this setting ACCURACY_THRES=10000, I get GPS locks under 1 min and it's quite accurate (GPS Status indicates 2m error).
It would be great to get a description of all gps.conf parámeters, but if you google for "gps accuracy threshold" you will find that for faster locks, a higher number is required.
Hope it helps!!!
ps: Note that NTP_SERVER is configured to south america, since I am in that zone. change it accordingly.
I guess that's an option when others fail. I've never changed that value, but have continued getting locks in about 1 minute or less using the earlier mentioned adjustments.
I have found that since I stopped Android from phoning home to Google and FROZE the Maps app, my GPS lock times with all other GPS apps are fantastically fast. Since I mainly use CoPilot for navigation, not using Google's apps for navigation is not a big deal for me.
But seriously, now, without even getting the latest aGPS data via GPS Status and Toolbox I'm seeing lock times daily that are under 20 seconds and often under 10 seconds.
I do use Fancy Widget to get up to date weather information, that probably keeps the GPS warm, but with the Google communication out of the way things now lock way faster than before. And I was using Fancy Widget back earlier too when things were slower and I was allowing Android to phone home to Google. So the only change is that I killed the continuous Android to Google communications, now my GPS locks way faster. Give it a shot and see how things do on average after a few days for you .
But seriously, now, without even getting the latest aGPS data via GPS Status and Toolbox I'm seeing lock times daily that are under 20 seconds and often under 10 seconds.
I do use Fancy Widget to get up to date weather information, that probably keeps the GPS warm, but with the Google communication out of the way things now lock way faster than before. And I was using Fancy Widget back earlier too when things were slower and I was allowing Android to phone home to Google. So the only change is that I killed the continuous Android to Google communications, now my GPS locks way faster. Give it a shot and see how things do on average after a few days for you
.
Thanks...
I want to say thanks to all the dev's and the descent members that provide us all with neverending upgrades and info for all our phone's
HD2 Running Cyn7......I hate windows
I want to say thanks to all the dev's and the descent members that provide us all with neverending upgrades and info for all our phone's
HD2 Running Cyn7......I hate windows
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
15I have had one problem with gps fix, it took about 90 sec to fix satellites.
I have found a thread in the Desire section that have solved this problem.
Now my gps takes about 15-30 sec to fis the satellite.
http://xdaforums.com/showthread.php?t=727887
This fix is only for European users and need to have root privilege.
You have to edit the file gps.conf located at /system/etc. I have used root explorer to edit the file.
You have to change the server like this:
NTP_SERVER=europe.pool.ntp.org
instead of
NTP_SERVER=north-america.pool.ntp.org
For me it is working fine. I hope it is the same for you.
Sorry for my English.92Update
thanks for help us..
I can add this too:
after opening the GPS.conf by Root system, right click and roll it down and choose (Open in Text Editor)
in the first line replace the stars with your server as shown below NTP_SERVER=***********
حبايبي في الشرق الأوسط - آسيا
For Middle east-Asia (Arabian Gulf)+yamen+jordan+syria+Iraq+Lebanon Try one of this servers :
Global servers:
0.asia.pool.ntp.org
or
1.asia.pool.ntp.org
or
2.asia.pool.ntp.org
or
3.asia.pool.ntp.org
or you can try your country server from below:
Philippines — ph.pool.ntp.org
Malaysia — my.pool.ntp.org
Turkey — tr.pool.ntp.org
Singapore — sg.pool.ntp.org
India — in.pool.ntp.org
Hong Kong — hk.pool.ntp.org
United Arab Emirates — ae.pool.ntp.org
Japan — jp.pool.ntp.org
Bangladesh — bd.pool.ntp.org
Israel — il.pool.ntp.org
Korea — kr.pool.ntp.org
Thailand — th.pool.ntp.org
Iran — ir.pool.ntp.org
Taiwan — tw.pool.ntp.org
China — cn.pool.ntp.org
Indonesia — id.pool.ntp.org
Vietnam — vn.pool.ntp.org
Pakistan — pk.pool.ntp.org
Oman — om.pool.ntp.org
Uzbekistan — uz.pool.ntp.org
Sri Lanka — lk.pool.ntp.org
Kyrgyzstan — kg.pool.ntp.org
Cambodia — kh.pool.ntp.org
for Africa countries:
1.africa.pool.ntp.org
or
0.africa.pool.ntp.org
or
1.pool.ntp.org
in Europe:
the global is:
0.europe.pool.ntp.org
or
1.europe.pool.ntp.org
or
2.europe.pool.ntp.org
or
3.europe.pool.ntp.org
or try your country server if available (sometime off)
Austria — at.pool.ntp.org
Switzerland — ch.pool.ntp.org
Germany — de.pool.ntp.org
Denmark — dk.pool.ntp.org
Spain — es.pool.ntp.org
France — fr.pool.ntp.org
Italy — it.pool.ntp.org
Luxembourg — lu.pool.ntp.org
Netherlands — nl.pool.ntp.org
Norway — no.pool.ntp.org
Poland — pl.pool.ntp.org
Sweden — se.pool.ntp.org
Slovenia — si.pool.ntp.org
United Kingdom — uk.pool.ntp.org
Finland — fi.pool.ntp.org
Ireland — ie.pool.ntp.org
Russian Federation — ru.pool.ntp.org
Belgium — be.pool.ntp.org
Portugal — pt.pool.ntp.org
Greece — gr.pool.ntp.org
Hungary — hu.pool.ntp.org
Bulgaria — bg.pool.ntp.org
Romania — ro.pool.ntp.org
Czech Republic — cz.pool.ntp.org
Yugoslavia — yu.pool.ntp.org
Estonia — ee.pool.ntp.org
Belarus — by.pool.ntp.org
Slovakia — sk.pool.ntp.org
Ukraine — ua.pool.ntp.org
Lithuania — lt.pool.ntp.org
Macedonia — mk.pool.ntp.org
Moldova — md.pool.ntp.org)
Latvia — lv.pool.ntp.org
Croatia — hr.pool.ntp.org
Republic of Serbia — rs.pool.ntp.org
Bosnia and Herzegovina — ba.pool.ntp.org
North America:
the global
0.north-america.pool.ntp.org
1.north-america.pool.ntp.org
2.north-america.pool.ntp.org
3.north-america.pool.ntp.org
or find your country below:
Canada — ca.pool.ntp.org
United States — us.pool.ntp.org
Mexico — mx.pool.ntp.org
Guatemala — gt.pool.ntp.org
Panama — pa.pool.ntp.org
Bahamas — bs.pool.ntp.org
Costa Rica — cr.pool.ntp.org
El Salvador — sv.pool.ntp.org
South America:
the global:
0.south-america.pool.ntp.org
1.south-america.pool.ntp.org
2.south-america.pool.ntp.org
3.south-america.pool.ntp.org
or find your country server below:
Brazil — br.pool.ntp.org
Chile — cl.pool.ntp.org
Argentina — ar.pool.ntp.org
Venezuela — ve.pool.ntp.org
Hope this give a more help
Regards2I don't know why people keep investing with changing the time server for the GPS.conf file. This is only used for calibrating the time of your phone. It does not matter which server you use as they all report in GMT. Saving 80ms is not going to make any difference. The default one works and the slight latency is fine.
Further more this gps conf file is used to configure the downloading the the GPS-A data. It is scheduled to run x times per week however I believe it does not run. The process is meant to be, it initially downloads the data to a local file location and then injects it into the GPS. The schedule job is not even running. I suspect it is a permissions thing. The second issue is the current kernel is not allowing the GPS data to be injected into the GPS where it can be used for speeding up GPS locks.
Testing of this fix is pointless within 24 hours as the GPS will remember the lock details it last had. Within a certain time period the same satellites will still be in place/available therefore a quicker lock. After 6-12 hours the satellites have move on and the old info does not apply anymore so a complete new lock is required. This takes time.2What finally worked for me...
Well, after reading and reading, I found out that there was too much guessing on the gps.conf settings. Still, these settings did solve my problem.
It appears that the ACCURACY THRESHOLD value is the key in achieving a quick GPS lock. Why? The less accuracy the more GPS satellites and the quicker the lock.
My gps.conf file is as follows:
Code:NTP_SERVER=south-a merica.pool.ntp.org XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin # DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info # 4 - Debug, 5 - Verbose DEBUG_LEVEL = 1 # Intermediate position report, 1=enable, 0=disable INTERMEDIATE_POS=1 # Accuracy threshold for intermediate positions # less accurate positions are ignored, 0 for passing all positions ACCURACY_THRES=10000 ################################ ##### AGPS server settings ##### ################################ # FOR SUPL SUPPORT, set the following # SUPL_HOST=supl.host.com or IP # SUPL_PORT=1234 SUPL_HOST=supl.google.com SUPL_PORT=7276 # FOR C2K PDE SUPPORT, set the following #C2K_HOST=c2k.pde.com #C2K_PORT=1234 ################################ # EXTRA SETTINGS ################################ # Wiper (wifi positioning), 1=enable, 0=disable ENABLE_WIPER=1 ################################# ##### AGPS Carrier settings ##### ################################# CURRENT_CARRIER=common DEFAULT_AGPS_ENABLE=TRUE DEFAULT_SSL_ENABLE=FALSE # TRUE for "User Plane", FALSE for "Control Plane" DEFAULT_USER_PLANE=TRUE REPORT_POSITION_USE_SUPL_REFLOC=1
By default, the ACCURACY_THRES parameter was not specified. I don't know if it defaults to 0. My lock times where +3 mins
Then I tried with ACCURACY_THRES=5000 and the GPS lock times went down to 1~3 mins
Now, with this setting ACCURACY_THRES=10000, I get GPS locks under 1 min and it's quite accurate (GPS Status indicates 2m error).
It would be great to get a description of all gps.conf parámeters, but if you google for "gps accuracy threshold" you will find that for faster locks, a higher number is required.
Hope it helps!!!
ps: Note that NTP_SERVER is configured to south america, since I am in that zone. change it accordingly.
New posts
-
-
-
Question Sony Xperia 1 mark V china up rom SEA, Can use update OTA
- Latest: Laclevuinhon
