AGPS Patch LG Optimus One 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK & MORE SATS

[richua]

New Google specific build without SSL just contains the gps.conf file, right?

And correct me if I'm wrong here: the new Google build just released seems to be the same as the 3.1 Google Alternate build, just with intermediate_pos set to 1. So, if I currently want the new no SSL build but in Alternate form, I don't need to do anything?

 

[crypted]

New Google specific build without SSL just contains the gps.conf file, right?

And correct me if I'm wrong here: the new Google build just released seems to be the same as the 3.1 Google Alternate build, just with intermediate_pos set to 1. So, if I currently want the new no SSL build but in Alternate form, I don't need to do anything?

Right, one file only... No SUPL needed as there is no SSL.

It is identical to the Google Build (not the Google Alternate) except for a couple of lines in the SUPL section (near the bottom of the conf) are commented out as compared to the Google Build. Essentially, you could comment out the same lines in the Alternate build to have the same effects if you're in a situation requiring the Alternate option.

 

[richua]

Got the new Google build and swapped the intermediate_pos flag to 0. It's a rainy and cloudy day here today and with the new patch and after a fresh reboot + cold GPS start, I got a lock in 27 seconds. The same scenario with the old 3.1 patch takes around 2 minutes and even that is still a huge improvement over stock.

I'm definitely donating again. This has already paid for itself.

 

[crypted]

Got the new Google build and swapped the intermediate_pos flag to 0. It's a rainy and cloudy day here today and with the new patch and after a fresh reboot + cold GPS start, I got a lock in 27 seconds. The same scenario with the old 3.1 patch takes around 2 minutes and even that is still a huge improvement over stock.

I'm definitely donating again. This has already paid for itself.

Well thanks! I'm glad that this continues to help you. I'm perplexed by the long delay even as 27 seconds. But, I don't have this phone to toy around with. It might be a hardware limitation of some sort.

Just to be clear, intermediate_pos is a positioning flag. If enabled (1), it permits the phone to start gathering data from GPS satellites that aren't completely locked onto. This can speed up your positioning time. However, there are some devices or device/software combinations that cannot handle this flag being enabled.

 

[richua]

Well thanks! I'm glad that this continues to help you. I'm perplexed by the long delay even as 27 seconds. But, I don't have this phone to toy around with. It might be a hardware limitation of some sort.

Just to be clear, intermediate_pos is a positioning flag. If enabled (1), it permits the phone to start gathering data from GPS satellites that aren't completely locked onto. This can speed up your positioning time. However, there are some devices or device/software combinations that cannot handle this flag being enabled.

I ran into an issue with the flag enabled and brought it up I think a few pages back, or maybe in PM. The locks were quicker, yes, but not entirely accurate and my location in nav and other apps would jump around often. This probably was a combination of CM, my nav apps, and the hardware.

I just switched the flag back to enabled (that is, stock Google build without SSL) and again saw the quicker locks. This time around, the jumpiness was not so bad. I only lost my place in nav twice today and got it picked up a few seconds later. I think I'll run it like this - with CM, nav, and this patch being updated since my last issue, things seemed to have smoothed out.

 

[crypted]

I ran into an issue with the flag enabled and brought it up I think a few pages back, or maybe in PM. The locks were quicker, yes, but not entirely accurate and my location in nav and other apps would jump around often. This probably was a combination of CM, my nav apps, and the hardware.

I just switched the flag back to enabled (that is, stock Google build without SSL) and again saw the quicker locks. This time around, the jumpiness was not so bad. I only lost my place in nav twice today and got it picked up a few seconds later. I think I'll run it like this - with CM, nav, and this patch being updated since my last issue, things seemed to have smoothed out.

Sorry for forgetting! I have had a heck of a time keeping the large amounts of discussions separated.

Let me know if you find that =1 is definitely needed in your case. We can work together in Private Message to draft a decent Note for people to understand the =1 better. I don't have issues so I really am not in the best place to write good info on it.

 

