Mock Location App on Android: Developer Testing Guide (2026)

A mock location app overrides Android’s GPS provider so apps you build or test see a coordinate you choose. We tested three of them on our Samsung Galaxy S24 (Android 15) and on our Pixel 8a (Android 14) across two weeks of QA work in April 2026.

The goal was to verify geofenced features on internal apps without driving across the Bay Area every afternoon. This guide covers the legitimate developer setup, what each tool is good for, and the apps where you absolutely shouldn’t point one.

#What a Mock Location App Does on Android

A mock location app registers itself with Android’s location framework as a fake GPS provider. Once you select it in Developer Options, every location request from any app on the device routes through your tool instead of the real GNSS chip. Android Studio’s emulator uses the same plumbing for its built-in location simulator, which is why it has been a stable, supported developer feature since Android 6.0 (Marshmallow).

The concrete use cases are narrow on purpose.

App developers test geofences, location-triggered notifications, or distance calculations without driving across town. QA engineers replay GPS traces from production crash logs to reproduce reported bugs in staging builds. Privacy-conscious users on their own device, on their own account, want to report a generic city-level position to apps they have permission to control.

None of those involve cheating in a multiplayer game or evading anti-fraud at a bank.

According to the Android 6.0+ mock location runtime permissions documentation, the platform exposes mock location as a debugging API and expects apps that handle sensitive data to detect it.

That detection is the part most casual users miss.

#How Do You Enable Mock Location on Android?

The setup runs through Developer Options and takes about three minutes on a stock Android 15 device. We tested this exact path on the Galaxy S24 and the Pixel 8a in April 2026 and the steps were the same on both.

1. Open Settings and go to About phone (or About device on Samsung).
2. Tap Build number seven times. Android pops a “You are now a developer!” toast.
3. Back out to the main Settings list. A new Developer options entry appears under System (Pixel) or Settings root (Samsung One UI 6).
4. Open Developer options and scroll to the Debugging section.
5. Install the mock location app you plan to use from Google Play first, then come back to Developer options.
6. Tap Select mock location app and pick your tool from the list.

If your tool isn’t in the picker, it hasn’t requested the right permission in its manifest. Reinstall it or pick a different app. Google’s Android source documentation covers the underlying ACCESS_MOCK_LOCATION permission, and well-written developer apps declare it correctly.

You can verify the mock is active using adb shell dumpsys location from a connected workstation. The output lists the active mock provider by package name and the last fix it reported. We used this on every test session to confirm the device hadn’t silently fallen back to real GPS when the screen locked, and to capture the exact lat/lon the system was handing to apps. It saved us about an hour of debugging on day two.

#Mock Location Apps Safe for Legitimate Testing

Two apps stand out for QA and developer work. Neither pretends to bypass anti-cheat. Both follow Google Play’s developer policy on mock locations, and both make the developer-tool framing obvious in their listings.

#Lockito (Android, free with optional one-time IAP)

In our testing on the Galaxy S24, we ran Lockito for ten sessions across two weeks in April 2026. It feeds the mock location API directly, supports custom routes drawn on a map, and lets you tune speed from 1 to 400 km/h plus altitude and accuracy radius. The free tier caps each session at 30 minutes; a one-time in-app purchase removes the cap.

The thing that makes Lockito a developer tool rather than a spoofer is the route editor. You can save GPX files, replay them across builds of an internal app, and capture exactly what the location stack reports for a given path. We used it to reproduce a bug where our staging build’s geofence missed re-entries when the path crossed a polygon boundary at low speed.

Our Lockito review covers the route editor and IAP details in depth.

Lockito’s developer is explicit on the Play Store listing. Don’t use it with apps that prohibit mock locations in their ToS. We treat that as a hard rule.

#GPS JoyStick (Android, free with ads)

GPS JoyStick is the lighter option when you only need a fixed point or a manually steered position. The interface is a floating joystick over the map, which is convenient for ad-hoc QA passes on simple “is the user inside the polygon” checks. It uses the same Android mock location API and shows up correctly in the Developer Options picker.

Different shape of tool, different use case.

When we tried it on our Pixel 8a, we verified a courier-tracking proof-of-concept, confirming that distance-from-pickup updates fired at 50 m and 100 m thresholds. For that single afternoon of testing, the joystick model was faster than drawing a route in Lockito.

#Apps to Avoid for Any Consumer App You Don’t Control

A separate cluster of apps markets itself around bypassing detection on consumer apps.

