yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] malfuncion:
I have been following this since he posted the OP, been trying here and there skeptically. Sometimes the "fixes" worked, sometimes not. I have been lurking in the shadows since. Today I flashed to 2.2 Beta4 and just for grins wanted to try the GPS out on the way to lunch. Much to my dismay I couldnt get the thing to lock at all. So while at Buffalo Wild Wings, I downloaded the Jupiter v6 and installed it. On my way back I locked within 20 seconds and tracked perfect on the way home.

All I can say is GOOD JOB! Thank the lord for the people in this forum. The dedication and troubleshooting here is phenomenal, not only on this situation but all the Captivate bugs.
[Captivate Android Development] boomerod:
Keep us posted on subsequent GPS runs...if what I've read so far applies, it will stop working at some point.

Agree, xdadevelopers and the community are a Godsend. :D
[Captivate Android Development] pkley:
Ok, well while mine is certainly not perfect, it is working. After a couple days of use, Nav and My Tracks tracked me down a windy road with only a couple times losing signal, although it was a canyon. Nav still jumped to various roads from time to time.

Signal strength is still an issue, I have to hold it close to the window for it to work, I don't have a dash holder.

It works, but it's tenuous...

Also, losing cell signal is ok, but reacquiring signal tends to make it jump to the cell tower and then lag until it gets a fix again.
[Captivate Android Development] CLShortFuse:
Use ClockSync instead of Micro Second and make sure you disable auto sync in your Android Settings
[Captivate Android Development] drancid:
Local Offset never goes over ±0.4.

10 mins test.

refreshed every 10 secs.

cog 2.2 beta4 + OCLF + Jupiter v006
[Captivate Android Development] creepyncrawly:
Do you mean Settings | Date and Time | Automatic?
[Captivate Android Development] drancid:
yes he meant it :)
[Captivate Android Development] gordec:
CLShort, is there any reason updating v006? Right now I get locks pretty well with stock Froyo. The tracking can be all over the place at times. I am going try your clock sync tomorrow. What exactly does v006 do?
[Captivate Android Development] askpcguy:
Tried Micro Second on cog2.2 BETA with no updated Jupiter file and while I had problems after flashing to cog2.2, a few reboots and deleting GPS data in LBSTESTMODE solved that. Then again I did switch to the google supl server.

With Micro Second, I can say when stationary in the vehicle, the position seems stable. Doesn't jump around as I might have seen it do previously.
[Captivate Android Development] BodaciousDrake:
I'm looking at your MyTracks run in both satellite and map modes, and it looks almost perfect in both...much better than any results I've been getting (jh7 ota w/ no gps mods).

It looks like you're on to something here ShortFuse. Perhaps Samsung should consider bringing you onto the team - maybe something would get done in a reasonable amount of time. Keep up the good work! Thank you!
[Captivate Android Development] max_warheads:
OK, tried ClockSync, haven't enabled it to auto-sync for me yet, but

Avg after sync, for approximately 15 seconds, is 0.5s +/- 0.12s

If I let it go over the minute mark (longest it took to do this) avg > 2.2s difference
[Captivate Android Development] TheSopranos16:
I've installed v006 on top of Froyo JI6 and I must say, this is the best performence I've had so far. Still quite bad overall, but at least it can somewhat track me when moving. I have no idea what v006 changes, but I'm happy that it seems to do something helpful.

As far as using ClockSync or any other program, this really doesn't make sense to me. According to ClockSync's description, it "synchronizes device system clock with atomic time from Internet via NTP." So, its improving the accuracy of the system clock. However, there is no way that GPS is using the system time at all so I don't see how this can possibly help. I did some Googling and found this website: http://astro.unl.edu/naap/motion1/tc_finding.html

Because light travels extremely fast, the time difference between emission and reception of the GPS signals are of order nanoseconds. To maintain that level of accuracy requires atomic clocks. Each of the satellites has one. GPS receivers tend not to carry expensive atomic clocks. If a GPS receiver's internal time is a little off the three distances will still reduce to single point, but coordinates can still be wrong. However, if the distance to a fourth satellite is calculated, the distances won't intersect at a point unless the time is correct. Thus GPS receivers tend to need signals from four satellites – where the fourth signal serves to constantly readjust the receivers internal clock. If the time is correct (and the receiver is constantly readjusting its time) then the fourth satellite also allows altitude calculations.​

