Try using LocationRequest.Builder

Below code for creating location request

Kotlin

LocationRequest.Builder(Priority.PRIORITY_HIGH_ACCURACY, 10000)
            .apply {
                setWaitForAccurateLocation(false)
                setMinUpdateIntervalMillis(IMPLICIT_MIN_UPDATE_INTERVAL)
                setMaxUpdateDelayMillis(100000)
            }.build()

Java

new LocationRequest.Builder(Priority.PRIORITY_HIGH_ACCURACY, 10000)
    .setWaitForAccurateLocation(false)
    .setMinUpdateIntervalMillis(IMPLICIT_MIN_UPDATE_INTERVAL)
    .setMaxUpdateDelayMillis(100000)
    .build()

Read more about here https://developers.google.com/android/reference/com/google/android/gms/location/LocationRequest.Builder

Yes, the LocationRequest constructor is deprecated. You can use its static method LocationRequest.create() to create a location request.

Kotlin:

locationRequest = LocationRequest.create().apply {
    interval = 100
    fastestInterval = 50
    priority = LocationRequest.PRIORITY_HIGH_ACCURACY
    maxWaitTime = 100
}

Java:

locationRequest = LocationRequest.create()
    .setInterval(100)
    .setFastestInterval(3000) 
    .setPriority(LocationRequest.PRIORITY_HIGH_ACCURACY)
    .setMaxWaitTime(100);

Update

As @Shimon pointed out LocationRequest.PRIORITY_HIGH_ACCURACY is now deprecated, so instead use Priority.PRIORITY_HIGH_ACCURACY

LocationRequest locationRequest = 
 new LocationRequest.Builder(
  LocationRequest.PRIORITY_HIGH_ACCURACY,
  10000
 ).build();

locationRequest.setFastestInterval(5000);

To update the priority for the location request without using the deprecated setPriority() method, you can utilize the LocationRequest.Builder and its method setPriority() directly when the switch is toggled. Here's how you can achieve that:

sw_gps.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
    if(sw_gps.isChecked()){
        locationRequest = locationRequest
                .setPriority(LocationRequest.PRIORITY_HIGH_ACCURACY)
                .build();
    } else {
        locationRequest = locationRequest
                .setPriority(LocationRequest.PRIORITY_BALANCED_POWER_ACCURACY)
                .build();
    }
}
});

The codes that I replace it with is

  locationRequest = new LocationRequest.Builder(Priority.PRIORITY_HIGH_ACCURACY, 100)
                .setWaitForAccurateLocation(false)
                .setMinUpdateIntervalMillis(2000)
                .setMaxUpdateDelayMillis(100)
                .build();

The old deprecated code is

locationRequest = LocationRequest.create();
        locationRequest.setPriority(LocationRequest.PRIORITY_HIGH_ACCURACY);
        locationRequest.setInterval(5000); 

I haven't used location services in a long, long time, so I'm just looking at the documentation for 'LocationRequest.Builder` and guessing at your equivalent code because it looks self-explanatory. Builders are a common pattern, used more often in Java-based APIs like this one than they are used in pure-Kotlin APIs. You can look up "java builder pattern" to read about it.

private fun NewLocation() { 
    val locationRequest = LocationRequest.Builder()
        .setPriority(Priority.PRIORITY_HIGH_ACCURACY)
        .setIntervalMillis(0L)
        .setMinUpdateIntervalMillis(0L)
        .setMaxUpdates(1)
        .build()
    mfusedlocation = LocationServices.getFusedLocationProviderClient(this)
    mfusedlocation.requestLocationUpdates(locationRequest, locationCallback, Looper.myLooper())
}

FYI since you're working on a portfolio:

• Function names in Kotlin start with a verb and lower-case letter by convention. Or if it returns a modified copy of an object, you can use a past participle instead of a phrase starting with a verb. For example, I would rename NewLocation() to something like beginLocationRequest().

• The mSomething pattern of naming variables (putting abbreviations in front of variable names) is called Hungarian notation. m stands for "member", but Kotlin properties are not even called member variables. I've never seen Hungarian notation used in Kotlin before, and it is rarely used in Java. It is widely regarded as making code less readable, especially with modern IDEs. I would advise against using it in a portfolio project as it is more likely to damage the impression you want to give than it is to help, especially if you are using it inconsistently.

I got the same problem, and I used LocationRequest.Builder to create my locationRequest then, GPS signal became stable:

locationRequest = new LocationRequest.Builder(Priority.PRIORITY_HIGH_ACCURACY, 1000)
                .setWaitForAccurateLocation(false)
                .setMinUpdateIntervalMillis(500)
                .setMaxUpdateDelayMillis(1000)
                .build();

Error: Exception e is instantiated as "ApiException" so casting to ResolveApiException(subclass) is not possible.

e.getClass();//returnsString ApiException instead of ResolveApiException

A possible workaround:use ResolvableApiException constructor,requires only status code.

ResolvableApiException resolvable = new ResolvableApiException(exception.getStatus());
//use ResolvableApiException Constructor
//public ResolvableApiException (Status status)