Database Info

GPS Issues and the gps.conf file

In the mysteries that lie within the GPS woes on the Inspire; I have been having GPS issues for sometime now. I have used three different ROMs and a handful of radios, all with GPS issues. I feel there is an issue within the Inspire itself that I hope HTC fixes soon, but with no real solution, I don't have any answers; just something to try. In my research on XDA and the WWW, I have found two different versions of the gps.conf file that have a slew of added lines. I added, subtracted, and even carried the one and came up with this:
NTP_SERVER=0.us.pool.ntp.org
NTP_SERVER=1.us.pool.ntp.org
NTP_SERVER=2.us.pool.ntp.org
NTP_SERVER=3.us.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
XTRA_SERVER_4=http://xtra4.gpsonextra.net/xtra.bin
INTERMEDIATE_POS=0
ACCURACY_THRES=0
DEBUG_LEVEL=3
ENABLE_WIPER=0
ENABLE_XTRA=TRUE
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_SECURE_PORT=7275
SUPL_NO_SECURE_PORT=3425
SUPL_HOST=supl.skyhook.com
SUPL_PORT=7278
CURRENT_CARRIER=common
#REPORT_POSITION_USE_SUPL_REFLOC=1
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
DEFAULT_USER_PLANE=TRUE
#START_MODE=WARM
#OPERATION_MODE=STANDALONE
PHONE_TYPE=UMTS
Now I just added this gps.conf file to my phone last night, so I'm still testing it. Adding this to your gps.conf file should help mostly with A-GPS. Last night and today I have been able to lock on pretty damn quick (before I would sometimes go 30 minute without any luck). I am using the stock AT&T HTC Inspire radio (internet speeds are the best, but if GPS continues to work, I'll be happy man).
For those that don't know, the gps.conf file is in system/etc. You will need a root explorer to navigate to it and edit the file. I use ES File Explorer (needs to be enabled root explorer within this apps settings). Nav to the root then to system/etc. Open gps.conf, paste the above, and save. May want to back up the original gps.conf file first just in case. If not, it will most likely contain something like this:
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
PHONE_TYPE=UMTS
Let me know if this helps or not. I hope it does.
**adding the gps.conf file in a zip, it is not flashable (can't upload the .conf extension)

Good info. Can you upload the gps file? This way people can push it via adb or create a flashable zip. I like what you've done here. I see in other threads people have had success with it.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.

what ive found is theres 2 seperate issues. 1 is where gps completely stops and doesnt even try to connect anymore(no gps icon or any gps activity at all). the other and more common problem is when gps turns on, just refuses to get a lock in maps. i think this happens when maps is updated or for whatever reason in /data, then roms are flashed but /data is not wiped. this is copy/pasted from my thread cause i dont feel like typing it up again, and should work for those that cant get a lock. some of these steps are probably unnecessary, but since this is exactly how i did it and it worked for me and someone else so far, thats how im gonna type it.
Ok disregard my last post. After messing with some things, my gps was broken as well. Not broken really, cause the gps was coming on and seeing sats, but maps WOULD NOT locate me at all. Here's exactly how I fixed it (its now locking almost instantly-
Go to /data/app with root explorer, delete com.Google.Android.maps.apk(whatever is in there involving Google maps, delete it)
Now go to /data/data-delete com.Google.Android.maps folder.
Now go to settings/applications/ click the all tab. Find maps in there, probably called com.google.Android.maps or something like that. Click on uninstall updates and force stop if its lit up. Now there should be just 'maps' under the all tab, click it and then clear data.
Now open maps and it should work.
I think what's happening is maps is being left in /data throughout flashes, and its getting corrupted or something. What we just did forced the maps in /system to work, and it should be now. Let me know if it works. It just did for me
Also, don't update maps in the market, that's gonna put maps in /data again, and it might not work. It could, I don't know. Since there is an update for maps, ill put the new one in the next build
Click to expand...
Click to collapse

@Irs421, added gps.conf file in 1st post
@di11igaf, what if you format /data using CW before flashing? Do you thing the map data is left behind? I always do the factory reset using CW and other times manually format /data, /system, etc using CW.

You might want to try the scripts in my sig, I've been working on this for the HD2 for awhile now since there is no agps support in the gps driver. But these scripts have helped many people including myself. Inspire at least the stock rom has agps support, and the stock gps.conf file seems to be enough (At least here on the east coast), I have a completely stock inspire and have no trouble when it comes to locks, But I have suggested my scripts to a few others in the inspire forum with promising results, I am now having Aria people testing the same script and it seems across the board its making an impact.
All files are CWR, 6 regions of the US and 62+ individual countries. Currently released is 1.1, I have 1.2 currently being tested by a handful of testers before testing phase two of the 1.2 release.

I love what you have going on here AngelDeath! Can you fix the link for US - North East?
Adding this to my gps.conf file has worked amazing for me for the last two days, but this morning I was not able to get a lock on. I have I hopes for your script, AngelDeath.
{edit}... It did try to created a flashable zip myself that I tested last night. It didn't work (obviously ); and this could be the issue to it not working this morning. I'll have to reflash the phone, set it all back up and test again to confirm.

Sorry directorfer, lost power in the area, but up and functional now that they fixed it, try again. Hope you have the same results, i am currently testing 1.2 with some testers if all goes well, then I can test phase two for the HD2, but the Inspire and the Aria dont need phase two. I'll keep you posted.

GPS is looking good again
Flashed my phone again last night and reapplied these settings to my gps.conf file and it locked on quickly and stayed locked on. This morning on my way to work it was the same. I hope this works for others.
AngelDeath, I haven't tried your script yet. I wanted to test the configurations I have here first. Next time I flash I will give it a try and let you know. Thank you!

AngelDeath said:
Sorry directorfer, lost power in the area, but up and functional now that they fixed it, try again. Hope you have the same results, i am currently testing 1.2 with some testers if all goes well, then I can test phase two for the HD2, but the Inspire and the Aria dont need phase two. I'll keep you posted.
Click to expand...
Click to collapse
Ever since using AngelDeath's scripts, I've had minimal problems with GPS, no matter what ROM I've used it on.
A good thing that works for me, even if I'm having problems, is to just go into GPS status first, let it lock, and then do whatever I wanted to do in the first place.
I usually get a lock in under 20 seconds, and the extra time spent in that app is totally worth it.

Hey AngelDeath the link for USA North East is wrong. When i flashed it, it said Mid West.

I am running CM7, I tried what the OP suggested, but it did not change anything. I still get maybe one or two satellites at the most. Funny thing is that with MIUI 1.4.15 after applying the fix in the original thread, I get anywhere between 6 and 10 satellites in GPS Status. I have never had that with CM7.
I wonder what the difference lies in CM7 and MIUI?

Numpangx said:
Hey AngelDeath the link for USA North East is wrong. When i flashed it, it said Mid West.
Click to expand...
Click to collapse
Should bring this issue up on AngelDeath's forum:
http://forum.xda-developers.com/showthread.php?p=11342772#post11342772

codyg1985 said:
I am running CM7, I tried what the OP suggested, but it did not change anything. I still get maybe one or two satellites at the most. Funny thing is that with MIUI 1.4.15 after applying the fix in the original thread, I get anywhere between 6 and 10 satellites in GPS Status. I have never had that with CM7.
I wonder what the difference lies in CM7 and MIUI?
Click to expand...
Click to collapse
Take a look at what AngelDeath has, http://forum.xda-developers.com/showthread.php?p=11342772#post11342772. I'm going to imagine that his scripts will do other procedures besides just adding content to the gps.conf file. Right now I have only tested this tweak using Cognition HD 1.0.1 which is based on the stock Inspire ROM. I haven't tested this tweak on ROMs that are based on the Desire HD stock ROM. While these ROMs work on the Inspire, there might be slight difference that could interfere (but don't quote me on that).

Numpangx said:
Hey AngelDeath the link for USA North East is wrong. When i flashed it, it said Mid West.
Click to expand...
Click to collapse
Its correct, I was too lazy to change the banner to reflect the location, Will change all in the next release.

directorfer said:
Take a look at what AngelDeath has, http://forum.xda-developers.com/showthread.php?p=11342772#post11342772. I'm going to imagine that his scripts will do other procedures besides just adding content to the gps.conf file. Right now I have only tested this tweak using Cognition HD 1.0.1 which is based on the stock Inspire ROM. I haven't tested this tweak on ROMs that are based on the Desire HD stock ROM. While these ROMs work on the Inspire, there might be slight difference that could interfere (but don't quote me on that).
Click to expand...
Click to collapse
I use AngelDeath's script on my phone, and I used GPS Status to see if it worked. At first it didn't see any satellites, but I reset the A-GPS data, and then it locked into seven satellites. Maps locked onto me instantly. Later on that evening, I tried it again. No dice this time. It only saw one satellite.

After flashing the zip with the updated gps.conf I have noticed a huge improvement on gps. Initially after flashing it took almost 10 minutes to get a lock on I think 9th satellites, this was indoors with rain. Since then I've been able to get a good lock within 30 seconds at most, usually quicker. Accuracy seems to float around 50 feet.
Great work on tweaking this file, works like a charm now!
Sent from my Inspire 4G using XDA App

directorfer said:
In the mysteries that lie within the GPS woes on the Inspire; I have been having GPS issues for sometime now. I have used three different ROMs and a handful of radios, all with GPS issues. I feel there is an issue within the Inspire itself that I hope HTC fixes soon, but with no real solution, I don't have any answers; just something to try. In my research on XDA and the WWW, I have found two different versions of the gps.conf file that have a slew of added lines. I added, subtracted, and even carried the one and came up with this:
NTP_SERVER=0.us.pool.ntp.org
NTP_SERVER=1.us.pool.ntp.org
NTP_SERVER=2.us.pool.ntp.org
NTP_SERVER=3.us.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
XTRA_SERVER_4=http://xtra4.gpsonextra.net/xtra.bin
INTERMEDIATE_POS=0
ACCURACY_THRES=0
DEBUG_LEVEL=3
ENABLE_WIPER=0
ENABLE_XTRA=TRUE
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_SECURE_PORT=7275
SUPL_NO_SECURE_PORT=3425
SUPL_HOST=supl.skyhook.com
SUPL_PORT=7278
CURRENT_CARRIER=common
#REPORT_POSITION_USE_SUPL_REFLOC=1
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
DEFAULT_USER_PLANE=TRUE
#START_MODE=WARM
#OPERATION_MODE=STANDALONE
PHONE_TYPE=UMTS
Now I just added this gps.conf file to my phone last night, so I'm still testing it. Adding this to your gps.conf file should help mostly with A-GPS. Last night and today I have been able to lock on pretty damn quick (before I would sometimes go 30 minute without any luck). I am using the stock AT&T HTC Inspire radio (internet speeds are the best, but if GPS continues to work, I'll be happy man).
For those that don't know, the gps.conf file is in system/etc. You will need a root explorer to navigate to it and edit the file. I use ES File Explorer (needs to be enabled root explorer within this apps settings). Nav to the root then to system/etc. Open gps.conf, paste the above, and save. May want to back up the original gps.conf file first just in case. If not, it will most likely contain something like this:
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
PHONE_TYPE=UMTS
Let me know if this helps or not. I hope it does.
**adding the gps.conf file in a zip, it is not flashable (can't upload the .conf extension)
Click to expand...
Click to collapse
Hey, why would you add a supl server and then work in standalone mode? Just asking

carloss86 said:
Hey, why would you add a supl server and then work in standalone mode? Just asking
Click to expand...
Click to collapse
Why would you bring this up after almost a year? There are plenty of GPS threads.
Thread closed

[Fix]GPS fix for all EVO roms

You need to download TyTung GPS FIX 2.0 from below.
DOWNLOAD:
http://nexus-hd2.googlecode.com/files/GPS_Libraries_v2.0_NMEA_for_HD2_Gingerbread_update.zip
1. Place the ZIP file on to your memory card.
2. After you do that, turn the phone off.
3. Hold the power button for 15 seconds until it boots into RECOVERY
4. Select AD Recovery and press the call button.
5. Go to “Install Zip From SD Card. Then “Choose Zip from SD Card”.
6. Select the GPS FIX ZIP File and Press Yes. After it is done, press the back button and then press Reboot System.
After the phone boots up normally, Go to Settings -> Locations & Security. Select “Use Wireless Networks” as well as “Use GPS Satellites”
Launch your favorite Navigation program and you are good to go!
All gps.conf settings, including default NTP and XTRA, won't be sent to libgps.so in Diem's version, so changing them won't make anything different.
If you feel it makes any difference, I believe it's due to the psychological feeling.
Because Diem's libgps.so lacks a lot of features, I decide to implement a new libgps.so.
I have studied all the related GPS code from Java, JNI to C source code, and know how the GPS works on Android from the top to the bottom in these two weeks.
My implementation is based on GPS Library in HTC-HD2 Android Libraries. (Thanks to dan1j3l.)
New Features:
Show the number of satellites before getting a location fix.
Show or hide the GPS icon in the status bar immediately when you start or stop a GPS app.
Support the leap seconds. (Thanks to arne182 for figuring it out.)
Modify the Accuracy (i.e. Error in meter) to be more reasonable. (See Todo list below.)
Add AGPS interface. (Won't see "no AGPS interface in agps_data_conn_open" in logcat now.)
Add the missing functions to receive the NTP, XTRA, and SUPL settings from gps.conf.
Todo List:
Add AGPS support.
Need to send settings of gps.conf from libgps.so to the GPS chip via RPC to complete the AGPS implementation.
It's harder than adding the AGPS interface.
Fix the Accuracy.
Position Accuracy = Dilution Of Precision (DOP) * Measurement Precision.
We only get the DOP value, and I assume Measurement Precision is 10 in version 1.0 release.
Fix the SNR (Signal to noise ratio) value.
Know issues:
With the new libgps.so, the GPS location lock time still depends on your geographical location and the weather due to lack of AGPS support.
Accuracy value is not correct.
SNR value is not correct.
You tell me.
Downloads:
GB234_GpsLocationProvider_JNI_fix_update.zip (For AOSP only.)
Change GpsLocationProvider JNI code from android-2.3.4_r1 to a new commit: Clean up HAL initialization/cleanup sequence.
If you're using AOSP ROMs, e.g. my NexusHD2-Gingerbread V2.7 (Android 2.3.4), you can flash this file as well.
If you're using CM7 ROMs, ask your ROM devs if this commit is already patched or not. (This zip file should be not compatible with CM7.)
If you're using Sense ROMs, just skip it. (This zip file should be not compatible with Sense.)
If you're using MIUI ROMs, no idea. (This zip file should be not compatible with MIUI.)
Please test and report. Remember to backup your ROM first.
　
GPS_Libraries_v1.0_for_HD2_Gingerbread_update.zip (It should work for all kinds of ROMs. Please test and report.)
You can install GPS Status & Toolbox or GPS TEST to test the new libs.
Credits: the XDAndroid Project, dan1j3l, rmcc, tytung, arne182, etc.>>
New Features:
* Show the number of satellites before getting a location fix.
* Show or hide the GPS symbol in the status bar instantly when you start or stop a GPS app.
* Support the leap seconds. (Thanks to arne182.)
* Modify the Accuracy (i.e. Error in meter) to be more reasonable.
* Add AGPS interface. (Won't see "no AGPS interface in agps_data_conn_open" in logcat now.)
* Add the missing functions to receive the NTP, XTRA, and SUPL settings from gps.conf.
* Add AGPS implementation including injecting AGPS data (xtra.bin) and NTP time into the gpsOne engine.
* Hide Fix/Sats info and make the GPS symbol in the status bar flashing when you go to basement or tunnel.
* Show DOP/HDOP/VDOP values in GPS Status.
* Show Altitude above Geoid (i.e. mean sea level) and Geoid height. (You will see both of them in GPS Status. The value within parentheses is Geoid height.)
* Show correct SNR (Signal to noise ratio) value.
* Activate the AGPS data injection. (You can get a cold lock very quickly due to the working AGPS.) (Thanks to qwerty_7564.)
Known issues:
* Accuracy value is for reference only.
o Position Accuracy (meter) = HDOP (unitless) * Measurement Precision (meter). (Please confirm whether this formula is correct.)
o We only get the correct HDOP value, and we assume the value of Measurement Precision, and then do a post calculation to get Accuracy. So don't trust it completely.
* Some ROMs are not compatible with NMEA version of libgps.so.
o Those ROMs don't set the correct permission to /dev/smd27, so libgps.so cannot read NMEA sentences from it.
o The solution is to flash GPS_NMEA_permission_update.zip for correcting the permission after booting.
* Some ROMs suffer from the "GPS off-and-on" bug.
o Those ROMs can shutdown the gpsOne engine properly when turning off GPS setting using gps_cleanup(), but they cannot restart the gpsOne engine again because gps_init() is never called when turning GPS setting on after turning it off.
o It's a Gingerbread bug which is fixed by applying this commit from the source code.
o If you cannot modify the source code, the workaround is to set/add GPS1_CLEANUP_ENABLED=0 into gps.conf to avoid doing full cleanup.
Downloads:
They should work for all kinds of ROMs, including Gingerbread and Froyo. Please test and report back.
We can get GPS related data from two sources, including NMEA sentences and RPC callback function.
* NMEA version: Show more info but may have random hot reboot issues.
o Show DOP/HDOP/VDOP values in GPS Status.
o Show Altitude above Geoid (i.e. mean sea level) and Geoid height. (You will see both of them in GPS Status. The value within parentheses is Geoid height.)
o Show correct SNR (Signal to noise ratio) value.

jmin9012 said:
If your GPS is not working, try this fix.
http://nexus-hd2.googlecode.com/files/GPS_Libraries_v2.0_NMEA_for_HD2_Gingerbread_update.zip
Flash in recovery. Reboot. GPS should work
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Has anyone tested this? Any details on what drivers it contains? The file has the gpd libs from HTC Bravo and Cleo.

ECrispy said:
Has anyone tested this? Any details on what drivers it contains? The file has the gpd libs from HTC Bravo and Cleo.
Click to expand...
Click to collapse
Updated OP. Should have all the info requested now. I have tested this on MIUI and on XPLOD for my Evo

GPS Fix that works 100% from this forum:
http://forum.xda-developers.com/showthread.php?t=1132412
Direct link to file:
http://forum.xda-developers.com/attachment.php?attachmentid=658352&d=1311002339
Put "GPS_Supersonic_FIX_Flash3.zip" file in sdcard and flash it from recovery.
This fix is good for all EVO 4G roms, AOSP and Sense.

aaanadie said:
GPS Fix that works 100% from this forum:
http://forum.xda-developers.com/showthread.php?t=1132412
Direct link to file:
http://forum.xda-developers.com/attachment.php?attachmentid=658352&d=1311002339
Put "GPS_Supersonic_FIX_Flash3.zip" file in sdcard and flash it from recovery.
This fix is good for all EVO 4G roms, AOSP and Sense.
Click to expand...
Click to collapse
Dude... That's pretty messed up.... This person is actually trying to develop something here that is way more than just an update to your drivers, and you go and post the same stale link to GPS fixes that are tried and true but have been done and can still use improvement. Don't get me wrong I use those fixes but this OP is doing actuall development to improve our phones and going way deeper than just a driver update...
Ok, I will dl tonight and test thank you so Mich op for having the ingenuity to step out and try to make a one stop process for actually fixing GPS!
Sent from my PC36100 using xda premium

imheroldman said:
Dude... That's pretty messed up.... This person is actually trying to develop something here that is way more than just an update to your drivers, and you go and post the same stale link to GPS fixes that are tried and true but have been done and can still use improvement. Don't get me wrong I use those fixes but this OP is doing actuall development to improve our phones and going way deeper than just a driver update...
Ok, I will dl tonight and test thank you so Mich op for having the ingenuity to step out and try to make a one stop process for actually fixing GPS!
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I didn't try to offense any developer. I respect them. I just put the way that worked for me. Yes, I read again my post and realized that anyone can take it in a wrong way, sorry.

Just flashed on CM7 nightly 225 and appears to be working great.
Sent from my PC36100 using xda premium

@aaanadie, I understand I can come off offensive too at times. I have yet to try this mod, how about you? It is good to see a report of it working.
Just to clarify, can the OP clarify if this is an original work or just a re-post?
Sent from my PC36100 using xda premium

AGPS Patch Galaxy S III 3.1 & 2.2 | NEW SIII SPECIFIC BUILD | Tentative Support

AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.
HOWTO INSTALL: (Remember to make a backup. See Notes section for what this patch does.)
Method 1:
1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
2. Extract the files into a specific folder.
3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
4. Open the batch file called "ADB Installation Script - RUN THIS" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.
Downloads:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Galaxy S III Specific Build(s)
Galaxy S III Test 2 (Like it? Don't forget to click on "Thanks" and to rate the thread)
Please comment if this helps better than the Generic. It appears to resolve MANY problems for the Verizon variant. Expect a few minutes for initial lock with very fast and accurate locks after that.
Galaxy S III Test 3 (Like it? Don't forget to click on "Thanks" and to rate the thread)
Please comment if this helps better than the Generic. It appears to resolve MANY problems for the Verizon variant. Expect a few minutes for initial lock with very fast and accurate locks after that.
Galaxy S III Test 2 ALT (Like it? *Don't forget to click on "Thanks" and to rate the thread)
Please comment if this helps better than the Generic. *It appears to resolve MANY problems for the Verizon variant. *Expect a few minutes for initial lock with very fast and accurate locks after that.
Galaxy S III Test 3 ALT (Like it? *Don't forget to click on "Thanks" and to rate the thread)
Please comment if this helps better than the Generic. *It appears to resolve MANY problems for the Verizon variant. *Expect a few minutes for initial lock with very fast and accurate locks after that.
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Unfortunately, it looks like S3 has taken a nose dive into the past and this might be why some are seeing such issues. Try this if you have problems with the standard patch series.
Recommended Generic Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (currently v3.1)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
2.x trunk Alternative Options (currently v2.2)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
Changelog: (I'll try to keep this correct and current)
Code:
v3.1 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
introduced my own NTP pools
repaired the LG Alternate build (was same as standard build, compilation error)
v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
based on v2.2 configuration
has my own XTRA/AGPS server instead of Qualcomm
re-added two AGPS variables from v1.3 (two beta-testers saw instant results with these re-added)
re-added on USE SUPL variable from v1.3 (two beta-testers saw instant results with these re-added)
variables are now divided into sections and sections have descriptions
Code:
v2.2 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v2.2 (additional builds added)
added a new SUPL version using data from Sony Ericsson
added an alternate release using LG SUPL servers
added an alternate release using Google SUPL servers
updated the ADB PUSH to include new versions
fixed broken download links for the patch
v2.2
removed local AGPS variable
removed local XTRA_SERVER variable
created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
reduced redundancy in NTP and XTRA (unnecessary entries)
added newly located SUPL server to T-Mobile build
v2.1 (encompassing changes between 1.3 to 2.1)
removed two NTP server pools
removed xtra1 server
removed multiple SUPL_HOST entries
aligned SUPL_HOST with SUPLROOTCERT in each package
increased QOS timeout from 89 to 100
removed QOS standalone timeout variable
removed extra AGPS variables
Old Versions:
3.x Trunk:
v3.0 ADB Push Installer
v3.0 Google Build
v3.0 Google Alternate Build
v3.0 Google CWM Build
v3.0 AT&T Build
v3.0 T-Mobile Build
v3.0 LG Build
v3.0 LG Alternate Build
v3.0 Sony Ericsson Build
v3.0 GPS Only Build
v3.0 GPS Only Alternate Build
2.x Trunk:
v2.1 Google Generic Build
v2.1 AT&T Specific Build
v2.1 T-Mobile Specific Build
v2.1 GPS.Conf Only Build
v2.1 GPS.Conf Only Build (alternate)
v2.0 Google Generic Build
v2.0 AT&T Specific Build
v2.0 T-Mobile Specific Build
v2.0 GPS.Conf Only Build
v2.0 GPS.Conf Only Build (alternate)
1.x Trunk:
Worldwide 1.3
Worldwide 1.3n (alternate)
North America 1.2
Worldwide 1.2
Worldwide 1.2n (alternate)
North America 1.1
Worldwide 1.1
Worldwide 1.0 (not recommended)
North America 1.0 (not recommended)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
Remember, this has to be reflashed when you update or change ROMs.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
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.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
Reports indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
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.
Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differently which is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
Acer Iconia
LG Optimus One
Sony Ericcson XPERIA X8
HTC Salsa
HTC Flyer
HTC Evo 3D
LG GT-540 OPTIMUS
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
HTC Desire S
Motorola Triumph
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
Asus Transformer Prime
Asus Transformer (TF101)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
HTC One X
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.

Here are some things you can do if you're having problems with the S3.
With no GPS icon showing up
(OPTIONAL AND RECOMMENDED: USE Triangle Away to reset counter)
1. Flash back to stock UNROOTED ICS ROM
(Stuck at samsung logo after? flash a cwm recovery, factory reset and clear cache n reboot)
2. Enter into dialer *2767*3855# (Will do a HARD reset, no internal storage will be lost except the usual data)
3. Boot up again and run maps to see if you have a GPS icon
(IF YOU DON NOT HAVE A GPS ICON YOUR HARDWARE IS MALFUNCTIONING)
With GPS icon showing but no lock
4. Turn all GPS related thing OFF
5. go into google services framework in applications, settings, and clear data
6. go into maps, delete updates if any and clear data aswell
7. reboot the phone
8. Update google maps (very important)
9.reboot for safe measure
10. turn on everything in location and services in settings
11. boot up maps
12. profit
If GPS is still flashing but no lock
1. If steps1-11 does not work for you it is highly recommended to flash Galaxy S III Test 3 (created by crypted)
2. Factory reset trough settings and repeat steps 1-3 if not gps icon or steps 4-11 if gps icon flashes
3. profit
For flashing new ROMs after the above series:
1. see if gps is showing up or not, if not then repeat steps 1-12 above and it is recommended not to flash the same rom that makes gps disappear
2. if gps icon is showing up but very inaccurate then repeat steps 4-11
This patch will work only when your device is properly working. It appears a lot of people are forgetting that fact. Bad ROMs, bad cache, and bad flashing aren't going to be fixed by a GPS configuration alteration.
Thanks to egyptshun for the above information. There's only so much I can do without a S3.
Another user provided the following quick steps to resolve their problem. So if you are having issues AFTER trying the above out, take note of the following:
1.) download the sgii test file
2.) go into location services disable everything.
3.) Power phone off.
4.) remove battery for at least 30secs.
5.) boot phone into recovery
6.) wipe cache, and dalvik cache
7.) install zip file.
8.) reboot
9.) go into location service and enable gps location ONLY!!!
10.) open navigation and navigate to some place. Lock could take 5-10 mins, but it works great after.
Click to expand...
Click to collapse