So, GPS signals need time that is accurate down to nanoseconds. There is no way that this type of accuracy can be achieved by syncing over the internet with a data connection that has a delay of hundreds of milliseconds. Also, the article explicitly says that GPS receivers internal time is corrected using information from the 4th satellite it locks on to.

Now, on the other hand, if we can try to investigate how well the internal GPS receiver is adjusting its internal clock based on data from the satellites, that might be more useful. Time might be part of the issue, but it would have to be the GPS receivers internal time, not android's system time.
[Captivate Android Development] KaLiBLeeK:
I installed this on Cog v2.2b4 yesterday, and couldn't get any kind of lock...

This morning, I turned off sensor aiding, and MyTracks was able to track my position almost exactly. Hopefully things don't regress over the next few days. Haha.

Sent from my Samsung Captivate (AT&T/XDA-App)
[Captivate Android Development] xetrev:
couldnt get a lock while moving earlier with 006 on froyo.
[Captivate Android Development] drancid:
I flashed cog 2.2 beta4 two days ago.

ran oclf and pushed jupiter v006 files.

I think cog 2.2 beta4 deletes gps data or something wrong with jupiter files with 2.2.

I got 10 sat locks just right after flashed and i could use navi well enough but after one reboot i couldn't get any sat on gps test app also my navi never located me at all.

So i ran gps position test via lbstestmode last night, got 8 sat locks in about 5 mins(took long...) navi worked again.

This mornig, got same problem..

Is this only my problem???

Tired of god D gps of this phone...
[Captivate Android Development] ajayendra:
OK guys, Please also let us know what settings are you using:

I am using: 2.2b4+lagfix+Jupiter 6

Supl Secure socket : off

AGPS Mode: Control Plane

Rest set to default and I am getting great tracking (still not the best)

I do have to restart phone sometimes. Also, if before startin Nav or map, I run the "Get Position Test" the lock is much faster.
[Captivate Android Development] drancid:
Have you tried after reboot??

My setting's same as urs but i put sulp server as supl.google.com / 7276
[Captivate Android Development] CLShortFuse:
I STRONGLY suggest somebody pull the GPS files from Vibrant JI6 and try them. I don't have the time right now but I've heard good things.
[Captivate Android Development] fraztto:
I tried cog 2.1.7 with v005 and 006 with no luck, it gets a lot of sats but doesn't get any fix at least before 5+ min. I think 006 is for froyo, it just doesnt look for sats.
[Captivate Android Development] CLShortFuse:
I tried to make an update.zip for VibrantJI6GPS files

I think you need 2.1 to run it but I'm not sure.

Anyway, here it is, completely UNTESTED (meaning, make sure you back up your stuff)

Doesn't work on Froyo
[Captivate Android Development] wilsongis:
Couple of questions:

I am not sure this is worth mentioning but I notice that many people are saying that they lose lock while moving. Could the issue have something to do with a conflict with the gyro or accelerometer?

Is it possible to look at the almanac the gps is downloading? Might be worth knowing if it is getting one.

Is there a way to look at the raw gps log? I realize that I can see things in logcat but I would like to look on the phone.
[Captivate Android Development] TechMizer:
Anybody try this, yet?
[Captivate Android Development] KaLiBLeeK:
I'm gonna try it out in a few; just installed Cognition v2.1.7, gonna setup a few things and try to install/test this. Heh.
[Captivate Android Development] Lee1733:
EDIT: Wrong topic, disregard.
[Captivate Android Development] tytdfn:
Lol I think your in the wrong thread

Yay no more fc
[Captivate Android Development] KaLiBLeeK:
Installation failed via stock recovery and Clockwork; granted I could've been doing something wrong, but I tried installing via zip with Clockwork, then renaming it to update.zip and installing with stock recovery and Clockwork, no dice on all 3 attempts.

This would be a long way of doing things, but couldn't I move the files around using RootExplorer?
[Captivate Android Development] CLShortFuse:
yes, you could
[Captivate Android Development] Lee1733:
I was indeed. Too many tabs open. Disregard. :)
[Captivate Android Development] joedoe:
In many places it's advised to add to the APN type the type"SUPL". However the Captivate doesn't allow to edit the APN type using the UI.

Any ideas?
[Captivate Android Development] zer0chance:
(sorry - apparently I am still, after some time, waiting for my account to be verified by a moderator so I can post outside links...)

