yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] crypted:
I ponder "slower" being because it now relies on aGPS and GPS data. A lot of ROM's or even stock setups will default to WiFi or tower triangulation at first. If it's going straight to GPS, you'll notice a slight lag.

I find it worth using aGPS/GPS only because tower triangulation and WiFi data has sent me for a loop around the world a time or two. I traveled about 5,000 miles in all sorts of directions in less than twelve hours one day when I reviewed my Latitude data. Actually, I was only traveling around Oklahoma City...
[Galaxy S III Android Development] Tectas:
Sry, but no, only used gps status toolbox to check the time and count, or do you mean it uses network location provider to get the correct satellites faster?

Edit: read a bit about the difference of agps and gps, doesn't the usage of agps mean the current position is acquired by pairing tower triangulation with basic gps signals?
[Galaxy S III Android Development] crypted:
Not what I meant...

On our phones, aGPS is two tiered. The big one, which I resolve, is based upon almanac data and specific time calculations with a mixture of variable modifications to obtain the optimal result from GPS satellites rather than relying on cellular towers and/or WiFi a majority of the time...which is what our devices do typically.
[Galaxy S III Android Development] myname70:
why you need this app at all? does someone has problems with the GPS on SGS3? I lock to 13-16 sattelites within couple of seconds. some of them arw GPS some GLONAS. perfect lock inside the building... without any patches
[Galaxy S III Android Development] crypted:
Then don't use the patch? This was silly to even post as you assert no one needs this when users asked me for it here. I don't go supporting devices randomly...

So good for you. But others need help sometimes for varying reasons.
[Galaxy S III Android Development] Thyrador:
works on my international S3 with Criskelo's rom.

locked a bunch of satellites within a few seconds inside buildings.

it's faster and there are more locks than i normally get.

thanks for your work
[Galaxy S III Android Development] wevsspot:
Crypted - just wanted to let you know that your patch works fine on an AT&T Samsung Infuse 4G running PA JB ROM (latest version). The GPS on the oroginal Froyo ROM was adequate, but got progressively worse as I flashed different custom ROMs up and to JB. Scott's PA JB GPS configuration worked surprisingly well, but I was still having issues coming out of sleep mode - with GPS taking as long to lock coming from a warm wake as from a cold boot.

I decided to give your patch a try. I haven't had much time to play with it, but my first impressions are that locks do occur a bit quicker, and I definitely have more satellites reported in view than I did previously (testing from the same location, same time and same weather conditions.....10-12 sats in view now while before I usually only saw 8-9), I also noticed that sats in use increased on average by 1-2.

Accuracy calculations (as reported by GPS test) take a little longer before they settle in. On the original PA JB ROM accuracy would settle to within approx. 25ft or so within about 2 minutes of lock. With the patch it appears to take a couple minutes longer. An example, initial accuracy starts at around 125ft and then eventually settles in to the 20-30ft range. This has been the same pattern since I changed from the stock Froyo - which locked almost immediately and had reported accuracy down to the 3ft range.

After reading this post I realize a lot of it sounds rambling - sorry about that. But mainly I wanted to thank you, and communicate to others that the patch does work with at least some JB custom ROMS, and will work on the Samsung Infuse 4G. It may not help much for some folks, but it certainly doesn't break anything either.

One thing I wanted to mention and look forward to your feedback...... Your gps.conf file contains a lot of additional information about what everything is doing or does. I took the liberty of editing the cheat sheet statements out of it and compressing it down to a more traditional .conf file.
[Galaxy S III Android Development] crypted:
Thanks for the kind feedback. Regarding your last paragraph, you can delete the comments out. However, these are entirely ignored and do not affect anything by being in place. Daemons overlook any # and the information flowing it.
[Galaxy S III Android Development] wevsspot:
I love learning new things :)
[Galaxy S III Android Development] crypted:
Official support has is now available for more devices:

Samssung Galaxy S III (AT&T, Rogers, Bell, Telus)

Samsung Galaxy S III I9300, I9305

Asus Transformer TF300T

Motorola Droid X2

Samsung Galaxy S 4G

If you appreciate this growing work, always consider clicking the Thanks.

Remember that I pay monthly hosting fees for the space and bandwidth necessary to keep this patch working on the backend. So, please consider donating a few bucks if you're a user. All donations go directly to the patch provisioning and there is absolutely no overhead to benefit me.
[Galaxy S III Android Development] tauran:
Quick question.

