AGPS Patch HTC Pure 3.1 & 2.2 | Not officially supported - Touch Diamond2, Pure Android Development

AGPS Patch HTC Pure 3.1 & 2.2 | Not officially supported - Touch Diamond2, Pure Android Development

AGPS PATCH FOR HTC PURE USERS
Use this if you're having GPS issues (unreliability, no functionality, etc.)
IMPORTANT: This device is not officially supported. It has a different chipset than the gps.conf patch is intended for. Further, the Froyo Android port does not have GPS available. Some users HAVE indicated this helped with the Gingerbread port. It won't hurt, but may not help.
This patch was created to provide quick GPS locking across North America. But, it has been ported into a worldwide solution 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:
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".
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
(Thank you eagleeyetom for helping make this possible!)
Method 2:
1. Download the patch
2. Copy gps.conf and suplrootcert 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.
3. Reboot the device
4. Review the NOTE section in Post #2.
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)
5. Reboot the device
6. Review the NOTE section in Post #2.
*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:
There are many new builds available. The 1.x trunk only flashed a gps.conf file. Starting with 2.x, more comes along with the package. This provides the SUPLROOTCERT that many ROMs seem not to have. I prefer the Google Specific version myself.
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.
3.x trunk (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 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 (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 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(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 (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)
NOTE(S):
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.
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.
Remember, this has to be reflashed when you update or change ROMs.
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!
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.
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".
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.
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.
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.
IF you have issues with GPS locking in v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance. It has been observed that some ROM's do not have SANE values for missing variables.
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 differenty and 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 theshold. Food for thought.
DO NOT USE any other GPS FIXING SOFTWARE 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.
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.
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.
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.
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.
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://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
AGPS Patch Officially Supported Devices:
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
Acer Iconia
LG Optimus One
Sony Ericcson XPERIA X8
HTC Salsa
HTC Flyer
HTC Evo 3D
*This works on over 15 other devices, at least with certain ROM configurations. I do not officially support those devices as of yet. You may private message me your success story for official support considerations.
(For v1.0) Thanks to Angeldeath for permitting me to take his work and start tweaking it for Inspire users across the continent. Angeldeath made a great series of AGPS patches designed for his HD2 which essentially updated the gps.conf to speed up the locking process. However, those scripts are based upon regions for USA and no general support for North America after v1.0.

Currently: this is a tentative supporting thread for my aGPS patch. Assuming more report success, I will start officially supporting this device.
Please let me know your success rates. Thus far, a few people have sent me messages and emails stating that this patch works great on this device.
As such, I'm thinking it would be good to provide this officially for this device.
This has been used on over 40 devices successfully. I don't offer official support for all devices. Rather, I offer official support once users convince me to do so for that particular device. That happened here.
Statistically, here is part of my post from mid-December on all official threads:
So, let me give you a general update directed to those 3.x trunk users:
My server has automatically generated an xtra.bin file for your GPS excitement 3,980 times since September 26th when the first beta went online to test it out.
My server attempts to build a new version every 30 minutes. Depending on what it can decypher from other xtra.bin sources, it provides a totally fresh xtra.bin approximately every 1.2 hours.
My server has served up over 500,000 xtra.bin files to users like you on XDA since v3.1 was released.
My server continues to provide a reliable NTP pool to v3.x users by directing your phones to a handful of RELIABLE and FAST-RESPONDING NTP servers around the world. This ensures you can travel and not have to switch NTP pools.
Click to expand...
Click to collapse
Enjoy!

Wow, so have you tested this on the TD2? Does it work on any other devices?
You know this is a Windows Mobile device running Android, correct? I'd be curious if any other devices in the port work...
Edit - I don't even know what to do with this, it just seems to be a gps.conf file and a cert... I find it hard to believe that's all that is missing from our port, but I guess it's possible.

arrrghhh said:
Wow, so have you tested this on the TD2? Does it work on any other devices?
You know this is a Windows Mobile device running Android, correct? I'd be curious if any other devices in the port work...
Edit - I don't even know what to do with this, it just seems to be a gps.conf file and a cert... I find it hard to believe that's all that is missing from our port, but I guess it's possible.
Click to expand...
Click to collapse
As you would find, there are 9 officially supported devices which have had many people using it. This device, here, is one that some are swearing makes GPS work very well (better) than it was working before.
It was requested and I offered to bring some support tentatively. If it showed to be valuable to the Android port, I would keep following up as officially supported.
I don't own the device and relied solely on others who kept telling me about it over the past few days.
Yes, it's a gps.conf and a cert. Certs are matched with their SUPL carriers. Further, the gps.conf is tweaked. Lastly, and my favorite, it uses my own NTP pool and my own XTRA.BIN service if the user chooses the 3.x branch.

crypted said:
As you would find, there are 9 officially supported devices which have had many people using it. This device, here, is one that some are swearing makes GPS work very well (better) than it was working before.
It was requested and I offered to bring some support tentatively. If it showed to be valuable to the Android port, I would keep following up as officially supported.
I don't own the device and relied solely on others who kept telling me about it over the past few days.
Yes, it's a gps.conf and a cert. Certs are matched with their SUPL carriers. Further, the gps.conf is tweaked. Lastly, and my favorite, it uses my own NTP pool and my own XTRA.BIN service if the user chooses the 3.x branch.
Click to expand...
Click to collapse
Well our port doesn't even have the userland libraries for proper XTRA support. So no offense, but I honestly don't see how a gps.conf file could magically fix all of our problems...
Unfortunately our issue is quite complex - much more so than a native Android device...
Edit - I'm still going to try this on a Rhodium, but I'm not hopeful. I got all excited at first tho .

arrrghhh said:
Well our port doesn't even have the userland libraries for proper XTRA support. So no offense, but I honestly don't see how a gps.conf file could magically fix all of our problems...
Unfortunately our issue is quite complex - much more so than a native Android device...
Edit - I'm still going to try this on a Rhodium, but I'm not hopeful. I got all excited at first tho .
Click to expand...
Click to collapse
Let me know how it goes. I will followup with the people who had "success" reports. That's intriguing to assume that the libs not being present would add benefit.
Give it a go and let me know just for the hell of it if you wouldn't mind. And if it works on Rhodium, cool.

There is 0 XTRA support in XDAndroid, unless someone has made some MAJOR patches since I last touched the GPS code.
Similarly, I'm 90% positive the SUPL interfaces are nonoperational.
What works on a native Android device isn't necessarily going to work on a port with incomplete functionality.
Someone wrote an improved GPS library for the HD2 which should be backportable to XDAndroid that might give XTRA support (SUPL is a different story - it looks like SUPL might need some RIL cooperation and that stuff is highly undocumented.)
Right now the only way I know to get good GPS performance in XDAndroid is to "preload" the chip by getting a GPS lock in WinMo prior to running HaRET.
Edit: Were you getting reports from GBX0B users or FRX07 users?
It looks like the Gingerbread codebase might be majorly overhauled.

Entropy512 said:
There is 0 XTRA support in XDAndroid, unless someone has made some MAJOR patches since I last touched the GPS code.
Similarly, I'm 90% positive the SUPL interfaces are nonoperational.
What works on a native Android device isn't necessarily going to work on a port with incomplete functionality.
Someone wrote an improved GPS library for the HD2 which should be backportable to XDAndroid that might give XTRA support (SUPL is a different story - it looks like SUPL might need some RIL cooperation and that stuff is highly undocumented.)
Right now the only way I know to get good GPS performance in XDAndroid is to "preload" the chip by getting a GPS lock in WinMo prior to running HaRET.
Click to expand...
Click to collapse
Again, I'd reference my post just above yours in response to arrrghhh.
I find this response from you guys to be very amusing in the sense that if the software libraries aren't present, someone found success.
Let us assume that you cannot support SUPL or XTRA. I wonder if some of the variables were the result of the success.

You have a bunch of "user reports" with no details, concerning an area (gps.conf) where 90% of the "fixes" people post are pure unadulterated placebo effect - Froyo? Gingerbread?
There's NO way that any SUPL or XTRA changes did anything on a Froyo build. I've read through the entirety of the source code for the GPS driver and I can tell you, without any doubt, there is not a shred of working SUPL or XTRA support. Gingerbread is a different story. Maybe these changes are useful on a Gingerbread build.
If these had an effect on Froyo, it was 100% pure placebo effect - the user likely locked in WinMo before booting xdandroid and attributed the success to gps.conf tweaks and not the fact that the GPS was preinitialized in WinMo.

Entropy512 said:
You have a bunch of "user reports" with no details, concerning an area (gps.conf) where 90% of the "fixes" people post are pure unadulterated placebo effect - Froyo? Gingerbread?
There's NO way that any SUPL or XTRA changes did anything on a Froyo build. I've read through the entirety of the source code for the GPS driver and I can tell you, without any doubt, there is not a shred of working SUPL or XTRA support. Gingerbread is a different story. Maybe these changes are useful on a Gingerbread build.
If these had an effect on Froyo, it was 100% pure placebo effect - the user likely locked in WinMo before booting xdandroid and attributed the success to gps.conf tweaks and not the fact that the GPS was preinitialized in WinMo.
Click to expand...
Click to collapse
I'm not trying to get in a pissing match here. I was actually agreeing with you all that if there isn't support there, then there would be as you say now a "placebo effect" if there were anything.
I'm only wondering if it would be possible that the other modifications in the gps.conf aside from the SUPL or XTRA would explain the better performance.
If that is a negative, then it definitely would seem placebo. This was an offering of tentative support to help users wanting to go Android from WinMo based on others experiences.
Sorry to have stirred the pot. If someone out there has tried this patch and had success, feel free to explain it. I've asked those to do so as well so my curiosity can be set to rest.
EDIT: And it would appear that the Gingerbread port was the intended one for supported success. So, there goes that for your other point.

Related

AGPS Patch Salsa 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:
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.
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?
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.
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:
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.
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.
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.
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.
Remember, this has to be reflashed when you update or change ROMs.
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.
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.
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.
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.
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.
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!
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.
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.
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".
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.
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.
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.
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.
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.
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.
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.
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.
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.
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://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
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.
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?
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.

v2.1 is out
Everyone, the latest version is out. It's a minor update.
I put a changelog on the thread now. It's just above the Notes section.
Also, there is a new installation method. You can install via a batch script. It uses adb push behind the scenes to install whatever patch you select from the menu options.

can this be made so you can install from the custom recovery software

gdavies08 said:
can this be made so you can install from the custom recovery software
Click to expand...
Click to collapse
Well, the third method works with Clockwork Recovery. That's how I update this thing. However, I don't know about other Recovery packages. It would require their necessary update.binary and an update.script tuned to that system.

I have released v2.2. Changelog is updated. A new version is out for LG phones. It might work with others just fine as it is only a change in SUPL to LG servers.
Still working on v3.x I promise!

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!

I just added a new flashable ZIP to both current versions. Some users are reporting issues flashing with CWM on the X8. Thanks eagleeyetom for your help as always! I placed this update on all threads so others who may not have had flash success can try it out. Feel free to send me a private message with what recovery app and version you're using, the phone model involved, and whether flashing anything worked.
Method 1 seems to be the best bet for anyone without flashable abilities with these ZIPs. It's a quick adb push script...
v3.1 is still in the works I promise. As stated previously, it'll be a bit longer before I get it out to the public. I hope to have my beta testing community trying it out in a week or so.
Again, v3.0 has all gps.conf variables grouped into sections with small discussion on what they are for. I'll try and replicate this into the v2.2 ZIP files in the near future.

Just thought I'd post an update. The Notes section has been revamped, added, and the Notes / Still Having Problems sections have been consolidated.
I considered adding checksums to the thread. But, I really don't see the need. If people prefer not to trust this, heck with 'em. They can pay $300 for a good standalone GPS unit.
3.1 is still on track.

works really well and locks on quick too.

gdavies08 said:
works really well and locks on quick too.
Click to expand...
Click to collapse
Glad I could be of assistance!!! Just for kicks, what version and what build are you using?

version 3 the cwm flash build installed easy and works well nice work

Version 3.1 is released. If you didn't think it could get any faster, well you may be surprised. Beta-testers are swearing to instant locks. My magic tricks sure do pay off!
Pay off? Speaking of that... There have been 30,000 downloads of v3.0. My server has served over 100,000 xtra.bin downloads. And even though I stated that this costs me money to provide, there's been zero donations since v3.0 was released. A few bucks really can help defray the hosting and provisioning costs I incur to keep y'all running top notch. If each user gave $0.10, that would be worth a whole dediated server for a year. Just sayin'.
Devs: I request that you notate your threads with which version of my patch you're using. If you include v3.x, please note the cost to your user base. Send me a message if you're using the patch so I can keep track and keep you in the loop of any impending changes.
With that, let me know how well this performs for you. I'm interested whether users see an increase in performance over the amazing speed that v3.0 provided.

I wanted to post a few things to the user community.
1. If you're a DEV and are using this in your ROM, please private message me your ROM thread and which version of this patch you're using. This will be useful with tracking, letting you know of updates for your ROM, and supporting users. If you know of this being used in a ROM, and you're not a DEV, you can report it to!
2. Version 3.1 is a great success. Today alone, the xtra.bin has been served 61,441 times to aGPS Patch users. The 3.1 files have been downloaded almost 10,000 times today as well.
3. Updates will continue to occur server-side for v3.1 and beyond. This means that barring any unforeseen issues, v3.1 will stick for some time without a predecessor. As you may have noticed, your xtra.bin and your NTP pool are through me! This means I can keep providing incoming data for you without needing to update the patch to achieve the same changes. Feel free to toss a penny in the pot.
4. Rate the thread! Some threads have been rated nicely. Others have been attacked with +1 ratings by users who failed to read instructions and/or seek help fixing their issues. This gives a bad impression to new users on XDA. I shouldn't be held accountable for hardware, ROM, or other software related issues out of the control of this patch.
5. Let everyone know of your success. If you're using this patch, let people know what ROM, RIL, Radio, and case you're utilizing. This will help greatly in supporting users who want to know what to use this patch with for best results. I only own one device I officially support, so it's hard helping those seeking assistance with those pieces of advice!
Thanks again for being supportive of this project. I'm glad that I could assist many of you with the same GPS issues I was facing. I literally decided not to buy a new GPS for my car after fixing this issue when my first version was release.

First, I want to with everyone a very happy holiday season. I will be sporadic with my responses to any questions or comments here on the aGPS Patch threads for the next three to four weeks.
Things to think about if you're having an issue:
Read all of the Notes Section commentary. I wrote that because so many people continually have the same or similar issue that can be easily resolved.
Remember that any GPS tools from Android Market CAN and usually DO overwrite this patch. Therefore, don't use any. The only thing I recommend if you're wanting to get stats is GPS Status, as referenced hundreds of times by yours truly.
If your getting a weak signal: remove the phone from a case and try again. Try a different ROM as CM users and ROMs derived from CM tend to show problems because of faulty ROM compilation, not this patch. Ensure your build.prop has the right variables. Go outside, try again. Lastly, delete the SUPL server section from the bottom of the gps.conf and try without that. Some models with some ROMs have issues with SUPL...outside of my control.
Post and wait for someone to respond. I'll do my best to get on the forum off and on over the holidays.
So, let me give you a general update directed to those 3.x trunk users:
My server has automatically generated an xtra.bin file for your GPS excitement 3,980 times since September 26th when the first beta went online to test it out.
My server attempts to build a new version every 30 minutes. Depending on what it can decypher from other xtra.bin sources, it provides a totally fresh xtra.bin approximately every 1.2 hours.
My server has served up over 500,000 xtra.bin files to users like you on XDA since v3.1 was released.
My server continues to provide a reliable NTP pool to v3.x users by directing your phones to a handful of RELIABLE and FAST-RESPONDING NTP servers around the world. This ensures you can travel and not have to switch NTP pools.
If you're a DEV and this is used in your ROM, please notify me via private message with a link to your ROM thread. This helps me track issues and keep you up-to-date with any new versions. We both win there!
Finally, if you use v3.x you should remember this isn't free to me. As all of the information above notes "My server...", I foot the bill to keep supplying this data. It's useful as hell to you and to me.
Consider donating a little to help offset server costs AND to help expand provisioning should enough donations come in. You can donate via Paypal by clicking the donate button next to my username on this or any of my posts. Every little bit helps. If you can't, I understand that as well.
Again, thanks everyone. Don't forget to click the Thanks button on my posts should you enjoy what I've got to say...like those amazing numbers cited above for 3.x users.

All threads have had an overhaul that was way overdue.
High points:
Note discussion of what the patch does and what it replaces.
Note confirming ICS support from various users.
Note section has gotten long, but covers most questions I am repeatedly asked.
A total of 9 officially supported new devices.
Download section reminds people to backup their settings. You only need to backup /system/etc/gps.conf and /system/etc/suplrootcert if you have one. But, I never had to revert!
As always, please don't forget to click Thanks if you use or like this patch -AND- don't forget to Rate the thread. Donations are always welcome.

FYI: Method 1, the easiest of the methods for those unfamiliar with file managers or recovery, has been updated. Some people required that the script also mount the partition. I have added that line to all options available and updated the ZIP file. Thanks enigmaamit for confirming that the new PUSH script works.

since you first posted this up and added me into the test group, Ive had nothing but joy from the gps! so quick, great locks, and it does not drop signal like it sometimes does, tested this on 3 different Roms, 2 Chinese and one UK all work fantastic

BigBearEvo said:
since you first posted this up and added me into the test group, Ive had nothing but joy from the gps! so quick, great locks, and it does not drop signal like it sometimes does, tested this on 3 different Roms, 2 Chinese and one UK all work fantastic
Click to expand...
Click to collapse
Awesome! Glad I've convinced a few people of this patch's ability.

Just a friendly notice that the thread has been updated.
There is a new build which I recommend. Before questioning or inquiring why I removed the use of SSL, review the NOTE on the matter. This has proven to be a faster operation by tests in various regions and numerous devices.
Lastly, I added a section for asking questions. Review that before communicating here. It gets really old seeing that people refuse to read what I've worked hard to write especially when it usually answers the questions asked.
Don't forget to consider donating if you appreciate the work and find it useful.

Thread kind of updated to include a new device:
Asus Transformer Prime
This patch can be useful on devices that need the GPS XML file which is prevalent in non-Qualcomm chipsets. So, it can be used in other devices as well.
The new release has no effect on other supported devices unless it is a non-Qualcomm phone.

AGPS Patch 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 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:
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.
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?
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.
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:
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.
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.
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.
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.
Remember, this has to be reflashed when you update or change ROMs.
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.
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.
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.
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.
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.
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!
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.
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.
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".
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.
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.
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.
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.
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.
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.
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.
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.
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.
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://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
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.
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?
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
Samsung 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.

Currently: this is a tentative supporting thread for my aGPS patch. Assuming more report success, I will start officially supporting this device.
Please let me know your success rates. Thus far, a few people have sent me messages and emails stating that this patch works great on this device.
As such, I'm thinking it would be good to provide this officially for this device.
This has been used on over 40 devices successfully. I don't offer official support for all devices. Rather, I offer official support once users convince me to do so for that particular device. That happened here.
Statistically, here is part of my post from mid-December on all official threads:
So, let me give you a general update directed to those 3.x trunk users:
My server has automatically generated an xtra.bin file for your GPS excitement 3,980 times since September 26th when the first beta went online to test it out.
My server attempts to build a new version every 30 minutes. Depending on what it can decypher from other xtra.bin sources, it provides a totally fresh xtra.bin approximately every 1.2 hours.
My server has served up over 500,000 xtra.bin files to users like you on XDA since v3.1 was released.
My server continues to provide a reliable NTP pool to v3.x users by directing your phones to a handful of RELIABLE and FAST-RESPONDING NTP servers around the world. This ensures you can travel and not have to switch NTP pools.
Click to expand...
Click to collapse
Enjoy!
EDIT: First post has been updated to reflect all standard data on officially supported device threads. Changelog and Notes Section is here...

Just a friendly notice that the thread has been updated.
There is a new build which I recommend. Before questioning or inquiring why I removed the use of SSL, review the NOTE on the matter. This has proven to be a faster operation by tests in various regions and numerous devices.
Lastly, I added a section for asking questions. Review that before communicating here. It gets really old seeing that people refuse to read what I've worked hard to write especially when it usually answers the questions asked.
Don't forget to consider donating if you appreciate the work and find it useful.

Thread kind of updated to include a new device:
Asus Transformer Prime
This patch can be useful on devices that need the GPS XML file which is prevalent in non-Qualcomm chipsets. So, it can be used in other devices as well.
The new release has no effect on other supported devices unless it is a non-Qualcomm phone.

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.

Official support has is now available for more devices. This brings the total officially supported to 32.
Welcome these newbies to the fold:
Samsung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Asus Transformer TF300T
Motorola Droid X2
Samsung Galaxy S 4G
If you appreciate this growing work, always consider clicking the Thanks.
Remember that I pay monthly hosting fees for the space and bandwidth necessary to keep this patch working on the backend. So, please consider donating a few bucks if you're a user. All donations go directly to the patch provisioning and there is absolutely no overhead to benefit me.

TopNTP - the app.
This app does installs a customized gps.conf file for your GPS. It has several different profiles to choose from. We recommend to use the default Google profile but it is up to you. Appart from the profiles you can customize the one chosen.
NTP servers
Derek Gordon maintains a special NTP server pool for you. Dispite what everyone thinks, it is not necessarily the one closest to you which is the best. We consider Derek Gordon's server to be the best option to choose because it has the best data and is most frequently updated.
For more information about the NTP server check out the "About this app" section found under the settings of this app. Also, feel free to visit derekgordon.com for more in depth information.
aGPS Alamanacs
Derek Gordon maintains a special aGPS almanac for devices using Qualcomm or similar chipsets. This xtra.bin data file is updated every 30 minutes and is located on a content delivery system maintained by the generous donations of ther userbase.
For more information about the NTP server check out the "About this app" section found under the settings of this app. Also, feel free to visit derekgordon.com for more in depth information.
Donations
To maintain the server we need money. Donations through this app will be divided between Derek Gordon (Crypted) and Zatta on XDA.
Each star costs 2 Euro and will reduce the waiting time before you can install the patch. 0 star users wait 20 seconds, 1 star users 10, 2 star users only 5 and 3 star users and Premium users can install immediately.
You can become a premium user for only 5 Euro. This is a discount of 1 euro compared to a three star user! We choose this method to allow every one to use all features of this app and because we believe in XDA developers users. Please, don't leech!
Backup and restore
On the first run of this app a backup is made on your SD card. Don't remove it because a backup is only made during the first run (or at an update if you choose to remove it anyway) and no other backup is found on your SD card.
ROM updates
The patch this app provides is located on your /system partition so every time you do update your ROM the patch is overwritten and you will have to redo the patch.
Unless you are using a Cyanogenmod based ROM and your rom has addon.d support. In that case a script will be placed in the addon.d directory to preserve the patch.
It can be disabled in the app's settings but is enabled by default.
Asus users
On ASUS roms a typical file is present at /system/etc/gps, namely the gpsconfig.xml file. This app pathes that file as well, to be specific the PeriodicTimeOutSec parameter. Of course a backup is made of this file as well.
Click to expand...
Click to collapse
We need bèta testers. Hopefully we can get some useful feedback to optimize this app. The patch itself has been proven to work, we just need to know for as much as possible devices if we can a) really install the patch and b) if the app is sort of clear in its use.
Get it on Google Play!

Hi Crypted,
Does this fix also work on MTK6577 or MTK6789 cellphones? There are now many chinese clone phones, but people say that many of them have GPS fix problem.
Thanks for your work.

ydur1 said:
Hi Crypted,
Does this fix also work on MTK6577 or MTK6789 cellphones? There are now many chinese clone phones, but people say that many of them have GPS fix problem.
Thanks for your work.
Click to expand...
Click to collapse
Tha app should as long as the device is rooted. If you try, please let me know the results.

Hi Zatta, I am asking about GPS fix because I am looking for another phone. I think it will be a MTk6577 or MTK6589 device. I read on internet that the MTK devices have problem with GPS. Can you or someone else confirm this?
Thanks
Ruud

ydur1 said:
Hi Zatta, I am asking about GPS fix because I am looking for another phone. I think it will be a MTk6577 or MTK6589 device. I read on internet that the MTK devices have problem with GPS. Can you or someone else confirm this?
Thanks
Ruud
Click to expand...
Click to collapse
If the gps is very important for you, then don't rely on any fix. If the hardware is crap than the software can't compensate for that. I don't have that device (and never heard of it) so I can't say anything more about the results of the gps, patched software or not.
Groetjes!
Edited for Autocorrect failures :S
Taptalked u see .. əəs n pəʞlɐʇdɐʇ

ydur1 said:
Hi Zatta, I am asking about GPS fix because I am looking for another phone. I think it will be a MTk6577 or MTK6589 device. I read on internet that the MTK devices have problem with GPS. Can you or someone else confirm this?
Thanks
Ruud
Click to expand...
Click to collapse
We don't have those devices to confirm with. Just install the APK and see what happens.

I confirm it works alright on NEO n003. Which, by the way has MTK6589T QuadCore CPU, so one of the questions above answered too.
Thanx a bunch bro!
:good:

mtk6589 UMI X2
pederzen said:
I confirm it works alright on NEO n003. Which, by the way has MTK6589T QuadCore CPU, so one of the questions above answered too.
Thanx a bunch bro!
:good:
Click to expand...
Click to collapse
Testing on

Working on UMI X2 MTK6589 LIGHTNING V7 ROM.
VERY THANK'S
Enviado desde mi UMI X2 usando Tapatalk

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

AGPS Patch Wildfire 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 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:
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.
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?
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.
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:
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.
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.
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.
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.
Remember, this has to be reflashed when you update or change ROMs.
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.
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.
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.
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.
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.
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!
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.
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.
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".
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.
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.
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.
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.
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.
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.
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.
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.
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.
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://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
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.
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?
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
Samsung 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.

Currently: this is a tentative supporting thread for my aGPS patch. Assuming more report success, I will start officially supporting this device.
Please let me know your success rates. Thus far, a few people have sent me messages and emails stating that this patch works great on this device.
As such, I'm thinking it would be good to provide this officially for this device.
This has been used on over 40 devices successfully. I don't offer official support for all devices. Rather, I offer official support once users convince me to do so for that particular device. That happened here.
Statistically, here is part of my post from mid-December on all official threads:
So, let me give you a general update directed to those 3.x trunk users:
My server has automatically generated an xtra.bin file for your GPS excitement 3,980 times since September 26th when the first beta went online to test it out.
My server attempts to build a new version every 30 minutes. Depending on what it can decypher from other xtra.bin sources, it provides a totally fresh xtra.bin approximately every 1.2 hours.
My server has served up over 500,000 xtra.bin files to users like you on XDA since v3.1 was released.
My server continues to provide a reliable NTP pool to v3.x users by directing your phones to a handful of RELIABLE and FAST-RESPONDING NTP servers around the world. This ensures you can travel and not have to switch NTP pools.
Click to expand...
Click to collapse
Enjoy!

Very nice, was a little bit off whilst in the house(about 15ft) but just popped out for a smoke and got a lock on Google maps within 5 seconds and it was accurate to within a foot, before flashing this it took nearly a minute and was never where I actually was.
[Q] how do I see how many sats I'm connected to?
I'd just like to see a before and after as I'm curious about everything.
Sent from my HTC Wildfire using xda premium

try app GPS Status...there is count of sats you are connected to

Scratch0805 said:
Very nice, was a little bit off whilst in the house(about 15ft) but just popped out for a smoke and got a lock on Google maps within 5 seconds and it was accurate to within a foot, before flashing this it took nearly a minute and was never where I actually was.
[Q] how do I see how many sats I'm connected to?
I'd just like to see a before and after as I'm curious about everything.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Glad it works for you.
B3!CrAZy said:
try app GPS Status...there is count of sats you are connected to
Click to expand...
Click to collapse
Definitely, I only recommend GPS Status because it is the only App that I am 100% sure does not interfere at all with this patch. Plus, it gives you enough general info to know how your setup is performing.
Other info tools, including GPS Fix, just overwrite the patch with its own internal junk that isn't worth much. Then, I end up with users wanting me to help them without telling me this and a lot of time and effort is wasted only to find they did not read the Notes Section.

i think it works for me too...17 sec to fix sats

B3!CrAZy said:
i think it works for me too...17 sec to fix sats
Click to expand...
Click to collapse
Let GPS Status run for about two minutes. Then, reboot and try again. It should get faster than that.
Glad it's helping you, though. 17 seconds, whew, I'd be going insane!

When using the ADB scrip without any pre-preparations it fails, because it doesn't set the /system folder to read/write.
Also the reboot option inside the ADB scrip doesn't reboot

nejc121 said:
When using the ADB scrip without any pre-preparations it fails, because it doesn't set the /system folder to read/write.
Also the reboot option inside the ADB scrip doesn't reboot
Click to expand...
Click to collapse
Odd. It still works with the device I have. I cannot guarantee it to work outside of my device for pushing. That's why I provide details for three methods of installation.
Personally, I typically use the flash method via recovery (CWR or EXT4 on my Inspire 4G).
Anyway, I'll see about updating that ADB offering but I'll have to solicit some others with different setups to make sure we're on par.
That aside, how did the patch work for you?

M
crypted said:
Odd. It still works with the device I have. I cannot guarantee it to work outside of my device for pushing. That's why I provide details for three methods of installation.
Personally, I typically use the flash method via recovery (CWR or EXT4 on my Inspire 4G).
Anyway, I'll see about updating that ADB offering but I'll have to solicit some others with different setups to make sure we're on par.
That aside, how did the patch work for you?
Click to expand...
Click to collapse
I must say that this works very well!
Took about 10 seconds from the install in GPS status for the GPS to lock on!
ROM: Cyanogenmod Nightly ErwinP build 1.
Update: I must say this is amazing. 3 second fix in the open.
4-5 second in a car (moving)

about improved gps fix
i tested this out and here are my results. the speed increase is remarkable. when im outside lock on my location only took 2 seconds! doesnt work when im indoors but it nerver has here
my old lock on used to take between 10 and 20 seconds
this is amazing and thank you so muck =1 thanks lol
device specs.
htc buzz
cyanogenmod 7.10.1
hboot 0.80.0002
kernal 2.6.35.14-nFinity arcos

Just tried it on my phone, blazing fast, about 8 seconds with agps.
Great stuff! Flashed the generic Google one, just so you know.

Tried with Google Maps... Position found in 5 sec...
I took me more than 10 minutes before!
So what to say except nice one and many thanks for sharing that!!!
I just have some question as I am a complete noob with gps stuff :
Who is behind derekgordon?
Who is behind xtra3(/2).gpsonextra.net?
Is the 'xtra.bin' source code available somewhere?
(I've seen some informations are in the file gps.conf...)
Again, thank you

lemmoned said:
Tried with Google Maps... Position found in 5 sec...
I took me more than 10 minutes before!
So what to say except nice one and many thanks for sharing that!!!
I just have some question as I am a complete noob with gps stuff :
Who is behind derekgordon?
Who is behind xtra3(/2).gpsonextra.net?
Is the 'xtra.bin' source code available somewhere?
(I've seen some informations are in the file gps.conf...)
Again, thank you
Click to expand...
Click to collapse
Glad it's working for you. I own derekgordon.com and run the DNS NTP pool and the system that produces the xtra.bin for download.
The other source (gpsonextra.net) is Qualcomm-related and provides the xtra.bin to all devices using Qualcomm chipsets assuming they have the proper gps.conf configuration to obtain the data.
The source code is not available at this time.

Ok, so I tested with and without earlier using gps status.
Without I found 2 sats and gave up waiting for a fix after about 7 minutes but with I found on and off between 8 and 12 sats and managed to get a fix on 9 of them in less than a minute, the first fix came within 10 seconds so once again thanks this is awesome, went out for a drive too, Google maps struggled a little when I nailed the throttle but caught up fast when I slowed down. For the first time since I got it, my wildfire can be used reliably as a navigation tool.
Sent from my HTC Wildfire using xda premium

Scratch0805 said:
Ok, so I tested with and without earlier using gps status.
Without I found 2 sats and gave up waiting for a fix after about 7 minutes but with I found on and off between 8 and 12 sats and managed to get a fix on 9 of them in less than a minute, the first fix came within 10 seconds so once again thanks this is awesome, went out for a drive too, Google maps struggled a little when I nailed the throttle but caught up fast when I slowed down. For the first time since I got it, my wildfire can be used reliably as a navigation tool.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Mmmmmm interesting mate, regarding my earlier chat with you about this, I'm not sure I'm gonna need this cos I've been using my phone alot for sat nag recently and although the lock isn't as fast as you mention it never lags whilst driving(maybe I need a faster car lol) I will try ur suggestion of version anyway and see tomoz.
Edit: ok flashed Google specific cwm version successful, cwm 3.2.0.0 HTC wildfire running cm7#255/6 no lock indoors but will test outdoor tomoz. Normal lock time for me previous was around 15 seconds. Cheers.
"sent from me2u"
Edit2: ok not much difference on lock time for me. i did the gps status test and it was connected to 11 out of 12 sats found which i think is a good sign. i never tested before the flash so cant really compare. gonna keep this installed due to the possitive feedback from everyone and the report from gps status.
anyway thanks alot and i can also confirm cwm 2.5.0.7 google specific cm7 #255/6

All threads have had an overhaul that was way overdue.
High points:
Note discussion of what the patch does and what it replaces.
Note confirming ICS support from various users.
Note section has gotten long, but covers most questions I am repeatedly asked.
A total of 9 officially supported new devices.
Download section reminds people to backup their settings. You only need to backup /system/etc/gps.conf and /system/etc/suplrootcert if you have one. But, I never had to revert!
That being said, welcome to official support. Thank you all who confirmed and worked with me to ensure it was proper to offer official support to this device.
As always, please don't forget to click Thanks if you use or like this patch -AND- don't forget to Rate the thread. Donations are always welcome.

Scratch0805 said:
but with I found on and off between 8 and 12 sats and managed to get a fix on 9 of them in less than a minute, the first fix came within 10 seconds
Click to expand...
Click to collapse
My stats are similar to yours. I've also had a quick sign of major improvement by noticing that I'm now able to get a lock from the terrace (yep also been out for a smoke for testing LOL). Without the patch I had to move away from the house 3 or 4 mtrs. at least to get a lock. I even get a quick lock now from inside - at the window - woot.
slymobi said:
although the lock isn't as fast as you mention it never lags whilst driving(maybe I need a faster car lol)
Click to expand...
Click to collapse
Whilst driving it also had been ok for me before - most of the time at least - and as you probably know we still have roads without speed limits here
B3!CrAZy said:
try app GPS Status...there is count of sats you are connected to
Click to expand...
Click to collapse
thx for that one - that's what I've been looking for a while ago without success...
For the record: Wildfire on CM7 nightly.

I'm glad this is helping everyone with GPS on the Wildfire.
FYI: Method 1, the easiest of the methods for those unfamiliar with file managers or recovery, has been updated. Some people required that the script also mount the partition. I have added that line to all options available and updated the ZIP file. Thanks enigmaamit for confirming that the new PUSH script works.

This is most likely one of the best patches ever made for the Wildfire!
A truly thank you from Belgium! First time it took 20seconds to get a fix,
after that it took only 2-3 seconds, wherever I am. Awesome!

AGPS Patch Galaxy S III 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, LOCK EXTRA 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.
Galaxy S III Specific Build(s)
Galaxy S III Test 2 (Like it? Don't forget to click on "Thanks" and to rate the thread)
Please comment if this helps better than the Generic. It appears to resolve MANY problems for the Verizon variant. Expect a few minutes for initial lock with very fast and accurate locks after that.
Galaxy S III Test 3 (Like it? Don't forget to click on "Thanks" and to rate the thread)
Please comment if this helps better than the Generic. It appears to resolve MANY problems for the Verizon variant. Expect a few minutes for initial lock with very fast and accurate locks after that.
Galaxy S III Test 2 ALT (Like it? *Don't forget to click on "Thanks" and to rate the thread)
Please comment if this helps better than the Generic. *It appears to resolve MANY problems for the Verizon variant. *Expect a few minutes for initial lock with very fast and accurate locks after that.
Galaxy S III Test 3 ALT (Like it? *Don't forget to click on "Thanks" and to rate the thread)
Please comment if this helps better than the Generic. *It appears to resolve MANY problems for the Verizon variant. *Expect a few minutes for initial lock with very fast and accurate locks after that.
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Unfortunately, it looks like S3 has taken a nose dive into the past and this might be why some are seeing such issues. Try this if you have problems with the standard patch series.
Generic 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:
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.
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?
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.
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:
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.
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.
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.
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.
Remember, this has to be reflashed when you update or change ROMs.
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.
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.
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.
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.
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.
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!
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.
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.
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".
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.
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.
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.
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.
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.
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.
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.
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.
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.
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://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
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.
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?
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.

Here are some things you can do if you're having problems with the S3.
With no GPS icon showing up
(OPTIONAL AND RECOMMENDED: USE Triangle Away to reset counter)
1. Flash back to stock UNROOTED ICS ROM
(Stuck at samsung logo after? flash a cwm recovery, factory reset and clear cache n reboot)
2. Enter into dialer *2767*3855# (Will do a HARD reset, no internal storage will be lost except the usual data)
3. Boot up again and run maps to see if you have a GPS icon
(IF YOU DON NOT HAVE A GPS ICON YOUR HARDWARE IS MALFUNCTIONING)
With GPS icon showing but no lock
4. Turn all GPS related thing OFF
5. go into google services framework in applications, settings, and clear data
6. go into maps, delete updates if any and clear data aswell
7. reboot the phone
8. Update google maps (very important)
9.reboot for safe measure
10. turn on everything in location and services in settings
11. boot up maps
12. profit
If GPS is still flashing but no lock
1. If steps1-11 does not work for you it is highly recommended to flash Galaxy S III Test 3 (created by crypted)
2. Factory reset trough settings and repeat steps 1-3 if not gps icon or steps 4-11 if gps icon flashes
3. profit
For flashing new ROMs after the above series:
1. see if gps is showing up or not, if not then repeat steps 1-12 above and it is recommended not to flash the same rom that makes gps disappear
2. if gps icon is showing up but very inaccurate then repeat steps 4-11
This patch will work only when your device is properly working. It appears a lot of people are forgetting that fact. Bad ROMs, bad cache, and bad flashing aren't going to be fixed by a GPS configuration alteration.
Thanks to egyptshun for the above information. There's only so much I can do without a S3.

I get about 18 satellites locked and a fix in 2sec on my international I9300 without any mod.
Any way maybe help other people's in other countrys.
Thank's

ausdim said:
I get about 18 satellites locked and a fix in 2sec on my international I9300 without any mod.
Any way maybe help other people's in other countrys.
Thank's
Click to expand...
Click to collapse
A number of users experience GPS issues especially with custom ROMs. Some devices and some setups just need a little repair.
There are times that the most notorious phones for horrible GPS reception will have a golden nugget out there that works perfectly all the time. Maybe you have one of those...

Hmm...
Didn't know that.
So for sure this will help some user's.
Maybe i will test it also.
Thank's again.

ausdim said:
I get about 18 satellites locked and a fix in 2sec on my international I9300 without any mod.
Thank's
Click to expand...
Click to collapse
As many do .
But for those withe poor lock its a useful bit of kit that i for one would not be without .
jje

ausdim said:
I get about 18 satellites locked and a fix in 2sec on my international I9300 without any mod.
Any way maybe help other people's in other countrys.
Thank's
Click to expand...
Click to collapse
Not to nitpick but isn't the most you should be able to see at any one time 12?
Anyway this looks a fantastic resource. My i9300 international is reporting a lock of 11 indoors at present but I'll be interested to see how others get on. I wasn't aware the i9300 had GPS problems.

MSRemmert said:
Not to nitpick but isn't the most you should be able to see at any one time 12?
Anyway this looks a fantastic resource. My i9300 international is reporting a lock of 11 indoors at present but I'll be interested to see how others get on. I wasn't aware the i9300 had GPS problems.
Click to expand...
Click to collapse
Again, Verizon's S3 users ended up using this and it works for them. I brought it to this forum as well in case there were some users needing a solution. Normally, people don't just stumble onto this patch by happenstance unless it's in their normally viewed forums.
As far as the # of satellites is concerned, a lot of newer devices are bringing support for GLONAS and the EU's satellite constellations. Further, this patch allows for intermediate "locks" which means satellites that aren't fully within your line of sight. GPS signals bounce and this allows your device to selectively use those signals that fall below an error threshold.

crypted said:
Again, Verizon's S3 users ended up using this and it works for them. I brought it to this forum as well in case there were some users needing a solution. Normally, people don't just stumble onto this patch by happenstance unless it's in their normally viewed forums.
As far as the # of satellites is concerned, a lot of newer devices are bringing support for GLONAS and the EU's satellite constellations. Further, this patch allows for intermediate "locks" which means satellites that aren't fully within your line of sight. GPS signals bounce and this allows your device to selectively use those signals that fall below an error threshold.
Click to expand...
Click to collapse
I stand corrected.

So does these setting depends on the derekgordon.com (yours I presume) to be up?
I downloaded the google cwm one and the conf has only 1 NTP server, which is yours.

priyana said:
So does these setting depends on the derekgordon.com (yours I presume) to be up?
I downloaded the google cwm one and the conf has only 1 NTP server, which is yours.
Click to expand...
Click to collapse
Not to be a complete turd, but do you make a habit of NOT reading the Notes Sections on threads?
Read it.
EDIT: For the hell of it, I would recommend Notes 2, 6, 7, and 8 to cover your concerns. Other Notes go into other details as they SHOULD be doing.

First thing I install on any new ROM - a must-have, and has always worked flawlessly. Many thanks again

crypted said:
Not to be a complete turd, but do you make a habit of NOT reading the Notes Sections on threads?
Read it.
EDIT: For the hell of it, I would recommend Notes 2, 6, 7, and 8 to cover your concerns. Other Notes go into other details as they SHOULD be doing.
Click to expand...
Click to collapse
Thanks for that.
Yeah, I must admit I have attention deficiency especially when the notes section goes to 25 points.
Sorry for that.
Sent from my GT-P1000 using xda app-developers app

Nice to see you here Crypted. I was one of your old DHD users and your patch definitely made the rubbish GPS on the DHD so much better.
The GPS on the S3 is actually pretty good, so the benefits of using your patch won't be as obvious as compared to the DHD, but still, a small speed benefit is better than none.

B3311 said:
First thing I install on any new ROM - a must-have, and has always worked flawlessly. Many thanks again
Click to expand...
Click to collapse
lukesky said:
Nice to see you here Crypted. I was one of your old DHD users and your patch definitely made the rubbish GPS on the DHD so much better.
The GPS on the S3 is actually pretty good, so the benefits of using your patch won't be as obvious as compared to the DHD, but still, a small speed benefit is better than none.
Click to expand...
Click to collapse
Thank you both for the kind words. I hope it does bring at least some benefit to you all.
priyana said:
Thanks for that.
Yeah, I must admit I have attention deficiency especially when the notes section goes to 25 points.
Sorry for that.
Click to expand...
Click to collapse
I know there are a number of Notes, but I got very tired of responding 10,20,30 times to the same questions. Each Note was created because of extremely repetitive inquiries.
This isn't a full-time job, so I don't have the luxury of giving the great tech support answers some garner from the 1800 numbers.

MSRemmert said:
Not to nitpick but isn't the most you should be able to see at any one time 12?
Anyway this looks a fantastic resource. My i9300 international is reporting a lock of 11 indoors at present but I'll be interested to see how others get on. I wasn't aware the i9300 had GPS problems.
Click to expand...
Click to collapse
The international versions supports gps and glonas (Russian gps) at the same time, that's why there are more satellites and the fix is faster, guess the American only supports gps.
@OP thx anyway for sharing, maybe helpful for some with problems
But just out of curiosity, does the device still use both systems after applying the patch or just gps?
Sent from my GT-I9300 using Tapatalk 2

I get 16 satellite lock within 5 seconds stock here in Australia. Using faster fix... even faster. I guess some countries are not so lucky?
Sent from my GT-I9300 using xda premium

rlorange said:
I get 16 satellite lock within 5 seconds stock here in Australia. Using faster fix... even faster. I guess some countries are not so lucky?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Getting a fix of 9 satellites within 15 seconds at my toilet (no window and no outer wall) in Austria^^
And 11 at the living room within 5 seconds (window and outer wall, but not standing at the window).
Sent from my GT-I9300 using Tapatalk 2

rlorange said:
I get 16 satellite lock within 5 seconds stock here in Australia. Using faster fix... even faster. I guess some countries are not so lucky?
Click to expand...
Click to collapse
Countries are irrelevant unless it boils down to a firewall blocking your access to aGPS data (as it's online).
Fasterfix doesn't work well with this patch as the Notes Section discusses so I assume you're implying that you are not using this patch at all. Therefore, I don't see why you're posting here.
Tectas said:
Getting a fix of 9 satellites within 15 seconds at my toilet (no window and no outer wall) in Austria^^
And 11 at the living room within 5 seconds (window and outer wall, but not standing at the window).
Click to expand...
Click to collapse
Are you saying that you're getting that amount without the patch or with the patch?
The patch isn't necessary in every circumstance. Some ROM's and sometimes the phone itself just cannot perform well as far as GPS is concerned. This patch can eliminate a number of issues except where the source is screwed up or hardware is failing.

crypted said:
Are you saying that you're getting that amount without the patch or with the patch?
The patch isn't necessary in every circumstance. Some ROM's and sometimes the phone itself just cannot perform well as far as GPS is concerned. This patch can eliminate a number of issues except where the source is screwed up or hardware is failing.
Click to expand...
Click to collapse
At the reported times i haven't, sry, but i have tested it now a bit.
First of all, tried both 3.1 google packages, both produced an error with status 0 at cwm touch 6.0.1.2.
Applied the fix afterwards with x-plorer without problems though.
After applying it, i got a fix of 11 satellites in about 8 seconds as average.
Without fix i got also a fix of 11 satellites, but within 5 seconds average.
But, with fix it has been more stable, it stayed almost at the fix of 11 only jumped one or two satellites up or down.
Without it hasn't been as stable, it even dropped to 7 satellites, only for about 100 milliseconds, but still.
Glonass seems also to be used still, because for short it also had 13 satellites.
Sent from my GT-I9300 using Tapatalk 2

Database Develop

welcome