ProximityRadius *is* big. I think I was using 1500 meters in the field test today. The "10 feet" I mentioned below was the minimum distance to travel before doing an location update. And I mean "10 meters".
I beginning to think my mental model is all wrong. I thought I could blindly throw intents out to the Android and it would fire off PAs back at me. Which intent belonged to which latlong was my problem to figure out. I'm now thinking I need to keep each PA intent in a global data structure^W^W^Winstance variable and carry them around with me and run an RequestUpdate on each one. :-? Is there someway for me to monitor myLocationManager to see when he fires off a PA? On Sat, Mar 7, 2009 at 7:29 PM, Mark Murphy <[email protected]> wrote: > > Faber Fedor wrote: > > I've set the minimum distance/time to check for updates to be > > ridiculously low (10 feet, 5 secs, 0 for each, etc.). > > That may be your problem. > > You want proximityRadius to be *big*, not small. A 10-foot proximity > radius means you need to be within 10 feet of the target location before > you will get an alert. > > Also, FWIW, the radius is in meters. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com > Android Training in Sweden -- http://www.sotrium.com/training.php > > > > -- Faber Fedor Linux New Jersey http://linuxnj.com faberfedor.blogspot.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
