yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] crypted:
Again, and I keep repeating this to S3 people for some reason, CM is mentioned in many posts and directly in the Notes Section.

CM does not always work with GPS because it does not actually have the S3 drivers to incorporate into the code to ENSURE it works. Also, the Nightlies and other releases sometimes have the GPS borked within the code itself.

I do not fix broken source code, ROMs, or hardware. This means you need to consider a different ROM if GPS matters to you.

Read my above responses today and yesterday. Again people, just do a LITTLE reading. It will prove your reading comprehension and direct you to the same conclusion of ROM issues.

Very few people donate, but many people like to BlTCH about everything being messed up without even trying to logically resolve it themselves. Maybe if it were a paying gig I'd be nicer... Hmm...
[Verizon Samsung Galaxy S III] nbaj2k:
I apologize. I'm on the bus headed for NYC and just realized my phones gps wasn't working and was scrambling trying to find a fix. (not an excuse) I completely missed your notes section referring to Cyanogen ROMs. Going to try to switch to a different ROM and give this a try. It looks like this is working for a lot of people, keep up the great work!
[Verizon Samsung Galaxy S III] monkeyhihi:
I took the advice of what you listed here, and I tried using both CleanROM 4.5 and Synergy ROM r112, yet none of those work either.

I've tried: Removing the battery for 30+ seconds; Disabling GPS, rebooting, enabling GPS, rebooting again; Using both the Test 3 and the Test 3 Alt Patches; Waiting 10+ minutes with the Test 3 and Test 3 Alt patches on both CleanROM 4.5 and Synergy ROM r112. I'm at a loss here of what I could try doing since I've READ ALL OF THE NOTES but nothing there seems to help.

edit: the only other issue I can think of is the GPS cache issue where it needs a certain amount of time to reset on its own, so I guess it's time to play the waiting game...
[Verizon Samsung Galaxy S III] crypted:
It's either that or it's hardware related so long as you do not have any other apps installed that "assist" GPS like FasterFix.

Your testing shows that the patch is irrelevant to fix a borked issue that is outside of the ROM.

If there are any scripts like Superwipe or Fullwipe for your device, that might clear the cache partition you reference. Don't use those scripts from other devices as your NANDFLASH partitions are most likely different.
[Verizon Samsung Galaxy S III] Scblacksunshine:
I have had the same problem as you and eventually went back to JB leaked stock ROM and GPS so far is working flawlessly. Just did another test an hour ago, went outside and got a lock in 15-20S with error ft at around 20. Navi will pick up right away too..I too thought my GPS hardware might be the issue but if that's the case it shouldn't be working on a stock ROM either and this is without using this patch. Perhaps there's a GPS driver change in both ClearnROM and Synergy, maybe not intentional but another file conflicts with the GPS driver. Anyone know the actual file name of the GPS driver ? (not GPS.config) What I don't get is, with the same S3, how come some people's GPS is working perfect on Clean or Synergy and there are people like us that struggle with the same ROM?
[Verizon Samsung Galaxy S III] crypted:
Second post is updated to include more information pertinent to GPS resolution on the S3. If you're still having problems, have a go at this. It's confirmed to work for a number of others.
[Verizon Samsung Galaxy S III] p-slim:
Test 3 zip and post 2 instructions fixed my S3 gps not locking issue on CleanROM 4.5
[Verizon Samsung Galaxy S III] buggerritt:
Test 3 and post 2 also fixed my GPS on CleanRom v5. Locking on 20 satellites with 3m precision again.

Sent from my SCH-I535 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S III] npompei:
Holy crap! Installed on my S3 with Clean Rom 5.0 with delayed GPS. Installed S3 zip#1 and it locked in less than 5 seconds! Whew! Thanks man!
[Verizon Samsung Galaxy S III] kimsj756:
Mind telling me step by step what you did? Tried but no luck... Thanks.

I'm 180 miles away from where I am.

More info might help...

I'm on clean rom 5. On maps app I'm right on my place. But when I try navigating, I'm 180 miles away from where I am. And no navi works.
[Verizon Samsung Galaxy S III] crypted:
Did you read the second post of the thread? Did you follow its details step by step?
[Verizon Samsung Galaxy S III] kimsj756:
Mind explaining how to flash back to stock unrooted?
[Verizon Samsung Galaxy S III] crypted:
Seriously? You really failed to follow the instructions and did not make a backup of your original ROM which almost all ROM threads recommend you do?

