I hoping this was fixed along the way and the issue not updated. I had to
drop a part of an internal application for a company because of this bug.
And like lbendlin said, you could just check the last known and see if it
was recent enough to use.
private static final int TIME_WINDOW = 1;
I haven't seen the issues with concurrent GPS access that you describe.
nevertheless you may want to anticipate a situation when another program is
currently actively using the GPS. In such a case you could ask the passive
provider first, and only if that location is too old or to imprecise the
Correct.
Note that this may have been fixed somewhere along the way and they haven't
taken time to mark that issue resolved. As you can see, the Droid and others
I confirmed that on were Android 2.0.1, which is hardly in use today.
At the time of posting that issue, I spent a ton of time trying
Just to clarify one thing:
> you don't want to use the requestLocationUpdates().
I suppose you meant: "you don't want to call requestLocationUpdates()
for continuous updates", right?In the BroadcastReceiver activity, I'll
call the requestLocationUpdates() and then removeUpdate() as soon as
there is
Many thanks for the helpful info, Steven .
I'm sure that will save me a lot of time.
--
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, se
That's exactly what I wanted to know, thanks a lot!
--
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+un
I tried to deal with this on an internal company app and you don't want to
use the requestLocationUpdates().
See this bug I logged:
http://code.google.com/p/android/issues/detail?id=5595
I'm not sure if that was a hardware driver or software, but I know you can
reproduce that on plenty of hard
7 matches
Mail list logo
