AGPS Patch Inspire 4G 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO MORE SATS

Search This thread

danielvelez

Senior Member
Sep 8, 2007
124
6
Hello Crypted.

There´s an issue with the time that the gps is reporting.
Download and install GPS Time - It uses the gps sat time to calibrate the cellphone clock
Then download and install ClockSync - It uses the internet connection to figure out the time on an atomic clock.
On my samsung galaxy tab, the GPS Time and the ClockSync time shows almost the same time with one or two seconds difference. Nevertheless, on the Inspire 4G somehow the sentence of the gps time is being overruled by the system clock, so on gps Time or any other gps application that shows accurated gps time (gps status or gps test or gps essentials) the gps time is actually the same system time, even if you have it intentionally moved it some minutes.

Have you noticed this before? Can you test / compare the time on your gps inspire 4g against an standard garmin gps device?
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
Hello Crypted.

There´s an issue with the time that the gps is reporting.
Download and install GPS Time - It uses the gps sat time to calibrate the cellphone clock
Then download and install ClockSync - It uses the internet connection to figure out the time on an atomic clock.
On my samsung galaxy tab, the GPS Time and the ClockSync time shows almost the same time with one or two seconds difference. Nevertheless, on the Inspire 4G somehow the sentence of the gps time is being overruled by the system clock, so on gps Time or any other gps application that shows accurated gps time (gps status or gps test or gps essentials) the gps time is actually the same system time, even if you have it intentionally moved it some minutes.

Have you noticed this before? Can you test / compare the time on your gps inspire 4g against an standard garmin gps device?

What effect does your time offset have your mapping locale?
 

danielvelez

Senior Member
Sep 8, 2007
124
6
Hello crypter

To explain my problem:
I use gps as a race logger for hanggliding races. I use a nice stand alone gps for it, but I´m also using the phone as a backup. there are nice flying logger for free out there. I use gaggle that also can give you real tracking on a server, and sometimes xcsoar.

The problem with the offset is that all the pilots have syncronized gps devices that shows the start of the race. If you have a wrong time showing then you would start before or after everybody.

The other issue would be that your recorded tracklog will reflect the wrong time, so it can show you winning a task when you came into goal on second place, even for a minute (if the offset is that big by that time).

On standard gps usage, such as google maps, google navigation, sygic, copilot, or anything like it, or even for getting the gps possition for geotagging, the wrong time information is not that relevant. Even then, when you are using the car gps software to be on time on an appointment, and the time is just plain wrong, then your ETA would not reflect the correct time neither.

That´s basically the consecuense, therefor my necessity to have a workaround.

I started a thread on the upper forum with a little more explanation on the problem, and some local tests that I did to be sure that there´s an issue on my gps time on the Inspire 4G.

I´m gonna test it on other Inspire 4G phones, with different roms.
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
Hello crypter

To explain my problem:
I use gps as a race logger for hanggliding races. I use a nice stand alone gps for it, but I´m also using the phone as a backup. there are nice flying logger for free out there. I use gaggle that also can give you real tracking on a server, and sometimes xcsoar.

The problem with the offset is that all the pilots have syncronized gps devices that shows the start of the race. If you have a wrong time showing then you would start before or after everybody.

The other issue would be that your recorded tracklog will reflect the wrong time, so it can show you winning a task when you came into goal on second place, even for a minute (if the offset is that big by that time).

On standard gps usage, such as google maps, google navigation, sygic, copilot, or anything like it, or even for getting the gps possition for geotagging, the wrong time information is not that relevant. Even then, when you are using the car gps software to be on time on an appointment, and the time is just plain wrong, then your ETA would not reflect the correct time neither.

That´s basically the consecuense, therefor my necessity to have a workaround.

I started a thread on the upper forum with a little more explanation on the problem, and some local tests that I did to be sure that there´s an issue on my gps time on the Inspire 4G.

I´m gonna test it on other Inspire 4G phones, with different roms.

Try this patch with Cleardroid's latest version and the latest stable build of the kernel he recommends. My GPS clock shows to be accurate.

EDIT: Also, consider disabling network time just in case you're getting bad readings that way IF the above ROM and kernel fail to help.
 
hey everyone I'm sure this has been covred before but having trouble finding a solid and answer if there even is one since changing to ics I'm having a problem keeping signal lock using Google maps it seems to be fine on everything else and if I check GPS tools it shows a lock so it must be an issue with Google and ics my other programs such as life 360 seem to work OK except for the occasional wrong location fix anyone with any insight on this who could point me on the wright direction would be a great help

