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 requests a notification interval greater than 1.
As far as I can tell this behavior has the effect of causing locationManager.requestLocationUpdates to stop delivering location updates for extended periods of time – which causes the app to appear to be ignoring location changes. Has anyone else experienced this? I have set the notification interval to 0 milliseconds and it seems to be working again (delivering lots and lots of location updates now!). The docs encourage use of time intervals as a means of conserving battery power. Is setting the time interval to 0 the correct work- around? -- 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
