yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Liv33viL:
Mixed Signals... Perhaps

Hey there Dalewest,

I'd like to make a suggestion...

First verify Modem and Kernel marriage is the best match for your device (just sayin'...)

Follow each step in order.

*Note there is a difference in result when either "Rebooting" or Powering Down" the device...

* Verify that all your settings are as they were in LBSTestMode, Prior to Flashing the PB 1.0 fix.

* Verify that, in fact, the NTP server for your region is correct.

* Wipe the GPS Cache and Data also any GPS related applications you may use (ie: Maps, Navigator, GPS Test Plus, Google Sky, etc...) is wiped of their caches as well. - If you have locations / directions stored in maps, or specifics in other navigational applications, back up you settings data files first, then clear the data and cache in these applications as well. Make sure to get them all cleared in the one session.

*Once data and cache is cleared - Do Not attempt to run any applications or even tap the back button... perform a complete shutdown device from the power button.

* Power up the device after about 30 seconds - enter recovery mode and clear the Dalvik Cache from the device / reboot...(will take a little longer on this boot) After powering up, open LBSTestMode settings once again (Information should still be in the OP). Ensure ALL the information throughout is correct. Power the device down once more after the last setting has been entered into LBSTM.

* After 30 seconds or so power up the device and re-flash the PB v1.0 fix again and ensure the permissions on those files that are being flashed are correct after the flash has completed. Now go into LBSTM and verify the settings you had previously entered are still indeed there and correct. If not - re-enter the correct information. - Reboot the device.

*Now with WiFi enabled GPS Loc Svs and in Pedestrian (sensory) Mode get your device an assisted data push with Maps or whatever apps you use to acquire locational data. Be sure to be in an outdoors open area with a know good reception channel. - Once you have forced a data push - just warm boot the device one last time and let it load up - and media scan...

Set WiFi enabled, GPS on and Sensory Mode on as well.

Now - calibrate the devices' compass settings in Maps and let new data (if any) push to the device. Perhaphs go for a short walk...

In the GPS Status & Toolbox - go into the main screen then go into setting (lower left touch sense button) and enable Radar mode for a brief period.

Go back into the GPS S&T and let run for 15 minuted or so.

Now go and match your data readings in GPS Test against GPS S&T - they should be almost dead balls on... if there is a slight variance between the two applications (one bird or so, TTL or Time To Lock, and the SNR) this is alright because there is a slight difference on how exactly each application pulls and displays the data.

HtH

Good Luck

Post back with your results (after the process)

Peace-

Liv33viL
[Captivate Android Development] BumRush:
Will I see a difference in performance if I use the Canada version compared to the North America or global one? I live in Canada but i do travel quite a bit.
[Captivate Android Development] askpcguy:
Thought I saw a post by Rrryan which says GPS includes Network Time Protocol which calculates the time offset from the device. Or uses the carrier time difference such as Att time.

In this way the ntp server settings are almost pointless.
[Captivate Android Development] Rrryan2:
Not quite. GPS computes the device location by determining how long it takes for the signals to arrive from the various satellites. To do this, it needs an accurate time source for comparison, and to speed the initial acquisition AGPS-enabled devices first synchronize over the internet with an NTP time server.

I think you're thinking of an earlier post where I remarked that synchronizing the phone's main system clock with NTP is unnecessary since the chip handles its own time. The main system clock can be off by several minutes and GPS will still work fine.
[Captivate Android Development] Rrryan2:
You're probably best off using the North America one. The North America pool is about 90% US-based servers anyway and is probably sufficient even within Canada. It's mainly only the big intercontinental hops that can really slow things down.

If you really want deliberate control, use the Faster Fix app from the market. It allows you to manually configure the NTP settings as necessary.
[Captivate Android Development] Rrryan2:
Assuming you've got unobstructed view of the sky, my guess here would be interference, either from within the handset or else from a nearby source. WiFi, microwave ovens, baby monitors, cordless phones etc. are near enough in the spectrum to cause interference.

You might try disabling WiFi. I'm starting to rethink my advice in the OP that recommends leaving WiFi on as in some forums it's believed that the WiFi radio may be causing interference with the GPS and/or exacerbating potential power starvation problems.

You can use another app like GPS Test (from the Market) to display the numerical SNRs to help quantify things more specifically if you're trying to figure out what's going on. I prefer GPS Status most of the time because it has better features for AGPS management, but GPS Test gives numerical values for the SNR instead of just the itty bitty bars.
[Captivate Android Development] Rrryan2:
No such animal as #42, so I don't know what that might have been about.

ftp://tycho.usno.navy.mil/pub/gps/gpstd.txt

Interference and/or power management within the phone are widely speculated to contribute to our GPS woes. However, this fix doesn't actually do much to actually address either of those, so if installing the fix helps then interference isn't the only problem...
[Captivate Android Development] crazililazn:
Using Serendipity 6.2 on my phone with Plumbob v1.0 has produced terrible results. Stationary locks are ok but tracking is terrible. The accuracy is just completely off, sometimes it can be as off as half a mile. This is with all recommended settings in the lbstestmode.

Would really love some help to get my GPS working :/

Sent from.... Waiting for location
[Captivate Android Development] Rrryan2:
See http://xdaforums.com/showpost.php?p=12130596&postcount=417

Though it seems to work great for some, Serendipity 6.0+ doesn't seem to want play well with this fix in all cases. Don't know what the issue is, but Mikey had written that they had changed something out on the GPS files.

I'm guessing that AT&T held up the KB1 release so long that the drivers used in it are actually somewhat outdated relative to the latest and greatest I9000 JS7, JS8 etc. and may not be 100% compatible.

I've finally had some success using files adapted from the JV1 I9000 Gingerbread leak so I'm working on a new test version that I hope to publish today. Maybe that will work better.
[Captivate Android Development] crazililazn:
Ahh ic :) then im looking forward to trying the new release and see if it works :)

