Aha! Thank you! As soon as I read your response it hit me - I am testing on the emulator, which will always give me a null provider! Which means no matter what I do I am gonna get a null which means I can't get a latitude... Which shows that I have had WAY too much time off of programming between Christmas and New years!
Thanks a million! On Jan 6, 2:26 pm, "Maps.Huge.Info (Maps API Guru)" <[email protected]> wrote: > You're not testing to see if you get a null provider, also I'm not > sure asking to use POWER_LOW and ACCURACY_FINE will work as GPS uses a > lot of power. > > I suggest dropping the POWER_LOW and testing provider for null. > > Also, unless you need a very accurate fix, the wireless network > location service (ACCURACY_COARSE) is much faster, uses less power and > also works indoors, you might consider using that as well. > > As a side note, you're not going to get a good fix using > getLastKnownLocation without first attaching a listener to the GPS. > The last known location might be 100 miles away, if the last time > location services were used was a while ago. I've found > getLastKnownLocation to be unreliable. > > -John Coryat > > "Radar Now!" > > "What Zip Code?"
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
