yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] buggerritt:
Well, no installs or updates. I used navigation flawlessly to get me to my destination and then after my appointment, I couldn't get a lock. I tried flashing it again and waiting. Nothing evolved. I restored a backup and it worked again. A couple hours later, nothing. Not sure what it could be.

Sent from my SCH-I535 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S III] crypted:
Have you considered faulty hardware?
[Verizon Samsung Galaxy S III] buggerritt:
I haven't ruled that out. I want to do some more testing though. I'll try an Odin flash back to straight stock official and see what's up. . I just restored a nandroid again and it's working fine. I don't get that.

Sent from my SCH-I535 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S III] crypted:
It might be that it overheats and creates bad data readings which become cached. Or, another glitch forces bad readings to cache. Hardware to software glitches can occur under various instances. If you use it a little bit, just like one or two seconds of readings, see how long that lasts.
[Verizon Samsung Galaxy S III] buggerritt:
I don't know. I just used navigation for about an hour and it worked great. It lost satellites a few times but switching over to GPS status brought them back each time. Before restoring, I made a backup of a clean flashed CleanRom 5.5 that could my get a lock. I just now shut down while having a perfect lock and restored that backup. It now gets a lock in seconds and it builds to lock 21 out of 21 satellites with 3m accuracy. I'll see how long it lasts.

Edit: I walked into a steak n shake for a minute. When I came out I tested it again. I started losing satellites (locking on 9 at the most) and the accuracy started fluctuating from 12m to over 100m and back down again. .

I give it a few minutes and try again. I get better readings but not the perfect 3m 21/21. Instead, it's like 9m and fluctuating from 12-19/22.

Sent from my SCH-I535 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S III] funnyperson1:
I think the "perfect lock" you were seeing with the AGPS patch was bogus results from something being cached on your phone. I'm not sure it's technically possible for you to lock on every single satellite that's visible and I imagine the GPS hw/sw is designed to stop trying to lock more satellites once it's reached max accuracy. When I first installed the AGPS patch the software showed an immediate "lock" with 0/0 satellites fixed and an accuracy of 0 meters. Then after it settled down a bit it actually started looking for satellites.

I think the 12-19 satellites and 9m accuracy is more typical of the hardware on this phone. I'm now seeing between 16-22 feet accuracy with like 9-15 satellites locked.
[Verizon Samsung Galaxy S III] buggerritt:
I beg to differ about the perfect lock being bogus cached data and here is why. I woke up this morning to having great GPS again. I did nothing further than what I had done yesterday. I had a lock of 17/21 satellites with 4m accuracy for the most part of an hour drive. I got out of my car and headed into campus to work for a while. I noticed, while inside the building, that GPS status was searching for a lock. I had backed out of it before exiting my car. I closed it with task manager and didn't bother with it anymore until I left, 2 hours later. When I got back into my car, I couldn't get a lock at all. I tried the entire hour drive home. I tried rebooting several times to no avail. When I reached home, I turned off all location services, cleared cache, data, and force closed GPS Status, Maps, and MapsServiceSamsung. I rebooted and turned on only standalone GPS services. I still got no lock. After about 10 minutes, I got 18/20 satellites with 3m accuracy again. WTF am I supposed to make of that? Did I lose GPS functionality because I was in an area that it was trying but unable to get a lock so it just gave up and died? I am definitely under the impression that is must be software related. Otherwise, clearing the cache/data of these apps would have no effect.
[Verizon Samsung Galaxy S III] buggerritt:
I hate to keep this dragging on but I found a "new" discovery (or so I think anyway). I just woke from a nap to find my phone with a notification in the bar that it was "searching using GPS". I pressed and held on the notification and then was offered the option of "App Info". I pressed and learned that the app that was searching for GPS was SystemUI. Evidently, it was unable to find GPS and GPS Status opened up on it's own in the task bar "looking for GPS Location". This is what was going on when I was on the campus and I didn't realize it at the time. I still only have standalone GPS services turned on. I also have gsiff_daemon renamed with .bak as a file extension (I did this after I got home so it doesn't matter if it has been renamed or not). It is going on for quite a long time, too. I finally force stopped it and was rewarded with my wallpaper being changed back to the default one from the ROM.

Why in the world is SystemUI calling for GPS? Am I the only one this is happening to?
[Verizon Samsung Galaxy S III] Tbenson:
What's really strange for me is that my wife's phone had great results two days ago but now its locking to the same damn coords up in Missouri while I'm down in south Texas.

So now both off the phones lock to that location. It has to be software related. Cm10, default kernel that comes with cm and agps patch #2.

Is there logs or configs that I could pull off our phones that could help identify the issue?
[Verizon Samsung Galaxy S III] crypted:
Just to be clear, I don't like CM or AOSP builds for your phone and many others. Your manufacturer doesn't provide driver trees so you could see problems from not using their drivers.

Next, I've been shocked to be told that there is no XML file for S3 gps like many new devices have. I would assume there's more than just a gps.conf file.
[Verizon Samsung Galaxy S III] xneuromancer:
Phone: Galaxy S3

FYI, I went back to stock jelly bean TW, flashed Galaxymod which is a TW based rom, and Maps and GPS has been pretty good, much better than last CM10 nightly I had on. The only issue I see, is that sometimes when first starting Maps and getting a "lock" it puts in North Carolina above Raleigh. After about a minute it finally updates to the correct location.
[Verizon Samsung Galaxy S III] crypted:
These reports of North Carolina originate from ROM's based on the official blob, correct? I'll repeat myself again on this... I really think there has to be another file somewhere with those coordinates as others report the same thing.

Case in point: the Asus Transformer Prime has another file called gpsconfig.xml which I further tweaked specifically for that device. In that file, there are latitude & longitude coordinates which point to a place in Georgia, USA. Some users would start out there and maybe never get a lock on the GPS and thus rely on other network services to move them out of Georgia. Anyway, I fixed the Prime's problem by modifying the gpsconfig.xml and the gps.conf.

So, there must be some other file involved here that no-one has found to provide me with.
[Verizon Samsung Galaxy S III] buggerritt:
Yeah. Mine kept starting me off in Ohio.

Sent from my SCH-I535 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S III] crypted:
Yes, but if you two are running two different bases, it could be that wherever the file originated is the difference of Ohio vs North Carolina for each of you.