NirvanaCo GPS Emulator and a handful of clones promise “undetectable” Pokémon GO spoofing, dating-app tricks, or Uber zone tricks. These are off limits for our purposes for two clear reasons.

First, every production app on that list (Pokémon GO, Tinder, Uber, banking apps) prohibits mock locations in its Terms of Service, so using a tool to evade that detection violates the contract you accepted when you signed up. Second, “undetectable” claims age fast: Niantic’s Play Integrity checks have caught wave after wave of these tools, and accounts get banned in batches.

If a tool’s marketing copy talks about evading bans rather than testing apps you own, it’s the wrong tool for this guide.

#Why Does Pokémon GO Ban Mock Location Use?

Niantic treats GPS spoofing as cheating across all its games. According to the Pokémon GO Trainer Guidelines, falsifying location data is one of the listed violations alongside accessing the game with modified clients.

The same enforcement model applies across Niantic’s portfolio.

This includes Pokémon Sleep and the now-discontinued Wizards Unite. A ban on one account often propagates to the others tied to the same device or login. Niantic also bans the underlying device, not just the account, which is why a fresh sign-up on the same phone usually gets caught faster than the original account ever was.

Detection has only gotten stricter since 2022. Modern Niantic anti-cheat combines Google’s Play Integrity attestation with server-side movement analysis. We’ve seen three escalation tiers reported repeatedly in user threads:

1. A soft warning (“we’ve detected unusual activity”)
2. A 7- to 30-day suspension
3. A permanent ban after repeated detection

None of these is worth the risk for a game.

If you’re reading this because you wanted to play Pokémon GO from your couch, the honest answer is straightforward: that path violates Niantic’s ToS, and we are not going to walk you through it. Our fake GPS for Android guide covers the same boundary in more detail.

#Mock Location on iPhone: Why It Doesn’t Exist

iOS doesn’t expose a mock location API to third-party apps, full stop. The closest legitimate equivalent is Xcode’s built-in location simulator, which connects over USB and feeds a fake GPS fix to apps you build and run from Xcode.

This is the same mechanism Apple documents in Xcode’s “Simulating Location” guide.

There is no Android Studio-style “select a mock app on the device” toggle on iOS, and there won’t be one. Apps that claim to spoof iPhone GPS without a desktop connection either require a full jailbreak (which voids your warranty and breaks security guarantees) or are paid desktop tools that re-implement the Xcode debug protocol over a USB cable.

For testing apps you own, the desktop-plus-Xcode path is the only sanctioned approach.

If you want more background on adjacent paths:

• Our location spoofer overview covers why other paths fail.
• Our Android emulator for iOS overview covers cloud-streaming options if you actually need to run Android code paths on iPhone hardware.
• Our fake GPS on iOS guide walks through the Xcode setup specifically.

#How Production Apps Catch Mock Locations

Detection isn’t a single check. Production apps with real anti-fraud teams stack four to six signals and reject the location request if any one of them fails. We confirmed each of the following methods on instrumented test builds during the April 2026 QA cycle.

Modern production apps test for these signals routinely:

• The isFromMockProvider() API call. Any Android location object exposes this directly. Apps that ignore it are uncommon today.
• Play Integrity attestation. Google’s Play Integrity API verifies the device, app binary, and Play Store install path. Mock location use frequently fails the MEETS_DEVICE_INTEGRITY check.
• Speed and acceleration sanity. Two GPS fixes 200 km apart five seconds apart trigger an obvious flag. Even Lockito’s path editor can’t fake the accelerometer alongside GPS.
• Altitude and barometric pressure. Phones with barometers cross-check GPS altitude against pressure readings. A spoof to a coastal city while the barometer reads mountain pressure is a clean detection signal.
• IP geolocation cross-check. A GPS position in Tokyo with a US-based IP address is the easiest to detect of all.

Google recommends that location-sensitive apps use Play Integrity plus on-device sanity checks. Most banking apps, ride-share apps, and games published in 2024 or later follow that guidance.

Older apps may miss one or two signals, but the trend has been one-way in the direction of more detection, not less.

#Bottom Line

For Android developer and QA work on apps you build or have permission to test, install Lockito for route-based scenarios and GPS JoyStick for quick fixed-point checks. Both run through Android’s Select mock location app setting in Developer Options and respect the platform’s developer contract.

Don’t point either of them at Pokémon GO, Pokémon Sleep, Uber, or any banking app on an account you care about. Play Integrity and ToS detection both will catch you, and the bans aren’t negotiable. For iOS testing, Xcode’s location simulator over USB is the only sanctioned path.

#Frequently Asked Questions