This mod has worked great for me on synergy cm10 and beans. I personally used the Google specific 3.1 cwm flashable zip!
And holy hell.. I hate when others do this but I am actually first! Lol
Sent from my SCH-I535 using Tapatalk 2

Download links not working.
Sent from my SGH-I535 using Tapatalk 2

houseboatwayne said:
Download links not working.
Sent from my SGH-I535 using Tapatalk 2
Click to expand...
Click to collapse
There appears to be a connectivity issue affecting a few people over the past hour. It should be resolved relatively soon.
Apparently, there's an issue with one an uplink.
Please check back after while. Sorry about this...way out of my control.

Interesting.... may have to tinker around a lil.... Thanks for bringing this to our attention!! :good:

shojus said:
Interesting.... may have to tinker around a lil.... Thanks for bringing this to our attention!! :good:
Click to expand...
Click to collapse
Yeap.
Also, I assume there are files in /etc/gps/ for this device. If this is the case, I can customize the patch further as I did to resolve all those nasty problems on the ASUS Transformer & Transformer Prime lineups.

crypted said:
Yeap.
Also, I assume there are files in /etc/gps/ for this device. If this is the case, I can customize the patch further as I did to resolve all those nasty problems on the ASUS Transformer & Transformer Prime lineups.
Click to expand...
Click to collapse
Yes there are files for gps in system/etc.
Sent from my SCH-I535 using Tapatalk 2

