yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mikeypopps:
Wow, this works great on cog 4.1

Cleared gps data, installed, turned on wifi and gps and got a lock indoors in 6 seconds. Only difference from recommended is I run it with ms assisted on.
[Captivate Android Development] ru-dmitry:
I am sure Adam's fix uses AGPS too. I don't know HOW, but it does. Because <10s coldstart is impossible without AGPS. Please correct me if I'm wrong.
[Captivate Android Development] rajendra82:
Is the JV1 leak using an even more updated agpsd than KB1, or is it just more tweaked configuration? Looking inside their GPS fix, they're using supl.google.com, but port 7275. Isn't that going against everything else up to this point, which said to change to port 7276 for the google server?
[Captivate Android Development] FeO2:
0.942 working good on Serendipity 5.12 here :cool:
[Captivate Android Development] bhairya:
I second that. Working better for me as well. The previous one didnt.
[Captivate Android Development] Rrryan2:
Yes, it does. But it also specifies enhanced-assisted="false" in Jupiter.xml. It's another one of those things where with the drivers being closed-source it's not quite clear when it might actually make a difference. Indeed, in a well-designed configuration interface making changes here shouldn't be necessary or even helpful. But in my opinion at least it's also one of those things where it certainly can't *help* to specify an unhelpful configuration.
[Captivate Android Development] Rrryan2:
I'm not sure what difference the 7275/7276 port setting would make. I was able to telnet into both of them, but had little success using 7275 on the Captivate. 7275 seems to be the industry standard for just about everything else.

Are you looking at the raw JV1 leak, or the "fix" that was in the Vibrant forum? I'm going to sit down tonight and digest and md5 compare the JV1 leak files to see what might have changed. But one early version of the "fix" posted on the Vibrant forum last night seemed oddly schizophrenic, with several re-named versions of jupiter.xml scattered throughout. Can't see how that might be helpful myself, but maybe jellette knows something I don't.
[Captivate Android Development] Rrryan2:
From http://www.vzwdevelopers.com/aims/public/menu/lbs/LBSFAQ.jsp#GenQues10 :

What is MS-Assisted mode of operation?

In MS-Assisted mode, the network elements calculate the location of the device. This mode is suitable for one-shot fixes, wherein the location does not need to be updated frequently.

What is MS-Based mode of operation?

In MS-Based mode, the network provides the satellite information to the device, based on a rough estimate of where the device is located, and the device acquires the GPS signals from the satellites and calculates its location. After the initial fix, the device operates like an autonomous GPS receiver, until the satellite information must be refreshed, at which time the device goes back to the network to update the satellite information. MS-Based mode is appropriate for applications that require the device location to be updated rapidly, such as a navigation application. "

In short, MS Assisted is basically determining position based solely on the signal from wireless towers and is unlikely to be helpful in this role. MS Based gets info about the satellites and an approximate initial location from the towers to help speed the initial acquisition, and then uses its onboard GPS.
[Captivate Android Development] iXNyNe:
i tried out 0.942 and i have no locks again

i got no locks with 0.94 as well but i was able to switch back to 0.93 and get locks again, now i cannot

