[FIX] Slow GPS fix

Search This thread

bihslk

Senior Member
Dec 29, 2011
1,592
308
42
You wish to know :P
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://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.

Tnx man. I installed Android 4.0.4 on my S2 and i didnt get lock then i changed it to europe and it locked the sattelite in 10 sec
 

gwaitsi

Senior Member
Aug 3, 2014
144
9
i don't understand why it is necessary to change the ntp time server.
what if the unit does not have a network connection?
Are you saying the GPS can't get a fix, because no timeserver is available?
 

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://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.
    9
    May i refer to an Android app that does exactly this?

    http://xdaforums.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.