[Verizon Samsung Galaxy S III] ben7337:
EDIT: After trying all 4 fixes for the galaxy s3, as well as the standard 3.1 no ssl, and the worldwide 1.3 fix, I can conclusively say that for my phone, only test 3 alt seems to work, and it does not work well as location is not very accurate and accuracy jumps around, up and down. 5-7 satellites are also no enough for a location fix, but 8 or 9 often get a location, 11 is enough to get accurate to 10-30m which is the best the phone can do. However it cannot always hold this accuracy.

Not sure if this post will be of any help, but I had a gps bug that seems to be somewhat common on the galaxy s3 for verizon. My phone used to have a nice instant gps lock. Then that stopped when I flashed from codename android to aokp. I can't remember how many satellites it saw, but it never seemed to connect.

I then used adbpusher to install the google gps fix, thinking aokp just needed a little help. The fix did not help, phone saw tons of satellites, but no signal strength for most of them, and never picked them up. Always just 1-3.

After this I flashed over to tons of roms, always wiping data/cache, and a couple times I even formatted /system. Nothing worked. I tried eclipse 2.1 biuld 4, codename android 3.6.6, and 3 different aokp builds. I then flashed to stock ICS 4.0.4 via odin, thinking stock had to work, because it had in the past. It didn't still no gps lock, not at all. So I installed updates from verizon and ended up at JB. Still no gps lock, even after giving it plenty of time.

Then I began thinking it was a hardware issue, but someone asked if I had tried the gps fix, and I thought, yes I had, but I had only tried one of the files. So I decided to try them again. I rooted my phone and unlocked the bootloader, installed eclipse 2.1 build 4, and began trying gps fixes. I did the standard google 3.1 with no ssl again, no luck. I then took the ones for the verizon galaxy s3, and copied all 4 folders to my internal memory card, and then just began copying and overwriting the gps.conf and the other file. I tried test 2, no luck, then I think it was late and I was fed up, so i tried test 3 alt. It still didn't work. Phone fixed on 3 satellites in a min or two, but then didn't add any more over the next 5-10 mins. So I gave up.

This morning I decided to try gps once more, and within 20 seconds, the phone locked on to a bunch of satellites and was doing great.

I have since tried getting lock many times and it is doing well. With the exception of the time I tried while typing this, where it took a minute ot two to get a lock. the phone had 4-6 satellites but didn't lock. While typing this it has worked up to 9-11 satellites.

My only gripe is how inaccurate the error counter is. I have a cheapo pantech marauder, which uses the same qualcomm soc which I believe holds the gps chip as well, and right next to each other, the marauder can have even fewer satellites fixed, and get location accurate to 3-5m, while the galaxy s3 is at 15 to 35m. However as I typed this the phone dropped to 7 satellites and the error kept rising on gps status and toolbox up to 145m inaccurate. I'd say it seems to hold around 25-35m normally. I just don't get why two phones with the same internal chipset for gps, can't both accurately determine location with a comparable number of satellites.

I know the marauder is a phone from a different manufacturer, but is there any chance the gps.conf and other file from it may be useful at all? Or if not, what part of the code in the phone itself handles the location calculations from gps information, because the gs3 does not seem to do a stellar job at that.

Now in maps my phone won't get a location lock. gps status and toolbox says it has 5 satellites, but it never seems to get a location lock even with a 5 satellite fix. Which makes no sense to me as that is plenty for a fix, if not a very accurate one. Maps got my location as accurate at 10m, then it ballooned out to eventually 100m, then dropped lock, and hasn't gotten it back since.