I've got an i9305, should i copy the entire "system" folder within the zip file? i tried just the gps.conf file but that failed to overwrite.

will copying the system folder merge or overwrite the existing data?
[Galaxy S III Android Development] crypted:
Are you rooted? You need to enable root WRITE permissions if you are. If you are not rooted, this will not work.
[Galaxy S III Android Development] tauran:
my mistake, i am rooted but what i missed was ex explorer ticked "mount system" but also displayed a message saying "failed to mount". i missed that bit, seems lik it's a common problem with ES. i'll find anoth root explorer.
[Galaxy S III Android Development] RiNo808:
Thank you for your awesome work...my question is..which one do I install for Att SG3...all I see if the SG3 test and an Att specific...thanks in advanced..
[Galaxy S III Android Development] crypted:
The OP post answers this point blank if you would read the darned thing.

Test builds are clearly labeled as specifically designed for this device. The AT&T build, which is not within the "Recommended" section, is just using AT&T SUPL data AS DISCUSSED in the Notes Section.
[Galaxy S III Android Development] crypted:
Okay, so I updated the main post to include:

As the * information discusses, this might be the resolution you're after if you keep popping up in random locales. I did not foresee this being a problem and will be very dismayed should it be the answer because it means that we have a reversal in progression of GPS processing at least for this phone.

Test it out and let me know.

Lastly, I feel that we're at a point to have two versions of this patch which are currently denoted as Test 2 and Test 3. This seems to be related solely to ROM base variations. Once the dust settles and we know more with the new ALT posts, I will move toward official status of multiple versions.
[Galaxy S III Android Development] spamtrash:
Few info... I have UK stock ROM with root&su + custom kernel.. first it was ICS, now it is JB one.

I always got at least 10 sats inside the building within seconds (before my Nav fully started, so I don't care if it was 5.66667s or 7.2222s), outside it was 12-16 reported as visible, with usually 10-14 in use.

Few questions: as this is international I9300 model, it sees the Glonas sats as well (sats with numbers bigger than 3, if I'm not wrong). Therefore: does your mod dealing with GPS sats only, or with Glonas as well? (sorry, I couldn't find it in notes).

Next question (to possible users, maybe, as long as I can't be sure how to revert it - I'll not install): AFTER your mod application: are the Glonas sats visible still by the device?
[Galaxy S III Android Development] crypted:
This will not interfere with the use of Glonas servers on top of GPS. Some people claim that it helped everything. My Glonas devices receive an overall performance boost. I do not do anything to affect Glonas, so I assume that the increase in GPS performance adds to the overall success rate which is additionally benefited by the other Nav satellites.
[Galaxy S III Android Development] spamtrash:
OK, my mistake, I assumed that you will check before posting any mods, therefore you could be sure, not use assumption. ALL I9300 devices are supporting Glonass, and this is visible to for example GPSTest as well as nav programs as satellites with number above 60.

I have no idea how this is integrated into scripts/GPS soft, but I'd check if these sats are visible as before patch before publishing... otherwise, I'd just write that I did not checked it...

At least, I hope that patch is not messing with it.
[Galaxy S III Android Development] crypted:
Allright smarty pants. Sorry that my longterm experience isn't good enough for you.

Maybe if people donated I'd buy devices to directly test from. But that seems to be out of the question, so yeah I have to make some educated guesses based upon my devices and those of friends that I get lucky enough to root and play with.

Based upon my educated experience in these matters, Glonass is not affected. However, this patch edits GPS processing and nothing for Glonass, so it seems logical that Glonass isn't going to be benefited directly whilst your entire performance can be benefited by the GPS issues being corrected. Thus, your software will get injects from all sources that are quick and proper cutting down on error filtration which leads to lag in actual locks and continual accuracy.

But hey, what do I know right? I don't have the device so my silly ass just made an assumption. :angel:
[Galaxy S III Android Development] Mopral:
Sorry if it's an idiot question but which one should be better for international S3:

-specific S3 build

-google no ssl from 3.x trunk

I would say google one because the S3 one is probably based on Qualcomm S3
[Galaxy S III Android Development] crypted:
It says that S3 is recommended. Right? I think I wrote that. If not, I think you're common sense is going to lead you to try the 4x variants of the S3. The difference is to resolve ROM-based issues assuming the ROM isn't totally ****.
[Galaxy S III Android Development] 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.
[Galaxy S III Android Development] spamtrash:
OK, smarty pants - you can try your best to convince them that your patch is 100% working...

good luck :good:
[Galaxy S III Android Development] crypted:
I can't win all battles. This isn't a paying gig so if someone can't follow the notes and use some common sense reasoning I have little patience left.

There are many possible issues than this patch works for. I will not fix a ROMs bad code or try to even bull**** a fix for bad drivers.
[Galaxy S III Android Development] boomboomer:
Just to let you ALL ;) know that glonass works perfectly with this patch enabled, the updated GPS Status app now shows glonass sats as little squares with separates signal strength bars.

This morning I locked within 12 seconds, using 17 sats, of which 3 were glonass and accuracy was within 4m.

Thanks for your continuing work crypted, it's greatly appreciated by the majority.
[Galaxy S III Android Development] RavinShubh:
Boom which patch did you use with out international model. I'm using the Google no SSL build and it with works well. However I've only gotten to 8 m accuracy
[Galaxy S III Android Development] boomboomer:
Generic Builds, the Google Specific No-SSL v3.1 build.

Although, it's exactly the same script that I had on my Sensation before I upgraded - it works just as well on the SG3.

Your accuracy will depend a great deal on many variables, 8m is very good considering that 40m is 'normal'.
[Galaxy S III Android Development] davieboynj:
Thanks! My Verizon Galaxy S3 (that i purchased about 2 months ago) wouldn't lock, and at most was connecting poorly to 4 satellites, most of them being rather far away. I tried a bunch of other home remedies on xda, (wiping the phone, clearing agps state, running with no battery cover) with no luck. I was about to return it, but a friend forwarded me this thread, and now i have a 3 second lock, and also seem to have some good accuracy back.

for the record:

Galaxy.S.III.Test.2 did not work at all. no lock.

Galaxy.S.III.Test.2.Alt worked perfectly.

I didn't try either of the Test.3s.

I'm trying to figure out who is at fault here, but i find it embarrassing for (in this order) Verizon, Samsung and Google that some guy on xda has to fix their mess.

Crypted, Your next beer is on me.
[Galaxy S III Android Development] crypted:
Thanks for the information. I'm getting the idea that the GPS unit in these phones went back in time to an older, less agile design.

Being that you're having to use ALT is evidence to support my impression above. ALT disables a very useful variable which permits the GPS unit to provide data from GPS satellites that aren't directly within range to garner closer accuracy and quicker lock times. Of course I provide an optimal error threshold to ensure those "out-of-bounds" satellites don't negatively interfere.

Yeah, it's also sad that I provide better NTP and XTRA.BIN almanac services than the conglomerates you speak of. How can some random guy resolve the network-based latency issues causing very unreliable aGPS where these people couldn't? This goes back to how I fixed ASUS Transformer problems and ASUS grabbed my work without a thanks for an OTA update.

This patch is such a simple thing really... :p

And I will drink any beer that is donated to me. But, I put all donations toward paying for the NETWORK SERVICES of this patch and would like to get MORE DONATIONS so that I can EXPAND to a large scale CDN with multiple redundances. :good:
[Galaxy S III Android Development] guywmustang:
I have a Verizon galaxy s3. I used the test 3 file. In the gps status application I show a quick lock and then resolution within a few feet. But in Google maps it shows its only accurate to 50 meters! Has anyone seen this issue? I don't understand the problem and I was hoping someone else has seen it. Thanks!
[Galaxy S III Android Development] crypted:
Naughty Google Maps.
[Galaxy S III Android Development] Cristiano Matos:
Thank you brother .'. :good:
[Galaxy S III Android Development] Napsterbater:
I see this patch is now listed as supporting the i9300/i9305 version of the SGS3, But after doing so digging this patch uses the Qualcomm almanac data file (xtra.bin) but the i9300 and i9305 use a Broadcom GPS/GOLNASS chipset and by default use an lto2.dat file from them.

Looks like the Qualcomm Snapdragon SGS3's (US SGS3's for one) would be fine since they are using a Qualcomm GPS.

