You can go through this document:

private FusedLocationProviderClient mFusedLocationClient;
private LocationRequest mLocationRequest;
mLocationRequest = LocationRequest.create()
            .setPriority(LocationRequest.PRIORITY_HIGH_ACCURACY)
            .setInterval(60000) ;     // 10 seconds, in milliseconds
          .setFastestInterval(10000); // 1 second, in milliseconds
if(mFusedLocationClient == null) {
        mFusedLocationClient = LocationServices.getFusedLocationProviderClient(mContext);
        mFusedLocationClient.requestLocationUpdates(mLocationRequest,
                locationCallback,
                null /* Looper */);
    }
 private LocationCallback locationCallback = new LocationCallback(){
    @Override
    public void onLocationResult(LocationResult locationResult) {
        super.onLocationResult(locationResult);
        Location location = locationResult.getLastLocation();
        if(location != null) {...you can get updated location
}}
//REMOVE LOCATION UPDATES
mFusedLocationClient.removeLocationUpdates(locationCallback);

Weird!!! Fused location should be faster and should provide more accurate location.

Make sure you are requesting location updates

LocationServices.FusedLocationApi.requestLocationUpdates(
    mGoogleApiClient, mLocationRequest, this
);

instead of getting last known location

mLastLocation = LocationServices.FusedLocationApi.getLastLocation(
    mGoogleApiClient
);

and you're using LocationRequest.PRIORITY_HIGH_ACCURACY(GPS).

Main difference between Fused Location and Location Manager is the latter does not depend on Google Play Services.

Use the Fused Location API.

As the name suggests it's a 'fused' location provider, so it uses a mixture of GPS and network provided location to give you a trade-off between accuracy and battery consumption. It can also be updated independently of the OS, so it has a shorter release cycle for updates.

FusedLocationProvider uses a mix of hardware to determine location based on the context of the request, meaning it's optimized transparently to you. It will also cache captured locations between applications to avoid unnecessary work to determine location info. So if a user has a variety of location-aware apps, they potentially avoid taxing the device (and waiting) for a location capture as one may have already been cached.

While the ol' LocationManager will suffice in small, one-off situations, you should definitely consider the newer alternative as the benefits may be great, and the work to implement, easy.

You may as well use it as Google Play Services is regularly updated across devices, and continuously includes improvements to location-based features (and more).

A link to an explanation of the FusedLocationProvider at launch: https://www.youtube.com/watch?v=Bte_GHuxUGc

Related

Have found a previous answer for you, looks like FusedLocationProvider is going to be better