onLocationChanged gets called multiple times on start of application

Question

I have written following service,The idea is to send User location to server on application launch and when user travels more than 500m, The problem is that on launch it calls onLocationChanged 3 times.

I am unable to understand that from where its calling it 3 times. Kindly guide me how to resolve this problem.

public class LocationUpdateService extends Service implements
        LocationListener,
        GoogleApiClient.ConnectionCallbacks,
        GoogleApiClient.OnConnectionFailedListener {



    private static final long BACKGROUND_INTERVAL = 60000;

    final private String TAG = LocationUpdateService.class.getSimpleName();
    private LocationRequest mLocationRequest;
    private GoogleApiClient mGoogleApiClient;
    private String LOCATION_PREF = "LOCATION_PREF";



    @Override
    public int onStartCommand(Intent intent, int flags, int startId) {
        Log.i(TAG, "onStartCommand: ");
        mLocationRequest = new LocationRequest();
        mLocationRequest.setInterval(BACKGROUND_INTERVAL);
        mLocationRequest.setFastestInterval(30000);
        mLocationRequest.setPriority(LocationRequest.PRIORITY_BALANCED_POWER_ACCURACY);
        mLocationRequest.setSmallestDisplacement(500);
        super.onStartCommand(intent, flags, startId);
        return START_STICKY;
    }

    @Override
    public void onLocationChanged(Location location) {
        Log.i("Location Service", "onLocationChanged: " + location.toString());
        saveLocationandReport(String.valueOf(location.getLatitude()), String.valueOf(location.getLongitude()));
    }

score 4 · Answer 1 · edited Nov 09 '17 at 14:15

You cannot control onLocationChanged, it is manage by location service. In your case you can set a buffer/wait time, if you have location update within buffer time you can check its compare its accuracy with previous location update which ever is best use it.

private int FASTEST_INTERVAL = 1000; // use whatever suits you
private Location currentLocation = null;
private long locationUpdatedAt = Long.MIN_VALUE;

@Override
public void onLocationChanged(Location location) {
    boolean updateLocationandReport = false;
    if(currentLocation == null){
        currentLocation = location;
        locationUpdatedAt = System.currentTimeMillis();
        updateLocationandReport = true;
    } else {
       long secondsElapsed = TimeUnit.MILLISECONDS.toSeconds(System.currentTimeMillis() - locationUpdatedAt);
       if (secondsElapsed >= TimeUnit.MILLISECONDS.toSeconds(FASTEST_INTERVAL)){
            // check location accuracy here
            currentLocation = location;
            locationUpdatedAt = System.currentTimeMillis();
            updateLocationandReport = true;
       }        
    }
    if(updateLocationandReport){
        //  send your location to server
    }
}

Mick · Answer 2 · 2017-01-31T11:43:28.530

2

You don't control when the onLocationChanged is called - it is the location service which calls it.

It may call if for a number of reasons - the most obvious is when the users actually moves and it detects this and sends you an update, but it also may be called when the location service gets a more accurate location.

As a general rule it takes a little time for an accurate location so if you need accuracy it may make sense to allow for this in your application.

edited Jan 31 '17 at 11:43

answered Jan 31 '17 at 11:14

Mick

24,231
1
54
120

Thanks, so do i need to trigger it lately? or Hit server on the third try, it always hit the service three times – dev90 Jan 31 '17 at 11:15
1

use the accuracy parameter provided by the location object , then based on that u can decide what to do – Ak9637 Jan 31 '17 at 11:26
@Ak9637 : getAccuracy returns 23.33 on all hits – dev90 Jan 31 '17 at 11:35
1

then u can use some kind of buffer to check it the last few locations that u have recieved are different of more accurate or not – Ak9637 Jan 31 '17 at 12:00
you can put logic in `saveLocationandReport` method to send location – Iqbal Rizky Jan 31 '17 at 15:01

onLocationChanged gets called multiple times on start of application

2 Answers2