i also tried going back to 0.84b with no luck, so i pretty much have no gps right now :(

i tried all kinds of combinations for settings too btw

could just be my luck, if it works for everyone else then maybe im doing something wrong, i just dont see why i cant fix it by flashing back
[Captivate Android Development] Rrryan2:
Settings -> Location and Security -> Use GPS satellites = on?

Settings -> Location and Security -> Use wireless networks = on?

LbsTestMode -> SUPL/CP Settings -> Server:supl.google.com, Server Port 727

6

?
[Captivate Android Development] iXNyNe:
Yes to all
[Captivate Android Development] Rrryan2:
:(

Don't know what's up then. I'd encourage you to note that in the OP JL2 is described as a modem that is known to not necessarily work so well with this fix.

You could try rebooting to recovery and clearing the Dalvik cache. If that doesn't work, I'm sorry and I'm out of ideas. :(
[Captivate Android Development] iXNyNe:
Didn't think of the modem or dalvik. Will try those. Kinda makes me sad to have to leave jl2 cuz its been lovely otherwise but hopefully that's all this issue is.
[Captivate Android Development] iXNyNe:
Well I tried jl3 and clearing dalvik, no luck.

I did recently switch kernels (earlier today, from suckerpunch voodoo to suckerpunch speedmod)

Would that maybe have any affect?
[Captivate Android Development] askpcguy:
Writing this on Fusion and with no GPS fixes I got an indoor lock in 95 seconds.

Might be worth looking at.
[Captivate Android Development] CuriousTech:
MS-Based sounds best.

<10s does require AGPS. It wouldn't be possible to go from cold start to fix in less than 30 seconds, or closer to 45 is about average.

In a nutshell GPS works basically like this. From a cold start the GPS has to scan channels listening for satellites, and requires (I think) at least 6 seconds per each one to at least catch the beginning of a data subframe. Full frames start on the half minute (atomic clock time). So without AGPS, scanning can take several seconds, then once it catches the beginning of a frame it takes 30 seconds to get all the data it needs, then knows what nearby sats are there and can listen for them, and a few seconds later should have enough for a fix after doing lots of time over distance calculations which take time. They have 12 or more channels so it's all running in parallel. But that can easily take 1 minute but shouldn't take much more. If it takes longer, reception is probably poor.

AGPS is like taking the whole process of building that fixed state, and just dumping it into the GPS in less than a second (all the satellite locations and your location or close enough) and turning it on. As long as reception is good, all it has to do is try to listen to the ones it should be able to hear and get back in sync with their data (<6s). If it can't hear any at that point (like starting up in underground parking), it'll invalidate the data (cold start) and begin channel surfing. So it's best not to start it up 10 seconds before walking outside for example.

There's much better info on all that on wikipedia and other sites if anyone is interested in the inner working of it all.
[Captivate Android Development] NascarFastcar:
How do I install the latest fix to a Stock Captivate with froyo? The phone is rooted with superoneclick and I have clockwork recovery.. Every time I go to reinstall packages it always looks for a update.zip which I dont have.
[Captivate Android Development] dalewest:
Out of curiosity....

Has anyone attempted to compile some sort of modem & GPS 'success' matrix based on the stock number of the phone? Some people claim that your fix works wonders while others don't, and they might even be running the same kernel, rom, and modem. Unless Samsung has serious quality issues in their manufacturing plants (which could be the case for all we know), and if all other things are equal, then the only real difference would be the batch number of the devices. IIRC, 1008 had issues with something, but later runs were fine (or vice versa).

Just sayin.
[Captivate Android Development] mopo01:
Someone posted in the app thread about tel nav works better than the google nav used it today spot on with paragon stock gps fix. Might be worth checking out.
[Captivate Android Development] iXNyNe:
I reflashed everything (rom, kernel, modem, plumbob)

I'm now on fresh paragon 6, suckerpunch 53, jk4 (as much as I don't like it) and 0.942 fix

I'm at work any my building is a black hole, so ill test more from home and on the road.
[Captivate Android Development] kevria:
I flashed this onto my wifes stock froyo phone last night. Prior to flashing this she might occasionally see 1 satellite. After flashing PlumbBob she sees 7-9 satellites and quickly gets a lock. Thanks all, now her GPS is useful.
[Captivate Android Development] Rrryan2:
Pointless endeavour. Far too many permutations and combinations of ROM/Kernel/Modem and/or versions of this and other fixes etc. The sample size would have to be enormous to get anything of statistical significance, and even if we found a problem with a particular build number or IMEI range there would still be nothing we could do about it. Not like you could even take the data to Samsung or anything either. If they cared and were capable of fixing the GPS problem(s) they would have by now. They either can't fix them and/or don't care. All there is to it.

And although QA/QC problems might contribute to the GPS problems we're having, there's still nothing to be done about design compromises about antenna size, location, and material (aluminum caseback!).

This is something I work on in my free time, and as such I prefer to put energy into areas where it might actually make a difference.
[Captivate Android Development] Rrryan2:
Apps --> ROM Manager -> Flash Clockwork Recovery.

Copy the .zip of the fix to the root of internal sdcard.

Reboot into recovery mode.

Install from sdcard --> Choose file --> select the appropriate .zip --> yes I'm sure.
[Captivate Android Development] NascarFastcar:
When I reboot into recovery mode I get these options only.

reboot system now

reinstall packages

delete all user data

delete cache data

format internal sd-card

And if I do click reinstall packages I get the

E:failed to verify whole-file signature

E:signature verification failed

Installation aborted.

This is stock froyo and rooted with rageinacage via superoneclick. Clockwork is flashed and all... Phones built 1009.
[Captivate Android Development] kevj:
Look here for the 3e recovery fix that allows installation of non-signed zip files.
[Captivate Android Development] Rrryan2:
Hm. That might help but really shouldn't be necessary; the .zip is actually signed. For whatever reason it doesn't seem like Clockworkmod recovery wants to 'take' but unfortunately I don't have a solution.
[Captivate Android Development] iXNyNe:
reporting back, after all my freshness things seem perfect on 0.942

getting locks indoors again, tracking well while on the road (will report more tomorrow during road trip)

anyway, keep up the good work!
[Captivate Android Development] Rrryan2:
Good to hear! I was concerned when a (relatively) longtime user was having problems that bad when everything had worked great before.

Maybe just a bad flash?
[Captivate Android Development] iXNyNe:
Yeah I think something jacked up one of my kernel flashes and it caused some bigger issues. I'm getting 10-30 meter locks in under 15 seconds consistently now.
[Captivate Android Development] ccdoggy:
I am looking for a little input on my problem.

My GPS was AWESOME yesterday, then something happened and everything was ForceClosing on me. re-flashed the same rom, then same kernel, then your tweaks and i get terrible GPS. Then i backed everything up and erased & reset to defaults and re-flashed everything again. Still nothing.

It looks like its downloading the GPS assistance data but its as if it is never actually using it because i get a 4-5 sat lock in 5-10 min. Used the GPS app to re-download the data, SGS tools to delete it, and others and still nothing.

The weird part comes that I had this problem before with my phone with the same rom/kernel/modem, I called for a replacement captivate but then one day my GPS worked amazing (before getting the replacement) and have never had a problem since till i had to re-flash. I sent back the replacement phone as mine was acting just fine.

Any ideas?
[Captivate Android Development] 41LY45:
Working fine with Andromeda 1.2 with Suckerpunch kernel #53. :)

Longest i got for a lock was 8 secs. :D
[Captivate Android Development] eliminat:
Anyone tried .942 on a non KB1 rom yet? I'm still on Cog3 and would like to know how it works compared to the non-kb1 .84b
[Captivate Android Development] iXNyNe:
I'm on paragon 6 (js3) with suckerpunch #51 and the jk4 modem using this fix (0.942) seeing significantly better results than when I wasn't using it

The fix (even latest version) does not seem to require any particular rom/kernel, although some modems supposedly have issues
[Captivate Android Development] NascarFastcar:
Thanks alot man!! That did the trick. Gonna test my gps now.

Reporting back. Getting about 7-8 sats inside with under 10 seconds lock. About 45-100foot acc that improves the longer gps test runs etc.

Outside im getting 11 sats locked with 16foot accuracy. I have never seen anything below 16ft/5m is that even possible on these phones?

Plus im getting SNRS up to 48!.
[Captivate Android Development] Rrryan2:
Recent reports seem to indicate that the most recent versions work with most ROMs. It's beginning to seem that some earlier probs with a buggy install script and file structure were being mistakenly attributed to modem quirks.

Over the weekend 0.942 is probably going to be re-badged as 1.0 since it's now stable and seems to work with most everything. I'll drop 0.8.4b in another post just in case, but I no longer think it's necessary to have both.
[Captivate Android Development] Rrryan2:
5m is the lowest I've ever seen. Don't know why, as any modern WAAS-enabled device should be capable of better than that and the BCM4751 can utilize it. Out of ignorance or apathy Samsung seems to have left it out though for whatever reason.
[Captivate Android Development] ridethelight:
both recommended and newest releases have had 0 affect on my GPS lock. I used to get a general location (about 100-200 meter circle) when i first started flashing ROMs, that has gotten increasingly worse with everything I've tried to make it better. After Adams GPS fix, maps gave me no location, ever, as apposed to a general location within seconds. Plumbbob also gives me no location in maps and 0 satellites in view(had 3-4 with adams GPS fix although they never got used).

using UGJL4 modem which gives me the best data and connection in my area, so i refuse to change it. Thanks anyway! Hope it works for some people.

The ONLY thing I miss about my BB Bold 9000 was the instantaneous GPS lock wherever i was no matter what.
[Captivate Android Development] snorkle:
"Changelog (0.9)

0.9:

- new libsecgps.so from KB1 leak

- New jupiter.xml from KB1 leak

-new secgps.conf from KB1 leak

- glgps daemon in Nexus S is the same as KB1, retained"

im running fusion and i notice in the first post you said that this fix does not work with KB1, so in v .9 + does that mean its working with kb1 now?

thanks
[Captivate Android Development] Rrryan2:
Sorry, I'll try to edit that mess that the OP has become later tonight. 0.9 and above were designed with UCKB1 in mind and are now believed to be fully backward-compatible with other setups as well. :)
[Captivate Android Development] snorkle:
so it doesnt work with KB1? xD
[Captivate Android Development] NascarFastcar:
I have it working on atnt stock kb1.
[Captivate Android Development] drancid:
WOW!!

0.942 fix works great with Cog4.1!!! nice work!! Thank you so very much!!
[Captivate Android Development] askpcguy:
What are your LbsTestMode Application and SUPL settings?
[Captivate Android Development] iXNyNe:
Follow the directions in the post for the fix you're using for best results (the op still has 0.8x which uses different settings than 0.9x so if you're using 0.9x follow the link from the op to get the 0.9x settings)
[Captivate Android Development] askpcguy:
I was not asking that.
[Captivate Android Development] drancid:
i used the lbstestmode to change settings.

My settings are

Tracking

S/W test

Ms base mode

Hot start

On

On

50

Off

Custom config

supl.google.com

7276

on

SUPL
[Captivate Android Development] askpcguy:
Thanks, I think my problem is coming from using the KB1 kernel and modem. Others using ROMS based on KB1 do not seem to have the same problem.
[Captivate Android Development] Rrryan2:
Wouldn't think so. All the binaries are lifted directly from stock UCKB1, and the rest is pretty much ROM/modem immaterial. I'd suspect a bad flash tbh.

Fwiw I was developing using Cog 4 KB1 until I got tired of not having my suckerpunch oc / UV and reverted to KP1. Kp1 seems slightly better at GPS but not drastically so, and plenty of users are reporting great results with cog 4 and other kb1 solutions.

You might just try reflashing.
[Captivate Android Development] askpcguy:
I really hope its just a bad ROM or flash.

I'm considering looking at http://xdaforums.com/showthread.php?t=897416
[Captivate Android Development] drancid:
yeah.. cog 4.1 is based on KB1 also
[Captivate Android Development] D12AKO:
Well, after several days of driving including one day with heavy overcast v0.942 seems to work really well overall.

Back then I barely got GPS to work properly on a clear day so the fact that it tracked really good on overcast was amazing.

Will try and compare rout tracking vs Adams Fix soon by Driving same route a few times with each under similar conditions.
[Captivate Android Development] Rrryan2:
Keep in mind that this fix contains files that Adam's fix doesn't, so simply flashing Adam's fix over this one won't remove all the changes and will not give a direct 1:1 comparison. You'd really need to start from a clean flash to compare so you're not looking at a mutt hybrid.

As well, Cog 4.1 and above already contain Adam's GPS fix and many users still report improved results adding this fix.

I'm getting v1.0 ready to launch in the next day or so. The changes will be pretty negligible over 0.942 though. Biggest change is a bigtime re-write of the OP. After testing this version is now stable and effective enough to launch, and I'm now running out of things to continue tweaking.
[Captivate Android Development] bobapunk:
Ok, Noob Question here.

#1 My GPS worked pretty well on stock 2.1

#2 Since updating to 2.2, I have not been able to get it to lock once. Even the Samsung Fix and the GPSFix app fail to get a lock.

So, I am eager to try this fix as I have read good things about it.

My question is this: I have been told that CWM does not work with KB1. The instructions for this fix (supposedly specific to KB1) state to install it by flashing with CWM... Well, if CWM does not work on KB1, this makes no sense...

Please explain!
[Captivate Android Development] mbc663:
Flash with cwm.
[Captivate Android Development] iXNyNe:
Cwm should work just fine on a kb1 rom however this fix may not play nice with the kb1 modem
[Captivate Android Development] rajendra82:
I have stock KB1 modem and Stock KB1 + Voodoo kernel, and version 0.942 works great.
[Captivate Android Development] bobapunk:
Ok, I guess that is that then...

On the topic of flashing ROMs I was told that I had to use Odin go back to 2.1 before flashing a custom ROM because CWM did not work with the 3e recovery mode that 2.2 uses...

Hopfully this fixes my GPS.

I think I may have broke it by applying a fix via SGS Tools that did not work well with KB1.

