You are implementing LocationListener in your activity MainActivity. The call for concurrent location updates will therefor be like this:

mLocationClient.requestLocationUpdates(mLocationRequest, this);

Be sure that the LocationListener you're implementing is from the google api, that is import this:

import com.google.android.gms.location.LocationListener;

and not this:

import android.location.LocationListener;

and it should work just fine.

It's also important that the LocationClient really is connected before you do this. I suggest you don't call it in the onCreate or onStart methods, but in onResume. It is all explained quite well in the tutorial for Google Location Api: https://developer.android.com/training/location/index.html

You can use this schema. Create new Runnable which will be called every time, when you want it

private final Handler _handler = new Handler();
private static int DATA_INTERVAL =  60 * 1000;

private final Runnable getData = new Runnable()
{
    @Override
    public void run()
    {
        getDataFrame();
    }
};
private void getDataFrame() 
{
    requestGPS();
    Timer time = new Timer();
    time.schedule(new TimerTask() {
            @Override
            public void run() {
                _locationManager.removeUpdates(_connector);
                this.cancel();
            }
        }, 5000, 5000);
    _handler.postDelayed(getData, DATA_INTERVAL);
}
private void requestGPS() 
{
    _locationManager.requestLocationUpdates(
    LocationManager.GPS_PROVIDER,
                0,
                0,
                _connector);
}

Workaround for this issue is to use only one LocationManager and one LocationListener. If your app has needs for different kind of simultaneous location requests (with different parameters), then you need to implement a "location request handler" which decides which parameters should be used for the location request i.e. which parameters have the tightest requirements for location.

Here is a simple example code that explains the idea of "location request handler":

Copyclass LR {

    long lock_min_time; // defined in set_lock_lr before using
    float lock_min_dist;
    boolean lock_active = false;

    long idle_min_time = 3600000; // 1 per hour
    float idle_min_dist = 200;
    boolean idle_active = true;

    long fast_min_time = 0;
    float fast_min_dist = 0;
    boolean fast_active = false;

    //constructor
    public LR()
    {}

    public void set_lock_lr(long min_time, float min_dist, boolean active)
    {
        lock_active = active;
        lock_min_dist = min_dist;
        lock_min_time = min_time;
        System.out.println("LR lock set: "+min_time+", "+min_dist+", "+active);
        update_location_request();
    }

    public void set_idle_lr(boolean active)
    {
        idle_active = active;
        System.out.println("LR idle set: "+active);
        update_location_request();
    }

    public void set_fast_lr(boolean active)
    {
        fast_active = active;
        System.out.println("LR fast set: "+active);
        update_location_request();
    }

    private void update_location_request()
    {
        // Remove current location request
        mlocManager_basic.removeUpdates(mlocListener_basic);

        if(fast_active)
        {
            mlocManager_basic.requestLocationUpdates(LocationManager.GPS_PROVIDER, fast_min_time, fast_min_dist, mlocListener_basic);
            System.out.println("LR: fast_active");
        }
        else if(lock_active)
        {
            mlocManager_basic.requestLocationUpdates(LocationManager.GPS_PROVIDER, lock_min_time, lock_min_dist, mlocListener_basic);
            System.out.println("LR: lock_active");
        }
        else if(idle_active) // only idle updates
        {
            mlocManager_basic.requestLocationUpdates(LocationManager.GPS_PROVIDER, idle_min_time, idle_min_dist, mlocListener_basic);
            System.out.println("LR: idle_active");
        }
    }
}

LocationManager.NETWORK_PROVIDER need network, but it is real, not precise. if you want to use LocationManager.GPS_PROVIDER, the situation must be outdoor instead of indoor, because GPS location need satellite, if you are in any building, the satellite cannot find you! pleasle go outdoor and check with GPS_PROVIDER again!

*best approach is getting location from both of GPS and NETWORK and check any of then that was not null and more accurate useing it.

According to the documentation RuntimeException is called when calling thread has no Looper. Try to call Looper.prepare() before you call LocationManager

1. minTime – Wise choice of value for minTime will help you reduce power consumption. What you need to keep in mind is that elapsed time between location updates will never be less than minTime, but it can be greater, because it is influenced by the implementation of each given Provider and the update interval requested by other running applications.
2. minDistance – Unlike minTime this parameter can be turned off by setting it’s value to 0. However, if minDistance is set to a value greater than 0, location provider will only send updates to your application if location has changed at least by given distance. This parameter is not a great power saver like minTime, but it should be kept in mind although.

These two parameters work in AND relation, so in order to receive location update, both of their conditions need to be achieved (i.e. more then 5 seconds has passed, and the distance change is greater than 10 meters).

You can check this link: https://blog.codecentric.de/en/2014/05/android-gps-positioning-location-strategies/