Sent from.... Waiting for location
[Captivate Android Development] mbc663:
Thanks for your help. I appreciate you putting something together for me. It seems like I'm back in business. Getting quick locks and accurate logging, only difference is I'm not locking into or seeing as many sats but its a world of a difference. Thanks again.
[Captivate Android Development] mbc663:
Damn! Until I reboot :/ wtf
[Captivate Android Development] CuriousTech:
Does anyone want to try testing with airplane mode on vs. off? I'm not sure if it was just me but signals appeared to be less jumpy without all the extra noise. It was a little more like when I was running Perception/Firebird2/KP1.
[Captivate Android Development] D12AKO:
Thanks PlumbBob

Just wanted to let yah know that this GPS Fix still works like a charm. Fixed my GPS as I expected when I installed Cognition v4.2.2 SHO.

Can't thank you enough for the great work PumbBob.

LMAO... I had too :D

Thanks again Rrrayan2
[Captivate Android Development] ckelvin87:
Hi, I flashed this on cog 3.03 with firebird and jk4 modem and it worked fantastic. I got locks within 5 seconds as long as I had clear view of the skies.

But just now I've upgraded to cog 4.1 with a kb1 modem/kernel. And the results with the fix aren't great. I haven't been able to get a lock at all, and can't even get more than 4 satellites in view.

Would this problem be due to the kb1 modem compared to the jk4/i9000 modem/kernel I had before?
[Captivate Android Development] D12AKO:
I'm on KB1 modem and this fix works just fine... always has. When you went back to Cognition 4.1.1 did you do so with fresh install or at the very least Clear Data/Cache and Dalvik on CWM?
[Captivate Android Development] ckelvin87:
I flashed 4.2.2

But before doing so I flashed back to stock, then master cleared, then flashed cog and wiped dalvik cache before I booted. Should I have chosen wipe data in the clockworkmod too? Master clearing the same as that right?
[Captivate Android Development] RepublicanDaddy:
WOW! This is GREAT! I'm running Cognition 4.1.1. I was having no luck with any tracking upon moving with my gps. After installing Plumbob fix, it works FLAWLESSLY! Even used it on a long road trip last eeeeek and never lost a track the entire time! Thank you sooooo much! With the combination of Cog 4 and your gps fix I am finally enjoying my cappy!
[Captivate Android Development] crazililazn:
Hmm weird. Supl mode wasn't working for me, but once I enabled control plane my gps is working flawlessly :)

However. For some reason my google navigation never works, but my dedicated gps software works perfectly with control plane.enabled :)

Sent from.... Waiting for location
[Captivate Android Development] reinbeau:
I have never felt it was a hardware problem other than weak signal. The GPS works, but the software that supports it is horrible. It's so obvious, after having had a Garmin iQue 3600 and learning about how important the handling of the data is for good GPS functionality. Samsung has no clue it seems of how to handle the GPS signals.
[Captivate Android Development] olo567:
I tested this extensively on vacation last week, with interesting results. I got a great lock when still. When I was driving in the car, locked pretty quickly, but every once in a while it would lose accuracy for a few seconds and then come back in Navigation. I decided to look at the number of satellites it was locking onto and it was about 8 or 9. Just for kicks, I took off the skin/case I was using and suddenly I was consistently locked onto 12. Doesn't seem like a big difference, but I didn't lose accuracy at all the rest of the way. Skin back on, same issues as before.

Can't guarantee this would help anyone else, but at least for me I found that the skin does hurt the GPS signal reception when moving.
[Captivate Android Development] D12AKO:
I've also noticed this with Tinted cars.

For example... on my Jeep that has factory tints from back row on I get really good GPS locks but on my whip... G35 Coupe with Tints all around... yes even Windshield....LOL 35% Windshield and the rest is 20%...Hehehe I get not so good GPS. Still good enough but get same issue you did with skin on.
[Captivate Android Development] CuriousTech:
Tint is semi-metalic so it's going to block the signal. Some windshields can have metal as well such as those with a HUD. I'm not going to comment on tinting one, but it sure makes a great faraday cage. ;) Silicone or rubber skins shouldn't cause a problem unless they have a metalic based finish which would be dumb to use on a cell phone skin. I'd try a different brand.
[Captivate Android Development] CuriousTech:
I've noticed similar performance but not as bad. It was definitely better with firebird (or I9000). I tried ZNKP1 (I9000) with CogKernel and voice calls were broken so flashed back, but GPS was better so some of it's in the modem.

If I could rate quality from 1 to 10 it might be like this...

Firebird = 4

Firebird with PlumbBob = 8

Cognition = 1

Cognition with PlumbBob = 5

It works, but not nearly as well in comparison.
[Captivate Android Development] ckelvin87:
I agree, In my car with tints all over I can't even get to see 1 satellite in view, but in my car without tints i got locks within 10 seconds without any problems
[Captivate Android Development] ckelvin87:
Yes I agree. Firebird with plumbbob was excellent, works so much better than I could've ever imagined. Cogkernel with plumbbob still works but pales in comparison to the firebird plumbbob combo. Having experiencing this actually makes me want to flash the firebird kernel again :D
[Captivate Android Development] mbc663:
I've tried every fix out there to get my google navigation from getting stuck on this "checking navigation availability". maps find me perfectly. Other gps programs work fine. I'm on a captivate and my girls inspire is doing the same thing OUT OF THE BOX. Whats the deal with google?
[Captivate Android Development] D12AKO:
Maybe Google don't like your area...LOL

Have you done a fresh install... going back to Eclair and then to the ROM you want with PlumbBob Fix?

Sometimes, after too many GPS fixes and Kernel/ROM changes... it's good to start from Eclair with factory restore.
[Captivate Android Development] crazililazn:
Try reinstalling Maps from the market. That should fix it.
[Captivate Android Development] mbc663:
I've tried uninstalling many times. Its not rom related. Its doing the same thing on a day old inspire with no root.
[Captivate Android Development] olo567:
Metallic or not, it does insulate the phone from some signals, and as strong a signal as the Captivate needs with its crappy GPS antenna this behavior isn't that surprising.
[Captivate Android Development] reinbeau:
Which is precisely why I wish I could hook up my rooftop antenna to it - no blocking of any signals that way.
[Captivate Android Development] Liv33viL:
GMaps

Try this...

First - don't know if you've applied any GPS fixes, PB's or otherwise. Not stated, assuming that you don't.

First, back up the GMaps application and its respective odex file. Then uninstall the application completely.

Once uninstalled, reboot into recovery and perform a dalvik cache wipe - the reboot the device.

Wait the time it takes then go to the A.M. and download the latest version of GMaps and an application called FasterFix, install both, then apply the FasterFix setting.

Verify your LBSTestMode settings for region and satellite locations.

When GPS is enabled, try also enabling sensory aiding and WiFi on a strong connection.

Open maps and see if the issue persists.

HtH

