-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not find the location of the GPS. #27
Comments
For me, too. Tested on Nokia C5-00 5MP. I tried to get the location by a short walk outside and also from inside the house (in an attempt to get an error message or other feedback), in both cases the red arrow representing my location did not appear. I installed the debug build from this Issue, the s60maps_log.txt file is attached. Thanks a lot to the developers! Long live Symbian :-) |
First I recommend you to read about GPS in Wikipedia. Also check out your phone manual ("Positioning" section). You can find it here:
I hope it can help you to understand how GPS positioning works and will reduce the number of questions and misunderstands.
For retrieving location S60Maps uses only internal GPS (if exists and enabled). Network connection (e.g., from operator or wifi) used for map tiles dowloading.
GPS doesn`t work indoors. For better signal from satellites go to open space.
S60Maps officially supports only for Symbian 9.1-9.4. Therefore I can`t guarantee that it can works on newer phones.
You are right. I didn`t found any problems in log you provided. However application worked only for 3 minutes. This may be not enough for retrieving location, especially for "cold" start of GPS. Note that usually it may takes up to several minutes. Partial position recieved in log means that GPS device is recieving signal from GPS satellites, but not obtained phone`s location yet. Besides lack of time there may be other reasons:
Moreover for make positioning work better you may enable A-GPS method (note that it uses network connection). Checking GPS statusYou may check GPS status in phone service menu. Go to If you see In addition, you can view satellites signal strength graph in Otherwise if signal is low or there is not enough satellites, you will see image like this. |
Thanks for your answer. Please note that I wrote only the 2nd message above, not the first. I know how GPS works. (I wanted to see if an error message will appear or differences in the log when there is certainly (almost) no GPS signal, so I tried at home). Regarding the partial GPS data, I tried again for about an hour of driving in and out of the town (slow and fast driving), on a sunny day. the phone was located under the windshield, with no success. So I checked the GPS status, and it seems that the device cannot succeed to see enough satellites or the signal is weak, so no fix. As you mentioned, I think the A-GPS doesn't work. Since supl.nokia.com doesn't exist for several years, I was used supl.google.com (and can navigate with Google Maps for S60), but since a few months ago Google Maps can't find my location anymore, so maybe google has changed something. |
I have also installed SSL update, but seems that google server does`n work on my phone. |
My two-cent contribution (using Nokia E72 s60v3 FP2 to this day): I first run Google Maps (v3.2.0, because this lets me use the Landmarks database...) until the position is determined, which is rather quick. Then I close Google Maps and open any other application that needs GPS: the lock will happen very fast. This works for me both with S60Maps, Mapnav and the standard Nokia Maps. |
Another bit of "black magic" regarding the use of the GPS in my E72: in "positioning methods" unmark "Wi-Fi/Network" (and obviously "Bluetooth GPS" too) but leave the other three options marked. With these settings I can get a reliable outdoors GPS lock without A-GPS (ie with the phone in offline mode) but it may take a while depending on the orography around you (it could be 30 minutes or more). |
Seems that your phone can connect to google SUPL-server using new SSL sertificates. Try to set |
No description provided.
The text was updated successfully, but these errors were encountered: