-
Notifications
You must be signed in to change notification settings - Fork 27
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
'Error Invalid Geo coordinates(395.672220,151.008035). Endpoint:venues/search' error message #94
Comments
Have the same problem, unlocked Pre+ from uk O2, running WebOS 2.1, using it in Argentina, Buenos Aires. |
same problem here in Brazil. US phone, coordinates slightly different but still very off. It could be a problem with webos or the gps hardware |
Anyone were able to fix or workaournd this? |
It seems to be a problem with WebOS, maxigmv. I am not sure how we can report it, but it makes Google Maps and other geo-aware apps fail in similar ways. I am trying to contact an internal dev person |
Same problem here in Brazil (Salvador, BA). I'm using a US unlock HP Veer. The GPS works fine with other apps. Any suggestion? |
Same problem with foursquare, facebook and google maps here in Brazil. Any news? |
I finally realize what's happening with foursquare and other apps that use location services. The problem is with google services activated. I don't know why google service provides allways location for origin country of phone. For example, my Veer is from USA and i'm in Brazil. Google services provides me a wrong latitude for Brazil like 416.502... (for Brazil this should be -12.5...). The longitude is allways correct (with or without google services activated). So, to use foursquare for example (no problem with app) I first get a real position from GPS outdoor and then can use the app. I know when go indoor gps will not capable to get any sign from satellite but I will have a last coordinates valid. The apps shoulb works, of course without precision. This is not a solution for the problem but is possible to use the apps in some times. I hope this comment help. |
Yes, I have the same here. My longitude is ok, but my latitude is showing something like 399.459 N. But, I don't get it. How you get the real position from GPS? With a different app? |
No, i simple got outdoor, wait for a moment and got a real position from GPS. The google services location must be disabled. Only GPS shoud be enabled. Of course when you go inddor the GPS will don't work but you will get the last postion acquired allowing the apps use it. P.S. I'm not using no special program to get GPS signal. At first time you do that can last a little long, but not too much. Another point is when/if you need to restart your phone you need to accquired GPS signal from outdoor again. The phone clear the last position when restart. |
Simplely got outdoor and wait for a moment (at first time you must wait a while, but not too much). The google services should be disabled. Only GPS must be enabled in location services. I'm don't using different app to get GPS coordinates. I use foursquare normally outdoor and not much precisely indoor, but it's works. Apps who is integrated with google services will not work. Even in foursquare i can't tap in a location to be showed in goolge maps since the apps needs google services that is turned off . I hope help you. |
MOSF isn't the wrong lat/long data being provided by the local telco in a format WebOS can't parse for southern latitudes? Was it launched in Australia? |
rbanffy, I don't think so. That problem also is happening in Australia, India, China and other countries (i read in some blog), not necessarily in south hemisphere. I could realize that problem when i tried to use google maps mobile and i was presented with a message "Google Maps is not available in your country. US version shown.", so i understood that wrong latitude is for north hemisphere only. Really weird. How i worldwide gsm phone have this limitation? I hope help you. |
I got this error while refreshing places tab, can not checkin at all due to this error. The actual geo coordinates should be 33.8245,151.0078.
The text was updated successfully, but these errors were encountered: