Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

The locations in my app are wrong or jump around

Short answer

On Android, accuracy depends on which location permission the user granted, and background updates are limited by the system. If a user allows only approximate location, the app cannot see a precise position. Check what permission your users have granted, then ask a developer to review how the app asks for and uses location.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • My drivers or staff show up in the wrong place on the map.
  • The position stops updating when the phone screen is off.
  • Locations jump or arrive only a few times an hour.
  • It works on my phone but not on some of my users' phones.
  • The app asks for location, but tracking still does not work properly.

Why does this happen?

  1. The user allowed only approximate location

    Android has two accuracy levels. Approximate location is accurate to within about 3 square kilometres, precise location usually within about 50 metres. If the user grants only the approximate permission, the app gets only approximate location, whatever the app asks for.

  2. The app only has foreground access

    The system treats location as foreground use when an activity is visible or the app runs a foreground service with a persistent notification. Tracking that must continue with the screen off needs that service, or the background location permission.

  3. Android limits background updates to save battery

    On Android 8.0 and higher, an app running in the background can receive location updates only a few times each hour. A tracking feature built without this in mind looks broken when the app is not on screen.

  4. Google Play restricts background location

    Google Play limits background location access to apps that need it for their core functionality and meet its policy requirements. Check the policy before you plan a feature that depends on it.

What can I do about it today?

  1. Check the phone's location setting for your appOn a phone that shows wrong positions, open the app's permission screen and see whether location is set to precise or approximate, and whether it is allowed only while using the app.
  2. Compare two phonesTest the same route on a recent phone and an older one. If only one is wrong, the cause is the phone setting, not your server.
  3. Ask users to keep the app allowedTell drivers or staff not to force-close the app and to leave location allowed. This is a safe request and does not change anything on your side.
  4. Do not ask users to turn off battery features at randomChanging power settings across many phones is hard to undo. Let a developer decide which settings matter first.
  5. Collect examplesNote the time, the phone model and a screenshot of the wrong position. Specific examples make the problem much faster to find.

When should I bring someone in?

  • Tracking is part of how your business runs, for example dispatch or delivery.
  • Wrong positions affect customers or payments.
  • You plan to add background tracking and are unsure if the store will accept it.

How do I handle it?

  1. Reproduce it with real phonesI test the app on the phones your users really carry, with the same permission choices, screen on and off.
  2. Read how the app asks for locationI check which permission is requested, when, and whether a foreground service is used for continuous tracking.
  3. Decide between tracking stylesFor some features a foreground service is right, for others a different approach is lighter on battery. I explain the options in plain words before building.
  4. Check the store rules before releaseIf background location is needed, I check Google's policy first so the update is not rejected.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Why does tracking work only when the app is open?

Android treats an open screen or a running foreground service as foreground use. Without one of those, the system limits how often a background app gets location.

Can the app force users to allow precise location?

No. The app can ask, but the user decides, and if only approximate access is granted the app still works with approximate location. A good app handles that case clearly.

Will the store accept background tracking?

That is Google's decision. Its policy restricts background location to apps that need it for core functionality and meet the policy requirements.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.