[FIX] Slow GPS fix

Search This thread

Claus72

Senior Member
Jul 10, 2006
894
68
0
Bologna
I 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://forum.xda-developers.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.
 
Last edited:

ClydeB1

Senior Member
May 6, 2009
11,018
4,274
0
Ignore mattog,

THANKS FOR THAT, REALLY APPROVED!
Yes it is useful, but mattog does have a valid point though, as this "fix" has been around for months and the full solution referred to by mattog is not only for Europe but for the Rest of the World also, so this post is misleading, although useful to some (ie if you happen to live in Europe) ;). The full solution however is even better as instead of only putting Europe (which is rather large) you can narrow it down even further to individual countries to even further improve response time.

The full solution has been posted on the HD2 Android forums and is even posted in a FAQ thread in this very forum, which nobody happened to notice this useful bit of info as who ever reads the FAQ's, because "that's for noobs and my problem is unique" :D.

If we need to start new posts for every solution that has already been posted numerous times already, xda will soon be swamped with multiple threads and posts, its no wonder then that nobody can ever find an answer to anything.
 
Last edited:

MattOG

Senior Member
Dec 22, 2009
279
49
0
Couldn't have put it better myself. :)

But just ignore me, I like to be able to find things in a forum without trawling through pages of the same problems. Where's the fun in that?

Sent from my HD2 NANDroid using XDA App
 

cmylxgo

Senior Member
Feb 13, 2007
1,680
2,033
0
I use 2.us.pool.ntp.org in my roms based on my finding from below.

C:\Users\c>adb shell ping 2.us.pool.ntp.org
PING 2.us.pool.ntp.org (72.9.108.133) 56(84) bytes of data.
64 bytes from 72-9-108-133.reverse.ezzi.net (72.9.108.133): icmp_seq=1 ttl=49 time=101 ms
64 bytes from 72-9-108-133.reverse.ezzi.net (72.9.108.133): icmp_seq=2 ttl=49 time=89.2 ms
64 bytes from 72-9-108-133.reverse.ezzi.net (72.9.108.133): icmp_seq=3 ttl=49 time=89.2 ms
64 bytes from 72-9-108-133.reverse.ezzi.net (72.9.108.133): icmp_seq=4 ttl=49 time=88.9 ms
64 bytes from 72-9-108-133.reverse.ezzi.net (72.9.108.133): icmp_seq=5 ttl=49 time=88.4 ms
64 bytes from 72-9-108-133.reverse.ezzi.net (72.9.108.133): icmp_seq=6 ttl=49 time=98.2 ms
64 bytes from 72-9-108-133.reverse.ezzi.net (72.9.108.133): icmp_seq=7 ttl=49 time=98.3 ms
64 bytes from 72-9-108-133.reverse.ezzi.net (72.9.108.133): icmp_seq=8 ttl=49 time=98.2 ms
64 bytes from 72-9-108-133.reverse.ezzi.net (72.9.108.133): icmp_seq=9 ttl=49 time=88.4 ms
^C
C:\Users\c>adb shell ping 1.us.pool.ntp.org
PING 1.us.pool.ntp.org (208.75.88.4) 56(84) bytes of data.
64 bytes from clock.trit.net (208.75.88.4): icmp_seq=1 ttl=53 time=177 ms
64 bytes from clock.trit.net (208.75.88.4): icmp_seq=2 ttl=53 time=166 ms
64 bytes from clock.trit.net (208.75.88.4): icmp_seq=3 ttl=53 time=177 ms
64 bytes from clock.trit.net (208.75.88.4): icmp_seq=4 ttl=53 time=167 ms
64 bytes from clock.trit.net (208.75.88.4): icmp_seq=5 ttl=53 time=177 ms
64 bytes from clock.trit.net (208.75.88.4): icmp_seq=6 ttl=53 time=177 ms
64 bytes from clock.trit.net (208.75.88.4): icmp_seq=7 ttl=53 time=167 ms
64 bytes from clock.trit.net (208.75.88.4): icmp_seq=8 ttl=53 time=177 ms
^C
C:\Users\c>adb shell ping 0.us.pool.ntp.org
PING 0.us.pool.ntp.org (207.210.74.166) 56(84) bytes of data.
64 bytes from druid.storyinmemo.com (207.210.74.166): icmp_seq=1 ttl=41 time=111 ms
64 bytes from druid.storyinmemo.com (207.210.74.166): icmp_seq=2 ttl=41 time=109 ms
64 bytes from druid.storyinmemo.com (207.210.74.166): icmp_seq=3 ttl=41 time=109 ms
64 bytes from druid.storyinmemo.com (207.210.74.166): icmp_seq=4 ttl=41 time=109 ms
64 bytes from druid.storyinmemo.com (207.210.74.166): icmp_seq=5 ttl=41 time=108 ms
64 bytes from druid.storyinmemo.com (207.210.74.166): icmp_seq=6 ttl=41 time=118 ms
64 bytes from druid.storyinmemo.com (207.210.74.166): icmp_seq=7 ttl=41 time=108 ms
64 bytes from druid.storyinmemo.com (207.210.74.166): icmp_seq=8 ttl=41 time=108 ms
64 bytes from druid.storyinmemo.com (207.210.74.166): icmp_seq=9 ttl=41 time=108 ms
 

nito2721

Member
Nov 22, 2010
23
3
0
CALI
I use 2.us.pool.ntp.org in my roms based on my finding from below.

Correct me if I'm wrong. I may not know all the facts, but dont the servers alternate?

If you were to do the same ping 5 different times you would get different results from different servers. The server ip changes every time you ping.
 

downloadzy

Member
Jan 6, 2008
37
3
0
Update

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 :)

Regards
 
Last edited:

markmarkr

Senior Member
Aug 9, 2010
50
3
0
Correct me if I'm wrong. I may not know all the facts, but dont the servers alternate?

If you were to do the same ping 5 different times you would get different results from different servers. The server ip changes every time you ping.

Yes, that is what the "pool" part means, there is a pool of servers and you get any server from the pool. There are over 500 servers in the US pool. Either just set things to us.pool or find the ip of an actual server near you if you think it will make a difference.
 

dusty_nz

Senior Member
May 5, 2008
465
11
0
I 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.
 

chris_ah1

Senior Member
Jan 4, 2010
307
3
0
London
Sorry, I really don't understand this - is GPS broken on gingerbread or HD2 NAND android?

I installed GPSstatus, downloaded A-GPS and got a lock on google maps first time in 10-30seconds.

??? what is broken? and why does a time server fix it?
 

Darnell_Chat_TN

Senior Member
Nov 29, 2008
2,443
503
0
Chattanooga, TN
Correct me if I'm wrong. I may not know all the facts, but dont the servers alternate?

If you were to do the same ping 5 different times you would get different results from different servers. The server ip changes every time you ping.

Yea, I tried testing tonight and saw just that. Varied results from various sites in the pool responding. The times varied when testing one and then trying it again a few minutes later. I just chaged my own setting back to north-america.pool.ntp.org and I'll leave it at that unless I travel outside the USA.