Sent from my Inspire 4G using XDA
 

ghostryder12

Senior Member
Jun 26, 2009
1,822
562
Northern California
hey everyone I'm sure this has been covred before but having trouble finding a solid and answer if there even is one since changing to ics I'm having a problem keeping signal lock using Google maps it seems to be fine on everything else and if I check GPS tools it shows a lock so it must be an issue with Google and ics my other programs such as life 360 seem to work OK except for the occasional wrong location fix anyone with any insight on this who could point me on the wright direction would be a great help

Sent from my Inspire 4G using XDA

For me, it depended on which ICS ROM boils I was using. Right now, I'm using Redemption v1.1 Alpha_8 and I have GPS locking once again. I was using http://xdaforums.com/showthread.php?p=3 and it is stripped down for speed and battery but I couldn't keep GPS locked at all.

I'm just an Inspire tweaking junky.
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
For me, it depended on which ICS ROM boils I was using. Right now, I'm using Redemption v1.1 Alpha_8 and I have GPS locking once again. I was using http://xdaforums.com/showthread.php?p=3 and it is stripped down for speed and battery but I couldn't keep GPS locked at all.

I'm just an Inspire tweaking junky.

Your post idly helpful. Read the notes section. You don't even indicate that you use this patch.

Lastly ics is alpha and GPS support is minimal.

So do the above and if you're a user of this patch, reply with PROPER information as the thread dictates.

Sent from my Transformer Prime TF201 using XDA
 

ghostryder12

Senior Member
Jun 26, 2009
1,822
562
Northern California
Your post idly helpful. Read the notes section. You don't even indicate that you use this patch.

Lastly ics is alpha and GPS support is minimal.

So do the above and if you're a user of this patch, reply with PROPER information as the thread dictates.

Sent from my Transformer Prime TF201 using XDA

I've been using this patch for several months now. When I was using the other ICS ROM, I couldn't get a GPS lock. Now that I am using the Redemption ICS ROM, WITH this patch, I now get GPS locking as it should.
the patch works well, just not well with some ICS ROMs.
Edit: Sorry I failed to follow your rules. Thank you for this patch. I have been talking it up to different Android users. But as of right now, that will end.
I'm just an Inspire tweaking junky.
 
Last edited:

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
sorry I'm using ice cold sandwich from lord 7.4 stripper edition with full wipe using 3.1 no SSL

Sent from my Inspire 4G using XDA


Try another ROM with a different base? go for clear droid...




I've been using this patch for several months now. When I was using the other ICS ROM, I couldn't get a GPS lock. Now that I am using the Redemption ICS ROM, WITH this patch, I now get GPS locking as it should.
the patch works well, just not well with some ICS ROMs.
Edit: Sorry I failed to follow your rules. Thank you for this patch. I have been talking it up to different Android users. But as of right now, that will end.
I'm just an Inspire tweaking junky.

You're fine my friend. I was taking to the other person about the notes and proper posting so we could actually try help should the notes not be sufficient. :)

Sent from my Transformer Prime TF201 using XDA
 

danielvelez

Senior Member
Sep 8, 2007
124
6
Hello again crypted.

I've been looking into Cleardroid rom, but it seems a little outdated in relation to Android Revolution. So before I "somehow" downgrade the rom I was wondering if my gps specific "time" issue (shows the phone clock instead than the gps clock) could be related to the "radio" instead than the rom.

Could you give me your radio info so I can try that approach first before going to another rom?

My actual radio (with corresponding RIL) is 12.65.60.29P_26.14.04.28_M

Thanks.
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
Hello again crypted.

I've been looking into Cleardroid rom, but it seems a little outdated in relation to Android Revolution. So before I "somehow" downgrade the rom I was wondering if my gps specific "time" issue (shows the phone clock instead than the gps clock) could be related to the "radio" instead than the rom.

Could you give me your radio info so I can try that approach first before going to another rom?

My actual radio (with corresponding RIL) is 12.65.60.29P_26.14.04.28_M

Thanks.

I use Cleardroid's latest ROM, the recommended radio, and BD-Ace Kernel's latest safe build.
 
  • Like
Reactions: danielvelez

danielvelez