The driver source does not do anything more than push raw chunks of data to/from the chipset. Apparently, the data is in "MEIF" format - a proprietary Nokia protocol. It doesn't seem the driver is particularly interesting or helpful in doing something useful with the BCM4751.

www spinics net lists linux-i2c msg03690.html

No details of the format are provided, only a document relating to licensing information from Nokia.

www forum nokia com info sw.nokia.com id b265d3aa-8198-4eb0-a0e3-077748ccea40 MEIF_Specification_License.pdf.html

The following talks a bit about MEIF, or the ME interface, describing it is "a de facto standard for GPS/GNSS chip manufacturers." Several related names seem to be "MEIF", "ME interface", and "ME-PE".

books google com books?id=stTSHdFhrFUC&pg=PA280&lpg=PA280&dq=meif+agps&source=bl&ots=z6QfZFkbPl&sig=pAsP8i1RWIhtF1Yebn3t1JApc4U&hl=en&ei=q8GcTK-BKcGB8gb67ZWVDw&sa=X&oi=book_result&ct=result&resnum=2&ved=0CBMQ6AEwAQ#v=onepage&q&f=false

It seems a common enough format in the industry, but no specifications were immediately forthcoming. Perhaps the Nexus has a more complete open source tree and includes something relating to MEIF?
[Captivate Android Development] iceman4357:
Mine has actually been MUCH better since the update. I tested the GPS on the way home from work. Its about a 35mile drive all highway with lots of side streets. Before the update the GPS position would bounce all over thinking I was on side streets when I was not. After the update the GPS position is much more accurate. I did pass undera bridge and the GPS was spot on, and didt really lag for me at all. It never once had a blue circle around my arrow.

Like a few others have stated, We will have to see if this fix stays accurate after a few weeks, as some of the "fixes" seem to work only for a few days.
[Captivate Android Development] Justinph5:
When I used my original stock rom & root, it would take a few minutes to get a lock, but after I got the lock, I could travel anywhere and the GPS would be spot on the whole way.

Yesterday I put on Cognition 2.1 with the OTA update. The GPS locks faster and in places it wouldn't lock before, but now I can't move anywhere without it sitting in the same spot then have to lock onto me again.
[Captivate Android Development] tehXKnight:
I had the same experience. Before it always seemed to do a cold start no matter what I set for AGPS, but once it locked on, GPS was solid and would hot start again until I had the GPS off for a few hours or reset the phone.

Now with Cognition 2.1 I get locks in under 30 seconds no matter what, but it acts like it just makes the lock, then drops it immedately, then it starts all over again and moves me on the map when it gets the next lock in 15-30 seconds. I watched it during the 20 minute drive home (the wife was driving) and the longest it went before dropping and reacquiring was 5-10 seconds.

But I agree. There's nothing wrong with AGPS. The problem is with the GPS itself maintaining a lock. *sigh* Kind of makes me want to go back to stock pre JH7. At least it eventually locked and stayed good then. It only seemed to get confused if I was stopped for a few minutes, like at a red light from hell.
[Captivate Android Development] phr00t:
I wanted to give you guys a heads up...

I just spoke with Samsung's tier-2 support, and they say it was just a misunderstanding that the JH7 OTA contained the GPS fix -- because it really doesn't:

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

The "real" fix is still scheduled to show before the end of this month.
[Captivate Android Development] iamamp3pimp:
I noticed a huge improvement using gps if it is on the dash and not in my lap.

as long as it can see the sky its happy.
[Captivate Android Development] Joe1981AL:
CRAP....typed up a long thing and crashed it by hitting backspace while not in the inputbox...

Ok I wanted to look at all this before even found source for drivers for the 4751 chipset for linux. I wanted to pass AT commands to the chipset. It may be possible using test functions that I've found. I'm just not good at programing, I just do some debugging, compiling, and testing.

Check out /etc/jupiter.xml and you see all the settings at the top, they are settings that apply to all jobs listed in the file. The jobs are specified with "job id". For those not familiar with the XML the <!-- sections are all commented out and DO NOT APPLY, they seem to be for an older chipset.

Check out /system/bin/gpsd also /data/gps and you will want to check out /data/gpspipe when this is running.

If you run "/system/bin/gpsd/glgps_samsungJupiter /etc/jupiter.xml normal" in one adb shell then in another run "cat /data/gpspipe" you will get raw NMEA pipe from the GPS.

