I am looking for device's location, I used the code provided by google (https://github.com/googlesamples/android-play-location/tree/master/BasicLocationSample) but it seems working differently if in different devices. The two devices are Samsung Galaxy Ace Plus 7500 (S7500) and HUAWEI Y530-U00, I used GPS and 3G, the result was a very big location difference (about 300 or 400 meters). I used FINE location to perform my location but it seems the same.
Another problem is about S7500 which seems to update his location only if an app require internet, so I have to open an app and after check again location.
I would know if 2 people are near but with an approximation of about 50 meters, how could I get it?
Thanks in advance!
Related
I'm doing a app to collect pure GPS locations.
So I choice use locationmanager whit ACCESS_FINE_LOCATION.
I don't want use google play services to locations because, I believe, it joins locations from various providers without user control.
I want a specific app to test the device GPS chipset, so I want only GPS locations no matters what time it become ready.
I do a app as described and it works fine in my cellphone Xiaomi Redmi S2 whit android 8.
But in a cellphone Quantum MUV with android 7 it don't get any locations.
Somebody knows some specific issue about location manager running in android 7 or in Quantum MUV cellphone?
We have a ReactNative app, running on both iOS and Android.
We developed our own native module for GPS updates.
On iOS, it's working OK !
On Android, we're using FusedLocationProviderClient.
My problem: in some very rare cases on android, less than a few % of our GPS data, we see GPS data with correct latitude, but longitude keeps jumping around the real one (e.g. this seems to happen on some Samsung S9+)
See this screenshot
This bug only last a few minutes, then seems to resolve on its own...
Has anyone encoutered this bug too ?
If so, how did you fix it ?
(note: I can add code samples if you think it can help, but I'm having big difficulties reproducing this bug myself, so I doubt it's useful in this case...)
GPS takes awhile to lock, and depending on the phone, it can take quite awhile and be unreliable. The best thing you can do is check the accuracy that is reported, and also live poll the user's location when they open a relevant activity so by the time you need the location, it most likely has an accurate lock.
Also if needed, ask the user to apply their highest location accuracy settings. Details on how to do this can be found here
GPS takes some time to latch, and there should be at least 3 satellites to be able to latch for the device, if the user is indoor, it is nearly impossible to latch.
You will have to check for the accuracy, on testing I have found that if accuracy value becomes 2.9 (may be different on different devices, but till now I haven't seen) then your device location is set.
Or give some time to devise and record coordinates when you think it's feasible depending upon accuracy.
Hope this may help you...
If I am not wrong, the only way Google can know my location is through my cellphone. This means that if my cellphone is showing the correct location for me, there seems to be no reason for computer to show the different location. (Synchronization across devices, refreshing etc has been done several times) However, what I see is strange to me. My location on mobile phone is different (and inaccurate) than my location on the desktop computer. The locations show the same area of city but they are separated by around 100-200 meters. My question is, if the Google map is anyway fetching my location using my cellphone, why is it showing incorrect location on my pc? Thanks in advance.
Most smartphones are equipped with a gps devices.
This allow accuracy unlike PC which most don't have a gps device.
Google Maps website uses permissions to your location and most likely other web browser location information, but they will never get as accurate as devices.
I've found the opposite to be true. I have a more accurate location reading using google maps through my PC than on my smart phone. The location, time last online etc . . is more accurate on PC.
This is a strange issue which mostly appears on Samsung devices but I cannot confirm its only on Samsung.
My app won't get or update to the correct location fix. It listens to GPS, network and cell providers but the location fix I get is still outdated and inaccurate sometimes the fix is like a day earlier.
I thought it might be a bug in my code but then I opened other apps (Yelp, etc...) and they also have the same problem.
I then open Google Maps and the location is perfectly accurate and up-to-date.
Is this an Android platform bug? Do Maps use a different internal location source provider? Has anyone dealt with this issue before and can provide a solution?
I ran into the same issue.
It is an Android platform bug and it seems that this is an open issue that Google knows about:
https://code.google.com/p/android/issues/detail?id=57707
It is randomly happening.
Google maps is working because their location is based on Google services (Fused Location) which you can also use.
But they also have a bug with the january 2014 update: if you are outside and request a fastest location update rate (e.g. every second) and you are connected to the both network and gps receiver, you will receive a new location only at around 10 seconds even if gps is connected.
They ruined my app which used to work fine with this update and still not fixed to this day!
So what you can do is wait for the fix or use google location service fused location if it fits for you!
Go to settings>wifi>advanced and turn off ALWAYS ALLOW SCANNING
I had a strange encounter once: The location on the phone's map application and even my application was wrong by a very large delta. As in it was quite off the actual location. Is it something many have encountered or some bug with my device ? What is the approx probability of this happening (from those who have tested this bug) ?
I am using a Samsung Galaxy SII with ICS and my application fetches info from GPS_PROVIDER.
You might have an encountered a cached location if the maps application couldn't get a fix on your current location. For getting up to date locations in you app take a look at this question here
It's pretty normal for my location to be off by a large amount for a few seconds after a device turns on, until the radios can get a fix.
I have seen errors of more than 10000 km. I was looking at network fixes which come from cells and wifi only, no gps. The fix put me in England (UK) somewhere even though I was at an outlet mall in California (US). My guess is that someone had moved their wifi server from England to California and the Google WiFi database had not updated itself yet. I had a few more errors like that but not as spectacular, only 1000-5000 km reporting locations in other states of the US.
Network fixes based on cell towers will usually be 1 km off and are often 10 km off. These are based on the cell tower seen by the phone, and in hilly terrain you can often miss the closest cell tower and grab one that is on a high location a few km away.
GPS fixes also can have errors, but usually less than 1 km. These errors mostly come when some GPS signals are blocked by hills or buildings or reflected off nearby hills or buildings.
I have seen all of the above when testing Android phone positioning. Not all phones will behave identically, the quality of the GPS implementation (chip choice, rf design) can make big differences in performance.