GPSTest by barbeau: An Open Source Android GNSS Test App

What GPSTest Is For, and Who Should Care

GPSTest is an Android application that displays what a device's GNSS chipset is receiving. The README describes it as an open-source global navigation satellite system testing app, and the feature list is a list of constellations rather than a list of user-facing features: GPS, GLONASS, QZSS, BeiDou/COMPASS, Galileo, IRNSS/NavIC, and several satellite-based augmentation systems including WAAS, EGNOS, GAGAN, MSAS, SDCM, SNAS, SACCSA and SouthPAN.

The audience follows from that. If you are validating a phone or tablet against a specification, comparing two devices on the same rooftop, or checking whether a firmware update changed satellite visibility, GPSTest gives you a readable view of the receiver's own output. It is also useful to Android developers who need to know whether a test device can see enough satellites before blaming their location code.

It is not a navigation tool. Nothing in the README describes turn-by-turn guidance, offline maps, or route planning. The screenshots and the feature list point at signal inspection, and the project's own accuracy page is framed around measuring accuracy rather than consuming it.

How GPSTest Reads Constellations and Dual-Frequency Signals

The mechanism is a direct read of the Android location and GNSS APIs, rendered as satellite tables and sky plots. GPSTest does not compute positions from raw measurements itself; it reports what the platform exposes and organizes it by constellation and by frequency band. That is why the constellation list is the headline feature: the app is a window onto the chipset, and the window is only as wide as the Android version and the hardware allow.

Dual-frequency support carries an explicit caveat in the README. It requires device hardware support and Android 8.0 Oreo or higher. This is the single most important constraint in the project. A phone can run GPSTest perfectly and still show only single-frequency data, because the second frequency is a hardware capability, not an app setting. The README links to a separate article on dual-frequency GNSS on Android for the details.

Data output is handled outside the main screen. The repository contains LOGGING.md and LOGGING-v3.md, and the README points readers at the Data Output and Logging page for sending GNSS data to the system log for further analysis. For anyone doing repeatable work, that logging path matters more than the live display, because it turns a visual check into a file you can diff between devices or firmware versions.

Accuracy measurement has its own page, ACCURACY.md, and the README links a corresponding article on measuring GNSS accuracy on Android devices. The repository layout also includes library/ and wear/ directories alongside the main GPSTest/ module, so the codebase is not a single monolithic app.

Installing GPSTest from Google Play or F-Droid

The README gives two install paths, both as store badges. There is no curl script and no package manager command. For most readers the fastest route is Google Play, where the package is com.android.gpstest. F-Droid carries a separate build under the package name com.android.gpstest.osmdroid.

If you want to build it yourself, the README says you can open and build the project using Android Studio, and points to BUILD.MD for details. The repository root has the usual Gradle wrapper files, so a command-line build is possible, but the README does not spell out a Gradle invocation. Treat Android Studio as the documented path:

# Clone the repository
# git clone https://github.com/barbeau/gpstest.git
# Then open the project in Android Studio and build per BUILD.MD

Once installed, the first real use is to open the app outdoors with a clear view of the sky and let it acquire. You should see satellite entries grouped by constellation, with signal strength and, on capable hardware, more than one frequency. If only one frequency appears, that is a hardware or Android version limit, not a fault in the app.

For repeatable work, follow the logging documentation rather than reading the screen:

# See LOGGING.md for the documented commands to output GNSS data
# to the system log for further analysis

The README does not document rollback, so if you install a beta build through the testing guide, check BETA_TESTING.md for what the project says about returning to a stable release.

Where GPSTest Stops Being the Right Tool

The clearest limitation is platform. GPSTest is an Android application. There is no iOS build in the repository layout, and the README never claims one. If your fleet is mixed, you are testing only the Android half with this tool.

The second limitation is that GPSTest cannot create capability that the hardware lacks. Dual-frequency GNSS requires device hardware support and Android 8.0 Oreo or higher, per the README. On older or lower-tier hardware, the app will faithfully report a single-frequency view, and no amount of configuration changes that.

The third limitation is the nature of the measurement. The app reports what the Android platform provides. It is not a survey-grade receiver and the README makes no accuracy guarantee. The ACCURACY.md page is about how to measure accuracy, which is a different promise from guaranteeing a number. If you need centimetre-level results or a controlled RF environment, a phone running an app is the wrong instrument.

Finally, the README does not document rollback or a stable-versus-beta channel policy beyond pointing at BETA_TESTING.md. Anyone deploying GPSTest across a device lab should read that file rather than assume a downgrade path exists.

GPSTest Compared with Chartcross GPS Test

The obvious alternative for Android users is GPS Test from Chartcross Limited, which appears in the related searches around this project. The difference in approach is ownership and reach. GPSTest is Apache-2.0 licensed, the source is in this repository, and the project accepts contributions, translations through Transifex, and beta testing through a documented guide. You can read the code, build it in Android Studio, and change what it displays.

Chartcross GPS Test is a closed application. You can install it and use it, but you cannot inspect or modify its behaviour, and you cannot add a constellation or a logging format to it. For a one-off check of whether your phone sees satellites, that difference may not matter. For a lab that needs a repeatable, auditable tool, or that needs to log GNSS data in a format it controls, the open source path is the one that can be adapted.

A second distinction is the ecosystem around the project. GPSTest ships a companion library/ directory and a wear/ directory, and its documentation set covers accuracy measurement, logging and translations as separate pages. That is a project organized for contributors, not only for end users.

Licence, Maintenance and the Cost of Upgrading

GPSTest is licensed under Apache-2.0, and the LICENSE file sits at the repository root. That permits commercial and private use, modification and redistribution under the terms of that licence. It is not a copyleft licence, so incorporating the code into a closed product does not by itself force you to publish your source. This is a description of the licence text, not legal advice; read LICENSE and, where the stakes are high, consult a lawyer.

The repository is not archived. The last push was on 2026-09-28, and the most recent release listed is v3.10.6 from 2026-08-29. The two releases before that, v3.10.5 and v3.10.4, both landed on 2024-12-28, so the cadence is not uniform: there was a long gap and then a fresh release. Plan upgrades around releases rather than assuming a fixed schedule.

Upgrade cost is low for users, since the app installs from Google Play or F-Droid and carries no server component. The cost sits with anyone maintaining a fork. The project has a Contributing Guide with code style guidelines and a template, a Transifex configuration for translations, and a Gradle-based Android build. Rebasing a fork means tracking all of that, and translations in particular are managed outside the repository through Transifex.

Editorial conclusion

Adopt GPSTest if you need to see what a specific Android device actually receives from GNSS constellations, or if you want to build and modify that inspection tool yourself. Do not adopt it as a navigation app, a cross-platform product, or a substitute for a calibrated receiver. Verify first that your device and Android version support the signals you intend to test, since dual-frequency GNSS needs Android 8.0 Oreo or higher and matching hardware.

Frequently asked questions

Official sources

1. barbeau/gpstest on GitHub
2. Issues
3. License: Apache-2.0
4. README
5. Releases