".. working as designed." I am not so sure. The following is taken from Class LocationManager:
public void requestLocationUpdates (String provider, long minTime, float minDistance, PendingIntent intent) ...... The frequency of notification or new locations may be controlled using the minTime and minDistance parameters. If minTime is greater than 0, the LocationManager could potentially rest for minTime milliseconds between location updates to conserve power. As written, the purpose of specifying a relatively high value for minTime, is to conserve power. When I specify a value for minTime corresponding to 10 minutes, a phone device using Android 2.x seem to start the GPS once every 10 minutes, and keep searching for a position fix for up to approx 20 seconds. If there is no GPS coverage, it then seems to give up. And will not start another search again before the 10 minutes has passed. On the Galaxy tab using Android 3.x however, when there is bad GPS coverage, the GPS seems to be searching (more or less) continuously. It does not seem to give up after a few seconds when it does not get a position fix - as the 2.x devices seem to do. If the Galaxy tab GPS behaviour is "as designed" - as you say - there is no point in specifying a high value for minTime, in order to conserve power. So I still think that the GPS implementation on the Galaxy tab (or on Android 3.x?) is bad. Or - there could be something that I haven't understood (?) On 6 Des, 13:06, lbendlin <[email protected]> wrote: > Go outside. gps needs a clear sky view. This is working as designed. -- 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