Now the question is "is there such a file?" or what... Search the devices for any files called gps. Also if you have a robust file scanner, look inside files for <pos Lat= and xmlns="http://www.glpals.com/" to see if we can maybe find it should there be one and it doesn't follow a gps based naming convention.
[Verizon Samsung Galaxy S III] goldsmitht:
if this has been reported, i appologize and cite the search function as the culprit

well, here is a good one:

i'm on AOKP, 4.1 and went into the build.prop file, and it doesn't even contain the ro.ril.def.agps.mod= file at all.

so i am unable to edit that line, can i just "add" it in the file without causing a problem? and i appologize also if that is the intent of "edit the file"

so, any advice?

thanks!

edit: flashed my synergy nandroid, went into the build.prop file and walla, there was a r.ril.def.agps.mod=2 file, so changed it, and will see how it works now.
[Verizon Samsung Galaxy S III] xneuromancer:
I searched using total commander, an extract of galaxy mod rs10, across all files including archives.

"pos Lat=" no hits

"Lat=" hits in \system\bin\quipc_main ; system\framework\com.google.android.maps.jar/classes.dex ; system\framework.jar/classes.dex ; \system\lib\libinput.so ; \system\vendor\pittpatt\models\detection\yaw_roll_face_detectors.6\head-y0-yi45-p0-pi45-r0-ri30.4a-v24\full_model.bin

glpals = no hits
[Verizon Samsung Galaxy S III] m_s_ifland:
With all the problems that people have with this issue, this topic should be stickied.
[Verizon Samsung Galaxy S III] crypted:
Is that definitely like stock rom?
[Verizon Samsung Galaxy S III] brandonrossl:
I just had that happen to me with the 2nd newest cleanrom lite with no gps fix.

Took a half hour for it to star finding me again and another half hour to stop lumping around like a lunatic.
[Verizon Samsung Galaxy S III] justinglock40:
Which do you think would work well with the new galaxy note 2?
[Verizon Samsung Galaxy S III] crypted:
Generic, Google 3.1 No-SSL. Don't use files designed for specific devices on devices that aren't what it was meant for.

Please don't respond here for support on the matter, this thread is for a different device. Message me if you have issues. All NOTES in this thread will apply to your device.
[Verizon Samsung Galaxy S III] xneuromancer:
I believe so, it's based on the VZW I535VRBLK3 jelly bean build.

