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

Search This thread

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
The new release has no effect on other supported devices unless it is a non-Qualcomm phone.


In this article (http://www.androidtablets.net/forum...rum/13787-your-gps-working-14.html#post199885) is mentioned that we far away from havinggpsfix on A500...IT is correct???????

As discussed previously, it may help your device especially those with ICS and with custom ROM's using portions derived from other devices such as the Transformer source code.

It could help you without such components, I do not know as I do not have an Iconia A500 to play with.

You could give it a try just for the fun of it.
 

drharisis

Senior Member
Jul 2, 2008
371
9
As discussed previously, it may help your device especially those with ICS and with custom ROM's using portions derived from other devices such as the Transformer source code.

It could help you without such components, I do not know as I do not have an Iconia A500 to play with.

You could give it a try just for the fun of it.


In previous article it is mentioned that is important to develop some drivers to make agps enabled on this device...I tested test build 5...It seems to locate more sats but not having a quick fix.........Do you recommend another patch????thanks...
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
In previous article it is mentioned that is important to develop some drivers to make agps enabled on this device...I tested test build 5...It seems to locate more sats but not having a quick fix.........Do you recommend another patch????thanks...

I understand that there is a driver issue and I said that previously. But, from my discussions with others THOR and possibly other ROM's are using drivers from other devices which are functional. So my point is that this patch will help even more for those who are using any such ROM that has the properly functioning drivers.
 
  • Like
Reactions: drharisis

drharisis

Senior Member
Jul 2, 2008
371
9
I understand that there is a driver issue and I said that previously. But, from my discussions with others THOR and possibly other ROM's are using drivers from other devices which are functional. So my point is that this patch will help even more for those who are using any such ROM that has the properly functioning drivers.


Which patch exactly do you mean???(test build 5 ???)
...I am a little confused..thanks
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
Which patch exactly do you mean???(test build 5 ???)
...I am a little confused..thanks

Assuming that the drivers are good to go on the custom ROM you are using, the Prime version's thread has "1.0" which should work fine for those ROM's using proper drivers and all that jazz.

I say this based on my hardware review of your device (here) and the ASUS models.
 
  • Like
Reactions: drharisis

drharisis

Senior Member
Jul 2, 2008
371
9
Assuming that the drivers are good to go on the custom ROM you are using, the Prime version's thread has "1.0" which should work fine for those ROM's using proper drivers and all that jazz.

I say this based on my hardware review of your device (here) and the ASUS models.

Just tested the new release...It is as good as test build 5 ,,but not quick lock(cold start)After locating the sats if I am going to use again gps I take then a quick lock...Thanks for trying to help us:)
 
Last edited:

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
Just tested the new release...It is as good as test build 5 ,,but not quick lock(cold start)After locating the sats if I am going to use again gps I take then a quick lock...Thanks for trying to help us:)

If someone will send me a private message containing the files from /etc/gps/ and /data/gps/, and the /etc/gps.conf if it exists FROM the stock ROM, I would be appreciative.
 

pacificwing

Senior Member
Jul 8, 2011
153
31
Vancouver
So i was looking through the GPS log debugging info and I found the following lines appear in every instance where I try to use my GPS.


Code:
$297083I  Start reading LTO ...
LTO file was not found!
$297083I  LTO reading complete.
$297083I LTO ignored (integrity)
$297083I  Start reading CBEE file ...
EE file was not found!
$297084I  CBEE file reading complete.
$297084W Warning: Using default vertical accuracy (45.000000)
$297084I Serialize REFPOS: (49.234780, -123.025234, 0.000000)(0) OK

I'm assuming LTO is the lto.dat. Not sure if this is causing the issue.

I was running GPS outdoors, with the latest patch from this thread (google NON-SSL). I was seeing 3-4 satellites, but they were not locking. I did have wifi access enabled and it was working.

Dunno if these means anything. Unfortunately, there is very little information out there on gps log outputs.
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
So i was looking through the GPS log debugging info and I found the following lines appear in every instance where I try to use my GPS.


Code:
$297083I  Start reading LTO ...
LTO file was not found!
$297083I  LTO reading complete.
$297083I LTO ignored (integrity)
$297083I  Start reading CBEE file ...
EE file was not found!
$297084I  CBEE file reading complete.
$297084W Warning: Using default vertical accuracy (45.000000)
$297084I Serialize REFPOS: (49.234780, -123.025234, 0.000000)(0) OK

I'm assuming LTO is the lto.dat. Not sure if this is causing the issue.

I was running GPS outdoors, with the latest patch from this thread (google NON-SSL). I was seeing 3-4 satellites, but they were not locking. I did have wifi access enabled and it was working.

Dunno if these means anything. Unfortunately, there is very little information out there on gps log outputs.

There should be an LTO file in the /data/gps/ folder. Its download is controlled by the GPSD and not in my script. See if it exists and report back. If the directory doesn't exist, create it.

Try flashing the Transformer Prime v1.0 and let me know how that goes out of sheer curiosity.
 

pacificwing

Senior Member
Jul 8, 2011
153
31
Vancouver
There should be an LTO file in the /data/gps/ folder. Its download is controlled by the GPSD and not in my script. See if it exists and report back. If the directory doesn't exist, create it.

Try flashing the Transformer Prime v1.0 and let me know how that goes out of sheer curiosity.

Transformer Prime caused by GPS to stop working entirely. I reverted back.

The only file in /data/gps is a file called gldata.sto

The GPS seems to dump the log files in here as well. There are a lot of those. They are named gl-<data><randomnumber>.txt. That is the file that generated the code above.
 

crypted

Senior Member
Nov 20, 2007
2,493
4,224
Miami, FL
derekgordon.com
Transformer Prime caused by GPS to stop working entirely. I reverted back.