Come on people. Let's educate ourselves at least just a tad bit before diving into the realm of rooting and all this jazz.

Why don't you search your device information for an update blob to flash back to the unrooted ROM if that is possible for your device? Seems logical...
[Verizon Samsung Galaxy S III] kimsj756:
Little confused.. How do you make a back up if you aren't rooted in the first place? Look, I understand why you are so frustrated, but I have my points too. Been rooting my devices since 2010, and what's wrong about asking about going back to stock unrooted? Never felt the need to go back and am asking now.
[Verizon Samsung Galaxy S III] crypted:
This topic is for aGPS Patch. This is not for device specific chatter. Start a thread of your own in the QA section of XDA of you're want... Better yet, read the stickies and FAQ sections as your questions are usually already covered.

Please don't flood this thread with unrelated discussion nonsense...
[Verizon Samsung Galaxy S III] kimsj756:
Okay got it. Sorry about it. I also wanted to find out what the guy of the previous post did because, from the post, it seems like he didn't have to flash back to stock because he said it worked on cleanrom 5. So wanted to find out what he did. Any idea?
[Verizon Samsung Galaxy S III] user32:
Because it took an extremely long time to lock a location and the fact the fact it was pretty far off when it did, I decided to intsall and test both patches. (Galaxy s3 on JB 118 build)

Original Test SIII

As prescribed I followed the steps and everything appeared to work as stated. Initial lock took about 7 min as suggested and evrything after that locked within seconds and accurate might I add. And maybe I needed it to settle in a bit more but i noticed that the first lock after restarting my phone will take 5-10 minutes to lock and lock instanaeously any time after that.So all is well unil i have to reboot my phone.

So I try the alternate patch

i tried to to follow the installation as prescribed but I had issues trying to get the initial lock when just turning on the GPS location only. So i manually put a start point(my city) and some random end point. It took 15-20 minutes to lock and took anywhere up to 2 minutes to lock after that.

So i reverted back to the original test sIII and I'm gonna sit on awhile and see if it improves over time. Eiter way I'm still better off with the patch.

Great work crypted!!!!
[Verizon Samsung Galaxy S III] blackguy101:
Ok so im trying to get a lock on V5 of cleanRom. So far it actually detects my general area when I go into navigation but still says searching and wont actually lock. Should I flash to a different patch? Or would it work if I were to actually go outside and test this out?

Edit: Ok So I went outside to test it out and it locked on in about 2 minutes and after that it was instant!
[Verizon Samsung Galaxy S III] buggerritt:
Howe did you flash this of you weren't rooted?

Sent from my SCH-I535 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S III] Kjennings15:
so.... if a Rom's build.prop is missing "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0", is that a bad sign? I've read and tried everything, except for switching Rom's or reflashing stock. I'll find a solution eventually, doing one of those things probably, but I am wondering if that's a give away that the gps on the rom is whack.
[Verizon Samsung Galaxy S III] crypted:
I'm unsure as no reports have been made either way for this device.
[Verizon Samsung Galaxy S III] Kjennings15:
I had no luck with this patch running liquidsmooth rc9 on d2vzw. It landed me permanently in North Carolina. I wiped settings and stuff, flashed some more, wiped some more, battery pulled.. Etc. I gave up. Then, walking to campus this morning and changing music in g music, gps status showed on my status bar and locked 11/18 haha.. Navigation and maps locked in seconds. We'll chalk this up as a win. Thanks!
[Verizon Samsung Galaxy S III] crypted:
Yeah, cache clearing issues on that hidden partition it definitely sounds like...
[Verizon Samsung Galaxy S III] storm81456:
Crypted, have you noticed the frequent reports of folks where their GPS defaults to them being somewhere in NC prior to getting an actual lock? Any ideas about why that might happen? I've seen it mentioned several times in this thread by different folks.
[Verizon Samsung Galaxy S III] crypted:
Honestly, without more information I couldn't deduce it.

However, on an older device there were a few of the same issues where the device was getting its location by the actual spot where the mobile network fed into the normal internet. So, a few users from around the USA were coming out of Houston, Texas if I remember correctly. Again, this was over a year ago. The solution on that device was exactly what I did in the "ALT" patches above.

