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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