So am I wrong? I could see some of the settings in the gps.conf file being helpful but I would think using the almanac data from the right company would make it better.
[Galaxy S III Android Development] crypted:
My patch works for more than just the almanac. Unless someone pulled a fast one, the two data files are irrelevant and won't interfere with one another as to the call variables in the gps.conf.

And, I don't have the .xml which controls more indepth GPS flow with the other device.
[Galaxy S III Android Development] Napsterbater:
I figured the rest would help as well, I was just thinking having a version with the lto2.dat for devices that use it could only be even better.

Do you need a copy of gps.xml?
[Galaxy S III Android Development] crypted:
If there is an XML for GPS, I would be much obliged to see it. I've requested this from users on numerous occasions but keep hearing that there isn't one.

If I had that, I could make a full customized patch as I do for other devices like ASUS and Acer brands.
[Galaxy S III Android Development] funkymonk101:
best patch ever

thankyouthankyouthankyouthankyou!

I'm running CM 10.0 on the Verizon Galaxy S3 (cm-10.0.0-d2vzw.zip). Great ROM in every way... except it frequently took 10+ minutes to get a GPS lock. I installed "Galaxy S III Test 3" (didn't try any others first), now I get a lock in under a second, in every app. Wow.

You da man!
[Galaxy S III Android Development] For_TG01:
Great work as i can make out from the thread. I have I9300. Could you please let me know which file to use as there are so many and am not sure which one to go for? Would installing the file 'agps.patch.google.build.v3.1.zip' through CWM do?
[Galaxy S III Android Development] crypted:
The user directly above your post stated that the S3 Test 3 worked great. Maybe use that?
[Galaxy S III Android Development] ctrlaltdel:
Re: AGPS Patch Galaxy S III 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, LOCK EXTRA SATS

hi, can i use this with my note 2 lte? and which file i should try?

thanks!
[Galaxy S III Android Development] Grooov3:
i am blind or i dont see the version for the international i9300
[Galaxy S III Android Development] Erahgon:
Re: AGPS Patch Galaxy S III 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, LOCK EXTRA SATS

I personally use the "Galaxy S3 Test 3 Alt" version.
[Galaxy S III Android Development] crypted:
TopNTP - the app.

We need bèta testers. Hopefully we can get some useful feedback to optimize this app. The patch itself has been proven to work, we just need to know for as much as possible devices if we can a) really install the patch and b) if the app is sort of clear in its use.

Get it on Google Play!
[Galaxy S III Android Development] popcorn1122:
Hi crypted... I know you do not like me !! But still i am writing this....

As some member has mentioned in last page, S3 only reads lto2.dat. S3's Broadcom chips uses the glonass V2 of lto2.dat from glpals.com.

The best way to edit the gps.conf file is to use the nearest npt server from http://www.pool.ntp.org/en/

I have attached the gps.xml (Stock from latest firmware of s3 of March 2013) as you have requested.

Also I have attached my own version of gps.conf for India NTP Server

This is all you need to run the GPS perfect in S3.

After changing the files in /system/etc go to /data/gps and delete the old lto2.dat and its .txt files and reboot s3 to enjoy the perfect GPS.
[Galaxy S III Android Development] crypted:
You state some incorrect things there. And, your gps.conf is incorrect.

Take your conclusion of the lto data. LTO is different than XTRA. Therefore, you would not use:

I leave XTRA in for all devices whether they use it or not because:

1. If the device does not use it, it will IGNORE it.

2. Some apps look for XTRA servers even though it will be ignored by the GPS daemon.

Your LTO data file locations usually comes from XML headers from GLPAL that loads from the other file you mention. So, again there you go.

I'm not going to get into a debate on NTP. I won that debate two years ago and for some reason as few of you out there don't want to give up.
[Galaxy S III Android Development] silentser:
i dont know why there is negative respond in here, i use this patch over and over each time after flashing of roms, it is like unlocking the phone gps limit from 8-9 maximum to 11-13 maximum.

great work, really great work
[Galaxy S III Android Development] highwar:
will it work with i9300 the international version

is there a way to flah the original gps file?

and which way is best since I prefer flashing a. od like I do with a rom so I wont do something stupid
[Galaxy S III Android Development] Zatta:
Use the app, it will backup your original gps.conf, so it is easy to revert if you dint like it. There is a restore function in the app.