Typically, you can get improper locations where the device doesn't actually process aGPS data at all. Rather, it uses the other location settings normally because of ROM issues.

Another thought is this... There could be an XML or other configuration file that I haven't been provided with. That file would have standard base coordinates that somehow ROM's keep defaulting to instead of using aGPS. Case in point, ROM's for the ASUS Transformer Prime were botched and defaulting to Georgia as the coordinates in the XML file were set to as a base point.

Again, from what I've been told there is no XML file for the S3 which I find perplexing.

From the above, I would be willing to bet that it's a problem like the ASUS one rather than the older device issue. But, users reported their problem went away with the ALT version which makes this a weird situation to deduce.

Others took my advice and waited patiently for their cache to clear. Things worked great with this patch once the cache on the hidden NAND partition finally flushed...
[Verizon Samsung Galaxy S III] EGill42:
I am on the newest CM10 nightly, and with the 3rd patch I am able to get a decent lock according to GPS Test; within 100ft. With an older nightly paired with a different patch I was getting within 20ft. In spite of GPS Test showing a lock, Google Maps will always say waiting for location.

Sounds like CM10 just won't work well with the GPS.
[Verizon Samsung Galaxy S III] hank3fan:
Be patient and you'll get a lock after 5 minutes or so then you should be good after that
[Verizon Samsung Galaxy S III] crypted:
Drivers... Yeah probably not. Reinstall Maps.

EDIT: As also stated just above my reply, it does take time. I figured you read my Notes Section which discusses waiting and that we already worked out everything possible. Do read the information I provide. I didn't write for the fun of it.
[Verizon Samsung Galaxy S III] EGill42:
I defiantly read through the notes, and appreciate you taking the time to write them. I recently went back to the stock unrooted rom the phone shiped with the other week, and was getting locks right away within 30ft. Although, I did have to have the Google Location Service box checked. Without I it believe Google Maps would also endlessly say waiting for location. It wouldn't even approximate me within the United States.

Google Maps should work just using agps, and not their location services, right? I might need to go back to stock to confirm if it is a CM issue like most people are having, or a hardware one....I just realized that made no sense. GPS Test shouldn't even get a lock it it were a hardware issue.
[Verizon Samsung Galaxy S III] crypted:
Try another ROM. That's logical. Nandroid backup...

aGPS is assisted GPS and requires a data connection. Google's Location Services uses WiFi and other non-GPS systems to get a general approximation.

This patch, if working properly, would permit you to be within 10ft not 30ft.
[Verizon Samsung Galaxy S III] EGill42:
Good to know that the patch isn't really working for me. I am going to give CleanRom a try, and see what I think. I defiantly prefer stock android looking roms, but perhaps the stability of a TW based rom will win me over. It looks like nearly all the AOSP roms out their are based on CM10, so they will probably have the same issue.
[Verizon Samsung Galaxy S III] mds96:
I'm running Hilbe's latest Unofficial AOKP Unstable 4.1.2 build. Here is my experience and issues with GPS. I couldn't get a lock at all, so I flashed Test 3 Alt, and I still wasn't getting a lock. So I went through the instructions and did the shut off GPS, reboot, wipe cache/dalvik, reboot, enable GPS, reboot, and then I got a lock instantly! Now for my problem! No matter if it's Maps, Navigation, or GPS TEST, I will constantly lose GPS signal. It will usually relock, but it just loses and gains signal non stop while driving. Have any suggestions on what I can try? I really don't want to go back to stock and start all over, but if that's the only fix, then I'll do it....lol
[Verizon Samsung Galaxy S III] crypted:
It sounds like it's either hardware related OR bad drivers that continually relock rather than reparse incoming location data.

If you're still using Test 3 Alt, go to Test 2. Test 2 gives OPTIMAL performance. Assuming your issue was not following the series instructions in the first place, then Test 2 should work...
[Verizon Samsung Galaxy S III] EGill42:
When I got home I installed CleanRom. I have found the closest to working result with Test 2. It locks me right away, but way in the wrong location. I am along the coast, but it puts me on the border of California & Nevada. I used GPS Test to check it out, and got good quick locks for a bit, then it wouldn't. Now it won't leave the border location.

