Yes, this absolutely makes sense. You were right, I was assuming
broadcasting as the only option in that case.
Thank you.
пятница, 4 октября 2013 г., 2:25:12 UTC+3 пользователь TreKing написал:
>
>
> On Thu, Oct 3, 2013 at 5:32 PM, Alex Belyaev
>
> > wrote:
>
>> What *LocationManager *does, w
On Thu, Oct 3, 2013 at 5:32 PM, Alex Belyaev wrote:
> What *LocationManager *does, when we call *requestLocationUpdates* and
> provide a *PendingIntent*? It sends us locations back with broadcasts.
>
It sends locations back with broadcasts ... *if you specify a broadcast for
your PendingIntent*.
What *LocationManager *does, when we call *requestLocationUpdates* and
provide a *PendingIntent*? It sends us locations back with broadcasts. So
basically *LocationManager *needs only an action, that is the only thing
you need to make a broadcast across the system. So I'm asking, why it need
a
Have you seen the previous thread on this yet?
http://groups.google.com/group/android-developers/browse_thread/thread/4bbd1593f41d1e97/dfaa7da78bc89ea7
The amount of time that it stops providing updates seems directly
based on the value you pass for the power saving hint parameter of
requestLocati
Thanks Lance, I just found that I was being hit by this bug/issue:
http://code.google.com/p/android/issues/detail?id=3147
I was logging the time of the first fix using localized time, and it
was appearing as if the callback was blocking for two seconds...
Thanks
On Dec 5, 6:26 pm, Lance Nanek
Neither version blocks. The onLocationChanged method won't even be
called during the requestLocationUpdates call, only afterwards as a
separate event.
On Dec 5, 4:04 pm, Mark Wyszomierski wrote:
> Hi,
>
> Using LocationManager to get location updates:
>
> LocationManager.requestUpdates(
>
6 matches
Mail list logo
