If I do Location.getAccuracy() I get a number of meters. Is that number a radius or a diameter? I thought it would be a radius, but Google's MyLocationOverlay uses that value as a diameter.
View 4 Replies
wanted to know that the accuracy value returned by the getAccuracy() is of which type radial accuracy or horizontal accuracy.
View 8 Replies View Relatedhow does "location accuracy" use a wifi network?
View 7 Replies View RelatedAs said in the Android Reference, the method getAccuracy() of android.location: "Returns the accuracy of the fix in meters. If hasAccuracy() is false, 0.0 is returned." But what does that mean exactly? The diameter or the radius? The Circular Error Probable (CEP), the 95-percentile or something else? I hope they are of the same type in GPS and GSM positioning. Does somebody know where these information are given into the system? As far as i know, are the GSM coordinates returned by a hidden Google API over a Web Service. So no chance to see an exact calculation. But where is the Accuracy of GPS calculated. I thought the GPS receiver only returns a dimensionless DOP value. And with Android 1.5 its not posible to read the NMEA sentences directly.
View 5 Replies View RelatedSuper happy with the Nexus One just minor issue is that on occasion - and not sure what triggers it - but the touch location seems to end being below where i actually touch on the screen, which of course causes erratic typing and erroneous screen clicks. A quick cycle of the sleep/power button (not turning unit off, just sleep/blank and back on.) seems to solve the problem.Hopefully an update will resolve this issue, as it seems to be a software issue.
Anyone have an accuracy issue? I just opened it for the first time and it shows my location as a good 1/4 mile away. Of course it does state accurate to 1400 meters.
View 5 Replies View RelatedHas anyone noticed the differences in using the two maps in terms of location accuracy? Specifically with GPS off. I don't expect either app to be extremely accurate in finding my location with GPS off, but what's odd is that Google Maps put's me about .25 miles WNW of my actual location while AT&T Maps put's my location .25 ENE of my actual location. You would think that the operating system determines the location and provides the app of that information, but that doesn't seem to be the case (since the two maps are showing different locations).
View 5 Replies View RelatedPhone settings: Location : Battery Saving (GPS off, using Wifi/network location only)
On Google Play Services 4.0.x - I get very accurate location small circle around where my house is.
After updating to 4.2.25 - I get a large circle - maybe the radius of an entire block / surface area of a cell tower coverage roughly
Uninstall the update to play services (back to 4.0.x) - get very accurate location again.
I am using a RAZR HD with 4.4.2 kit kat / CM11.
Did play services update broke my specific phone?
I would stay on the older Play Services but Hangouts and Maps keep bitching about needing to update it.
Does anyone know the proper interpretation of the accuracy measurements returned by getAccuracy()? For instance, are they calculated as:Circular Error Probability (meaning, if i understand correctly, radius of a 50% confidence circle)? Radius of 95% confidence circle? something else? In addition, what are the actual calculations that are used and how much can we rely on them? Does it depend on the source of the location estimate (GPS vs. network)?
View 1 Replies View RelatedJust a question for fellow users, how accurate is your GPS on your HERO? I turn on Google Maps and "my location" is hardly ever accurate.
View 25 Replies View RelatedHow much accurate are the coordinates received by the GPS antenna in the reality?I'm using the emulator but it doesn't work well with coordinates too much close is there nobody that have tested an application based on the package "Location" in a real device(I don't have a real one yet..) and knows how to answer me?
View 7 Replies View RelatedWith my location listener i get accuracy values about 30-100 m (being on an open field without annoying houses around me disturbing the gps signal). Why is that so bad? I thought you could get an accuracy about 3m with gps. And the Google maps applet for example has a much better accuracy. How can i improve the accuracy? I'm using the default gps provider. I saw you can create a Criteria object to get the best provider, but there are only the gps and the mobile phone net providers anyway - so it's some kind of senseless to get the location provider that way. is there no way to define the needed accuracy?
View 6 Replies View RelatedMy app has an issue where many players get bounced all over kingdom come when using GPS to get a signal. I had this issue with my G1 on occasion but not on my Nexus One. I am talking hundreds of miles from their real location. I changed the code to throw out anything that was not at least 500 meters accurate. My question is, if the location placement is hundreds of miles off, how reliable will the accuracy reporting be? Does it realize that it could be hundreds of miles off?
I am asking the community because I cannot reproduce the scenario with what I currently have so I can't test if my fix is meaningful. Does GPS know when its readings are that far off?
I'm writing a mapping application. In simple terms, it sends some info about the user's current location to a server when the user clicks on a button. I need the location to be absolutely correct, and when I first started to implement LocationListener, I found that it often wasn't. So I've used location.getAccuracy() to check the GPS accuracy, and warn the user - without submitting the data - if the location isn't accurate enough. Code...
View 3 Replies View RelatedIm working on an app that use gps My testing devices are Nexus One and Htc Mytouch 3g Slide
So does anyone know how to improve the gps accuracy?
I am developing a website which used W3C GeoLocation API to obtain users' position. I try to run the website in Android Emulator and use DDMS / geo fix to send the coordinate to the device. However the coordinate received is inaccurate.
For example, (22.377127, 114.095535) will become (22.370335, 114.08523353). I try to run some Android GPS example from Internet, and the results is just the same. I can certainly say that this is not my program bug. From my observation, it seems like some rounding problem.
I'm having a weird problem with GPS accuracy. Basically, I check the GPS accuracy in a background thread after the user clicks a report button, and show the accuracy in a progress dialog, changing second by second. (Code is below.) The following strange thing happens:
1. If the user clicks more or less immediately on the button after taking the phone out, accuracy is unsurprisingly pretty poor to start off with, say more than 100m. But the accuracy never really improves very much while the user is running the background thread. There is some improvement, but it's slow and it never gets very accurate. 2. However, if the user gets the phone out and then waits for several seconds *without* clicking on the button and running the background thread, and *then* clicks on the button, the accuracy quickly improves and becomes very good. When they click on the button, the accuracy shows up as fine - within the same length of time............
I am curious about the accuracy of the motorola droid GPS, before installing a golf app. Can these units pinpoint to within a few yards or is the area fairly wide.
View 4 Replies View RelatedHas anyone else noticed how far off google navigator is? I have used it a couple times and one time it was almost a mile off from the actual location I wanted to go to. Or am I doing something wrong?
View 13 Replies View RelatedWife and i use latitude gps to track each other. however the accuracy is not very good. It can show she is 2 miles from where she actually is. is there a tweek or another program to help make it more accurate?
View 4 Replies View RelatedWe are writing an application that uses acceleration sensor data to plot phone's movement in 3D. We are finding gross inconsistencies in the actual data output by the sensor. Also, sampling rates vary greatly from 8 to 200 millis. (using System.currentTimeMillis())
Specifically, when we try to draw a circle with G1 flat on the table all the time (filtering out gravity accel 9.8), most of the time we would get a plot of phone's position that is not a circle at all. Lots of times, it would be close to a straight line. Sometimes, it would start drawing an arc, but would not close the circle shooting off in a random direction.
We tried to eliminate the time variable, by substituting a constant time sampling rate (10 millis) to calculate phones position, but the result was very close to what we had before (shapewise). Also, the acceleration in Z direction when the phone is displaced lying flat on a table (XY plane) varies too by +/- 2 units which is a lot.
I do not think it is an error in our code, as we have checked it many times. If there were an error indeed and the accelerometer worked properly, we would see a consistently wrong depiction of the phone's movement. Unfortunately, repeating the same movement (circle) would produce sometimes wildly differently shaped plots.
It all comes down to us wanting to know if that is indeed the case that the G1 accelerometer is very unreliable and inconsistent device when used for more or less precise measurements? Is there some documentation/facts paper that would tell us just how reliable accelerometer is?
I thought I have read somewhere that the accuracy of Android's GPS is about 10cm?
Can anyone verify or correct this? Reason being is that my application I am trying to develop keeps track of locations an user has visited and it would help me out tremendously to know the margin of error I can expect?
My question in a nutshell is: Is there a correlation between the number of decimals used in GPS co-ordinates and the accuracy of the location?
Right now I happen to be working with the Android SDK but I'm sure this question can apply to many other geolocation SDKs. Basically, Android returns GPS coordinates with up to 14 digits. That seems like overkill in most situations. Lets say I needed accuracy down to about an area of 10 feet by 10 feet. How many decimals do I really need to worry about? The use-case that I'm looking for is I want to know if a person is north or south of a particular latitude - how many digits would I need to store in the database and how many digits would I need to compare?
I am now beginning an app which will use the compass and tilt sensors to determine a persons heading and line of sight. Can I assume the sensors on devices such as the G1 are fairly accurate or can I expect to run into problems such as the compass being 5-10 degress off etc?
View 4 Replies View RelatedI'm developing a mapping app using Eclipse 3.5.I'm setting the minimum update period with the LocationManager's requestLocationUpdates method, via a configuration activity. When I set the property I see in Logcat that the system process sets the value OK.When I actually send a new location from the DDMS emulator control and the location changes on the map view, I see that the system process then sets the minimum time to zero.Below is a capture of the system's log messages. You can see that I'm setting the period to 32 seconds, then 16, then, after I've sent a simulated location change the system sets it to zero.The map responds to location changes to location changes instantly even if they are sent only a couple of seconds apart.
View 1 Replies View RelatedIn my application I have to fetch the current location. First it correctly fetches the location. But we are moving from the current location to some other location. It shows the previous address. It is not updating the location. My code is: locManager = (LocationManager)getSystemService(Context.LOCATION_SERVICE); locListener = new MyLocationListener();locManager.requestLocationUpdates(LocationManager .GPS_PROVIDER ,0,0,locListener); location = locManager.getLastKnownLocation(LocationManager.GPS_PROVIDER);if(location != null){latitude = location.getLatitude();longitude = location.getLongitude();} Please find the mistake and when i launch first time it is not working on second time itself it is working so check this thing also.
View 1 Replies View RelatedI have an application which uses the network as the location provider (rather than GPS eg.), however I can't seem to figure out how to send the emulator test coordinates. In DDMS I would usually send coordinates in the Emulator Control tab.Is there a place to simulate coordinates derived from the cell phone network provider?
View 6 Replies View RelatedI want to override the method enableMyLocation() in MyLocationOverlay class, in order to implement my own positioning algorithm to get latitude/longitude, and then plot them onto a MapView. I figured out how to do that, but now I'm stuck because I dont know what Canvas to pass when I call the method drawMyLocation().
Here is the MyLocationOverlay class
Just wondering what people think of the accuracy of the screen. Coming from a WM phone and a resistive touch screen, I find it a lot harder to hit small places on the EVO. Little check boxes are hard to get. Also, I just feel like it doesn't always hit where I think it should.....
What are others thoughts on this? I have read in the past that resistive screens are more accurate but really just blew it off as people who were just defending their WM phone's but that statement really does seem to be true....
Still love the thing though and it finally feels like I got a totally new device! My last 4 WM phones just felt like the same thing over and over again with a little enhancement on each one....
I have been using my N1 for a few days now and the GPS accuracy is really wrong, about 500m out of the right position. I know GPS is not really precise, but 500m is far too much.
I am seeing this behaviour when on WI-FI, haven't test through 3G/edge yet though.
I haven't installed any ROM.