AGPS Patch Galaxy S II 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO MORE SAT

Search This thread

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
AGPS Patch Galaxy S II 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO MORE SAT

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


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

AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
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.
 
Last edited:

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
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:
  1. 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. :eek:
  2. 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.
  3. My server has served up over 500,000 xtra.bin files to users like you on XDA since v3.1 was released.
  4. 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.

Enjoy!
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
Seems to have worked on my GS2, atleast its getting the GPS lock faster now than before (altho, it wasn't slow before)

Anyway, i decided to help you out with the xtra.bin, and have created a cronjob to get it from your server, once every hour, and store it at http://eve-kill.net/xtra.bin

Feel free to use it aswell :)
Server is in Holland on a 1/1Gbit connection :)

Thanks for the info. I might end up calling on you if the load gets overbearing. Heck, it if we keep needing this an Europe starts showing latency, I'll definitely hit you up to do that officially.

Glad it's working for you even though you didn't have issues before! :D
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
Hey man,
sounds good, will definately give your gps.conf a try. I am on CM7 self compiled KANG for the S2. I just checked build.prob and it doesn't contain the variable you mentioned in your FAQ "ro.ril.def.agps.mode".
Should I add it, or should this work also without that variable set?
Also, I'd like to know if this patch could also improve GPS accuracy, that is reported in apps lke GPS Test or others. I used to have 5-10m accuracy with samsung based roms, but this went up to 10-20m with CM7. Might only be a placebo effect, but well. Lower sounds better to me ;-)

Thank you for reading the Notes section first! You should be okay without the variable. If you aren't pleased with results, you can always toss it in later.

This patch normally improves speed and accuracy. On my device, it took 1 - 2 minutes to lock with an error of about 20 - 30 meters. With the patch, I lock in under 7 seconds with accuracy at around 3 meters. Some get even better with better phone hardware.
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
Alright man will give see how my gps performs when driving home later. Btw, I downloaded and flashed the Google specific 3.x Trunk version, though not the "CWM" flashable ... accidently, but it flashed just fine via CWM, why's that? Whats the difference in the other version that has CWM in the zip filename?

boba

Some phones cannot flash cwr. via cwm so the different version was to accommodate those users. I was baffled by that issue as all was fine for other devices including mine.

Sent from my Desire HD using XDA App
 

lutanica

Senior Member
Jul 9, 2008
392
34
Well I couldn't test too much, just right in front of the office building here while having a smoke ;-) locked pretty quickly onto 10 sattelites, though as I said I stood right in front of a 100 feet+ building. Error though was min. 10 metres, but that might be due to the large obstacle right in front of me ....

boba

Mate, which file did you install? And how did you install it? Cause I too use CM7.2 and I didn't see improvement.
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
Mate, which file did you install? And how did you install it? Cause I too use CM7.2 and I didn't see improvement.

Which patch build did you use? If you're not having luck with the standard Google build, try the Alternate. It might be that something is prohibiting a more advanced feature from working properly.

Some CM builds have issues as the Notes section discussed. I don't use and won't use CM on my device because I was annoyed with the recurring problems.

Don't forget to describe your environment and the actual results you receive. I can't be of help without anything to go on.

Lastly, cases can really screw up GPS reception.
 

eRajesh

Senior Member
Jul 15, 2010
649
203
Kolkata
What does this mod exactly do as in what all system file modifications does it do? I hope it does not only change the GPS server settings like thousands of other mods do?
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
What does this mod exactly do as in what all system file modifications does it do? I hope it does not only change the GPS server settings like thousands of other mods do?

It depends on which version you choose. If you use version 1.x, it does what you describe and only modifies the gps.conf.

If you use v2.x, it modifies the gps.conf and provides actual certificates necessary to connect and utilize specific SUPL servers in each build.

If you use v3.x, it does all of the above and adds two other pieces that have proven the most beneficial. It utilizes my own DNS pool for NTP servers. I select servers based on response times to various cellular networks with the help of people all around the globe. Lastly, it uses my own servers to provide an xtra.bin that proves much more responsive and downloads much faster to devices all around the globe because of better peering.

There are few nuts and bolts modified in the gps.conf compared to other patches as well.

I think you'd be pleased if you gave v3.1 a try.
 

mecss

Senior Member
Jan 10, 2011
106
244
Hamburg
First of all I want to thank you for your patch. It works awesome for me. Before this patch I had only 1-2 sats in my study but by this patch I have now 5-7 used sats and very fast fixing. I used agps.patch.google.build.cwm.v3.1. myself and can not enough to thank you...:)
 

cmd512

Senior Member
Aug 25, 2009
3,348
841
Shanghai
Just a quick sanity check: Given I do a lot of international travel for business, the Google build would be the best for me given it doesn't necessarily favor the US carriers, correct?

