yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] alphadog00:
I agree - i thought the vibrant files that were ported over did the trick - there was more there then config files. Also, I think it may have something to do with IO blocking - lag fix related that could be causing the issues.

As mentioned, the chip is used in other hardware without incident. Also, i don't see samsung rewriting a vendor provided driver and config files would have been fixed ages ago.

I guess we will just wait and see, but i do have faith that Samsung will sort this out.
[Captivate Android Development] Joe1981AL:
we'll have to see what happens, i do notice the CNR bouncing erratically even the same sat going from 37 to 13 then back to 35 in a matter of 2 seconds while the device hasn't moved at all. Whatever is causing the bouncing CNR could cause the bouncing location as well.
[Captivate Android Development] CLShortFuse:
Is there anyway we can get our hands on the Verizon Fascinate rom files?

I have a suspicion their GPS is better than ours.
[Captivate Android Development] NetCopAD:
Which files do you need?

Give me a list and I'll extract them for you.
[Captivate Android Development] hashish16:
I believe the cell tower information is creating a problem, i noticed while driving through the back roads in WV.

After establishing a lock, I would have 50-100m accuracy with a live data connection. Once I lost all cell signal, my accuracy went down to 10m and maintained that accuracy.

Thought it was a fluke at first, but got the same results on the journey back.
[Captivate Android Development] foxbat121:
One of the Broadcom employee (although not working on GPS chip) mentioned that it is some kind of noise issue and a driver is updated to solve this issue. I believe JH7 is simply too old of a version of contain such driver (first created at the end of August).
[Captivate Android Development] alphadog00:
GPS should work fine without any cell towers. There is aGPS which does use cell towers, but our phones should work fine without them.
[Captivate Android Development] tazman171:
I also noticed this, drove to my parents and nav had me next to the highway not on it. Lost cell reception and GPS was spot on always had me on the highway and in the correct lane, got reception again and poof, was driving 200 ft off the highway again. Confirmed this on the drive home.
[Captivate Android Development] Matrioux:
OK, so is there a way to turn aGPS off and test if maybe that's where the errors are coming from?
[Captivate Android Development] TheSopranos16:
In LbsTestMode, go to Application Settings and change Operation Mode from MS Based to Standalone. That turns AGPS off, but it will take longer to get an initial lock.

One thing you can do is leave AGPS on, do a Get Position Test until you get a lock. Let it run for a few seconds to get almanac data. Then make the switch to Standalone. You should still get a lock fairly quickly as long as you don't move much in between. Let us know how it works out, I'm at work and don't have time to test it myself at the moment.
[Captivate Android Development] foxbat121:
The interference could be from cellur radio rather than AGPS. You could turn on the flight mode to disable the cellur radio for testing but you will need to use some offline nav software for testing.
[Captivate Android Development] CLShortFuse:
It's interesting that you guys say that it works better without AGPS since that's actually how the Verizon Fascinate is made to work. They turn off AGPS, but that's via a special menu.

I don't think AGPS is disabled with LBSTestMode. I"m almost sure LBSTestMode is "fake".

Grab the v002 to make sure there is NO AGPS and disable it in android

adb shell

su

cd /dbdata/databases/com.android.providers.settings

sqlite3 settings.db

update secure set value="0" where name = "assisted_gps_enabled";

.quit

reboot

Delete GPS Data in LBSTestMode

/etc/jupiter.xml

/system/bin/gpsd/*
[Captivate Android Development] NetCopAD:
Here are the files from the I500USDI06 Fascinate ROM
[Captivate Android Development] lpsi2000:
Would any of these settings cause other applications that use network to find your location not work (e.g. Google search, weather app, etc...)?
[Captivate Android Development] CLShortFuse:
I'm really not sure. I don't think the cell tower information is completely blocked off by disabling AGPS.
[Captivate Android Development] CLShortFuse:
Sweet, thanks!

Jupiter.XML looks identical

Driver is different (then again, our driver had references to ATT TEST)

Supposedly it works fine for Verizon and the only difference is CDMA for AGPS instead of GSM AGPS. Maybe it's the driver, maybe it's AGPS. Let's start with testing AGPS off. Going on a road trip now...

Actually, you guys can test the AGPS with v002. I'll test this Verizon driver
[Captivate Android Development] NetCopAD:
Something weird though... I mounted a Captivate ROM's factory.fs and I can't find glgps_samsungJupiter inside. Only agpsd in /bin.

Also I wonder what about libsecgps.so and libclientgps.so?
[Captivate Android Development] CLShortFuse:
Can you compile a directory list?

Btw, Verizon driver doesn't work on our GSM devices. I guess there are CDMA specifics. boo

Edit: Oh dear... GPS doesn't turn on.
[Captivate Android Development] Unhelpful:
Captivate? I've only seen agpsd in Vibrant dumps before, and it didn't seem to work on Captivate, even with the Vibrant gps libraries.
[Captivate Android Development] jason531:
Thank you for this thread, CL, especially the "re-education" part. I had read about some of those concepts in various sources, but your summary is very readable, concise, and informative.

I concur with the theory that AGPS is a major cause of the problem. Mine only works acceptably in standalone mode. I also have seen the "driver reset" issue where I cannot get a lock, disable/enable the GPS, then get a lock within 5-10 seconds.

Please let me know if there is anything I can do to help, since the best Captivate support comes from XDA, not AT&T/Samsung. I have a Captivate running Cognition 2.1 (JH7) and also have access to my wife's Droid 2 (Froyo). Thanks again for working on this issue.

Edit: I mention the Droid 2 for comparative testing. Last night I was walking around running My Tracks simultaneously on both phones to see if both of the little blue circles included my known position.
[Captivate Android Development] Asraiil:
Ha! and here I thought I was the only one using my wife's phone (HTC Aria) for comparison testing! The price for using her phone is steep, as she keeps on poking me and asking why I have to use her phone if mine's so much better...
[Captivate Android Development] NetCopAD:
Wow! My bad! It's a Vibrant ROM. I've messed up with all this ROMs around LOL!

Guess I'll have to take a look again tomorrow after sleep :o
[Captivate Android Development] sblees:
Lol... I have to keep my wife in the dark about my gps issues or else she will give me hell about why didn't I get the iphone.
[Captivate Android Development] tazman171:
It seems to be more than just AGPS, will try with flight mode. Problem is, can't use google nav in that mode.

Sent from my Captivate/Voodoo 1.6 Ext 4
[Captivate Android Development] phr00t:
Has anyone tried using the Blackberry's FrqPlan from the first post:

FrqPlan="FRQ_PLAN_26MHZ_2PPM_10MHZ_100PPB"

?

I've been doing some very small testing with it, but not enough to make any conclusions. I will test it on my way home (using Jupiter v002 and the above FrqPlan).
[Captivate Android Development] no driver:
You could always load up your route in Navigate and then turn on flight mode. I did this a while back and after Navigate loaded up the map the GPS showed where I was even though I wasn't following the route Navigate had picked out for me. I'm not sure if it would load enough map data for a long drive but for my 25-30 minute commute home it had enough of the surrounding area to be usable without additional data past the initial loading of the map.
[Captivate Android Development] whorider:
Does AT&T's own nav app work on this phone?
[Captivate Android Development] foxbat121:
It can't perform miracles. If you GPS doesn't work well, the AT&T TeleNav will be affected as well.
[Captivate Android Development] tmusall:
Or you can use MapDroyd from the market. It caches all maps offline then positions you using gps only. Should be good to use when testing in airplane mode.
[Captivate Android Development] whorider:
I was just curious, b/c AT&T sells that service for $9.99 a month. One might think that AT&T would be pushing sammie for a fix as well.
[Captivate Android Development] Unhelpful:
Would somebody who would pay monthly for an inferior service even notice that the GPS doesn't work too well? I've used telenav on i617, and its flaws are many, but most annoying is the fixed distance at which it instructs you to turn. Often it does so 1-3 streets before the correct turn. :(
[Captivate Android Development] MrBuddyCasino:
This looks very much like a confirmation of the low-quality almanac data theory. This forum does not allow me to post an URL (le sigh), just google for "demystifying-gps-issues-samsung-galaxy-s-2.html", its the first result.

I use "GPS Status" to populate my almanac and ever since I did that (every few days), I get a fix in ~15 seconds and good static accuracy. Not sure I it helps with tracking accuracy (when moving), though.
[Captivate Android Development] Joe1981AL:
CL, I know we are working on tracking issues here but on the quick fix topic try this and see if you see good results like I do.

edit your jupiter.xml file changing this, ltoFileName="/data/gps/lto.dat"

download an LTO from http://gllto.glpals.com/7day/latest/lto.dat

and place in /data/gps

I updated my jupiter.xml as above, loaded the lto.dat to location, went into lbstestmode and deleted gps data, turned on airplane mode and restarted the phone.

I started up GPS Test after reboot and had a solid lock of 10 sats in 45 seconds.

edit: If this does work, an app could be wrote to do the same thing quickGPS did on WM
[Captivate Android Development] CLShortFuse:
I just got back from using v002 all day and it doesn't help with accuracy at all. AGPS isn't the problem. I've realized if you turn off the GPS and start it up again, you'll get a VERY accurate position. Something in the cache isn't right. We can force certain parts of the cache not to be used by these settings

ignore_osc="true"

ignore_rom_alm="true"

ignore_nav="true"

ignore_pos="true"

ignore_ram_alm="true"

ignore_time="true"

Which one(s) should we disable to test v003?
[Captivate Android Development] Asraiil:
Ok, a couple of things:

First, I updated to Jupiter.002, went for a run, and my track was pretty accurate, it even got when I crossed to the other side of the road. (Thanks forum for not letting me put up pictures...

w w w dot flickr.com/photos/20983849@N05/5031592190/

This area is pretty densely wooded, except for right where I began the track.

For a comparison, here's the beginning of my track from Work to Home, where it was way off even while sitting in a parking lot:

w w w dot flickr.com/photos/20983849@N05/5031592218/

Now to my second thing:

I went to turn off the AGPS via the ADB shell commands:

adb shell
su
cd /dbdata/databases/com.android.providers.settings
sqlite3 settings.db
update secure set value="0" where name = "assisted_gps_enabled";
.quit
reboot

when I get to the sqlite3 settings.db command, I get the following error:

sqlite3: not found

I've tried various permutations of the command, and haven't been able to get it to come up at all. Any ideas?
[Captivate Android Development] CLShortFuse:
At this point, it's not worth it. Stick with v001
[Captivate Android Development] foxbat121:
I tried turn on flight mode and the navigation accuracy didn't improve at all. So, at this moment I would say the driver in JH7 is still hosed. Samsung probably will take its sweet time to roll up any future GPS fix into Froyo update which we probably won't get until Nov at the earliest (Given that Europe will get it at the end of Oct.).
[Captivate Android Development] Asraiil:
Ok,

Well I figured out how to use sqlite3 via the shell. I had to pull the settings.db, I hadn't actually pulled it before. I've got .002 in right now, and I've made the changes for disabling agps, but when I go to chown the file once it's back in it's place, I can't seem to do it and I get this error:

chown: unknown user/group system:system

I did an ls -l to see the properties, and this is what I came up with:

# ls -l /dbdata/databases/com.android.providers.settings/settings.db
ls -l /dbdata/databases/com.android.providers.settings/settings.db
-rw-rw---- 1 0 0 50176 Sep 28 2010 ←[0;0m/dbdata/databases/com.android.providers.settings/settings.db←[0m

anyone know how I can fix that? I'm running mostly stock, just using the voodoo fix kernel.
[Captivate Android Development] orlandoxpolice:
no change in GPS performance for me. I think i may have botched something when i restored with titanium backup and restored system data with it.
[Captivate Android Development] istitch:
My GPS tracks properly for the first time ever...!!

Kudos to CL. You did what no one could do!

All other fixes I tried till now only worked with getting a faster fix but did nothing to fix the tracking issue. Thanks to your fix, my GPS tracks properly for the first time ever...!!

PS: I am using Cognition 2.1.4 with your Jupiter.xml V001.
[Captivate Android Development] tazman171:
Oh yeah, Quick GPS. Forgot about my tilt hitting that every 6 days. GPS always worked well on it, hell, it still does.
[Captivate Android Development] askpcguy:
If you pull the settings.db file and edit it, when you copy it back you have to change the permissions and ownership of the file.

adb shell
su
chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
chown system.system /dbdata/databases/com.android.providers.settings/settings.db

Taken from http://samsungcaptivate.wikia.com/wiki/How_to_Sideload
[Captivate Android Development] nammyczc:
ok dont shoot me, but are you guys just manually replacing the jupiter.xml?
[Captivate Android Development] drancid:
yup. U have to replace original jupiter.xml file. And i disabled the AGPS either. After all, i got locked really quick like in 10secs..(little longer in my room tho.. but less then 20 secs) Great work!! Imma test tracking with my navigon tom.
[Captivate Android Development] phr00t:
I have been using Jupiter v002, but I replaced the "FrqPlan" with "FRQ_PLAN_26MHZ_2PPM_10MHZ_100PPB".

Seeing satellites and average lock times have improved over JH7 OTA with this setup. It now seems to get a lock in a reliable amount of time, which is nice. I've tested this over about 3 days with 5-6 30 minute My Tracks.

However, accuracy is still lacking. When the track begins to wander, I switch back to GPS Test and see the number of locked satellites are few (3-4) and the signal strength is jumping wildly. I'm beginning to worry that this is just a reception problem at this point... I'm curious to try other FrqPlans, but I don't know which ones to try... it'd just be trial and error :-\
[Captivate Android Development] max_warheads:
In this case I would actually suggest he try 1000.1000, as this has been seen occuring with system.system, but 1000.1000 has worked in previously samfirmware-released JH*
[Captivate Android Development] compuguy1088:
Your talking about this thread on Android forums: http://androidforums.com/captivate-...demystifying-gps-issues-samsung-galaxy-s.html
[Captivate Android Development] BigPrince:
Running Cognition 2.1.4 and eplaced the jupiter.xml with the v001 file. My GPS has been absolute crap since I first got the phone and unfortunately it's still the same. Turned agps off as well with no change. If it does find my position on google maps it's usually at least 300-400m off target. I'm going to give the phone another week and if Samsung doesnt provide a fix or someone else I'm going to punt it and go to Verizon.
[Captivate Android Development] foxbat121:
If Samsung has another fix in a week or two, it should be leaked already. Remember JH7 was leaked in early Sept. with a build date of 8/27 (IIRC).
[Captivate Android Development] exparrot:
Thanks for the highly detailed work on this.

I've replaced the jupiter.xml, and my compass now appears to be reversed, or out-of-whack. I've tried to calibrate, but no change.

Is there a way of purging/clearing compass data to recalibrate cleanly?

(I've searched before asking and didn't see any posts on this topic)

Thanks gang!
[Captivate Android Development] CLShortFuse:
Well, my compass has never worked for me, so I can't even begin to test it.
[Captivate Android Development] ScratchSF:
@CLShortFuse, I like the approach you've taken in trying to troubleshoot and solve Samsung's GPS problem. I'm a T-Mobile Vibrant user (yes, I know this is a ATT Captivate group). :-)

Anyway, my GPS was horrible. It would only work when it decided to work. In many cases, I would only lock two of the weakest satellites, even though many more were visible. Also troubling was that the date/time information was completely inaccurate when I would use the GPS Test application (downloaded from the Marketplace).

Last week, I decided to apply a patch that's been circulating in the Vibrant forum: xdaforums.com/showthread.php?t=782242 . After applying this patch, my GPS now locks within seconds. And, more interestingly, the GPS Test app now reports the correct date / time information. So, I speculate that the fix contains more than just configuration changes.

I understand that the patch contains the GPS "fix" from a leaked, forthcoming, Vibrant ROM update. But I don't have any specific details. I would speculate that some in the Vibrant app dev forum might have more information.

Anyway, if you're not aware of this patch or some of the work in the Vibrant gorup, I thought I'd make you aware - if only for cross-pollination and information sharing. Perhaps there's something useful in that file you can leverage, or visa-versa.
[Captivate Android Development] myx0mop:
What doesn't make any sense to is the fact that my GPS has actually worked from day one, without any issues. It's reliable. If the problem is with the driver, or chip firmware, or the device itself... what gives?
[Captivate Android Development] foxbat121:
Read post#16 in this thread.
[Captivate Android Development] DemonWav:
The OTA JH7 had many different checksums compared to the leaked JH7, so I'm not sure why you would say that.
[Captivate Android Development] foxbat121:
So far I see no evidence to indicate that OTA and leaked JH7 are different builds. OTA is obviously packaged to contain only the difference bits between JH7 and JF6 images in order to save download size. Samsung may tweak something in order to make this as small as possible. That explains why even the removal of bloatware will cause OTA update fail. But, there is no evidence to indicate that anything significant has changed.
[Captivate Android Development] CLShortFuse:
Are there any other GSM phones that uses a broadcom GPS chip?
[Captivate Android Development] adityaksharma:
lol same with my girlfriend, she's giving me hell right now about not getting an iphone lol
[Captivate Android Development] ThisWasATriumph:
The iPhone 3GS and 4 use a 4750 but i dont think that would be helpful :rolleyes:
[Captivate Android Development] drancid:
try this settings guys

i've tried a lot of lbstestmode settings but this is the best settings i found.

i wanna share my lbstestmode.

just try this..

if u dun like this, just go back.. lol

i replaced jupiter.xml (ver.2) file and disabled AGPS.

here's my lbstestmode settings..

Application Settings

Session Type : Tracking

Test Mode : S/W Test

Operation Mode : MS Based

Start Mode : Hot Start

GPS Plus : ON

Dynamic Accuracy : ON

Accuracy : 50

Use SkyHook : OFF

Use PC Tool : OFF

SUPL/CP Settings

Server FQDN Type : Custom Config

Server : supl.google.com

Server Port : 7276

SUPL Secure Socket : OFF

AGPS Mode : Control Plane

and i Deleted GPS Data --> Reboot --> Go Outside --> LbsTestMode -->

Get Position Test (wait till u get at least 8 Sats Locked)

done..
[Captivate Android Development] Zeimus:
CLShortFuse, do you facepalm when someone tells you clouds act like a wall against gps?
[Captivate Android Development] max_warheads:
Unfortunately, thee statements appear contradictory
[Captivate Android Development] CLShortFuse:
v003 is up.

But i just found out we DO have the source code to the gps. Samsung did release it.

Where can I get the source code (and specifically mach-jupiter-gps.c)

Edit: Found it

Edit2: Worthless. I think we need the glgps source
[Captivate Android Development] Matrioux:
In the change notes you state that you are using supl.google.com 7576. Do you mean 7276? In looking at the jupiter.xml it appears to be set at 7276 which I think is correct for supl.google.com
[Captivate Android Development] docflower:
v3 not working as well as v1

I have updated the jupiter file from V1 to V3 and am getting much worse GPS test data. From 6 second fix to 93 second fix over 5 tests. Im going to switch back. Does anyone have the Vibrant file so I could try that fix?

Cheers.
[Captivate Android Development] socca1324:
I put the jupiter.xml into /etc/ and then i rebooted but when i go into lbstestmode the settings dont reflect whats in the jupiter.xml... i am confused.
[Captivate Android Development] ulbonado:
The OTA JH7 has a kernel build date of Sep 11. The leaked JH7 was available prior to that date. That strongly suggests that they are not the same.
[Captivate Android Development] hashish16:
I want to confirm that this patch works on our phones and its wonderful. I went from 4-6 satellites with 50-100m accuracy to 10 satellites with 16-30m accuracy. Once locked I never lost a lock even when I moved the phone from the dash to my cup holder. I dub thee the holy grail of Captivate navigation.

BTW I am running JM5 with captivate kernel.

Thank you Vibrant nerds and ScratchSF for the post :)
[Captivate Android Development] foxbat121:
They tweaked some system file permissions to disable the easy SIM unlock app out there. So, it might cause the newer date. But since it still uses the same build number, it inidicates there is no source code change that requires a new build number. Big companies like Samsung typically does not re-use software build numbers for the sake of tracking and support.
[Captivate Android Development] bblaze1874:
V3 is working great for me so far I can get 9-11 sat locks in about 15 seconds...which i have had before but never consistent. The biggest improvement is the strength of the individual locks in GPS test. Keep up the great work!!
[Captivate Android Development] CLShortFuse:
I got some files from a leaked i9000 GPS. I'm going to post them in a few. Supposedly they work. the Jupiter.XML is different so I'm posting a v004 soon
[Captivate Android Development] docflower:
thanks shortfuse for your efforts!!
[Captivate Android Development] norrgrd:
Interesting following this thread with my files :)
[Captivate Android Development] docflower:
says invalid attachment
[Captivate Android Development] CLShortFuse:
Yeah, I don't get why.

Get it here

I'm pulling it since it gave me BSOD (boot screen of death)
[Captivate Android Development] docflower:
flashing via Clockwork and stuck on installing update...
[Captivate Android Development] CLShortFuse:
it's not an update...
[Captivate Android Development] docflower:
so you dont flash via clockwork? how do you install a firmware change then? obv noob. sorry.
[Captivate Android Development] CLShortFuse:
don't. since it crashed my phone...
[Captivate Android Development] nephets0:
okay how do i know if the file got copied where it should?

i'm kind of new at the whole terminal thing.

i used terminal emulator to go

su

cp /sdcard/jupiter.xml /etc/jupiter.xm

exit

got no message that anything had been done etc?
[Captivate Android Development] drancid:
Check the file size with rootexplorer
[Captivate Android Development] CLShortFuse:
I uploaded v005. Maybe I'll do an update zip for v006
[Captivate Android Development] drancid:
so.. i have to enable the AGPS again since v3 updated right?