And I have tried the battery trick, the rebooting and clearing cache tricks, and anything else I could find.
[Verizon Samsung Galaxy S III] crypted:
And in post #2 of the thread... You did that exactly as outlined?
[Verizon Samsung Galaxy S III] mds96:
Nope I did follow the instructions. Been using this ever since the first test. After messing with it this morning I got the best results I've ever had as far as satellites and accuracy. At one point I was 13 out of 13 and withing 10 feet. So I'll test Nav later, then if I still have issues I'll try Test 2. Thanks for the reply and I'll report back after the tests!
[Verizon Samsung Galaxy S III] xneuromancer:
What is the relationship between gps test and Google maps? gps test reports about 10 satellites locked on, but Google maps still is off by 4 or 5 blocks and sometimes the pointing in the wrong direction.

I have a galaxy s3. I've tried the s3 test 2 and test 3 zips so far.
[Verizon Samsung Galaxy S III] crypted:
I don't know about GPS Test, but assuming it is equal to that of GPS Status, it reports direct data from GPS location. GMaps uses GPS/aGPS, network, and tower based assistance. Further, GMaps has application libraries for processing such data. Therefore, it could be off based upon how GMaps receives and handles that information.
[Verizon Samsung Galaxy S III] xneuromancer:
I tried gps status and that looks good too.

Does anyone know of anything I can try to improve my google maps accuracy?

I just tried the map quest app and after a few minutes it was accurate to 10 yards which is much more accurate than g maps. I guess this confirms its not a hardware issue.
[Verizon Samsung Galaxy S III] crypted:
Again, it's the specific apps libraries so Google is your entity to ask. However, only some ROM'S have issues with GMaps so doubt they'll care.
[Verizon Samsung Galaxy S III] jeffnucci:
Running CM10 stable and the Test 3 on the specific builds got me a lock in 2 seconds after having GPS problems on AOSP ROMs.
[Verizon Samsung Galaxy S III] xneuromancer:
i flashed back to jelly bean vzw stock, and maps was working correctly using GPS only. must have been an issue on my last ROM.

I really don't like the touchwiz based roms, so I'll have to play around more with AOSP to find something that works.
[Verizon Samsung Galaxy S III] crypted:
Most likely, you will have issues with ROM's that do not use S3's original ROM as a base. This is because the drivers will be generic or ripped from other devices that have open-source driver configuration trees. This isn't like Windows. Drivers are actually compiled into the ROM and kernel at the time of creation. You cannot just them swap out...
[Verizon Samsung Galaxy S III] buggerritt:
It doesn't get any better than this. This is after flashing test 3. It took about aan hour to settle but once it did, I was on track again.

Sent from my SCH-I535 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S III] Tbenson:
I can not figure this out. My wife and I have the same models. Running the same rom (CM 10.0 stable).

For my wifes phone, I rooted, flashed cm 10, then I flashed the test2 patch and modified the build.props to include the ro.ril.def.agps.mode=1, and bam works like a charm. GPS status shows multiple locks and it works great.

I performed the same actions on my phone and for some reason it keeps locking on somewhere in Missouri off state hwy 96 (37 degrees 11.097, 94 degrees 4.780). I'm in south Texas.

I have performed multiple clean installs (wiping all partitions) but no matter what it keeps locking up to that same coords. I have tried test 2, test 2 alt, test 3, test 3 alt with all clean installs and it still keeps going to that darn address.

Last resort I wanted to go back to stock, (I am on basebase VRLHE) but scottsroms link to the stock rom http://xdaforums.com/showthread.php?t=1941334 are no longer working. Anyone have a link for the VRLHE base stock?