Ty07allstar said:
Yes there are files for gps in system/etc.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
If you can private message me those files, I would appreciate it.
I'm looking for any gps files in /etc/ and all files in /etc/gps/ should this exist.

Behold how good and how pleasant it is!
Sent from my SGH-I535 using xda premium

I copied the files to /system/etc and replaced what was in there. My GPS lock is much faster and does not drop. I'm on CM10 9/10 nightly with imoseyon's kernel.
Sent from my SCH-I535 using xda premium

Holy cow it works!
Sent from my SCH-I535 using Tapatalk 2

xXJay_RXx said:
Holy cow it works!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Glad to hear it. Guess we might do full support sooner than expected.

For CM10, which version do you apply? The SSL version or non-ssl version?

WhammyDroid said:
For CM10, which version do you apply? The SSL version or non-ssl version?
Click to expand...
Click to collapse
It doesn't matter quite honestly. The difference is discussed in the Notes Section. There's a slight performance benefit of one over the other.

It says I'm I'm NC and I forgot to back up
Sent from my SCH-I535 using xda app-developers app

jayotero said:
It says I'm I'm NC and I forgot to back up
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
And, you didn't read the Notes Section.
Have a gander for incorrect location issues...

crypted said:
And, you didn't read the Notes Section.
Have a gander for incorrect location issues...
Click to expand...
Click to collapse
I did the wiping and rebooting and selected only gps
Sent from my SCH-I535 using xda app-developers app

