Hi guys,
I thought I would share what I discovered today. If this solution has been found, I apologize. Most users have been trying to get their Fuze GPS to lock on to satellites. Having used several GPS phones and many Bluetooth GPS pucks, I would say I'm somewhat experienced with using GPS on the PPC platform.
I have no issues with getting a lock on my Fuze. My issue is with Fuze's GPS chip randomly stop streaming data to my GPS applications. This usually happens after the initial lock. So for example:
a) Get a lock using any GPS application (GPS Test for example)
b) Exit GPS application
c) Launch GPS application again. Fuze will take several seconds to regain lock.
d) Fuze will take several seconds again to lock in, THEN it just stop streaming data to the GPS application!
I was able to reproduce this consistently. If you're using Garmin or TomTom, they will indicate that GPS lock is lost or something to that effect.
THE SOLUTION: Turn OFF aGPS!
a) Start->Setting->System->AGPS Settings
b) Uncheck BOTH "Enable AGPS" and "Enable AGPS location information..." (under the Privacy tab)
I was able to show that this consistently resolved my GPS data stream stopping problem. I'm using the .28 radio, but try it on the stock radio to see if that works and let the community know. What about QuickGPS? AFAIK, it's not causing any problem at all.
I hope this is helpful.
After standing on my deck for 20mins last Friday waiting on locks, I follow above and get a lock in 10secs(in my living room).
Turned off AGPS was the only change
It looks like without AGPS, the GPS would just stream whatever info it had cached even if it lost signal.
AGPS would clear last state instead and so become highly sensitive to signal-loss on the next poll. It doesn't help that this device is weaker in picking up GPS signals.
Yes, turn off AGPS.
NuShrike said:
It looks like without AGPS, the GPS would just stream whatever info it had cached even if it lost signal.
AGPS would clear last state instead and so become highly sensitive to signal-loss on the next poll. It doesn't help that this device is weaker in picking up GPS signals.
Yes, turn off AGPS.
Click to expand...
Click to collapse
Indeed, that would be exactly how I like my GPS to behave (use the cached ephemeris data). In fact, that was how all Bluetooth GPS puck works before the advent of AGPS. I guess AGPS is a good concept, but its implementation needs to be further tweaked.
If you have not used your GPS in a week or so, then AGPS is an advantage. Daily use, perhaps not so much.
basically the only program i can get to work with my GPS location is google maps and its usually off a few city blocks. no other prgram can even get my location including sprint navigator. is there anything i can do to help fix this problem?
Have you downloaded the satelittes via quick gps? If so did you make sure to enable GPS in the programs? I know for google maps you have to do Menu > Settings > Enable GPS
This might fix all your GPS troubles
I used to have a big problem with my GPS too. I installed the GPS Mod Driver by Mach2003 and now applications like TomTom and Navigon are able to find my GPS far quicker and I have more control over my GPS settings.
How it works is by simply creating a layer between the GPS native driver and the application. This layer, communicates with both the native driver and the application and is pretty robust. It gets the job done better than the native driver could by providing extra options like cell tower triangulation and path guessing.
Try it, it might fix your problem.
The forum link is:
http://forum.xda-developers.com/showthread.php?p=4729010#post4729010
Mach2003 said:
This Driver installs between your gps application and the GPSID driver that reads the hardware gps data.
Lag is compensated, by guessing your position 'some number' of milliseconds in the future, current course and speed changes are included in the guess.
It corrects for invalid data in the gps strings, Out of range DOP values, and Heading values of 'NaN' (Not A Number). Position, Speed, and course are reported, even though the distance traveled is less than 30 meters.
Click to expand...
Click to collapse
I know it might be stupid, but have you enabled the location settings on the phone. If its not enabled googlemaps will use triangulation to get the location within a few hundred to a thousand feet. With location enabled googlemaps will get my position within about 15-20 feet. I would check that then do the other things that are posted above.
My guess is that location setting needs to be changed from 911 only to on
Ok, There are a lot of posts and information regarding the GPS issue that some are experiencing. I am starting (yet) another post in the interest of compiling and maintaining information regarding that information in one location. As users/devs find out information I will update this post so everyone doesn't have to go looking everywhere for the information. I am hoping that the Moderator will sticky this post.
Some users are experiencing very long lock times for their GPS. Everyone, after reading A LOT of posts/threads it seems to be the consensus that this is a software/settings issue - NOT, a hardware issue. However, results from tweaking the following settings are very mixed. Most seem to get great results by tweaking the following settings while stationary - but, moving is a whole different ball game. I use the below settings and have great results while stationary. However, my G1 blows the Captivate completely out of the water!!! My G1 gave 3-10m accuracy while driving. This device can barely keep me on the correct highway and always seem lagging behind my current location. The G1 was spot on no matter what. What hasn't been determined is if these issues are hardware or software. For whatever my opinion is worth - I think it is a firmware/software issue. Here are some things to try.
Here is the info:
To get to your GPS settings open you dialer and dial the following number. This will not call anyone - it is a code shortcut to the settings:
*#*#1472365#*#*
Once entered you will observe a screen that has five buttons:
Get Position Test
Application Settings
SUPL/CP Settings
Test Application
Delete GPS Data
We will be interested in three of these initial buttons.
Get Position Test: This will be what one uses to test the results of your changes.
Application Settings: Exactly what it says.
SUPL/CP Settings: settings that determine specific data connectivity with the satellites.
In Application Settings the following are some that you might consider adjusting:
Operation Mode - Standalone, MS Based, MS assisted, Network Provider
Accuracy - defaults to 50. Don't set it below 10 (and only use increments of 10's)
SkyHook - not sure what it does. But, someone on a thread mentioned it and it DOES effect satellite lock times.
In SUPL/CP Settings one we'll be interested in the following:
Server FQDN Type
Server
Server Port
The following are the options provided on other threads:
Original/Stock Settings:
SUPL/CP Settings/SErver FQDN Type/Custom Config
Application settings/Operation Mode/Standalone
SUPL/CP Settings/Server/www.spirent-lcs.com
SUPL/CP Settings/Port/7275
Second suggested setup (from other posts and claimed to have great results):
SUPL/CP Settings/SErver FQDN Type/Custom Config
Application settings/Operation Mode/MS Based
SUPL/CP Settings/Server/supl.google.com
SUPL/CP Settings/Port/7276
Other settings that I have played with:
Application settings/SkyHook/On (and Off)
SUPL/CP Settings/SErver FQDN Type/Auto Config (and Custom Config)
You can play around with these to see what gives you the best results. If your GPS doesn't work better with whatever changes you made - than you can always put it back to the orginal settings above.
However, it has been recommended and I concur (for whatever that is worth) that you NEED TO SET THE FOLLOWING BEFORE YOU START PLAYING AROUND: Settings/Location and security/uncheck (turn off) "Use Wireless Networks). Most likely this won't really effect anything while your testing within the GPS settings - however, this will effect your results if you test using Google Maps, etc.
Now, having duly noted all of the above and having played around with the settings for several hours I found the best results FOR MY DEVICE IN MY AREA AT ONE LOCATION was the following:
Note: I adjusted these settings from earlier as the earlier settings proved to be very accurate when stationary - but, very inaccurate while moving. The latest settings I'm using are below. Also, look to the bottom of this post regarding changing your gps configuration file. That also helped A LOT. The bottom section of information is from the Official websites that run the time servers(effects GPS performance).
Application Settings/Operation Mode/MS Based
Application Settings/Operation Mode/SkyHook/ON (VERY IMPORTANT)
SUPL/CP Settings/Server FQDN Type/Custom Config
SUPL/CP Settings/Server/supl.google.com
SUPL/CP Settings/Server Port/7276
SUPL/CP Settings/SUPL Secure Socket/Off
Turning "SkyHook" ON assisted in faster locks with ALL of my tested settings when stationary!
My test results with the above would lock on up to three satellites in under four seconds and between 7 and 10 by eight seconds. Google Maps would locate me in about 6-8 seconds.
Using "Get Position Test" the settings in the three lines above consistently gave the not only the fastest locks and the most locks - but, also STRONGER SIGNALS!
I used at least seven different combinations of the above settings and some of them were just as quick - but, not as strong. Most of them were slower.
If anyone has better information to add then please PM me and I will add it to this top post.
LASTLY, I will make some guesses as to what some of the other settings do as I have heard different information:
Application Settings:
Session Type: Tracking or Singleshot - obvious (use Tracking)
Start Mode: Hot or Cold Start - someone posted on a thread that Hot uses data from your last read to get started. Cold start will start all over. So, Cold start SHOULD increase the time for you to get a lock unless you went left the area to an area that had different satellite to look up.
Test Application:
Performance Test: worked for me - but, I found the test above to work faster and give me quicker results for what I wanted.
Hardware Test/Sensitivity Test: Pretty cool - went on forever and I stopped it.
CNO Test: Seemed to test the average satellite signal strength.
Antenna Test: Never worked for me and I received errors.
H/W Test Settings: Settings for the above tests - I didn't mess with them.
NOTE: WANT TO SEE HOW ACCURATE YOUR ACCELEROMETER/COMPASS/ORIENTATION settings are? Check this out:
Test Application/Show Sensor Data - there is no way to calibrate it here... But, you can see just how sensitive your instruments are!!
Delete GPS Data - I didn't select this button and I don't recommend anyone else doing so either unless someone from Samsung tells us what it does. LOL!
FINALLY: Keep in mind that if you are seeing GPS lock times that are in the 3-8 second range (which was what I was getting) this WILL NOT be how long it takes for Google Maps to get the GPS data! Expect 8-15 seconds or a little longer (but, under 30 seconds) for Google Maps to pick up your location. Although the GPS sensors might pick up the satellites - you still have to give the software time to evaluate the data and apply it to the software.
Hope this helps someone out there.
Update/Additional Information (http://androidforums.com/1194187-post197.html):
Hot Start - The GPS receiver remembers its last calculated position and which satellites were in view, the almanac used, and the UTC Time. It then performs a reset and attempts to acquire satellites and calculate a new position based upon the previous information. This is the quickest re-acquisition of a GPS lock.
Cold Start - The GPS receiver dumps all information and resets. It then attempts to locate satellites and then calculate a GPS lock. This takes the longest because there is no known information. The GPS receiver has to attempt to lock a satellite signal from all of the satellites, basically like polling, which takes a lot longer than knowing which satellites to look for. This re-acquisition of a GPS lock takes the longest.
Thanks to Shadow77895 for the link to this info. I altered the settings above. Doesn't effect my results much at all.
MSBased Operation Mode(http://www.vzwdevelopers.com/aims/public/menu/lbs/LBSFAQ.jsp#GenQues11):
What is MS-Based mode of operation?
In MS-Based mode, the network provides the satellite information to the device, based on a rough estimate of where the device is located, and the device acquires the GPS signals from the satellites and calculates its location. After the initial fix, the device operates like an autonomous GPS receiver, until the satellite information must be refreshed, at which time the device goes back to the network to update the satellite information. MS-Based mode is appropriate for applications that require the device location to be updated rapidly, such as a navigation application.
And email thread regarding using the Google settings for GPS(http://osdir.com/ml/android-platform/2009-08/msg00386.html)
NEW INFORMATION!!!
ALSO! Check out this page: http://www.pool.ntp.org/en/use.html:
As pool.ntp.org will assign you timeservers from all over the world, time quality will not be ideal. You get a bit better result if you use the continental zones (For example europe, north-america, oceania or asia.pool.ntp.org), and even better time if you use the country zone (like ch.pool.ntp.org in Switzerland) - for all these zones, you can again use the 0, 1 or 2 prefixes, like 0.ch.pool.ntp.org. Note, however, that the country zone might not exist for your country, or might contain only one or two timeservers. If you know timeservers that are really close to you (measured by network distance, with traceroute or ping), time probably will be even better.
Find your optimal pool server here: http://www.pool.ntp.org/zone/north-america
For US the optimal server is: us.pool.ntp.org
Reference other threads I (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=731462) I recommend you do the following:
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
If you are NOT in the US go to here: http://www.pool.ntp.org/en/use.html and look at the links in the center of the page to navigate to the closest pool to your geographical location and use that pool for the top server entry.
REQUEST FOR ADDITIONAL INFORMATION:
Many are suggesting that we do NOT leave the Secure Socket ON. How will this effect data security with our devices? I don't understand how it could hurt us... But, there must be a reason for it. If someone could let me know I would appreciate it.
Good, guide, think you meant hot start should be faster though.
I'll be linking to this.
Sent from my Samsung Captivate using XDA app
Great, but doesn't address the problem
I need to point out that while this information is helpful it doesn't really address the problem that the GPS is facing.
What the above settings are doing is enabling multiple different A-GPS technologies to help compensate for the Galaxy S's poor GPS performance. A properly functioning GPS unit would not need these crutches except to acquire a faster fix.
I had my GPS outdoors today, with the first set of recommended settings, and was unable to achieve a fix while seven satellites were in view (according to it) with sufficient signal strength. This is a GPS firmware issue!
The above post is very helpful for people to get some better performance - however - the core GPS issues need to be addressed by Samsung.
I hope people will refrain from saying "It's perfect now!" and let up on Samsung. Unless you know what what the following are you're tweaking settings blindly and declaring victory: ephemeris, PDOP, SBAS, WGS-84, 2D fix, 3D fix (And the conditions one is chosen over the other.) and finally SA
I'm betting this phone would never achieve a fix in an SA environment! It's also clear that the person(s) who originated this information knew exactly what they were doing..!
If anyone is interested in learning how GPS works there are tons of great resources on the web that Google will point you to. Of course they're written for all sorts of different levels.
In short, the above settings may help, but please don't become convinced that things are "fixed"!
I'd suggest you read my posts on the subject:
http://forum.xda-developers.com/showthread.php?p=7244888#post7244888
http://forum.xda-developers.com/showthread.php?p=7289539#post7289539
@haydonxda - I agree that this does NOT address the potential problem that the firmware and/or hardware is inadequate! And, we should put pressure on Samsung to fix this issue. However, the phones have already been produced and I'm just trying to do the best with I have.
@Shadow77895 - thanks for the info. Added a bunch of further information after looking into your posts and references from them.
Try this fix (from 4pda.ru), working on Galaxy S, root access required:
$su
#cat /data/gps/secgps.conf > /sdcard/secgps.conf
#rm /data/gps/secgps.conf
#reboot
After reboot, new (correct) secgps.conf appears.
At your own risk!
shaneaus said:
NEW INFORMATION!!!
ALSO! Check out this page: http://www.pool.ntp.org/en/use.html:
As pool.ntp.org will assign you timeservers from all over the world, time quality will not be ideal. You get a bit better result if you use the continental zones (For example europe, north-america, oceania or asia.pool.ntp.org), and even better time if you use the country zone (like ch.pool.ntp.org in Switzerland) - for all these zones, you can again use the 0, 1 or 2 prefixes, like 0.ch.pool.ntp.org. Note, however, that the country zone might not exist for your country, or might contain only one or two timeservers. If you know timeservers that are really close to you (measured by network distance, with traceroute or ping), time probably will be even better.
Find your optimal pool server here: http://www.pool.ntp.org/zone/north-america
For US the optimal server is: us.pool.ntp.org
Reference other threads I (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=731462) I recommend you do the following:
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
If you are NOT in the US go to here: http://www.pool.ntp.org/en/use.html and look at the links in the center of the page to navigate to the closest pool to your geographical location and use that pool for the top server entry.
Click to expand...
Click to collapse
How do you use the text editor in Root Explorer. I can see the text but it won't allow me to edit it.
Hello, the code:
*#*#1472365#*#*
starts a GPS Test Application.
The settings inside this application are only for this application.
You can test your GPS in different modes.
But the settings are not relevant for other applications.
It is a simple illusion that it helps to manipulate this settings.
GPS is very time-dependent.
And:
I don't know where we can change the default GPS Mode/s...
So when I walk outside my office there are like 7 satellites, and I still cannot get a lock. This is sad.
Out of the box it worked great, navigated from BB to my house with relative ease. Inside my house when I showed my parents it worked great. I rooted and deleted some ATT apps. I have yet to get a lock.
I have also changed the NTP servers and no dice. This is pretty saddening performance.
I still don't get why my Nexus One, sitting right next to my Samsung Captivate, is able to get a aGPS location (via My Location in maps) that is pretty damn accurate despite not having a GPS lock and my Captivate is unable to even get an aGPS location and just says my location data is temporarily unavailable.
Nexus One: Can get approximate location very easily
Samsung Captivate: Cannot even get approximate location using WIFI/Cell Towers.
Foursquare never knows where I am until I go outside in the middle of a parking lot. This is BS.
Won't anyone try GPS NMEA MONITOR App and see if the data sentences are correct? If the GPS chipset is putting out the correct Lat/Lon, then you can fiddle and fiddle what Captivate does with the information
Has anyone tried to contact Samsung about the issue yet? I tried yesterday and was on hold for an hour and half and then my call dropped. I'm joint to try again today.
SkyHook isn't a "feature" persay, it's a corporation: http://www.skyhookwireless.com/
Same one Apple uses. Not sure exactly how it works but they do wardrive and use WiFi and triangulation to pick up your position as well, so leaving that OFF will perhaps be better for calibrating your GPS settings, but you certainly want it back ON when in normal use.
TexUs said:
SkyHook isn't a "feature" persay, it's a corporation: http://www.skyhookwireless.com/
Same one Apple uses. Not sure exactly how it works but they do wardrive and use WiFi and triangulation to pick up your position as well, so leaving that OFF will perhaps be better for calibrating your GPS settings, but you certainly want it back ON when in normal use.
Click to expand...
Click to collapse
What kind of aGPS does the Nexus One use? I tried to dial the code and it didn't bring up the same menu on the Nexus (it may be different). My Nexus is great at figuring out where I am without a GPS signal.
I changed all my settings last night and it seemed to fix the issue. I was getting a lock within 10 seconds or less. Now I cannot get a lock with the exact same settings and reboot. Has anyone contacted Samsung over this? Anyone get an answer from them? I love this phone but the GPS issue sucks.
Every time I try one of these new fixes it seems to work but then when I go somewher else it is broken again they need to fix this asap. I use that feature a lot
superscientific said:
I changed all my settings last night and it seemed to fix the issue. I was getting a lock within 10 seconds or less. Now I cannot get a lock with the exact same settings and reboot. Has anyone contacted Samsung over this? Anyone get an answer from them? I love this phone but the GPS issue sucks.
Click to expand...
Click to collapse
I just got off the phone with Samsung galaxy s support. They knew nothing!!!!!! Said I was the first one to call with the issue.
I'm thinking about returning the phone... GPS is the most important part of a smartphone to me... I'm very disappointed
Jreitnauer7 said:
I just got off the phone with Samsung galaxy s support. They knew nothing!!!!!! Said I was the first one to call with the issue.
I'm thinking about returning the phone... GPS is the most important part of a smartphone to me... I'm very disappointed
Click to expand...
Click to collapse
I don't know about most important but I agree, it's very important. This HAS to be fixed
Jreitnauer7 said:
I just got off the phone with Samsung galaxy s support. They knew nothing!!!!!! Said I was the first one to call with the issue.
I'm thinking about returning the phone... GPS is the most important part of a smartphone to me... I'm very disappointed
Click to expand...
Click to collapse
Don't give up hope, i'm sure that guy doesnt know anything. Engadget and a few sites are aware of the issue and i'm sure Samsung took notice. i'm sure a firmware fix is in the works.
Location
I have tried all the settings. And I don't really notice any difference. I live in the heart of Manhattan, NY., so I am sure roaming around int he concrete jungle trying to get a lock surely has a lot to do with my GPS issue. I do however, get a lock in every setting that has been written up in this forum, and other forums. The difference to me is hardly any, since it always takes many minutes for me to get a lock. I never have used any other GPS device since living here in the city, so I would like to ask other who live in a large city if it is taking them several minutes as well? Because it seems as though people are saying it is taking them only seconds to lock on. Hmmm.....
I'm currently travelling abroad and I'm therfore on roaming with data traffic disabled. I experience that the GPS is unable to find my position under these conditions and remains on the last known position (or it might take even longer than the few minutes i was willing to wait).
Whereas with data enabled or wifi i get a really fast lock.
Can anyone confirm this behaviour. Imho it should also be possible to get a lock (although slower) without any data connection. At least this is the way it works on my ios devices. It might take a minute or two but it works.
Any thoughts/experiences on this?
Some_One_Else said:
I'm currently travelling abroad and I'm therfore on roaming with data traffic disabled. I experience that the GPS is unable to find my position under these conditions and remains on the last known position (or it might take even longer than the few minutes i was willing to wait).
Whereas with data enabled or wifi i get a really fast lock.
Can anyone confirm this behaviour. Imho it should also be possible to get a lock (although slower) without any data connection. At least this is the way it works on my ios devices. It might take a minute or two but it works.
Any thoughts/experiences on this?
Click to expand...
Click to collapse
If the phone's been moved a dramatic amount of distance, the GPS almanac data will be really off. The data/wifi connection helps it locate your position and give the map a hand in finding you.
If you can get data somehow, you can try getting the "GPS Status and Toolbox" app from the Market, and then one of the menu options, perhaps advanced, is to download the GPS almanac data. That should give you quicker locks.
distortedloop said:
If the phone's been moved a dramatic amount of distance, the GPS almanac data will be really off.
Click to expand...
Click to collapse
It was only a few hundred meters from the last known position. That's why I'm a little bit concerned?
Thanks for the tool tip will definately have a look at it.
Some_One_Else said:
It was only a few hundred meters from the last known position. That's why I'm a little bit concerned?
Thanks for the tool tip will definately have a look at it.
Click to expand...
Click to collapse
Oh, yeah, that sounds like a problem. Even several miles shouldn't make that big a difference.
go to starbucks or some restaurant/bar/cafe with free WiFi
then use the phone there, and turn on GPS to get it updated
I was experimenting a little bit today and it seems to me that this is primarily a google maps problem.
It seems that google maps falls back to the last known position if you have no gps fix. For a strange reason however this last known position is not neccesarily the effective last known position but the last position when I had used google maps with an active internet connection position (which makes no sense imho).
This does not happen always and as long as you have an active data connection you will probably not run into this issue.
Some_One_Else said:
I was experimenting a little bit today and it seems to me that this is primarily a google maps problem.
It seems that google maps falls back to the last known position if you have no gps fix. For a strange reason however this last known position is not neccesarily the effective last known position but the last position when I had used google maps with an active internet connection position (which makes no sense imho).
This does not happen always and as long as you have an active data connection you will probably not run into this issue.
Click to expand...
Click to collapse
That makes some sense, since Google Maps relies on WiFi for it's initial fix if you have the enhanced location settings checked on.
Not really, does it? Example:
Pos1: wifi, hotel no GPS
Pos2: showing Pos1, after GPS fix showing correct position
Pos3: showing Pos1 (i would expect Pos2 now) after GPS fix showing correct position
Pos4: showing Pos1 again, whe no GPS fix
i would expect it to always show Pos(n-1) when there's no GPS fix and not always again Pos1. This is the way it works on ios devices which i think is correct.
Further i noticed that the blue circle (that should br really big if position is uncertain) does not grow respectively reflect this uncertainty by its size.
Therfore i guess: --> Defect in google maps 5.0?
Some_One_Else said:
Not really, does it? Example:
Pos1: wifi, hotel no GPS
Pos2: showing Pos1, after GPS fix showing correct position
Pos3: showing Pos1 (i would expect Pos2 now) after GPS fix showing correct position
Pos4: showing Pos1 again, whe no GPS fix
i would expect it to always show Pos(n-1) when there's no GPS fix and not always again Pos1. This is the way it works on ios devices which i think is correct.
Further i noticed that the blue circle (that should br really big if position is uncertain) does not grow respectively reflect this uncertainty by its size.
Therfore i guess: --> Defect in google maps 5.0?
Click to expand...
Click to collapse
I just checked on mine to confirm, but for me I recall Google Maps ALWAYS opens to the last position I was on with the app open, not my current position. It's cached for sure. Even with WiFi off just now, it opened to that, but within under a minute it jumped to my actual position via the actual GPS.
I wonder if others see this too or if my HTC Sensation 4G is broken.
When I'm in Google Navigation I often see the position 200 ft east of the highway.
I might add that I run the phone w/o a data plan so I'm loading the plan over WiFi and then start driving. It does not seem to make much of a difference if I wait for a stable GPS fix or just start driving an let it fix on the road.
The behavior is very annoying, as the Navigation app grabs on to parallel or incoming side roads and reroutes all the time, wasting lots of battery and heating up the device.
PlanBForOpenOffice said:
I wonder if others see this too or if my HTC Sensation 4G is broken.
When I'm in Google Navigation I often see the position 200 ft east of the highway.
I might add that I run the phone w/o a data plan so I'm loading the plan over WiFi and then start driving. It does not seem to make much of a difference if I wait for a stable GPS fix or just start driving an let it fix on the road.
The behavior is very annoying, as the Navigation app grabs on to parallel or incoming side roads and reroutes all the time, wasting lots of battery and heating up the device.
Click to expand...
Click to collapse
Do you have a case on your phone? If so, try the app without the case to see if you get the same results.
I get about 20 ft error (average). But it can jump up to 50 or so. But I have a MIUI installed. Also adding that I am on a data plan and I believe using cell towers in conjunction of gps narrows down the error.
No case
Thanks, really good question, but my phone is naked so to speak. I don't use any case.
Unfortunately I have learned that Assisted GPS (AGPS) is a feature that does not work with cell towers, but with a data connection. Only if a data connection is present can the helping hand of assisted GPS (search Wikipedia for assisted GPS) work to find you a faster GPS fix.
Do you use Google navigation and do you see similar issues, like position jumping off the highway and attempting to enter the highway from a side road?
PlanBForOpenOffice said:
Thanks, really good question, but my phone is naked so to speak. I don't use any case.
Unfortunately I have learned that Assisted GPS (AGPS) is a feature that does not work with cell towers, but with a data connection. Only if a data connection is present can the helping hand of assisted GPS (search Wikipedia for assisted GPS) work to find you a faster GPS fix.
Do you use Google navigation and do you see similar issues, like position jumping off the highway and attempting to enter the highway from a side road?
Click to expand...
Click to collapse
Once and a while but I cannot reproduce it.
You can try some of the fixes from crypted in the dev section. Just keep a backup of your gps.conf file if you want to test it. But the fix is for AGPS use.
What you can try is possibly sygic, but it's not free. I think its like 17 bux. But you can try it for a week.