You can create your own jobs in the jupiter.xml file, or make your own xml file and just specify it in the command line, while glgps is running you can send commands to the chip via a pipe that is opened to the chip at /data/gpsd/glgpsctrl

AFAIK on lbstestmode, dynamic accuracy off you get a lock only at the specified accuracy and loose lock if its worse. with dynamic on it tries for the best possible accuracy but if it goes over the specified setting for too long it looses lock. Thats why the higher the faster the lock.

I've got like 50 things going on here at work and playing with this, so if typo'd or missing something my bad, but just trying to give some help.
[Captivate Android Development] Kizzmiazz:
Same lol on my lap it would loose me all the time but if I held it in my hand chest level it would work perfect.

Sent From My Samsung Cognition v2.1.1 | Voodoo

Using Tapatalk No Force Close App
[Captivate Android Development] Joe1981AL:
from disassembly pics I've seen the WIFI antenna is on the bottom of the phone or maybe thats the cell antenna, there are two nubs that stick up and touch the battery cover

I'm assumming those have some type of antenna function, since I've seen no other antenna wiring in the phone pics from disassembly.

Used Bluetooth GPS to get data from my bluetooth "i-blue" that I have mounted in my trucks dash with external antenna on top. Used to use that for navigation for work with my laptop. The CNR is always about 20 more than the captivate is, which the "i-blue" used to do the same crap, run me through the woods before i gave it a boost with the external antenna. No matter the number of sats, low CNR will cause slow updates and bad tracking.
[Captivate Android Development] foxbat121:
I noticed the same thing. Not only that I found that when I stand the phone vertically (portrait mode) gives me better results than landscape mode.

Use GPS Test app, I noticed that I need 2 or 3 satellites in upper 30 SNR range in order to get mostly error free navigation. In rare occations, I got 40+ SNR on one or two birds. Sometimes, all I got are low 20s and low 30s. That will be a really bad day for GPS navigation.

BCM 4751 is suppose to be designed to work well in weak signals. But it didn't.
[Captivate Android Development] Joe1981AL:
Wonder if the extra satellite support SBAS/WAAS is turned on when the driver fires up or if its off, i believe this can be determined from the nmea if logged and looked over.
[Captivate Android Development] Joe1981AL:
oh yea, the commands in the "hal" section of the juptier.xml are parsed every time the gps is fired up by the system. The reason I'm 100% sure is back when JH3 came out you'd fill up your data partition with GPS logs if you didn't edit jupiter.xml and turn the logging off.
[Captivate Android Development] DemonWav:
Well if this is true, not sure I believe it, than we won't have to wait long.
[Captivate Android Development] jgaviota:
GPS Plus

Hi all, I live in Guatemala Central America

My GPS used to fail to get lock.

With the latest Cognition, it also didn't work.

Changed the settings in LBSTestMode to

MS Based

Supl Server: supl.nokia.com

Port: 7275

(The one configured in Cognition appears to work only from ATT)

With these settings I managed to get a lock, but while driving accuracy was waaay of, specially the bearing.

I then disabled GPS Plus, thinking that it is this setting that tries to guess where you are going and is responsible for overshooting and all of that.

After that bearing and position are spot on :D

So I think GPS Plus is responsible for figuring out where you will be, based on current speed and bearing. What do you think?
[Captivate Android Development] Joe1981AL:
hell, dunno what i did, but after latest update i can't get into lbstestmode

i haven't changed anything, went to stock, rooted, and put on cog 2.1
[Captivate Android Development] jgaviota:
Have you made an Activities Shortcut to LBSTestMode in Launcher Pro?

I'm told that you can also use Beutifull Widgets for that.

Key sequence doesn't work with JH7
[Captivate Android Development] Joe1981AL:
yea searched after i posted, someone mentioned lbstestmode in market so that was enough for me... its just a link to launch it :)
[Captivate Android Development] jgaviota:
If the settings aren't system-wide, how do we figure out where to change them so that they affect the whole system? Is there a driver to decompile or hex edit to change settings?
[Captivate Android Development] Joe1981AL:
from what I'm seeing we are using glgps daemon to fire off the GPS and control it, only some settings from lbstestmode are passed along to glgps, and other settings are controlled in jupiter.xml

the vibrant that is supposedly fixed or has a fix, i believe has moved passed the glgps and is using a better driver based system. something of that fashion may be what samsung plans on pushing to the captivate, hopefully they will...
[Captivate Android Development] BodaciousDrake:
My installation failed as well.