Playstore link is in my signature.

Taptalked u see .. əəs n pəʞlɐʇdɐʇ
[Galaxy S III Android Development] LentoViolentoMan:
i'm getting no permission due to read-only filesystem.. any ideas?
[Galaxy S III Android Development] Zatta:
Where, how and when do you get that? What are you trying to do?

Taptalked u see .. əəs n pəʞlɐʇdɐʇ
[Galaxy S III Android Development] LentoViolentoMan:
thanks for replying,

i get this message when running the adb batfile, then choosing option 4.
[Galaxy S III Android Development] Zatta:
Right, than the next message also goes for you:

We (I) developed the app for the problems / questions you are facing.

Taptalked u see .. əəs n pəʞlɐʇdɐʇ
[Galaxy S III Android Development] husky69:
Is there a problem with using NTPSync along with this app? It's an app automatically syncing my phone's clock to a given NTP server whenever the phone is connected to WiFi.
[Galaxy S III Android Development] Zatta:
I don't see a problem with that. Maybe you can tell me?

But why would you need your phone's clock synchronised anyway? I'm not judging, just curious. Sounds not neccesairy to me to do so.
[Galaxy S III Android Development] husky69:
I just like to have my clock set correctly, and NTP let's me automate that. And I have that app installed long ago, so I'm used to it...
[Galaxy S III Android Development] sasot:
Is this different from this http://xdaforums.com/showthread.php?t=2429642&page=2
[Galaxy S III Android Development] FlemishDroid:
The one you linked have some different settings...for example if you choose the version of Europe you got a gps.conf with many EU countries:

NTP_SERVER=eu.pool.org

NTP_SERVER=0.europe.pool.ntp.org

NTP_SERVER=1.europe.pool.ntp.org

NTP_SERVER=2.europe.pool.ntp.org

NTP_SERVER=3.europe.pool.ntp.org

NTP_SERVER=fi.pool.ntp.org

NTP_SERVER=ru.pool.ntp.org

NTP_SERVER=be.pool.ntp.org

NTP_SERVER=gr.pool.ntp.org

NTP_SERVER=hu.pool.ntp.org

NTP_SERVER=sk.pool.ntp.org

NTP_SERVER=ee.pool.ntp.org

NTP_SERVER=by.pool.ntp.org

NTP_SERVER=ro.pool.ntp.org

NTP_SERVER=ua.pool.ntp.org

NTP_SERVER=cz.pool.ntp.org

NTP_SERVER=lt.pool.ntp.org

NTP_SERVER=bg.pool.ntp.org

NTP_SERVER=mk.pool.ntp.org

NTP_SERVER=md.pool.ntp.org

NTP_SERVER=lv.pool.ntp.org

NTP_SERVER=hr.pool.ntp.org

NTP_SERVER=yu.pool.ntp.org

NTP_SERVER=rs.pool.ntp.org

NTP_SERVER=ba.pool.ntp.org

NTP_SERVER=am.pool.ntp.org

NTP_SERVER=is.pool.ntp.org

NTP_SERVER=li.pool.ntp.org

NTP_SERVER=al.pool.ntp.org

NTP_SERVER=me.pool.ntp.org

NTP_SERVER=gi.pool.ntp.org

NTP_SERVER=ie.pool.ntp.org

NTP_SERVER=az.pool.ntp.org

I prefer the gps.conf from Crypted. ;)

---------- Post added at 11:08 PM ---------- Previous post was at 10:44 PM ----------

I use Galaxy.S.III.Test.3.zip on official CM10.2 with Boeffla kernel beta 7 and it works amazing! It's faster then the stock gps.conf file from CM10.2.
[Galaxy S III Android Development] sasot:
Ok. I will try this one. :)
[Galaxy S III Android Development] sasot:
Which build should i choose?
[Galaxy S III Android Development] Zatta:
Just download the app from the play store, press install, choose "install with reboot", done. I have a i9300 too and can confirm the standard settings are okay.

Verstuurd van mijn GT-S5660 met Tapatalk
[Galaxy S III Android Development] Marcuss?:
Thanks [MENTION=700051]crypted[/MENTION]. This solved my GPS woes. I used Test3.
[Galaxy S III Android Development] GTK87:
false suggestion - delete this please