Senior Member
Sep 8, 2007
124
6
I use Cleardroid's latest ROM, the recommended radio, and BD-Ace Kernel's latest safe build.

Ok.

Somehow I ended up on a bootloop when trying lastest Cleardroid ROM. Installed three times and I'm not sure if I didn't wait enough for the first boot (almost 20 minutes).

Anyway, on another thread one user that had a lot of nandroid backups took the time to check the gps time issue and found out that almost all the gingerbread roms where showing device time instead of gps time. Nevertheless, the ICS Roms seems to work this out, and they stated that the Froyo ROMS did not have this issue. So maybe it's related exclusively to the base ROM and not the customizations.

Finally I decided to try out Ice Cold Sandwich (ICS 4.0.4) since yesterday. First thing that I checked was this GPS issue, and it's gone. ICS, using GPS Time, showed the correct gps clock next to the internal clock, so the gps loggers should be working fine now.

Thanks for all the effort and ideas on this matter.
 

ClearD

Inactive Recognized Developer
Jan 10, 2009
3,261
1,445
37
Gallipolis
Somehow I ended up on a bootloop when trying lastest Cleardroid ROM. Installed three times and I'm not sure if I didn't wait enough for the first boot (almost 20 minutes).

There's an issue with 1.3.2 unless you flash it after 1.3.1, if you wish to try in the future, flash 1.3.1 first, and 1.3.2 will boot immediately after. :) sorry about that.

Sent using XDA-funded carrier pigeons
 

biglittlegato

Senior Member
Jun 4, 2009
532
147
Cali
Ok.

Somehow I ended up on a bootloop when trying lastest Cleardroid ROM. Installed three times and I'm not sure if I didn't wait enough for the first boot (almost 20 minutes).

Anyway, on another thread one user that had a lot of nandroid backups took the time to check the gps time issue and found out that almost all the gingerbread roms where showing device time instead of gps time. Nevertheless, the ICS Roms seems to work this out, and they stated that the Froyo ROMS did not have this issue. So maybe it's related exclusively to the base ROM and not the customizations.

Finally I decided to try out Ice Cold Sandwich (ICS 4.0.4) since yesterday. First thing that I checked was this GPS issue, and it's gone. ICS, using GPS Time, showed the correct gps clock next to the internal clock, so the gps loggers should be working fine now.

Thanks for all the effort and ideas on this matter.

Glad you found a rom that works for you.

Sent using the power of the dark side.
 

SpiderCrow

Member
Oct 19, 2009
7
4
Medellin
www.alexcuervo.com
Reporting!

HTC Inspire 4G
Region: South America
Country: Colombia
ROM: IceColdSandwich 7.4 AOKP STRIPPER EDITION
http://xdaforums.com/showthread.php?t=1450962
Radio: 12.65.60U26.14.04_M
RIL: 2.0.0201HM
Patch: Google Specific No-SSL v3.1

Software used to test: GPS Status
Test time after install gps.conf: 10 minutes
Satellites indoor: 5/5
Time to connect indoor: 61 segs, second time 11 segs
Average Satellites outdoor: 5/5
Time to connect outdoor: 8 segs.
Maximum Satellites outdoor 9/9

Thanks crypted, I will invite you an beer next week!

Regards,
Alex.
 

Attachments

  • Indoor.jpg
    Indoor.jpg
    38 KB · Views: 465
  • Outdoor.jpg
    Outdoor.jpg
    39.8 KB · Views: 450
Last edited:

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
Reporting!

HTC Inspire 4G
Region: South America
Country: Colombia
ROM: IceColdSandwich 7.4 AOKP STRIPPER EDITION
http://xdaforums.com/showthread.php?t=1450962
Radio: 12.65.60U26.14.04_M
RIL: 2.0.0201HM
Patch: Google Specific No-SSL v3.1

Software used to test: GPS Status
Test time after install gps.conf: 10 minutes
Satellites indoor: 5/5
Time to connect indoor: 61 segs, second time 11 segs
Average Satellites outdoor: 5/5
Time to connect outdoor: 8 segs.
Maximum Satellites outdoor 9/9

Thanks crypted, I will invite you an beer next week!

Regards,
Alex.

