Related
Remember the time before HTC launch HTC Diamond/Touch Pro? Everywhere in the news and also HTC's own website stated that the builtin GPS is an A-GPS. HTC even boost about it's A-GPS feature. If you have read the product specification for HTC Diamond, the GPS is stated as A-GPS.
Now, if you go to HTC's website, HTC has changed the specification from A-GPS to Internal GPS (for both Diamond and Touch Pro).
Of course we know that it is has the A-GPS feature, but it is not supported like Nokia (where it has its own server, supl.nokia.com for the A-GPS to connect to). HTC does not provide such feature for us. So before the product is released, tell everyone that it is offering A-GPS (which HTC won't support), then when it is released, quietly change the specification to Internal GPS.
It's a bit more complicated.
For the record, I really would like to point out that "AGPS" can stand for both Assisted and Aided GPS. Most people do not know there is a difference. I assume you might. However, I digress...
The HTC Raphael as well as almost every single handset designed, manufactured and sold world-wide is AGPS enabled. Luckily for us, most HTC devices go a step further and provide 'hybrid' GPS front-ends.
In the Raphael's case, the GPS RF front-end, GPSOne, is a part of the MSM platform and is a hybrid GPS engine which means it is capable of Aided (in this case 'QuickGPS'), Assisted (Network Aided) and fully Autonomous GPS. The Raphael is compliant with OMA SUPL and 3GPP location standards.
The people you should be complaining to is not HTC but rather your network operator who may or may not be allowing network location data available via the user plane.
The AGPS on the HTC Fuze I am using on North Americas' AT&T is working just fine.
Nokia happens to be VERY proactive about location information and have made it clear they wish to be at the forefront of this market enabler.
programatix said:
Now, if you go to HTC's website, HTC has changed the specification from A-GPS to Internal GPS (for both Diamond and Touch Pro).
Click to expand...
Click to collapse
So? In strong consideration to the many laymen out there who have been falsely led to believe that A-GPS is 'inferior' to GPS then this may be dumbed-down BUT smart marketing by HTC. With the crap out of other companies and much misinformation found on the internet, too many people now falsely believe that A-GPS denotes an 'inferior' hardware device that ONLY derives location from that of the cellular system (triangulation from cell towers being the popular buzz) while lacking the hardware to derive a location from satellites....
We here should particularly know better that the HTC Qualcomm devices have the integrated GPSOne A-GPS chipset. That denotes an ability to derive the location, downloading of satellite ephemeris data, and possibility to refine location precision via GPS satellites and assistance or fallback to a Network Assistance server.
programatix said:
Of course we know that it is has the A-GPS feature, but it is not supported like Nokia (where it has its own server, supl.nokia.com for the A-GPS to connect to). HTC does not provide such feature for us.
Click to expand...
Click to collapse
As it is practiced it's down to the responsibilities of the carriers to support their subscribed client with the Assisted mode from THEIR Network Assistance Servers.
programatix said:
So before the product is released, tell everyone that it is offering A-GPS (which HTC won't support), then when it is released, quietly change the specification to Internal GPS.
Click to expand...
Click to collapse
Dude, I politely declare your topic to be conflated FUD.
move on...nothing to rant about here.
So is there any way we can tell our phone's to connect to Nokia's AGPS Server?
Don't get me wrong. Right now I'm pretty happy with my GPS since it locks faster than my Lowrance GPS in my car and it locks onto just as many satellites.
If I could cut the time down to several seconds instead of 30 seconds locks, I'd be even happier than I already am but I'm actually quite content since it's already very fast.
Harvey,
It would be almost impossible.
The SUPL middleware clients are different between the OS (Symbian vs WinMo) and are based on platform and handset.
-Op
Operation619 said:
Harvey,
It would be almost impossible.
The SUPL middleware clients are different between the OS (Symbian vs WinMo) and are based on platform and handset.
-Op
Click to expand...
Click to collapse
I actually got it working with Da_G's help. It's very fast now. Maybe 10 seconds or less every time even without extra.bin from QuickGPS.
a-gps works for me
a-gps is good for those times when you drive through a tunnel and the gps is cut off for a mile or two, your phone has a chance to redeem its lack of satellite reception by giving a +/- 2000 feet estimate as to where you are.
It would be better though to use the phones accelerometer to create a cheap "inertial navigation system" (a handy backup system used in airplanes) by using last known location before GPS fails + detected movements by accelerometer to determine current location. This would be far more accurate than triangulation. Though unless I am missing something, the software simply isnt there and would take a lot of work to develop
Hmm, I think at the least you would need to strap your phone to the vehicle to ensure it stays at the same angle, etc. while moving.. and then it would become wildly inaccurate the moment you turned off course a little.. without a gyroscope or compass.. doh! but i like that idea
Interesting topic here, wish I could join in an intelligent manner but alas, my gps refuses to connect to anything, let alone satellites. My point is this, I've done extensive searches to try and get the thing to actually work say nothing about working in a stable way and every one of the suggestions whether it be registry hacks, advance config tweaks or programs suggested to shut off agps because it only hindered and really didnt work. What's that about? The bottom line is the gps on these phone's collectively if compared to the iphone or any other comparable device is deplorable period. My wife has an iphone and the gps works flawlessly. My friend has the touch pro for sprint and it works flawlessly. What is going on?
sorry not really on topic, just a bit frustrated. I am curious why everyone seems to think it needs to be turned off though...
Im on AT&T too in North america and my GPS takes a good 5 minutes to find satalites, are you using stock radio and rom or did you change the radio?
Operation619 said:
It's a bit more complicated.
For the record, I really would like to point out that "AGPS" can stand for both Assisted and Aided GPS. Most people do not know there is a difference. I assume you might. However, I digress...
The HTC Raphael as well as almost every single handset designed, manufactured and sold world-wide is AGPS enabled. Luckily for us, most HTC devices go a step further and provide 'hybrid' GPS front-ends.
In the Raphael's case, the GPS RF front-end, GPSOne, is a part of the MSM platform and is a hybrid GPS engine which means it is capable of Aided (in this case 'QuickGPS'), Assisted (Network Aided) and fully Autonomous GPS. The Raphael is compliant with OMA SUPL and 3GPP location standards.
The people you should be complaining to is not HTC but rather your network operator who may or may not be allowing network location data available via the user plane.
The AGPS on the HTC Fuze I am using on North Americas' AT&T is working just fine.
Nokia happens to be VERY proactive about location information and have made it clear they wish to be at the forefront of this market enabler.
Click to expand...
Click to collapse
ATT Northamerica here as well. I've tried nearly every radio, every rom and none of them have been good experiences although... I did manage to get it working somewhat a few ROM updates ago. Don't remember how I did it though because it was before I realized it was going to be a huge issue for me.
I don't think it matters what radio your using quite honestly. Nor do I think it matters what drivers your using or ROM your using... I think it has something to do with the hardware or the implementation of the chip through either all of the above or specific gps programs.
I could be wrong...actually I probably am wrong. All I know is I've owned several Fuze's which I returned for various reasons and all of them were terrible experiences with GPS.
If you look at the proposed solutions here on the forum's they range from simple to far fetched to just plain ridiculous. Most of them are just explanations of what happened to work for the person posting and most of the posters aren't even sure what they did.
Sounds like a hardware/foundation level driver issue to me.
Operation619 said:
The AGPS on the HTC Fuze I am using on North Americas' AT&T is working just fine.
Click to expand...
Click to collapse
does that agps using at&t's networks work with tomtom if so which version do i need. thanks
Da_G said:
Hmm, I think at the least you would need to strap your phone to the vehicle to ensure it stays at the same angle, etc. while moving.. and then it would become wildly inaccurate the moment you turned off course a little.. without a gyroscope or compass.. doh! but i like that idea
Click to expand...
Click to collapse
This much is true, however with a little thought we could probably convince the system to "trust" that we are still on the road, and limit the accelerometer's influence on the foreward / backward motion (the accelerometer could be set to only interpret change on one axis). You are right, the traditional inertial navigation system requires gyros and a compass, vaccuum pump driven, but in a vehicle on the ground we have far less variables. The system wouldn't be perfect, but it would be a lot better that the current system, which is crude triangulation
ya the gps on the touch pro/fuze is complete BS. there is definately something wrong with the agps. Whenever i had agps enabled it would either not connect at all or connect and then quickly loose satellite reception. when i disabled agps, it would get a lock after 2-3 mins minimum and then be fine. I had agps in my tytn II, nokia e71, and now my touch HD, and they all work fine. i just got the touch HD, and with agps enabled i can get a lock from a cold start in ~30 secs. plus this huge screen makes navigating a pleasure
i do have a question to ask everybody that might help this problem. when you click on tomtom after not using it for a day or two (as in cold start). from the tomtom home screen.... click on the signal bars in the lower right hand corner then click on the signal bars in the upper right part of the screen. does it show little balls with numbers in side them or not?
also what version is everyone using?
omaralt said:
ya the gps on the touch pro/fuze is complete BS.
Click to expand...
Click to collapse
An absolutely innane comment in light of others having it working and a previous statement in this thread concerning the Touch Pro working "flawlessly." Dude, don't post in a bubble and make the classic error of an absolute write-off when your particular item is failing. It is not all or nothing.
Mine works. Mine consistently works "flawlessly" and that is witnessing a data connection made each fairly fresh time the GPS is initiated and then followed by satellite reception within seconds to location deriving locks within 10-20 seconds. The Assisted portion of the A-GPS is functioning and assisting the GPS attain quicker satellite locks with updated ephemeris data from my designated Network Assistance server.
For those who have Raphael's where the internal GPS is unable to receive locks -- then first blame your carrier (who in North America are typically ultimately responsible to the software setups on their phones often to help push their own pay-per-use GPS software) and then secondly place some fault upon yourself for not finding the existing resolutions to work around the carrier implemented GPS limitations. The latter is understandable as there is plenty of misinformation around and posted solutions that are quite dated --> old guesses at a necessity to disable the Assisted modes....
By tobeychris on ppcgeeks, here are the working AGPS solutions for some North American CDMA carriers. Carrier specific CABs are listed. Similar resolutions exist for GSM Raphaels.
My experiences
I have lots of trouble with the GPS on a stock rom ATT Fuze. When I turn off a-gps and quick gps, then enable the windows mobile intermediate driver (the external GPS settings icon) with hardware on com4: baud 4800 and soft-port com6: and use 4800 baud EVERYWHERE I can, It usually works. With any other setting (mostly when a-gps enabled tho) it connects for 2 seconds then sets the hardware port to "(none)" in the windows mobile GPS settings and refuses (haha fuses) to do anything with the GPS again until I reboot. I would like to know exactly what the $%^*%$^ is going on.
walscobry said:
I would like to know exactly what the $%^*%$^ is going on.
Click to expand...
Click to collapse
As previously mentioned it is likely your carrier's fault for not adding an Assistance Server IP address to permit the assisted portion of the A-GPS chipset to properly function. That is why you can better attain a satellite lock when the Assisted mode is disabled but fail when the hardware first expects to download the latest ephemeris data from its non-existant Network Assistance server - 0.0.0.0 as the IP address or lack of carrier info thanks to AT&T).
Blame AT&T for 'crippling' (not fully implementing) the GPS features of your phone. Resolve your lack of an Assisted Server IP issue with searches and previously posted links.
Hello All,
Junior Newb here.
I'm thinking of purchasing an HTC Touch Pro(1) Sprint model from someone here. I am not planning on getting a sub from Sprint. I am purchasing the phone mainly to use as an GPS for when I am motorcycling as I do not have a mounted GPS on the bike. I am unclear on how GPS actually receives its signal? I have read and best I can decypher is GPS units gets their signal from various satellites. I have also read were various cell phone companies have their own spin on GPS software of their own creation? Am I going to be able to use Google maps on this phone and have it do what I want it to do? I am eons behind times,in case you hadn't guessed that by now. Also will the GPS be readable if I have the phone stuck in my chest pocket and pull it out going down the road? Can someone chime in on how long battery life would be with this scenario as well? I know the battery life listed in spec sheets are usually not even close in the real world.
Thanks,
Barry
Right!
GPS works by checking the different time stream data from several satellites - the receiver (in this case the phone) uses this to produce your position (and by changing position over time - speed).
Honestly - for 99.9% of people, this as it is - is useless. You then need to put this info into mapping software. Google maps is ok, but IMO itsnt very good for using while driving (prob much less for while on a bike!). Personally i use tomtom for in car and google for walking (so if you're checking your position & local roads, then riding - stop & repeat then google maps will prob be fine).
If you read more on the forums (and the web in general) you will come across 2 other "types" of GPS:
aGPS - assisted GPS - works by using your known position (roughly) from mobile/cell towers, this allows the GPS receiver to get a lock quicker.
quickGPS - this downloads the almanac data from the web so youre device knows where the satellites are. If you dont do this, it will download the data from the satellites themselves, but this takes longer.
Neither are any use on their own - they simply improve GPS lock times (from turning on, to having your position).
Battery life - depends on many things including your rom & radio, software, battery condition etc etc.
Remember - for google maps to work you will need a data connection (watch the cost if its not part of a deal).
If all you want is a hand held or bike GPS - then i think you're looking at a very bad choice in the touch pro! if you want a phone, pda, web browser, gps etc etc then it will probably do everything you want.
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.....
Well it seems the GPS on our Captivates has been improving over time due to adjusted Jupiter files, ROM updates, improvements in some leaked builds, and now a new GLGPS Daemon port, etc, but still seeing posts by lots of folks who still have trouble achieving good results. So, while the improvement quest continues, was thinking it might be helpful to have a common scoring or grading system for people to use when reporting on their gps results.
Would appreciate any comments on the usefulness of this, or agreement or disagreement with the descriptions. Just seems to me that currently it is often difficult to know what someone means when they say their GPS is good, best its ever been, or terrible.
(Note - to be most helpful to others please post your grade/results and anything you've done that has improved the gps performance.)
It would go something like this:
Captivate GpsGrade
A Common Way to Report GPS Effectiveness
Grade = A. Description – Performance is excellent at all times and very consistent. Applications such as Maps, Copilot, Google Nav, MyTracks always perform perfectly. Tracks as recorded by MyTracks consistently show the route accurately. GPS Locks are quick – under 30 seconds, and accuracy shows 5 to 10 meters or better as measured by lbstest, or GPS Test applications. When used for navigation, there is no drifting off of the road, no lag, and no overshoot of intersections. In short – its how we would want it to be.
Grade = B. Description – GPS function often works as expected, but occasionally does not. Usually no problem seeing several satellites and get locks within 30 seconds but always under a minute. Navigation apps are usable but sometimes there is a small bit of drift and sometimes will lag or show overshooting of intersections. Tracking via MyTracks is often accurate to the route taken, but sometimes off by a bit. Locks are sometimes lost but the system usually locks on again in just a few seconds. Accuracy often around 30 meters. Its not quite what we would like, but can live with it. Might call it pretty good.
Grade = C. Description – system achieves locks but often takes 60 seconds or longer. Locks are sometimes maintained while moving, sometimes not. Erratic performance. Can sometimes get Apps like Maps and Nav to work, but often have trouble with them or the system shows being on the next road or off the road. Routes recorded by MyTracks show inaccurate performance – route shown is close to the one taken but has occasional gaps with loss of lock. Accuracy is between 30 and 50 meters. In other words, performance may be good enough for location based services to be used, but not too useful for map or navigation functions. Mediocre.
Grade = D. Description – system sometimes gets a lock but cannot maintain lock. GPS Apps are not useable do to poor performance. In GPS Test or lbstest can sometimes see a couple satellites, but trouble getting a fix. Basically the GPS Icon is flashing pretty much the entire time. Awful would describe it.
Grade = F. Description – system does not work at all – cannot get locks, and cannot use any GPS Apps such as Maps or Nav, ever. Its just horrible.
good idea.
The problem with this, is most people have no idea how to properly test anything. For this to have any meaning, all tests should be conducted as follows:
Using multiple devices - not just a Captivate but another phone as well on another run
Not holding the phone in your hand - we know this can cause signal issues
Repeatable routes (testing on the same route)
Driving - walking does not allow for fast enough position change to reveal problems
No other apps running on phone - try to reduce any type of processor or storage contention issues
1. Mount device in car mount in the front windshield - other windows may have tint that interfere with signal reception
2. Launch Google mytracks - start driving after 10 seconds (fixed time for lock - equal for all)
3. Drive route with local and highway speeds and turns
4. Repeat with another device
5. Compare MyTracks recordings
Turn-by-Turn nav is a nice way to view accuracy BUT it has no way to record measurements. Comparing devices with a tool like Googles MyTracks is the only way to show that the captivate GPS sucks or not - maybe other phones suck too in certain environments.
This same methodology should be used before and after any mods as well - otherwise it is all hearsay.
alphadog00 said:
The problem with this, is most people have no idea how to properly test anything. For this to have any meaning, all tests should be conducted as follows:
Using multiple devices - not just a Captivate but another phone as well on another run
Not holding the phone in your hand - we know this can cause signal issues
Repeatable routes (testing on the same route)
Driving - walking does not allow for fast enough position change to reveal problems
No other apps running on phone - try to reduce any type of processor or storage contention issues
1. Mount device in car mount in the front windshield - other windows may have tint that interfere with signal reception
2. Launch Google mytracks - start driving after 10 seconds (fixed time for lock - equal for all)
3. Drive route with local and highway speeds and turns
4. Repeat with another device
5. Compare MyTracks recordings
Turn-by-Turn nav is a nice way to view accuracy BUT it has no way to record measurements. Comparing devices with a tool like Googles MyTracks is the only way to show that the captivate GPS sucks or not - maybe other phones suck too in certain environments.
This same methodology should be used before and after any mods as well - otherwise it is all hearsay.
Click to expand...
Click to collapse
Are there actually people that have GPS that is consistently accurate to 10 meters or less? I can't even get a lock like that standing in one spot on a sunny day. If I don't enable wireless networks, my GPS icon will flash forever.
ChaoticKinesis said:
Are there actually people that have GPS that is consistently accurate to 10 meters or less? I can't even get a lock like that standing in one spot on a sunny day. If I don't enable wireless networks, my GPS icon will flash forever.
Click to expand...
Click to collapse
Yes, many of us has GPS that works fairly well. I have had my phone since launch and running the stock GPS config.... it works OK.
My GPS is an A. I got a replacement and has worked perfectly since.
Sent from my GT-I9000 using XDA App
ChaoticKinesis said:
Are there actually people that have GPS that is consistently accurate to 10 meters or less? I can't even get a lock like that standing in one spot on a sunny day. If I don't enable wireless networks, my GPS icon will flash forever.
Click to expand...
Click to collapse
Results are extremely variable. Your phone sounds like mine. By trial and error I have gotten mine to an "A", but only by doing these four things 1) flashing new ROM - Assonance (5.0), 2) installing Da_g's GPS fix, 3) Removing the rear cover and just using my Bodyglove cover, and 4) when in the car plugging into car charger.
There are other solutions and reported good results from other ROMs and methods, but these are the things that work for me. I have done extensive testing with each of the four items, including MyTracks recordings, to validate the impact they each have. Good luck with yours - it IS possible to get a working system.
Mines grade b at most.
Sent from my SAMSUNG-SGH-I897 using XDA App
Where can I get this Da_G fix? I'm using Assonance 5.2 and it works fairly well - about a C+ or B I guess. I tried searching XDA for the Da_G fix and couldnt find anything
PixelPerfect3 said:
Where can I get this Da_G fix? I'm using Assonance 5.2 and it works fairly well - about a C+ or B I guess. I tried searching XDA for the Da_G fix and couldnt find anything
Click to expand...
Click to collapse
You can get Da_G's fix at the post below. Three options - I have been using the Google version and had good success with it.
http://forum.xda-developers.com/showthread.php?t=881941
I've owned a GSM Galaxy Nexus (Samsung i9250) with JB 4.2.1.
The one deficiency that I didn't initially notice is the lack of decent GPS reception.
My friend have a galaxy S3 take 30seconds or less for fix gps without wifi ou 3g. The nexus make maybe 10min GPS lock on its own (no Wi-Fi required) and then would keep the lock the whole time when the phone was in my pocket.
The GPS of nexus is, quite simply, broken. It takes, on average, 5-10 minutes to get a GPS lock when standing outside with a clear view of the sky and the phone in the palm of my hand. Sometimes it takes longer but usually I give up after 10 minutes because, strangely enough, I do have a life. Unfortunately, even after this GPS lock is achieved, it loses it easily. Putting the phone in my pocket will cause the GPS lock to be lost within a few minutes, typically.
Unfortunately, it appears that I'm not the only one with the problem. This is unfortunate because this means if I call Samsung asking for a replacement phone most likely my situation will not improve.
Strangely enough, if I enable Wi-Fi and are within the vicinity of some networks, I can get a GPS lock fairly quickly. In fact, even sitting here in my condo typing this, with Wi-Fi enabled I can get a lock within a few seconds by holding the phone near the window. The phone will only see 4-5 satellites, but that's all that is needed for a 3D lock. This makes a little bit of sense because WPS probably seeds the GPS subsystem with location data so it knows exactly where to start (vs. a cold or warm start).
After searching around a little bit I found a few suggestions. One was to shut off the phone and remove the battery for a few minutes, which seemed silly since this suggestion only temporarily fixes the problem. The second, that seemed to work for a few people, was to force a cold start and redownload A-GPS data, both of which can be done using GPS Status & Toolbox, an application I've used in the past and is pretty darn neat.
Unfortunately, performing the cold start (reset) and redownloading the A-GPS data didn't work out for me. I was still left in the same situation as I was before. However, using the GPS Status & Toolbox provided me with some additional information about the GPS problems. Apparently when the Galaxy Nexus is stuck searching for a GPS lock, usually it actually does see a whole boatload of satellites, but fails to receive any data from them.
GPS lock with Wi-Fi enabled. I don't even have a clear view of the sky since I'm indoors. However, I'm standing at a window:
Why does the GPS on the Galaxy Nexus not quickly receive the second and third parts of the GPS message from any satellites when Wi-Fi is disabled? According to the first screenshot above, it can clearly be seen that a number of satellites are providing adequate signal strength, but most are just stuck in the no info stage or have only processed the first GPS message. I wish I had an answer.
I suspect the problem may be due to inadequate RF shielding of the GPS receiver inside the hardware itself. Perhaps the GPS receiver is getting a strong signal but it's too noisy and the messages are chock full of errors and can't be processed correctly. This is really only speculation, though
I tried so many things, gps.conf etc..maybe is a hardware problem ? isnt the google location server problem..
Anyone have any suggestions or comments?
hoobinho said:
I've owned a GSM Galaxy Nexus (Samsung i9250) with JB 4.2.1.
The one deficiency that I didn't initially notice is the lack of decent GPS reception.
My friend have a galaxy S3 take 30seconds or less for fix gps without wifi ou 3g. The nexus make maybe 10min GPS lock on its own (no Wi-Fi required) and then would keep the lock the whole time when the phone was in my pocket.
The GPS of nexus is, quite simply, broken. It takes, on average, 5-10 minutes to get a GPS lock when standing outside with a clear view of the sky and the phone in the palm of my hand. Sometimes it takes longer but usually I give up after 10 minutes because, strangely enough, I do have a life. Unfortunately, even after this GPS lock is achieved, it loses it easily. Putting the phone in my pocket will cause the GPS lock to be lost within a few minutes, typically.
.
Unfortunately, it appears that I'm not the only one with the problem. This is unfortunate because this means if I call Samsung asking for a replacement phone most likely my situation will not improve.
Strangely enough, if I enable Wi-Fi and are within the vicinity of some networks, I can get a GPS lock fairly quickly. In fact, even sitting here in my condo typing this, with Wi-Fi enabled I can get a lock within a few seconds by holding the phone near the window. The phone will only see 4-5 satellites, but that's all that is needed for a 3D lock. This makes a little bit of sense because WPS probably seeds the GPS subsystem with location data so it knows exactly where to start (vs. a cold or warm start).
After searching around a little bit I found a few suggestions. One was to shut off the phone and remove the battery for a few minutes, which seemed silly since this suggestion only temporarily fixes the problem. The second, that seemed to work for a few people, was to force a cold start and redownload A-GPS data, both of which can be done using GPS Status & Toolbox, an application I've used in the past and is pretty darn neat.
Unfortunately, performing the cold start (reset) and redownloading the A-GPS data didn't work out for me. I was still left in the same situation as I was before. However, using the GPS Status & Toolbox provided me with some additional information about the GPS problems. Apparently when the Galaxy Nexus is stuck searching for a GPS lock, usually it actually does see a whole boatload of satellites, but fails to receive any data from them.
GPS lock with Wi-Fi enabled. I don't even have a clear view of the sky since I'm indoors. However, I'm standing at a window:
Why does the GPS on the Galaxy Nexus not quickly receive the second and third parts of the GPS message from any satellites when Wi-Fi is disabled? According to the first screenshot above, it can clearly be seen that a number of satellites are providing adequate signal strength, but most are just stuck in the no info stage or have only processed the first GPS message. I wish I had an answer.
I suspect the problem may be due to inadequate RF shielding of the GPS receiver inside the hardware itself. Perhaps the GPS receiver is getting a strong signal but it's too noisy and the messages are chock full of errors and can't be processed correctly. This is really only speculation, though
I tried so many things, gps.conf etc..maybe is a hardware problem ? isnt the google location server problem..
Anyone have any suggestions or comments?
Click to expand...
Click to collapse
Hoobinho,
I'm having the same problem.
I'm pretty sure it's software related, because 4.1.2 worked very nice with GPS. This issue started after 4.2, and continues with 4.2.1. I will roll back to 4.1.2 as soon as I have time to do it, and stay there until Google fixes it.