jayotero said:
I did the wiping and rebooting and selected only gps
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Could you supply more details? This really doesn't tell anyone what your setup is like, what you're experiencing, etc.
I don't have time to pick through the OP at this moment to point out what it asks you to post in initial conversations. It includes ROM's, GPS apps, etc. though.

crypted said:
Could you supply more details? This really doesn't tell anyone what your setup is like, what you're experiencing, etc.
I don't have time to pick through the OP at this moment to point out what it asks you to post in initial conversations. It includes ROM's, GPS apps, etc. though.
Click to expand...
Click to collapse
Sorry I was driving I'm using Verizon gs3 Rom I'm using is synergy nightlies r71 I'm using stock navigation it work previously just took any where from 10min to 1 hour or never kernel I'm using is Synergy and ziggys, now the gps app saying searching for gps signal while the phone says gps set also says my location is in N.C. While maps shows I'm in NJ, (correct location) I also followed step 26
Sent from my SCH-I535 using xda app-developers app

AGPS Patch Galaxy S 4G 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, LOCK EXTRA SATS

AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.
HOWTO INSTALL: (Remember to make a backup. See Notes section for what this patch does.)
Method 1:
1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
2. Extract the files into a specific folder.
3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
4. Open the batch file called "ADB Installation Script - RUN THIS" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.
Downloads:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Recommended Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (currently v3.1)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL TWRP build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
2.x trunk Alternative Options (currently v2.2)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
Changelog: (I'll try to keep this correct and current)
Code:
v3.1 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
introduced my own NTP pools
repaired the LG Alternate build (was same as standard build, compilation error)
v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
based on v2.2 configuration
has my own XTRA/AGPS server instead of Qualcomm
re-added two AGPS variables from v1.3 (two beta-testers saw instant results with these re-added)
re-added on USE SUPL variable from v1.3 (two beta-testers saw instant results with these re-added)
variables are now divided into sections and sections have descriptions
Code:
v2.2 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v2.2 (additional builds added)
added a new SUPL version using data from Sony Ericsson
added an alternate release using LG SUPL servers
added an alternate release using Google SUPL servers
updated the ADB PUSH to include new versions
fixed broken download links for the patch
v2.2
removed local AGPS variable
removed local XTRA_SERVER variable
created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
reduced redundancy in NTP and XTRA (unnecessary entries)
added newly located SUPL server to T-Mobile build
v2.1 (encompassing changes between 1.3 to 2.1)
removed two NTP server pools
removed xtra1 server
removed multiple SUPL_HOST entries
aligned SUPL_HOST with SUPLROOTCERT in each package
increased QOS timeout from 89 to 100
removed QOS standalone timeout variable
removed extra AGPS variables
Old Versions:
3.x Trunk:
v3.0 ADB Push Installer
v3.0 Google Build
v3.0 Google Alternate Build
v3.0 Google CWM Build
v3.0 AT&T Build
v3.0 T-Mobile Build
v3.0 LG Build
v3.0 LG Alternate Build
v3.0 Sony Ericsson Build
v3.0 GPS Only Build
v3.0 GPS Only Alternate Build
2.x Trunk:
v2.1 Google Generic Build
v2.1 AT&T Specific Build
v2.1 T-Mobile Specific Build
v2.1 GPS.Conf Only Build
v2.1 GPS.Conf Only Build (alternate)
v2.0 Google Generic Build
v2.0 AT&T Specific Build
v2.0 T-Mobile Specific Build
v2.0 GPS.Conf Only Build
v2.0 GPS.Conf Only Build (alternate)
1.x Trunk:
Worldwide 1.3
Worldwide 1.3n (alternate)
North America 1.2
Worldwide 1.2
Worldwide 1.2n (alternate)
North America 1.1
Worldwide 1.1
Worldwide 1.0 (not recommended)
North America 1.0 (not recommended)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
Remember, this has to be reflashed when you update or change ROMs.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
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.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
Reports indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
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.
Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differently which is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
Samssung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Samsung Galaxy S 4G
Sony Ericcson XPERIA X8
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.

Support is here, as promised...

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.

I couldn't get a lock for nothing after installing this, went back to stock with my LB6 modem and get a lock again within 1min. This was on a unreleased latest CM9 build.

getochkn said:
I couldn't get a lock for nothing after installing this, went back to stock with my LB6 modem and get a lock again within 1min. This was on a unreleased latest CM9 build.
Click to expand...
Click to collapse
You didn't read the OP post. So much for my hard work!

Here are the quotes from users already taking advantage of this patch. The quotes were on a temporary thread prior to me bringing support.
iamperson347 said:
Seems to work alright. I cleared gps data with angry gps and ran a tracking test. It locked in about 10 seconds to 8 satellites.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
iamperson347 said:
Flashed with twrp (that comes with aokp). I checked the file it was supposed to replace to the confirm it worked. I used gps fix build 3.1 no ssl.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I_eat_tacos said:
Build 3.1 no ssl is working good for me . Running Beam rom with Hefe kernal and UVLB6 modem.
Click to expand...
Click to collapse
foltz61 said:
3.1 no ssl worked for me on Unofficial CM9. I looked at the update script and the only thing affecting my device was copying gps.conf to system/etc (it wasn't in there at all) so, I did that manually. Rebooted and had a quick gps fix.
Sent from my SGH-T959V using Tapatalk 2
Click to expand...
Click to collapse
ko08 said:
Went from taking over 1 minute to ten seconds great improvement using cm9 on ics rom Oc to 1400 mhz
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse

Couldnt get it to work either.
Sent from my SGH-T959V using xda premium

gizmoscoop said:
Couldnt get it to work either.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Explain your comment as per OP rules.
Sent from my Galaxy Nexus using xda app-developers app

i do not see anthing about akop going to try it lb6 akop b6 m5

crypted said:
Explain your comment as per OP rules.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I would like to explain, it just that there isnt much too explain. Simply nothing happened when I flashed it.
Sent from my SGH-T959V using xda premium

gizmoscoop said:
I would like to explain, it just that there isnt much too explain. Simply nothing happened when I flashed it.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
You are being very lazy. Read the section on how to post. Then, read the Notes, and give us information so we can know what doesn't work.
Sent from my Galaxy Nexus using xda app-developers app

gizmoscoop said:
I would like to explain, it just that there isnt much too explain. Simply nothing happened when I flashed it.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
So, you're on stock Froyo, flashed the 3.x branch Sony Ericsson patch onto your Samsung Galaxy S 4G (the only solid information you gave us, and only accidentally since it's in your signature) and your GPS still worked exactly the same, right? Since you didn't clarify, that's my assumption on your process.
On my part, I've flashed it onto a Galaxy S 4G phone that was on AOKP m6r5 using the 3.x TWRP No-SSL patch. Seems about the same, still won't lock onto any of the satellites with 3 floors above my head, though it does see 10 as existing (0/10 locked using GPS Status). Maybe better, definitely not worse.

Theraze said:
So, you're on stock Froyo, flashed the 3.x branch Sony Ericsson patch onto your Samsung Galaxy S 4G (the only solid information you gave us, and only accidentally since it's in your signature) and your GPS still worked exactly the same, right? Since you didn't clarify, that's my assumption on your process.
On my part, I've flashed it onto a Galaxy S 4G phone that was on AOKP m6r5 using the 3.x TWRP No-SSL patch. Seems about the same, still won't lock onto any of the satellites with 3 floors above my head, though it does see 10 as existing (0/10 locked using GPS Status). Maybe better, definitely not worse.
Click to expand...
Click to collapse
The Notes explain the differences. The numerous variants that are not Google derived use SUPL servers of those companies listed in the filename. This is discussed in the thread.
If you have three floors above you, I would not expect any lock whatsoever. GPS signal is very reflective. So, your device could see 10 unique identifiers bouncing within your building. But, those will be too far above the minimal error threshold I use. Ergo no lock.

