# GPSTest ships under two application identifiers and calls dual-frequency a footnote

> An Android app for looking at what the satellite receiver in your handset is actually doing, covering six constellations and eight augmentation systems. The free build carries a different application identifier from the store build, the headline feature is gated on device hardware, and the release history is two patches half an hour apart followed by twenty months of silence.

**barbeau/gpstest** — The #1 open-source Android GNSS/GPS test program

- Repository: https://github.com/barbeau/gpstest
- Stars: 2,415 · Forks: 424
- Language: Kotlin
- License: Apache-2.0
- Published: 2026-09-28 · Updated: 2026-09-28 · Language: en
- Canonical page: https://hysenlabs.com/projects/barbeau-gpstest

## Two application identifiers, and the free one is named after a map library

The install section offers two links and they are not the same application.

```text
play.google.com/store/apps/details?id=com.android.gpstest
f-droid.org/packages/com.android.gpstest.osmdroid/
```

Two different package identifiers, and the second one carries a suffix named after a mapping library. That naming is the tell: the free distribution is the variant built with maps, and the store build is the one without them. So a user who installs from a store and a user who installs from a free software repository are running different builds under different identifiers, which means the two can be installed side by side on one device and will not share data, settings or updates. Nothing on the page states this, and a reader who installs from one and then tries to switch will discover it from the installer. It also means the two listings can drift, and the version numbers in the two stores are the only way to tell which is which.

## Eight augmentation systems, one of them misspelled with Greek letters

The constellation list is six entries with a country each, and the augmentation list underneath is eight, also with attributions: the American, European, Indian, Japanese, Russian and Chinese systems, the Caribbean and South American one, and the Australasian one. That last Caribbean entry is the one worth reading closely, because its Spanish name has two letters that are Greek omicrons rather than Latin o's, so the name will not match any search or any system identifier, and it is the only entry on the page attributed to an international organisation rather than to a country. Both faults are in one line, and both are the kind that a spell checker passes and a copy and paste breaks: paste that line into a search and you get nothing. The other seven spellings are correct, which makes this look like a one character transcription slip rather than a systematic encoding problem.

## The headline feature is a footnote about the handset

The features section opens by saying the app supports dual frequency reception, and then attaches a numbered footnote that takes the claim apart.

```text
Dual-frequency GNSS requires device hardware support and Android 8.0 Oreo or higher.
```

So the most interesting thing on the page is bounded twice: by an operating system version and by whether the handset has the hardware at all. That is the correct thing to tell a reader, and putting it in a footnote rather than in the sentence means the sentence can be quoted without the caveat. The page links out to a long article on dual frequency support on Android devices for the detail, which is the right place for it, but the summary a reader takes away from the features list alone is wrong. The eight augmentation systems are not qualified at all, by contrast, so those read as unconditional coverage when in practice an augmentation signal is only receivable where it is broadcast.

## Two patches half an hour apart, then twenty months

The release history is not a steady line: the two tags numbered 3.10.4 and 3.10.5 landed thirty minutes apart on the same evening in late December 2024, which looks like a fix and its immediate follow up. Then twenty months with no release at all, then a single patch, 3.10.6, in late August 2026. which looks like a fix and its immediate follow up. Then twenty months with no release at all, then a single patch in August 2026. The last recorded commit on the master branch is dated 2026-10-01, five weeks after that newest tag, so the working branch is ahead of anything published. For a user this means the store version is the only version, and it may be either five weeks or two years old depending on which store you look at. For someone who wants to file a bug against current code, the mismatch between what they are running and what is on the branch is the thing to say in the report.

## The documentation is loose Markdown at the root, and one of the files is versioned

There is no documentation directory. The guidance is eight files sitting beside the readme.

```text
ACCURACY.md
BETA_TESTING.md
BUILD.MD
FAQ.md
LOGGING.md
LOGGING-v3.md
TRANSLATIONS.md
AndroidStyle.xml
```

Three things stand out. One file is named with an all capitals extension while the other seven use the conventional one, which breaks a case sensitive glob. There are two logging documents, one of them explicitly suffixed for a major version, which means the pair has to be kept in step manually and the older one will outlive its usefulness. And the code style lives in an editor configuration file rather than in a documented convention, so the style guide is whatever that file says when your editor loads it. A contributor is pointed at a contributing guide inside the repository's own configuration directory for the rules that matter, which is reasonable, and at a separate guide for testing early builds.

## Three support channels, one of them on a hosted application platform

Support is spread across a chat group, a mailing group and a frequently asked questions file, and the choice of hosting for the chat is worth noticing. The chat invite lives on a subdomain of a general application hosting platform rather than on a permanent domain the project controls, and platforms of that kind have a history of retiring free hosting. So the most likely place to ask a question is the least durable link on the page. The mailing group and the frequently asked questions file are the durable ones. Around them the project also runs two documented contribution routes beyond code: an issue label that marks work suitable for a first contribution, with an invitation to comment before starting, and a beta testing guide for people who want builds before everyone else.

## The credibility section is the oldest content on the page

The last section of the readme is a short list of places the app has been mentioned, and both entries are dated: a manufacturer product launch video from March 2020 and a European Union agency news item from August 2018. So the endorsements are five and eight years old respectively, and they are being used to introduce the app to a reader arriving today. They are not false, and a manufacturer's launch video and a regulator's news item are the right kinds of evidence, but they cannot tell you anything about the current version. The tree gives a better sense of what the project is now: an application module, a separate library module, and a wearable module, so this is not only a phone app. There is a release automation directory, a translation platform configuration, icon assets, tooling and script directories, and build files written in the older Groovy style rather than the newer Kotlin one.

## Conclusion

GPSTest suits someone who wants to know what their handset's satellite receiver is actually doing, rather than what the specification says, and who will read the accuracy guide before drawing conclusions from a reading. Two things to check before you rely on it. Dual-frequency support is a property of the device, not of the app, so a handset without the hardware will never show it regardless of version. And the release history is uneven, with the branch running ahead of the newest published tag by some weeks, so a bug report should say which build was actually installed and where from, because the two store builds carry different application identifiers and can be at different versions. The chat channel is also the least durable link on the page; the mailing group and the questions file are the better places to ask.

## FAQ

### What is GPSTest?

An open-source Android application for testing the global navigation satellite system receiver in a handset. It covers six constellations, GPS, GLONASS, QZSS, BeiDou, Galileo and IRNSS, plus eight satellite based augmentation systems, and it is published under the Apache 2.0 licence.

### Where can I get GPSTest?

From a mobile store or from a free software repository, and the two builds have different application identifiers. The repository build carries a suffix named after a mapping library, which indicates it is the variant built with maps, so the two can be installed side by side and will not share data.

### Does GPSTest support dual-frequency GNSS on any phone?

No. The readme states dual-frequency support requires device hardware support and Android 8.0 or higher, so the feature depends on the handset rather than on the app. The page links to a separate long article for the device side of this.

### Which satellite systems does GPSTest report on?

Six constellations, and eight augmentation systems: the American, European, Indian, Japanese, Russian and Chinese ones, the Caribbean and South American system, and the Australasian one. Only the augmentation systems are named individually on the page; the constellations are listed with the country associated with each.

### How do I contribute a translation to GPSTest?

Through the project's translation platform rather than by editing files, with a translations document in the repository describing the arrangement. The readme points at the platform dashboard for both improving an existing language and adding a new one.

## Sources

- [barbeau/gpstest on GitHub](https://github.com/barbeau/gpstest)
- [Issues](https://github.com/barbeau/gpstest/issues)
- [License: Apache-2.0](https://github.com/barbeau/gpstest/blob/master/LICENSE)
- [README](https://github.com/barbeau/gpstest/blob/master/README.md)
- [Releases](https://github.com/barbeau/gpstest/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/barbeau-gpstest