yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] zoid_99:
Vibrant:

# busybox find . -name *gps* -print

./data/gps

./data/gps/secgps.conf

./data/app/com.eclipsim.gpsstatus2.apk

./data/data/com.eclipsim.gpsstatus2

./data/data/com.eclipsim.gpsstatus2/shared_prefs/com.eclipsim.gpsstatus2_preferences.xml

./data/data.bak/com.eclipsim.gpsstatus2

./data/data.bak/com.eclipsim.gpsstatus2/shared_prefs/com.eclipsim.gpsstatus2_preferences.xml

./data/dalvik-cache.bak/data@app@com.eclipsim.gpsstatus2.apk@classes.dex

./data/dalvik-cache/data@app@com.eclipsim.gpsstatus2.apk@classes.dex

./sdcard/gps_fix_epic_signed.zip

./sys/devices/platform/jupiter-battery/power_supply/battery/gps

./system/etc/gps.conf

./system/lib/libclientgps.so

./system/lib/libsecgps.so

./system/bin/agpsd
[Galaxy S I9000 Android Development] Case_:
I was talking about stock Vibrant. And yeah, make that jupiter.xml, not jupiter.conf. At least the libgps.so was correct, I really did mean this library, not libsecgps.so. Obviously I should stop trying to figure out something and finally get some sleep. Two stupid typos like these in a single post - not a very good sign...
[Galaxy S I9000 Android Development] _brainlock:
$ md5sum /system/lib/libsecgps.so
8cf4c6a138c7e59665d56e554510bfeb /system/lib/libsecgps.so

the same as your Vibrant.

Also,

