Enabling mock location on Android requires turning on Developer Options and selecting a spoofing app under the “Select mock location app” setting.
The first hurdle to enabling mock location on Android is finding where Google hid the switch. On older builds, the setting was a simple toggle called Allow mock locations. Sometime around Android 6.0, that toggle was swapped for a more precise control: Select mock location app. If you search for the old name and can’t find it, that’s why. This article walks through the exact steps for both modern and legacy software, plus the common pitfalls that trip people up.
What Exactly Is Mock Location on Android?
Android’s mock location feature is a developer tool that lets you designate a specific app to supply fake GPS coordinates to the entire operating system. Instead of reading signals from an internal GNSS receiver, the OS pulls location data from your chosen app.
It has two mainstream uses:
- Testing — Developers feed fake coordinates into location-aware apps to confirm behavior without physically traveling.
- External GNSS receivers — Pro users (like surveyors using an Eos Arrow) feed high-accuracy external receiver data into Android by selecting that app as the mock provider.
The feature lives inside Developer Options — a hidden menu that most people never touch. The exact label for the setting depends on your Android version and your phone manufacturer’s skin.
Enabling Mock Location On Android: The Steps That Work Today
The six-step sequence below works on Android 6.0 and higher. If you are on a much older version, jump to the legacy toggle section further down.
- Open Developer Options. Go to Settings > About Phone (or Settings > System > About Phone on Pixel/near-stock Android). Tap Build Number seven times. Android will confirm that developer mode is unlocked.
- Enter Developer Options. Go back to Settings > System > Developer Options. Some OEM skins (Samsung, Xiaomi) place this under Settings > Additional Settings instead.
- Find the mock location control. Scroll to the Debugging section. The entry is labeled Select mock location app on modern builds and Allow mock locations on older ones.
- Install a mock location app. Before you can select it, you need one installed. A widely used free option is Fake GPS Location by Lexa. Download it from the Play Store.
- Assign the app in Developer Options. Tap Select mock location app and choose Fake GPS Location (or whichever app you installed).
- Test the setup. Open the spoofing app, set a fake location, and confirm it works by checking your position in Google Maps. If you are using an external workflow like the Eos Arrow, mock location must also be enabled inside Eos Tools Pro under its own settings menu.
The key detail that catches beginners: simply toggling Developer Options does nothing. Android will not inject fake coordinates until you have both an app installed and that app selected as the mock provider.
| Symptom | Likely Cause | Fix |
|---|---|---|
| Can’t find “Allow mock locations” | The setting was renamed on your Android build | Look for Select mock location app instead |
| Mock location still shows real GPS | No app selected in Developer Options | Go back into Developer Options and choose your spoofing app |
| Developer Options is missing | Hidden by OEM or not yet enabled | Search “Developer” in Settings; otherwise, tap Build Number 7 times |
| Developer Options is grayed out | Enterprise MDM policy has locked it | Can’t be overridden; check with your IT administrator |
| Fake GPS app says mock location not active | Never selected as the mock provider | Revisit Select mock location app and pick it |
| Maps keeps switching back to real location | Location accuracy mode is overriding mock data | Try setting Location Mode to Device Only (GPS only) |
Why Your Phone Hides the Mock Location Setting
Android 4.2 and higher hide Developer Options by default. That is intentional — the tools inside it are for testing, not daily use. The system gives you access only after you deliberately poke the Build Number repeatedly. This prevents casual users from tripping over settings that can break navigation, banking, geofencing, and other location-sensitive services.
Starting with Android 6.0, Google also changed the mock location control from a simple on/off toggle to a specific app picker. The new design is more secure because it prevents any app from silently claiming mock location privileges. Only the app you explicitly name in Select mock location app becomes the authorized provider. If you scan older guides, they will reference the old toggle, which is why so many people get stuck on current phones.
| Feature | Allow Mock Locations (Legacy) | Select Mock Location App (Modern) |
|---|---|---|
| Introduced | Android 4.2 | Android 6.0 |
| How it works | Global toggle — any app with the permission could spoof | Designated app selection — only the chosen app can feed data |
| Security | Lower — any malicious app could claim the privilege | Higher — explicit user assignment required |
| Discovery | Easier to spot in the menu | Often missed because users look for the old toggle name |
| OEM support | Still found on very old custom skins | Standard on Pixel, stock, and most current OEM builds |
When Mock Location Still Won’t Work
If you followed the steps above and your location keeps snapping back to the real one, check these three specific failure points.
Enterprise-managed phones. Corporate MDM policies often block Developer Options entirely. If the Developer Options entry is simply absent when you search for it — or grayed out — the phone is likely under remote management. You will not be able to enable mock location on that device without IT intervention.
Multiple spoofing apps. If you have more than one mock-location-capable app installed, Android only honors the app selected in Select mock location app. Open your Developer Options and confirm the correct app is chosen. Having a second app installed can accidentally draw focus away from the active one.
App-specific detection. Some apps (banking apps, certain games) specifically detect mock location and refuse to run. This is not a problem with your setup — it is the app checking the isFromMockProvider() API and blocking spoofed coordinates. No amount of reconfiguring will fool an app that actively checks for it.
When everything works correctly, you will see the spoofing app running (often with a persistent notification), and your fake location will stick in any app that reads your coordinates without its own anti-spoofing logic.
Mock Location Setup Checklist
- Developer Options are unlocked (Build Number tapped 7 times).
- A compatible mock location app is installed from the Play Store.
- The app is selected in Developer Options > Debugging > Select mock location app.
- If using an external GNSS receiver (Eos Arrow, etc.), mock location is also enabled inside that receiver’s own companion app.
- Tested in Google Maps — the map pin lands on your fake coordinates and does not jump back to the real location.
References & Sources
- Google Pixel Phone Help. Thread confirming the rename to “Select mock location app” on modern builds. Official support thread showing the setting moved and renamed.
- Eos GNSS. “How to Enable Mock Location on Android with Eos Tool Pro.” Explains the dual-enable workflow for external GNSS receivers.
- Fake GPS Location (Lexa). Widely-used mock location app available on the Google Play Store.