Many thanks in advance! :)
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
Just a quick sanity check: Given I do a lot of international travel for business, the Google build would be the best for me given it doesn't necessarily favor the US carriers, correct?

Many thanks in advance! :)

Definitely. Over the holidays, I got instant locks in four different cities in Peru. It has worked in travels to Europe as well.

Google build will do fine. Actually, all of them should do fine... But, I only recommend the Google build to the standard user.
 
  • Like
Reactions: cmd512

cmd512

Senior Member
Aug 25, 2009
3,348
841
Shanghai
Definitely. Over the holidays, I got instant locks in four different cities in Peru. It has worked in travels to Europe as well.

Google build will do fine. Actually, all of them should do fine... But, I only recommend the Google build to the standard user.

Excellent, most of my travels take me to Asia, so I'll test this out during a whirlwind tour of Japan, Taiwan, and China I have coming up shortly.

Even though you're from Oklahoma, thanks given for your general disdain of Apple(s). :D
 

LaMaaH

Senior Member
Jul 7, 2007
77
81
Thanks for the info. I might end up calling on you if the load gets overbearing. Heck, it if we keep needing this an Europe starts showing latency, I'll definitely hit you up to do that officially.

Glad it's working for you even though you didn't have issues before! :D

np :)
It's still getting the file from you every hour, since i've altered your config to use it :)

Also, the one i installed was the Google Specific CWM download.
And this is an image from earlier today.

Worked great when i actually went outside, ~20 seconds and it had 4 sattelites, not 20 seconds later, this :p (Wasn't really outside, it was from the window of a moving bus, so "outside")
20120116_151056.jpg
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
probably a NOOB question but is this compatible with ICS? recommended?

I have had only success reports for.ICS and this patch. However, those are reports for only three devices. There should be no reason that it wouldn't work based on what was said. Of you're having issues give it a try and report back. Won't kill the phone... Just make a backup as always recommended.

Sent from my Desire HD using XDA App
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
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.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 304
    AGPS Patch Galaxy S II 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO MORE SAT

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


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

    AGPS Patch Officially Supported Devices:
    Acer Iconia
    Asus Transformer Prime
    Asus Transformer (TF101)
    Asus Transformer TF300T
    HTC Inspire 4G
    HTC Desire HD
    HTC Sensation
    HTC Incredible S
    HTC Salsa
    HTC Flyer
    HTC Evo 3D
    HTC Desire S
    HTC Wildfire
    HTC Wildfire S
    HTC Droid Incredible 2
    HTC Thunderbolt
    HTC Desire
    HTC Desire Z
    HTC One X
    LG GT-540 OPTIMUS
    LG Optimus One
    Motorola Triumph
    Motorola Droid X2
    Samsung Galaxy S II Skyrocket (SGH-I727)
    Samsung Galaxy S II (I9100)
    Samsung Galaxy S II (SGH-T989)
    Samsung Galaxy S Plus I9000
    Samsung Galaxy Nexus
    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.
    39
    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:
    1. 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. :eek:
    2. 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.
    3. My server has served up over 500,000 xtra.bin files to users like you on XDA since v3.1 was released.
    4. 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.

    Enjoy!
    8
    Seems to have worked on my GS2, atleast its getting the GPS lock faster now than before (altho, it wasn't slow before)

    Anyway, i decided to help you out with the xtra.bin, and have created a cronjob to get it from your server, once every hour, and store it at http://eve-kill.net/xtra.bin

    Feel free to use it aswell :)
    Server is in Holland on a 1/1Gbit connection :)

    Thanks for the info. I might end up calling on you if the load gets overbearing. Heck, it if we keep needing this an Europe starts showing latency, I'll definitely hit you up to do that officially.

    Glad it's working for you even though you didn't have issues before! :D
    8


    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.

    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!
    6
    Hey man,
    sounds good, will definately give your gps.conf a try. I am on CM7 self compiled KANG for the S2. I just checked build.prob and it doesn't contain the variable you mentioned in your FAQ "ro.ril.def.agps.mode".
    Should I add it, or should this work also without that variable set?
    Also, I'd like to know if this patch could also improve GPS accuracy, that is reported in apps lke GPS Test or others. I used to have 5-10m accuracy with samsung based roms, but this went up to 10-20m with CM7. Might only be a placebo effect, but well. Lower sounds better to me ;-)

    Thank you for reading the Notes section first! You should be okay without the variable. If you aren't pleased with results, you can always toss it in later.

    This patch normally improves speed and accuracy. On my device, it took 1 - 2 minutes to lock with an error of about 20 - 30 meters. With the patch, I lock in under 7 seconds with accuracy at around 3 meters. Some get even better with better phone hardware.