Peace=
[Captivate Android Development] mbc663:
As wierd as it sounds out started working in the car this morning first time I tried it, and works perfect now. I'll have to see what the inspire is doing when she gets home. Thanks for the response liv33vil
[Captivate Android Development] Rrryan2:
The leaked KV1 Gingerbread for I9000 has a seperate configuration for an external antenna mode. Since SGS only has USB I'm not sure how they would connect it though. USB might work I guess (maybe through a new car dock?) or maybe through Bluetooth.
[Captivate Android Development] acdbx:
works great for me on cm7
[Captivate Android Development] Rrryan2:
That's really interesting because I really had no idea what it might do on CM7.

How was it before?
[Captivate Android Development] acdbx:
stock cm7 tracking was horrible. cm7 w/ this fix is great in the 30 min i've used it.

romkitchen js5 was decent out of the box, improved w/ this fix.

i haven't found out how to get to lbstestmode on cm7, but something's working.
[Captivate Android Development] Liv33viL:
GPS Config File for LBSTestMode

There's a file named "secgps.config" located in the /data/gps directory.

You can verify and/or modify your configuration data there.

Peace-
[Captivate Android Development] Liv33viL:
Ghost in the Machine...

Excellent!

Glad it's working for you.

Peace-
[Captivate Android Development] Ikonomi:
So I think that I've found a setup that actually provides functional GPS. I'm running PlumbBob 1.0 with control plane enabled and the combination of firmware in my sig. The key seems to be the JQ1 modem.

My GPS has been nonfunctional with each and every fix I've tried, including Da_G's and PlumbBob, but the combination of JQ1 and control plane seems to give good results. I just took a drive and stayed at 8-10 satellites in use with 5-10 meter accuracy, except when turning. During turns the accuracy will usually drop to 30 meters. I have yet to see how this will play in Google Navigation.

I did have one instance of all satellites being dropped while driving in a straight line. They remained in view, but the phone lost all connection to them. This happens repeatedly for me with the KP1 and JPG modems, so I'm interested to see if JQ1 will mostly fix the issue. The connections recovered relatively quickly, but more testing will be needed to see if the problem will persist with this setup. This behavior is definitely a deal-breaker for a "functional" GPS, so I have my fingers crossed.

The GPS isn't great by any stretch, but it looks like it will be usable in an emergency. For all other times I have my GlobalSat receiver. I'd encourage anyone with a 1006 Captivate like mine (with probably the worst GPS out there) to give JQ1 and control plane enabled a shot.

Perception 10.2 | SpeedMod K13D | I9000XXJQ1
[Captivate Android Development] akuru:
Please forgive my ignorance, with "control plane" do you mean changing the AGPS mode from "SUPL" to "control plane" under;

SGS Tools -> Secret Codes -> GPS Test and settings (LBSTestMode) -> SUPL/CP Settings -> AGPS

?

Also, are you using PlumbBob fix as well or just changed this setting without it. I'm using JQ1 and would like to give it a try. I'd appreciate if you can share your settings.
[Captivate Android Development] clueless captivate:
how do you make changes??
[Captivate Android Development] Liv33viL:
Edit The Config

Just as you would edit any type of text file.

Assuming you have root access to your device and a directory navigator (ie: Root Explorer) you will navigate to the directory, as stated, open the file, as stated, and modify the configuration according to what Rrryan2 has recommended in the OP and throughout this thread.

If you haven't done so already, I'd suggest reading the entire OP plus much of this thread before making any changes. It may just not work well with your device. That's left to be seen, but be sure to back up that config file and write down any settings that you might modify going forward.

If you need to revert to your original settings, then you have them handy.

Good luck.

Peace-
[Captivate Android Development] Liv33viL:
Additional Note

Additionally if you have Captivate SGSTools you can search the menu in secret codes until you find LBSTestMode.

Open LBSTM and you can make the same modifications to your config strings.

You can find the SGS Toolbox in the Android Market.

HtH

Peace-
[Captivate Android Development] wgarrido:
Fasterfix doesn't do anything except set the same ntp server i aleady had. Sgs tools can set ntp as well.
[Captivate Android Development] Liv33viL:
Yes, that is true.
[Captivate Android Development] Ikonomi:
Yep, changing the AGPS mode to control plane in LbsTest and then activating control plane as detailed in the second post via the *#1575# menu. I am indeed using PlumbBob.

