The Devs Tools

Setting a Mock Location in Seconds: Map, Search, and Favorites

August 16, 2026 · The Devs Tools Team

Setting a mock location is the developer process of overriding a mobile operating system's Global Navigation Satellite System (GNSS) hardware provider with user-specified geographic coordinates (latitude, longitude, altitude, accuracy) to validate location-dependent application behaviors. Rather than deploying physical handsets to distant geographic coordinates or compiling hardcoded location stubs into debug builds, mock location tools inject simulated coordinates directly into the Android LocationManager framework. This enables mobile developers, QA engineers, and automated test frameworks to verify regional catalog availability, geofencing boundary triggers, localized pricing models, and internationalization rules within seconds.

[!TIP] Want to mock location movement on your test device right now? Try Feint to plan routes, mirror screens, and automate GPS mock coordinates completely offline.

The Need for Rapid, Frictionless Single-Point Mocking

While multi-stop route playback and complex kinematic simulations are necessary for testing active turn-by-turn navigation or fitness tracking, the vast majority of day-to-day mobile QA workflows require only an instantaneous single-point location override:

  • Regional Content and Gating: Verifying that a ride-hailing or delivery application renders the correct local currency, payment rails, and regulatory disclosures for a target city.
  • Geofence Boundary Audits: Placing the device directly on the perimeter of a virtual boundary to assert whether the application fires ENTER or DWELL transition callbacks.
  • Bug Reproduction: Recreating edge-case crashes or anomalous states reported by end users from specific geographical coordinates found in crash telemetry logs.
  • Storefront and Service Pickers: Confirming that local inventory locators and nearest-branch search widgets select the correct regional fulfillment hubs.

When performing these verification steps dozens of times per day, setup friction must be minimized. Connecting to a desktop workstation or opening heavy companion suites for a simple location check slows down developer velocity.

Three Streamlined Input Modalities for Location Setting

To accommodate varied testing inputs—from high-level landmark exploration to exact production coordinate replication—Feint provides three distinct input pathways:

┌─────────────────────────────────────────────────────────────┐
│                 Input Modality Selector                     │
└──────────────┬────────────────┬─────────────────────────────┘
               │                │                │
               ▼                ▼                ▼
     ┌──────────────────┐ ┌───────────┐ ┌───────────────────┐
     │ Interactive Map  │ │  Search   │ │ Exact Decimal     │
     │ Direct Tap / Pin │ │  by Place │ │ Latitude / Longitude│
     └────────┬─────────┘ └─────┬─────┘ └─────────┬─────────┘
              │                 │                 │
              └─────────────────┼─────────────────┘
                                │
                                ▼
         ┌──────────────────────────────────────────┐
         │     Location Normalization & Dispatch    │
         │  - Latitude / Longitude Decimal Degree   │
         │  - Altitude & Accuracy Metatags          │
         └──────────────────────┬───────────────────┘
                                │
                                ▼
         ┌──────────────────────────────────────────┐
         │ Android OS LocationManager Mock Provider │
         └──────────────────────────────────────────┘
  1. Interactive Map Visual Tapping: When exploring general territorial boundaries or visually scouting urban centers, developers can pan, zoom, and tap anywhere on the high-density map interface. The map engine resolves the pixel touch coordinates into standard WGS 84 decimal coordinates (latitude, longitude) and dispatches them immediately to the mock location provider.
  2. Full-Text Geocoding and Place Search: When test specifications dictate locations by landmark name, street address, or airport code (e.g., "Heathrow Terminal 5" or "Berlin Central Station") rather than raw coordinates, integrated forward geocoding enables instantaneous searches. The search subsystem queries place indexes and centers the coordinate marker on the resolved target point.
  3. Direct Coordinate Injection (Decimal Degrees): For bug reports, ticket reproductions, and deterministic automated testing, manual entry allows engineers to input exact floating-point coordinate pairs directly:
    • Latitude: 37.774929
    • Longitude: -122.419416
    • Altitude: 15.5 m
    • Accuracy: 2.0 m

Manual entry supports standard decimal formats, eliminating conversion errors when copying coordinates from Google Maps, OpenStreetMap, or automated telemetry dashboards.

Organizing Test Fixtures: Favorites and Transient History

Repetitive testing across standardized global test fixtures requires persistent organization. Manually searching for the same regional distribution centers, test branches, or overseas airports across daily test cycles introduces unnecessary operational overhead.

┌─────────────────────────────────────────────────────────────┐
│                    Saved Test Locations                     │
├─────────────────────────────────────────────────────────────┤
│ ★ Favorites (Persistent Test Locations)                     │
│   ├── [HQ] San Francisco Office       (37.7749, -122.4194)  │
│   ├── [Branch] London Staging Hub     (51.5074,  -0.1278)   │
│   └── [Geofence] Tokyo Test Depot     (35.6762, 139.6503)   │
├─────────────────────────────────────────────────────────────┤
│ ◷ Recent History (Auto-Logged Coordinates)                  │
│   ├── 10:42 AM - Berlin Mitte         (52.5200,  13.4050)   │
│   ├── 10:35 AM - Sydney CBD           (-33.8688, 151.2093)  │
│   └── 10:15 AM - Paris 8th Arr.       (48.8724,   2.3126)   │
└─────────────────────────────────────────────────────────────┘

Persistent Favorites

Engineers can bookmark recurring testing coordinates as named Favorites. These saved entries are stored locally on the device, allowing one-tap coordinate switching between regional hubs, compliance test zones, and developer staging environments without re-entering coordinate strings.

Automatic Location History

Every point set during a testing session is automatically appended to a chronological History list. If an engineer tests an ad-hoc coordinate to verify an edge-case bug and needs to return to that exact point later in the session, it can be recalled instantly from the history log without having been explicitly bookmarked in advance.

Complete Standalone Architecture: Zero Mac Companion Dependency

A common limitation among desktop developer utilities is requiring a tethered computer to drive basic mock location updates. Feint's coordinate engine is engineered to run 100% standalone directly on the Android target device.

Component Standalone On-Device Requires Desktop / Mac?
Interactive Map Pinning Yes No
Place Search & Address Geocoding Yes No
Manual Coordinate Entry Yes No
Favorites & History Management Yes No
Low-Level Mock Provider Dispatch Yes No
Multi-Stop Route Planning No (Advanced Feature) Yes (Mac Companion)
Simultaneous Multi-Device Control No (Advanced Feature) Yes (Mac Companion)
USB Screen Mirroring (scrcpy) No (Advanced Feature) Yes (Mac Companion)

While the Mac companion app delivers multi-device management, route road-snapping, and screen mirroring, the standalone Android application operates autonomously. Developers can pick up a physical Android test phone, search for a location, and set mock coordinates anywhere—in the office, on transit, or in air-gapped laboratory environments—with zero workstation dependencies.

Summary

Rapid mobile QA requires instant, frictionless coordinate mocking. By combining direct interactive map tapping, full-text address search, and manual coordinate entry with persistent favorites and automatic history logs, Feint enables developers to set mock locations in seconds—completely standalone on the target device, with zero dependencies on desktop companion software.