yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] GRACO:
Hello there, I flashed Cog 4.1.1 and my GPS sucks big time... and I want to use this fix, my question is... what is the difference between GLOBAL or USA files? ...

If I travel to europe, I need to re-patch for europe? or should I use GLOBAL?

regards!!
[Captivate Android Development] rajendra82:
I believe the difference is which ntp server is used to pull clock data. The closer the server, the more accurate the clock will be. Using USA points you to a server in USA, which will result in slightly worse time accuracy when abroad. Using Global will compromise the US clock accuracy, but the accuracy will be better when abroad.
[Captivate Android Development] randyyy:
What if I live in México? Which one shohuld I download?
[Captivate Android Development] kevria:
I would guess USA since that would be the closest region.
[Captivate Android Development] rajendra82:
North America
[Captivate Android Development] askpcguy:
There also have been discussions on using an atomic clock sync app to reduce the tendency of the GPS position cursor to "slide around" while stationary.

Not sure how much help that would be but it might be worth looking at.

-I am using cog 4.11 without any GPS fixes and I'll update on how Google Maps does compared to Telenav.
[Captivate Android Development] Rrryan2:
Easiest way is to use Faster Fix app from market. It will let you customize the NTP setting if there's not a version for your region or of you're traveling etc.
[Captivate Android Development] Rrryan2:
Doesn't really seem to help much. If things are working right the GPS daemon uses the NTP server to compute an "offset" against the phone's onboard clock to use for its own timing, so the setting of the phone's clock doesn't matter lots.

All in all Telenav is likely to do better at navigation than Google Maps, which is really still in beta.
[Captivate Android Development] mbc663:
I think he means pb=plumbbob
[Captivate Android Development] GRACO:
Damn, what a difference!!! before 4 satellites view/lock outside .. after fix, my GPS is like an orgasm, awesome....

Dont forget to delete gps data and modify the settings before applying the patch.

regards!
[Captivate Android Development] jgotti107:
Sweet...works great on Cog. 4.1.1...thanks!!!!
[Captivate Android Development] fooldog01:
I hate to ask this but do I just copy the zip to the root folder and I will have an option to run it in CWM? All I have ever done with CWM is flash Cog 4.1.1 and that was using ROM manager to automate it. Thanks for the help!
[Captivate Android Development] Rrryan2:
Yes. Boot to recovery -> Install zip from sdcard -> choose zip from sdcard -> (choose the right .zip) -> Yes - Install (zip name) -> Go back -> Reboot system now
[Captivate Android Development] Rrryan2:
v1.0 UPDATE 3/10/2011

Changelog

1.0

- enabled PPS (Pulse Per Second) Mode in Jupiter.xml. This is (or would be) a highly accurate means for providing timing control within the unit, but although the chip seems capable it's not clear if the drivers make use of it

- increased the WarmStandbyTimeout times to 3 and 6 seconds to help reduce drops

- used a different method of signing the .zip that should (hopefully) allow it to be installed on systems using stock kernels by renaming to update.zip and choosing "reinstall packages" from recovery
[Captivate Android Development] drancid:
Great!!

I'll give it a shot!!
[Captivate Android Development] momulah:
Anyone checkout GPS AIDS in the market. Claims to have found a feature that enhances gps. May'be it could be of some help with this FIX.
[Captivate Android Development] reinbeau:
This app actually 'broke' my GPS, which was working pretty well before I tried it. Beware.
[Captivate Android Development] Rrryan2:
Mainly for the I9000 and doesn't work well with Captivate. It's basically an endaround band-aid fix that tries to manually download the AGPS info on demand . PlumbBob fixes the configuration to allow it to happen organically instead, a better approach in my opinion.
[Captivate Android Development] aalh:
pb = plumb bob

your nom de plume
[Captivate Android Development] wickedninjalo:
Running Adam's fusion rom, kb1 kernel and kb1 modem. Using plumbbobs 1.0 gps fix I get a 3d gps fix in copilot live within 3 seconds!!! mr.plumbbob consider this a virtual pat on the back. GREAT JOB SIR!
[Captivate Android Development] Rrryan2:
Heh. Actually, the Plumb Bob name is a joke of sorts, a term borrowed from surveying. On the more sophisticated surveying instruments it's now been replaced by downward looking lasers and such but just a few years ago even the best instruments were dependent on a piece of stone age tech, a plumb bob (weight on a string) to make sure it was precisely oriented above a control point or orienting station. In other words, I thought the high tech Captivate could stand some improvement from some low tech reasoning.
[Captivate Android Development] Ikonomi:
I enjoy the name Plumb Bob. I always envision a giant plumb bob hanging from a GPS satellite with the bob just over my car.

I'm easily amused.

Perception 10.2 | SpeedMod K13C | I9000ZSJPG
[Captivate Android Development] askpcguy:
Oddly, since I gave cognition 4.11 a try, GPS has been pretty good to me.

Drove around yesterday and while I had the phone as close to the window as I could with the screen off, I only got rerouted one time. But that was likely due to taking an on-ramp to a freeway that was a giant circle.
[Captivate Android Development] NascarFastcar:
Whats the best way to flash over .942? Just deleted the gps data via sgstools and flash v1.0 via clockwork? Or should I restore with gpsrestore ap etc?

Also whats the major difference between the north american files and the usa?
[Captivate Android Development] imb951:
THIS FIX WORKS BEAUTIFULLY!! THANK YOU!!!!!!

I vote to sticky this thread.
[Captivate Android Development] Rrryan2:
Just flash over the previous version. There's not much of a change between 0.942 and 1.0 though actually, just basically took it out of beta with only some very minor tweaks. If you're not comfortable with what you're doing you might just leave it alone. If it's not broken don't fix etc.

Don't use the Samsung GPS restore app. Ever. Not only does it only return things to a known-problematic configuration, but it wasn't ever even updated for Froyo. It can basically do nothing good at this point.

The only difference between the regional versions is the setting for the NTP time server. Either is probably fine is you live in the US, though the US version might be slightly faster if only just very slightly. US-based servers make up about 90% of the North American part of the pool any way so they're almost the same. I really only even built a North American version because it was confusing to non-US residents.
[Captivate Android Development] NascarFastcar:
Thanks for clearing that up. Just flashed it and it works perfect!

What did the gpsrestore ap even do? I noticed when using it during 2.1 that it never changed my settings in lbstest or anything..
[Captivate Android Development] mbc663:
Once again dev of the year for this device.

Plumbbob!!!!!
[Captivate Android Development] HoggerJeff:
Beautiful work! Cognition 4.1.1 with this flash and I get 9 sats and 15' accuracy in less than 40 seconds!
[Captivate Android Development] Rrryan2:
Indoor acquisition times can vary enormously, but you should generally be able to expect better acquisition times than that if "use wireless networks" is enabled and you have a good data connection.
[Captivate Android Development] 4-2ndtwin:
Thanks !!

Rrryan2,

Really appreciate all of your time and hard work on this Fix :D
[Captivate Android Development] Rrryan2:
Don't think anyone has really studied it (or at least I haven't) for a few reasons. For one thing, it didn't work or at least for most) so there wasn't too much worth studying.

What's telling though is that it wasn't titled a "fix" or "repair tool" or such but "GPSrestore" with the market description stating it was to restore any improper changes made by the user. This implies of course that it's operator error, not faulty design or software from Samsung.

The major function of the GPSrestore app is thus to serve as an ass-covering tool for Samsung, not to actually address any problem with the GPS. There's just no way whatsoever that by November (when the app was released) an app to fix gps coded by sober persons could have specified the faulty lcs-spirent server. It betrays that the real intent was just to help shield them from liability and encourage continued sales if a "fix" was available.
[Captivate Android Development] drancid:
i dunno why but 0.942 was better then 1.0 for me.

I'll change supl setting to control plane and try again.

Thanks a loooooot for your time spending for us ryan!!
[Captivate Android Development] drancid:
control plane mode gives me better performance!

Nice work!!
[Captivate Android Development] Rrryan2:
Probably just a fluke. For one thing Control Plane was disabled in Jupiter.xml after 0.9 and up. I've attached a modified version with control plane turned on if you want to try experimenting though. Keep in mind you have to turn on CP by dialing *#1575# too - see the 2nd post on front page for more info.

In my own testing using Control Plane didn't seem to provide much benefit if it was even working at all, in which case it might quickly time out and immediately fall back on the SUPL (internet) data for the AGPS info instead. I wondered if using Control Plane in this way wasn't disabled by AT&T or at least on some towers.

A good way to test might be to delete GPS data, disable wifi AND 3g cellular data (and maybe even intentionally specify a bad SUPL server) and then see if you can get a GPS fix. If it gets a fix in under 15 sec or so (with good view of the sky) then CP is probably working. If it takes closer to a minute or more then it's probably not.

And if by "better" performance you mean accuracy or tracking, CP actually has nothing to do with it. It would mostly only affect the download of AGPS data to assist in getting the first fix.
[Captivate Android Development] Rrryan2:
You know, I don't know. Since CM7 is still in development I hadn't quite seen the need/point of developing any 3rd party fixes yet, and last I heard Da_g (aka the Captivate GPS guru himself) was contributing gps dev to CM7 anyway.

It probably uses the same glgps_samsungJupiter as Nexus S/UCKB1 (*not* AGPSD like Vibrant/I9000, Captivate uses GLGPS) and I expect the files and configurations might work just fine but might not be needed at all. But since my only phone for testing is needed as a daily driver I can't experiment with beta ROMs so I haven't flashed CM7 yet to poke around in it and don't know for certain.

Weirdly, because of the new daemon and libraries I didn't expect 0.9+ to work with pre-UCKB1 ROMs/Modems and that was why I left 0.8.4b in the OP for a long time. Turns out it wasn't that big a deal though for some reason and once I ironed out some bugs that were muddying the issue it worked fine. So who knows what it might do to CM7...

tl;dr Hell, I don't know.
[Captivate Android Development] rajendra82:
Rrryan2:

You seemed a bit unsure about enabling the PPS mode in jupiter.xml, when you first posted 1.0. What exactly is PPS, and how can we test to see if it is making any difference, or even working.
[Captivate Android Development] Rrryan2:
P

ulse

P

er

S

econd: http://en.wikipedia.org/wiki/Pulse_per_second

How can we know if the driver makes use without being able to see the source? We really can't, or at least I don't know of any way.

How can we test? Your guess is as good as mine. It was another one of those things where I sort of unscientifically decided the GPS in these needed all the help it could get, and I figured it really couldn't make the GPS much *worse* than it already is...

To be honest, my *guess* is that it's yet another feature of the chip (like WAAS and sensitivity that should allow use of weaker signals but the driver won't use anything below SNR 20dbHz) that Samsung decided to not take advantage of for some inexplicable reason. I don't think enabling it within Jupiter.xml really makes any difference at all, and indeed in this schizophrenic configuration interface the significance of Jupiter.xml is not always certain. But again, it can't really hurt, this thing needs all the help it can get, and this sort of reasoning and experimentation got me this far... ;)
[Captivate Android Development] drancid:
Oh.. thanks for the info.

I just flashed your 1.001 cptest fix now. will do test drive tom and report the result!

Thank you always!

Edit. when i dial #*1575# it says

gps module is in ap side.

cog 4.1
[Captivate Android Development] bay_wolf:
Just wanted to say that it worked great for me. I got 12 sats locked in about 15 seconds from a cold start and 10m accuracy. I'm running serendipity 5.8 with the jk4 modem. I havent done any driving tests but will be sure to tomorrow.
[Captivate Android Development] hiepgia:
WOW! Good Result. Fix 15m with 7 Sats in 6s :D
[Captivate Android Development] gsx-r:
Sound that's impressive, but how about tracking?

My Cappy with un-fixed GPS file can get lock in 12 sec /8 sat (with data connection on) but tracking is not good at all. (Rom Kitchen JS5, JK4 modem, and Mobifone also :D)
[Captivate Android Development] nyydynasty:
you're right. I took it on a 20 minute drive just now. Although it put me about 100ft to my left twice during the trip, it corrected itself pretty quickly. It was quick with recognizing when I made a turn and when I didn't, which is a first for me. Usually it keeps going straight for a few seconds even if I followed the directions and made that last turn.

Interestingly enough, I waited about 2-3 minutes before google nav picked up the initial lock, which never happens. I usually always get a lock within 15 seconds. But the interesting part is where I had to keep my phone. Prior to this test, I noticed no difference whether I kept my phone in my cupholder or if I put it on the dashboard (for a clear shot to the sky). It never mattered before. It had equal performance in both locations. But with your fix, I had to keep it on the dashboard for an accurate fix. I'm assuming this is why it had a hard time getting my initial location because I had it in my cupholder, not the dash. As soon as I put it back in my cupholder during the trip, the blue circle got bigger and the tracking was VERY slow to follow me.

I guess I'll be purchasing a windshield mount, now. I'll do more testing on longer trips but so far so good.

thanks!
[Captivate Android Development] mhr650:
It seems to do what it was intended to do. Ever since I started using custom ROM’s I have been able to get fast fixes, but the tracking when using navigation was worse than it was stock, once it found you the stock system did a good job of keeping you on the track. This morning I gave it a tough test by taking the Blue Ridge Parkway to work, it is very hilly and curvy and Google thinks that it is closed in winter so it constantly tries to re rout you off of it. With the ROM’s I have been using I have had lots of off road excursions in sharp corners and it takes a while to get back on track. This morning it did a much better job of keeping to the track. I am using Paragon 5.1 with JK4 modem.
[Captivate Android Development] bames:
looks interesting so may give this a spin but it is contrary to everything i have experienced in regard to tracking.

Leaving WIFI while good for initial or stationary lock generally = worse tracking results because its using cell towers to triangulate your location vs. actual gps hardware.

Not sure if its just me but with current rom and several other customs i get excellent tracking but have to use different settings than recommended. The supl.google.com settings have never been good for my tracking results. Generally my best results come with the stock

www.spirent-lcs.com

supl. sec. off

set to control plane

Have you tested this at all with the spirent server?
[Captivate Android Development] bames:
not sure if its more related to my location or my build 1007

but jk4 has been my best for tracking on every rom i have used.
[Captivate Android Development] Jay_eS_Iye:
i'm going to keep this in mind. I've never had good luck with tracking but haven't gotten to try many fixes. I'm using the Phoenix fix that ryude has included for her Precision ROM but I'm without my truck right now (only motorcycle) so tracking testing hasn't been possible yet. But if that doesn't work I'll be trying these out.

Did you build yours upon Da_G's files or start from scratch?
[Captivate Android Development] Rrryan2:
Yeah. I decided to question conventional wisdom and take a different tack, basically deciding this thing needed all the help it could get.

Respectfully disagree. True, data (whether 3G or WiFi) is the biggest help during a "cold start" for downloading the almanac data and getting an approximate fix, which can take many minutes over the satellites. It's also most useful when stationary, because of course at highway speeds WiFi is rapidly out of range.

Don't confuse WiFi and cell/3G data either. Although they're both "wireless" they're different animals.

Turning on "use wireless networks" allows the unit to poll towers for their location and uses the names of any WiFi networks in range to make and initial "guess" about location which greatly speeds acquisition times. This might be especially useful in urban canyon environments when buildings and EMI make it difficult to get usable signals from the satellites. On rural highways... maybe not so much.

Again too, I just took the strategy that this thing needed any and all help it could get.

Could just be you. Many ROMs now include their own GPS tweaks, different modems seem to handle it better too.

No, I haven't. Mainly because the Spirent server is no longer reachable at that url as the domain name registration has now passed to a spammy "parking lot" so it's not even possible. Just try and browse to it. This is an example of the horribly bad job Samsung did in configuring these things. Not only was that server no longer reachable at the provided address by launch time, but including "www." in the address would have made it unreachable anyway. Utterly broken.

Really the only two other options are either supl.google.com or the 3gppnetwork.org (that defaults when auto SUPL configuration is selected). I had good results with both, but for the large-scale testing I made a guess that keeping things in-house with supl.google.com might be better. For one thing Google might more/better WiFi maps because of the Google Street View canvasses and information sharing from Android users. It also *might* play more nicely with Google software like maps, navigation, and, well, Android. I continue experimenting though.

"Control Plane" is an altogether different animal. The Control Plane is actually used by the cell networks to do things like coordinate hand-off between towers when the user is moving. Since it includes the very precise surveyed locations of the towers whose location doesn't change and a coordinated time signal, it should theoretically be helpful for approximate initial location fixes. If it's working, the SUPL settings are mostly moot which explains why you could still get good results.

However, I have not gotten consistently reliable results using Control Plane this way for unknown reasons. One thing I did notice was that the network time provided by the towers is usually several seconds off NTP-coordinated time which is typically closer to GPS time, though this could vary by region. For this reason I included NTP settings in the gps.conf file and forced SUPL mode.
[Captivate Android Development] Rrryan2:
Both/neither. I looked at what about a dozen or so fixes used. Da_G's is probably the closest to what I wound up using but I used a different strategy in tweaking the configuration and included a number of things he didn't.

There are only a few dozen lines of code of configuration settings though no matter which fixes you're looking at, and even Da_G's included some drop-ins from the Nexus S.
[Captivate Android Development] Rrryan2:
In analyzing mytracks data I see that it still does have some "ghost inertia" that carries the computed position through intersections even after making a turn. I expect this owes to imperfect smoothing algorithms and it may or may not be possible to improve. It's greatly reduced over what I had experienced under previous configurations, and I'm toying with the idea of forcing vehicle mode to see if it improves a little more.

In any case it now seems to recover much more quickly and requires less route recalculation so at least the nav is usable now.

Could be any number of things, among them the age of the maps cache and/or the quality of the data connection when downloading maps. If it continues happening or happens to more users I could look into it.

I think too that at least some of the problems we've been having owe to the fact that Navigator is still immature and in beta, as you're required to acknowledge when loading the first time. It's easy to forget. Of course, the app seems to work just great on most other devices, but anyhoo...

That's something else I think people forget too easily. The GPS just ain't gonna work if the antenna can't "see" over the dash or up through the roof. The Galaxy S series and the Captivate in particular also seem to have made a number of compromises to keep the super-slim form factor, which doesn't help any.

Remember too that the GPS antenna is on the back/underside of the device.

I have no idea why this might have been more noticeable using this fix as it's not really possible to adjust antenna sensitivity etc. with this chipset. In fact, I even tried and the GPS became inoperable. I'm going to have to regard it as a red herring for now.
[Captivate Android Development] crazililazn:
This^

with KP1, my tracking always lagged behind a bit. JK4 has definitely been the best modem for GPS performance.
[Captivate Android Development] Rrryan2:
Changelog for v0.8.3b:

Added regional localization for NTP servers to improve speed and accuracy of time sync for GPS for international users. This was reported by many users esp. in Europe to improve speed of initial acquisition (TTFF). For best performance download the version for your region, or if your region isn't listed or you frequently move between regions use the GLOBAL version. This is also the same thing that the "GPS Fix" option in SGS Tools does but provides options besides North America and Europe.
[Captivate Android Development] LinuxNewb:
Just get a car with in dash nav or buy one :) Crappy part is Lexus wants $300 for the updated maps. Torrentz and dual layered DVD ftw.
[Captivate Android Development] Rrryan2:
Well, yes. They tend to be $$$ options though compared to these. ;)

In-dash (especially OEM) nav systems will usually be superior to just about anything else, if for no other reason than they can use a large external antenna for GPS and augment it with INS (Inertial Navigation System) sensors.

However, the maps in Google Maps Navigation will tend to be very up-to-date without manual updates and provide traffic data. With no subscription fees.

A $30 external bluetoof GPS receiver is another less expensive and very effective solution. It just pisses me off to think that I should have to pay for one when the Blackberry Curve I had for 3 years had a pretty flawless GPS...
[Captivate Android Development] cumanzor:
No luck here. My GPS is still worthless. Some time ago I was running in a different config (modem/kernel/rom, dont remember the details) and it was working perfectly fine. I am now running Cognition v0.4, TLGL3, SuckerPunch 49, and my GPS doesn't work with or without this fix.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] bay_wolf:
Just did two tests runs. First time it wasn't accurate at all. Then the second run I held the phone a little higher and it never lost track of me or had bad accuracy (no blue circle around the arrow in navigation).
[Captivate Android Development] crazililazn:
I couldn't find it in the OP, but what operation mode should this be in? Cuz I tried MS Based mode and the tracking was terrible... x.x