Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am experimenting with the GeoLocation speed reading on mobile device browsers, and it would be great if there existed list of devices that support it. Searching didn’t help a lot.
So far, I’ve tested a few Android 2.3 (those I tried give an accurate speed reading), IPhone 3 and 3G (both return null), IPad (returns null). What I’m more interested in, is this tied to the API implementation or the gps hardware in the device? Also, does IPhone 4 support the coords.speed reading?
According to the spec, an implementation must return
nullif speed reading is not supported. Seems like they do that, but some people on the internet say the iOS browser implemented thespeedAPI, at least inwatchPosition, see eg. these pages.From the spec, I would also assume that you cannot reliably tell whether a
nullvalue means ‘No API support’ or ‘No GPS support’. It could mean either.In any case, I think you’re better off implementing fallbacks and a user-friendly notice the device isn’t giving you any information, rather than whitelisting/blacklisting… based on what? UA strings aren’t everything, especially not what with Android’s ability to have alternative browsers (eg. Firefox Mobile, Opera, …).