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

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

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

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.

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.

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.
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.

Click to expand...

Click to collapse

GamingSV said:

Patch works really well! Used the Google specific CWR version. Flash via CRW using the Samsung Galaxy S II recovery. Not enough post to post a reply.

Click to expand...

Click to collapse

InstigatorX said:

Btw, where is Post #2 referred to in OP.

"4. Review the NOTE section in Post #2."

I copied files manually to /system/etc. Permissions? 644?

Click to expand...

Click to collapse

Petropavlovsk said:

The patch works great on my skyrocket outstide Atlanta. No more than 10 to 15 seconds to lock on and it is super accurate even out of town where I live and had problems before. Using the sat layer I can literally watch myself moving about the backyard with maybe a 10 to 20 foot margin. Thank you so much for an awesome patch.

Click to expand...

Click to collapse

eliwu26 said:

Darn. On stock ROM it made my GPS completely broken, sorry derek.
I had been having slow GPS anyway, like 40+ seconds for first lock and 20+ for warm lock, and this makes it so that it locks on to aGPS data, which actually makes no sense.

Basically, when going into GPS status, 23 sat's seen but no sat's are getting used and it's getting a lock. Apparently somewhere in Texas. Wireless network Location is turned off also.

Would anyone know why? Do I have a faulty Skyrocket?

REALLY hoped this would fix my GPS. So far the only GPS that works better than stock is Mod1441's NexusM0d ATT rom.

Click to expand...

Click to collapse

ljbrenes said:

Holy GPS Batman! I flashed the google specific patch in cwm and now my phone locks into my position in like 2 seconds. Also, the accuracy is up to 3 meters, which I have never seen before in my phone, the best I have ever seen is 9.

So the patch has greatly improved the gps in my phone.

Samsung Galaxy S (note is not S II, it is the first generation galaxy S) on USA Verizon Network.

Thanks for the patches!

Click to expand...

Click to collapse

knightnz said:

Installed into an international SGS2 and while sitting at my desk in the middle of an office where I can see a tiny amount of sky, it's flicking on & off with anywhere from 1-4 satellites, it may just be the time of day but I've never seen it pick up any before.

The GPS on the SGS2 generally seems to be pretty good but can sometimes take half a minute or so to get a good lock. There's a known problem area just around the corner from here which has a good view of the sky but always locates incorrectly, I'll try it down there and see how it goes.

I'm over in New Zealand so anything north-America specific will be right out the window. I'm running a "standard" version of the KL3 leak ROM and SiyahKernel 2.6.7. I don't use CM7 as they don't seem to be able to get bluetooth working well enough for my use.

Click to expand...

Click to collapse

kr3g3r said:

just tried out the google build...........and now it has me set about a 9 hour drive away in a different province!!!! wtf?

Click to expand...

Click to collapse

1. Is this issue in Google Maps and/or in GPS Status?
2. What were your issues before using this patch?
3. What ROM are you using?
4. Did you check the build.prop and other portions of the Notes Section?
5. Are you using any other GPS software? Such as GPS FIX, GPS ESSENTIALS, etc..?

1. Can you try the Google Build Alternate and report back as well?
2. Last, but not least, comment out the SUPL part of the gps.conf if you're up for it. Or, I can send you one with it commented out already. SUPL data might be supplied poorly because its finding you somewhere else on the network than where you really are.