yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] crypted:
If you're saying that this patch works great now as compared to the earlier attempt, I would suggest that your problem was cache based. A lot of devices have numerous NAND partitions that are inaccessible for clearing including some hidden cache one's. There is/was a cache partition for GPS data. Maybe that finally reset during the process perhaps by coincidence...
[Verizon Samsung Galaxy S III] Coderedpl:
no idea, I'm not sure how a restore and redoing the same steps would, but hey, it works now =D:cowboy:
[Verizon Samsung Galaxy S III] BlueCross:
I don't know why you're having issues, but I'm getting instant locks when I'm outside and 3-5 second locks indoors.

I thought the GS3 utilized GLONASS, which is superior to many other smartphones. But maybe I'm oh so wrong. :cowboy:

(Synergy R73 and Imoseyon 1.1exp kernel)
[Verizon Samsung Galaxy S III] crypted:
Are you saying you're not having problems by using this patch or in general?

GLONAS plus GPS is a new offering. It theoretically is better, but this isn't always the case in practice.
[Verizon Samsung Galaxy S III] mad96:
I wanted to say thank you to the dev for this patch. It was taking 4to 5 minutes to get a lock if I was lucky now it locks on in about a second and that's no exaggeration. So again thanks for your work

M.yA.nD.droidS3
[Verizon Samsung Galaxy S III] BlueCross:
I have had zero problems with GPS in general whiles on a TW based ROM. And installing this patch made locks instant.
[Verizon Samsung Galaxy S III] crypted:
Great, thanks for the clarification. I'm glad this helped even further!
[Verizon Samsung Galaxy S III] XfrostX:
Are people using this patch with CM? I patched it but I'm still getting really slow locks :(. When you turn on GPS + Maps there's usually a notification saying (Searching for GPS or GPS Locked) but I don't see that instantly. It shows up after a minute or so. Any idea?
[Verizon Samsung Galaxy S III] crypted:
Read and comply with the Notes.
[Verizon Samsung Galaxy S III] jbdan:
2nd time using this patch. 1st on CleanRom 2.5 and now Liquid RC5. Exceptional on both thx for your work and time into making these phones that much better!
[Verizon Samsung Galaxy S III] keatond:
awesome

Just wanted to say that this patch works perfectly. I live in San Francisco and it was taking up to 5 minutes to get a gps lock in town. Since the patch was installed I get a lock in under 3 seconds. Its great! Thanks!
[Verizon Samsung Galaxy S III] Madcat81:
This worked great on CleanRom 2.5! went from no GPS lock (gave up after 8 minutes) to less then 5 seconds!

Thank you.
[Verizon Samsung Galaxy S III] wingchun108tek:
I have a question about trouble shooting using those steps. does it matter if we are connected to wifi/3g/4g even if the "use wifi and mobile networks" option is NOT ticked? I just want to make sure that i'm testing out the GPS lock properly instead of fooling myself into thinking it is working when infact it may not be.
[Verizon Samsung Galaxy S III] crypted:
Yes, it could matter - WiFi could allow IP based location sensing and mobile can allow for tower based. However, if you're under 30ft you should be GPS based.
[Verizon Samsung Galaxy S III] tu3218:
Phones GPS icon is solid showing I have lock, an its right around where I am, but not right. I also went into GPS status, giving me all information at the bottom as if I'm locked, but no green bars signifying I'm locked onto satellites. Any ideas?
[Verizon Samsung Galaxy S III] tu3218:
Heres a picture.
[Verizon Samsung Galaxy S III] crypted:
Read the entire OP post. The Notes would probably help you out considerably. Furthermore, you failed to abide by the requirement on how to post for help as per OP post.

And, there is no image showing up either.

Please abide by the rules I established to ensure we all are on the same page with one another.
[Verizon Samsung Galaxy S III] tu3218:
Its showing up on my xda app right now.

I did read it. Now its putting me in NC but im in MD an I tried step 26 an still no go. It actually keeps going back an forth. Did I miss something?

I'll give the CM tips a shot.
[Verizon Samsung Galaxy S III] crypted:
I know absolutely nothing still. Come on, read the OP Post.