Here were the results of my own testing:
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>a​db shell ping
2.us.pool.ntp.org
PING 2.us.pool.ntp.org (72.26.125.125) 56(84) bytes of data.
64 bytes from sulfur.mednor.net (72.26.125.125): icmp_seq=1 ttl=54 time=146 ms
64 bytes from sulfur.mednor.net (72.26.125.125): icmp_seq=2 ttl=54 time=154 ms
64 bytes from sulfur.mednor.net (72.26.125.125): icmp_seq=3 ttl=54 time=173 ms
64 bytes from sulfur.mednor.net (72.26.125.125): icmp_seq=4 ttl=54 time=242 ms
64 bytes from sulfur.mednor.net (72.26.125.125): icmp_seq=5 ttl=54 time=120 ms
64 bytes from sulfur.mednor.net (72.26.125.125): icmp_seq=6 ttl=54 time=129 ms
64 bytes from sulfur.mednor.net (72.26.125.125): icmp_seq=7 ttl=54 time=118 ms
64 bytes from sulfur.mednor.net (72.26.125.125): icmp_seq=8 ttl=54 time=127 ms
64 bytes from sulfur.mednor.net (72.26.125.125): icmp_seq=9 ttl=54 time=126 ms
64 bytes from sulfur.mednor.net (72.26.125.125): icmp_seq=10 ttl=54 time=124 ms
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>a​db shell ping
0.us.pool.ntp.org
PING 0.us.pool.ntp.org (72.167.42.82) 56(84) bytes of data.
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>a​db shell ping
1.us.pool.ntp.org
PING 1.us.pool.ntp.org (67.18.208.203) 56(84) bytes of data.
64 bytes from skavoovie.net (67.18.208.203): icmp_seq=1 ttl=51 time=98.7 ms
64 bytes from skavoovie.net (67.18.208.203): icmp_seq=2 ttl=51 time=157 ms
64 bytes from skavoovie.net (67.18.208.203): icmp_seq=3 ttl=51 time=106 ms
64 bytes from skavoovie.net (67.18.208.203): icmp_seq=4 ttl=51 time=104 ms
64 bytes from skavoovie.net (67.18.208.203): icmp_seq=5 ttl=51 time=104 ms
64 bytes from skavoovie.net (67.18.208.203): icmp_seq=6 ttl=51 time=102 ms
64 bytes from skavoovie.net (67.18.208.203): icmp_seq=7 ttl=51 time=122 ms
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>a​db shell ping
2.us.pool.ntp.org
PING 2.us.pool.ntp.org (204.9.54.119) 56(84) bytes of data.
64 bytes from private.ssl119.ord02.your.org (204.9.54.119): icmp_seq=1 ttl=54 ti
me=137 ms
64 bytes from private.ssl119.ord02.your.org (204.9.54.119): icmp_seq=2 ttl=54 ti
me=126 ms
64 bytes from private.ssl119.ord02.your.org (204.9.54.119): icmp_seq=3 ttl=54 ti
me=134 ms
64 bytes from private.ssl119.ord02.your.org (204.9.54.119): icmp_seq=4 ttl=54 ti
me=123 ms
64 bytes from private.ssl119.ord02.your.org (204.9.54.119): icmp_seq=5 ttl=54 ti
me=122 ms
64 bytes from private.ssl119.ord02.your.org (204.9.54.119): icmp_seq=6 ttl=54 ti
me=120 ms
64 bytes from private.ssl119.ord02.your.org (204.9.54.119): icmp_seq=7 ttl=54 ti
me=119 ms
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>a​db shell ping
3.us.pool.ntp.org
PING 3.us.pool.ntp.org (173.193.227.67) 56(84) bytes of data.
64 bytes from w1-wdc.ipv4.got-root.me.uk (173.193.227.67): icmp_seq=1 ttl=47 tim
e=98.2 ms
64 bytes from w1-wdc.ipv4.got-root.me.uk (173.193.227.67): icmp_seq=2 ttl=47 tim
e=97.4 ms
64 bytes from w1-wdc.ipv4.got-root.me.uk (173.193.227.67): icmp_seq=3 ttl=47 tim
e=115 ms
64 bytes from w1-wdc.ipv4.got-root.me.uk (173.193.227.67): icmp_seq=4 ttl=47 tim
e=104 ms
64 bytes from w1-wdc.ipv4.got-root.me.uk (173.193.227.67): icmp_seq=5 ttl=47 tim
e=102 ms
64 bytes from w1-wdc.ipv4.got-root.me.uk (173.193.227.67): icmp_seq=6 ttl=47 tim
e=101 ms
64 bytes from w1-wdc.ipv4.got-root.me.uk (173.193.227.67): icmp_seq=7 ttl=47 tim
e=99.1 ms
64 bytes from w1-wdc.ipv4.got-root.me.uk (173.193.227.67): icmp_seq=8 ttl=47 tim
e=98.1 ms
64 bytes from w1-wdc.ipv4.got-root.me.uk (173.193.227.67): icmp_seq=9 ttl=47 tim
e=106 ms
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>a​db shell ping
0.us.pool.ntp.org
PING 0.us.pool.ntp.org (72.26.217.210) 56(84) bytes of data.
64 bytes from icarus.seobeo.com (72.26.217.210): icmp_seq=1 ttl=44 time=183 ms
64 bytes from icarus.seobeo.com (72.26.217.210): icmp_seq=2 ttl=44 time=182 ms
64 bytes from icarus.seobeo.com (72.26.217.210): icmp_seq=3 ttl=44 time=181 ms
64 bytes from icarus.seobeo.com (72.26.217.210): icmp_seq=4 ttl=44 time=180 ms
64 bytes from icarus.seobeo.com (72.26.217.210): icmp_seq=5 ttl=44 time=198 ms
64 bytes from icarus.seobeo.com (72.26.217.210): icmp_seq=6 ttl=44 time=206 ms
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>a​db shell ping
1.us.pool.ntp.org
PING 1.us.pool.ntp.org (128.10.19.24) 56(84) bytes of data.
64 bytes from andromeda.cs.purdue.edu (128.10.19.24): icmp_seq=1 ttl=47 time=145
ms
64 bytes from andromeda.cs.purdue.edu (128.10.19.24): icmp_seq=2 ttl=47 time=175
ms
64 bytes from andromeda.cs.purdue.edu (128.10.19.24): icmp_seq=3 ttl=47 time=155
ms
64 bytes from andromeda.cs.purdue.edu (128.10.19.24): icmp_seq=4 ttl=47 time=115
ms
64 bytes from andromeda.cs.purdue.edu (128.10.19.24): icmp_seq=5 ttl=47 time=155
ms
64 bytes from andromeda.cs.purdue.edu (128.10.19.24): icmp_seq=6 ttl=47 time=134
ms
64 bytes from andromeda.cs.purdue.edu (128.10.19.24): icmp_seq=7 ttl=47 time=134
ms
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>a​db shell ping
2.us.pool.ntp.org
PING 2.us.pool.ntp.org (208.53.158.34) 56(84) bytes of data.
64 bytes from mirror (208.53.158.34): icmp_seq=1 ttl=54 time=112 ms
64 bytes from mirror (208.53.158.34): icmp_seq=2 ttl=54 time=111 ms
64 bytes from mirror (208.53.158.34): icmp_seq=3 ttl=54 time=130 ms
64 bytes from mirror (208.53.158.34): icmp_seq=4 ttl=54 time=158 ms
64 bytes from mirror (208.53.158.34): icmp_seq=5 ttl=54 time=127 ms
64 bytes from mirror (208.53.158.34): icmp_seq=6 ttl=54 time=116 ms
64 bytes from mirror (208.53.158.34): icmp_seq=7 ttl=54 time=115 ms
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>a​db shell ping
3.us.pool.ntp.org
PING 3.us.pool.ntp.org (68.68.18.78) 56(84) bytes of data.
64 bytes from 68.68.18.78.customer.bluemilenetworks.com (68.68.18.78): icmp_seq=
1 ttl=47 time=125 ms
64 bytes from 68.68.18.78.customer.bluemilenetworks.com (68.68.18.78): icmp_seq=
2 ttl=47 time=105 ms
64 bytes from 68.68.18.78.customer.bluemilenetworks.com (68.68.18.78): icmp_seq=
3 ttl=47 time=124 ms
64 bytes from 68.68.18.78.customer.bluemilenetworks.com (68.68.18.78): icmp_seq=
4 ttl=47 time=102 ms
64 bytes from 68.68.18.78.customer.bluemilenetworks.com (68.68.18.78): icmp_seq=
5 ttl=47 time=120 ms
64 bytes from 68.68.18.78.customer.bluemilenetworks.com (68.68.18.78): icmp_seq=
6 ttl=47 time=108 ms
64 bytes from 68.68.18.78.customer.bluemilenetworks.com (68.68.18.78): icmp_seq=
7 ttl=47 time=107 ms
64 bytes from 68.68.18.78.customer.bluemilenetworks.com (68.68.18.78): icmp_seq=
8 ttl=47 time=115 ms
64 bytes from 68.68.18.78.customer.bluemilenetworks.com (68.68.18.78): icmp_seq=
9 ttl=47 time=114 ms
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>a​db shell ping
north-america.pool.ntp.org
PING north-america.pool.ntp.org (97.107.134.28) 56(84) bytes of data.
64 bytes from rigel.jeffkaplan.net (97.107.134.28): icmp_seq=1 ttl=41 time=104 m
s
64 bytes from rigel.jeffkaplan.net (97.107.134.28): icmp_seq=2 ttl=41 time=102 m
s
64 bytes from rigel.jeffkaplan.net (97.107.134.28): icmp_seq=3 ttl=41 time=111 m
s
64 bytes from rigel.jeffkaplan.net (97.107.134.28): icmp_seq=4 ttl=41 time=100 m
s
64 bytes from rigel.jeffkaplan.net (97.107.134.28): icmp_seq=5 ttl=41 time=159 m
s
64 bytes from rigel.jeffkaplan.net (97.107.134.28): icmp_seq=6 ttl=41 time=97.4
ms
64 bytes from rigel.jeffkaplan.net (97.107.134.28): icmp_seq=7 ttl=41 time=106 m
s
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>a​db shell ping
north-america.pool.ntp.org
PING north-america.pool.ntp.org (169.229.70.95) 56(84) bytes of data.
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>a​db shell ping
north-america.pool.ntp.org
PING north-america.pool.ntp.org (173.8.198.242) 56(84) bytes of data.
64 bytes from www1.bitvector.org (173.8.198.242): icmp_seq=1 ttl=47 time=175 ms
64 bytes from www1.bitvector.org (173.8.198.242): icmp_seq=2 ttl=47 time=174 ms
64 bytes from www1.bitvector.org (173.8.198.242): icmp_seq=3 ttl=47 time=214 ms
64 bytes from www1.bitvector.org (173.8.198.242): icmp_seq=4 ttl=47 time=194 ms
64 bytes from www1.bitvector.org (173.8.198.242): icmp_seq=5 ttl=47 time=184 ms
64 bytes from www1.bitvector.org (173.8.198.242): icmp_seq=6 ttl=47 time=183 ms
64 bytes from www1.bitvector.org (173.8.198.242): icmp_seq=7 ttl=47 time=182 ms
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>a​db shell ping
north-america.pool.ntp.org
PING north-america.pool.ntp.org (208.69.56.110) 56(84) bytes of data.
64 bytes from one.tariox.com (208.69.56.110): icmp_seq=1 ttl=50 time=125 ms
64 bytes from one.tariox.com (208.69.56.110): icmp_seq=2 ttl=50 time=124 ms
64 bytes from one.tariox.com (208.69.56.110): icmp_seq=3 ttl=50 time=123 ms
64 bytes from one.tariox.com (208.69.56.110): icmp_seq=4 ttl=50 time=131 ms
64 bytes from one.tariox.com (208.69.56.110): icmp_seq=5 ttl=50 time=120 ms
^C
D:\Program Files (x86)\Android\android-sdk-windows\platform-tools>
 

pyrorob

Senior Member
Oct 19, 2006
1,091
175
93
39
Hickory, NC
OnePlus 6T
hmm.... some good info here, i guess i''ll add my 2 cents.. heres t-mobile usa's supl (agps) server: lbs.geo.t-mobile.com and port: 7275
in gps.conf, change it from supl.google.com under supl_host= and port=
 

pyrorob

Senior Member
Oct 19, 2006
1,091
175
93
39
Hickory, NC
OnePlus 6T
No. I used it on the way home and it seemed to take just as long to lock on. That said it did not seem any worse. I will let you guys know if I see any real improvement.

yeah.. i read after i posted those that the gps driver currently doesnt read agps commands from the network, i believe it was gauner1986 that posted that.. might have been in these forums or on irc.. but, he said there going to be working on that in newer driver builds, so theres hope at least
 

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    I 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://forum.xda-developers.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.
    9
    May i refer to an Android app that does exactly this?

    http://forum.xda-developers.com/showthread.php?t=825717
    2
    Update

    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 :)

    Regards
    2
    I 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.
    2
    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:

    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.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone