yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Rrryan2:
With a quick look, that's more or less the same sort of thing I was thinking of putting together. I think a see a few things that might be tweaked a little more, but the improvement(s) would probably be pretty minor in real terms relative to the gains using plumbBob on Froyo.

If there's continued interest I'll see if I can put something together this weekend. Maybe I've been lucky but I've been getting entirely decent out-of-box GPS performance on most of the GB ROMs I've tried. But if there's a demand I'll see what I can do.

And FWIW the best Samsung GPS performance I've seen to date was on an Infuse. It locked quickly on the display inside the store, and I couldn't even get one bird on my Captivate held next to it no matter how long I waited. I'd want to look to Infuse code 1st before Nexus S, but I suppose I'd have to research potential hardware compatibility issues first (Anybody know if the Infuse still uses the Broadcom BCM 4751 GPS chip?).

Off the top of my head AngryGPS.apk (the much-improved replacement for LbsTestMode) is included in most Captivate ROMs. The only one I can think of that didn't have it was an early build of Mosaic, but I pointed it out in their thread and I don't even know if they re-included it in later builds.
[Captivate Android Development] jswclw:
Now that I an on gingerbread, gps is really solid, quick lock, accurate. Only complaint would be its tendancy to overshoot my location when I come to a stop at an intersection, sometimes thinking I missed a turn.
[Captivate Android Development] daverup:
I am on Serendipity VII now and found that my GPS was much worse than on the Froyo roms. I flashed the "proper_JVO_GPS_from_NEXUSs_234.zip" file and starting showing better results on the AngryGPS app. Obviously, results seem to vary depending on which phone build you have. Mine is 1007.

The AngryGPS never showed up on my app list, but I found it as a LauncherPro Activity.

I am also able to run LBSTestMode through SGSTools.
[Captivate Android Development] destrorox:
Seems by trying the nexus gps .zip I've borked my gps. It just hangs now. It will fix but then after getting a fix it freezes.

I'm on serendipity VII and wondering how to revert back to its original files without having to reflash. Any suggestions?

sent from my captivate using the xda app
[Captivate Android Development] nelsonw:
I have Cognition 5beta 2 and GPS was bad. But it had a decent fix. Installed PB 2 beta 11 and now it doesn't even fix... can it be reverted? I cleaned Dalvik Cache and check for Google supl. And also have FasterFix. THANKS!

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] mikel.canovas:
Does only 2bx work on gingerbread based roms? Or does 1.x work also?
[Captivate Android Development] Rrryan2:
Both 1.x and 2.x were intended solely or use on Froyo ROMs.

I'm still working on a set of GB tweaks, but in the meantime I'd encourage GB users to look at H3llstorm's GPS 'fix'.
[Captivate Android Development] iXNyNe:
I'm very much looking forward to a gingerbob or whatever you decide to call your next GPS fix, until it shows up ill go with h3llstorm. Btw is there an official thread or post for that somewhere?
[Captivate Android Development] minduka:
I'm having a problem installing in CWM3, running apex9.2

"Amend scripting (update-script) is no longer supported."

I understand this is because Amend was used and is not supported by CMW3,

Is there a way to get the Edify version? Thanks
[Captivate Android Development] bigbooty:
You need to read up about three posts. Not for gb.
[Captivate Android Development] minlee85:
please.....make one for GB...my gps is @#$%^&*!!!:mad::mad:
[Captivate Android Development] crazililazn:
Ok, im confused. In the first post, the picture shows Secure SUPL set as "no"

The 2nd post shows it set as "yes"

Both say they are recommended settings. Do we use the first one, or the 2nd one? x.x
[Captivate Android Development] Rrryan2:
Sorry for the confusion. I'll edit the post to clarify. The latest (0.8.4b) version includes the necessary certificate so Secure SUPL actually works now. I recommend it for security/privacy reasons (i.e. not broadcasting your unencrypted personal location over the intertubes), but it's not a big deal as far as performance goes.
[Captivate Android Development] crazililazn:
Mkay, tyvm for clarifying that :)

Sent from.... Waiting for Location....
[Captivate Android Development] Rrryan2:
Off the top of my head it needs at least 28dB SNR on at least one bird to get a time sync for initial fix. After the initial fix it can use weaker signals. I recall reading that Sirf STAR III can hold a fix as low as 12dB but I haven't come across a published spec for the Broadcom BCM4751 in these.

Eh. There are others. Audience chip for one, which is why the ports from Rogers ROMs etc. don't include support for it. The drivers could reasonably be considered proprietary closed source and there might be nobody complaining if they actually worked.

Heh. Saw a guy today sitting at a red light holding his phone out the window above the roof. Didn't see if it was a Galaxy though. ;)
[Captivate Android Development] sjavvaji:
yea...the jm9 i was using did have the supl.google.com settings as default so it performed really well but i just tried your fix and it blew me away...i normally get the same amount of satellites with jm9 but it got my location with so much more accuracy
[Captivate Android Development] Rrryan2:
Hmm. Got a link or can you upload it? I'm constantly looking for more clues and would be curious to see what else is different.

Good to hear! :)
[Captivate Android Development] sjavvaji:
this is what i was using...got it from some obscure i9000 thread
[Captivate Android Development] mcann:
New Captivates and GPS

I will apologize first for a long post.

I was dealing with the same GPS issues as everyone in this thread is having. I am speaking in the past tense because my GPS issues are a thing of the past. Unfortunately, I have done the xda community a small injustice. Let me explain...

There are 3 main KNOWN issues with all Captivates.

1. random shutdowns

2. battery drain

3. a GPS system I would only let my mother-in-law use to find my house

Yours may have none. I was having all of these issues and after flashing various ROMs, no luck. Some made shutdowns worse, some better. Some battery drain was worse, some better. None of the ROMs were great with GPS. Some were enough of an improvement to actually allow me to navigate with them. Still some off the tracking by hundreds of feet, huge blue circles, etc. With no cure in sight I reflashed back to stock and went to the Device Service Center (warranty repair). The DSC is well aware of these problems. The Cap is even on their Featured Device List. For the owner of a phone on the list, it means you won't get much of a hassle with a return. I walked in with my problematic phone and walked out about 10 minutes later with a new phone, albeit a refurb. I returned a build 1007 and got back the same. I asked for a later build, but the tech said it was all he had. This is where the injustice comes in. Instead of doing a little scientific research, I flashed a new ROM as soon as I got back to my office. I should've worked with the new phone for a day or two to test it out. But I didn't. What I can tell you is that the GPS rocks! 8 sats inside my house in seconds, more outside. On the windshield, my lap, cupholder - doesn't matter. Spot on, no blue circles. I turn, it turns. I stop, it stops. I try to confuse it by not following its route, it re-routes immediately.

I've flashed about 5 different modems and 3 kernels, GPS works every time. To avoid any ideas that I'm trying to promote a ROM here, I will not disclose which one I am using. You may PM me and I will let you know. Or if the OP wants me to post it here, I will do so.

My suggestion to all of you Cap owners with GPS issues - bring it back to your nearest DSC. MAKE SURE YOU REFLASH TO STOCK AND WIPE! Also, don't mention the GPS issue as your reason for returning it. AT&T is not taking returns for that. Use the random shut down issue or battery drain. They already know about it and can't test something on the spot if it's random or wait and time your battery drain. If you make the return, do those here a favor and see how the GPS is working before flashing a custom ROM. Report your settings and findings and maybe the OP can come up with a working solution.

Once again, sorry for the long post. But your easiet solution might just be a new device. It worked for me and it took considerably less time than adjusting and testing the lbs settings, which I did for days, by the way. Good luck!

MC
[Captivate Android Development] Rrryan2:
Heh. Nope, that's the same one I had found. I read through a lot of long and obscure threads to in researching this too. ;)

It contains a similar binary for the glgps daemon that I (and more truthfully Da_g) used, but the /etc/jupiter.xml in that .zip still specifies lcs-spirent.com. Unfortunately it can't just be changed in LbsTestMode alone and all the settings in the various configurations have to match to work right.

Samsung did a really awful job of designing the control interface on these, which is probably why more experienced devs often seem simply threw up their hands and move on to more productive endeavors after beating their heads against it for a while.
[Captivate Android Development] Rrryan2:
(Excuse me for the selective quote, but I think this bit summarizes your post neatly and succintly)

I'm not afraid of contradictory opinions. And in fact I think you're exactly right. I had considered the same and even got a UPS return label from Samsung to do a repair/exchange with them.

My personal, emotional, and irrationally subjective objections to this though are:

I don't have absolute confidence that I wouldn't just get another similarly flaky GPS with the same flawed config, and

Frankly, it pisses me off that I should be expected to accept a refurb when all the devices I had never worked *right out of the box.*

For me, this is an amusing challenge for the moment and it gives performance I can at least live with for the time being. But if in another month or so Samsung still hasn't rolled out that mythical fix (AND FORYO!) I think I might too just drive over to my DSC too for a "refresh." And I'll do it with a clear conscience too, since it wasn't working *out of the box.*

(AT&T users who are interested in this should go here: http://www.wireless.att.com/answer-center/main.jsp?t=solutionTab&solutionId=KB91429)

If you're ever about to flash a new ROM I'd be curious to see what happens if you tried my fix to see what happens. I've only heard from one tester so far who tried it on a refurb and the results were non-wonderful. And if anyone does this, I'd love to be able to see what the refurb units are using for configurations to see if it's different.
[Captivate Android Development] Rrryan2:
Believe it or not, the antenna is on the volume button side of the housing. So you might actually get even better reception by orienting it in "upside-down landscape," i.e. home buttons left.
[Captivate Android Development] Ikonomi:
I'm jumping on board with this. I'm one of the unfortunate souls that have had no luck with any of the GPS fixes out there, including Da_G's excellent work. The GPS in my 1006 Captivate is so hopeless that I've purchased a standalone Bluetooth GPS receiver which works fantastically.

And yet I, like you and everyone else, would like all the features of his multi-hundred dollar smartphone to function properly. I can't wait to try this fix out tomorrow. Thank you in advance for your hard work on this project. I'll definitely be keeping up with it.

SGH-i897 | Perception 10.2 | SpeedMod K13C | I9088ZNKP1
[Captivate Android Development] sjavvaji:
dude you are awesome for working on this...thanks for working on such a monumental task
[Captivate Android Development] Rrryan2:
Modems Matter

I'm convinced now that the modem used affects GPS performance more than a little bit. I'll be assembling a list an updating as reports continue to come in.

If your modem is or isn't on the list though it's not necessarily meaningful.

Modems that are

known

to work with this fix so far:

JL3

JK4

KP1
[Captivate Android Development] sjavvaji:
yea...this doesnt work well for me after testing it in a car...the gps test shows a small area but the navigation while moving is just terrible...im back on jm9 after restoring the files this flashed over...back on my incredible gps...jl2 batch 1009
[Captivate Android Development] mcann:
No offense taken! I know it was a bit long-winded, but I just wanted to stress the point that anyone wishing to make a warranty exchange at the DSC should NOT use the GPS as your reason. You will be pointed to the door and told to wait for a Samsung OTA fix.

I am upset with myself for not working with the phone first. Are there actually Caps with a working GPS right out of the box? I was making the assumption that there was a design flaw and all of them were faulty. I wasn't thrilled with taking a refub either, but it's working. It seems that the later builds (>1010) are not friendly to flashing. If you do exchange, look for an early build. So, am I just plain lucky that I've got a smokin' GPS now? While I was typing, I turned off my phone, restarted and placed it on my desk, about three feet from a window. 8 sats locked in 6.5 seconds, accuracy 15 meters, now at 5 meters that it's been on for a few minutes.

If your exchanged phones' GPS isn't working, bring it back for battery drain. Or whatever reason you didn't use the first time!

There is a stock 2.2 Captivate ROM hitting the boards as we speak.

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

Maybe you can find some wisdom in there? If you are interested I'm happy to forward my settings to you.

MC
[Captivate Android Development] sjavvaji:
yup...good advice...im lucky that i can get good (legitimately) with the jm9 fix...when i got my phone on jh7...it would not lock at all in the clear outdoors...would not even recognize a satellite...i had to flash froyo before anything worked...i would not do this myself because i have one of those few phones that can do 1.45ghz stable
[Captivate Android Development] Rrryan2:
Dangit. So very frustrating. If the results were at least consistent I might be able to decide what to do. For some it's just great, for others mediocre, and for a small number it's just terrible.

I'm beginning to suspect that the Nexus S glgps daemon especially doesn't want to play well with all modems. I think this is the only feedback I've had for JL2 yet but KP1 and JK4 seem to work great.

I'm toying with the idea of making a test version that only gets the AGPS working successfully and leaves all the binaries, smoothing etc. alone if you or others feel up to testing.
[Captivate Android Development] Rrryan2:
Depends on who you ask. From what I can tell about 30% or so do seem to work properly out of the box (new/retail).

I've had a 1008, 1010, and 1007. I kept the 1010 and sent the 1007 (replacement for fualty GPS that didn't work either!) back since I liked the 1010 display better. Had no issues flashing; maybe I just got lucky there. ;)

Yeah, pretty much. At least in my opinion.

This actually sounds like your GPS itself is working fine but the AGPS augmentation isn't. It sounds as if it's updating the ephemeris (info each bird sends about its orbit and trajectory, broadcast every 30 sec) from the satellite signal itself over a few minutes, whereas with AGPS the 50k or so of necessary data is downloading far more quickly.

Of course, I'd understand if you want to just leave well enough alone too. :)

I'll have to give it a look. If nothing else it might be interesting to see if the config. has been updated or if there's something to use besides bogarted Nexus S binaries.
[Captivate Android Development] sjavvaji:
have a drive on jm9 after clearing your edited files and gps data...i was extremely surprised this morning that it didn't work because it was great in the house...i tried it on a bus and it didn't lock on for 5 minutes but then it was shady...in my car, it locked on in like 20 seconds (still long) but the area was flashing between like 16 feet and 150ish feet. never stable...jm9 works with a 5 second lock and gives me a consistent lock...i will test it on the bus tomorrow to see if jm9 works there too
[Captivate Android Development] mcann:
Your understanding of GPS technology seems very strong. My understanding of it is "it gets me from A to B". It may not always be the best route, but I do get there eventually. If my GPS wasn't running so smoothly right now, I would certainly alter some of the settings. Users who flash their ROMs don't subscribe to the theory of "if it ain't broke, don't fix it". We are always looking for the next best ROM. But I do use the GPS and I would hate to have it acting like the ~70% of Caps. I'm so satisfied (finally) with the phone as it stands, I might not even flash another ROM until there's a stable Gingerbread.

I guess I'll go to bed feeling lucky! About the phone, that is.