The only file in /data/gps is a file called gldata.sto

The GPS seems to dump the log files in here as well. There are a lot of those. They are named gl-<data><randomnumber>.txt. That is the file that generated the code above.

Okay so we have some stark deviations in configurations of ROM's here. Some use XTRA, some use STO, and some use LTO. Holy crap Batman. Not fun for me here at all.

I need original gps.conf and all files from /etc/gps/ and /data/gps from the ROM you're using before my patch. And, I need that from a lot of ROM's by the look of it that way I can try and figure out why the hell this device has such randomization in it.

It used to work for most people before these new ROM's started dumping out! Ugh!
 

pacificwing

Senior Member
Jul 8, 2011
153
31
Vancouver
Okay so we have some stark deviations in configurations of ROM's here. Some use XTRA, some use STO, and some use LTO. Holy crap Batman. Not fun for me here at all.

I need original gps.conf and all files from /etc/gps/ and /data/gps from the ROM you're using before my patch. And, I need that from a lot of ROM's by the look of it that way I can try and figure out why the hell this device has such randomization in it.

It used to work for most people before these new ROM's started dumping out! Ugh!

HaHa! They can't make it too easy for you!

As I understand it, Flexreaper (the rom I'm using now) is based on the latest honeycomb leak. With the exception of Thor's, which rewrites everything from the ground up, I expect most of the major ROM releases here to have the same basic data.

Might I sugest downloading the stock ICS 4.0.3 leak from here and using the files from that?

http://xdaforums.com/showthread.php?t=1524736

My current ROM has been so bastardized from tweaking and fiddling I doubt it would be much use to you.

Cheers,
-PW
 

Zoandroid

Senior Member
Dec 9, 2010
665
116
Working on ICS Lightspeed ROM

I just wanted to say thanks for this nifty GPS patch, and that I have now used it on 3 devices with success. A Droid X running CM7, My A500 tablet when it ran Thor's HC 3.2.1 version 14, and now as of tonight the same A500 tablet running Lightspeed ICS ROM version 4.4.

To make it work with the ICS ROM, I had to add your suggested line "ro.ril.def.agps.mode = 1" to the build.prop file. Just changing the gps.conf (which is what worked the first 2 times) wasn't enough. With that line also added, I have fast GPS lock using GPS Status as well as using Latitude on the A500.
 

pacificwing

Senior Member
Jul 8, 2011
153
31
Vancouver
I went back to Thor's 14.2 tonight, to try and figure out why it works so much better on that ROM.

After looking over the filesystem, and the logs, I found one noticeable difference:

/data/gps/lto.dat

It exists in the old Thor 14.2 rom, but it is not generated or successfully pulled in any other ROM.

Anyway, apparently this file (long term orbit data) holds some critical information for the locking component of satellites. Without it, you may see multiple satellites, but locking on could take ages. This file speeds up locking considerably.

For more information, here is a link:
http://www.broadcom.com/collateral/tb/LTO-TB100-R.pdf

Anyhow. You can get the file here:
http://gllto.glpals.com/7day/latest/lto.dat

Unfortunatly, I won't be able to test it until morning. But everything I've read (including my log file above) indicates that that file is supposed to be there, and is not getting pulled. I've downloaded the file onto a clean install of Flexreapers ROM, and am going to place it in /data/gps/.

I'll let you know how it goes tomorrow morning. It may be that including this file into your patch could result in better performance on the A500. That may not be viable though, since apparently the file is supposed to be updated every 7 days for optimum performance.

It still doesn't explain why the file is not getting generated/downloaded in the first place though. But that is another issue.

EDIT:

Okay. So I've not been upstairs to try it yet, but I can say from the logs I'm getting much fewer error messages with this file present. It's looking hopefull.

On that note: Any idea where I might get a copy of the "/data/gps/cbee.cbee" file I'm apparently missing?
 
Last edited:
  • Like
Reactions: duongla and maris__

maris__

Senior Member
Aug 26, 2011
450
204
Incredible, you found it!! I tested lto.dat with FlexReaper R.11, and get almost an immediate SAT fix indoors that doesn't get lost (when the tab is placed near the window). Thanks!!

Best regards, maris
 

pacificwing

Senior Member
Jul 8, 2011
153
31
Vancouver
Incredible, you found it!! I tested lto.dat with FlexReaper R.11, and get almost an immediate SAT fix indoors that doesn't get lost (when the tab is placed near the window). Thanks!!

Best regards, maris


That's really good news! I'm glad. I can't wait to test it tomorrow.

Now that we know *what* the problem is, it looks like the next task is to figure out *why* this file isn't getting downloaded. Maybe there is a setting in gps.conf or gpsconfig.xml which is responsible for instructing the unit to download this file.

We are still missing the extended ephemeris (CBEE) file, which could speed things up even faster. No idea where to get that.

I'll keep looking into it.

EDIT:

I just went outside and tested it, and yes, it appears to have been the problem. crypted, you may want to add this revelation to your long list of notes.

The next step is obviously to figure out why the file isn't being downloaded automatically, since it will have to be updated manually every 7 or so days.

Cheers, and goodnight.
-PW
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 67
    AGPS PATCH

    REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.

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

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

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

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

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

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

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


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

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

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

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

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


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

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


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

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

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


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


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

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

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

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


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


    REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
    6
    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! ;)
    3
    v2.0 is out

    First round of v2.0 is released. The beta-testers loved it and all gave the go-ahead today. I hope you all enjoy it as well.

    Do note the multiple versions. I'm trying to help as many as we can specifically based on what people wanted.

    I use the Generic/Google version even though I'm an AT&T customer.
    2
    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.
    2
    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.