However, as Rryan2 mentioned in that post, results don't seem to be entirely consistent with control plane. In my testing yesterday (long drive through the city), performance seemed to depend on the tower I was connected to. Strange stuff. But even with the variable performance, I am getting better results than with PlumbBob with just SUPL.

Perception 10.2 | SpeedMod K13D | I9000ZSJPG
[Captivate Android Development] Miami_Son:
Forgive me if this has been answered, but the thread is just too long. There is a USA and Canada version of the fix on the download page. What is the N. American version for? I'm in CA, so which one should I use?:confused:
[Captivate Android Development] Liv33viL:
Which File To Use...

Hey there Miami_Son

The only difference that I can see between the files (There may be additions, but it hasn't caught my eye as of yet) is the settings of the NTP server.

For example: Each region uses variant of the NTP Server Addresses (as shown below)

North American Region of the USA ...

North America - north-america.pool.ntp.org

Within the USA... USA - 0.us.pool.ntp.org

A World Traveler Perhaps... Global - pool.ntp.org

You may want to begin with using the USA CWM file first.

Then, perhaps, you may want to experiment with the North America NTP sever settings, depending on where in California you are located - extreme Northern Cali like by Washington State or bordering on Mexico.

You can always reconfigure your settings back to what worked best for you if the result is not as anticipated.

HtH

Peace-
[Captivate Android Development] Miami_Son:
Thanks for that. Pretty confusing if you ask me. Having separate files for Canada and USA makes sense since they have different carriers, but North America is typically understood to be the U.S. and Canada combined, so having that file in the mix is just confusing. I'll try the USA file first since I'm in SoCal.:cool:
[Captivate Android Development] Rrryan2:
Thread is long, but the search button works great.

The only difference is the setting for the NTP server. You might have slightly better times using the USA one, but the North America NTP pool is about 90% US-based servers anyway.
[Captivate Android Development] Rrryan2:
Don't know what to say. Sorry you got confused, but after nearly 500 posts in the thread, you're the first one who couldn't remember that California is in the USA.

There's lots more to North America than US and Canada.
[Captivate Android Development] Miami_Son:
Dude, no need to get defensive. You're right, N. America encompasses a large area, including USA and Canada. That's why it is confusing. Instead of giving me crap why not just put a sentence or 2 on the OP telling readers why they should use one over another? Don't blame me for being confused, blame yourself for not explaining it well enough. Damn, devs can be so touchy.:D
[Captivate Android Development] Rrryan2:
Nvm. Not worth it.
[Captivate Android Development] low99:
hey rrryan2, if you're still checking on the gps files on JS8 as stated at the OP, you might want to check out Continuum v4's Heathens GPS fix, worked great for me out of the box, just had to change the server using faster fix.

link to Continuum v4 - http://xdaforums.com/showthread.php?t=1006031

link to Heathens GPS fix - http://xdaforums.com/showthread.php?t=974702
[Captivate Android Development] wgarrido:
So this works on the captivate? Just flash s.GPS?
[Captivate Android Development] Rrryan2:
I'm working on a port as well of the JV1 files that's a little more agressive about incorporating the tweaks I've had success with so far as well. Real life has kept me too busy to get the kinks worked out, but I hope to be able to put out a test version this weekend.

I would advise Captivate users against installing the Heathens fix outright. As described in the OP the Vibrant handles GPS processing differently, and installing it completely wrecked GPS in one configuration I tried, giving the "2 seconds and quit" problem that finally required re-flashing.

Continuum doesn't fully implement the Heathens fix in my opinion; it includes the files but doesn't do the scripting necessary to actually use them so it's actually still falling back on the older methods. But again, with everything being closed source and so many variables affecting troubleshooting we're all more or less shooting in the dark.
[Captivate Android Development] low99:
My bad, I meant I flashed Continuum v4 and just changed the server using faster fix, I did not flash Heathens GPS fix.

And to rrryan, thanks for your GPS fix nevertheless, worked awesome for me when I was on cognition :D
[Captivate Android Development] CuriousTech:
LOL

1. Ping the servers using any of the free ping apps in the market.

2. Keep the server with the lowest ping time.

3. Profit
[Captivate Android Development] bigbooty:
Some peoples kids......