A number of us, on a variety of ROMs, including stock, have had difficulty getting our GPS systems to acquire a location fix. This can be temporary, or may happen so often it can appear permanent.
Background
When there is satellite reception, it can take a GPS receiver as much as 12.5 minutes to acquire a fix, depending on the number of satellites being received and their relative positions in the sky. To speed this up, our phones use a technology called Assisted-GPS (A-GPS), using location information obtained via mobile data and/or WiFi connections to more accurately and quickly determine a position.
Sometimes, A-GPS data seems to be incorrect, leading to no location fix.
What can we do?
Option A
The GPS Status application, available from the Market, can show you the location, signal strength, and acquisition data from GPS satellites above. It can also flush and reload Assisted-GPS data. This will clear any existing A-GPS aberration, and reset the acquisition sequence.
Option B -- Root required
Google provides Assisted-GPS data to Android phones via an A-GPS standard called Secure User Plane Location (SUPL). Cyanogen's team has determined that for some CM ROM users, disabling Google's SUPL connection in the phone's GPS receiver configuration can improve fix speed. As I understand it, his team is not yet sure of the root cause.
I'm not on Cyanogen's team. Even so, I could guess at a root cause, but it is only a guess. Perhaps the data packet is never received, due to a problem at the server. Perhaps the data packet is received but is missed by the GPS software. Perhaps the data packet is invalid and rejected, but a new replacement packet is never received and the GPS software just waits ....
Whether those guesses are right or wrong doesn't matter. When Google's SUPL service is removed from the phone, other A-GPS location data is used, allowing a GPS fix to proceed. Reportedly, with good speed. From my own experience, also, it seems to work well without SUPL service configured.
1. Mount the /system partition read-write. This can be done from adb, from the Root Explorer application, or from a terminal emulator
2. Edit /system/etc/gps.conf, and remove the lines that begin with "SUPL". For CM7, as an example, this is lines 5 and 6, "SUPL_HOST=supl.google.com" and "SUPL_PORT 7276"
3. Reboot.
i use gps status when i'm having issues. it works pretty well
is this pretty standard for most devices...gps issues?
One resolution that seems to work consistantly for me when in a "no sats" situation is to flush A-GPS data and immediately reboot.
The cause seems to be multiple apps having requested location data (such as browser and map), and may be related to the ROM I use (CM7), but this fix works for me every time.
Lockeskidney said:
is this pretty standard for most devices...gps issues?
Click to expand...
Click to collapse
Nope, i've never had a problem with my GPS.
had GPS issues when i was using CM7 nightlies prior to the RC1 release. but since flashing to RC1, GPS has been working flawlessly and barely takes 3-4 seconds to get a location fix.
I want to try Option B on my Evo before I try flashing a new radio. I'm rooted and using CM7, so I thought this would be an easy first step.
Even after the mount system app says it has successfully mounted with R/W access, I cannot edit the file with a text editor like this.
I know Google is my friend but alas I give up, I cannot figure out how to edit that file. What am I doing wrong?
skeene85 said:
I want to try Option B on my Evo before I try flashing a new radio. I'm rooted and using CM7, so I thought this would be an easy first step.
Even after the mount system app says it has successfully mounted with R/W access, I cannot edit the file with a text editor like this.
I know Google is my friend but alas I give up, I cannot figure out how to edit that file. What am I doing wrong?
Click to expand...
Click to collapse
Just install SQL Editor from market, and you are good to gther alternative is to copy the gps.conf file to your pc,make a backup of the original and then edit it with Notepad or some similar text editor and then bring back the file to the root of the phone.Just be careful to set the permissions as they were on the original conf file.
cevi said:
Just install SQL Editor from market, and you are good to gther alternative is to copy the gps.conf file to your pc,make a backup of the original and then edit it with Notepad or some similar text editor and then bring back the file to the root of the phone.Just be careful to set the permissions as they were on the original conf file.
Click to expand...
Click to collapse
You know that that post is more than 10 months old right? You are in trouuubbbblllleeee
Related
If you use a program like visualGPSce, you may notice that you can see lots of satellites, but you can't get a fix. I managed to fix it by:
1) Setting my log file to 3200bytes (using advanced config)
2) Disabling aGPS
3) I then turned off the phone, took out the battery for 10-20 seconds and replaced it.
4) Ran the quickgps program
5) Managed to get a fix and have it working quite fast!
I don't think all of this is necessary, but I have a theory:
I have a holux gpsslim 236B and sometimes it exhibits similar behaviour if you send it screwed up commands. The way to fix that was to remove the battery and then open the case to short out the backup battery (Yep, they were so helpful in enabling it to "remember" your corrupt settings). Reassemble and the gps device works fine. I get a feeling that the raphael may also benefit from such treatment (a forced reset on the gps module).
The only other theory I have is that the gps log file was corrupt (I couldn't delete it so I just made another one) and maybe that fixed it.
I've only given it limited testing, but if it breaks, I'll let you know so you don't waste your time!
I noticed my GPS performance was much better when I set my gpslogfile to 32KB as opposed to setting it's size to 0.
Just my 2c.
Isn't the quickgps tool for agps?
So either the disabling of agps or the quickgps is not necessary
ledg3 said:
I noticed my GPS performance was much better when I set my gpslogfile to 32KB as opposed to setting it's size to 0.
Just my 2c.
Click to expand...
Click to collapse
what's the logic/reasoning behind adjusting he gpslog file? i occasionally use GPS/tomtom though i would probably consider using it more frequently if getting a signal lock didn't take anywhere from 5-15 minutes.
i currently have disabled agps (no data plan so it's useless anyway) and have no logfile set to 0 as per the suggested settings i saw on fuzemobility.com post.
Can you post the file you used to load QuickGPS? I tried to download one but could not get it to run on my XDA Serra.
@kimbja98
how long has it been working? get back to us after a month or so of solid performance... the GPS issues seem to be so random that doing almost anything can seem like it fixes it... but i hope you're right
Just used it on the train on the way into work and it was fine, took about 2 minutes to get a location.
One thing I think may have been the problem is that it thinks it should see X satellites but obviously can't and gets confused (even if there are others in clear view), which may be down to agps, quickgps (I'm not sure if they're the same thing) or corrupted log file but now those satellites it can't see get dropped from the list (you can see this happening in VisualGPSce) and it gets a location after about 5 or 6 have been found. The holux seems to get positions at 4 (which theoretically, is the minimum but could be done with 3 if altitude is negligable) but that uses the sirfstar III chipset...I don't know what the raphael uses though.
I should mention I use ROMeOS 1.40 and that may have something to do with it. Either way, I'll be giving it some fairly rigorous testing. If it does break, I'll know how long it took and it may be that the log file got full and if it that, some regular deleting may be called for.
kimbja98 said:
If you use a program like visualGPSce, you may notice that you can see lots of satellites, but you can't get a fix. I managed to fix it by:
1) Setting my log file to 3200bytes (using advanced config)
2) Disabling aGPS
3) I then turned off the phone, took out the battery for 10-20 seconds and replaced it.
4) Ran the quickgps program
5) Managed to get a fix and have it working quite fast!
I don't think all of this is necessary, but I have a theory:
I have a holux gpsslim 236B and sometimes it exhibits similar behaviour if you send it screwed up commands. The way to fix that was to remove the battery and then open the case to short out the backup battery (Yep, they were so helpful in enabling it to "remember" your corrupt settings). Reassemble and the gps device works fine. I get a feeling that the raphael may also benefit from such treatment (a forced reset on the gps module).
The only other theory I have is that the gps log file was corrupt (I couldn't delete it so I just made another one) and maybe that fixed it.
I've only given it limited testing, but if it breaks, I'll let you know so you don't waste your time!
Click to expand...
Click to collapse
YES, your method seems to be one of working the best.
Congratulation.
I use the mix of some methods in the forum, and my GPS reception is quite good, even in my room inside!!
MY CONCLUSION:
1. to get rid of useless stuffs from the system (which also bad for the sat reception), use
[ROM] [WWE]RAPHAEL WM6.1 V05 - Build 20758.1.4.1 - pdaviet.net (http://forum.xda-developers.com/showthread.php?t=438488&highlight=20758.1.4.1) and
[RADIO] Raphael Radio 1.02.25.28 (http://forum.xda-developers.com/showthread.php?t=437219)
(before installing these ROM, the first step should be installing the HARD-SPL to save your device (http://forum.xda-developers.com/showthread.php?t=410150)
2. to get a really quick fix,
take the battery out, as mentioned above, for a few minutes, to clear the GPS memory. (You can try for example igo now, you will see nothing on the sat view at this time...).
After that download QuickGPS data (the ROM I mentioned has a correct quickGPS data download!) If you see iGO sat view this time, you will see a lot of red dots immediately, and after a not too long waiting, you'll have fix)
3. to make the GPS even faster,
adjust the baudrate to 38400 (with comport4) in your navigation program. (But leave port4 and baud4800 settings in the Windows Mobile settings!!)
4. there could be some navi software, which couldn't get fix (iGO yes, for example Googlemapsmobile not every time), use GPStest (http://www.chartcross.co.uk/products/WM00002_details.asp), select com4 and baud 38400 also, minimize, and run the other navi. It WILL work!
5. after getting a fast signal, in order to get rid of lag while navigating, use this excellent method from the forum:
A. With Advanced config 3.2 http://www.touchxperience.com/fr/out...ol-32-cab.html
1. disable A-GPS
2. disable GPS logging
3. logfile name must be empty
4. old logfile name must be empty
5. maximum size of logfile must be 0
6 delete the files : \windows\GPSLogFile.txt and \windows\GPSLogFileBack.txt
Under: HKLM\SYSTEM\CurrentControlSet\GPS Intermediate Driver\
- Drivers\GpsOneDevice\PollInterval -> 100 (default is 1000)
- Drivers\InputBufferSize -> 256 (EDITED!!) (default is 4096)
- Drivers\OutputBufferSize -> 256 (EDITED!!) (default is 4096)
- Drivers\SleepOnNoData -> 100 (default is 1000)
- Multiplexer\MaxBufferSize -> 256 (EDITED!!) (by default not present, you have to create it)
AND: from
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver] leave blank the followings (delete the data from inside):
"CurrentLogFile"=" "
"OldLogFile"=" "
With these settings, I have a really cool reception!!
One more thing: if you feel that the reception going worse, do the battery-taking-quickgps-using trick again!
FOR ALL THESE INFOS THANKS FOR THE DIFFERENT MEMBERS OF THIS FORUM!!!!!
(ps: some series ((series "2" ?!)) have no any gps reception problem. If you have this series, be happy, and don't do anything...)
ps2: I've tried other methods also from the forum (for example Nadavi HTC GPS tool, etc.), and made hard reset on my phone many many times to try other methods, but the mix of these methods seems to work, the other ones are not really necessary. So this mix has no contains all the possible solutions from the forum, and this was not the way of selection without thinking..
g2tl said:
Isn't the quickgps tool for agps?
So either the disabling of agps or the quickgps is not necessary
Click to expand...
Click to collapse
as I know quickgps and agps are quite different
-quickgps is downloading the latest sat positions to get faster fix
-agps is using phone cell informations also for positioning, besides the satellites
you NEED quickGPS, DO NOT USE aGPS!!!
So after reading around and trying things and discovering that LbsTestMode.apk doesnt exist for our phone, I just editted the file directly.
So without futher ado follow the below steps to see if it fixes YOUR gps.
MOST of the credit for this goes to the guys in the captivate and vibrant forums.
1. Copy the following into a file named secgps.conf
Code:
#Generated by GpsLocationProvider.
#Thu Dec 02 13:09:21 EST 2010
SSL=1
SSL_TYPE=0
POSITION_MODE=7
OPERATION_TEST_MODE=0
ACCURACY=50
SESSION_TYPE=1
SERVER_MODE=0
ENABLE_NMEA=false
START_MODE=HOT
GPS_LOGGING=0
AGPS_MODE=0
DYNAMIC_ACCURACY=1
ADDRESS_MODE=1
TIME_BTW_FIX=2000
OPERATION_MODE=MSBASED
USE_DEFAULT=true
DYNAMIC_ACCURACY_VALUE=50
SUPL_PORT=7276
ENABLE_XTRA=true
SUPL_HOST=supl.google.com
NUM_OF_FIX=999999999
TIMEOUT=3600
2. adb push secgps.conf /sdcard/secgps.conf
3. adb shell
4. su
5. remount rw
6. cat /sdcard/secgps.conf > /data/gps/secgps.conf
or copy it with root explorer of esfile explorer
7. reboot
Secondary fix to help speed up gps locks.
Code:
Use Root Explorer or some other method (I use Root Explorer as it has a built in Text Editor and automatically backs up the altered file.) to go to here:
system/etc/gps.conf
Use the text editor to alter the gps.conf file to this (if you are in the US):
NTP_SERVER=us.pool.ntp.org
XTRA_SERVER_1=north-america.pool.ntp.org
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
Now go to some place you should normally get a gps signal and launch maps.
this should correct it.
Couple of notes, this file appears to be dynamically generated, so if we can someone get a LbsTestMode.apk that works with the epic, or a script to copy the file over cron based through to make sure the settings stick that would be best.
if your gps stops working as it did after the fix, simply copy it back to /data/gps/ and reboot.
This is entirely a beta attempt and may not correct anything..
this is also for ADVANCED people, do not bother posting if you dont understand how and what you're doing above as we're not here to hold hands we're here for a solution.
art3mis-nyc said:
So after reading around and trying things and discovering that LbsTestMode.apk doesnt exist for our phone, I just editted the file directly.
So without futher ado follow the below steps to see if it fixes YOUR gps.
MOST of the credit for this goes to the guys in the captivate and vibrant forums.
1. Copy the following into a file named secgps.conf
Code:
#Generated by GpsLocationProvider.
#Thu Dec 02 13:09:21 EST 2010
SSL=1
SSL_TYPE=0
POSITION_MODE=7
OPERATION_TEST_MODE=0
ACCURACY=50
SESSION_TYPE=1
SERVER_MODE=0
ENABLE_NMEA=false
START_MODE=HOT
GPS_LOGGING=0
AGPS_MODE=0
DYNAMIC_ACCURACY=1
ADDRESS_MODE=1
TIME_BTW_FIX=2000
OPERATION_MODE=MSBASED
USE_DEFAULT=true
DYNAMIC_ACCURACY_VALUE=50
SUPL_PORT=7276
ENABLE_XTRA=true
SUPL_HOST=supl.google.com
NUM_OF_FIX=999999999
TIMEOUT=3600
2. adb push secgps.conf /sdcard/secgps.conf
3. adb shell
4. su
5. remount rw
6. cat /sdcard/secgps.conf > /data/gps/secgps.conf
or copy it with root explorer of esfile explorer
7. reboot
Secondary fix to help speed up gps locks.
Code:
Use Root Explorer or some other method (I use Root Explorer as it has a built in Text Editor and automatically backs up the altered file.) to go to here:
system/etc/gps.conf
Use the text editor to alter the gps.conf file to this (if you are in the US):
NTP_SERVER=us.pool.ntp.org
XTRA_SERVER_1=north-america.pool.ntp.org
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
Now go to some place you should normally get a gps signal and launch maps.
this should correct it.
Couple of notes, this file appears to be dynamically generated, so if we can someone get a LbsTestMode.apk that works with the epic, or a script to copy the file over cron based through to make sure the settings stick that would be best.
if your gps stops working as it did after the fix, simply copy it back to /data/gps/ and reboot.
This is entirely a beta attempt and may not correct anything..
this is also for ADVANCED people, do not bother posting if you dont understand how and what you're doing above as we're not here to hold hands we're here for a solution.
Click to expand...
Click to collapse
Lol... i'll hold ur hand. Plus it seems that the GPS locks faster now. but like u said it's temporary
I was playing around with this at work yesterday (also saw this on the captivate forum), but didn't have time to give it a test last night.
Here is a reference for more info on the captivate discussion http://forum.xda-developers.com/showthread.php?t=789383
Edit 20101203:
There are four major things going on in this fix, so lets talk about each one separately.
============================================================
1) Operation Mode - Switch to MSBASED
Standalone - The handset has no connection to the network, and uses only the GPS satellite signals it can currently receive to try and establish a location.
MS Based - The handset is connected to the network, and uses the GPS signals and a location signal from the network.
============================================================
2) Switching from WARM to HOT
Should make getting a fix faster provided you have cache money.
##GPSCLRX# if you aren't feeling as fresh as you would like to be
============================================================
3) SUPL server change for SUPL
Broadcom's Hosted Secure User Plane Location (SUPL) Location Platform (SLP) offers Mobile Network Operators (MNO) and service providers all the functionality of the most precise wireless location technologies including Assisted GPS (AGPS) without the need to make investments in Location Based Services (LBS) infrastructure.
SUPL is the emerging standard developed by the Open Mobile Alliance (OMA) for AGPS using existing IP networks as the underlying data bearer. SUPL lends itself very well to a hosted
solution where the vendor takes responsibility for providing a specified quality of service, assured by Service Level Agreement.
Doing a quick pingarooski, the google SUPL servers seem to be faster
============================================================
4) Time server
Do-whatcha-like but if you are in the US, the pool us.pool.ntp.org is probably going to be the fastest. But hey be my guest. If you want to run a time server from your phone you could always put in localhost.
How did you switch from hot to cold start? The old dialer code doesn't work in froyo.
Is this file erased with #gpsclrx## dialercode?
Hi, I have a broken GPS. Im running the Froyo Stock(ish) ODIN Tar that has the built in root and clockwork.
I was running 2.1 Epic Experience before and GPS worked fine. I wiped my data and cache and then used ODIN to flash the DK17 Froyo.
My GPS has not worked and I have not gone back to other roms just to perform a workaround.
I did try as you suggested with the secgps.conf file but it still will not give me a lock.
Thanks for all your efforts on this.. I really want GPS working
Brian
Gps would not work at all, before.
This fixes it for me.
For those wondering, it didn't work until I did both fixes. do both fixes...
Sent from my SPH-D700 using XDA App
brian_hoffman said:
Hi, I have a broken GPS. Im running the Froyo Stock(ish) ODIN Tar that has the built in root and clockwork.
I was running 2.1 Epic Experience before and GPS worked fine. I wiped my data and cache and then used ODIN to flash the DK17 Froyo.
My GPS has not worked and I have not gone back to other roms just to perform a workaround.
I did try as you suggested with the secgps.conf file but it still will not give me a lock.
Thanks for all your efforts on this.. I really want GPS working
Brian
Click to expand...
Click to collapse
I had this issue. I put on stock..got a gps fix. the applied a froyo ROM Quantum over my stock..got another GPS fix. THEN I wiped the froyo ROM.
All good now. I use ##GPSCLRX# to reset the GPS if it's taking to long too lock. I get lock in about 10 seconds now. 9 satellites and more.
ZenInsight said:
I had this issue. I put on stock..got a gps fix. the applied a froyo ROM Quantum over my stock..got another GPS fix. THEN I wiped the froyo ROM.
All good now. I use ##GPSCLRX# to reset the GPS if it's taking to long too lock. I get lock in about 10 seconds now. 9 satellites and more.
Click to expand...
Click to collapse
I'm hesitant to format my phone.. I just got it up and going and customized and synced. Not that its THAT big of a pain..
I guess I just hoped I could run this build till the official froyo comes out without re-doing everything.
On a side note, I did try both the above fixes as it was mentioned that it worked for someone else.
I also tried your ##GPSCLRX# to clear my GPS.. But it didn't work.
At this point it may be best to start over again.
I tried downloading some GPS test app, flashing some update.zip (gps Fix) from a different thread, manually changing the files mentioned here and clearing my GPS from the dialer code.
I'm feeling defeated, I'm not sure why we need to lock in a from a different modem. I'm guessing it generates some file? that sticks on a system upgrade?
I really hope this gets resolved the right way.
My GPS was working wonderfully using Mammon's Froyo 1.0.3 (I went through a bit of a process inspired by the first Froyo GPS fix post, involving flashing to DI18 and getting a lock before flashing Froyo)
Then today the nav program started to lose the GPS signal (going back to maps or toggling the GPS off and on seemed to get the signal back, but it was still flaky). I tried parts of this mod (I left start mode on warm and operating mode on standalone, going to experiment with each setting one at a time to look for any noticeable changes)
So the only thing I changed so far is the uml server and port, and while I am getting roughly the same performance as before the change, now my position is off - it used to be almost spot-on when reporting anything lower than 4m accuracy, but now it claims 1m and is still a good 15 feet (roughly 4 - 5m) north east of my actual position. It's still plenty accurate enough for navigation, so this is simply an observation - the google server appears to be slightly off, whether it's an (admittedly tiny) location error, or the maps aren't quite in sync with the GPS data on the server (I don't know much at all about how GPS works, so if anyone can explain the uml's role in the locating process, or anything else about how GPS works under the hood, please enlighten us)
That being said, I do think that I'm getting a lock ever so slightly quicker, but I was already getting a fairly rapid lock pre-mod so it's hard to be certain.
fastmikey1969 said:
How did you switch from hot to cold start? The old dialer code doesn't work in froyo.
Is this file erased with #gpsclrx## dialercode?
Click to expand...
Click to collapse
there is no dialer code(or associated program) in froyo on the epic for some reason hence the need to automate a cron to replace this file once it's been editted.
you can switch it just by editing the file directly and changing but im still not sure under what circumstance s the file gets regenerated dynamically.
brian_hoffman said:
I'm hesitant to format my phone.. I just got it up and going and customized and synced. Not that its THAT big of a pain..
I guess I just hoped I could run this build till the official froyo comes out without re-doing everything.
On a side note, I did try both the above fixes as it was mentioned that it worked for someone else.
I also tried your ##GPSCLRX# to clear my GPS.. But it didn't work.
At this point it may be best to start over again.
I tried downloading some GPS test app, flashing some update.zip (gps Fix) from a different thread, manually changing the files mentioned here and clearing my GPS from the dialer code.
I'm feeling defeated, I'm not sure why we need to lock in a from a different modem. I'm guessing it generates some file? that sticks on a system upgrade?
I really hope this gets resolved the right way.
Click to expand...
Click to collapse
no real reason to format the phone, give the above settings a try thoruhg whatever file explorer you use and see how it works.
if nothing else it may work for a few hours
The "gps fix" post by BThomas22 does some of this (modifies the /system/etc/gps.conf). I'm curious about "secgps.conf" as it doesn't exist on the filesystem at all typically, and there's already a "gps.conf" with those settings in it. Are you sure that tool didn't just do backups to a secgps.conf or something? Are we sure this file is actually read?
This also seems more likely to help with slow locks and cache issues some people are facing, but is almost certainly not the solution to the no GPS at all issue some people are having after flashing a froyo modem.
http://forum.xda-developers.com/showthread.php?t=839710 has an inexplicably working solution (verified by several people including myself) for at least some of the people who get no lock ever. If you're on a froyo modem, install "GPS Status" or "GPS Test" from the market and if you don't get any sats in view, you'll likely be fixed by those steps.
I haven't had the cache/slow issue, so I can't speak to whether this helps that or not, but the AGPS parts seem as though they would.
drunix said:
The "gps fix" post by BThomas22 does some of this (modifies the /system/etc/gps.conf). I'm curious about "secgps.conf" as it doesn't exist on the filesystem at all typically, and there's already a "gps.conf" with those settings in it. Are you sure that tool didn't just do backups to a secgps.conf or something? Are we sure this file is actually read?
Click to expand...
Click to collapse
Nope not at all.
This also seems more likely to help with slow locks and cache issues some people are facing, but is almost certainly not the solution to the no GPS at all issue some people are having after flashing a froyo modem.
http://forum.xda-developers.com/showthread.php?t=839710 has an inexplicably working solution (verified by several people including myself) for at least some of the people who get no lock ever. If you're on a froyo modem, install "GPS Status" or "GPS Test" from the market and if you don't get any sats in view, you'll likely be fixed by those steps.
Click to expand...
Click to collapse
That method has also not worked for a lot of people as well, so it's rather hard to say. I suspect that the only reason the modem flash "works" is because it caches data that the dk17 modem then reads as far as sat position and other things to basically give directions without actually "locking". No sats in view could also mean you just dont have a good line of site either(happens to me at work until i move near a window)
I haven't had the cache/slow issue, so I can't speak to whether this helps that or not, but the AGPS parts seem as though they would.
Click to expand...
Click to collapse
And the ntp part is meant to speed up caching and lock but the rest of it is more to configure it correctly.
I don't have the gps problem at all so couldnt say for sure.
PS: did you try this on your phone completely without other gps "fixes" or did you just come in to post a rather meaningless post about a bunch of stuff we're already aware of and attempting to dealing with, and not offer any solution or any new information or even just results?
brian_hoffman said:
I'm hesitant to format my phone.. I just got it up and going and customized and synced. Not that its THAT big of a pain..
I guess I just hoped I could run this build till the official froyo comes out without re-doing everything.
On a side note, I did try both the above fixes as it was mentioned that it worked for someone else.
I also tried your ##GPSCLRX# to clear my GPS.. But it didn't work.
At this point it may be best to start over again.
I tried downloading some GPS test app, flashing some update.zip (gps Fix) from a different thread, manually changing the files mentioned here and clearing my GPS from the dialer code.
I'm feeling defeated, I'm not sure why we need to lock in a from a different modem. I'm guessing it generates some file? that sticks on a system upgrade?
I really hope this gets resolved the right way.
Click to expand...
Click to collapse
I had the same/similar issue with GPS not working at all. Sound 0 satellites. Tried all of the stuff, but the only thing that I found to fix it was to redo the ODIN flash of froyo. I hope that helps.
ZenInsight said:
I had this issue. I put on stock..got a gps fix. the applied a froyo ROM Quantum over my stock..got another GPS fix. THEN I wiped the froyo ROM.
All good now. I use ##GPSCLRX# to reset the GPS if it's taking to long too lock. I get lock in about 10 seconds now. 9 satellites and more.
Click to expand...
Click to collapse
I get a good lock as well(most of the time). How do you see how many satellites are locking? I get accuracy reading of 8ft but nowhere does it state how many satellites...
1deviant said:
I get a good lock as well(most of the time). How do you see how many satellites are locking? I get accuracy reading of 8ft but nowhere does it state how many satellites...
Click to expand...
Click to collapse
get the app GPS Status, that will show ya all the infos
art3mis-nyc said:
The "gps fix" post by BThomas22 does some of this (modifies the /system/etc/gps.conf). I'm curious about "secgps.conf" as it doesn't exist on the filesystem at all typically, and there's already a "gps.conf" with those settings in it. Are you sure that tool didn't just do backups to a secgps.conf or something? Are we sure this file is actually read?
Nope not at all.
Click to expand...
Click to collapse
If you delete secgps.conf and reboot, the file is regenerated. This would seem to indicate that it is being used, as it is recreated upon reboot if it is missing. If it exists, it isn't overwritten however.
Also, gps.conf does not have the same settings as secgps.conf.
plapczyn said:
If you delete secgps.conf and reboot, the file is regenerated. This would seem to indicate that it is being used, as it is recreated upon reboot if it is missing. If it exists, it isn't overwritten however.
Also, gps.conf does not have the same settings as secgps.conf.
Click to expand...
Click to collapse
Phil, you're very smart! Thanks for the info!
chillaxtodamax said:
Phil, you're very smart! Thanks for the info!
Click to expand...
Click to collapse
Thanks Yuhan. I was waiting all semester for you to tell me that.
plapczyn said:
Thanks Yuhan. I was waiting all semester for you to tell me that.
Click to expand...
Click to collapse
No problem. See you in homeroom on Monday!
The following seemed to have helped some people on my post on AF so figured I'd post it here as well.
If you're still having GPS issues in an area where you have data coverage, and you've tried changing the gps.conf and possibly updating your libraries as noted in other threads, have you tried changing your GPS settings to MS Based instead of the default of "Standalone"?
From wikipedia:
Mobile Station Based (MSB) - In MSB mode A-GPS operation, the A-GPS device receives ephemeris, reference location, reference time and other optional assistance data from the A-GPS server. With the help of the above data, the A-GPS device receives signals from the visible satellites and calculates the position.
You can do that by doing the following, as noted in my previous post:
My GPS was really taking a long time to lock. Usually 10 minutes or so using GPS Status before it would lock. I tried both just using gps only and then also with wireless network and it still took a long time. So I updated the lbstestmode.apk to use MS Based and the gps.conf file that was mentioned earlier and now I get a lock in GPS Status in about 8 seconds from a cold boot using only the GPS with no wireless network.
If anyone wants to try, I've attached a flashable zip. I took the zip posted by merkuralex earlier in the other gps thread (thanks merkuralex) and added the lbstestmode.apk posted in this SDX thread:
http://forum.sdx-developers.com/index.php?topic=13593.0
The following flashable zips are attached:
lbstestmode_mt_gps_conf.zip - contains the gps.conf file from the other thread + the lbstestmode.apk file.
lbstestmode.zip - contains only the lbstestmode.apk
I'll repost the instructions here (thanks to cornaljoe on sdx for the actual instructions):
Pre-1. Flash the one of the attached zips in CWM first to install the lbstestmode.apk (or just copy the lbstestmode.apk into /system/app/ if you'd rather) and then reboot your phone.
Follow these directions:
1. After boot create a shortcut to Activities -> LbsTestMode -> .LbsTestMode
You may have to install LauncherPro if your launcher doesn't support the activities option under shortcuts. Once installed all launchers will have this option.
My note: Just an FYI, LauncherPro can be downloaded from the Market for free if you don't already have it. Or any other app that allows you to create shortcuts (such as AnyCut I think can also do that)
2. Start LbsTestMode and goto the application settings and set it to MS Based and press back until you exit app.
3. Reboot phone and then use GPS Status under a clear sky until you get a lock.
The main thing to pay attention to is the numbers labeled Error(m) and Fix/Sat in the lower corners of the compass.
Error(m) is the accuracy of your location in meters which shows after you get a lock. Fix/Sat is the number of satellites locked and in view prospectively.
In GPS Status, you can do the following to force aGPS data to download:
3A. Click Menu --> Tools --> Manage A-GPS state --> Reset . This will clear all previous A-GPS data.
3B. Click Menu --> Tools --> Manage A-GPS state --> Download. This will download fresh A-GPS data.
3C. Let GPS Status lock. The first time will take longer as your gps/phone syncs the data.
After you get a lock, you can try powering down your phone and then restarting and see if your lock is faster from a cold start.
This may or may not help you. All I can say is that changing to MS Based helped my gps lock time--I usually have data access where I am.
I have done this, and it works perfect!
Cloudy and raining here today. I will definitely try it. Quick question though, you saying use either zip or use one before the other? I'm not really clear on this.
Also do You have to keep the short cut?
You need to apply the zip first (in CWM) or else you won't have the option to create the shortcut
Wich one, there's 2 zips? I've got it all installed and working. Even though its cloudy, I got instant lock on. I'll test it again tommarow when I go out of town. So far so good though.
Edit: indoors is about 10 sec lock on. Great find OP. Has anyone posted this over at hofo? Another question, will clearing data cache from apps hurt it any?
Sent from my MOTWX435KT using XDA App
Everything went great today. I left my phone off all night so it could get a solid cold start this morning. Its cloudy and rainy again today too. I hit the road this morning and fired the GPS up and it locked in about 15 seconds. Great job on this fix. Also since then it has been instant lock times when i try it.
Sent from my MOTWX435KT using XDA App
tcross8361 said:
Everything went great today. I left my phone off all night so it could get a solid cold start this morning. Its cloudy and rainy again today too. I hit the road this morning and fired the GPS up and it locked in about 15 seconds. Great job on this fix. Also since then it has been instant lock times when i try it.
Sent from my MOTWX435KT using XDA App
Click to expand...
Click to collapse
Which ZIP did you use? I used the lbstestmode_mt_gps_conf.zip
idbl_fanatic said:
Which ZIP did you use? I used the lbstestmode_mt_gps_conf.zip
Click to expand...
Click to collapse
Actually I installed them both...lol But that's the last one I used.
I did have a bit of a hiccup on my way home. After lunch I turned my phone off. When I got back on the road 3 hours later I turned it back on and started up Navigation. It took a minute or so on the first lock. I exited out of Navigation and waited 20 minutes or so. I started it up again and it took about 30 seconds. Every time after that it was instant lock. Still very impressed. It was very cloudy and rainy today though. I was getting 1.1 mb down and 500 kb up today also. I would post this over at HoFo for all the nay sayers, but I wouldn't be able to answer any technical questions if anyone had them.
This place is starting to remind me of Seatle, rain every day...lol. I guess Fall is here to stay.
You are wasting your time.
I have traced this code extensively. For those who are unaware the GPS works on RPCs, which are internally processed by the kernel and passed to the chipset.
The chipset on this phone does not know how to handle AGPS requests - XTRA requests to inject the time (NTP time) and the orbital data are flatly refused.
You can set whatever you want, the data will never get to the chip. The Froyo base load intentionally discards such attempts and never sends them. If you load Gingerbread (and build it from source, as I have) and FORCE it to be sent it will return an error every time.
The problem appears to be in the silicon and/or the radio driver itself, which there is no source for. If someone's going to fix this, it's going to be at the radio interface level - not in user space.
My CM7 port is capable of cramming the data in there but it's turned off right now as when I enable it there's a fairly decent chance that the consequence of trying to do so is that the radio locks up and forces a watchdog reset (that is, a reboot on the phone)
Hi,
came from CM12.1 (GPS not working at all in the end) to CM13. Unforunately, the GPS works after a few minutes of searching but will disconnect more often. I'm testing the signal with several apps. Back in GMaps the signal is lost again. Today it won't get a signal for about an hour. This all with a clear blue sky..
In the gps.conf are the (standard) american NTP-servers noted. As I'm in germany, i would change them to those (with the hope of better signals). Instructions were given a lot in the web.
But everytime i change the gps.conf by copying/direct editing and "using" the GPS (High Accurate or only Device) i get a freeze and an instant restart.
I tried also with a clean file with only one line (just NTP-server): i get a restart. Tried also to clear Dalvik afterwards.
Tested this with different CM13 versions: Official, Resurrection Remix, Tesla. All with stock kernel and without any mods.
Always wiped the Cache, Dalvik, Data.
Could you please help me?
Thx in advance.
That's because you most likely replaced the gps.conf file without reading what's inside of it. I faced the same problem on my Mi 4.
Go to YouTube. Search for "How to make your gps lock faster?". You should get a video on the official xdadevelopers channel. Go to that video's description. You'll get a link to various gps.conf files per country/continent. Download the one which corresponds to your region.
(Sorry, but I'm not able to post links here as of now.)
I suggest you do this on a PC.
1. Download the file that corresponds to your region.
2. Get the gps.conf file that you have in your phone: /system/etc/gps.conf and copy it onto your PC.
3. Open both files, the one that you downloaded and the one that was in your phone with a text editor(Notepad++ recommended).
4. For convenience, I'll call the gps.conf file that you downloaded as "1" and the one that you copied from your phone as "2".
5. Whatever lines are present in 1, add them to 2 WITHOUT REMOVING any of the existing lines in 2. If there is any line in 2 that begins with a "#" that isn't with a "#" in 1, remove that specific # from 2. If there is any line that's present in both 1 and 2 but has different values, edit the line in 2 to match the VALUES in 1.
6. Most important thing again, don't remove any line in 2 just because it is not there in 1.
After this, your GPS should lock a lot faster and should be more accurate.
Thank you very much for your reply!
First i have to say that i did the GPS hardware fix for the Mi 4 --> http://en.miui.com/thread-173141-1-1.html
Result: found much more satellites with standard config and quicker (but still interrupts).
I followed your instructions and had a look on every line in detail.
Seems that the main issue for the restart was the XTRA_SERVER.
The gpsonextra won't connect or connection timed out. Let it at izatcloud (recommended for Qualcomm ARM?).
Then i did a ping on every NTP_SERVER and ordered them by response time.
Tested this in the last 3 days. First fix on the day will take some time (1-2 Minutes) but the following are within seconds and do not interrupt.
Not perfect, but much better than no fix at all :good:
2. Get the gps.conf file that you have in your phone: /system/etc/gps.conf and copy it onto your PC.
I dont seem to have a system or etc folder in my Mi4?
Back to stock, get a gps lock and reflash custom
This is definitely not solved. With the stock gps.conf and with all the other modifications suggested by MI4 owners, there is no significant change in GPS performance. GPS works, but there's no AGPS support, and that's why it takes 1 or more minutes for satellites to appear, and at least 2 minutes for a lock.
A look at the logcat shows this:
Code:
GpsXtraDownloader E No XTRA Servers were specified in the GPS configuration
I tried with both gpsonextra.net and izatcloud.net servers. This has to be a software issue, and boo to Xiaomi for ignoring MI4 owners.
I had the same problem with miui (I'm in Spain). Now I have LineageOS and much better.
I recommend you to try FasterGPS (needs root), in Google Play. This edits the gps.config with the countri in wich you are. Basically, it's the same you do manually, but this way you can not do a mistake.
I left away google maps and use Waze instead, that uses same maps and do not lose signal as gMaps (I don't know why...)
Good luck.
i have the same problem before, turns out it was my aluminium casing that blocks the antenna signal. i tried everything from faster gps, etc none really works. so the solution was to flash the rom into global rom miui and avoid using any metal casing for ur phone. this totally works for me?. questions please pm me
Using lineageOS, the GPS on my phone is so inaccurate it is unusable. For the first couple minutes when it starts searching for the satellites, my location will jump all over the place miles apart, then when it finally locks onto several satellites it will settle on a location, but it can be 1000+ feet away from my actual location. As I move, the location indicator will move along with me with the same offset from my actual location.
When I tried flashing back to the stock ROM, it worked flawlessly. It immediately found my location and was accurate within a few feet.
I'm not sure what's causing the issues. I've tried different maps apps, different versions of LineageOS, with or without MicroG. Occasionally it will find my location properly and everything works right, but that's rare. Even when I leave maps opens so it's constantly searching for the satellites for hours, it doesn't seem to improve it.
Anyone know what causes this? Is LineageOS failing to connect to some service that calibrates it?
It might be because the system apps that assist to your location (like YGPS) are removed. My phone does the same as I have seen it does not have the YGPS anymore. Rooting or HMS Core might be the culprit.
I got it to work by changing the gps.conf file for a different one from a phone on which the gps works. I didn't look into all the details of what settings were different, but at a minimum I know the time server and supl server were different.
In case anyone else has the same issue, I was able to change gps.conf without rooting the phone by doing a temporary boot of twrp with fastboot. Within twrp mount /vendor/, then use the twrp file manager to go to /vendor/etc/ and rename the old file to something else (for backup) and copy in the new gps.conf from the sdcard.