Tracking
Tracking & sync
Presets, interval, sync interval, sync condition and accuracy filters
Found under Settings → Tracking & sync. The screen holds five groups in this order: Recording, Sync interval, Sync only on, Positioning accuracy and Accuracy filter. The server address and offline mode live on Connection.
Available Settings
| Setting | Description | Default | Accepted values |
|---|---|---|---|
| Interval | Time between GPS fixes | 5 seconds | ≥ 1 s |
| Movement threshold | Minimum movement to keep a fix | 0 | ≥ 0 |
| Sync interval | Time between uploads | Instant (0) | Instant, 1 min, 5 min, 15 min or Custom |
| Sync only on | Networks Colota uploads over | Any network | See Sync Condition |
| Positioning accuracy | High-precision or battery-saving fixes | High accuracy | High accuracy / Lower accuracy |
| Filter inaccurate locations | Enable/disable accuracy filtering | Off | On/Off |
| Accuracy threshold | Drop fixes rated worse than this | 50 | ≥ 1 |
The interval and movement threshold sit under Custom in the Recording group; picking a preset sets both. The two distance settings use whichever unit you picked in Settings → Appearance, so they read as meters or feet. Every number field takes whole numbers only and states its minimum under its label; a value below it is set to the minimum when you leave the field. There is no upper limit on any of the three numbers.
Tracking profiles override two of these
If a tracking profile is active, it supplies its own interval, movement threshold and sync interval, and its own accuracy filter if it has one, for as long as its condition holds. The Recording and Sync interval groups then open with a line naming the profile and the values in force, as does the Accuracy filter card when the profile has its own filter, and the rows below stay the defaults the app falls back to when no profile applies. A profile is the usual reason fixes arrive at a different rate than the one set here.
Recording
Colota includes built-in presets that configure interval, movement threshold, sync interval and retry interval together. Each row on the screen prints its fix rate, its sync cadence and what it costs.
| Preset | Interval | Distance | Sync interval | Retry interval | Cost |
|---|---|---|---|---|---|
| Instant | 5 s | 0 m | Each fix | 30 s | Most battery, finest track |
| Balanced | 30 s | 2 m | 5 min | 5 min | Moderate battery, fewer wake-ups |
| Power saver | 60 s | 2 m | 15 min | 15 min | Least battery, coarser track |
| Custom | 1 s-∞ | 0 m-∞ | 0 s-∞ | last preset's | Printed from the numbers you set |
Select a preset in Settings → Tracking & sync → Recording or choose Custom to set the interval and movement threshold under it. A preset owns those four values and nothing else: choosing a row in Sync interval or typing an interval there moves the preset to Custom, while the sync condition, the network name, the batch size and the accuracy filter leave it alone. The retry interval is how long a failed sync waits before the next attempt; Custom keeps whichever preset held it last.
Interval
How often the app requests a GPS fix. Shorter intervals keep the GPS awake more of the time and record more points.
- 1-5 seconds: High detail, suitable for driving or cycling
- 15-30 seconds: Good balance for walking or commuting
- 60+ seconds: Low battery usage, suitable for long trips
Movement Threshold
Only records a new location if you've moved at least this far since the last recorded point. Both the interval and this distance must pass before a fix is kept, so a higher threshold saves storage and sync data rather than battery. It is not applied inside a pause zone or by a stationary profile.
- 0: Record every GPS fix (default)
- 10-50 m: Skip stationary updates, good for daily use
Sync Interval
How often queued locations are uploaded. Locations are always recorded and queued locally first.
- Instant (0s): Each location is sent immediately after recording
- Batch (1 min, 5 min, 15 min, or Custom): Locations are queued and sent in batches at the configured interval
With the Overland template, or the Dawarich template in batch mode, a Batch size field appears in this group. See Batch Sync Behavior.
If a tracking profile is active it supplies its own sync interval, and the Sync interval group opens with a line naming the profile and the cadence in force.
Sync Condition
Controls when Colota uploads locations. Locations are always recorded and queued locally regardless of this setting.
| Option | Behavior |
|---|---|
| Any network | Syncs over mobile data as well as Wi-Fi, counting against your plan (default) |
| Wi-Fi or Ethernet | Syncs only on unmetered networks; fixes wait on mobile data |
| Specific Wi-Fi network | Syncs only on the network you name; nothing syncs until one is named |
| VPN | Syncs only while a VPN is up |
This is useful for:
- Limited mobile data - Avoid using cellular bandwidth for location uploads
- Private backends - Only sync when on your home network or VPN
- Roaming - Prevent expensive data charges while traveling abroad
Configure this in Settings → Tracking & sync → Sync only on. For a specific network, type the name as shown in Wi-Fi settings, or take the one the phone is on from the button under the field.
In offline mode, the Sync interval and Sync only on groups are hidden since no syncing occurs, and the retry interval in the preset table is not used. Preset rows show only their recording values. For displaying the maps network requests are still made to maps.mxd.codes. See Offline maps for predownloading maps.
Positioning Accuracy
How precise the continuous location stream is. The exact effect depends on the phone and its ROM.
- High accuracy (default): the most accurate fixes, using more battery. This is what Colota has always used.
- Lower accuracy: coarser fixes that use less battery and can arrive without bearing or altitude.
Only the continuous stream follows this setting: the one-shot fresh fixes behind geofence exit, the pause watchdog and the stationary heartbeat stay on High accuracy, so a network fix can't falsely end a pause. Changing the setting restarts tracking, so it applies at once.
Without Google Play services the effect depends on the ROM. GrapheneOS and Android 15 and older keep GPS on, so Lower accuracy changes nothing there. On Android 16 and newer, and with microG, it can mean network fixes only or none at all. If points stop arriving, switch back to High accuracy.
With the Accuracy filter on, a strict threshold can drop Lower accuracy fixes. They often carry no speed, so a stationary profile can resolve late - or not at all with intervals over a minute or network-only fixes - and the position-jump filter can't compare speed on them.
Accuracy Filter
When on, fixes the chip rates worse than the threshold are dropped. A stricter threshold leaves gaps indoors and in dense streets, where every fix is rated poorly. The switch's own caption carries the threshold in both states, so turning the filter off hides the field without losing the number.
The accuracy value comes from the GPS chip's own estimate of its confidence, not from ground truth. Chips sometimes report a tight accuracy on a position that is badly wrong, and no threshold can reject those, because the fix does not admit to being imprecise. If a stationary device is filling your history with drift, the Movement Threshold is the setting that keeps those points out of the log.
The Google Play variant uses Android's HIGH_ACCURACY positioning mode via FusedLocationProvider, which combines GPS, Wi-Fi, and cellular data. The FOSS variant requests the same high-accuracy mode from the platform's fused location provider on Android 12+ and falls back to GPS_PROVIDER on older versions or ROMs without a fused provider.
Position-Jump Filter
Some GPS chips occasionally emit a single fix that's far off (10s of km) with a wrong altitude but tight reported accuracy. The accuracy filter can't catch these because the chip lies about its own confidence on those fixes.
Colota drops these automatically by comparing the chip's reported speed against the speed implied by the distance and time since the previous fix. When the two disagree by a wide margin, the fix is discarded. The filter is always on, has no user setting, and only triggers on this specific glitch pattern - normal travel passes through because the chip-reported and implied speeds agree closely.
A second check drops any fix that could only be reached faster than an airliner (400 m/s, about 1440 km/h), however long the gap since the last kept fix and whether or not the chip reports a speed. This catches GNSS spoofing and jamming, where a stationary phone suddenly reports a position on another continent with a tight accuracy and a plausible speed. The time between fixes is measured by the phone's own clock, not the GPS time a spoofer can shift. Both fixes' accuracy is allowed for, so a coarse fix never trips it, and a real long-haul flight is kept. If fixes keep failing this check for 15 minutes, at least three of them, the last kept fix is taken to be the wrong one and tracking continues from the newest fix. Fixes Colota requests itself, such as the one that decides whether a pause ends, go through the same check, so spoofing that lasts less than 15 minutes cannot end a pause.
See also
- Connection - the server address, offline mode and what happens when a sync fails
- Tracking profiles - switch interval and movement threshold automatically on charging, speed or a stationary phone
- Geofencing - pause GPS entirely inside a zone