Re: [android-developers] Cost of requestLocationUpdates

On Sun, Feb 27, 2011 at 12:58 PM, TreKing <trekingapp@gmail.com> wrote:
> Both conditions must be met. So you if you specify 60 minutes and 60 meters,
> the check won't even run for at least an hour.

Actually, that's not true. I thought it was, originally. The distance
is a filter for what events you receive. The time is merely a
guideline, and you may get events more frequently than that.

"If minTime is greater than 0, the LocationManager could potentially
rest for minTime milliseconds between location updates to conserve
power."

That being said, longer minTime values should generally be better for
power. Or, as the docs put it:

"Background services should be careful about setting a sufficiently
high minTime so that the device doesn't consume too much power by
keeping the GPS or wireless radios on all the time. In particular,
values under 60000ms are not recommended."

--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

Android 3.0 Programming Books: http://commonsware.com/books

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