JH7 OTA w/ OCLF
[Captivate Android Development] KaLiBLeeK:
Well, I was able to get everything copied over with a combo of RootExplorer and adb...but my GPS didn't seem to like it, and I couldn't get any sort of lock while driving. Haha.

Ah wells, onto the next mod. Gonna try and leave all the GPS files as is after a reflash, and see how things act over the next week or so. I'm sure "poorly" will be the result.
[Captivate Android Development] 1randomtask:
Cog 2.2 beta 5, Jupiter 006 (except I modded gps.conf's ntp server to the Australian pool, au.pool.ntp.org).

Things looked a bit crap for a sec there, but hard reset the phone, google maps nailed within 10m.

Found whilst I could push gps.conf and jupiter.xml up with adb, needed root explorer to change secgps.conf
[Captivate Android Development] gloverka:
Where did you find/place the secgps.conf file?

Thanks!

Edit: found the secgps.conf file, but after adding all 3 files...seems to make 0 difference. Do I just simply copy the files over and replace the existing?
[Captivate Android Development] creepyncrawly:
Yes, but it wouldn't hurt to rename the files instead, if case you might want to restore them later.
[Captivate Android Development] CLShortFuse:
secgps.conf is just lbstestmode settings
[Captivate Android Development] asrrin29:
So I've noticed that the trend with any and all of the GPS fixes, including ShortFuse's, is that they tend to stop working after a period of time, or work at a reduced accuracy. I flashed to Cog 2.1.6, and GPS was atrocious (obviously, no GPS fixes in that version.) I ran Jupiter v005 and it functioned perfectly the first 24 hours. cold lock in 30 seconds, hot start in 5, 11/11 sats locked, accuracy to 16 feet the whole day while driving. Then it stopped working like that, and went back to a half fixed, sometimes works sometimes doesn't sort of fix that's better than the stock GPS, but worse than it was fresh.

I have a few questions regarding this. Has anyone taken a look at the files after they stopped working? maybe they get overwritten with a "default" configuration. If they don't get overwritten, maybe there are "defaults" hardcoded in the kernel or system files that get read from after a certain time period. This would explain why almost every single GPS fix works well for the first day, and then goes to trash after that.

Just my (somewhat unorganized) thoughts.
[Captivate Android Development] CLShortFuse:
There's a log folder that the GPS uses. What about using LBSTestMode's "Delete GPS Data" button?
[Captivate Android Development] mattbeau:
So I have noticed that deleting gps data does help after it has stopped working I've also noticed that no matter what version I'm running gps works great at first then deteriorates some time. after deleting gps data it some times comes back. We need some consistency in testing I always test with my phone on the dash and always use my tracks maybe should do better logging of exactly what we are doing using the same tools, versions, methods, time from install and list all of our installed apps maybe we can find a common link I will be doing a fresh install tonight of cognition 2.2.5 ive decided to keep the gps files stock for now to test
[Captivate Android Development] Dani897:
ive been doing some tinkering and my tracks shows great tracking on froyo, but, i cant get google nav to work, it gets a fix, then loses it gets another fix quickly, then after 10 min the gps turns off! nav is running but the gps icon disapears and it reports that it lost the gps signal. i had this problem with jf7 and i dont think it's samsungs fault this time, i think its google maps 4.5.xx when i ran jh2 i used maps 4.4.something and actually had decent results. im reverting back to 4.4 and trying to run nav to see if it works. has anyone else had this problem?

EDIT: its not the maps version, still mucking about trying to figure out why I could nav for 4 hours on jh2 with stock gps files, but since jf7 and ji6 it dies, quite literally after 10 minutes. Gps just turns off. Am I three only one experiencing this?
[Captivate Android Development] ewingr:
Road Trip GPS Test update

I had two Captivates on a 250 mile trip, each way, for total of 500 miles. Used both to compare.

One had stock install of Cognition 2.17.

One had Cognition 2.16, after doing a GSM reset, and then also applying the Jupiter V5 files.

Both had exact same results.

Worked perfect ONLY if the device was mounted from a suction cup device from the windshield, and it had no car roof overhead. Worked good in cloudy weather too.

In both devices, if I held it in hand, under roof, I would get blue circle, and occasionally drive through fields.

I am of the opinion (not expert) that the antenna is poor, and that no matter what we do, we won't get results we are expecting, unless no roof or hand obstructions.

My city driving, while not having done that much yet, appears to be running with same results.