MC
[Captivate Android Development] perosredo:
Is there a known reason/fix for GPS and Google Maps not playing nice together? GPS locks fine in LbsTest but Google Maps can't get a fix whatsoever.
[Captivate Android Development] }{Alienz}{:
I have a Vibrant. Will be trying this in conjunction with JL4 modem as its the closest to JL3 we have for the Vibrant.

EDIT: I believe it's not working. Terrible locks really. 3 satellites in 4 minutes...still not locked of course.
[Captivate Android Development] Rrryan2:
Known/documented reason? No, not that I'm aware of. It's also not 100% clear whether the problem is actual GPS tracking on the move or flaky Google Maps Navigator code. Google seems to bypass some of the configurations, which might even be contributing to the problem.

If you want to see something really weird, try running Mytracks while navigating along a route with Google Maps Navigator, and then make a turn not suggested by the route. The Mytracks track will "ghost" you along the route for a bit more than if you weren't running navi. Same road, same turn with no routing = no ghost inertia through the intersection in Mytracks. It's not clear if this is a Google problem or a Samsung/Broadcom GPS problem.
[Captivate Android Development] Rrryan2:
UPDATE - EXPERIMENTAL v0.9

CAUTION: EXPERIMENTAL! GET A NANDROID BACKUP FIRST!

These are essentially the stock configuration files from the KB1 leak, which contains a new driver library. In a deviation from my previous strategy I decided to retain the stock settings (standalone, pedestrian, etc.). Since acquisition and tracking performance with the stock settings seems to be working properly I have decided to leave them alone for the time being.

Initial testing on KP1 was very successful. Since it includes the updated libraries I expect this will work on the new KB1 ROMs but haven't been able to test yet. I'm getting ready to flash Cog 4 to test.

v0.8.4b will be left in the OP for now just in case anyone needs to roll back. Will update later depending on testing reports.

Changelog:

- new libsecgps.so from KB1 leak

- New jupiter.xml from KB1 leak (uses 3GPPnet.org instead of Google for SUPL service)

- new secgps.conf from KB1 leak

- glgps daemon in Nexus S (used in previous versions of this fix) is the same as KB1, retained

Updated LbsTestMode SUPL/CP Settings (Must be made manually):

Sever FQDN Type: Auto Config (Should default to h-slp.mnc410.pub.3gppnetwork.org and Port 7276)

Things to do:

-investigate why jupiter.xml lists 7275 as SUPL port setting but LbsTestMode defaults to 7276. Initial guess is that it is (now?) correctly looking to the LbsTestMode settings for SUPL configuration. Or maybe either will work...? :confused:

Testing reports greatly appreciated, but please specify ROM/Modem as well to aid troubleshooting!
[Captivate Android Development] Rrryan2:
Test case yielded mixed results. With Cognition4 stock settings I get initial lock in about a minute, quick warm starts thereafter.

With 0.9 added... it's about the same. Can't track or lock on more than 6 birds with either in the location where I was getting 11/11 before. This will require more study.

On the plus side, at least it doesn't break the KB1 GPS. :)

I also noticed that UCKB1 includes an updated LbsTestmode.apk as well judging by the MD5 checksums.
[Captivate Android Development] bames:
am i the only one using the standalone settings?
[Captivate Android Development] ewingr:
I'm sure you saw some of my posts during your research. As noted in your posts, important aspect is having good clear view of the sky; and I found also wiht repeated tests that having the metal back off helped also. (I have it in a Seido Innocase, so the back is not necessary, so this works OK for me).

All that being said, even though my GPS has been good most of the time (no, not perfect), a couple weeks ago I broke down and purchased the external Bluetooth device. It's a bit more of a pain to use, but not that much, and I get 3 foot accuracy, and absolutely no driving in fields, or blue circles.

I wonder if I would get down to 1 foot accuracy if I implement your fixes :p
[Captivate Android Development] perosredo:
The back is carbon-fiber.
[Captivate Android Development] chasesavestheday:
which gps fix is included in the SGSTools app?
[Captivate Android Development] Rrryan2:
No. It's aluminum made to look carbon-fiber-ish. It's also used to serve as an auxillary antenna, but apparently the aluminum was chosen more for its lightness than its suitability for an antenna material, because aluminum makes slightly awful antennas.
[Captivate Android Development] Rrryan2:
The SGS Tools gps "fix" only allows the user to select between Europe or North America for the location of the NTP time server specified in gps.conf. A better version of the same tweak has been included since 0.8.3b.
[Captivate Android Development] movielover76:
Good results on experimental

I have a version 1007 captivate, which was formally working with some fixes and completely broke when I installed cognition 4.0

installed the experimental version over cognition 4.0 and my gps is working so far

8 satelite lock in 10 - 15 secs

on stock KB1 I was getting two or three satelite's and no lock no matter how long I waited.

Working in Maps, 30 meter lock indoors.

I will do some mytracks testing when I go out tommorrow

thanks for the great work
[Captivate Android Development] CuriousTech:
It would have been better as a CF back with a flat flex circuit antenna attached to it. lol

I couldn't get a fix on Cognition 4 either, after 5 mins which is a first. I used GPS Status (market app) and even loaded AGPS a couple times in the app. 0/0, no signals at all. Then went to LbsTestMode, changed the server, then ran the fix test. Fix in 5 seconds. Went back to GPS Status and it worked. Then a couple hours later it was dead again. Whatever Samsung did seems to be more flaky on mine.