On Thu, Oct 3, 2013 at 4:43 PM, Alex Belyaev wrote:
> And why not?
>
"Why not?" is not really a good reason to do something.
> ) In theory you can provide a unique action, so *LocationManager* can
> simply broadcast location changes.
>
I don't follow what you're suggesting.
> And yes, there
And why not?) In theory you can provide a unique action, so *LocationManager
* can simply broadcast location changes. And yes, there is a possibility,
that someone can listen to this broadcast too and potentially abort them.
So that is the reason why I am asking.
пятница, 4 октября 2013 г., 0:
On Tue, Oct 1, 2013 at 3:18 PM, Alex Belyaev wrote:
>
> I have a quick theoretical question: why *
> LocationManager.requestLocationUpdates* method needs* PendingIntent *instead
> of an action?
>
Well, what is your reasoning for why an Action would make sense here
instead?
--
Hello guys!
I have a quick theoretical question: why *
LocationManager.requestLocationUpdates* method needs* PendingIntent *instead
of an action? Just for having a possibility to send location updates to the
specified *UserHandle *or any other reasons?
Thank you in advance.
--
You received th
In Android 1.6 there are log messages being generated by
GpsLocationProvider about exceeding MIN_FIX_COUNT and stopNavigating.
There are some bug reports against 1.6 saying that the
locationManager.requestLocationUpdates has a problem that causes it to
hibernate at the incorrect times if an app re
Hi,
Using LocationManager to get location updates:
LocationManager.requestUpdates(
String provider,
long minTime,
float minDistance,
LocationListener listener);
If our main UI thread registers the LocationListener, will it get
blocked whenever the service is trying to get a
6 matches
Mail list logo
