yashsingh1/xdaforums huggingface dataset:
[Captivate General] crypted:
For those having issues with bouncing or a range in error on devices... I would recommend trying the "alternate world patch" to see if that alleviates the bouncing assuming it's related to a glitch in some GPS units.

Yes, I use the similar tactics in the gps.conf. AT&T, and WWE ROM's, typically don't have a fully configured gps.conf. I added variables that are actually supported. However, I plan to drop some variables because they only assist with older devices and not many of us keep those around when we can upgrade again.

Also, I use my co-located Linux servers to monitor NTP pool and XTRA server response times. I modified to get the best all-around attainment that way.

I don't know of these other people and have not seen their patches. I have had over 30,000 downloads and not even 2% negative response. Those who get grumpy failed to follow directions and are resolved one they are pointed back to the notes section or something like that.

I'll be introducing a "surprise" in v3.0 and that won't be discussed until it's time. I've had my work ripped by a lot of people and "slightly" modified without giving credit. I'd like to keep this one under wraps as best as possible.
[Captivate General] quick6black:
I was following it on a map and the gps marker was jumping around maybe 15-20 feet around my real location. It was jumping east to west as time progressed, kept the gps active for maybe 60 seconds. With the stock gps file as the accuracy increased the gps marker which was south of my real location, slowly moved north in small increment.
[Captivate General] crypted:
If I understand you correctly, it's jumping and off-base when it's patch and when it's stock. If that is true, this lends credence to reports that CM has messed up the aGPS capabilities. Seems to be a standard issue the past few days with their latest builds. Luckily, a user dug into it for me and showed the code issues where CM is messing up by not allowing aGPS to function.

Let's hope they fix it!
[Captivate General] Rrryan2:
Your understanding of how pool.ntp.org works seems incomplete. 0.pool, 1.pool etc. point to random sets of servers that change hourly. As such, you can't just "align" them based on response and expect to get reliable, reproducible improvement going forward.

Xtra.bin is not used on the Captivate and is not ever downloaded. Even if you manually download it, it just gets discarded as corrupted. In any case, lto2.dat (valid for 7 days) > xtra.bin (24 hours).

Here's the complete stock gps.conf from the Samsung Nexus S, an 'AOSP' device that's a close relative to the Captivate and uses the same Broadcom BCM4751 chip:

NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
[Captivate General] crypted:
Thanks for the input. Not having the device, I did not know the bin was out of the running. That's why I started the thread!!!

As far as pools, I'll check into that more thoroughly. I'm not in full agreement, but 24 hours of logging nslookup may change that and prove your point.
[Captivate General] Rrryan2:
From http://www.pool.ntp.org/en/use.html :

"The 0, 1 and 2.pool.ntp.org names point to a random set of servers that will change every hour."​

What's not to agree with?

24 hours of lookup logs to randomly assigned servers will be exactly that, and won't be able to predict what performance will be like over the next 24 hours of randomly assigned server groups.

Here's a quick dump of a few pings to 1.pool.ntp.org conducted just a few minutes apart:

>ping 1.us.pool.ntp.org

Pinging 1.us.pool.ntp.org [204.9.136.253] with 32 bytes of data:
Reply from 204.9.136.253: bytes=32 time=365ms TTL=50
Reply from 204.9.136.253: bytes=32 time=363ms TTL=50
Reply from 204.9.136.253: bytes=32 time=356ms TTL=50
Reply from 204.9.136.253: bytes=32 time=346ms TTL=50

Ping statistics for 204.9.136.253:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 346ms, Maximum = 365ms, Average = 357ms

>ping 1.us.pool.ntp.org

Pinging 1.us.pool.ntp.org [67.18.187.111] with 32 bytes of data:
Reply from 67.18.187.111: bytes=32 time=307ms TTL=48
Reply from 67.18.187.111: bytes=32 time=210ms TTL=48
Reply from 67.18.187.111: bytes=32 time=102ms TTL=48
Reply from 67.18.187.111: bytes=32 time=156ms TTL=48

Ping statistics for 67.18.187.111:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 102ms, Maximum = 307ms, Average = 193ms

>ping 1.us.pool.ntp.org

Pinging 1.us.pool.ntp.org [173.193.227.67] with 32 bytes of data:
Reply from 173.193.227.67: bytes=32 time=687ms TTL=46
Reply from 173.193.227.67: bytes=32 time=573ms TTL=46
Reply from 173.193.227.67: bytes=32 time=638ms TTL=46
Reply from 173.193.227.67: bytes=32 time=705ms TTL=46

Ping statistics for 173.193.227.67:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 573ms, Maximum = 705ms, Average = 650ms

Note that 1.us.pool.ntp.org resolves to a different IP each time, and avg. ping times vary accordingly. An hour from now, it will resolve to a different set of servers/IPs.

Arranging 0.pool, 1.pool etc. into some arbitrary order isn't going to accomplish anything.
[Captivate General] crypted:
No worries. I may just make my own pooling! I'm prone to do stupid things like that with my time.
[Captivate General] NascarFastcar:
Should stock gps settings be used?

(standalone, www.spirent-lcs.com, 7275)

Or

(ms based, supl.google.com, 7276)?

Here is captivates stock gps.conf
[Captivate General] Shammyh:
Take a look at http://xdaforums.com/showthread.php?t=881941

Has lots of useful GPS information specific to the Captivate GPS chipset. You might even find some useful stuff to incorporate in your patch.

For example, if you're on AT&T, there's no reason not to use the following AGPS SUPL server:

h-slp.mnc410.mcc310.pub.3gppnetwork.org w/ port 7275

That's an AT&T run SUPL server that presumably, since it's on their own network, can provide good information for U.S. based people.
[Captivate General] crypted:
That domain showed up on a spam blacklist. I'd stick with Google...
[Captivate General] crypted:
I'll check out that SUPL. What's funny is, the stock ROM for three devices from AT&T do not have that SUPL. Being those are my devices to screw with, I did not know and had not been informed that there is a SUPL. :confused: Why would they do that I wonder... I'm going to screw w/ them now.
[Captivate General] Rrryan2:
Ugh. Facepalm.

Lcs-spirent.com was a testing domain setting in the Broadcom SDK that was intended for developer/mfr. testing when using specialized testing equipment that had sandboxed, hard-coded DNS settings etc. For some inexpiable, unforgivable reason that setting was inappropriately folded into Samsung's retail builds and set as the default. Speculation ran from just plain ineptitude and incompetence on Samsung's part to a hurried, slapdash pressing need for a sudden and drastic re-work when Google insisted just prior to launch that the Skyhook service couldn't be used. See the Motorola litigation that's been all over the major news in recent months, etc.

Following launch of the Galaxy S line the lcs-spirent.com domain was subsequently registered by an opportunist who pointed it to a spammy 'parking lot' ad page.

This is the sort of thing that ought to be common knowledge to anyone who knows anything about Captivate or Galaxy S GPS and/or has access to Google search.

Actually, the stock ROM for Captivate (KB1 2.2 is still the latest official 'stock' Samsung/AT&T ROM for I-897, sadly) does indeed default to a 3gppnetwork.org server if 'Automatic' configuration is manually selected in AngryGPS. A 'custom' configuration using the spurious lcs-spirent.com is the default setting though. :(

3GPP is a worldwide mobile industry consortium. It's a mobile industry alternative to supl.google.com. It actually works pretty well for the most part.

I can't say as to why you weren't informed of these details. :confused: I'll be sure to let SamsungJohn know as soon as the opportunity presents though.
[Captivate General] Oxicottin:
AGPS first initial try

Cryped, I have a Samsung Captivate (one of the first out) and with each ROM my GPS is different some good some bad. Right now I'm using the Pinnacle 1.2ROM and my GPS locks onto about 6-7 sats. @ 30 meters. I installed your 1.3v and ran GPS Status and it locked onto 10-11 sats. @ 5-10 meters in just a few seconds. Mind you this is out in the open on a partly cloudy day in eastern united states and I haven't tried in my vehicle yet..... Works great so far Thanks!

I attached my gps.conf as requested in your first post.
[Captivate General] Oxicottin:
Proof...... It got really cloudy outside from last post due to storm rolling in.
[Captivate General] crypted:
This is very interesting. A few posts back, a user said that your device basically cannot parse the bin file. Yet, your gps.conf that you attached shows it calling for bin. Not only that, you tried the patch and it fixed your problem. This is entirely in contradiction to his post.

Anyone else have an opinion? Does the Captivate use dat files and somehow this stock gps.conf was messed up in its release to include bin instead? Or, what?
[Captivate General] Rrryan2:
gpsOneXTRA is a Qualcomm service. The Captivate uses a Broadcom chip and thus uses Broadcom's Long Term Orbits (LTO) service instead. This is why AGPS data gets written to /data/gps/lto2.dat but xtra.bin never appears in /data/gps/ or anywhere else -- even with this "patch" implemented. And it doesn't really matter much really. Xtra.bin only provides predictive ephemerides for 24 hours, but LTO gives as much as 7 days. As long as you've got LTO, XTRA is redundant. 7 > 1.

Xtra server configurations are indeed specified in gps.conf, but the settings are extraneous and unused; I wonder even if they're just deadweight artifacts of AOSP or another Samsung device. In fact, you can delete them from gps.conf altogether and gps will still function just fine.

The bulk of the gps configuration on SGS devices (on GB ROMs at least) is carried out in /system/vendor/etc/gps.xml. Most of the rest is in settings.db and/or NVRAM, some of which can be edited using the Samsung-provided AngryGPS.apk. The configurations aren't simply "missing" from gps.conf. If that were the case, gps wouldn't function *at all*

I'm all for debate and scientific inquiry. And I'll cheerfully admit that I don't know everything about GPS or its implementation on these devices. I would be just delighted if we finally found a cure for GPS and would congratulate you genuinely if you found it.

But nowhere in this thread or your other one is any actual evidence, documentation or research presented. It's fueled exclusively by hope and optimism. One of the major supposed features of this patch that worked by supposedly "aligning" the NTP servers was quickly shown to be woefully misconceived, relying on a problematic understanding of the basic workings of pool.ntp.org.

I can't prove a negative. Can you provide any actual documentation? Anything besides anecdotal evidence, magic beans or "Because I said so?"
[Captivate General] crypted:
Why act as though I'm discounting your evidence provided? And why institute hostile means of communication? So, I'm a magician. Now, let me work magic to save the world economy. (waiting) okay did it work?

Sarcasm aside, just because one piece of the entire configuration is not aligned as I may believe and you have shown for disproving...does that mean the rest is inaccurate? How would magic in taking nonexistent GPS capabilities on some phones and making them work accurately be such? I could just create a blank gps.conf if that were the case...

Rather, you show there is a newer method introduced in Samsung devices. This only disproves my patch having an ability to assist this device. My reason for attempting to include this device was based on a users private message and insisting it worked. I started this thread. You posted data to show it wouldn't work. That was the point of this thread.

Then, my next inquiry... Would this newer method always be found on every ROM for this device? Or if the ROM uses a different ported WWE, would it still use the older method my device has? If it were possible that some ROMs aren't using this new method, it would explain WHY people are reporting benefits.

Logical?

EDIT: And regarding my XTRA changes, every f-ing device using XTRA uses the 1st server. It made logical sense to start utilizing secondary and tertiary servers because of significant latency and wait times for server responses. But, that's magic on my part. Voodoo as German asserted.
[Captivate General] Rrryan2:
Yes. One piece of woefully misconceived configuration that betrays a pretty big misunderstanding about the basic technology involved actually does tend to call into question the credibility of the rest of the "patch" (actually just a text file, but anyway...). Especially since the only justification for the rest of it continues to be "Because I said so."

Yes. It is the same gps approach, at least for the Samsung-based ROMs. CM7, MIUI etc. are different beasts with their own caveats.

Not newer or older. Every Samsung android device so far uses same or similar approach. Manufacturers do things differently sometimes. Sometimes they even use different components.

10 people reporting snake oil works doesn't mean snake oil works. Only means 10 people used snake oil.

If it were something that elementary, wouldn't you think Qualcomm would have engineered that into their system? Once again, these are load-balanced groups of servers. Not like a multibillion dollar company is going to try to run a global network for millions of users on 4 total servers. You don't gain anything by arbitrarily choosing the second different managed server group. And again, XTRA is not used in these devices. Not a Qualcomm device. 100% immaterial here.

This discussion seems non-productive and I'm going to bow out. Good luck with your project.
[Captivate General] crypted:
You really are hell bent on being a jack ass for some reason. Test it out and see that I'm wrong. Please do.

My entire statement rested on what you said previously and that this device is inherently different from the other that I may use.

I'm extremely sorry for my pathetic attempt to assist users with this godly device and for even thinking that users may portray enlightenment about their individual situation when describing this helped them and asking for official inclusion of said device.

My the great Lord end my days of agony of ignorance so that you can rule commentary on XDA and ensure that someone trying to help will never again do so.
[Captivate General] NascarFastcar:
I really dont understand whats up with this phones gps.

Heres my story:

-Got my original captivate (1009)on black friday. Gps was okay stock and improved with changing to supl.google.com etc. Then it just went back to being bad. Ryans PB v.9-1 fixes made it usable but it still was off.

-Got a refurbished unit (1007) in april. Had amazing stock gps but had to be returned due to random shutdowns

-Got 4 other reburbs within a month due to random shutdowns happening after a few days (all on stock roms). But the gps on all units worked fine. (all 1008's)

-My final and current phone was brand new (atnt rep opened a new phone for me) 1103 built.

This phone works great gps wise but still started to shutdown after two weeks. Odin'd it and reflased kb1. Gps started going downhill. None of the tricks work. This phone performs the best gps wise with stock settings(after a fresh odin and kies flash). Hell even changing this gps.conf file screwed things up. Putting the stock file back wont help. Not even plumbobs fix will do anything. Even if I start messing with lbsmode/system files the gps wont work in till I reflash kb1. Then the gps is mediocre at best.

I guess I might go to my service center and get another. They let me test the gps at the store and I wont leave inless I see a instant 10+ sats 20+snr. This has to be something with the stock samsung flash. All my previous phones worked great but had shutdowns.

Still believe the gps problems with this phone are 90% hardware and 10% software. My current phone has a perfect gps chip. But since i messed around with its software it seems to have rendered it useless.
[Captivate General] ZeroG1:
I tried this out while driving, but unfortunately I didn't notice much difference. GPS Test seems to be show a good picture, 8-11 sats, 30-40 SNR, but gmaps doesn't seem to hold the signal very well.

I'm running the Iluence 1.1 ROM (very nice by the way!) with Dark Core kernal.
[Captivate General] Nerz:
I have always thought it was the actual antenna itself because on the four that I have had they get decent, and only decent, gps when I hold the phone in a vertical position. If put it in my lap or seat it instantly loses accuracy, and then gps reception almost completely. When I hold it vertical again, it gains fairly accurate reception fairly quickly.
[Captivate General] crypted:
Most gps units are on the bottom top areas...signals are easy to lose and have very weak penetration. Also they bounce on walls... So it matters how you hold it and where..
[Captivate General] NascarFastcar:
Well ive been there back when we were scraping the coating off the connection area's on the back case and bending the antenna up. Yes reception increased etc. But these phones actually work the best with the back cover off and facing down.. Hell on my original phone I had the otter box commuter case and i use to use leave my back cover off within the case and use a rubber gasket to seal dirt from entering where the spear is. Worked great.
[XPERIA X8 General] crypted:
Well, my goal for the upcoming v2.0 of my aGPS Patch is to bring support to five more devices. This is one of the devices I selected!

I'm looking for some testers to see if the patch will effectively work.

It simply replaces gps.conf in /etc/ to be much better performing.

You can download v1.3 by clicking here.

To install, use Root Explorer or ES File Explorer to copy the new one over. Reboot. Give GPS a try! I recommend GPS Status. If your device uses ClockWork Recovery, you can simply flash the ZIP.

A reference thread can be seen at http://xdaforums.com/showthread.php?t=1250226.

Also, I'd love for someone to send me the gps.conf currently on their device.

Thank you for assisting me in the determination if this version works.
[XPERIA X8 General] wc_how:
Better performance? You mean faster located or accuracy?

It is just the aGPS?
[XPERIA X8 General] crypted:
Yes, and stabilized results. Users who would lose signal while traveling or at higher speeds, this tends to keep the lock consistent and constant.

Also, if you would send me your /etc/gps.conf I would appreciate it. Custom ROM's tend to not do much in the way of making a crappy situation better, but I'm curious.

Thanks for your interest in assisting!
[XPERIA X8 General] wc_how:
This is my gps.conf from GDX.

I will test it in later 2hours time, still in the office now.

and i have no problem on the old file, i can get the location with 20secs,(normally within 10secs) with my Papago Navigator in open air.But yes, my GPS device is NEVER turn off.

Just the information how i use the GPS.

* I saw your another post, is this patch only for North America?

I am from Malaysia.
[XPERIA X8 General] crypted:
No, this is worldwide. I did two versions but that ended and I am only offering worldwide patches now. So, should work no matter where you're at.
[XPERIA X8 General] wc_how:
I simple tried the new gps.conf. I don't have any positive feedback for you nor the negative. I don't really feel any useful compare with the original one. Maybe 2secs faster, i am not sure.

But in conclusion, it can be used and no problem for a short test. I might give more opinion for a longer try.
[XPERIA X8 General] crypted:
At least we know it's compatible, then. It didn't kill your phone's GPS. Didn't think it would anyway. If you have time, play with it. If not, thank you for helping. ;)
[XPERIA X8 General] crypted:
Well, I have released official support with v2.0 as promised.

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

Hope this helps some people out!
[XPERIA X8 General] shitlord68:
Works very well with gingerdxv17 and linuxv4 on my x8...

Great work, keep it up...

BTW, I know it's not related with the topic but can u pls recommend a navigation app (the best one)...

Thanks
[XPERIA X8 General] crypted:
Could you post this on the official thread for the patch? Link is a post up from yours. ;)

Answer: I only use Google Maps. It works better than my TomTom.
[XPERIA X8 General] shitlord68:
Did it, thanks again...
[XPERIA X8 General] wc_how:
depend on which country you stay,and the map update.
[XPERIA X8 General] shitlord68:
If u refer to Google maps, I don't use them...

I use sygic mobile maps 10...

And I live in f*cking Croatia so I wouldn't agree...
[Optimus One, P500, V General] crypted:
Well, my goal for the upcoming v2.0 of my aGPS Patch is to bring support to five more devices. This is one of the devices I selected!

I'm looking for some testers to see if the patch will effectively work.

It simply replaces gps.conf in /etc/ to be much better performing.

You can download v1.3 by clicking here.

To install, use Root Explorer or ES File Explorer to copy the new one over. Reboot. Give GPS a try! I recommend GPS Status. If your device uses ClockWork Recovery, you can simply flash the ZIP.

A reference thread can be seen at http://xdaforums.com/showthread.php?t=1250226.

Also, I'd love for someone to send me the gps.conf currently on their device.

Thank you for assisting me in the determination if this version works.
[Optimus One, P500, V General] deetailed:
Attached is the gps.conf in my P500. I'm not sure if it's the same as original gps.conf in LG's stock ROM, since I'm currently using a custom ROM (andy572's Phoenix with Gingerbread 2.3.4), but IIRC Andy didn't tweak the gps so it might be the same.

I can't flash the zip (using AmonRa recovery, disabled verification) but I'll try using File Expert to put it in /system/etc/ later.
[Optimus One, P500, V General] crypted:
I've had word a week ago it worked swimmingly with this device...

Look forward to your results.
[Optimus One, P500, V General] ccdreadcc:
i think gpsconf is better in noejns void froyo final
[Optimus One, P500, V General] deetailed:
I've changed the gps.conf. Nowhere near an rigorous test, but my results using GPS Status are:

Before - Fix in 112s, 5-6 satellites, didn't note the error

After - Fix in 28s, 7-10 satellites, error 5-10 m

Seems to work. Will try your note #2 and test in more locations later.

Do you think it'll do any good if I add my country-specific server (id.pool.ntp.org) to the file?
[Optimus One, P500, V General] dryhte:
Will test tonight :)

I've attached my gps.conf; I'm using default 2.3.3 with only a custom kernel. I haven't used gps since upgrading to 2.3.3 (used void. before, there gps was really snappy)

However, can you tell us how we can test with gps status? I can't really tell when the gps gets a lock...
[Optimus One, P500, V General] crypted:
Country specific NTP servers aren't necessary at all. Your device should get an NTP server near you and quickest for you from the NTP pool by default.

Well, open up the app once it's installed. Let it run for a few minutes and let the GPS learn about its fellow satellites near you. You should see 5-10 satellites depending on your location. After that, exit the app. Reopen it after a few seconds, see how quick the lock is. Further, you can see the Error accuracy on it as well.

---------- Post added at 08:15 AM ---------- Previous post was at 08:14 AM ----------

Did you actually try this one? Or are you just stating that?