Works wonderfully! On cm9.1 and got locks in 8-12seconds and my accuracy went as low as 4ft without wifi assistance. Used 3.1v no-ssl
Sent from my SGH-T959V using xda premium

Thanks a lot
Hi
i have galaxy S 4G AOKP ICS
i have tried it without believing it
because i am suffering from gps issues since the first day i bought this phone
i have tried all the crappy solution (angry gps, Gps status, .... ,faster fix ...)
i have just flashed this one: Google Specific NO-SSL TWRP
it works perfectly
thanks a lot!!!!!!!!!!

I have sgs4g and use barebones 1.1.3 Rom (for its battery life)
Blastoff v2.5 kernal
Cwm recovery 5x
I have always had gps issuse with this phone
I flashed the non-SSL google build
First link in post
Flashed perfect...first use no lock
I let it run maybe 5 or 10 minutes rebooted phone...
Second attempted it locked 6 of 11 sats in 3 seconds
Now gps locks every time in 3 to 5 seconds
Thanks so much for this mod now I can use my
gps on my phone.Thanks again
Sent from my Kindle Fire using xda app-developers

Root
SGS4G
Slim ICS
Flashed the 3.x Google specific CWM flashable
Nothing happens in 20 secs, but after 40 I get 7 locked. This is a major improvement over it never locking in the first place.
Does this patch require root access? I know methods 2 & 3 do, but does the first method? This might sound like a stupid question, but I have never done an ADB install.
After testing my GPS again, I can't get a lock. I am trying to run Runtastic Pro with it. I switched to the recommended Google Specific NO-SSL and there was no improvement. It says that there are 13 satellites around, but can't lock.