I extracted the default VZW I535VRBLK3 image that I have (.tar.md5) but it contains everything wrapped up in .ext4 files which WinRAR can't work with. I tried http://www.diskinternals.com/linux-reader/ but it won't let me browse the mounted images. think i'm stuck at this point.
[Verizon Samsung Galaxy S III] funnyperson1:
The .ext4 files are probably filesystem images, it should be easy enough to mount and browse them in linux if that's what they are.
[Verizon Samsung Galaxy S III] Tbenson:
Here is a quick filename scan for GPS.

This is from CM10. No additional apps but maps and a terminal client.

I can pull these files but I don't know how much of a help they would be. Also I'll Odin back to unrooted stock and root it, then do a scan and pull any files for you this weekend.

find / -name gps*
/system/etc/gps.conf
/system/lib/hw/gps.default.so
/system/lib/hw/gps.goldfish.so
/sys/devices/platform/sec-battery/power_supply/battery/gps
/data/misc/gpsone_d

---------- Post added at 05:18 AM ---------- Previous post was at 04:55 AM ----------

Also just want let you know that I'm currently searching for those string you mentioned across the entire device.

And for those who want to do the same, we already have a robust file scanner, grep :).

You can either connect your device up and get a adb shell or install a terminal emulator and run the following to search within the files for the string specified by crypted. I'm using adb shell as its easier to type on the computer :)

grep -r "STRING_TO_SEARCH" /DIR_TO_SEARCH > /sdcard/filename.txt

For example I am dumping the following out in files, if anything shows up I'll email them over to you crypted.

grep -r "<pos Lat=" /DIR_TO_SEARCH > /sdcard/posLat-CM10.txt

grep -r "glpals.com" /DIR_TO_SEARCH > /sdcard/glpals-CM10.txt

Thanks for you help trying figure this out. Again I'll do the same above on base stock if no one gets to it before me.
[Verizon Samsung Galaxy S III] Tbenson:
None of those strings show up my phone running cm10. I'll Odin to stock tonight and do the same
[Verizon Samsung Galaxy S III] BHermes21:
What is everyone running on the GS3? What test file and stuff? I am really confused... Sorry
[Verizon Samsung Galaxy S III] Tbenson:
Ok on stock jellybean latest ota, fresh odin (I535VRBLK3)

find / -name gps*
/system/etc/gps.conf
/system/lib/hw/gps.default.so
/sys/devices/platform/sec-battery/power_supply/battery/gps
/data/misc/gpsone_d
/date/misc/gpsone_d/gpsone_loc_api_q
/data/misc/gpsone_d/gps_loc_api_resp_q

And the string "pos Lat=" is not showing up anywhere under /etc. Would it be in any other directory that etc?
[Verizon Samsung Galaxy S III] Tbenson:
Well I finally got a lock on mine and my wifes phone. :)

My phone:

Latest stock baseband (BLK3)

CM 10.1

aGPS patch 3 alt with the build prop edit for ro.ril.def.agps.mode =1

Wifes phone:

HE baseband

CM 10.1

aGPS patch 3 alt with the build prop edit for ro.ril.def.agps.mode =1

The only difference between last week really is now we am using an unofficial build of 10.1 cm from aerovan. Maybe it was just a CM 10 issue?

One note is that I never get a lock unless I open navigation open then wait till I get a lockm then other apps will lock (maps, c:geo). I have to do this everytime, weird but I will take it. Now I can finally get those geocaches I been needing to get.
[Verizon Samsung Galaxy S III] crypted:
Sorry for being out of pocket.

I have several confirmations on CM 10.1 or whatever working whereas CM 10 always failed. These were from uses with less than 10 posts so they couldn't post on the S3 threads.
[Verizon Samsung Galaxy S III] EGill42:
CM 10.1 paired with patch 3 alt seems to work for me as well. Just curious, where did you find the ro.ril.def.agps.mode =1? In CM 10 I searched for the it the build file, but couldn't ever find that line.
[Verizon Samsung Galaxy S III] Tbenson:
I added per the notes section on Page one. AOSP ROMs don't have that line
[Verizon Samsung Galaxy S III] EGill42:
That explains a lot! So would it be something I would manually need to add? Or since it is not there, don't bother?
[Verizon Samsung Galaxy S III] Tbenson:
I added b/c without it I couldn't get it to lock and the notes mentioned to add it if you are having a problem. If you are not sounds like you are fine without it.
[Verizon Samsung Galaxy S III] brandonrossl:
Have been having hellacious spontaneous GPS issues on CleanROM (vrblk3 based) with matching radio and rpm.

Currently wiped ALL data, system, internal sd, cache etc (except for external SD) and am:

-mount system

-flashing GPS fix 3 alt