Gracias! I'm glad it works for you.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 198
    AGPS Patch Inspire 4G 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO MORE SATS

    AGPS PATCH

    REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.

    List of officially supported devices is at the bottom of this post.

    Use this if you're having GPS issues (unreliability, no functionality, etc.)

    This patch provides a worldwide solution to GPS issue for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.

    HOWTO INSTALL: (Remember to make a backup. See Notes section for what this patch does.)

    Method 1:
    1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
    2. Extract the files into a specific folder.
    3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
    4. Open the batch file called "ADB Installation Script - RUN THIS" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
    5. Select the version you want from the list.
    6. Follow the prompts to reboot. You're done.
    4. Review the NOTES section.

    Method 2:
    1. Download the patch
    2. Copy all file(s)* into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
    **Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
    3. Reboot the device
    4. Review the NOTES section.
    *Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.

    Method 3 (easiest if you use a compatible version of CWR or CWM)*:
    1. Download the patch
    2. Boot into CWR (Clockwork Recovery)
    3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
    4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
    If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
    5. Reboot the device
    6. Review the NOTES section.
    *This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.


    Downloads:
    SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.

    Recommended Builds (pick either):
    Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)

    Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.

    3.x trunk Alternative Options (currently v3.1)
    Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the Google Specific NO-SSL TWRP build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    *The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.

    2.x trunk Alternative Options (currently v2.2)
    Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
    *The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.


    Changelog: (I'll try to keep this correct and current)
    Code:
    v3.1 update - New Version
    introduced the NO SSL version for Google build.  Shows faster performance times.
    
    v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
    introduced my own NTP pools
    repaired the LG Alternate build (was same as standard build, compilation error)
    
    v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
    based on v2.2 configuration
    has my own XTRA/AGPS server instead of Qualcomm
    re-added two AGPS variables from v1.3   (two beta-testers saw instant results with these re-added)
    re-added on USE SUPL variable from v1.3   (two beta-testers saw instant results with these re-added)
    variables are now divided into sections and sections have descriptions

    Code:
    v2.2 update - New Version
    introduced the NO SSL version for Google build.  Shows faster performance times.
    
    v2.2 (additional builds added)
    added a new SUPL version using data from Sony Ericsson
    added an alternate release using LG SUPL servers
    added an alternate release using Google SUPL servers
    updated the ADB PUSH to include new versions
    fixed broken download links for the patch
    
    v2.2
    removed local AGPS variable
    removed local XTRA_SERVER variable
    created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
    reduced redundancy in NTP and XTRA (unnecessary entries)
    added newly located SUPL server to T-Mobile build
    
    v2.1 (encompassing changes between 1.3 to 2.1)
    removed two NTP server pools
    removed xtra1 server
    removed multiple SUPL_HOST entries
    aligned SUPL_HOST with SUPLROOTCERT in each package
    increased QOS timeout from 89 to 100
    removed QOS standalone timeout variable
    removed extra AGPS variables


    Old Versions:
    3.x Trunk:
    v3.0 ADB Push Installer
    v3.0 Google Build
    v3.0 Google Alternate Build
    v3.0 Google CWM Build
    v3.0 AT&T Build
    v3.0 T-Mobile Build
    v3.0 LG Build
    v3.0 LG Alternate Build
    v3.0 Sony Ericsson Build
    v3.0 GPS Only Build
    v3.0 GPS Only Alternate Build

    2.x Trunk:
    v2.1 Google Generic Build
    v2.1 AT&T Specific Build
    v2.1 T-Mobile Specific Build
    v2.1 GPS.Conf Only Build
    v2.1 GPS.Conf Only Build (alternate)
    v2.0 Google Generic Build
    v2.0 AT&T Specific Build
    v2.0 T-Mobile Specific Build
    v2.0 GPS.Conf Only Build
    v2.0 GPS.Conf Only Build (alternate)

    1.x Trunk:
    Worldwide 1.3
    Worldwide 1.3n (alternate)
    North America 1.2
    Worldwide 1.2
    Worldwide 1.2n (alternate)
    North America 1.1
    Worldwide 1.1
    Worldwide 1.0 (not recommended)
    North America 1.0 (not recommended)


    Rules For Posting Questions:
    1. Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
    2. Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
    3. DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
    4. Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.


    NOTES Section:
    1. This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
    2. This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
    3. I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
    4. This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
    5. Remember, this has to be reflashed when you update or change ROMs.
    6. Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
    7. Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
    8. NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
    9. IF you have issues with v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance.
    10. IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
    11. CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
    12. Reports indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
    13. Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
    14. Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
    15. I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
    16. Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
    17. I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
    18. If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differently which is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error threshold. Food for thought.
    19. DO NOT USE ANY OTHER GPS FIXING APPS with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
    20. Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
    21. Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
    22. There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
    23. Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
    24. Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://xdaforums.com/showthread.php?t=1101066 provides a video on self-repair.
    25. An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
    26. Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
    27. Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.

    AGPS Patch Officially Supported Devices:
    Acer Iconia
    Asus Transformer Prime
    Asus Transformer (TF101)
    Asus Transformer TF300T
    HTC Inspire 4G
    HTC Desire HD
    HTC Sensation
    HTC Incredible S
    HTC Salsa
    HTC Flyer
    HTC Evo 3D
    HTC Desire S
    HTC Wildfire
    HTC Wildfire S
    HTC Droid Incredible 2
    HTC Thunderbolt
    HTC Desire
    HTC Desire Z
    HTC One X
    LG GT-540 OPTIMUS
    LG Optimus One
    Motorola Triumph
    Motorola Droid X2
    Samsung Galaxy S II Skyrocket (SGH-I727)
    Samsung Galaxy S II (I9100)
    Samsung Galaxy S II (SGH-T989)
    Samsung Galaxy S Plus I9000
    Samsung Galaxy Nexus
    Samssung Galaxy S III (AT&T, Rogers, Bell, Telus)
    Samsung Galaxy S III I9300, I9305
    Samsung Galaxy S 4G
    Sony Ericcson XPERIA X8

    * I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.

    Thanks Section
    While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
    Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
    Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.


    If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)


    REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
    12
    Notes and Info post

    Post consolidation. I'm keeping this post open in case it's needed later.
    7
    Today, AGPS Patch has reached a total number of 28 officially supported devices. Support was added for the Asus Transformer TF101, Samsung's Galaxy Nexus, Samsung's Galaxy S I9000, and HTC's One X.

    I predicted that companies would get wiser and start providing properly built stock ROM's for GPS usage. That was incorrect. I'm willing to research and work with people to bring more devices into the fold.

    There have been millions of downloads of my personal xtra.bin data and tens of millions of queries submitted through the DNS pool I maintain for Stratum II time servers. I lost track of the number of ROM's that have incorporated this patch. In fact, v3.x began 11 months ago and has brought worldwide help to the masses.

    And remember, I don't have to release new versions of this patch locally because it has been so fine-tuned. But, I'm always working on the xtra.bin data almanac and the Stratum II time servers to keep this thing going strong.

    To the few that have donated to support the many, thank you very much. If anyone would like to continue to support this project for growth in more devices and continual data provisioning, please consider donating as well.
    5
    v1.3 released

    I have released v1.3. A lot of testers have discussed it on threads and people have been clambering to get a hold of it!!! So, I decided to forego the planned release schedule to give it to y'all sooner.

    Changes include reorganized NTP and XTRA servers and some removed variables.

    The next version, v1.4, will be a major release change. So, I'm thinking it should be a v2.0.

    The planned release following v1.4 (or, v2.0) will also be a major release. It will contain a surprise. Many ROM dev's are excited about it. It may be considered a major release as well.

    Don't forget to click "Thanks" and to donate. Why donate? Well, assuming I can release the second planned release (above), it will require some money for upkeep. Now you are all really curious!!! :D
    5
    NEW VERSION(S) OUT!

    v2.2 is updated. There were bad ZIP links for which I apologize for. Further, I added some new BUILDS. These builds can work on all phones no matter what your manufacturer is. However, some manufacturers provide SUPL data for their hardware. I'm helping you take advantage of multiple SUPL SERVER providers.

    v3.0 is here! What does this mean for you?
    I provide you with my very own xtra.bin file. This has led to some beta-testers having INSTANT locks. I can't promise that, but it works wonderfully for all testers except one person in China.

    Guess what! It costs me money to provide this. Donations would be welcome to cover hosting fees should this work for you.

    What's next for the 3.x trunk?
    You should see v3.1 in a matters of weeks depending on reported success of v3.0. I intend to create my own NTP servers and NTP pools. This may cost a few dollars a month, but should be worth it for all of us.
    Other flashing recoveries may be supported. Right now, I'm only providing for Clockwork Recovery. But, there are two other easy installation methods available aside from CWR in Method #3.

    I've added more notes. Read them if you have issues before posting.

    I've added more information to Method 2 installations.

    Finally, click thanks on this POST if you truly enjoy and appreciate the work! ;)