I only use the gps for geocaching and I just found out this weekend that my gps is no longer locking properly :(

Any help or link to the stock rom is appreciated

POST EDIT

I also want to mention that while its says it locks to that coords, the fix/sats # always shows 0
[Verizon Samsung Galaxy S III] crypted:
Okay, so let's first think this through with your EDIT notation. Your GPS is not working AT ALL. Your location is being provided through other location methods which clearly is wrong AND/OR your cache is corrupt. But, your GPS most definitely IS NOT functioning. That was simple.

Now, let's go further. Did you do Note #26? Did you follow the guide for fixing issues with the S3 particularly in the second post on this thread???

Lastly, cache may take a few days to clear out. Yes, this sucks but that's your device and its the way it handles hidden NANDROID GPS cache partitions. A user right above you posted something you should re-read and consider. It took 24 hours before it worked for him.
[Verizon Samsung Galaxy S III] Tbenson:
Crypted,

Thanks for the quick response. And I want to thank you for your work b/c it did indeed help my wife sg3 after I installed patch #2 and edit build.props with the agps property.

I did read, all of post #1 and #2. Below is an overview of what I have done. I have tried with each patch. (Patch 2 seems to have the fastest lock but again its not showing right location).

Is there a way to force the gps cache clean? Such as under the tools menu of gps status?

Here is all the steps that I have done.

Started with a fresh install of CM10.0 (Wiping all partitions, user, system, cache, davlik)

Booted it up.

Went to location settings and enabled only gps, did not check the google locations

Opened google maps. Never locks

Opened gps status, never locks

Started with patch #2, by rebooting into recovery, mounting system, flashing patch, clearing cache/davlik.

Boot up.

Start gps status, never locks.

Modified build.props, restarted, clear cache, etc

Boot up, this time it locks but the coords are showing up in missouri.

I have repeated these steps with clean installs each time for each patch # but i can't get a proper lock.

I also tried clearing the framework, pulling the battery, etc as indicated in post #2.

I wanted to flash back to a stock rom just to rule out any rom but I can't find a odin tar, when I was on stock months ago it worked fine. I'll post over in the right thread for that.

Meanwhile I'll just flash CM10 again cleanly (formatting everything) and flash patch #2 and will let it sit overnight and see what happens.

Again I only using it for geocaching so I'm not in dire need to get it working until next time I go looking for some caches.
[Verizon Samsung Galaxy S III] crypted:
There are many reasons why the hidden GPS cache can corrupt and be problematic. And, there's no way to clear it unless someone manually determines which partition it is and creates a script or instruction sets for it. However, clearing this is very risky because you start screwing with the hidden NANDFLASH partitions and not just the boot, system, data, cache one's that you have visible. You can easily brick it.

My old Transformer took about three days to clear once. It went bonkers from a ROM swap. Eventually, it was back to business and worked 1000x better than before...with my patch of course.
[Verizon Samsung Galaxy S III] Scblacksunshine:
For people that have used this patch and GPS is still not working, I have a suggestion for you. Call Verizon or send the phone back for warranty service. Like many on this thread, I have tried to get GPS to work on numerous tries, different ROM and even back to stock...while I see certain level of success from time to time, most often the GPS on my phone was still inaccurate and sometimes it won't lock at all. Anyway long story short, got a replacement phone and let me tell you performance on GPS is night and day. So sometimes you might have bad hardware and unfortunately there's no real clear cut way to test that until you compare it with another phone. Now I can get a lock in under 10 secs even without this patch and accuracy usually within 10-15 ft...never before was I able to do this even with the patch...so if hardware is the culprit, nothing will help.
[Verizon Samsung Galaxy S III] Tbenson:
Thanks again man.

Gotcha on the hidden partition, I'm just going to do a clean flash and apply patch #2. And then just sit on it for a few days. :)
[Verizon Samsung Galaxy S III] Blaiser47:
SGIII Test 3 regular worked like a charm for me. On AOKP JB Milestone 1. Wasn't having major issues before, but now the lock is super quick and far more accurate. I did as the user on the second post did (as stated in the notes), disable all location services, power down, pull battery for 30 sec, reboot into recovery, then wipe cache, dalvik cache, then mount, install zip, rebooted and all was good. Thanks!
[Verizon Samsung Galaxy S III] buggerritt:
After my initial great results, a few hours go by and I can't get a lock anymore. It's really odd.

Sent from my SCH-I535 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S III] funnyperson1:
I don't want to jinx myself but so far test 3 is awesome. It used to take like 5 minutes to lock and now it's a second or two.
[Verizon Samsung Galaxy S III] crypted:
With or without a case?
[Verizon Samsung Galaxy S III] buggerritt:
Either/or. I'm on latest JB Leah with latest CleanRom and latest radio/rpm.

Also, this same TPU case has never made a difference before. I don't see why it would start now.

Sent from my SCH-I535 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S III] crypted:
What was done between the time it worked and stopped working? What updates, what actions?