Home/ Questions/Q 7191417
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T19:43:27+00:00

This is a problem that is quite the opposite of the regular use of

  • 0

This is a problem that is quite the opposite of the “regular” use of the GPS. The goal is to have the gps read or “fix” at a very precise rate (when available) across the multitude of devices that exists. So until now I believed that the timing parameter in e.g.

lm.requestLocationUpdates(LocationManager.GPS_PROVIDER, 2000, 1f, this);

would take care of this for me. But behold, when testing on a Nexus S and Galaxy Nexus I got completely different behavior, almost opposite (minimum time between reads in one case, maximum in the other). Why is this, and what could be done to fix it?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Why is this

    If you read the documentation, you will see that the minTime parameter to requestLocationUpdates() “is only used as a hint to conserve power, and actual time between location updates may be greater or lesser than this value”.

    what could be done to fix it?

    You come up with a new design that makes no assumptions whatsoever about the availability and frequency of GPS fixes.

    • 0