/** this criteria will settle for less accuracy, high power, and cost */
public static Criteria createCoarseCriteria() {
  Criteria c = new Criteria();
  c.setAccuracy(Criteria.ACCURACY_COARSE);
  c.setAltitudeRequired(false);
  c.setBearingRequired(false);
  c.setSpeedRequired(false);
  c.setCostAllowed(true);
  c.setPowerRequirement(Criteria.POWER_HIGH);
  return c;
/** this criteria needs high accuracy, high power, and cost */
public static Criteria createFineCriteria() {
  Criteria c = new Criteria();
  c.setAccuracy(Criteria.ACCURACY_FINE);
  c.setAltitudeRequired(false);
  c.setBearingRequired(false);
  c.setSpeedRequired(false);
  c.setCostAllowed(true);
  c.setPowerRequirement(Criteria.POWER_HIGH);
  return c;
 make sure to call this in the main thread, not a background thread
 make sure to call locMgr.removeUpdates(...) when you are done
public static void init(){
  LocationManager locMgr =
    LocationUtils.getLocationManager(ctx.getMyContext());
  // get low accuracy provider
  LocationProvider low=
    locMgr.getProvider(locMgr.getBestProvider(createCoarseCriteria()));
  // get high accuracy provider
  LocationProvider high=
    locMgr.getProvider(locMgr.getBestProvider(createFineCriteria()));
  // using low accuracy provider... to listen for updates
  locMgr.requestLocationUpdates(low.getName(), 0, 0f,
        new LocationListener() {
        public void onLocationChanged(Location location) {
          // do something here to save this new location
        public void onStatusChanged(String s, int i, Bundle bundle) {
        public void onProviderEnabled(String s) {
           // try switching to a different provider
        public void onProviderDisabled(String s) {
           // try switching to a different provider
  // using high accuracy provider... to listen for updates
  locMgr.requestLocationUpdates(high.getName(), 0, 0f,
        new LocationListener() {
        public void onLocationChanged(Location location) {
          // do something here to save this new location
        public void onStatusChanged(String s, int i, Bundle bundle) {
        public void onProviderEnabled(String s) {
          // try switching to a different provider
        public void onProviderDisabled(String s) {
          // try switching to a different provider
    
When attaching a location listener to a location provider (regardless of the exact kind of
provider), it is important to execute this listener code in the main thread of your activity or
service. If you run this in any background thread (like using an executor) then this will not
work. The listener code itself has to be on the main thread. You can kick of a task in an
executor in the listener, but the listener itself must run in the main thread of the app.
    
Some devices will require you to detach the listener and then reattach it periodically. This is
not a bad idea, since it eliminates the possibility of the listener going stale.
    
You can switch providers at any time, and switch out a fine provider with a coarse one to save
battery life, for example. There is really no limit to how often you can switch out providers.
You can also do this when you discover that a provider is unavailable, via a call to the
registered location listener.
    
Finally, the parameters you pass to the location provider, when you attach your location listener
are totally optional. The device you are running on will decide whether to respect those
parameters or not. So it’s best never to rely on them. Also, different devices behave differently
with reporting location movements. Eg, the Droid X and Droid 2 are very zippy about providing
location updates, they will do it every second and provide you with a very high level of
accuracy. The Samsung Galaxy S is less zippy with the location updates. The HTC Incredible is
better than the Galaxy S, but not as zippy with the frequent updates as the Droid X and Droid 2.
Finally, the LG Ally is one of the worst with location updates, providing very infrequent
updates, and very poor accuracy (even on autonomous GPS). So don’t make any assumptions about the
accuracy and frequency of updates – you have to test it on real devices on real networks in real
life situations.
The best way to handle GPS is to use the “network” or “passive” provider first, and then fallback on
“gps”, and depending on the task, switch between providers. This covers all cases, and provides a
lowest common denominator service (in the worst case) and great service (in the best case).
    developerlife.com site was started in Nov 1998 by Nazmul Idris, with coverage for topics related to Java, XML,
    and web and desktop technologies. Today it covers Rust, TUI, CLI, Kotlin, TypeScript, Node.js, React, Android,
    JDK, Web, Cloud technologies, User Experience Engineering (UXE) and design topics. © Nazmul
    Idris 2022. All rights reserved.