I'm really fed up reading about the min time and min distance being "a hint". If there's a complex interaction between our parameters and the resulting effect, why isn't it documented? Just how the heck does it work? I'm using the NMEA listener and want to have direct but high level control over the frequency of logging. When travelling straight and fast, log every 10-20 seconds, when slow and twisty, say every second or so. My Garmin GPS does this without being told - but I can't change its behaviour. I was really hoping that I could with my Android phone. Every time I read "just a hint" my blood boils. I've spent countless hours tweaking the values, but just can't work out how they're used. Does anyone in really know?
On Thursday, February 16, 2012 6:37:17 AM UTC+11, Mark Murphy (a Commons Guy) wrote: > > On Wed, Feb 15, 2012 at 2:32 PM, Kristopher Micinski > <[email protected]> wrote: > > The interval is not exact > > Moreover, the interval can be completely ignored. The minimum distance > is a filter; the minimum time is a hint. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > _Android Programming Tutorials_ Version 4.1 Available! > > -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
