If you expect to do something time sensitive by hoping that location
manager respects the frequency argument: it doesn't. For triggering when
the phone is moved you have to monitor more closely. That's probably not
the best idea: you'll kill the battery. I'd figure something else out.
Kris
On Jan
Kristopher,
Sorry but I don't know what you mean by "useful for scheduling within your
app". I'm using the locationlistener to trigger when the phone is moved.
(I'm targeting Gingerbread)
Are you saying that even with jellybean it doesn't work right?
Would I be better off explicitly getting a
Even now, you can't expect that method to be useful for scheduling
*within* your app to any kind of real granularity.
kris
On Sun, Jan 20, 2013 at 12:33 PM, Mark Murphy wrote:
> Quoting the documentation for requestLocationUpdates():
>
> "Prior to Jellybean, the minTime parameter was only a hint
Quoting the documentation for requestLocationUpdates():
"Prior to Jellybean, the minTime parameter was only a hint, and some
location provider implementations ignored it. From Jellybean and
onwards it is mandatory for Android compatible devices to observe both
the minTime and minDistance parameter
in the onCreate event for my Service I setup locationlistener...
locMgr = (LocationManager)getSystemService(Context.LOCATION_SERVICE);
locLstnr = new MyLocationListener();
debugLog("Instantiated new Location listener", false);
locMgr.requestLocationUpdates(LocationManager.GPS_PROVI
5 matches
Mail list logo