$ md5sum /system/bin/gpsd/*
0a28dafb3cab3a7249654d5c8323ef33 /system/bin/gpsd/7651b327.0
6b31db2a30ec1bac19f6efc3fe174dd3 /system/bin/gpsd/c9dbfc2e.0
9dbedb7e623a515178b57c7e53248c7c /system/bin/gpsd/ddc328ff.0
2c305a6aa6fc2ae1563e1df79e33ea06 /system/bin/gpsd/f0b6e66f.0
8cdfee5db243edb70f8d5c3d2d568794 /system/bin/gpsd/glgps_samsungJupiter
[Galaxy S I9000 Android Development] lqaddict:
Hmm the lib in epic fix is different even the size
[Galaxy S I9000 Android Development] Case_:
Could someone with Vibrant perhaps share with me/us the files from the root of the file system? Especially init.rc... it would save quite a lot of time...

As for reverting the fix on Vibrant - I can't seem to make the update script work and realy am in no condition to do such things anymore today, God knows what I'd mess up. So, if you have root, you can revert the fix manually:

1. Delete the directory /system/bin/gpsd and its contents.

2. Delete the file /system/etc/jupiter.xml

3. Delete the file /system/etc/libsecgps.so

4. Copy the attached libsecgps.so to /system/lib - you have to unpack it first, of course (it's extracted from the Vibrant stock fw).

5. Done

Sorry about that, I'll try to make a proper package out of it as soon as possible.
[Galaxy S I9000 Android Development] dsellers2:
Maps is FL After Installing

Hi there,

I have installed the fix and it seems my fixes are way more accurate and much much faster. But, after implementing I try to load up Google Maps and I'm getting Force Closes for some reason. Once I load Maps it opens and shows a map and a few seconds later it crashes.

With Google Navigation I'm not getting force closes.

I have tryed reinstalling, Fixing permissions in Rom Manager, and I have turn on and off use Wireless for "My Location"

Any one else experiencing this problem? Any help would be appreciated, since this is the best fix I've seen yet, I have to be able to use maps.
[Galaxy S I9000 Android Development] distortedloop:
Not sure how anyone can declare things better after just a test or two...like the original poster stated, GPS can go days without issues for some of us.

I installed this fix just for the heck of it. GPS test in the house seemed to grab a signal quicker than normal, but the satellite locks fluctuated wildly from 2-6 mostly.

Testing with Google Maps on my 5 mile commute, GPS locked fairly quickly, and tracked fairly accurately most of the ride. The only thing I noticed was the first few minutes of the drive, my position on the map was lagging about 500 feet, but the track in relation to being on the street I was on, was accurate. About 1/4 of the way to the office, my vehicle started showing me driving in the front yards/living rooms of the houses on the street. LOL. This is an improvement, actually, as sometimes on that portion of my ride, it will show me a block or two away from my actual location.

I'm reserving judgment on this, since obviosly a few days of actual use is needed to notice real and lasting improvement.

Still, thanks to the OP for packaging this up and posting it!

FYI - I'm on a recently flashed/fresh install of JM5 and hadn't touched any GPS settings since flashing the ROM.
[Galaxy S I9000 Android Development] mickeko:
Ok, here's something new to try for you. This may be just wishful thinking, but I really do feel that my gps does drop the lock on the satellites much less this way:

Just disable Orientation in Settings - Sound and display.

But be warned, I've just briefly tested this, so don't go touting it as the godsent solution to all our problems... :p

EDIT: Oh, and even if it DOES work, it'll just help the GPS maintain the lock and not actually make it any more precise.
[Galaxy S I9000 Android Development] Mycorrhiza:
Will this work with JP3?
[Galaxy S I9000 Android Development] mastergrillo:
Installed the epic gps files and its working way better then jm5 jh2 jh3 on my captivate lock really fast indoors and picking up alot more sats going to do a test run on the way to work
[Galaxy S I9000 Android Development] xetrev:
Installed and navigation/google maps work fine indoors and get me pretty close (it thinks i am in the middle of the house next door). I will test shortly when i go for a drive and see how it keeps up.
[Galaxy S I9000 Android Development] Case_:
No.

10char.
[Galaxy S I9000 Android Development] omriasta:
Also noticed this in JH3 with/without using the update.zip included here. Tried reinstalling /rebooting/fixing permissions. No Luck. I am on a Captivate.
[Galaxy S I9000 Android Development] Mithent:
I've not taken it anywhere, but with this fix it seems much the same to how JM5 was before for me (with the Google SUPL change). It fixes fairly fast, but it's not very accurate and drifts a lot.

Hm, I assume it did install correctly.. my /system/etc/jupiter.xml has a newer date than the other files in there, so I guess so.
[Galaxy S I9000 Android Development] :
Forgive me being a noob, but does my phone need to be rooted to apply this potential fix ??

Galaxy S on o2 (UK) ECLAIR.I9000XXJM1
[Galaxy S I9000 Android Development] jentech:
Ran this fix on my Bell Vibrant with JH2. My quick and dirty testing from my desk at work, using LbsTestMode.

Before fix; no better than 50m accuracy with 3 to 5 sats.

After fix; 10 to 30m accuracy with 7 to 9 sats.

Will try Co-Pilot after work and see it I get better lock.

edit: I let testmode run for about 10 minutes each time.
[Galaxy S I9000 Android Development] distortedloop:
Well, you need to be rooted to use ROM Mgr, and it says to use ROM Mgr to apply the fix.

You MIGHT be able to just rename the fix file to update.zip and apply it through the native recovery.

Might also be able to use adb to manually push the files in the zip to their appropriate locations. Not sure if you need root for that on the phone.
[Galaxy S I9000 Android Development] :
Thanks for the info, I'm not really confident enough to root the phone yet. Maybe after the "September" roll out of FroYo :)
[Galaxy S I9000 Android Development] Case_:
You DON'T need to be rooted! That's the beauty of ClockworkMod recovery for Galaxy. Just download it as an update.zip and put it to /sdcard. Then just start your phone in recovery mode and select "apply update.zip". The ClockworkMod recovery will start (it might just reboot back into the standard recovery the first time you do this, just apply the update.zip again) and from it, you can make nandroid backup and flash whatever you want.

Every time you want to start ClockworkMod recovery, just repeat the above. And if you want to remove it (meaning the recovery, not this fix), just delete the "/sdcard/update.zip" file and it's gone.
[Galaxy S I9000 Android Development] InsaneJester17:
How can I remove this? My Captivate doesn't even try to GPS lock now after running this. :-\

I'm on JF6 with unlock the beast and tayatuma lag fix BTW.
[Galaxy S I9000 Android Development] Case_:
You may try to give it some time, sometimes the GPS does that when you change its files. Just let the phone be for a while without using the GPS (15 minutes, half an hour), you may even reboot it meanwhile, then try again. It SHOULD work on Captivate - after all, the alternative fix based on JH2 fw uses files from Captivate.

As for how to remove it on Captivate - I could try to make a revert package for Captivate, but it won't be today. Other than that your main option is to just restore the nandroid backup (you did make a nandroid backup before flashing an experimental fix not tested for your phone, right?) or you can get the files it replaces and manually overwrite them using adb and/or Root Explorer.
[Galaxy S I9000 Android Development] distortedloop:
You've used clockwork without root? Market description says "ROOT USERS ONLY!!!", but in light of the way it works (update.zip from regular recovery) seems like it doesn't really need root after all. Hmmm...

Not sure why anyone wouldn't want root anyways?
[Galaxy S I9000 Android Development] OGC313:
Installation aborted???!

Any ideas?
[Galaxy S I9000 Android Development] xetrev:
Drove around town today and it was all over the place. It did follow me better on the map but once i made a turn the blue circle blew up bigger then i have ever seen it. If i held the hand held directly under my front windshield it seemed to work better but the gps is still broken. If i need directions i am using the navigation and just having it print out turn by turn directions and then following them.
[Galaxy S I9000 Android Development] Case_:
ROM Manager does need root ('cause it runs as an app in the system). ClockworkMod recovery for Galaxy doesn't, so it doesn't ;) So if you don't want root, you can just ignore ROM Manager and use "standalone" ClockworkMod recovery.
[Galaxy S I9000 Android Development] dereknas:
I could not get this installed through recovery. Renamed the attached file to update.zip and copied to root folder. After select update.zip in recovery mode, got some errors like "...signed...." or something like that.
[Galaxy S I9000 Android Development] Toss3:
Thanks a million for this - getting a lock in under 10 seconds without using aGPS and without the supposed GPS fix settings that were posted awhile ago(never worked for me, so I decided to use the standard settings as they seem to work a lot better).
[Galaxy S I9000 Android Development] KLoNe1:
Installed Epic G4 files. With GPS TEST I can't see any satellites at all (didn't test before Epic G4 test though).

Brisbane, AUSTRALIA here.
[Galaxy S I9000 Android Development] ChiGGz:
lock in 10 seconds, but inaccurate to 100+ feet at times.

Sigh, I'm losing hope.....
[Galaxy S I9000 Android Development] boomerbubba:
Has the OP, or anyone else for that matter, discovered for a fact which of the files from the Epic dump contain the proprietary GPS driver from Broadcom?

If so, can you tell whether that has changed from other Samsung S variants? How can you tell?
[Galaxy S I9000 Android Development] insty:
Epic installed fine. Google Maps was almost instant to find my location.

Great stuff!
[Galaxy S I9000 Android Development] Evans_Prophet:
I did it through update.zip. During the whole day (I am on vacations) I had not been able to get a lock. After applying the patch I had a proper and accurate lock quite quickly.

Fact is, however, that the GPS still seems to average too much your course: take a quick sharp turn and you will see the dot reacting quite slowly and taking a much wider turn.

Recommended at the moment if you want to be able to use navigation.

Btw refresh rate is still 1hz - I was expecting 2hz (as in other phones)...
[Galaxy S I9000 Android Development] kenkiller:
One strange side effect. The Downloads tab in Market no longer works. Keep getting network errors. But searching for apps works, as with Appbrain.....strange.... :)

Epic fix installed.
[Galaxy S I9000 Android Development] lgkahn:
Re market... don't think this app caused the issue.. market worked all day for me after installing this patch, but not now... think there is currently a problem with Android market.
[Galaxy S I9000 Android Development] kenkiller:
I see....interesting. :D Pure coincidence I guess.

strange that only the Download tab doesn't work.
[Galaxy S I9000 Android Development] insty:
Yep, can confirm. Download tab is broken.
[Galaxy S I9000 Android Development] kenkiller:
Maybe not. I tried with my wife's Desire, Market is down. Our Market probably has the front page cached, so it seems that only Download tab is down, when in fact the market is down. :(

Some twitter posts also state market is down.
[Galaxy S I9000 Android Development] Bajo76:
Yes, the market is down atm.
[Galaxy S I9000 Android Development] Telanis:
No change for me on my Vibrant -- GPS still doesn't work at all.
[Galaxy S I9000 Android Development] KLoNe1:
Same here; bit of a joke.
[Galaxy S I9000 Android Development] Toss3:
Which GPS settings are you using?
[Galaxy S I9000 Android Development] NetCopAD:
Tried it on XXJF5 - walking, driving, standing. Didn't make a noticeable difference. Maybe a bit worse than before, but this could be due to temporary conditions.
[Galaxy S I9000 Android Development] Case_:
Thanks for the init.rc! Yes, that commented out part refers to files that we do have on I9000 but are not in Vibrant fw. See these parts of init.rc:

# create data/gps for GPS demon
mkdir /data/gps
chown system /data/gps
chmod 771 /data/gps
# GPS development for broadcom.
#chmod 0777 /system/bin/gpsd/glgps_samsungJupiter
#chmod 0666 /system/lib/libgps.so
chmod 600 /system/etc/secgps.conf

#service glgps /system/bin/gpsd/glgps_samsungJupiter -c /system/etc/jupiter.xml
# user root
# group root

#added for STE GPS
service agpsd /system/bin/agpsd
user root
oneshot

So you have commmented out the "usual" GPS service, but added something referred to as "STE GPS" that's not on I9000 (we don't have the agpsd file in bin). And our files are referred to as "GPS development for broadcom"? What's going on there?

Anyone has any idea what that is? Does that mean the GPS in Vibrant is using different hardware? And if it is, why the people with Vibrant report improvements when using this Epic4G fix...?
[Galaxy S I9000 Android Development] appelflap:
Well that's very interesting! My guess is that the files on the i9000 are still under development. What else could "GPS development for broadcom" mean? And what should we as end user do with a development environment on our devices?

Can one of you Vibrate guys post the /system/bin/agpsd file, so we can try it out?
[Galaxy S I9000 Android Development] Case_:
Just download Vibrant firmware and you can extract it easily. But to test it, you'll probably have to compile your own kernel, 'cause we can't change init.rc any other way (unless I'm mistaken).
[Galaxy S I9000 Android Development] Krad:
have been using the 4g files on my captivate and it may lock a bit faster then JH3, it jumps around alot! it is like a leap frog. Going back to the JH2 files listed..
[Galaxy S I9000 Android Development] ghosty_uk:
i have not applied the fix, but then since swapping my SGS for a new one after my first one failed to get a lock, i have had no problems, in finding sats / getting locks.

to appleflap, i tried your apk, file and it showed 0 sats 0 locks, when both gps test and lbstest show i have at least 8 shown and 5-6 locked tried it both inside and outside but no luck.

ok just tried again, it found 6 sats, locked 4, and min SNR was 21 accuracy wes jumping from 117 -90 meters

ok min SNR has now dropped to 15, on 5 seen, 4 locked. accuracy is now down to 25 meters,

im inside my house. and SGS is as it was from stock.
[Galaxy S I9000 Android Development] lqaddict:
It will not make sense if vibrant is packed with different hardware for gps, will it? I mean if Samsung is working on the fix for it across all models they would have to develop different fix for us vibrant users in the US. I'm scratching my head now. So there is no way manually edit init.rc file?
[Galaxy S I9000 Android Development] Case_:
As far as I know, no. The init.rc is inside the zImage on Galaxy S phones and I'm not aware of a way to splitting the zImage to the individual components, editing init.rc and then putting it back together.
[Galaxy S I9000 Android Development] TriC_101:
Just install gps_fix_epic_signed.zip on my Bell i9000 and it installed ok.. using ClockworkMod recovery.. will let you know when I go for a drive or walk tomorrow how good it works

.
[Galaxy S I9000 Android Development] appelflap:
Isn't it possible to copy the agpds file to the /system/bin/gpsd/ directory and rename it to glgps_samsungJupiter. I know, it's a quick and dirty method :) , but maybe it works. Don't know if the system will fail on the -c /system/etc/jupiter.xml argument though :)

If you don't like to try it (can cause some boot problems) just upload the agpds file and I will give it a try.

Furthermore, have you tried flashing the Vibrant kernel over a i9000 firmware version? (if not maybe you can upload the vibrant zImage file too?)
[Galaxy S I9000 Android Development] TriC_101:
I do find after applying the gps_fix_epic_signed.zip my compass seems to be way off..
[Galaxy S I9000 Android Development] CommanderROR:
Has anyone found out yet whether there are any hardware differences between the Epic4G GPS and and the Galaxy S GPS?
[Galaxy S I9000 Android Development] amertak:
Nice work, after Epic4G fix i can get fixed even at home. Accuracy about 30meters inside, outside test soon :)
[Galaxy S I9000 Android Development] CommanderROR:
I can't try it myself yet, but I just read from another user in a different thread that the 4G fix did not really do much to fix the GPS problems in his case. Maybe it really is down to different phones having slightly better or worse GPS system onboard, maybe a faulty or at least weak component?
[Galaxy S I9000 Android Development] ickyboo:
I can honestly say that this helped. But then again i rarely use gps

Sent from my Apple Newton 2100
[Galaxy S I9000 Android Development] CommanderROR:
I just read on a swiss android forum that the SGS GPS reception problem micht be similar to the Iphone 4 phone reception problem. I can't verify this, but maybe you can.

Apparently, there is a measurable difference between holdin the SGS in your hand and just holding it with two fingers, not covering the back.

http://www.pocketpc.ch/samsung-galaxy-s/97921-hardwareproblem-gps-empfaenger-2.html

Here is where I found this theory and some attempts at reproducing it have been made. Please give it a go and see whether you can reproduce. Maybe somebody should open a new thread for this topic to get faster and more numerous test results.
[Galaxy S I9000 Android Development] distortedloop:
I've noticed better GPS performance between holding the phone in my hand while driving, putting it in the center console cup holder, and hanging it from charging cord higher/closer to the windshield. Seems to support the theory you're quoting in my experience.
[Galaxy S I9000 Android Development] Case_:
Oh, that is dirty indeed! Never even occured to me ;) Might give it a try later.

The Vibrant kernel doesn't seem to work on I9000. But I'll upload both files soon nevertheless.
[Galaxy S I9000 Android Development] Fatherboard:
Tried the epic fix, slight improvement. waze/google maps/igo amigo are still barely usable (huge lag in position update - it doesn't even manage to provide the correct speed, maybe after few minutes of runtime).
[Galaxy S I9000 Android Development] Case_:
Yes, the lag is the biggest problem and I'm afraid there's nothing we can do about it. Tried just now another comparison of track recording between Galaxy S and VF845, 'cause I've been testing some mixed files fix alternatives. VF845 came out as a clear winner again. Spot on track record, no problems with sharp turns - which you can see from the attached screenshots (Galaxy is in red, VF845 is in blue and obviously matches perfectly the path I was actually taking). What you can't see is the fact that my supposed location on Galaxy was dragging some 10 meters behind all the time.

From my perspective, the "fix" did help with maintaining somehow accurate path when the signal is good. Once it's not so good or once you start changing directions too fast, it's all over the place, just as before. And the constant lag is annoying and could be very problematic when using turn by turn navigation in the car, 'cause you would be far ahead of the GPS location.

And I don't think there's much we can do about it. We can hope that Samsung will be able to solve it, otherwise we either have to adapt to it or sell our phones (I hate to say it, but it seems like a more likely option for me if Samsung doesn't fix this, I'd hate to have a perfect phone with one very annoying flaw, it would bug me to no end...). I still want to test a few more things and most likely upload the "fix" that gives the best results to me, but that's about it, then it's in Samsung's hands...
[Galaxy S I9000 Android Development] Fatherboard:
Very saddening.. the lag issue is a major flaw which has to be fixed (not "optimized or improved" - thanks to samsung's CRD). I can pass two or three traffic lights before it updates my current position. :(
[Galaxy S I9000 Android Development] Mycorrhiza:
Does this with with the new jm1?
[Galaxy S I9000 Android Development] BackfireNL:
New jm1 is slightly better but still some lag
[Galaxy S I9000 Android Development] Case_:
I've just seen on other thread the (supposed) Epic 4G init.rc and it's even more confusing...

# GPS development for broadcom.
#chmod 0777 /system/bin/gpsd/glgps_samsungJupiter
#chmod 0666 /system/lib/libgps.so
chmod 600 /system/etc/secgps.conf

So there's supposed to be a /system/etc/secgps.conf file that is missing from the dump we have available (given that its permissions are set to 600, I guess it's not that surprising...)

And then this:

#Disable BRDC GPS Daemon
#service glgps /system/bin/gpsd/glgps_samsungJupiter -c /system/etc/jupiter.xml
# user root
# group root

So the GPS daemon isn't even started at all? That's all there seems to be in Epic 4G's init.rc in relation with GPS, nothing more (so even less than we have on I9000)...
[Galaxy S I9000 Android Development] boomerbubba:
Remember that there is also the mysterious system app called GpsSetup, which no one without an Epic has run.
[Galaxy S I9000 Android Development] Case_:
I know about that. Been wanting to try to do something about that, but haven't had time just yet...:(