Hint: Rules For Posting Questions.
[Verizon Samsung Galaxy S III] Wontfinishlast:
I've been having the same problem as tu3218. I'm on Liquid Smooth RC5 running leankernel 1.4. However I also had this problem on synergy r73 running leankernel (I don't remember exactly which release). I've only ever used Google maps and gps status to test the performance of my gps signal.

My gps has always worked, however the first lock after a reboot takes between 3 and 15 minutes. All subsequent gps locks are between 5 to 20 seconds.

If I do not have network location enabled, maps puts me in North Carolina instead of North New Jersey. At least until a real lock is established several minutes later.

I have read the notes extensively and i have the same issues before after battery pull and with/without my case.

It seems like, for some reason, everytime my phone is rebooted, or location is off for extended periods of time, the agps is cleared.
[Verizon Samsung Galaxy S III] crypted:
That's very strange. And, this occurs with the deoxed stock ROM as well?

Sometimes it's something as crappy as the NAND management or the hardware itself. But, I find that most of the time it is ROM related when the Notes do not assist.
[Verizon Samsung Galaxy S III] Wontfinishlast:
Yessir.

I suppose I could go back to stock and start from scratch. Like I said though it's usually only the initial lock that takes forever and I don't completely rely on gps like some other folks here. Maybe I'll save it for something to do on a rainy day :)
[Verizon Samsung Galaxy S III] crypted:
Well it really sounds cache related and the reboot is indicative of a problem with the special NAND partitions for GPS. Without the device I assume that this exists for this device like all other Android devices I've toyed with. Not skilled in the low-level area to check or repair this, though.

Again, this is ruling out hardware based upon your above stated observation.

Download or edit GPS Status if you already have it. Set it to re-download aGPS data twice or thrice daily. See if this helps resolve it. For instance, consider rebooting. Before opening up Maps, use GPS Status to download new aGPS data and see what happens.
[Verizon Samsung Galaxy S III] Wontfinishlast:
I have tried that also. It was ineffective.
[Verizon Samsung Galaxy S III] ice.candi:
I I've had the same prob with being in nc while in nj...except i can't get a gps fix for the life of me...and its telling me there's 26 satellites in view just won't connect to them i guess...reboots bat pulls wipes...tried all 3 methods....once i restore my nandroid I'm back to where i should be without the patch (although i wouldn't mind being where it tells me i am...i used the s3 download on about 5 diff roms ranging from cm10/aosp to stock and a few inbetween with same results...even stood outside for 40 min waiting to see if it would lock on there eventually...but nope gps still says in nc...maps shows me in the right place visually but still tells me I'm in the wrong...verison s3 bug maybe?
[Verizon Samsung Galaxy S III] crypted:
Very odd, indeed. The only times I've seen irreversible issues where my Notes do not resolve the matter have been 1) hardware and 2) NANDFlash partition issues. Either way, it's outside of the scope of this patch.

If you're seeing 26 satellites then I would say that it is entirely screwed up even with GLONASS support being available. The likelihood of that unless you were out in the little middle of nowhere with flat terrain is very much on the border of insanity. Heck, even then that's a high number...

So, it isn't really parsing GPS data for some reason... I'll bet it as being issue #2 which would require someone to determine exactly which hidden partition is the cache partition for GPS data and how to successfully re-format it.
[Verizon Samsung Galaxy S III] jbdan:
This patched has worked great for me on CleanRom 2.1 - 2.5 and on LiquidSmooth RC5. I loaded up CleanROm3.0 today and had major gps issues, unlike past roms (were minor), and installed the patch via same way I did all the other times. It worked initially, but then began telling me I was turning on streets that I wasn't turning on. Also showed me going the wrong way on roads and it was lagging behind really bad. My wife has a gs3 as well and her gps is perfection. I took the gps.conf from her phone and pasted it to my gs3 /system/etc and now mine is AOK. Not a complaint per se, just an observation. Oh well.....
[Verizon Samsung Galaxy S III] crypted:
Well we can deduce this to being a ROM-related issue since it worked well for you in the past on multiple ROM's. The curious part is that something assisted you for this particular ROM by reverting back to stock if I'm not mistaken in what you're saying?

If you could please private message me the content from her device, I would like to review it and maybe make some further tweaks. Please, don't paste it here as that will only add to some confusion.

Thanks for the input!
[Verizon Samsung Galaxy S III] jbdan:
Oh definitely rom related I agree. I didn't know what it'd do if I took her gps.conf and pasted it to my phone, but it works perfectly now. Shes running CleanRom 2.1 and came from stock. I've flashed every ROM out there on my sgs3 :laugh:

Will PM you her gps.conf shortly thanks
[Verizon Samsung Galaxy S III] sebastianraven:
Oddly enough, I'm having the same issue with the update. If you come across a fix or need anything from my phone, hit me up.
[Verizon Samsung Galaxy S III] crypted:
Sending you a private message with a test build. Let me know how it goes via PM.

I'll release it if we're golden.
[Verizon Samsung Galaxy S III] speedingcheetah:
SGS3

Flashed the SGS3 build to my stock rooted phone...and no improvement....still showing me 30-40 feet away from where I am...same as before flashing.

EDIT...WOA....now I go to make a call and I get message that verizon can't authenticate phone....WTF?

Well...not sure what happened...phone locked up for a bit..i rebooted twice..and now it seems to be working fine..maybe a push update tried to go through ...no idea.
[Verizon Samsung Galaxy S III] crypted:
This patch CANNOT screw up a phone as you describe. Something else is wrong in your personal scenario I'm afraid.

Read the Notes Section about this whole deal. Also, I'm working on a new beta for the SIII and will release it pending success of the user base.

EDIT: Actually, I think I even sent you the private link to the new BETA a few hours before your last post. Discuss it with me privately if you want to work with it.
[Verizon Samsung Galaxy S III] voodoomanx:
Flashed this per instructions using cwm. I now have no satellites and the gps icon doesn't even light up in the upper left corner. Any tips?

Edited: reflashed. Now I am in Creed more nc with zero satellites.
[Verizon Samsung Galaxy S III] crypted:
You're not helping me diagnose anything. Read the part on how to post and the Notes Section. Then, repost.
[Verizon Samsung Galaxy S III] voodoomanx:
Well I read each and every note in the section. I am running jellywiz rls8 hybrid and flashed the s3 specific build in cwm after mounting system as described. What else would you like to know?

I attempted the ssl version but it came back 0. I am attempting the no ssl version now.
[Verizon Samsung Galaxy S III] crypted:
What was your issue before the patch?

Have you done note #26?

And you are sure this isn't ROM related?
[Verizon Samsung Galaxy S III] voodoomanx:
Gps was intermittent so I thought I would try this. I did note 26 and battery pull. Now I no longer have an active gps icon in the upper left of the screen and cannot get a satellite lock using gps status.
[Verizon Samsung Galaxy S III] crypted:
Really sounds ROM related. Use GPS STATUS to reset and redownload the aGPS data. If that fails, do a Nandroid and test another ROM to be sure.
[Verizon Samsung Galaxy S III] voodoomanx:
Downloaded faster fix, went outside and now have 18 of 21 satellites with accuracy of 3 meters. Just in time for deer season. All is good.
[Verizon Samsung Galaxy S III] crypted:
As per notes, that'll hijack some of my patch. I'm quite curious what it would have done on your device. Interesting...
[Verizon Samsung Galaxy S III] voodoomanx:
Well I figured since the patch didn't do anything it was time to try an alternative. Will post any adverse effects.
[Verizon Samsung Galaxy S III] countryfolk07:
Not trying to disrespect anyone, please do not read into anything. But isn't it strange how several people are being located in NC, when they are elsewhere, as I also am. And now people can't lock. I've done this before on This exact stock ROM, and it worked. But now I am also having the same issues as everyone else recently. I've done all the notes twice, and nothing has helped. Now my GPS is not working. How can we revert back to stock? Without reflashing everything. I don't want to do that because I've been slowly trying to tweak this thing. Any help other than referring to the notes would be greatly appreciated. :confused:

EDIT: Replaced the modified with the stock GPS.conf and was able to lock accurately within a few minutes. I think something is up with the server? Or something? Just trying to help.

Sent from my what the Nexus should have been! GSIII (It's a long story)
[Verizon Samsung Galaxy S III] crypted:
It isn't server related. I'm perplexed as I don't have the device to work from.

I provided a new ZIP to people to test who were having this problem. I haven't had any response to indicate success or not.

I'll send it to you as well since you're having the same problem.
[Verizon Samsung Galaxy S III] MrCapcom:
I'm having the same issue pass well with navigation always saying I'm in nc I flashed sags3 test zip from op
[Verizon Samsung Galaxy S III] crypted:
Can you try the generic no SSL version and report back?
[Verizon Samsung Galaxy S III] checktravis:
just tried the Galaxy S III Test 2 and my CM10 M2 locked within about 3 seconds. it got a location before any sats were fixed. i tried everything, i just flashed to stock to start over because i rarely could get any gps lock and still no help until this.

awesome! thanks!
[Verizon Samsung Galaxy S III] Ratzinc:
Was experiencing gps issues when I used my hyperion extended battery and back cover, threw on the original battery and back cover and it gps worked again...
[Verizon Samsung Galaxy S III] crypted:
Yes, that can cause a problem with there being too much blockage or reflectivity on the GPS antenna...depending.

This patch has been used countless times and serves millions of requests weekly. But, my work cannot compensate for hardware issues whatsoever (or, faulty ROM's in some instances).
[Verizon Samsung Galaxy S III] bits8mybytes:
Freakin' Awesome

Thank you so much for your effort, and this post. I, like others on a Galaxy S3, was having this weird NC Durham for my GPS lock. I fixed it by following your exact instructions in the OP. Then when I rebooted and got the North Carolina location I enabled and disabled my GPS multiple times while maps was open and it was trying to get a lock. After doing that a couple times one of the times it locked onto my correct location. Now it locks on to my location almost instantly! Before it was taking 1-10mins for a lock every time I restarted my phone. You have made my S3 so much better, again thank you very much.
[Verizon Samsung Galaxy S III] MrCapcom:
For whatever reason it won't flash for me in TWRP or Clockwork Touch

wait re read OP lol ill try one of the other ways
[Verizon Samsung Galaxy S III] crypted:
Did you notice there are three different installation methods? So, if flashing fails the OP post instructs to try another method. There is no way that all options would end up failing so long as you are rooted.
[Verizon Samsung Galaxy S III] MrCapcom:
Sorry I did edit the post above. I did the auto installer and got this:

I am Rooted I'm running Synergy Rom
[Verizon Samsung Galaxy S III] crypted:
Lord, just do the copy/paste method?

It looks like your phone isn't mounted in USB debugging mode...
[Verizon Samsung Galaxy S III] MrCapcom:
Yup I tried doing that as well and the same thing. Now thing is I noticed a change when switched roms in Google Maps and before and after I flashed your patch. But when I go into Navigate its the same thing im in Virginia again and I have to wait a good 10 minutes for it to lock and correct itself.

Also at the top the gps icon doen't blink and says location set by gps dunno if that helps at all either
[Verizon Samsung Galaxy S III] crypted:
Did you read the Notes Section, or how about the post RIGHT above your first post today discussing "freaking awesome" locks and what that user had to do to get it to stabilize?

Come on now, I'm not paid here so I'm not going to put the gravy boat to your mouth.
[Verizon Samsung Galaxy S III] MrCapcom:
Thanks for your help so far and yes I did read and none of that works. Even followed the instructions in the second post under the OP still nothing. Only thing I haven't tried is this:

"IF you have issues with v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance."

The patch seems to work fine because my maps location is dead on vs it putting me blocks away with out it, but Navigation still won't work and I still stuck in Virginia. If above doesn't work then ill just go to stock and try getting a lock if that doesn't work I guess somehow my gps got borked and ill have to send for a replacement.

Once again thanks for the replies OP
[Verizon Samsung Galaxy S III] LLStarks:
Can I try that new test build? Is it the same as the not-so-hidden Test 3?

I'm getting the Carolina bug too.
[Verizon Samsung Galaxy S III] crypted:
For you, and anyone else who wants to test, try: http://derekgordon.com/gps-files/beta/Galaxy.S.III.Test.3.zip
[Verizon Samsung Galaxy S III] cell128:
I always had GPS lock issues. I flashed test 3 version on my gs3 and it locked instantly. Thank you very much for this I hope the fix sticks!!!
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Darn, I need to try Test 3 then. I've been running Test 2 all this time.
[Verizon Samsung Galaxy S III] BlackBytes:
Flashed test3 with CWM touch (Rom manager version). GPS lock in less than 2 seconds.

Good job op!
[Verizon Samsung Galaxy S III] Hulk0069:
Which file do I pick? Can't find test version 3
[Verizon Samsung Galaxy S III] FAUguy:
Its only listed 4 posts above you!

---------- Post added at 05:28 AM ---------- Previous post was at 04:58 AM ----------

I've been using the Test 2 for a while now, most recently over the past three days with the new J1 Jelly Bean leaked ROM.

Today I wanted to try the Test 3, disabled GPS, removed battery for a min, cleared cache and dalvik, installed the Test 3 zip in CWM, restarted phone and re-enabled GPS.

The TouchWiz Weather Widget thought I was in NC, not FL, and the GPS status app gave the wrong Lat/Lon. After 30 seconds the GPS did show the correct lat/lon and the Weather widget did show the right city and state. But an hour later when the Weather widget went to update, it again thought I was in NC.

I never had this issue with Test 2, so I'm not sure if there is an issue with Test 3 that is causing the wrong location to be reported?
[Verizon Samsung Galaxy S III] BlackBytes:
That's weird, it works fine for me on CleanROM 4.5.

All I did is reboot to recovery, mount sys and flash.
[Verizon Samsung Galaxy S III] crypted:
The only difference is the sensor timings for sampling. I had it modified to my own beliefs in proper figures in Test 2. But, I threw in original numbers in Test 3 which helped some.

All in all there two posts show that it's going to be a real ***** making a one size fits all patch for this device being that the various ROMs really seem to matter whether the sampling configuration should be stock or OP-optimized.
[Verizon Samsung Galaxy S III] FAUguy:
Even after flashing back to Test 2 from Test 3, I'm still getting wrong Lat/Lon in the GPS Status app, and the Weather widget still shows me in NC instead of FL. Maybe it has something to do with this new J1 leaked Jelly Bean ROM. But I had been using Test 2 with it for three days just fine until I installed Test 3.
[Verizon Samsung Galaxy S III] crypted:
Your caché will flush at some point. This is a cache issue.
[Verizon Samsung Galaxy S III] FAUguy:
Even though I went into CWM and cleared Cache, Dalvik, and Fix Permissions?

I ended up doing a CWM Restore of a backup I did on Thursday after the J1 ROM was installed. Even though the GPS lock takes longer now, it is saying my location and lat/lon is correct, not in NC.
[Verizon Samsung Galaxy S III] crypted:
I think I mentioned it in the Notes somewhere, but assuming that I did not, there is a special cache partition on the NAND that is inaccessible to clearing except for special scripts written for each specific device to clear them. They will flush normally within a day. Sometimes, doing the battery removal method for a short time will do it sooner.
[Verizon Samsung Galaxy S III] voodoomanx:
Why then would a device that has never been in NC suddenly be stuck in NC after flashing your fix now need to be flushed, unless the " fix" is causing the issue?
[Verizon Samsung Galaxy S III] crypted:
It's a version difference that I theorize could do this. But, it is abnormal and typically occurs where a fault exists in the ROM.

But hey tens of thousands use this and my experience should be enough to not need to defend the points so often.

XDA is boring me with this **** nowadays. Might hang up this hat...
[Verizon Samsung Galaxy S III] voodoomanx:
Lol 10's of thousands. Defend? If the "fix" creates a problem then its obviously the end user who didn't read the notes? And sure its the ROM...when I have never had a GPS issue putting me in NC until I flashed your "fix".