[4wd vege]

Great Work!

Worked out of the box on my Lg Optimus One with the lateset CM7 nightly.

Very happy.

 

[Gruber11]

Great Work!

Worked out of the box on my Lg Optimus One with the lateset CM7 nightly.

Very happy.

which file did you used from first post?

 

[crypted]

Thread kind of updated to include a new device:
Asus Transformer Prime

This patch can be useful on devices that need the GPS XML file which is prevalent in non-Qualcomm chipsets. So, it can be used in other devices as well.

The new release has no effect on other supported devices unless it is a non-Qualcomm phone.

 

[richua]

Chiming in to say the patch works well on CM9.

One question in general: sometimes my GPS will drop out completely while in use and won't lock onto any satellites until I reboot the phone. I've had this happen to me on my Nexus One and G2x with CM7 and CM9, possibly even stock too (but I never used stock for very long on either phone).

In your opinion, is this a hardware error where GPS simply stops working, or is it more related to the connection or GPS data?

 

[crypted]

Chiming in to say the patch works well on CM9.

One question in general: sometimes my GPS will drop out completely while in use and won't lock onto any satellites until I reboot the phone. I've had this happen to me on my Nexus One and G2x with CM7 and CM9, possibly even stock too (but I never used stock for very long on either phone).

In your opinion, is this a hardware error where GPS simply stops working, or is it more related to the connection or GPS data?

I'd suspect rom or gps internal configuración. I'd like to know results from a close to stock rom with this patch on top.

Sent from my Desire HD using XDA

 

[ThePresence]

I'm unable to flash this it gives errore I'm on cm 7.2 rc1

Sent from my LG-P500 using xda premium

 

[crypted]

I'm unable to flash this it gives errore I'm on cm 7.2 rc1

Sent from my LG-P500 using xda premium

There are two other methods of installation listed on the first post.

It isn't the patch with an issue, rather your recovery doesn't support the update binary used in the flashable versions.

I cannot make and maintain 100+ variations for all 24 supported devices.

Sent from my Desire HD using XDA

 

[Bec de Xorbin]

There was a bug in CM7 since end of October(!) that prevented using A-GPS altogether. That's why getting a lock took ages, also with this. I complained the slowness here and now I apologize.

It is now fixed in latest nightly. GPS's now blazingly fast even with gps.conf shipped with CM7.

 

[crypted]

There was a bug in CM7 since end of October(!) that prevented using A-GPS altogether. That's why getting a lock took ages, also with this. I complained the slowness here and now I apologize.

It is now fixed in latest nightly. GPS's now blazingly fast even with gps.conf shipped with CM7.

No worries. The Notes Section discussed this since October 2011, though.

 

[Bec de Xorbin]

No worries. The Notes Section discussed this since October 2011, though.

Oh snap

But now it is fixed

 

[crypted]

Today, AGPS Patch has reached a total number of 28 officially supported devices.

Support was added for the Asus Transformer TF101, Samsung's Galaxy Nexus, Samsung's Galaxy S I9000, and HTC's One X.

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

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

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

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

 

[bautroibaola]

AGPS Patch doesn't work on JB 4.1. Do you plan upgrade thí project?

 

[crypted]

AGPS Patch doesn't work on JB 4.1. Do you plan upgrade thí project?

It DOES work on Jellybean. Please elaborate how you reached this conclusion in your OWN environment.

 

[crypted]

Official support has is now available for more devices. This brings the total officially supported to 32.

Welcome these newbies to the fold:
Samsung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Asus Transformer TF300T
Motorola Droid X2
Samsung Galaxy S 4G

If you appreciate this growing work, always consider clicking the Thanks.

Remember that I pay monthly hosting fees for the space and bandwidth necessary to keep this patch working on the backend. So, please consider donating a few bucks if you're a user. All donations go directly to the patch provisioning and there is absolutely no overhead to benefit me.