UPDATE:

Ok, either I am a total noob or I need more coffee...

Either way, I have having a small issue.

I installed CWM via Rom Manager.

I reboot into recovery intending to follow these steps:

Open rom manager app
Click boot into recovery
Brings you to green clockwork recovery
Select install or apply zip from sd
Scroll using volume up and down
Select zip using power

The problem is that I do not have an option to "install zip from SD". I just have

reboot

reinstall packages

delete all user data

delete cache data

format internal sd

So, what am I missing?

Thanks!

UPDATE 2

Ok, so was just rewatching some mobile tech vid ROM reviews and it became obvious that I am booting back into the Samsung Recovery and not CWM Recovery. So can I get into CWM Recover with 2.2/Froyo/KB1 so I can install this GPX Fix? If so, then how?

Thanks!
[Captivate Android Development] wmbenham:
Thank You!

I just applied the fix and my indoor locking is amazing. I've yet to leave the house today, but when I do I'm using Navigation to see if this is the fix that will actually stop all the GPS dropping I've been experiencing. You are the man.
[Captivate Android Development] mbc663:
Happy trails!
[Captivate Android Development] kevria:
This fix worked fine on my wifes stock KB1 phone.
[Captivate Android Development] rajendra82:
The froyo update KB1 kernel uses the 3e recovery, which checks signatures for update.zip files, so it can't be used to flash this fix. What you need is a kernel with CWM recovery built in. Go to the dev forum, and get the Odin flashable version of supercurio's stock KB1+ voodoo kernel. This fixes the recovery issue too, do that and you will be able to flash the GPS fix afterwards in the red CWM recovery. Flashing either does not erase any user data, so after each reboot, everything else will look the same.
[Captivate Android Development] nakedninja42:
I saw this article yesterday http://www.tomsguide.com/us/google-maps-android-phone-android-os,news-10378.html about new real-time traffic updates coming from Google for Navigation. Do you know if the fix is going to affect the updates for the GPS? I assume no since the SUPL is directed to supl.google.com.
[Captivate Android Development] bobapunk:
Many Thanks (yes I clicked the button)

I will have to try this later when I get home.
[Captivate Android Development] reinbeau:
Should I use the old version, or this new 0.942 version, on Serendipity, with the modem that comes with the ROM (JK4)?
[Captivate Android Development] mnjm9b:
I hate to even ask this...

How much (if any) of this could be applied to CM7???
[Captivate Android Development] rajendra82:
I doubt it is directly applicable to CM7. Although CM7 most likely uses the Nexus S agpsd driver (same as Captivate after the KB1 update), the location where it stores the settings and the files it stores them in are probably very different. If you figure the differences out, you can probably apply the same fixes contained in 0.942 by manually editing the equivalent settings files in CM7. Not sure it needs it though.
[Captivate Android Development] madmack:
I have a I9000M. I tried 0.942 on Darky's 9.3 beta with JL2 modem. So far very impressive results in tracking although I sort of lost the initial fix speed I used to get previously (5-10 s). Now it can be anywhere from 20s to a couple of minutes.
[Captivate Android Development] Dnorwood:
Not entirely true, you can install a fix that installs a 3e recovery that doesn't require signatures. Search the forums, someone made a script to automatically install this. Currently I am running stock kernel with the fix and have cwm working great, have backed up my rom and flashed files with.
[Captivate Android Development] NascarFastcar:
This helped me alot.

http://xdaforums.com/showpost.php?p=10517130&postcount=1
[Captivate Android Development] LMSarmiento:
PB,

Job well done with 0.942. As a user of Cog 4.1.1, I was getting erratic-at-best GPS locks on my cappy.

Even with the question mark regarding the viability of 0.942 with the official froyo modem, it was worth the try. The payoff is a GPS that is once more locking in seconds (instead of minutes...maybe) indoors and outdoors alike.

Keep up the great work.
[Captivate Android Development] Rrryan2:
Um. Glad that it helped, but ... um... who? :)
[Captivate Android Development] JRd1st:
Question: in the instructions you say to set "Server: supl.google.com, Server Port: 7276" but in your secgps.conf you have SUPL_PORT=7275?
[Captivate Android Development] Rrryan2:
7276 is what I've had best results with, but either should work. In truth, the Supl setting in secgps.conf is mostly superfluous anyway and doesn't make much of a difference.