-flashing modem and rpm

-flashing Cleanrom

Will report back, have CWM recovery, newest version as of writing this.

Add:

-chose not to restore from google, but to backup to google from now on (to reduce past problems coming back from the dead)

-Updated apps w/o opening any

-Rebooted

-Opened maps

-gps blinks but no fix

-downloaded and opened GPS Test (doesn't futz with settings)

-Zero satellites, zero signal on anything

Had a tingle the combined RPM and modem package was at fault, re-downloading them from here:

http://xdaforums.com/showpost.php?p=30195492&postcount=2

no dice

Will flash and report back.

Next Step will be flash these two:

http://xdaforums.com/showpost.php?p=34400206&postcount=4

Flashing....

Success!

Multiple satellites, good fix, FAST fix.

Impressions: avoid combined rpm modem flashes

Avoid vrblk3 modem and rpm. The link before 'no dice' has a mis-named modem (vrlk3).

Don't know if it matters, but it did for me.

I've been having 3g issues all day (has been on 1xrtt) and my 3g is now restored with the vrblk1 rpm and modem.

SO note to those having issues, try the bold linked rpm then modem.

I'll report back with any more issues.
[Verizon Samsung Galaxy S III] nbaj2k:
I assume this is in regards the following note from the OP?

13. Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.

I was under the impression that this would only help if that line was already in your build.prop file, then you could just change it to =1. Wouldn't the ROM have to be designed specifically to look for that line? I didn't think that just adding something like that could make a difference (I'm new to this, so I apologize if I'm incorrect).

~J
[Verizon Samsung Galaxy S III] jknolls:
Thanks!

To the person who made this patch: THANK YOU! You're a genius! I used alt 3 zip and my GPS performance is off the charts now. Many times I'm getting instataneous locks (even indoors). Samsung and other phone companies need to incorporate your patch into their software and pay you royalties for it! Thanks again.
[Verizon Samsung Galaxy S III] Dr. Light:
anyone got the stock VRBLK3 leak GPS files?
[Verizon Samsung Galaxy S III] p-slim:
Actually the S3 can do much better than that, I often have 3 or 4m locks.
[Verizon Samsung Galaxy S III] ben7337:
I'm not saying the s3 can't. I'm saying that mine can't, and accuracy of gps lock should have absolutely nothing to do with the hardware, it is purely software as far as I am aware.
[Verizon Samsung Galaxy S III] tech.kyle:
Just a quick background story, original symptoms were that I could stand outside all day and it would never connect. Tried the "Clear Location Framework Services cache and reboot" trick and managed to sometimes sort-of get a lock after 60-ish seconds outdoors. Wiped my phone to stock with root patch with no change and am now trying this.

I first tried the "Galaxy S III Test 3" version of this patch and was shocked when it did an indoor lock in 2 seconds. Woah! That's incredible! Well, too incredible, it seems. GPS Status claims there's a lock with 0 foot accuracy in 2 seconds, but with 0 satellites in use. Getting absolutely zero signal from any satellites. In fact, it seems to think I'm in California. It's obviously not a true lock. I've left it open for 10-ish minutes and there has been no improvement.

Next up, "Galaxy S III Test Alt". No insta-lock on first run. That's a good sign. Seems to have more satellites "in view" than previous patch. Let it sit for 10 minutes and no lock. Seems to have gone back to how it was before.

Third time's a charm? "Download the Google Specific v3.1" this time. 25 in view, 2 second fix, no satellites in use. Hardware problem? I'll try more at home.
[Verizon Samsung Galaxy S III] niv3d:
Anyone have any ideas on some more gps fixes? I have tried pretty much everything lol. I can't get a lock for anything :/
[Verizon Samsung Galaxy S III] crypted:
Notes.
[Verizon Samsung Galaxy S III] ben7337:
Many of the fixes have this 0ft lock bug where they don't lock on to any satellites, but claim to have a lock, where the status bar icon stops blinking and locks you into some incorrect location. Some apps which use your cell tower location info may still show your right location though. This is why google maps shows you as in one spot, but if you switch to navigation with a bad fix, it will place you somewhere else, many others posted that it put them in NC, which mine did as well.

Also for my phone only 3.1 alt worked. 2 and 3 non alt had the 0ft bug as did 3.1. I don't remember what 2 alt did, but it didn't work. 3 alt works sometimes. The first lock may not work, try pulling the battery for a minute and turning the phone back on. Be patient, It can take up to 10 minutes. See how that goes. If it still won't lock, wait and try again another day. So far I've found I can get a lock in 30 seconds to 5 mins with this 3 alt fix for the gs3, none of the others worked, not the google 3.1 standard, not the 1.3 worldwide, not any of the other gs3 specific fixes. I think we need more gs3 specific ones though.
[Verizon Samsung Galaxy S III] socalwrx:
Alright so Ive had gps problems since day one when I got the phone on launch. Just now have I researched fixes and have tried just about everything! (chronological order)

-problems since day 1 on ICS (sometimes it worked, most of the time it didnt)

-rooted/unlocked to flash leaked JB

-tried battery pull and took off case

-then flashed test 3 fix. It locked me into northern CA right on the border of NV (I live in southern CA)

-full wipe/clear cache and flashed latest cleanrom w/ stock kernel.

-flashed test 3 fix again (still put me in that weird location

GPS test shows 26 in view / 0 in use.

I mean, this has to be faulty hardware? guess i should look into a replacement :/
[Verizon Samsung Galaxy S III] mmalkin:
I'm having this exact same issue and also live in SoCal. I wonder if this is a coincidence...Got my phone in the mail from Verizon when it came out, so would be surprised if it's a "bad batch" of early failing. Maybe it's a modem issue? On LK1.

Edit1/8/13: GPS is finding satellites now. Had as many as 8 or 9. Not necessarily locking quickly, but getting distance within 30 meters.
[Verizon Samsung Galaxy S III] Gervin:
I tried this with Test Fix 3, and it locked right away..... 1000 miles away.

My phone permanently thinks I'm in NC... only in 2 GPS apps, and the rest won't lock at all.

So I assumes it was the AGPS data which I wiped. No luck.

I even tried

I'll reflash another fix and keep trying until one works, or until I toss my phone out the window.

Why won't s**t just WORK!!!
[Verizon Samsung Galaxy S III] p-slim:
Once gps breaks there is no fix except to get a new phone
[Verizon Samsung Galaxy S III] lohp75:
Has anybody tried to just go into manage apps /maps and cleared data. Then open maps and it should lock almost instantly. :)
[Verizon Samsung Galaxy S III] niv3d:
Mine is on the way. Now my only fear is if it does work better or at all, I hope GPS doesn't break between flashing etc...
[Verizon Samsung Galaxy S III] dansan382:
i think this is what is happening to a friend of mines phone. she told me a few weeks ago her GPS just stopped working. she had an older version of AOKP from back in september so I reflashed CleanROM on it and still doesnt get a lock. nothing i was doing worked and i was so confused. didnt try any of these fixes as i had no idea about this issue and her GPS still doesnt work.

is it safe to say she needs a new S3?
[Verizon Samsung Galaxy S III] brandonrossl:
Flash a matching rpm and radio and retry, don't do a vrblk3 radio.
[Verizon Samsung Galaxy S III] dansan382:
i dont see her very often so i wont have a chance to try things. figure ill just tell her to have verizon replace it.
[Verizon Samsung Galaxy S III] Gervin:
Gps dead - replacement

So after a long discussion with a Verizon tech, who was very cool about custom ROMS, he told me the following:

Many people with the Samsung Galaxy are indeed having GPS issues rated to the chip itself.

The phone will work flawlessly for a while, and then GPS will stop.

No software patch or troubleshooting will repair a phone with this issue. Nothing but a replacement.

(That's not to say that some GPS issues are indeed software related, but that's it's known there was a bad production run).

The good news, Verizon will quickly replace a phone after they do the troubleshooting steps to make sure it's not a AGPS issue.

The bad news, as they send out refurbished phones, there is a chance you will receive another defective phone.

Which is really a pain in that the ture of the defect may not show up for some months (as many people with GPS issues had no trouble for a while). I'm thinking it's a bad solder or something on that production run that a bump will loosen.

What I'd like to know, and have been searching for, is if anyone has any idea what serial numbers (or range thereof) are affected.

That way I could check the refurbished unit to see if it's in that production run.
[Verizon Samsung Galaxy S III] Hypnosis4U2NV:
Re: AGPS Patch Galaxy S III 3.1 & 2.2 | NEW SIII SPECIFIC BUILD | Tentative Support

Samsung has historically continued to push out crappie radios since the first Galaxy S.. The S3 behaves exactly the same way my Fascinate did with its GPS.. They had plenty of chance to get it right, and at this point, I doubt they ever will.

Sent from my Commodore 64..

READY.

load"*", 8,1