A USB GPS receiver feeds Android navigation apps only through a bridge app set as the mock location provider, not directly.
For the full breakdown, see our best Android GPS USB guide.
A USB port on an Android tablet is not a location port. The connector is wired for charging, media transfer, or Android Auto, and Android has no built-in handler that turns a plugged-in receiver into its location source. Getting a USB GPS receiver working with an Android tablet or head unit comes down to three conditions: a port running in USB host mode, a receiver and bridge app that understand each other, and Android’s mock location setting pointing at that app. Miss one and the setup fails quietly — no error message, just a map that never moves.
Which Android Devices Can Accept A USB GPS Receiver?
A device accepts a USB GPS receiver only when its port runs in USB host mode and the receiver is documented for Android — the port’s shape proves nothing on its own. USB-C tablets need a USB-C OTG adapter; micro-USB models need a micro-USB OTG adapter, and either must carry data, not just power.
Compatibility hinges on the manufacturer’s kernel, the USB chipset, how much power the port can spare, and the app doing the reading, so two tablets with matching specs can behave differently. Head units are the riskier bet. Many expose USB for media, charging, Android Auto, or a proprietary accessory only, and a receiver can show up in the device list while staying invisible to every navigation app.
On the receiver side, most inexpensive USB GPS units output NMEA serial data, which Android does not consume by itself — they need a USB-serial driver or a companion app. USGlobalSat’s BU-353-N runs at 1 Hz with a waterproof housing, magnetic base, and 5-foot cable; the BU-353NC is the USB-C version at 10 Hz; the BU-353N5 adds GLONASS, Galileo, BeiDou, QZSS, and SBAS. None of those listings states Android support outright, so confirm it before buying — the Android GPS USB receivers in our tested roundup are a faster starting point than guessing from spec sheets.
Bluetooth is a separate path, not a preview of the USB one. The Garmin GLO 2 is a Bluetooth receiver rated for up to 13 hours and up to 10 position updates per second, and it proves nothing about how a USB model will behave on the same tablet.
Connecting A USB GPS Receiver To Your Tablet Or Head Unit
The working order is adapter, receiver, bridge app, mock location, then the map app — the bridge has to report a fix before the navigation app opens.
- Seat the receiver in the OTG adapter, plug the adapter into the tablet or head unit, and accept the USB permission prompt.
- Open the bridge app, pick the receiver’s serial interface, and set the baud rate the app lists for that model.
- Turn on Developer options: open Settings > About phone (or About tablet) and tap Build number seven times.
- Go to Settings > Developer options > Select mock location app and choose the bridge app.
- Take the setup outside, place the antenna under open sky, and wait for satellite count, latitude, longitude, and accuracy to populate.
- Open the navigation app and set its external GPS option to Internal (fused), which lets its GPS panel show that the position is mocked.
Expect the map marker to settle on your real position with the satellite count holding steady — that is what a finished setup looks like. Mergin Maps’ external GPS notes cover the same mock-location handoff if a step doesn’t match your screens.
Turn mock locations back off once testing ends. Mock data overrides real GPS, so leaving it on can park your navigation app somewhere you are not.
Why Does The Receiver Show No Fix?
No fix usually means the port never entered host mode, the receiver has no compatible driver or bridge, or the head unit refuses mock locations — the receiver itself is rarely the problem.
| What You See | Likely Cause | What To Do |
|---|---|---|
| Nothing at plug-in | Charge-only port or a power-only adapter | Swap in a data-rated OTG adapter |
| Receiver listed, apps blind to it | No bridge app chosen under Select mock location app | Set the bridge, then reopen the map app |
| Fix appears, then quits | Head unit cannot spare enough USB power | Use a powered hub or the tablet’s own port |
| Fix holds, position is off | Antenna under a coated windshield or indoors | Move the antenna to open sky |
| Coordinates fine, map blank | No downloaded map data or no data connection | Save offline maps before driving |
Two distinctions matter here. Android Automotive OS and Android Auto are not the same thing: a vehicle with Google built in must supply location to apps itself, while Android Auto is a projection layer running off your phone. And an external receiver supplies coordinates only — no internet, no map data, no cellular service — so save offline maps for the area before you rely on it.
If the receiver enumerates on a computer but never on the head unit, the head unit’s documentation settles it: check USB GPS support, the Android version, the receiver chipset, and whether location injection is accepted system-wide or by one navigation app.
Run the sequence once outdoors before anything gets mounted or hardwired. Adapter, receiver, bridge app, mock location app, map app, satellite count holding steady. Then switch mock locations off until the external receiver is genuinely needed.
FAQs
Do I need root access to feed a USB GPS into Android?
No. The mock location developer setting is the supported route, and it sits in plain Settings on stock Android. Root only enters the picture for custom workflows that rewrite system location services, and those are unnecessary for the adapter-plus-bridge setup described above. If Select mock location app is grayed out on a company-managed or carrier-locked device, an administrator has disabled developer options and no app can change that.
Why does Google Maps ignore my external receiver?
Google Maps on Android has no external GPS setting. It reads whatever Android reports through the fused location provider, so the bridge app has to be registered under Select mock location app before Maps will see the receiver’s coordinates. Open Maps after the bridge reports a valid fix, not before. Some apps also smooth or reject mocked positions, which shows up as a jittery or drifting marker.
Will a receiver work on an Android Auto head unit?
Plug the receiver into the phone, not the car. Android Auto mirrors the phone’s screen and uses the phone’s location, so a receiver connected to the handset through an OTG adapter can feed the projection. The car’s own USB ports typically serve charging and data projection only, and they rarely expose a serial interface that a GPS bridge could read.
References & Sources
- Mergin Maps. “External GPS” Documents the mock-location handoff and the Internal (fused) receiver option used in the steps above.
- Android Developers. “Test with the Desktop Head Unit” Explains the Android Automotive and Android Auto distinction and how location is supplied to apps.