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?
View 4 Replies
I read the thread about swype accuracy going to hell, and checked to make sure that wasn't the case for mine. For me its not totally unusable, but in the last week I've noticed severely diminished accuracy. If I totally focus I can swype with few errors, but as soon as I try to resume the speed that I used a week ago, swype's accuracy drops to about 50%, many of the suggested words aren't words I've ever used.
Another issue I'm having is the pop-up tutorial when I select a word other the the first suggestion. I've been through every setting and nothing will stop the tutorial pop-up
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 RelatedI've had my DroidX since it was released and have been satisfied by the Swype keyboard. However, this morning when I went to use it, it's accuracy appears to have taken a major nosedive. Hello becomes Bello, this becomes toda, for becomes fue, etc. It's unusable. But when I use it as a regular keyboard by pressing the individual keys, it works fine. This is in portrait mode, btw.
View 3 Replies View Relatedwhats the best battery status app out there in your opinion. In terms of features, status it shows and of course accuracy.
View 8 Replies View RelatedIs it just me, or has anyone else noticed that they're message typing skills have gone down with 2.1? I seem to get way more typos.
I seem to have noticed that the touchscreen accuracy has reduced with this build, so I think that's part of it, but I'm also wondering if the typing prediction isn't as good as 1.5 was? I just typing doong, meaning to get doing, but it didn't change it. In fact, of the options it did give me for that, "doing" wasn't one of them.
Is it just me being critical knowing it's a beta build, or is anyone else noticing these?
And I've already recalibrated the keyboard and the g-force.
How 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?
wanted to know that the accuracy value returned by the getAccuracy() is of which type radial accuracy or horizontal accuracy.
View 8 Replies View RelatedIf 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 View RelatedI'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?
how does "location accuracy" use a wifi network?
View 7 Replies View RelatedMy 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 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 RelatedJust 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.
I made a quick video to demonstrate the vast difference in reported 4G speed between the Android speedtest.net app and the browser version of the speakeasy test. My results show great differences btw the two (2-3 Mbps). I don't know which one is correct; but I think the Speedtest app cannot correctly determine WiMax and WiFi speeds. In addition to what the video shows, when the EVO is connected to home Wifi the greatest speed Ive seen is 11 Mbps (even though the app dial stops at 10) when a laptop test done at the same time correctly shows 15+. Is anyone else seeing similar? I just think its flawed that many are using the app as the standard for network speeds on mobile devices.
View 21 Replies View RelatedYour "best" (lowest value) GPS Accuracy you have seen on your Captivate. This is to compile data to send to Samsung's technical support, hopefully to aid in trouble-shooting the issue. After voting in the poll, please post indicating which firmware you are running (pre or post update, or which custom ROM or leak). This poll is not concerned with time to lock, holding a lock, or any other GPS issue than accuracy, and is just to compile a data set to test one part of a hypothesis of mine. It seems my Captivate has a "best" (lowest) accuracy of ~16.2 ft (5m), much higher than say, an N1 or G1 (which max out around 6.6 ft).
If you are unsure how to check for accuracy to get a specific number, use either GPS Test or GPS Status (free, in the market) as they both will display accuracy of the lock in real-time. GEnerally the accuracy improves with the longer the lock holds, so for maximum effectiveness, let's set the official accuracy time at 5 minutes (leave the app open for 5 minutes, then record the accuracy) or the best value you have noticed. Also, if your value is not exactly one that is up here, please select the closest number to your value...
I had a question come up here at the office about the accuracy of the GPS on my EVO. I loaded the "GPS Status" app and went outside and found that I am getting 3 Meter accuracy which is as good as my Magellan GPS that I use while hiking. My question is this, while using Google maps I believe that location can also be derived via signal strength triangulation from cell towers. If this is so has anyone seen a position accuracy that is derived from both the GPS and the Towers.
View 6 Replies View RelatedSeems as though the accuracy of Swype has been going down for me over the last 2 weeks. I haven't messed with any of the settings. The main thing is that it will put in a word that I am clearly not spelling, even if I go so slow and make sure I'm touching the exact letters.
The biggest culprit for me is the word, "WANT". It keeps spelling it as "WASN'T". It is driving me crazy. I am making 100% sure I am not touching the apostrophe at all. And it will still spell "WASN'T". I have to manually type the word "WANT" everytime. There are other examples, but that is the biggest one.
Advice?
I'm new to android development and I'm implementing a simple localization method to get used to the device. I've been reading some articles and I can't seem to figure out how the phone figures out sensor accuracy. My guess is that it decides this based on how long its been since it was last calibrated.
View 3 Replies View Related