Cooptx said:
SGS4G
Slim ICS
Flashed the 3.x Google specific CWM flashable
Nothing happens in 20 secs, but after 40 I get 7 locked. This is a major improvement over it never locking in the first place.
Does this patch require root access? I know methods 2 & 3 do, but does the first method? This might sound like a stupid question, but I have never done an ADB install.
After testing my GPS again, I can't get a lock. I am trying to run Runtastic Pro with it. I switched to the recommended Google Specific NO-SSL and there was no improvement. It says that there are 13 satellites around, but can't lock.
Click to expand...
Click to collapse
Your phone has to be rooted first. Read the Notes.
Sent from my Galaxy Nexus using xda app-developers app

crypted said:
Your phone has to be rooted first. Read the Notes.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I am rooted, that question was just for my friend. He doesn't want to root.
Sent from my SGH-T959V using xda app-developers app

crypted said:
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.
Click to expand...
Click to collapse
We'll call this one hidden in plain site.
I've been testing a new kernel for Beastmode lately and was trying to get GPS to work. I flashed 3.1 google specific build and still no lockie. So I did what cryptic mentions in the OP and READ the notes. Well that note that I quoted up above is the thing that needs to be done for this phone to make GPS work. After I added that line to the build.prop and rebooted I got a lock in about 10 seconds indoors to an accuracy of 6 meters. Not bad for this phone at all.
Most of are ICS ROMs use CM as a base. So after going through and looking at most of their props NONE of them have that line. I don't know how it's escaped notice as long as it has. I've only tested it on CM9 8-29 build with Beastmodes yet to be released kernel. I doubt that it matters though. Flash the zip, add that line, reboot and you should be good to go.
So thanks to cryptic for this fix and one of the most detailed OP's I've ever had the pleasure of reading. And too erikmm(aka Beastmode) for the incentive to actually look into this.

[SOLVED] Mediatek quad core gps tracking bug solved: very easy.

One user in endomondo forums (sorry but the link does not work when I put it) has posted a solution for this annoying problem affecting to all mobiles using mediatek 6589 or 6589T processor.
You only need to add a line to the build.prop file located in system directory, so you need to be root, framaroot works fine with this processor.
The line alters the behavior of the JIT compiler, surpassing the bug, and all tracking and sports applications like mytracks, endomondo and every other one, now report accurate data in distance and speed.
The line you have to add is this:
dalvik.vm.execution-mode=int:fast
I added it at the end of my buld.prop (caesar h7500+ with last zopo stock rom) after another line starting with dalvik. too, using es file explorer editor, no need to change file permissions with this software, but you need to be able to write system. This is how the end of my build.prop is now:
ro.kernel.android.checkjni=0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.execution-mode=int:fast
# begin adupsfota properties
ro.adups.fota.oem=Vanzo
ro.adups.fota.device=ZP800H
ro.adups.fota.version=ZP800H 20130604-192031
# begin adupsfota properties
Other users have used build prop editor from the play store with success.
This solution has been extensively tried and tested in spanish forums htcmania and movilesdualsim (this post and folowing), and it works in every phone.
Some custom roms, have a different build.prop file and users have reported as failure, so if you are using a custom rom and the problem is not solved, I advice you flash a stock rom and try afterwards.
Some users report also higher antutu values after the patch, so it seems that the changing in jit compiler working mode does not compromise phone efficiency.

I will try decompile the app and add android:vmSafeMode = true under Application tag.

jackiechin said:
I will try decompile the app and add android:vmSafeMode = true under Application tag.
Click to expand...
Click to collapse
After decompiled the app and did the modificaton I said. The distance or speed measuring are back to normal state, but the flip map layer wont display anything.
So a modified app signed by myself will solve the mtk6589 issue but also bring new problems.
Mtk6589 or CM10.1 users can test the modified version (enable vmSafeMode)
TEST_MTK6589_Endomondo Sports Tracker Pro v9.0.2.apk (11.3 MB)
https://
mega.co.nz/#!MNJU3QoB!Z63HBVAH-c4JgsY0oBIKoCXMtopzsFaUWhGu66jU9GM

Made the changes on my Acer Liquid E2 Duo (mtk 6589) and i now can use Endomondo again.
Thanks for the tip.
Verstuurd vanaf mijn ASUS Transformer Pad TF300T met Tapatalk 4

Did this one my THL W9 Mediatek 6589T, thanks bro!

elsita said:
One user in endomondo forums (sorry but the link does not work when I put it) has posted a solution for this annoying problem affecting to all mobiles using mediatek 6589 or 6589T processor.
You only need to add a line to the build.prop file located in system directory, so you need to be root, framaroot works fine with this processor.
The line alters the behavior of the JIT compiler, surpassing the bug, and all tracking and sports applications like mytracks, endomondo and every other one, now report accurate data in distance and speed.
The line you have to add is this:
dalvik.vm.execution-mode=int:fast
I added it at the end of my buld.prop (caesar h7500+ with last zopo stock rom) after another line starting with dalvik. too, using es file explorer editor, no need to change file permissions with this software, but you need to be able to write system. This is how the end of my build.prop is now:
ro.kernel.android.checkjni=0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.execution-mode=int:fast
# begin adupsfota properties
ro.adups.fota.oem=Vanzo
ro.adups.fota.device=ZP800H
ro.adups.fota.version=ZP800H 20130604-192031
# begin adupsfota properties
Other users have used build prop editor from the play store with success.
This solution has been extensively tried and tested in spanish forums htcmania and movilesdualsim (this post and folowing), and it works in every phone.
Some custom roms, have a different build.prop file and users have reported as failure, so if you are using a custom rom and the problem is not solved, I advice you flash a stock rom and try afterwards.
Some users report also higher antutu values after the patch, so it seems that the changing in jit compiler working mode does not compromise phone efficiency.
Click to expand...
Click to collapse
HY
can you write a step-by-step guide for newbies?
Thank you so much

what about Google Maps navigation? works?

jackiechin said:
After decompiled the app and did the modificaton I said. The distance or speed measuring are back to normal state, but the flip map layer wont display anything.
So a modified app signed by myself will solve the mtk6589 issue but also bring new problems.
Mtk6589 or CM10.1 users can test the modified version (enable vmSafeMode)
TEST_MTK6589_Endomondo Sports Tracker Pro v9.0.2.apk (11.3 MB)
https://
mega.co.nz/#!MNJU3QoB!Z63HBVAH-c4JgsY0oBIKoCXMtopzsFaUWhGu66jU9GM
Click to expand...
Click to collapse
Works perfectly, thank you bro!

Thanks work fine with my symphony w125...accept for the problem u have mentioned..

elsita said:
One user in endomondo forums (sorry but the link does not work when I put it) has posted a solution for this annoying problem affecting to all mobiles using mediatek 6589 or 6589T processor.
You only need to add a line to the build.prop file located in system directory, so you need to be root, framaroot works fine with this processor.
The line alters the behavior of the JIT compiler, surpassing the bug, and all tracking and sports applications like mytracks, endomondo and every other one, now report accurate data in distance and speed.
The line you have to add is this:
dalvik.vm.execution-mode=int:fast
I added it at the end of my buld.prop (caesar h7500+ with last zopo stock rom) after another line starting with dalvik. too, using es file explorer editor, no need to change file permissions with this software, but you need to be able to write system. This is how the end of my build.prop is now:
ro.kernel.android.checkjni=0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.execution-mode=int:fast
# begin adupsfota properties
ro.adups.fota.oem=Vanzo
ro.adups.fota.device=ZP800H
ro.adups.fota.version=ZP800H 20130604-192031
# begin adupsfota properties
Other users have used build prop editor from the play store with success.
This solution has been extensively tried and tested in spanish forums htcmania and movilesdualsim (this post and folowing), and it works in every phone.
Some custom roms, have a different build.prop file and users have reported as failure, so if you are using a custom rom and the problem is not solved, I advice you flash a stock rom and try afterwards.
Some users report also higher antutu values after the patch, so it seems that the changing in jit compiler working mode does not compromise phone efficiency.
Click to expand...
Click to collapse
Wowww, you're an :angel:!!!
Since I'm using my Zopo ZP980 smartphone with Android 4.2.1 I couldn't use my favourite running app (Endomondo) but after reading and follow your instructions it's working perfectly.
For luca_vivi below my step-by-step:
1) Root your device (Google search)
2) Download BuildProp Editor in from the Google Play Store
3) Start BuildProp Editor
4) Click on the pencil icon right bottom
5) Search the line dalvik.vm.stack-trace-file=/data/anr/traces.txt en typ onder deze regel dalvik.vm.execution-mode=int:fast
If above done you'll have something like:
---
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.execution-mode=int:fast
# begin adupsfota properties
ro.adups.fota.oem=Vanzo
ro.adups.fota.device=ZP800H
ro.adups.fota.version=ZP800H 20130604-192031
# begin adupsfota properties
---
6) Click on the save icon left top
7) Restart your device and now it should work

Still need some help, please
I did the fix above (dalvik .... int:fast) on my doogee DG100 (MTK6572) which could not attain any lock before.
under GPSTest it now locks even indoors close to the window.
But when ever I move to any other application (google maps, waze, ...) it looses lock and hence the GPS is still useless .
Any ideas ??
thanks.

benbassa said:
I did the fix above (dalvik .... int:fast) on my doogee DG100 (MTK6572) which could not attain any lock before.
under GPSTest it now locks even indoors close to the window.
But when ever I move to any other application (google maps, waze, ...) it looses lock and hence the GPS is still useless .
Any ideas ??
thanks.
Click to expand...
Click to collapse
this thread is not for your micro, ask somewhere else
Enviado desde mi ZP800 usando Tapatalk 2

elsita said:
this thread is not for your micro, ask somewhere else
Enviado desde mi ZP800 usando Tapatalk 2
Click to expand...
Click to collapse
Used the fix and Endomondo improved slightly, but distances are still wrong. A ~1.6-1.7km stretch is being reported as 1.9-2.0 which is not nice when I want to track how much I walk everyday. What the fix did was to improve the distance accuracy a bit as well as, more importantly, the starting point, which was off earlier.
Tried Runtastic and it seems to record distances correctly. Will test over the next few days, but I do like Endomondo.
PS: Does unrooting after making changes had any negative impact on the accuracy?
PS2: Any tweak to improve gps fix time? Its very erratic currently, sometimes I get in <15 secs, a couple of times I waited for ~4 mins and couldn't get a lock. Had to reboot and then it worked.

I'm using runkeeper, and ex/importing the tracks to my old endomondo-account. A bit work, but better than the nerving endomondo-app.

Daemonarch2k said:
I'm using runkeeper, and ex/importing the tracks to my old endomondo-account. A bit work, but better than the nerving endomondo-app.
Click to expand...
Click to collapse
I am trying Runkeeper also (along with Endomondo, Runtastic and Sportypal), but found that while Runkeeper was more accurate than Endomondo, it was not as accuratte as Runtastic. Maybe you want to confirm the distances with Google Maps if accuracy is critical to you.

Clarification - side effects ???
What kind of new problems are you talking about? Is it something to do only with the app, endomondo or some phone features will get affected ??? Could u pls clarify ???
jackiechin said:
After decompiled the app and did the modificaton I said. The distance or speed measuring are back to normal state, but the flip map layer wont display anything.
So a modified app signed by myself will solve the mtk6589 issue but also bring new problems.
Mtk6589 or CM10.1 users can test the modified version (enable vmSafeMode)
TEST_MTK6589_Endomondo Sports Tracker Pro v9.0.2.apk (11.3 MB)
https://
mega.co.nz/#!MNJU3QoB!Z63HBVAH-c4JgsY0oBIKoCXMtopzsFaUWhGu66jU9GM
Click to expand...
Click to collapse

Hi
Well big thanks for traking this down.
Actually this also fixs the same issue on the MTK dual cores (MT6577)...
It will be merged into the gravityBox (Xposed Module)
Regards

Ties(to) said:
Wowww, you're an :angel:!!!
Since I'm using my Zopo ZP980 smartphone with Android 4.2.1 I couldn't use my favourite running app (Endomondo) but after reading and follow your instructions it's working perfectly.
For luca_vivi below my step-by-step:
1) Root your device (Google search)
2) Download BuildProp Editor in from the Google Play Store
3) Start BuildProp Editor
4) Click on the pencil icon right bottom
5) Search the line dalvik.vm.stack-trace-file=/data/anr/traces.txt en typ onder deze regel dalvik.vm.execution-mode=int:fast
If above done you'll have something like:
---
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.execution-mode=int:fast
# begin adupsfota properties
ro.adups.fota.oem=Vanzo
ro.adups.fota.device=ZP800H
ro.adups.fota.version=ZP800H 20130604-192031
# begin adupsfota properties
---
6) Click on the save icon left top
7) Restart your device and now it should work
Click to expand...
Click to collapse
can I use this method for other phone brand?
if can, what should I put on the below section? it seems like entering the phone model, etc
# begin adupsfota properties
ro.adups.fota.oem=Vanzo
ro.adups.fota.device=ZP800H
ro.adups.fota.version=ZP800H 20130604-192031
# begin adupsfota properties

Hi!,
I added the line "dalvik.vm.execution-mode=int:fast" in my buildprop, and it seems to works in Endomondo app with an error about 10%, in distance and altitude. But if I use Sports Trackers, app that I used, the error is very high.
Someone has use Sports Trackers app?
Thanks for everything.

Tested with Galaxy Note 3 Clone
MTK6589 QuadCore 1.2Ghz
Model : SM-N900
is not working..i am not able to find any GPS Satellites...