Accordingly, SO question , especially cgr answer.
The offset set for LocationRequest has no chance of gaining space if the device is still located, since the move has a precedent over Intevals (interval and fastestInterval). As I might have guessed - you might have passed another LocationRequest object (without a set of offsets) to LocationServices.FusedLocationApi.requestLocationUpdates ().
LocationRequestSmallestDisplacement set (float smallestDisplacementMeters)
sets the minimum offset between updating the location in meters. By default, this value is 0. It returns the same object, so setters can be chained.
NOTE. Location requests from applications with ACCESS_COARSE_LOCATION and no ACCESS_FINE_LOCATION will automatically throttle to a slower interval, and the location object will get confused only show a rough level of accuracy.
See page for details.
source share