# PDXWalk and OsmTrails: Complete User Guide for AI Assistants

Source: https://osmtrails.com/llms-full.txt
Applies to app version: 20261015 (shown as "v20261015" in More options > About . . .)
Guide date: 2026-10-21
Human-readable FAQ: https://osmtrails.com/faq.html

This file is written for AI assistants (ChatGPT, Claude, Gemini, Copilot and similar) that a
user has pointed here to answer questions about the PDXWalk and OsmTrails Android apps. It is
long on purpose: it records exact on-screen labels, edition differences, and the messages the
apps show, so an assistant can give precise answers instead of guesses.

---

## 0. Instructions for AI assistants

1. **Identify the edition first.** Answers differ between the brands (PDXWalk, OsmTrails) and the
   tiers (Full, Lite, Loaner). If the user has not said which one they have, ask, or tell them
   how to check: the name under the app icon, or main page > More options > About . . . (see
   section 1, "How to tell which edition you have"). If it does not matter for the question,
   say so and answer once.
2. **Answer from this file.** Use the exact labels written here in **bold**. Do not invent menu
   paths, buttons, settings or features. If this file does not cover something, say that plainly
   and suggest the user long-press the nearest button (almost every button opens a help dialog
   on long-press) or contact the developer through the website (PDXWalk.com or OsmTrails.com).
3. **Things these apps do NOT do**, so do not suggest them:
   - No iPhone/iOS version. Android only (Android 7.0 or newer).
   - No turn-by-turn navigation. **Route highlight** shows a named OSM route; it is not routing.
     The walking routes to a target or to the HERE marker are experimental short-distance
     previews, not navigation.
   - No online map tiles while you scroll. Every base map is an offline file that is downloaded
     or imported first.
   - No user accounts, no cloud sync, no automatic upload of tracks. Files leave the phone only
     when the user shares, emails or copies them.
4. **Quote messages exactly** when the user reports one. Section 6.A is an index of the messages
   the apps show, with their meaning and the fix.
5. **Safety.** The apps carry a no-warranty notice (section 1). Do not present the apps as a
   safety or navigation device. For backcountry trips, recommend a paper map and the usual
   precautions in addition to the app.
6. **Labels may appear in capitals.** Android often shows button text in capitals, so **Buy
   Maps** can look like BUY MAPS. A label written with a line break in the app (for example
   "Extract / Track File") is written here on one line.
7. **Trust order.** Where an older in-app help text disagrees with this file, this file describes
   what version 20261015 actually does. Section 6.C.6 lists the known stale in-app texts.

## Notation used in this file

- **More options** = the three-dot overflow menu at the top right of a screen (also written ⋮).
- **Main page** = the screen the app opens on. **MAP page** = the map screen.
- **Long-press** = press and hold about one second.
- "Full only", "Lite", "Loaner", "OsmTrails only" mark edition differences. When nothing is
  marked, the feature is the same in every edition.

## Glossary

- **Profiles file** (`.osmprofilesdb`; downloads arrive zipped as `.osmprofilesdbz`): the app's
  own offline trail database. A curated extract of OpenStreetMap paths, trails, some roads, named
  route relations, named points and crossings, with elevation. It is not a picture map; it is
  drawn as lines and points on top of the base map, and it powers **Lines**, **Route
  highlight**, **Path Name Search**, **Path Systems**, Path System Alerts and snapped exports.
- **Base map**: the background picture. Either a Mapsforge vector map (`.map`) or a raster
  MBTiles file (`.mbtiles`). Only one shows at a time; with none, the background is white.
- **Terrain / hillshade**: a Terrain-RGB MBTiles file that shades hills and valleys over the
  base map (**Show hillshade**).
- **OpenAndroMaps**: a free third-party website with Mapsforge `.map` files for most of the
  world. Downloaded in a browser, unzipped, then added with **Import File**.
- **Rapid Tracking / Rapid Track**: recording a GPS track as an **event**.
- **Event**: one recording session with a start, optional pauses and resumes, and an end time.
  Events are listed on **Show Events (last 8 days)** and can be exported as GPX.
- **Map-only session**: opening the MAP page runs GPS for about 5 minutes so the blue line and
  centering work. It is not an event and is not listed as one.
- **Breadcrumbs** (**Show Breadcrumbs** in the MAP page menu): the master switch for drawing
  Profiles lines and points on the map.
- **Lines / Points / Tracks**: MAP page buttons for Profiles lines, Profiles points and
  crossings, and GPX/GeoJSON track files.
- **Multiline / route relation**: a named OSM route made of many segments (for example the PCT
  or the Portland 40 Mile Loop).
- **Route highlight**: highlights all segments of a tapped named route as one feature.
- **Path System**: a cluster of connected trails (a park's trail network). **Path Systems**
  (in Path Name Search) lists nearby ones; **Path System Alerts (driving)** announces them as
  you drive.
- **Chop Chop**: a phone gesture during an event that takes a burst of accurate GPS fixes and
  saves a **mark**. A mark means "something mattered here"; it is not a lap boundary.
- **Target**: a point you choose; the MAP page shows the distance and direction to it.
- **HERE marker**: the green box at the map center showing the distance from you to the
  center of the map.
- **Code 123**: a confirmation step for large downloads. The dialog itself shows the code; it is
  not a password or license key.
- **Snapped GPX / Plus OSM / Rich / Laps**: kinds of exported GPX files (section 5.15).

## Contents

1. Editions, purchasing, and downloadable data
2. The main page, files, settings, and import
3. The MAP page: controls, layers, and map data
4. Finding and following things: search, Path Systems, Route highlight, tours, targets, compass
5. GPS recording: Rapid Tracking, events, Chop Chop, heart rate, alerts, export
6. Messages, troubleshooting by symptom, and version history

---

## 1. Editions, purchasing, and downloadable data

This section covers the editions, buying maps, and every kind of file the apps can download, import, manage, or share.

### 1.1 The editions

There are two brands, **PDXWalk** and **OsmTrails**. Each is published in two tiers, **Full** and **Lite**. A third tier, **Loaner**, is not sold; it is installed by hand on devices that are lent to people.

| Edition (name under the app icon) | Brand | Tier | Android package id | Ads | Buy maps in app |
|---|---|---|---|---|---|
| **PDXWalk** | PDXWalk | Full | `com.pdxzone.pdxwalk` | No | Yes |
| **PDXWalk-Lite** | PDXWalk | Lite | `com.pdxzone.pdxwalk.lite` | Yes | No |
| **OsmTrails** | OsmTrails | Full | `com.pdxzone.osmtrails` | No | Yes |
| **OsmTrails-Lite** | OsmTrails | Lite | `com.pdxzone.osmtrails.lite` | Yes | No |
| **PDXWalk-Loaner** | PDXWalk | Loaner | `com.pdxzone.pdxwalk.loaner` | No | No (not sold; loaned devices only) |
| **OsmTrails-Loaner** | OsmTrails | Loaner | `com.pdxzone.osmtrails.loaner` | No | No (not sold; loaned devices only) |

- Minimum Android version: Android 7.0 for every edition.
- Each edition has its own package id, so several can be installed on one phone at the same time. Each keeps its own settings and its own app-private files.
- Lite and Loaner have exactly the same download rules (1.4). Lite shows ads (1.5); Loaner has an expiry date (1.3).

### 1.2 How to tell which edition you have

1. **Look at the name under the app icon.** It is one of the six names in the table above. The two brands use different launcher icons.
2. **On the main page, open More options > About . . .** The version line shows `v20261015`. In **Lite and Loaner** it also shows this note: "(The 'Lite' version excludes the ability to download most MBTiles Maps or Profiles files from within the app. Cannot buy maps within the 'Lite' version. ...)". Full editions do not show this note. Loaner editions show it too, even though it says "Lite".
3. **Lite only:** near the bottom of the main page there is an "Advertisements:" strip with an **Authorize Ads** or **Disable Ads** button.
4. **Loaner only:** the status text at the bottom of the main page shows "Loaner Version Expires: (2028-01-31)" followed by return instructions.
5. **Brand on the MAP page:** the title bar shows "PDXWalk" or "OSMTrails". It shows the brand only, not the tier.

**Gotcha:** the **Recent Updates...** dialog header reads "PDXWalk v20261015" in every edition, including OsmTrails. Use the app icon name or the MAP title bar to identify the brand.

### 1.3 Loaner editions: expiry

- Rapid Tracking works through the expiry date shown in the app (2028-01-31). From midnight at the end of that day (phone time), starting Rapid Tracking is blocked, both from **Start** on the Rapid Tracking page and from the start control on the MAP page. Instead the app shows: "If this is a loaner version it might need to be returned to get updates. Rapid Tracking is disabled." with an **OK** button.
- Everything else keeps working: the map, file lists, downloads (same rules as Lite), imports, Extract Track File, and email. An event that is already running keeps running.
- To track again, return the device as the main-page status text says, or install a Full or Lite edition.

### 1.4 Full vs Lite (and Loaner)

| Capability | Full | Lite and Loaner |
|---|---|---|
| GPS tracking, MAP page, track files, Import File, sharing files | Yes | Yes |
| Download the large regional Profiles files (Oregon, West, South, MidWest, NorthEast, UK Britain, West subsets) | Yes | No |
| Download the large regional Mapsforge maps (Oregon, West, MidWest, South, NorthEast, British Isles) | Yes | No |
| Download the small "special" Profiles, Mapsforge maps, and terrain files (Forest Park, Portland, Mt. Hood, Tahoe Rim, Foothills Trail; UK specials in OsmTrails) | Yes | Yes |
| Country-level terrain (hillshade) at zoom 8 (US; also UK in OsmTrails) | Yes | Yes |
| More detailed terrain: country zoom 9/10 and regional zoom 11 | Yes | Hidden |
| Buy raster MBTiles maps (Google Play in-app purchase) on **Buy Maps** | Yes | No |
| Download the free raster MBTiles listed on **Buy Maps** | Yes (all free entries) | Some (listed below) |
| Guided tours that download their own files (4.4) | Yes | Yes |

#### What Lite and Loaner can download

**Profiles** (screen: **Show Downloaded Profiles List**)
- Forest Park, Mount Hood, Portland Metro ("PDXMetro"), Tahoe Rim, Foothills Trail
- OsmTrails editions only: UK-Cumbria, UK-Ledbury-Malvern

**Mapsforge maps** (screen: **Show Downloaded MapsForge Maps List**)
- Forest Park, Portland, MtHood, Tahoe Rim Trail, Foothills Trail
- OsmTrails editions only: UK-Cumbria, UK-Ledbury-Malvern

**Raster MBTiles maps**
- From **Show Downloaded MBTiles List**: the **ForestPk-z13**, **ForestPk-z15**, **ForestPk-z17**, and **MtHood-z13** buttons.
- From **Buy Maps** > **Bought (or, free included)**: MultFalls-z17, PdxMetro-z16, MtHood-z13, US48-z09, UK-Britain-z11, UK-Cumbria-z13, and UK-Cumbria-z15. The note on that screen ("* Lite Version Note: PdxMetro and MultFalls files above are downloadable.") names only two of them, but all seven can be downloaded.

**Terrain (hillshade) MBTiles** (screen: **Show Downloaded MBTiles List** > **Hillshade only**)
- Places & trails: Forest Park, Portland Metro, Mount Hood, Multnomah Falls, Foothills Trail, Tahoe Rim Trail. OsmTrails also has UK-Cumbria and UK-Ledbury-Malvern.
- Country coverage: US at zoom 8 (about 116 MB). OsmTrails also has UK at zoom 8 (about 8 MB).

#### What a blocked download looks like in Lite and Loaner

Menu items for files you cannot download are still visible. The tier check runs after you tap.
- **Profiles:** a "Lite Version Note:" dialog: "The Profiles files are large and expensive to make available for download. This feature is limited to full version." Close it with **Dismiss**.
- **Mapsforge maps:** a "Lite / Loaner Version Note:" dialog. It suggests downloading the same kind of map free from OpenAndroMaps and importing it (1.12), and reminds you that the low-resolution US terrain file (US or UK in OsmTrails) is still available. Buttons: **Open OpenAndroMaps** and **Dismiss**.
- **Raster MBTiles:** a "Lite Version Note:" dialog: "The MBTiles files are very large and expensive to make available for download. This feature is limited to Full version." It also explains how to import MBTiles files made by others.
- **Buy Maps lists:** a short message: "This list is for the Full version. Not available to buy from Lite or Free version." The list still opens.
- **Terrain:** files above zoom 8 for countries, and all regional files, are not listed at all.

### 1.5 Ads (Lite only)

- **Banner ad on the main page:** off until you tap **Authorize Ads** (green). The button then reads **Disable Ads** (red); tap it to hide the banner again. The app remembers your choice.
- **Once-a-day full-page ad:** shown at most once per day (the day changes at midnight UTC) when the app opens, whether or not banner ads are authorized. When you close it, a "Thanks for opening the app!" dialog explains that the ad is an experiment to help pay for future downloads. It offers **Try Route highlight**, which opens the guided tours (4.4), and **Continue to app**.
- The app shows no ad-consent dialog of its own. Full editions have no ads. To avoid ads entirely, use a Full edition.

### 1.6 PDXWalk vs OsmTrails

Both brands share the same features, screens, and download rules. The differences:

| Area | PDXWalk | OsmTrails |
|---|---|---|
| Name, icon, website | PDXWalk, PDXWalk.com | OsmTrails, OsmTrails.com |
| MAP title bar | "PDXWalk" | "OSMTrails" |
| Credit on raster maps | "© PDXWalk.com ..." | "© OsmTrails.com ..." |
| Exported GPX "creator", generated images | PDXWalk branding | OsmTrails branding |
| Guided tours (**Try Route highlight**) | Portland Loop and Mt. Hood Tours only | **US Tours** (Portland Loop, Mt. Hood Tours) and **UK Tours** (Cumbria Tours, Ledbury Loop) |
| UK special downloads: UK-Cumbria and UK-Ledbury-Malvern Profiles and Mapsforge maps | Not offered | Offered in every tier |
| UK terrain (UK-Cumbria, UK-Ledbury-Malvern, UK z8/z9/z10/z11) | Not offered | Offered. z8 and the two specials in every tier; z9, z10, z11 in Full only |
| British Isles Profiles and Mapsforge map | Full only | Full only |
| **Buy Maps** raster catalog | Older generation of raster maps | Somewhat newer generation, including Britain. UK-Britain-z15 is free in OsmTrails Full |
| Forest Park / Mt. Hood raster buttons | Download the original ForestPark and MtHood-z13-202208 files | Download the 2023 (202306) versions |

- The in-app guide text is the same for both brands. Only the tour descriptions change.
- A PDXWalk user can still use a UK Mapsforge map from OpenAndroMaps (1.12). The Cumbria Profiles, the UK tours, and UK hillshade are OsmTrails-only.

### 1.7 Buying raster maps (Full only)

Only raster MBTiles map archives are sold in the app. Profiles files and Mapsforge `.map` files are never sold: Full editions download them at no extra cost, and Lite and Loaner get the subset in 1.4.

**The developer recommends against buying the raster maps first.** The **Buy Maps** screen opens with a "Before you buy raster maps" note. It says the raster files are huge (often many gigabytes) and that the developer now prefers Mapsforge `.map` files plus terrain hillshade. Lite can use that setup too, with free OpenAndroMaps maps. Tap the note to read the details (summarized in 6.C.5) and to reach **Try Route highlight**.

#### How to buy and download a raster map

1. Make sure you are online. On the main page, tap **Buy Maps**.
2. Optional: narrow the list with "Filter by State (OR, not AND):" (WA, OR, ID, MT, WY, CA, NV, UT, CO, AZ, NM) or "Filter by Region (OR, not AND):" (OR WA, ID MT WY, MidWest, NEast, CA NV, UT CO AZ NM, West, South, British Isles). **Hide** and **Show** collapse each filter.
3. Tap **Available To Buy (Requires Internet)**. Each entry shows its file name, size ("N MBs"), and price ("$ N").
4. Long-press a map ("Long Press to begin Purchase or Download").
5. A dialog asks "Would you like start Purchase Flow for: ..." and shows "Enter Code: 123". Type **123** and tap **Yes**. The Google Play purchase sheet opens. When the purchase completes, "Purchase Acknowledged" appears. A cancelled purchase shows no message.
6. Tap **Bought (or, free included)**. Your purchases and the free maps are listed, each marked "Download Now?" or "Already Downloaded".
7. Long-press the map. In "Would you like to download: ...", type **123** and tap **Yes**. Download progress appears in Android notifications.
8. Use the buttons at the bottom of the screen to go to your files: **MBTiles** (raster list), **Maps** (Mapsforge list), **Profiles**.

#### Gotchas

- **What the 123 code is:** a deliberate "are you sure" step for large downloads. It is not a password, license key, or payment. The dialog itself tells you to type 123. Guided tours replace it with their own confirmation.
- **Where purchased maps are stored:** in the **Private Int DL** folder. When the MBTiles list opens there for this reason, it says "Opened Private Int DL because Buy Maps stores downloads here."
- **Large map cooldown:** files of 1,000 MB or more cannot be downloaded again right away. The cooldown is 3 days after the first successful download, plus 3 more days after each later successful download of the same version. Deleting the file does not reset it. The "Large map cooldown" dialog shows the date when you can download again. The download history is kept on each device.
- **A paid map needs a valid purchase to display.** If a paid MBTiles file is in the app's private folders but this device and Google account have no matching purchase, the app shows "File ... requires valid purchase, please buy ... or delete." On **Buy Maps**, More options > **Sync Google Play Purchases** re-reads your purchases.
- **Purchased maps cannot be shared** from the app ("Purchased MBTiles files cannot be shared").
- If the product list has not loaded yet (for example, you just turned on the internet), the app asks you to wait a few seconds and try again.

### 1.8 What a Profiles file is

A **Profiles** file is the app's own offline trail data: a curated subset of OpenStreetMap (OSM) way definitions (paths, trails, and some nearby roads, named route relations, named points and crossings), with elevation added along each path. It is not a display map. A Mapsforge map or raster MBTiles shows you a picture; the Profiles file holds the actual trail lines and their OSM details.

Features that read the Profiles file:
- the **Lines** and **Points** buttons on the MAP page (3.6)
- **Route highlight** (4.3)
- **Go to Path Name Search** and **Path Systems** (4.1, 4.2)
- Path System Alerts and Intersection Alerts (5.3, 5.12)
- walking routes to a target (4.5)
- snapped and "Nearby OSM Lines" exports (5.15)
- coverage checks before tracking starts, when an option that needs Profiles is on (5.1)

Facts about Profiles files:
- Downloads arrive as a zipped `.osmprofilesdbz` file and are unpacked automatically to `.osmprofilesdb`. The unpacked file is larger than the download.
- The file name ends in a year-month stamp that is the OSM data date, for example `OrProfiles202610`. Mapsforge maps use the same stamp, for example `oregon-202610.map`; a Profiles file and a map with the same stamp come from the same OSM download. The 202610 files use OSM data downloaded 2026-10-17.
- Lite and Loaner get small sample areas (1.4).
- Only one Profiles file is in use at a time. You choose it on the Profiles list (1.9).
- Profiles are curated, not complete: they hold OSM ways tagged as paths and some nearby roads, not every street.
- OpenAndroMaps cannot supply Profiles files. They come only from the app's downloads, a guided tour, or an `.osmprofilesdbz` file someone shares with you.

### 1.9 Managing downloaded files

There are three file-list screens, all opened from the main page's More options menu:

| Menu item | Screen title | Header | Choosing the active file |
|---|---|---|---|
| **Show Downloaded Profiles List** | Profile File (OSM+Elev) | "Downloaded Profile files:" | Select a file and tap **Use Selected Profile** |
| **Show Downloaded MBTiles List** | MBTiles Files (raster) | "Downloaded MBTiles Map files:" | Select a file and tap **Show Selected on MAP** |
| **Show Downloaded MapsForge Maps List** | Map Files (vector) (shown with a stray leading dot in 20261015) | "Downloaded MapsForge Map files:" | Select a file and tap **Show Selected on MAP** |

#### Controls shared by all three screens

- **Folder buttons:** **Public Download**, **Private Int DL**, **Private Ext DL**. Each switches the list to that folder. A button appears only if that storage exists on your device; for example, **Private Ext DL** needs removable storage. Each folder is separate, so a file in one does not appear in the others.
- **Coverage focus:** **Map center** or **GPS location**. Each file in the list shows whether it covers that point. This is the same setting as **Near:** in Path Name Search. **GoTo MAP** opens the MAP page.
- **Copy selected file to:** **Int** / **Ext** copies the selected file between internal and external private storage.
- **Delete File** asks "Are You Sure?" / "Do you want to delete <file>?" Tap **Yes** to delete or **No** to cancel. For a file of 1 GB or more, the dialog also reminds you that deleting does not reset the large-map download cooldown.
- **Share** (and More options > **Share selected**) sends the selected file through the Android share sheet (1.13).
- Swipe the list down to refresh it, for example while a large import is still copying or unpacking.

#### Profiles list

1. Tap a file to select it.
2. Tap **Use Selected Profile**. The button reads **Set Selected Profile** (greyed out) when nothing is selected, and **Profile In Use** when the selected file is already the active one. The active file's row is marked **ACTIVE**.
3. More options > **Disable Profiles** is a check-mark toggle that turns Profiles data off without deleting anything. Selecting a profile again turns it back on.
4. Download buttons (under "Get Profile (download):"): **ForestPark**, **Oregon**, **Special profiles...**, **West subsets...**. The More options menu adds: **Download West (11 states, ...)**, **Download MidWest**, **Download South (TX-to-FL)**, **Download NorthEast**, **Download PDXMetro**, **Download MtHood**, **Download UK Britain**.

#### MapsForge maps list

1. Select a `.map` file and tap **Show Selected on MAP**. The button reads **Map In Use** for the file already shown on the map.
2. Checkbox: "Use Theme that shows contours if available?"
3. Download buttons (under "Get Map (download):"): **Forest Park**, **Portland**, **MtHood**, **Other specials...**. The More options menu adds: **Download West (11 states, ...)**, **Download MidWest**, **Download South (TX-to-FL)**, **Download NorthEast**, **Download British Isles**, **Download Oregon**, plus **OpenAndroMaps Info (Third-Party)** (1.12).

#### MBTiles list

1. Choose a filter: **All files**, **Hillshade only** (terrain files), or **Exclude hillshade** (raster maps).
2. Select a file and tap **Show Selected on MAP**. In **Hillshade only**, the list marks the terrain file the map is currently shading with.
3. More options > **Set To No Map At All** clears the raster map selection.
4. Download buttons: with **All files** or **Exclude hillshade**: **ForestPk-z13**, **ForestPk-z15**, **ForestPk-z17**, **MtHood-z13**. With **Hillshade only**, the heading changes to "Get Hillshade (download):" with **Forest Park terrain** and **Other specials...**.

#### Gotchas

- **Freeing space:** **Delete File** removes the file from that folder only. Check the other folder buttons for copies.
- **Uninstalling the app** or using **Clear Storage** in Android Settings deletes the app's private folders (Private Int DL and Private Ext DL), including downloads.
- **Download buttons turn grey** when the file is already in the selected folder or is still downloading. In version 20261015 a failed or cancelled download can also keep a button grey (known issue, fixed in the next update; see 6.B.4).

### 1.10 Downloading each kind of file

All app downloads need an internet connection and run in the background. Progress appears in Android notifications. Files arrive in the app's private download folder for the selected storage. The app needs free space of the file size plus about 300 MB ("Not enough disk space" otherwise). Download messages are listed in 6.A.13.

#### 1.10.1 Profiles files

| Profiles file | Where | Full (both brands) | Lite and Loaner |
|---|---|---|---|
| Forest Park (~5 MB) | **ForestPark** button | Yes | Yes |
| Mount Hood (~10 MB) | More options > **Download MtHood** | Yes | Yes |
| Portland Metro (~50 MB) | More options > **Download PDXMetro** | Yes | Yes |
| Tahoe Rim (~20 MB), Foothills Trail (~9 MB) | **Special profiles...** | Yes | Yes |
| UK-Cumbria (~33 MB), UK-Ledbury-Malvern (~4 MB) | **Special profiles...** | OsmTrails only | OsmTrails only |
| Oregon (~139 MB) | **Oregon** button | Yes | Blocked |
| Oregon, Washington; California, Nevada; Idaho, Montana, Wyoming; Arizona, New Mexico, Utah, Colorado | **West subsets...** | Yes | Blocked |
| West (11 states), MidWest, South (TX-to-FL), NorthEast | More options > **Download ...** | Yes | Blocked |
| UK Britain (British Isles, ~2.0 GB) | More options > **Download UK Britain** | Yes | Blocked |

Steps:
1. More options > **Show Downloaded Profiles List**.
2. Tap a button or menu item. The dialog "Would you like to download: <name>? <size> MB -- Enter Code: 123" opens.
3. Type **123** and tap **Yes**. "Download attempt initiated for <name>" appears. The file is unpacked after it downloads.
4. Select the new file and tap **Use Selected Profile**.

Sizes are approximate and change with each data update. They are the unpacked size ("sizes uncompressed"), which is the space the file takes on the phone, so use them to check that a file will fit. The download itself is smaller.

#### 1.10.2 Mapsforge `.map` files

| Map | Where | Full (both brands) | Lite and Loaner |
|---|---|---|---|
| Forest Park (~2 MB), Portland (~24 MB), MtHood (~15 MB) | Buttons on the screen. Download starts immediately, with no code | Yes | Yes |
| Tahoe Rim Trail, Foothills Trail | **Other specials...** (Yes/No confirmation, no code) | Yes | Yes |
| UK-Cumbria, UK-Ledbury-Malvern | **Other specials...** | OsmTrails only | OsmTrails only |
| Oregon, West (11 states), MidWest, South (TX-to-FL), NorthEast, British Isles | More options > **Download ...** (code 123) | Yes | Blocked; use OpenAndroMaps instead (1.12) |

After downloading, select the map and tap **Show Selected on MAP**.

#### 1.10.3 Raster MBTiles maps

- **Dedicated buttons** on **Show Downloaded MBTiles List** (filter **All files** or **Exclude hillshade**): **ForestPk-z13**, **ForestPk-z15**, **ForestPk-z17**, **MtHood-z13**. Available in every edition. Download starts immediately, with no code.
- **The Buy Maps catalog:** see 1.7. Full editions can buy and download paid maps and download the free ones. Lite and Loaner can download only the seven free entries listed in 1.4.

#### 1.10.4 Terrain (hillshade) MBTiles

Terrain-RGB MBTiles files hold elevation data. The MAP page uses them to draw shaded relief (hillshade) on top of the base map (3.7). They are listed only under the **Hillshade only** filter.

1. More options > **Show Downloaded MBTiles List** > **Hillshade only**.
2. Tap **Forest Park terrain**, or tap **Other specials...** to open "Other hillshade specials". Groups: **Places & trails**, **Country coverage**, **Regional coverage** (tap a heading to collapse it). Each row shows size, maximum zoom, and "Available to download", "Downloading", or "Downloaded".
3. Tap a row. In the "Download <name> hillshade" dialog, type **123** and tap **Download**.

| Terrain file | Max zoom | Approx. size | PDXWalk Full | PDXWalk Lite/Loaner | OsmTrails Full | OsmTrails Lite/Loaner |
|---|---|---|---|---|---|---|
| Forest Park | 12 | 1 MB | Yes | Yes | Yes | Yes |
| Portland Metro | 12 | 6 MB | Yes | Yes | Yes | Yes |
| Mount Hood | 12 | 25 MB | Yes | Yes | Yes | Yes |
| Multnomah Falls | 14 | 2.5 MB | Yes | Yes | Yes | Yes |
| Foothills Trail | 12 | 33 MB | Yes | Yes | Yes | Yes |
| Tahoe Rim Trail | 12 | 38 MB | Yes | Yes | Yes | Yes |
| UK-Cumbria | 12 | 21 MB | No | No | Yes | Yes |
| UK-Ledbury-Malvern | 12 | 0.8 MB | No | No | Yes | Yes |
| US | 8 | 116 MB | Yes | Yes | Yes | Yes |
| US | 9 | 393 MB | Yes | Hidden | Yes | Hidden |
| US | 10 | 1.22 GB | Yes | Hidden | Yes | Hidden |
| UK | 8 | 8 MB | No | No | Yes | Yes |
| UK | 9 | 25 MB | No | No | Yes | Hidden |
| UK | 10 | 73 MB | No | No | Yes | Hidden |
| West | 11 | 1.50 GB | Yes | Hidden | Yes | Hidden |
| Midwest | 11 | 898 MB | Yes | Hidden | Yes | Hidden |
| South | 11 | 987 MB | Yes | Hidden | Yes | Hidden |
| Northeast | 11 | 274 MB | Yes | Hidden | Yes | Hidden |
| UK (regional) | 11 | 213 MB | No | No | Yes | Hidden |

A row marked "Coming soon" is listed but not published yet.

### 1.11 Guided tours that download files

The guided tours (**Try Route highlight**) set up a working example and download only the files that are missing, with their own confirmation instead of the 123 code, in every edition. Entry points, the tour menus per brand, the files each tour downloads, and the steps are in 4.4. Tours do not unlock other regions: a Lite or Loaner user who wants Oregon or another large region is still blocked on the regular download screens.

### 1.12 OpenAndroMaps: free Mapsforge maps you add yourself

OpenAndroMaps (https://www.openandromaps.org/en) is a third-party site with free Mapsforge `.map` files for much of the world. The app never downloads from it; it only opens the site in your browser. It is the main alternative for Lite and Loaner users who need a regional map, and for anyone who needs an area the app does not offer.

#### How to get and import an OpenAndroMaps map

1. Open the site from the app in any of these ways:
   - **Show Downloaded MapsForge Maps List** > More options > **OpenAndroMaps Info (Third-Party)** > **Open Website**
   - the Lite/Loaner blocked-download dialog > **Open OpenAndroMaps**
   - a Cumbria tour > **Own map instead** > **Open OpenAndroMaps** (4.4)
2. In the browser, choose Downloads and then your region (for the Lake District: Europe, then UK-LakeDistrict). Download the **Karte/Map** file, not the theme.
3. The browser saves a `.zip` file in your Download folder. **Extract it** with your Files app so the `.map` file is visible. (**Import File** can open a `.zip` only if it holds exactly one supported file; extracting first always works.)
4. Back in the app, tap **Import File** on the main page. The Android file picker opens in your Download folder. Pick the `.map` file. It is copied into the Mapsforge maps list (2.10).
5. On **Show Downloaded MapsForge Maps List**, select it and tap **Show Selected on MAP**.

#### Limits

- OpenAndroMaps supplies Mapsforge `.map` files only. It has no Profiles files, raster MBTiles, or terrain files. Trail lines, Route highlight, and Path Name Search still need a Profiles file from the app.
- OpenAndroMaps maps do not include the app's own styling that makes "path" lines stand out.
- Its catalog and terms belong to the third-party site and can change.

#### Make or import your own raster MBTiles

- In any edition, copy an `.mbtiles` file into the phone's Download folder (or download it there with a browser), then use **Import File**.
- The developer publishes a desktop tool, the GPX_to_MBTiles_Tool repository on GitHub (https://github.com/LostRat/GPX_to_MBTiles_Tool). It turns a GPX track into a small MBTiles file that keeps high-zoom tiles only near the track.

### 1.13 Sharing files with another device

- Every list screen has **Share** and More options > **Share selected**. They work in every edition and have no tier limit. Sharing sends a copy of a file already on the device; it never downloads anything.
- **Profiles:** the app first asks "Compress for share?" ("<file> is N MB. Zip it to .osmprofilesdbz in the 24-hour share cache, then share?"), tap **Compress**. It zips the file into an `.osmprofilesdbz` (you can leave the screen and tap Share again later), then asks "Share now?" (**Share**). The zip is kept for 24 hours. The recipient imports it with **Import File**.
- **Mapsforge `.map`** and **terrain** files can always be shared. **Raster MBTiles** can be shared unless it is a paid catalog map ("Purchased MBTiles files cannot be shared").
- Track files are shared from **Show Track File List** or **Show Imported GPX List** (2.11, 2.12).
- A Lite or Loaner user can therefore receive and use a shared Profiles file or map that their edition cannot download itself.

### 1.14 No-warranty disclaimer

**When it appears:** the first time the app asks for location permission. The dialog (titled with the app name) shows the disclaimer with **I AGREE** and **I DON'T AGREE**. **I AGREE** continues to a location-use notice (**Turn On** / **No Thanks**) and then the Android permission prompt (2.1). **I DON'T AGREE** closes the dialog without requesting location.

Text, where [website] is PDXWalk.com or OsmTrails.com and [app] is the edition name:

> [website] (Ron Ledbury) MAKES NO GUARANTEES, REPRESENTATIONS OR WARRANTIES RESPECTING THE RELIABILITY OF THE [app] OR ANY GPS DATA. THIS PRODUCT IS NOT SUBJECT TO REVIEW, TESTING, APPROVAL OR CERTIFICATION BY ANY GOVERNMENT OR PRIVATE AGENCY FOR USE IN CONNECTION WITH:
>
> (1) NAVIGATION OR AVIATION ACTIVITIES
> (2) LIFE SAFETY ACTIVITIES
> (3) MOTOR OR OTHER VEHICLES OR VESSELS OF ANY KIND
> (4) ANY OTHER PURPOSE OR USE
>
> ANY USE OF THE [app] app FOR ANY ACTIVITY IN WHICH THE USER'S HEALTH OR SAFETY IS POTENTIALLY AT RISK AND FOR THE ACCURACY OR RELIABILITY OF GPS DATA IS CRITICALLY REQUIRED, COULD RESULT IN DAMAGE TO PERSON OR PROPERTY, UP TO AND INCLUDING INJURY OR DEATH
>
> [website] (Ron Ledbury) SPECIFICALLY DISCLAIMS ANY AND ALL LIABILITY, INCLUDING WITHOUT LIMITATION, CONSEQUENTIAL AND INCIDENTAL DAMAGES THAT MAY ARISE IN ANY WAY FROM THE USE OR RELIANCE ON THE [app] app OR ANY RELATED DATA.
>
> NOTE: PATH DATA (LINES AND POINTS) ARE FROM THE OpenStreetMap Contributors. YOU TOO CAN BECOME A CONTRIBUTOR AND CORRECT ERRORS THAT YOU FIND. THE LINES ARE ONLY AS GOOD AS THAT CONTRIBUTED BY THE LAST EDITOR.

Related: the guided-tour and Buy Maps texts point out that **Route highlight is not routing**. It highlights OSM ways that share a route relation. It does not calculate routes or give turn-by-turn directions.

### 1.15 Quick answers

**Q:** Which edition should I install?
**A:** Full (**PDXWalk** or **OsmTrails**) if you need large regional Profiles files, regional Mapsforge maps, detailed terrain, or paid raster maps. Lite works with the small sample areas, the guided tours, zoom-8 country terrain, and anything you import, such as OpenAndroMaps maps. Choose OsmTrails if you want the UK tours and UK specials.

**Q:** The app asks me to "Enter Code: 123". Where do I get the code?
**A:** The code is 123, as shown in the dialog. It is a confirmation step for large downloads, not a license key or payment.

**Q:** I'm on Lite and tapped "Download Oregon" in the Mapsforge menu, but got a "Lite / Loaner Version Note". Why does the menu show it?
**A:** Menus list every region in every edition, and the tier check happens after you tap. Large regional maps are Full-only. Get a free map for your region from OpenAndroMaps and add it with **Import File** (1.12).

**Q:** Can Lite get an Oregon Profiles file?
**A:** Not by download. Lite can download Forest Park, Mount Hood, Portland Metro, Tahoe Rim, and Foothills Trail (plus UK-Cumbria and UK-Ledbury-Malvern in OsmTrails). It can import an `.osmprofilesdbz` file that a Full user shares with you.

**Q:** I can't find the US zoom 9/10 or regional terrain files in Lite.
**A:** They are Full-only and hidden in Lite. The US zoom-8 file (and UK zoom-8 in OsmTrails) is under **Hillshade only** > **Other specials...** > **Country coverage**.

**Q:** Where are the UK tours in PDXWalk?
**A:** The UK tours, the UK-Cumbria and UK-Ledbury-Malvern specials, and all UK terrain exist only in OsmTrails. British Isles Profiles and map downloads are available in both Full editions.

**Q:** I bought a raster map. How do I download it on a new phone?
**A:** Sign in with the same Google account, open **Buy Maps** > **Bought (or, free included)**, long-press the map, and enter 123. If the map does not show as bought, use More options > **Sync Google Play Purchases**. The large-map cooldown history is kept per device.

**Q:** Can I share a map I bought with a friend?
**A:** No. Purchased raster MBTiles cannot be shared. Profiles, Mapsforge maps, terrain, and free raster maps can be shared.

**Q:** How do I delete a big file to free space?
**A:** Open the matching list (**Show Downloaded Profiles List**, **...MapsForge Maps List**, or **...MBTiles List**), choose the folder button where the file is, select it, tap **Delete File**, then tap **Yes**.

**Q:** How do I stop using Profiles without deleting them?
**A:** **Show Downloaded Profiles List** > More options > **Disable Profiles**.

**Q:** Can I import the OpenAndroMaps `.zip` directly?
**A:** Only if the zip holds exactly one supported file. Extracting the `.zip` with your Files app first and importing the `.map` always works.

**Q:** How do I turn off ads in Lite?
**A:** Tap **Disable Ads** on the main page to hide the banner. The full-page ad still appears at most once a day. Full editions have no ads.

---

## 2. The main page, files, settings, and import

This section covers the screen you see when you open the app (the main page), its More options menu, and the non-map screens reached from it. The file-list screens and downloads are in section 1, the MAP page in section 3, and the Rapid Tracking and Events screens in section 5.

### 2.1 First launch and permissions

1. Open the app. Because location permission is missing, the app immediately shows the **DISCLAIMER** dialog (title = the app name; full text in 1.14). **I AGREE** continues. **I DON'T AGREE** closes the dialog without asking for anything.
2. After **I AGREE**, a disclosure dialog headed "**Will use your location:**" explains why:
   - "To center MAP on your location."
   - "To capture and store in background to display your tracks on MAP, or build GPX export file for you to optionally share via EMail."
   - "Rapid Track option runs continuously for specified time even when you switch to other apps…"
   - Buttons: **Turn On** (shows Android's own permission prompts) or **No Thanks**.
3. Android then asks for the permissions that are still missing:
   - **Location** (precise location is required).
   - **Notifications** (Android 13 and later).
   - **Storage** (Android 10 and earlier only).
4. Afterwards a short message appears at the bottom of the screen: "**Thank You for permission. Try task again.**" If you denied location, it says "<app name> App Requires Access to GPS."

#### The status text on the main page

The text area below the buttons always starts with one of these:
- "**Global Location is turned off.**" Your phone's Location setting is off.
- "**All permissions granted. GPS ready to go.**" It is followed by either "(Note: Notifications are on.)" or a note that Notifications are off. Android requires notifications for the app to keep collecting GPS track data when the app is not on screen.
- "**Permissions Needed** …" Some permissions are still missing. Tap any button to get the permission dialogs again, or grant them in Android **Settings → Apps → <app name>**.

#### Background ("Allow all the time") location

The first-launch prompts do not request background location. The app asks for it only when you tick **Resume Active Tracking After Reboot** on the Rapid Tracking page (5.6). The heart-rate monitor (5.11) does not need it. Other permissions are covered in 5.17.

**Gotchas**
- Almost every main-page button checks permissions first. If a permission is missing, the button shows the permission dialogs instead of doing its job, so tap it again after granting. On Android 13+, Notifications count as a required permission here.
- On Android 13+, if you turned notifications off, background track recording will not continue when the app is closed. You can still use the MAP to see where you are.

### 2.2 The main page

The screen title is the app name. The buttons are arranged in rows, top to bottom. Landscape uses the same buttons.

| Row | Button (on-screen label) | Tap | Long-press |
|---|---|---|---|
| 1 | **Reset Tracks DB** | Opens the reset dialog (2.7) | Help: "Reset Tracks DB Help" |
| 1 | **Show Location Info Below** | Shows your current location in the status area (2.3) | — |
| 1 | **Text MSG My Location** (green) | Opens the text-message preview (2.4) | Help: "Text MSG My Location Help" |
| 2 | **Extract Track File** | Asks for a time period and writes .gpx files (2.5) | Help: "Extract Track File Help" (with a **Track File Settings** button) |
| 2 | **Email Extracted Track File** | Opens the email preview with the newest extract attached (2.6) | Help: "Email Extracted Track File Help" (live status and an **Extract Track File** button) |
| 3 | **Buy Maps** | Opens the maps-for-sale screen (1.7) | — |
| 3 | **Import File** | Opens the Android file picker in the Download folder (2.10) | — |
| 3 | **Start Stop Rapid Track** | Opens the Rapid Tracking page (5.1) | — |
| 3 | **Map** (large, green) | Opens the MAP page (section 3) | — |
| lower left | Compass button (round compass image) | Turns the compass display on/off (2.8) | Help: "Compass Button Help/Explanation" |

- Older instructions mention a **Snap GPS** button. It is hidden in every current edition.
- **Lite only:** an "**Advertisements:**" strip with **Authorize Ads** / **Disable Ads** (1.5).

### 2.3 Show Location Info Below (location readout)

1. Tap **Show Location Info Below**.
2. The status area adds a block like:
   ```
   Current Location
   Latitude:   45.47910° N
   Longitude: 122.51254° W
   Elevation: 85 m  (279 ft)
   Accuracy:  ±5 m
   Fix age:    12 sec ago
   ```
   - Coordinates have 5 decimals, with N/S/E/W.
   - Elevation is in metres and feet, or "Elevation: unavailable".
   - Accuracy only appears if the phone reports it.
   - Fix age is shown as "N sec ago", "N min N sec ago", or "N hr N min ago".
   - If the phone has no fix at all: "No location fix available."
- The readout comes from the phone's last known location. When you open or return to the main page, the app also requests a fresh fix in the background, so tapping again a few seconds later may give a newer, more accurate reading.

**Q:** Why is the fix age large or the accuracy poor? **A:** The readout shows the last fix Android had. Go outdoors, wait a few seconds, and tap again. Opening the main page or the MAP triggers a fresh location request.

### 2.4 Text MSG My Location

1. Tap **Text MSG My Location**. A preview dialog titled "**Last Location . .**" shows **AGE:** (how old the fix is), **ACC:** (accuracy), and the **to:**, **message:**, and **using:** values from your SMS template.
2. If the last fix is older than about 3 seconds or worse than 10 m, the app gets a fresh location ("**Getting Current Location**"). The preview refreshes when a newer fix arrives, for up to 30 seconds.
3. Choose:
   - **forward to sms**: opens your messaging app with the prepared message and a map link. **You must tap Send in that app.** The app never sends texts itself.
   - **edit**: opens the SMS template screen (2.14).
   - **cancel**: closes without sending.

If no messaging app can be opened: "Failed To Invoke Texting App".

### 2.5 Extract Track File (export from the tracks database)

1. Tap **Extract Track File**. A dialog titled "**Export GPS Coordinates From Database to File**" offers: **All**, **Today**, **Yesterday**, **Past Week**, **Last Hour**, **Last 15 Minutes**. Your last choice is pre-selected.
2. Tap **Export** (or **Cancel**). A message confirms the choice, e.g. "Exporting Today's Tracks".
3. The app writes a new .gpx file named `tracks_<ALL|TODAY|YESTERDAY|WEEK|HOUR|15MINS>_yyyyMMdd_HHmmss[_TAG]_.gpx` in the My Tracks folder (Internal or External, per Track File Settings). The TAG part only appears if you set one.
4. If **Set Track File Settings** has extra outputs turned on (snapped GPX, Nearby OSM Lines, Rich Data, GeoJSON; see 5.15), those files are written too. If there is no rich data for the period you see "No rich data available for the selected duration."; the normal GPX is still written.
5. The new files appear in **Show Track File List** and are what **Email Extracted Track File** attaches.

- Extracting does **not** remove anything from the tracks database. Extract as often as you like.
- The duration you pick here is the same setting as **Select Duration:** in Track File Settings.
- Events can also be exported one by one from the Events screen (5.14).

### 2.6 Email Extracted Track File

1. Tap **Email Extracted Track File**. A preview dialog titled "**Last Location . .**" shows:
   - **to:**, **subject:**, **body:** from your email template.
   - "**Include link to current location?**" with the map used.
   - "**Include track file attachments?**", the file list, and an **Age:** in Days/Hours/Mins.
2. **forward to email** opens your email app with the files attached. **You must tap Send in your email app.** **edit** opens the email template. **cancel** closes.
3. The attachments are only what **Extract Track File** last wrote. The email does not read the database.

**Long-press status report.** Long-press **Email Extracted Track File** to see a "**Right now:**" summary:
- "Newest extract: …" (when, and how many files) or "none yet".
- "Tracks database: holds points since …" or "empty (reset, or nothing recorded yet)".
- "Latest tracking event: started …, reached X mi from its start", or "no real movement", or "none since the last reset".
- A verdict: "**Extract again before emailing.**" (if you moved at least 100 m after the newest extract), "**The newest extract is up to date.**", "The newest extract was made before the last reset.", or "**Nothing to attach yet. Tap EXTRACT TRACK FILE first.**"
- The dialog has an **Extract Track File** button that opens the export dialog directly.

If no email app can be opened: "Failed To Invoke Chooser".

### 2.7 Reset Tracks DB

1. Tap **Reset Tracks DB**. A dialog "**Reset Track File Databases to Empty**" warns: "This cannot be undone. Data is not stored anywhere else, other than in track files you may have already exported/extracted."
2. Optional checkbox: "**Reset Cell Data along with other GPS track data.**" Cell signal-strength data is meant to be kept for future hikes, so leave this unchecked normally.
3. Tap **Yes, ReSet GPS Track Data to EMPTY** or **Cancel**. A "RESETTING TRACK DATA" message appears.

What reset removes:
- All recorded points in the tracks database. The live track on the MAP and **Extract Track File** read from these.
- All tracking **events**, so the Events screen becomes empty.
- The Path System Alerts history.
- Cell data, only if you ticked the box.

What it keeps: every extracted track file and every imported or downloaded file.

**Typical workflow** (from the in-app help): RESET at the start of an outing, walk, then EXTRACT TRACK FILE at the end, and email the file if you want a copy elsewhere. Reset is optional: it is also fine to keep several days of tracks (5.16).

**Gotchas**
- Anything recorded but not yet extracted is gone for good after reset. Extract first (there is an **All** option).
- Extracted files live in the app's own folder. Uninstalling the app or using **Clear Storage** in Android Settings deletes them with the database. Email or copy important tracks off the phone (**Copy To Downloads**, 2.11).
- The long-press help for Reset does not mention that events are deleted too, but the reset does delete them.

### 2.8 Compass button (main page)

- Tap to turn the compass display on or off. It only turns on when the phone's Location setting is on.
- When on, it shows a needle, a degrees reading at the top-left, and a magnetic reading at the bottom-left.
- Long-press help explains that it uses the phone's rotation sensors and can flip between readings indoors or in a car (the phone's two compass sensors disagree). It needs figure-8 style calibration after a phone has been off. It is described as "just a curiosity": "Always carry a real compass with a real magnet."
- The MAP page has its own compass tool, the gunsight (4.6).

### 2.9 More options menu on the main page

| Menu item (exact label) | Opens |
|---|---|
| **Recent Updates...** | The "Recent Updates & Feature Guide" dialog (2.16) |
| **Ask AI About This App...** (next update and later) | The "Ask AI about this app" dialog (2.16) |
| **Go to Path Name Search** | Path Name Search (4.1) |
| **Set EMail Settings** | Email template screen (2.14) |
| **Set SMS Text Settings** | SMS template screen (2.14) |
| **Set Track File Settings** | Track File Settings screen (5.15) |
| **Set Track Log Boundary** | Track Log Boundary screen (2.14) |
| **Show Track File List** | Your own extracted and exported track files (2.11) |
| **Show Events (last 8 days)** | Events screen (5.14) |
| **Show Imported GPX List** | Imported tracks screen (2.12) |
| **Show Downloaded MBTiles List** | Raster maps and terrain files (1.9) |
| **Show Downloaded Profiles List** | Profiles files (1.9) |
| **Show Downloaded MapsForge Maps List** | Mapsforge vector maps (1.9) |
| **About . . .** | About dialog with instructions and **Try Route highlight** (2.16) |

### 2.10 Import File (and opening files from other apps)

#### How to import

1. Put the file in your phone's **Download** folder, e.g. download it with a browser or save an email attachment.
2. On the main page tap **Import File**. Android's file picker opens, starting in Download.
3. Pick the file. A message says "**Import started. A zipped map is inspected first, which can take a minute.**"
4. The app copies the file into its own storage and opens the matching list screen.

#### Supported file types and where each one goes

| File | Result | Screen opened after import |
|---|---|---|
| `.gpx` | Copied to the imported-tracks folder | **Imported Tracks** (dialog "**Importing GPX File**") |
| `.geojson`, `.geojson.json` | Copied to the imported-tracks folder | **Imported Tracks** (dialog "**Importing Geojson File**") |
| `.mbtiles` (raster or Terrain-RGB hillshade) | Copied to the MBTiles folder currently shown on the MBTiles screen. If that is **Public Download**, it goes to the app's private download folder instead | MBTiles list (dialog "**Importing MBTiles File**": "If large it may take time to copy. (Swipe list down to refresh.)") |
| `.map` (Mapsforge, e.g. OpenAndroMaps) | Copied to the app's private download folder | Mapsforge maps list ("<file> imported. The list has been refreshed." or "<file> import failed. Check free space and try again.") |
| `.osmprofilesdbz` (compressed Profiles) | Copied, then unpacked to a usable Profiles file | Profiles list (dialog "**Importing Profiles File**": "If large it may take time to decompress. (Swipe list down to refresh.)") |
| `.zip` containing **exactly one** of the files above (**next update and later:** only a `.gpx`, `.geojson` or `.map` file) | The single file inside is extracted and imported as above | Same as the contained file |

- Anything else shows "**Importing Unknown File** — Sorry, this app cannot open selected file." with the file name. A `.zip` holding more than one file is also refused; extract it first.
- An unzipped `.osmprofilesdb` file is copied as is and opens the Profiles list (next update and later; version 20261015 refuses it). Share Profiles as `.osmprofilesdbz`.
- Upper-case extensions are accepted. A file named, for example, `TRACK.GPX` is imported and saved as `TRACK.gpx`; your original file keeps its name.
- If a file with the same name was imported before, you see "<name> is already imported. The existing file was kept." The original is not overwritten. Android "copy" suffixes such as `name (1).gpx` count as the same name.
- Before copying, the app checks for enough free space (file size plus about 10 MB). If there isn't enough, the import does not start, and you see "Not enough free space to import <file>. Free up space and try again." Version 20261015 shows no message here (fixed in the next update).
- After a GPX or GeoJSON import, the confirmation dialog says "The file still needs to be verified. May be deleted from this list if it fails verification. [this is a TODO item]". No verification step runs in this version; the file simply stays in the list.
- Edition limits apply only to downloading from inside the app. **Import File** works in every edition.

#### Opening files and links from other apps

The app registers itself so you can open files directly from a file manager, browser download list, email, or Quick Share. Choose the app (PDXWalk, OsmTrails, etc.) in the "Open with" or "Share" chooser.
- **GPX** and **GeoJSON** files: View or Share.
- **MBTiles** and Mapsforge **.map** files: View.
- **.osmprofilesdbz** Profiles files: View or Share.
- Some generic XML/JSON/binary files are also offered to the app. They are rejected with the "Importing Unknown File" dialog if the name does not end in a supported extension.
- **geo: links** (e.g. `geo:45.5,-122.6?z=14` from another app or web page) open the app's MAP centered on that point. The zoom from `z=` is used if present. `q=lat,lon` is also understood.

**Q:** I downloaded an OpenAndroMaps map but Import File says it cannot open it. **A:** The zip probably holds more than one file. Extract it with your Files app first, then import the `.map` file itself.

**Q:** Where did my imported GPX go? **A:** More options > **Show Imported GPX List**. Imported files are kept separately from your own extracted tracks (**Show Track File List**).

### 2.11 Track File List (More options > Show Track File List)

Screen title: **Track File List**. Header: "Track file list to either delete or to send in email." Hint: "**LongPress item to show track shape.**"

**Folder choice:** **Internal** / **External** radio buttons switch between the app's internal and external track folders (My Tracks). The folder path is shown under the header. Which folder new extracts go to is set by **Storage Location** in **Set Track File Settings**.

**The list:** your extracted and exported files, sorted by the date in the file name. Each row shows a shape thumbnail, a title, a summary such as "X.X mi • N pts • GPX" (the type is GPX, Rich, Snapped, Plus OSM, Laps, or GeoJSON), the date range, and the extras present (heart rate, steps, movement, quality). Tap rows to select or deselect them.

| Button | What it does |
|---|---|
| **DELETE** | Asks "Are You Sure? Do you want to delete selected track files?" then deletes the selected files. **See the known issue below.** |
| **CLEAR Selections** | Unselects everything and clears the tracks chosen for map display |
| **EMAIL SELECTED** | Opens your email app with the selected files attached |
| **SHARE** | Opens Android's share sheet for **one** .gpx or .geojson file ("Share one file at a time") |
| **Copy To Downloads** | After "Are You Sure?", copies the selected files to the phone's shared **Download** folder, where other apps and your PC can see them |
| **CREATE SNAPPED GPX** | Asks "Snap N GPX file(s) to OSM data?" and creates a copy of the track snapped to OSM ways from your active Profiles file |
| **ADD OSM DATA** | For the first selected GPX, shows the active Profiles file and its coverage of the track, then writes a copy that includes nearby OSM ways as routes (next update and later: the copy is `…_PlusOSM_V3.gpx` and takes the ways from every Profiles file in the selected file's folder). Offers **Rebuild OSM Data** if the file already has them, and asks before overwriting |
| **Show Selected Files** | Opens the MAP with up to **5** selected GPX/GeoJSON files drawn (3.8) |

**Long-press a row** to open a track-shape preview with **Show on map** (shows only that file) and **Close**.

> **Warning. Known issue in version 20261015 (fixed in the next update):** confirming **DELETE** on the Track File List also empties the recorded-points database that **Extract Track File** reads from, even when no file is selected. Events are not affected. Until you update, extract any recent tracks before using DELETE.

**Q:** How do I get a track file onto my computer? **A:** Select it and use **EMAIL SELECTED**, **SHARE**, or **Copy To Downloads** (then connect the phone by USB or use a file app).

**Q:** What is a "Laps" file in the list? **A:** It was created by **Export laps** on the Events screen (5.14).

### 2.12 Imported Tracks (More options > Show Imported GPX List)

Screen title: "<PDXWalk or OsmTrails> Imported Tracks". Header "**Imported Track Files:**" and hint "**LongPress item to show track shape.**" Swipe down to refresh the list (useful right after an import).

| Button | What it does |
|---|---|
| **Delete Selected** | Deletes the selected imported files after "Are You Sure?" (this button does not touch recorded points) |
| **Select None** | Clears the selection |
| **Share** | Shares one selected .gpx/.geojson file (also More options > **Share selected**) |
| **CREATE SNAPPED GPX** | Creates an OSM-snapped copy of the selected GPX ("GPX Snapping" dialog) |
| **ADD OSM DATA** | Writes a copy including nearby OSM ways (same as on the Track File List) |
| **Show Selected Files** | Shows the selected files on the MAP |

- Long-press a row for the shape preview with **Show on map**.
- A GPX file containing several tracks is drawn as separate lines on the map.
- The More options item **Select GeoJSON file from Downloads** does nothing in this version. Use **Import File** on the main page instead.

### 2.13 Events (More options > Show Events (last 8 days))

The Events screen lists your Rapid Tracking events from the last 8 days, with filters, **Show on Map**, **Export...**, trimming, and lap detection. It is described fully in 5.14.

### 2.14 Settings screens

#### Set EMail Settings (screen "EMail To Send Tracks")
- Intro: "Plan ahead: save a contact and message so you can share your location with fewer steps when you need to." Below it: "Recipients are saved on this device. When you share your location, the template opens in your chosen app, where you review and send it."
- **Recipients**: a short list of rows, each with **Include recipient**, **Name (optional)**, and **Email address**. "Check the recipients to include. You can leave these blank and choose in your messaging or email app."
- **Message**: **Subject** and message text.
- "**Include current location link**", with the map for the link set to **Google** or **Apple**.
- "**Include recently exported track files**", with file types **GPX**, **GeoJson**, **GPX+OSM**. **GPX+OSM** attaches recent `…_PlusOSM_V3.gpx` files (next update and later); version 20261015 attaches none, because it looks for a file name no export writes.
- Tap **Save** ("Template saved on this device"). If you leave with unsaved changes, the app asks "**Save template changes?**" with **Save** / **Discard** / **Keep editing**. An invalid address shows "Enter a valid email address or leave blank".

#### Set SMS Text Settings (screen "SMS To Send Location")
- Same layout and intro as the email template.
- **Recipients**: rows with **Include recipient**, **Name (optional)**, and **Phone number**. An invalid number shows "Enter a phone number or leave blank".
- **Message**: the message starter. "**Map for location link**": **Google** or **Apple**.
- Tap **Save**. The app never sends texts or email itself; your SMS or email app does.

#### Set Track File Settings (screen "Track File Settings")
Duration, file-name TAG, extra outputs, and storage location. All options and defaults are in 5.15.

#### Set Track Log Boundary (screen "Track Log Boundary")
Two optional boxes, each given as **North Latitude**, **South Latitude**, **West Longitude**, **East Longitude**:
- "**Log Tracks Only Within This:**" (**Reset (only within)** clears it). Points outside this box are not saved.
- "**Log NO Tracks Within This:**" (**Reset (none within)** clears it). Points inside this box are not saved. Use it to keep your home or a private area out of track logs.
- Tap **Save All**. Invalid numbers show "Invalid Coordinates Found".
- Independently of these boxes, the app saves points only in its supported regions: the Americas, Europe, New Zealand and Fiji (5.13).

### 2.15 File-management screens

**Show Downloaded Profiles List**, **Show Downloaded MBTiles List**, and **Show Downloaded MapsForge Maps List** are described in 1.9; downloading is in 1.10. Imported files show up there automatically after **Import File**.

### 2.16 In-app guides

- **Recent Updates...** opens "📱 Recent Updates & Feature Guide". The version line reads "PDXWalk v20261015" in both apps. It has expandable sections, the first opened automatically: **Latest Updates — October 2026**, **Latest Updates — September 2026**, **🧵 Route highlight — Guided Tour**, **🆕 What's New Since v20260707**, **🚶‍♂️ Step Counter**, **❤️ Heart Rate Monitor**, **🗄️ Database Update**, **🎯 GPS Movement Analysis**, **🥢 ChopChop Feature**, **📤 GPX Export with OSM Routes**, **🧭 Compass Gunsight Navigation**, **🔄 What Stays the Same**, **💡 Quick Tips**. Buttons: **Got it!** and **Try Route highlight**.
- **About . . .** shows the app name and version ("v20261015"), the Lite note in Lite and Loaner (1.2), and the "Getting Started" instructions, labelled "updated 20250317". Buttons: **Dismiss** and **Try Route highlight**.
- **Try Route highlight** opens the guided tours (4.4).
- **Ask AI About This App...** (next update and later) opens "Ask AI about this app". It shows the prompt "Read https://osmtrails.com/llms-full.txt, then answer this question about the {app name} Android app: " with an example question. {app name} is the edition's name, such as OsmTrails or PDXWalk-Lite. **Copy** puts the prompt on the clipboard ("Copied. Paste it into your AI assistant and add your question."), **Open FAQ** opens https://osmtrails.com/faq.html in the browser, and **Close** closes it. A user who arrives with that prompt has pasted it into you; their question follows it.
- The content of these texts is summarized in 6.C, and the parts that no longer match the app are listed in 6.C.6.

### 2.17 Notifications and links that open the app

- Tapping a **Path System Alerts** notification opens the MAP fitted to that trail system (5.12).
- Tapping an intersection notification opens the MAP centered on that intersection.
- **geo:** links from other apps open the MAP at that point (2.10).
- **Text MSG My Location** and **Email Extracted Track File** hand off to your SMS and email apps. Opening the current map spot in another map app (Google Maps, OsmAnd) is done from the MAP's amber arrow button (3.10).

### 2.18 Quick Q&A

**Q:** I tapped Email Extracted Track File but my latest walk isn't attached. **A:** Email only attaches the newest extract. Tap **Extract Track File** first. Long-press **Email Extracted Track File** to see whether the extract is up to date.

**Q:** Does Reset Tracks DB delete my GPX files? **A:** No. It empties the tracks database and events. Extracted and imported files stay.

**Q:** I deleted a file in Track File List and now Extract finds no recent points. **A:** That is the known issue in version 20261015 (fixed in the next update): DELETE also empties the recorded-points database. The points can only be recovered if you had extracted them to a file.

**Q:** The app says "Permissions Needed". **A:** Tap any button to get the permission dialogs again (**I AGREE** → **Turn On**), or enable Location and Notifications for the app in Android Settings.

**Q:** Can the app send texts or emails automatically? **A:** No. It prepares the message and opens your SMS or email app. You press Send there.

**Q:** Where is "Trim Old GPS Data"? **A:** In the More options menu of the **Rapid Tracking** page (**Start Stop Rapid Track**). See 5.16.

**Q:** What file types can I import? **A:** .gpx, .geojson / .geojson.json, .mbtiles, Mapsforge .map, .osmprofilesdbz, or a .zip containing exactly one of these.

---

## 3. The MAP page: controls, layers, and map data

The MAP page is opened with the large green **Map** button on the main page. It is the same in every edition and both brands, except that the title bar reads **PDXWalk** or **OSMTrails** and help texts name PDXWalk.com or OsmTrails.com. Search, Route highlight how-to, tours, targets and routes are in section 4; recording is in section 5.

If you see two-letter test buttons such as RT, OT, RR on the map, you are using a developer build.

### 3.1 Screen layout at a glance

Portrait and landscape use the same controls in the same places.

| Where | Control | Tap | Long-press |
|---|---|---|---|
| Top bar | App title (**PDXWalk** / **OSMTrails**) | Changes color as the battery drains (3.13) | - |
| Top bar, More options | Map options menu | See 3.11 | - |
| Top right, first line | Map file name label (starts as **Map-File-Name: NONE**) | Nothing | - |
| Top right | Center button (crosshair) | Center once on your GPS position (3.3) | Double-tap: GPS burst and mark |
| Below the center button | Down/left arrow (**Expand/Collapse**) | Show or hide the right-side control set | - |
| Right-side control set | **Points**, **Lines**, **Tracks**, Map Tiles (MBTiles), Vector Tiles (Mapsforge) buttons | Turn that layer on/off or cycle its states | Help dialog |
| Lower right (in the set) | **Show hillshade**, **Route highlight** checkboxes | Turn on/off | Settings / restore |
| Top left | Satellite button (GNSS sky) | Live GNSS Sky Observer (3.10) | - |
| Beside the satellite button | Compass gunsight | Help and target dialog (4.6) | Move it |
| Below the satellite button | Green Rapid Tracking toggle | Show/hide Start, Pause, Resume, Stop (5.1) | Help dialog |
| Top, between the left and right buttons | Path System Alert strip / Explore pill | See 3.9 and 3.3 | - |
| Lower left, top of stack | North / rotation indicator | Toggle north-up (by mode) | **Map Rotation Mode** sheet (3.4) |
| Lower left, middle | Amber arrow (open in another map app) | Send map center and zoom to another app (3.10) | Help dialog |
| Lower left, bottom | Line order button (paths/multilines) | Swap which line set draws on top | Help dialog with **De-Select Lines** |
| Bottom center | **−** and **+** | Zoom out / in one level | Magnifier down / up (125%, 150%) |

Gotchas:
- Many map buttons are icons with no words. Screen-reader labels on several layer buttons read "Event Tracking" even though they are layer buttons. Describe them by position and icon.
- Long-press works on almost every button and usually opens a help dialog. When a user is unsure what a button does, tell them to long-press it.
- The right-side controls (including **Lines**, **Show hillshade** and **Route highlight**) are visible only while the set is expanded (arrow pointing down).

### 3.2 Zoom, the magnifier, and gestures

1. Tap **+** to zoom in one level, **−** to zoom out one level.
2. Pinch with two fingers to zoom freely.

- Taps less than half a second apart are ignored, so a quick double-tap on **+** counts once.
- With no base map, zoom runs from level 2 to 21. With an MBTiles map showing, zoom stops at the file's own minimum zoom and one level past the file's maximum zoom (capped at 22). Mapsforge maps allow up to 22. The **+** button itself stops at 21.

#### Magnify the map (125% / 150%)

The magnifier draws map tiles larger at the same zoom level, like a reading glass. It helps in bright sun or for small text.

1. Long-press **+** to step the magnifier up: normal → 125% → 150%.
2. Long-press **−** to step it down: 150% → 125% → normal.
3. A snackbar shows **Magnifier 125%**, **Magnifier 150%** or **Magnifier off**.

- The setting is remembered and comes back the next time you open the map.
- Route highlight name buttons grow with the magnifier. Other markers and buttons keep their normal size.

**Q:** The map text looks blurry or oversized. **A:** The magnifier may be on. Long-press **−** until the snackbar says **Magnifier off**.

**Q:** Can I zoom in past the map's detail? **A:** With an MBTiles map you get one extra level past the file's maximum. Turn the tiles off (Map Tiles button) to zoom further into Profiles lines and points (3.5).

### 3.3 Centering and follow-me

#### Center once on your position (single tap)
1. Tap the center button (top right).
2. The map jumps to your last fix if it is under about 100 seconds old, then requests a fresh GPS fix and centers on it when it arrives (if you have not moved the map in the meantime).
3. The button flashes green.

#### GPS burst and mark (double-tap)
1. Double-tap the center button. The button flashes orange.
2. The app takes a short burst of high-accuracy fixes (about 3 to 6 seconds), saves each one, and centers on the result unless you move the map.
3. During a running (not paused) event, a double-tap also saves a mark in the event ("center"), like a Chop Chop gesture (5.9). With no event running, no mark is saved.

#### Follow me (Continuously Center)
1. Open More options and check **Continuously Center**.
2. The map re-centers on each new fix, at most once every 2 seconds.
3. Uncheck it to stop following. It is off by default and the setting is remembered.

#### The Explore pill (centering is off during an event)
While a Rapid Tracking event runs and **Continuously Center** is off, a dark pill appears at the top of the map:
- With no new fixes yet it reads **Continuous centering is off · tap to turn on**.
- Otherwise it counts fixes, for example "3 new fixes · 4 min since centered" (or "since event start"). It refreshes every 30 seconds.
- Tap the pill to turn **Continuously Center** on and center now.
- Tap its **✕** to hide it. It comes back when you reopen the map or tap the center button.

#### Files that cover your location (center button)
When you tap the center button and the selected base map or Profiles file does not cover your GPS position, a dialog **Your location is outside the selected files** offers installed files that do. Choose **Use map ...**, **Use Profiles ...**, or **Keep**. This does not happen during an event with continuous centering on, because then the app switches files itself (5.12).

Gotchas:
- Centering waits for GPS. Indoors, the first fresh fix can take a while; the map first jumps to the last saved fix.
- Zooming or panning during a center request cancels that centering, so the map does not jump away from where you are looking.
- If you pick a file from a list during an event and it does not cover your position, the map says "Continuous centering is off: your location is not inside …" and assumes you are exploring elsewhere.

**Q:** Why does the map keep jumping back to me? **A:** **Continuously Center** is checked in More options. Uncheck it.

**Q:** What is the "N new fixes · X min since centered" bubble? **A:** The Explore pill. Your event is still recording; the map just is not following you. Tap it to follow again, or tap ✕.

### 3.4 Map rotation and orientation

The north indicator sits at the lower left, above the amber arrow. It turns with the map so its red tip points north.

#### Choose a rotation mode
1. Long-press the north indicator. The **Map Rotation Mode** sheet opens.
2. Pick one:
   - **North Up** - **Keep north at the top**. Two-finger rotation is turned off. This is the default.
   - **Manual Rotate** - **Drag to rotate the map**. Rotate with two fingers.
   - **Target Direction** - **Align with target direction**. The map turns so the line to your target points up, and follows as you move. Greyed out with the hint **Set a target to enable this mode** until a target is set and **Show Target Arrow** is on (4.5).

#### Tap the north indicator
- **North Up:** nothing happens (already north).
- **Manual Rotate:** if rotated, snaps to north and remembers the angle; tap again to restore that angle.
- **Target Direction:** switches between pointing at the target and north-up. The choice is remembered.

Gotchas:
- Turning off **Show Target Arrow** in the menu switches Target Direction back to North Up.
- The in-app guide mentions a "Compass Mode" that turns the map to match the phone. The current sheet has no such option.

**Q:** I can't rotate the map with two fingers. **A:** The mode is North Up. Long-press the north indicator and choose **Manual Rotate**.

**Q:** The **Target Direction** option is greyed out. **A:** Set a target (4.5) and make sure **Show Target Arrow** is on.

### 3.5 Base maps: MBTiles, Mapsforge and the blank map

The map draws one base map at a time, all offline:
- **MBTiles** (raster tiles, `.mbtiles`) - picture tiles with a fixed zoom range.
- **Mapsforge** (vector map, `.map`) - drawn on the phone at any zoom up to 22.
- **No base map** (a white background) - Profiles lines, points and tracks still draw on top.

Profiles files are not a base map. They are drawn as lines and points on top of whichever base map is showing (3.6). Terrain hillshade is a separate layer (3.7). There are no online map tiles: if no offline map file is installed or selected, the background stays blank. Download (1.10) or import (2.10) a map file first. Initially, no map is selected.

#### Map Tiles button (MBTiles)
In the right-side set. Its icon is a diamond.
- Tap: if MBTiles is showing, turns the base map off. Otherwise turns MBTiles on (this replaces a Mapsforge map). With no MBTiles file selected, it opens the help instead.
- Long-press: **Map Tiles Toggle Help/Explanation**, with buttons **MBTiles page** (your downloaded MBTiles list), **Buy Maps page** and **Dismiss**.
- The help notes: when tiles are shown, zooming in is limited to the available tiles; with no tiles you can zoom in further on path data and points. "The transition may take a second or two to redraw."

#### Vector Tiles button (Mapsforge)
Next to the Map Tiles button.
- Tap: if Mapsforge is showing, turns the base map off; otherwise turns it on (this temporarily replaces MBTiles). If exactly one `.map` file is installed and none is selected, it selects that one. With no `.map` file, it opens the help.
- Long-press: **Vector Tiles Toggle Help/Explanation**, with **Go to MapsForge Maps page** and **Dismiss**. The help says free `.map` files can be downloaded to your Download folder and added with **Import File** on the main page, and that non-Lite editions may include downloadable `.map` files with contour lines.

#### Reading the two diamond icons
- Teal diamond lit: that button's source is drawing.
- White diamond lit on both buttons: no base map (white background).
- Faint diamond: the other source holds the base map.

#### Choosing a different map file
- More options → **Change MBTiles Map** opens the MBTiles list.
- Long-press the Vector Tiles button → **Go to MapsForge Maps page**.
- The file name label at the top right shows the map file in use, without its extension.

#### How the app picks the file that covers the view
1. **Turning a base map on:** if the selected file covers the map center, it loads. If not, a dialog (**Switch MBTiles file** / **Switch Mapsforge map**) lists installed files that do. If none do (**MBTiles coverage** / **Mapsforge coverage**: "No downloaded … covers the current map center."), you can **Snap to selected** (jump to the selected file's area), open the list page, or **Cancel**.
2. **Center button:** offers covering files for your GPS position (3.3).
3. **Edge switch button:** with a Mapsforge map showing, when part of the screen goes past the edge of the file and another installed file covers that side, a floating button **Switch to map ...** (or **Switch to Profiles ... and map ...**) appears there. Tap to switch.
4. **Snap-back:** if you drag the map so that less than 15% of the screen still shows the base map file, the map pans back to it at the same zoom.
5. **Automatic handoff during an event:** with an event running and **Continuously Center** on, the app switches Profiles and Mapsforge files itself (never MBTiles), choosing the smallest installed file that covers you (5.12).
6. **On opening the map:** a base map or line layer that does not cover the saved view is turned off, with a snackbar "Turned off …: not available for this area. Turn it (them) back on to choose a file that is."
7. **Newer Profiles installed:** "<old> is out of date; <newer> is installed." with **Use it**.

Gotcha: if the map is white, check that a base map button is lit and that a file covering this area is selected. Purchases and download rules per edition are in 1.4 and 1.7.

**Q:** Why is my map blank/white? **A:** No base map is showing, or the selected file does not cover this area. Tap the Map Tiles or Vector Tiles button. If a coverage dialog appears, pick a listed file, or download one that covers the area (6.B.3).

**Q:** Why won't the map let me zoom in further? **A:** MBTiles maps stop one level past their highest zoom. Switch to a Mapsforge map, or turn the tiles off to zoom into Profiles lines.

**Q:** The map pans back when I drag it away. **A:** Snap-back keeps at least part of the map file in view. Choose a map file that covers the area you want to look at.

**Q:** Can the app download map tiles from the internet as I scroll? **A:** No. All maps are offline files that you download or import first.

### 3.6 Profiles lines, points and labels

A **Profiles** file (1.8) is drawn as lines and markers on top of the base map. Nothing from Profiles is drawn until a Profiles file is downloaded and selected and **Breadcrumbs** is on.

#### Turn on Profiles lines
1. Download and select a Profiles file (main page More options → **Show Downloaded Profiles List**).
2. On the map, open More options and check **Show Breadcrumbs**. It is off by default.
3. Make sure the right-side controls are expanded, then tap the **Lines** button.
4. Lines draw at zoom 11 and closer.

If the selected Profiles file does not cover the map center, a **Profiles coverage** or **Switch Profiles file** dialog appears (**Use selected**, **Profiles page**, **Cancel**). During an event it may say **Tracking is running**, with **Switch anyway** or **Keep current** (switching to a file that does not cover you stops routing, OSM way snapping and intersection detection for the rest of that event).

#### Lines button
- Tap: switches between off and paths (path, footway, cycleway, bridleway, steps).
- With **Breadcrumbs** off, a tap opens the help dialog instead.
- Long-press: **Profile Lines Toggle Help/Explanation**. It lists three states: no lines, paths and footways, and paths plus a subset of roads.
  - **Include Roads** switches to paths plus roads. This third state is only reachable here.
  - **GoTo Profiles files.** opens the Profiles list.
  - If Breadcrumbs is off, the dialog offers **Turn on Breadcrumbs** instead.
- Icon: a cyan stroke means paths are on, a white stroke means roads are on, a faint stroke means that layer is off.

| Way type | Color |
|---|---|
| path | red |
| footway | purple |
| cycleway | mint green |
| bridleway | orange |
| steps | light orange, very wide |
| track and minor roads | olive / dark green, thin (paths plus roads only) |

| Route relation (multiline) | Color |
|---|---|
| hiking | blue |
| bicycle | green |
| foot | red |
| road | black (with paths plus roads, or with Route highlight on) |
| ferry | yellow |

#### Line order button (lower left)
OSM data comes as single lines (ways) and as route relations (multilines). Where they overlap, one hides the other.
- Tap: swaps which set draws on top. Route relations draw on top by default. The choice is remembered.
- Long-press: **OSM Line/MultiStringLine Toggle Help/Explanation**, with **De-Select Lines** (clears a long-press selection, see below) and **Dismiss**. The help notes Breadcrumbs can be compute-intensive.

#### Points button
- Tap to cycle: off → points → crossings → both → off.
- With **Breadcrumbs** off, a tap opens the help.
- Long-press: **Points Toggle Help/Explanation**, with **Profiles page** or **Turn on Breadcrumbs**, and **Dismiss**.
- **Points** are named OSM features such as peaks and trailheads (in Portland, named bus stops too). A magenta dot; named points get a cyan label.
- **Crossings** are places where two ways meet or come close. They draw as an orange star, with a two-line label of the two names. (The help text says "blue X"; the app now draws an orange star.) The app is deliberately over-inclusive: some crossings are near-misses, park entries or creek crossings.
- At most 50 of each are shown, nearest the map center, at zoom 10 and closer.
- Tip from the help: turn the Map Tiles off to zoom in further on clustered points and lines.

#### Labels
- **Crossing label colors:** yellow for an ordinary crossing; **cyan** when one of the ways is a waterway (canal, stream, river...), so cyan marks a likely water crossing; pale green when a trail name merely contains "creek", "river" or "stream". An unnamed waterway shows its type, for example "(stream)".
- **Route and path name labels:** with **Route highlight** checked, rotated name labels appear along hiking, bike and road routes, and along named paths, steps and footways (merged into one label per name). Colors: bike green, hike blue, foot red, road black/white. Up to 15 per kind.
- **Label size:** Mapsforge map labels grow as you zoom in past level 15. Profiles labels do not grow with zoom; use the magnifier (3.2) to enlarge them.

#### Tap a trail line
1. Tap a Profiles line.
2. The way is highlighted with a contrasting halo, and its two ends get **bracket end caps** (a loop gets a circle). Its crossings appear; a blue disc marks a potential stream crossing.
3. The map zooms out just enough to show the whole way (never in).
4. An elevation profile marker appears at the lower left (shows PDXWalk.com or OsmTrails.com).
5. A snackbar lists the OSM tags, with **DETAILS** (a details dialog with OSM links) and **DISMISS**.
6. Tap the same way again to clear it.

Tapping a route relation segment with **Route highlight** unchecked does the same and adds the segment number.

#### Route highlight checkbox
The **Route highlight** checkbox (lower right of the expanded control set) turns on whole-route highlighting: tap one segment of a named route and all its segments light up. Long-press the checkbox while checked to restore the previous highlight. The full how-to is in 4.3; guided tours are in 4.4.

#### Long-press the map (select the closest line)
1. Press and hold on the map for about 1 second (not on a marker).
2. The nearest single way is selected in cyan and the nearest route segment in thick yellow. At zoom 16 and closer, red dots show the line's points.
3. The selection is remembered until you clear it with **De-Select Lines** (long-press the line order button).
4. With **Route highlight** checked, if several routes are nearby, **Choose nearby multiline** lists up to 12, with **Select nearest normally** and **Cancel**.

- Long-press on the map is reserved for line selection. It works from the Profiles data even when the Lines button is off.

**Q:** I tapped Lines but nothing appears. **A:** Check **Show Breadcrumbs** in More options, make sure a Profiles file covering this area is selected, and zoom in to level 11 or closer (6.B.5).

**Q:** How do I show roads too? **A:** Long-press the Lines button and tap **Include Roads**.

**Q:** What do the cyan labels mean? **A:** A crossing with a waterway (stream, river, canal): a possible water crossing on the trail.

**Q:** A line stays highlighted cyan/yellow. **A:** That is a long-press selection. Long-press the line order button (lower left) and tap **De-Select Lines**.

### 3.7 Terrain hillshade

Hillshade shades hills and valleys from a Terrain-RGB MBTiles file (1.10.4), drawn over the base map or over the blank map.

#### Turn hillshade on or off
1. Make sure the right-side control set is expanded (arrow pointing down).
2. Tap **Show hillshade**.
3. If the selected terrain file covers the map center, a snackbar says **Hillshade on**. Unchecking says **Hillshade off**.
4. If not, a dialog **Switch Terrain-RGB file** lists covering terrain files. If none cover the area, **Hillshade coverage** ("No downloaded Terrain-RGB file covers <lat>, <lon>.") offers **Use selected**, **Manage MBTiles** (opens the MBTiles list filtered to hillshade files) and **Cancel**.

#### Adjust hillshade
Long-press **Show hillshade** to open the **Hillshade** settings:
- **Opacity** 0-255 (default 150)
- **Exaggeration** 0.50-4.00 (default 1.00)
- **Sun altitude** 10-80° (default 40°)
- **Sun azimuth** 0-359° (315 = north-west)
- Buttons: **Close**, **Defaults**, **Turn off** / **Turn on**, and **Change file**.

Gotcha: the checkbox shows even when no terrain file is installed. Checking it then opens the coverage dialog instead of shading the map.

**Q:** I checked Show hillshade but nothing changed. **A:** No installed terrain file covers the map center. Use **Manage MBTiles** in the dialog to download one for this area.

### 3.8 Tracks on the map

#### Your current track (the blue line)
- The newest recorded points draw as a thick line: the last 10 points in blue on a white outline, older recent points in indigo.
- A pale circle with a black ring marks your newest point ("Here").
- Tap the line to hide it ("Would you like to HIDE this RECENT line?", **Yes, Hide This Recent Line**), or once hidden, to show a longer recent line (**Yes, Show Longer Recent Line**).

#### Map-only session
Each time you open or return to the map, the app runs GPS for about 5 minutes so the blue line and centering work, even with no event running. This map session is **not an event**. Details are in 5.7.

#### Recent days (menu)
In More options, check any of:
- **Show Tracks TODAY** - red thin line, since midnight.
- **Show Tracks YESTERDAY** - green thin line, the previous calendar day.
- **Show Tracks WEEK** - cyan thin line, the last 7 days including today.

These read the same recorded points as **Extract Track File**, including map-only sessions.

#### Track files (the Tracks button)
The **Tracks** button (right-side set, "TRACKS" icon with two diamonds) shows GPX/GeoJSON files you have selected:
1. Tap to cycle: off → your exported tracks → imported tracks → both → off.
2. If no file has been selected yet, a tap opens the help instead.
3. Long-press: **Layer Toggle Help/Explanation**, asking "CENTER map on an Imported or your Exported track?" with **Imported (from others)**, **Exported (your own)** and **OK**.

Choose files:
- Your exported files: on the **Track File List** screen, check files (up to 5) and tap **Show Selected Files**. **CLEAR Selections** clears them.
- Imported files (received from others): on the Imported Tracks screen, check files and tap **Show Selected Files**; **Select None** clears.
- Long-press any file in either list to preview its shape, then tap **Show on map**.

Colors and shapes:
- Your exported tracks: cyan, thick, on a black outline.
- Imported tracks: pink-magenta, thick, on a black outline.
- A GPX file with several tracks shows each track as its own line, never joined. Separate segments within a track also stay separate. A route-only GPX shows its route. A GeoJSON file shows its first line.
- Very large files are trimmed (up to about 20,000 points per file; files over 20 MB load only the first track).
- The map zooms to fit a newly shown track.
- Tapping a track line may show an elevation profile card (pale yellow, purple profile dots, max/min elevation in feet). An orange-red dot marks you when you are near the track. Tap the card to dismiss it.
- A file with fewer than 2 points shows "There are not at least 2 GPS points to draw."

Gotcha: the Tracks icon colors do not match the line colors. On the icon, teal means imported and red-pink means your own; on the map your own tracks are cyan and imported are pink.

**Q:** I opened a GPX with three tracks; why are there three separate lines? **A:** Each track in the file is drawn as its own line on purpose, so separate tracks are not joined by false connecting lines.

**Q:** I only looked at the map; why is there a blue line? **A:** Opening the map runs GPS for about 5 minutes and draws where you have been. It is not an event and is not saved as one (5.7).

**Q:** I selected a track file but it isn't on the map. **A:** Tap the Tracks button until the icon shows the right set (your own, imported, or both). Make sure the right-side controls are expanded so you can see the button.

**Q:** I used **Show on Map** on the Events screen. How do I hide that event's line and bring it back? **A:** The event is saved as one of your own track files, so the **Tracks** button controls it. The map opens showing your own tracks. Each tap then moves on: imported tracks only (event hidden) → both (event shown) → off (event hidden) → your own (event shown). So tap three times for off and once more to bring it back. Or long-press the button and tap **Exported (your own)** to return in one step, centered on the line. There is no single on/off tap.

#### Track Drag Bar (next update and later)
More options → **Track Drag Bar** opens a slider bar under the map. Sliding it moves a cyan diamond along one line of recorded or file points and keeps the map centered on it; the distance along the line shows at the left. Choose the menu item again, or tap ✕ on the bar, to close it. Opening the bar turns **Continuously Center** off, and turning Continuously Center on closes the bar.

The button on the bar names the current source. Tap it to open **Track points for drag bar**:

| Choice | Button | Points |
|---|---|---|
| **Today GPS** | TODAY | The same points as **Show Tracks TODAY** |
| **Current event** | CURRENT | The running event |
| **Most recent completed event (last 8 days)** | LAST EVENT | The newest finished event |
| **Selected track file** | FILE | A shown track file: the one you chose, or else the first shown (your own before imported) |
| **Yesterday GPS** | YESTERDAY | The same points as **Show Tracks YESTERDAY** |
| **Week GPS** | WEEK | The same points as **Show Tracks WEEK** |

- The bar follows one source at a time. The **Show Tracks** lines don't need to be on, and turning them on doesn't change what the bar follows. The bar draws only the diamond, not the line.
- Each source is a snapshot. Choose it again in the list to reload it.
- After midnight, points recorded earlier move from **Today GPS** to **Yesterday GPS**.
- **Week GPS** joins every outing in time order, so the diamond jumps across the gaps between them.
- Picking another source while the bar is open swaps the line and starts again at 0.
- Messages: "{source} needs at least two different GPS points", "No current event", "No completed event in the last 8 days", "No track file selected".
- Track files: after **Show on map** with several files, the snackbar "N tracks shown; the drag bar follows one" has **Choose** ("Drag along which track?"). With the bar closed, tapping a shown track line offers "Drag along {file}" with **Drag**. Long-press the Tracks button for **Drag along the shown track**.

**Q:** How do I slide along yesterday's or this week's track? **A:** Open More options → **Track Drag Bar**, tap the source button on the bar, and choose **Yesterday GPS** or **Week GPS**.

### 3.9 Path System Alert strip (display)

When **Path System Alerts (driving)** is on (5.12), an event is running, and **Continuously Center** is on, alerts also appear as a strip at the top of the map:

- Up to two alert rows, newest first, each reading like the notification, for example "Path system 2.3 km NE" / "4.1 km of trail: <trail names>". On a freeway the distance is told from an exit, for example "... of <exit name>".
- Tap a row to fit the map to that trail system. Centering pauses while you look.
- Tap **✕** on a row to dismiss that alert from the strip (its notification stays).
- With more than two alerts, a "**N more…**" row opens a **Path System Alerts** list.
- After you tap an alert, a large red **Resume centering** button appears. Tap it to fly back to your position at your earlier zoom and continue following.
- If you drive beyond every installed Profiles file, a yellow line says **No Profiles file covers here: no path system alerts**.
- The strip and the red button are large on purpose, for use while driving.

**Q:** I don't see the alert strip. **A:** It shows only during an event with **Continuously Center** on and **Path System Alerts (driving)** enabled.

### 3.10 Markers, target and other map tools

#### HERE marker and target marker
- With **Show Here There Arrow** on (the default), moving the map away from your position draws a green line from you to a green **HERE** box at the map center with the distance (miles, plus meters under 2,000 m). Tap it to set that point as your target; long-press it for an experimental walking route.
- With **Show Target Arrow** on, a cyan **TARGET** box and a cyan line show the distance to your target. Drag it to move the target; tap it for an experimental walking route.
- Full details are in 4.5.

#### Compass gunsight
An oval compass beside the satellite button (on by default). Tap for help and **Set Target**; long-press to move it; double-tap to reset its position. See 4.6.

#### GNSS sky (satellite button)
- Tap the satellite button (top left) to open **Live GNSS Sky Observer**: heading, magnetic field, satellites used/visible, signal strength (C/N₀), HDOP/PDOP, reported accuracy, and a trend over time. Tap **Done** to close.
- It needs GPS running (an event or the map session). Otherwise it says "GNSS sky capture is inactive. Enable GNSS capture and start tracking."
- The dialog marks itself "Diagnostic only"; the thresholds are experimental.
- Long-press does nothing.

#### Open this spot in another map app (amber arrow)
1. Center the map on the place (for example a trailhead) and pick a zoom.
2. Tap the amber arrow at the lower left.
3. Android asks which map app to use (for example Google Maps or OsmAnd). That app opens at the same point and zoom; ask it for directions there.

**Next update and later:** step 3 is a menu, **Open other map**:
- **Directions in Google Maps**: Google Maps opens directions from your current location to the map center. Choose walking, cycling or driving in Google Maps.
- **Directions in OsmAnd**: OsmAnd plans a route from your current location to the map center. Choose the travel profile in OsmAnd. If OsmAnd is not installed, the **Get OsmAnd for offline directions** dialog recommends it for driving to trailheads without mobile coverage (download OsmAnd's maps for the route while you still have internet) and offers **Open Google Play** or **Not now**.
- **Open this point in another map**: what step 3 does in version 20261015.

- The other app opens as its own entry in Recents, so you can switch back and forth.
- If no app can open it: "No map app can open this location". Next update and later, **Directions in Google Maps** without Google Maps shows "Google Maps is not installed or cannot open directions".
- Long-press for **Jump to other Map Help/Explanation**.

#### Links
Links in the OSM feature info dialog open in your browser as a separate Recents entry. If none can open them: "No app can open this link".

#### Other menu layers
- **Show Recent Cell Signal** - cyan squares with signal bar counts from the last 12 hours (at zoom 12 or closer), and green squares for towers near the map center. Recorded with **Capture Cellular Bar Strength?** (5.3).
- **Show Lat Lng Gridlines** - latitude/longitude grid.
- **Re-Center on Selected Path** - centers the map on the path or multiline chosen in Path Name Search (4.1).

### 3.11 The map's More options menu

| Item | What it does |
|---|---|
| **Change MBTiles Map** | Opens the MBTiles list to pick a raster map file |
| **Show Tracks TODAY** / **YESTERDAY** / **WEEK** | Recent GPS lines (red / green / cyan) |
| **Show Recent Cell Signal** | Cell signal markers |
| **Show Lat Lng Gridlines** | Coordinate grid |
| **Show Here There Arrow** | HERE marker and line from you to the map center |
| **Show Target Arrow** | Target marker and line |
| **Show Breadcrumbs** | Turns on Profiles line and point drawing (3.6) |
| **Continuously Center** | Follow your position |
| **Re-Center on Selected Path** | Center on the selected path |
| **Go to Path Name Search** | Opens Path Name Search (4.1) |

Checked items are remembered between visits.

### 3.12 Rapid Tracking controls on the map

The green toggle under the satellite button shows or hides small Start / Pause / Resume / Stop controls for an event, using your saved Rapid Tracking settings. **Stop** appears only after **Pause**. Long-press the toggle for **Rapid Tracking Toggle Help/Explanation**. See 5.1.

### 3.13 Battery warnings in the title bar

The map's title bar changes color with the battery:
- 50% or less: amber.
- 30% or less: orange, **Low Battery** / "Map functionality will stop soon".
- 20% or less: deep orange, **Battery Critical** / "Navigate away & turn off screen immediately".
- 10% or less: red, **⚠ TURN SCREEN OFF NOW!** / "Battery critical - tap power button".

Most battery drain comes from frequent GPS and from keeping the screen on while viewing the map (5.18).

---

## 4. Finding and following things: search, Path Systems, Route highlight, tours, targets, compass

Everything in this section works the same in every edition unless noted. Terms used below:
- **Lines**: single OSM ways, such as one trail or one street.
- **MultiLines**: OSM route relations, which are named routes built from many ways (for example "40 Mile Loop" or "PCT - Oregon Section G").
- Path Name Search, Path Systems, Route highlight, and walking routes all read the selected Profiles file (1.8).

### 4.1 Path Name Search

Path Name Search finds trails, roads, routes, and points by name in the selected Profiles file. It can also list everything near a point, and it can center the map on any result.

#### Open Path Name Search
- From the main page: More options → **Go to Path Name Search**. The app asks for location permission first if it has not been granted.
- From the map: More options → **Go to Path Name Search**.

The screen's title is **Path Name Search**. The name of the Profiles file in use is shown at the bottom of the screen. A **Help** button at the bottom right opens an explanation. More options → **Show Downloaded Profiles List** opens the Profiles file list.

#### Screen layout (top to bottom)
1. **Top row:** a green **▼** triangle (hides or shows the search controls), the **Enter Feature Name** text box, the **Search** button, and the green **GOTO MAP** button.
2. **What to search:** radio buttons **Lines**, **MultiLines**, **Points**. A fourth button, **Xs**, is always disabled.
3. **Filters (Lines and MultiLines only):** radio buttons **Hike**, **Bike**, **Any** (the default is **Any**), and a **Named only** checkbox.
4. **Search origin:** **Near:** with radio buttons **Map center** (default) and **GPS**; a **No roads** checkbox; and a caption that shows the origin's coordinates.
5. **Search range slider** with five steps: **All Results**, **City Wide**, **Area**, **Local** (default), **Nearby**. The current step is shown as "Search Range: …".
6. Two buttons: **Any Near Map Center** (its label changes to **Any Near GPS** when the GPS origin is selected) and **Path Systems** (4.2).
7. The results list.

#### Search by name
1. Choose **Lines**, **MultiLines**, or **Points**.
2. Type a name in **Enter Feature Name** (1 to 30 characters).
3. Choose **Near:** **Map center** or **GPS**.
4. Set the slider. **All Results** searches the whole Profiles file. **City Wide** through **Nearby** limit the search to smaller and smaller areas around the origin.
5. Tap **Search**.

Each Lines or MultiLines result shows the name (or the OSM ID if it has no name), the length in miles, the elevation gain and loss (↑↓) when known, and the distance in miles plus the compass direction from the search origin. An unnamed Lines result is labelled with its road type instead.

How names are matched (current Profiles files, version 4 or later):
- Each word you type matches the beginning of a word in the name. For example, `wild` matches "Wildwood".
- Put the term in double quotes to match an exact phrase.
- In **Lines**, a search term made only of digits and longer than 6 digits is treated as an OSM way ID, and that way is listed.

#### List everything near a point (no search term)
Tap **Any Near Map Center** (or **Any Near GPS**). This ignores the search term and lists every line, multiline, or point (depending on the radio selected) near the origin, using the slider range. If the slider is at **All Results**, the app moves it to **City Wide** for this kind of search.

#### Hike / Bike / Any, Named only, No roads
These filters apply to **Lines** and **MultiLines** and are disabled for **Points**. Changing a filter re-filters the last results immediately, without searching again. The choices are remembered.
- **Any**: no type filter.
- **Hike**: keeps only walkable ways, up to a chosen depth.
- **Bike**: keeps only bikeable ways, up to a chosen depth. Bike also counts the bike-lane tags recorded on a road, so a busy road with a mapped bike lane can pass.
- **Named only**: hides results that have no name.
- **No roads** (Lines only): removes vehicle roads from Lines results and keeps paths, footways, steps, cycleways, and bridleways.

Choose which road types Hike or Bike includes:
1. Long-press **Hike** (or **Bike**).
2. A dialog titled **Hike: keep** (or **Bike: keep**) lists the depths. Each depth also includes everything above it:
   - **Hike:** **Trails only**; **Trails, forest roads and cycleways**; **Also quiet streets** (the default); **Also busy roads**.
   - **Bike:** **Bikeways and greenways**; **Also bike-friendly streets and MTB**; **Also mixed use: paths, tracks, tertiary** (the default); **Also busy roads**.
3. Tap a depth. The app selects that radio button, re-filters the list, and shows a snackbar such as "Hike: Trails only".

Even at **Also busy roads**, Hike and Bike leave out the heaviest roads (primary, trunk, motorway). Only **Any** shows those.

For **MultiLines**, the filter uses the route type:
- **Hike:** hiking and foot routes count as trails. Bicycle, horse, and mixed routes count at the next depth. Other route types appear only under **Any**.
- **Bike:** bicycle routes count as bikeways, MTB routes as bike-friendly, mixed routes as mixed use, and road routes as busy roads.

#### Search near map center vs. GPS
- **Near:** sets the origin for both "near" searches and the distances shown in the list. **Map center** is the map's last center; **GPS** is your last known location.
- **GPS** is disabled when the app has no GPS location yet. The caption then shows "GPS location unavailable".
- This setting is shared with the Profiles, MBTiles, and Mapsforge file lists, which use it to show whether each file covers the map center or your GPS location.
- If the origin is outside the selected Profiles file, a **Profiles coverage** dialog (or a list of covering files) offers to switch to a downloaded Profiles file that covers it, or to open the **Profiles page**. Searches at **All Results** skip this check.
- If a tracking event is running and the file you pick does not cover your GPS position, a **Tracking is running** dialog warns that switching stops routing, OSM way snapping, and intersection detection for the rest of that event. The choices are **Switch anyway** and **Keep current**.

#### Center the map on a result
1. **Tap** a result to see a short distance message ("Distance to centroid of line: …"). Tapping does not move the map.
2. **Long-press** a result. A dialog asks "Would you like to set Map Center to <name>?" and has an **Also set as target** checkbox.
3. Tap **Yes**.
   - If your current base map does not cover the result, a **Switch base map** dialog lists downloaded MBTiles or Mapsforge files that cover it ("Mapsforge: name (App downloads)" and similar). You can also choose **White board** (a blank background) or **Never mind**, which keeps the current map center ("Kept the current map center"). If no downloaded file covers the result, the dialog is titled **Base map coverage**.
   - A message confirms "Map Center Set For <name>", or "Map Center and Target Set For <name>".
4. Tap **GOTO MAP**. The map opens at that center, at your current zoom level. The chosen line or route is drawn as the selected path.

Later, on the map, More options → **Re-Center on Selected Path** moves the map back to the selected path.

#### Gotchas
- A search term that is empty or longer than 30 characters does nothing, and no message appears.
- Common names repeat, so long result lists can be trimmed. Narrow the search with the slider, **Named only**, or a longer name.
- At **All Results** a search can take a while, because it scans the whole Profiles file.
- **Also set as target** saves the target, but it does not turn on the map's target display. If you don't see the target, turn on map menu → **Show Target Arrow**.
- The in-app **Help** text refers to the near-search button by an older name, 'PATHS NEAR MAP'.

**Q:** Why do I get no results for a trail I can see on the map?
**A:** Check four things: (1) the slider range (try **All Results**); (2) the **Hike**/**Bike** depth or **Named only**, which may be hiding it; (3) that you chose **Lines** for a single trail or **MultiLines** for a named route; (4) that the selected Profiles file covers that area. The file name is shown at the bottom of the screen.

**Q:** What is the difference between Lines and MultiLines?
**A:** **Lines** are individual OSM ways, such as one trail segment or one street. **MultiLines** are named OSM route relations made of many ways, such as the PCT or a city loop route.

**Q:** Can I search by OSM ID?
**A:** Yes, for **Lines**. Enter the way ID (more than 6 digits, digits only) and tap **Search**.

**Q:** How do I hide the controls to see more results?
**A:** Tap the green **▼** at the top left. Tap it again to bring the controls back.

### 4.2 Path Systems (nearby trail systems)

A "path system" is a group of trail ways (path, footway, steps, track, bridleway) in the Profiles file that connect to each other. Ways that come within about 25 m of each other are grouped together. A short street crossing can therefore join two halves of a park, while parks a block apart stay separate. Systems with less than about 1 km of trail are not listed.

1. Open **Path Name Search** and set **Near:** to **Map center** or **GPS**.
2. Tap **Path Systems**.
3. A dialog titled **Path systems near map center** (or **near GPS**) offers **Within 1 km**, **Within 2 km**, **Within 5 km**, and **Within 10 km**. Pick one. A snackbar shows "Finding path systems within N km...".
4. A dialog titled **Closest path systems within N km** lists up to 5 systems, nearest first. Each row shows:
   - up to three trail names (longest first), or "Unnamed paths";
   - how many ways it has, the total km of trail, and either "here" (when you are within 50 m) or the distance and direction to its nearest point (for example "1.2 km NE").
5. Tap a system. The app fits the map to that whole system (offering a covering base map first if needed) and opens the map.

Gotchas:
- "Path systems need a Profiles file with a tile index (version 4 or later)" means the selected Profiles file is too old. Download a current Profiles file.
- "No path systems within N km" means no qualifying trail group was found. Try a larger radius, or check that the origin is inside the selected Profiles file.
- **Path System Alerts (driving)** announces the same kind of trail systems while you drive (5.12).

**Q:** Does Path Systems use my search term?
**A:** No. It uses only the origin (**Map center** or **GPS**) and the radius you pick.

### 4.3 Route highlight (whole named routes)

Profiles files contain named OSM ways and multiline route relations. When **Route highlight** is on, tapping one segment of a named route highlights all of that route's segments in view as one thick, connected feature. The highlight extends as you pan. It draws only real mapped geometry and never invents connecting lines.

Route highlight is **not routing**. It only highlights OSM ways that belong to the same route in the OpenStreetMap database. It does not calculate a route to a destination or give turn-by-turn directions.

#### Turn on Route highlight
1. On the map, turn on **Breadcrumbs**: More options → **Show Breadcrumbs**.
2. If the right-side controls are hidden, tap the expand/collapse arrow under the center button.
3. Tap the **Lines** button so that trail lines from the Profiles file are drawn (3.6). If Breadcrumbs is off, tapping **Lines** opens a help dialog with a **Turn on Breadcrumbs** button.
4. Check **Route highlight** (lower right of the control set). A snackbar says "Route highlight enabled" (or "Previous multiline restored").

The guided tours (4.4) do all of these steps for you.

#### Use it
1. **Tap a segment** of a named route. All its segments in view are highlighted together as one fat line, and a green info marker shows the segment number, gain/loss, and miles. A snackbar lists the OSM tags; tap **DETAILS** for a details dialog, or **DISMISS**.
2. If several routes are under your finger, choose from **Choose multiline route**. Replacing an existing highlight asks **Switch extended multiline?** (**Switch** / **Keep**).
3. The highlighted route gets a **name button** (a rounded label along the line), slightly larger than ordinary line-name labels. Smaller name buttons are labels only; they do not respond to taps.
4. **Tap the larger name button** to open whole-feature details: Type, Bicycle, Network, Reference, Length (miles), an **OSM relation** link to openstreetmap.org, the OSM tags, and any website links stored in the tags. **Copy all** copies the details ("Feature details copied"); **Close** closes the dialog. Links open in your browser as a separate task, so you can switch back. External links may be outdated, and the dialog says so.
5. **Long-press the larger name button** to open a menu:
   - **Show whole feature**: zooms out to show the entire route.
   - **Zoom back to previous view**: appears after you used **Show whole feature** on that same route, and returns to your earlier view.
   - **Dismiss fat line**: removes the highlight.
   - **Keep**: closes the menu with no change.
6. While a highlight shows, taps on other routes are ignored below zoom 12.
7. Unchecking **Route highlight** clears the highlight ("Route highlight cleared"). **Long-press the checkbox** while checked to restore the last highlighted route ("Previous multiline restored", "Previous multiline is outside the map view", or "No previous multiline to restore").

**Q:** I tapped a trail but only one short piece lit up.
**A:** **Route highlight** is probably unchecked, or the trail is a single way and not part of a named route. Check **Route highlight**, then tap a line that belongs to a named route (a MultiLine).

**Q:** Where are the OSM links?
**A:** Tap the larger name button for a route, or tap **DETAILS** in the snackbar after tapping a single line. The dialog includes the openstreetmap.org link and any website links stored in the OSM tags.

**Q:** How do I see the whole route (for example the PCT or a loop) and then get back?
**A:** Long-press the larger name button, choose **Show whole feature**, then long-press it again and choose **Zoom back to previous view**.

### 4.4 Guided tours ("Try Route highlight")

The guided tours set up a real example: they pick a Profiles file and Mapsforge map, turn on Breadcrumbs, Lines, and Route highlight, center the map, and highlight a named route. Each tour first reuses compatible files already on the device. Then, if you confirm, it downloads only the files that are missing, with no 123 code, in every edition.

#### Where to start a tour
- Main page More options → **About . . .** → **Try Route highlight**.
- Main page More options → **Recent Updates...** → **Try Route highlight**.
- **Buy Maps** screen → the **Before you buy raster maps** note → **Try Route highlight**.
- **Lite only:** the once-a-day "Thanks for opening the app!" dialog shown after the full-page ad → **Try Route highlight**.

#### Tour menus by brand
**PDXWalk** — the **Try Route highlight** dialog ("Choose a guided map demonstration. …") offers:
- **Portland Loop**: Portland 40 Mile Loop (a bicycle route).
- **Mt. Hood Tours** → **Timberline Trail** or **PCT Search**.
- **Cancel**.

**OsmTrails** — the dialog asks you to choose a region:
- **US Tours** → **Portland Loop** or **Mt. Hood Tours** (→ **Timberline Trail** / **PCT Search**).
- **UK Tours** → **Cumbria Tours** or **Ledbury Loop**.
  - **Cumbria Tours** → **Aira Force Loop** (the Aira Force and Gowbarrow Park circular trail beside Ullswater) or **Scafell Pike** (England's highest mountain, climbed from Wasdale via Hollow Stones).
  - **Ledbury Loop**: the National Byway Ledbury Loop cycle route near the Malvern Hills.

The UK tours are not offered in PDXWalk.

#### What each tour needs (and downloads if missing)

| Tour | Brands | Profiles file | Mapsforge map | Hillshade (Terrain-RGB) |
|---|---|---|---|---|
| Portland 40 Mile Loop | Both | PDXMetroProfiles202610 (about 51 MB) | portland-202610.map (about 27 MB) | none |
| Mt. Hood Timberline Trail | Both | MtHoodProfiles202610 (about 10 MB) | mt-hood-202610.map (about 16 MB) | none |
| PCT Search (PCT - Oregon Section G) | Both | same as Mt. Hood | same as Mt. Hood | none |
| Aira Force Loop | OsmTrails | UK-CumbriaProfiles202610 (about 33 MB) | uk-cumbria-202610.map (about 29 MB) | none |
| Scafell Pike | OsmTrails | UK-CumbriaProfiles202610 (about 33 MB) | uk-cumbria-202610.map (about 29 MB) | uk-cumbria-terrain-rgb.mbtiles (about 21 MB) |
| Ledbury Loop | OsmTrails | UK-LedburyMalvernProfiles202610 (about 4 MB) | uk-ledbury-malvern-202610.map (about 2 MB) | ledbury-malvern-terrain-rgb.mbtiles (about 0.8 MB) |

- Any Mapsforge map already on the device that covers the tour's start point counts as the map, including an imported OpenAndroMaps map. In that case the tour downloads only the Profiles file (and hillshade, if the tour uses it).
- The Profiles check is separate: the Profiles file must contain the tour's route, so it is usually the listed file.

#### Run a tour
1. Pick a tour. A dialog says "Checking the offline maps and Profiles files on this device…".
2. If everything is present, the tour starts right away. Otherwise a **Download missing tour files?** dialog lists each missing file with its size and the total download size, and says: "This explicit tutorial confirmation replaces the usual 123 code. The code remains required on the ordinary download screens."
   - **Download and start**: starts the downloads. A **Preparing <tour>** dialog shows Profiles, Mapsforge map, and Hillshade status, and starts the map automatically when everything is ready. Android also shows download notifications. **Continue in background** closes this dialog; reopen the tour later and finished files are reused. After 30 minutes the dialog says the download is taking longer than expected; you can close it and come back later.
   - **Not now**: cancels.
   - **Own map instead** (Cumbria tours only, when the map is missing; see below).
3. When the tour starts, the map opens zoomed in on the route with the route already highlighted. A dialog titled "<route name> is highlighted" explains how to use the larger name button. Tap **Try it**.
4. Follow the dialog: long-press the larger name button → **Show whole feature**, then long-press again → **Zoom back to previous view**. Try tapping other named routes.

On the hillshade tours (Scafell Pike, Ledbury Loop), the hillshade layer is also turned on. Use the **Show hillshade** checkbox to compare the map with and without relief shading.

#### PCT Search tour (advanced Path Name Search)
1. **Try Route highlight** → **Mt. Hood Tours** (OsmTrails: **US Tours** first) → **PCT Search**.
2. The tour opens Path Name Search with **MultiLines** selected, the slider at **All Results**, and **pct** already searched. A dialog titled **Advanced PCT multiline tour** explains that these results come from the entire Mt. Hood Profiles file, whatever the current map center. Tap **Try it**.
3. Long-press **PCT - Oregon Section G**, then choose **Yes** to set the map center.
4. Tap **GOTO MAP**. (The dialog says this button is "at the bottom of this page", but it is the green button at the top right of the screen.)
5. On the map, a **Find PCT Oregon Section G** dialog appears. Breadcrumbs, Lines, and Route highlight are on. Zoom in if needed, then tap a PCT line. The whole Oregon Section G route is emphasized. Long-press its larger name button to show the whole feature or to return. Tap **Explore the map**.

#### "Own map instead" (Cumbria tours, OsmTrails)
If the Mapsforge map is missing on **Aira Force Loop** or **Scafell Pike**, the download dialog also offers **Own map instead**, which opens **Use your own Mapsforge map**:
1. In your web browser, open openandromaps.org, choose Downloads, then Europe, then UK-LakeDistrict. Download the map file, not the theme.
2. The browser saves a `.zip` in your Download folder. Extract it with your Files app so the `.map` file is visible.
3. In the app, tap **Import File** on the main page and pick the extracted `.map`. It is copied into the Mapsforge maps list.
4. Reopen the tour. It detects the imported map and offers only the missing Profiles (and, for Scafell Pike, hillshade) files.

**Open OpenAndroMaps** opens the site in your browser. The app never downloads from OpenAndroMaps itself, and OpenAndroMaps' own terms apply. **Back** returns to the previous dialog.

#### Gotchas
- A tour needs location permission. Without it the app shows "After permissions are granted, reopen the Route highlight tour".
- Starting a tour changes your settings. It selects the tour's Profiles file and Mapsforge map, switches the base map to the Mapsforge (vector) map, turns on Breadcrumbs, Lines, and Route highlight, and moves the map to the tour area. Switch back afterwards if you want your previous setup.
- Stay online until downloads finish. The app is built to use the downloaded files offline afterwards.
- Tours do not unlock other regions on the ordinary download screens (1.11).

**Q:** I'm on PDXWalk. Where are the UK / Cumbria tours?
**A:** They are only in OsmTrails. PDXWalk offers **Portland Loop** and **Mt. Hood Tours** directly.

**Q:** Will the tour download everything again?
**A:** No. It reuses compatible Profiles files, Mapsforge maps, and hillshade files already on the device, and downloads only what is missing.

**Q:** The tour says it is still downloading after a long time.
**A:** Downloads continue in the background, and progress appears in Android notifications. Tap **Continue in background** and reopen the same tour later. Files that finished are reused, and only what is still missing is offered.

### 4.5 Targets, the HERE marker, and walking routes (experimental)

#### The target
A **target** is a saved point that the app measures and points toward. When **Show Target Arrow** is on (map More options), the map draws a cyan line from your location to the target, with a cyan **TARGET** marker that shows the distance in miles (and meters when you are close). A second label shows "Target is ..." or "<part> of <total>" (distance as the crow flies). **Show Target Arrow** is off by default; setting a target from the map turns it on.

Ways to set a target:
- **HERE marker:** when the map center is away from your location (more than 5 m) and **Show Here There Arrow** is on (the default), a green "Here to There" line runs from your location to a green distance box at the map center (miles, plus meters under 2,000 m). This box is the **HERE marker**. **Tap** it to open **Target GPS Coordinates**, which shows the latitude and longitude (you can edit them) and asks "Set this point as new target?" Tap **Yes, Set Here as new Target** or **Cancel**.
- **Compass gunsight:** tap the gunsight → **Set Target** sets the map center as the target (4.6).
- **Path Name Search:** check **Also set as target** when centering on a result (4.1).
- **Drag the TARGET marker** to a new spot. The same coordinates dialog asks you to confirm.

Turning off **Show Target Arrow** hides the target display. If the map was rotating toward the target, it also returns to North Up.

#### Walking route to the target (experimental)
1. Make sure you have a GPS location, a target, and **Show Target Arrow** on.
2. **Tap the TARGET marker**, or the distance label on the target line. The app computes a route from your current location to the target over the Profiles trail and road data and draws it.
3. **Tap the TARGET marker again** to hide the route ("Dijkstra route hidden").

#### Walking route to the HERE marker (experimental)
1. Pan the map so the point you want is at the center. The HERE marker appears there.
2. **Long-press the HERE marker**. The app routes from your current location to that point.
3. A **yellow pin** beside the HERE marker shows the route length ("route X.XX mi") and "tap to hide".
4. **Tap the yellow pin** to hide the route ("Route to HERE hidden"). A new HERE route replaces any route already shown.

#### What you see on a route
- The route is drawn as an outlined pastel line. Dashed orange pieces mark short gaps where no mapped way connected and the app bridged the gap.
- **First route:** a bottom panel titled **Experimental route** shows a short technical summary and this caution: "Experimental: this route may use closed, private, or missing paths. Check it against the map and what you see before following it." The panel stays until you tap **Dismiss**. If you tick **I know it is experimental. Auto-close and show only the route data from now on.**, later routes show only a brief snackbar.
- **Tap the route line** for a balloon with the route length ("Route to target: X.XX mi"), the straight-line distance, and the caution. A snackbar also appears:
  - "Route to target hides in 20 s" with **Keep**, while Profiles lines are on;
  - "Route to target hides once Profiles lines are on", while they are off;
  - "Route to target kept" with **Hide**, after you tapped **Keep**.
- **Auto-hide:** while Profiles lines are shown, the route hides itself 20 seconds after it is drawn or last tapped, unless you tapped **Keep**. With Profiles lines off, the route stays.
- **Freeways:** freeway portions (motorways and divided highways with their ramps) are left out. The app shows the part off the freeway and leaves freeway driving to a navigation app.
- **Gap filling:** the route also uses paths from the selected Mapsforge map to fill gaps in the Profiles data.
- Routing is aimed at short distances ("the last 2 miles" to a target).

#### When a route can't be made (messages)

| Message | Meaning / what to do |
|---|---|
| "Too many paths and roads between here and there for a quick route. Try a closer point." | The app gave up early: the corridor between you and the point holds too much map data (typical of dense city areas). Pick a closer point. |
| "Dijkstra route: target is beyond the configured distance (…)" | The point is too far in a straight line (about 5 km). The app checks this before loading any data. Pick a closer point. |
| "Dijkstra route: current location unknown (…)" | No GPS location yet. Wait for a fix. |
| "Dijkstra route: no target set (…)" | No target is saved. |
| "Dijkstra route: route graph unavailable (…)" | No usable trail data was loaded, for example when no Profiles file covers the area. |
| "Dijkstra route: no nearby line or multiline (…)" | Your location or the point is not close to any mapped way. Turn on Lines and pick a spot on a trail. |
| "Dijkstra route: no route found (…)" | The ways near you and the point don't connect within limits, or the whole route would be on a freeway. |
| "Dijkstra route already computing…" | A route is still being worked out. Wait and try again. |
| "Dijkstra route failed" | An unexpected error occurred. Try again. |
| **Switch map for this route?** dialog | The selected Mapsforge map does not cover both ends, but another installed map does. Choose **Use <map>**, or **Keep <current map>** / **Route anyway**. Either choice starts the route. |

The text in parentheses at the end of these messages is a technical note and can be ignored.

**Q:** Is this turn-by-turn navigation?
**A:** No. It is an experimental line drawn over the map, with no voice or turn instructions. Check it against the map and the ground before following it. For directions to a point, use the amber arrow button (3.10) to open another map app such as Google Maps or OsmAnd.

**Q:** Why did my route disappear?
**A:** While Profiles lines are on, routes auto-hide after 20 seconds. Tap the route and choose **Keep** to hold it.

**Q:** Why doesn't tapping the target do anything?
**A:** The target marker only exists when **Show Target Arrow** is on and a target is set. Also check the snackbar: a route may already be computing, or the target may be too far.

### 4.6 Compass gunsight

The gunsight is an oval compass object on the map, beside the satellite button, that helps you face toward your target. It contains a compass needle with orienting lines, and flashing balls on the needle that show when you are aligned. It is accurate to about ±15 degrees, which is good enough for hiking. It is on by default.

Set up:
1. Center the map on the place you want to go (a peak, a junction, a point of interest).
2. **Single-tap the gunsight**. A **Compass Gunsight** dialog explains the display:
   - green lines point North;
   - the red needle shows which way the device is pointing;
   - rotate until the red dots align;
   - a large colorful dot means perfect alignment.
3. Tap **Set Target** to make the map center your target ("Target set successfully"). If a target already exists, **Center Target** moves the map to it ("Centered on target"). **Got it** closes the dialog.

Use:
1. Hold the phone flat, screen up.
2. Turn your body until the alignment indicators flash. The phone's bottom-to-top edge then points toward the target.

Gestures: **tap** shows help; **long-press** then drag moves the gunsight; **double-tap** resets it to its default position.

Map rotation (North Up, Manual Rotate, Target Direction) is in 3.4. The main page's compass button is in 2.8.

Gotchas:
- Compass and target headings are smoothed so they jitter less, and they account for portrait, landscape, and upside-down screen orientation.
- Always carry a real magnetic compass and check the phone against it. Accuracy can be poor indoors or in a car, and right after the phone has been off for a while.
- To calibrate, move the phone in a figure-8, or rotate it on all axes with sweeping movements.
- If the compass keeps flipping between directions, the phone's two compass sensors disagree. This is common indoors.

---

## 5. GPS recording: Rapid Tracking, events, Chop Chop, heart rate, alerts, export

Recording, events, and export are the same in both brands and all editions; only the app name in notifications differs. A line break inside a button label is shown here as a space.

Terms used in this section:
- **Event**: one Rapid Tracking recording session. It has a start, an end time chosen in advance, optional pauses, and an optional early stop. Events are listed on the **Events** screen (5.14).
- **Map session** (map-only GPS): the short GPS run the app starts every time you open the MAP. It draws your blue GPS line but is **not** an event (5.7).
- **Tracks database**: where every saved GPS point goes, whether from an event or a map session. **Extract Track File** and the map's **Show Tracks TODAY / YESTERDAY / WEEK** read from it.
- **Mark**: a "something mattered here" timestamp inside an event, made by Chop Chop or by double-tapping the map's center button. A mark is **not** a lap end.

### 5.1 Rapid Tracking: what it is and how to start it

Rapid Tracking is the app's active GPS recorder. It runs as an Android foreground service with an ongoing notification, so it keeps recording when the screen is off or you switch apps. It stops on its own when the event's time runs out.

#### Open the Rapid Tracking page
1. On the main page, tap **Start Stop Rapid Track**. (If location permission is missing, the app asks for it first.)
2. The **Rapid Tracking** page opens. It has:
   - three columns of choices: **Duration:**, **Frequency:**, and **Distance:**;
   - **Capture Cellular Bar Strength?** and an **Advanced** button;
   - **Resume Active Tracking After Reboot**;
   - the **Start**, **Status Update**, and **Stop** buttons;
   - a status text area and a **GOTO MAP** button;
   - More options menu: **Trim Old GPS Data** (5.16).

#### Start an event from the Rapid Tracking page
1. Pick a **Duration:**, a **Frequency:**, and a **Distance:** (5.2).
2. Optionally tick **Capture Cellular Bar Strength?**, or open **Advanced** for more options (5.3).
3. Tap **Start**.
4. The status shows **status: starting location tracking...** (up to about 10 seconds), then **status: running** with **Time left to run:** (h:min:sec) and **expires at** HH:mm.
5. While the event has time left, **Start** is disabled and **Stop** is enabled.

#### Start, pause, resume, and stop an event from the MAP
The MAP has a green Rapid Tracking toggle below the satellite button (top left). It shows and hides the event controls, which use the settings you last used on the Rapid Tracking page.
1. Tap the toggle to show the controls.
2. Tap the start control. The event starts with your last-used duration, frequency, and distance.
3. While recording, only the pause control is shown. Tap it to pause.
4. While paused, the resume and stop controls are shown. On the map, **Stop is only reachable after Pause**.
5. Long-press the toggle for **Rapid Tracking Toggle Help/Explanation** ("START (it is just this one step)", "PAUSE (it can be Resumed)", "RESUME", "STOP (you only see this option if you first Paused)").

Differences from the Rapid Tracking page:
- An event started from the map always begins with batching off. **Batch GPS Lower Power** is ignored.
- An event started from the map does not save the **Capture Cellular Bar Strength?** choice; the value saved at your last **Start** on the Rapid Tracking page stays in effect.

#### Starting may ask about Profiles coverage
If **Intersection Alerts**, **Enable: Live GPS Snapping**, or **Enable: Periodic Refinement** is ticked, Start first checks that a downloaded Profiles file covers your location. If none does, you see a **Profiles coverage** dialog with **Use selected**, **Profiles page**, and **Cancel**. If another downloaded file covers you, a **Switch Profiles file** dialog appears instead. If the app has no location to check against, it shows "Map location is not available for Profiles coverage" and does not start; open the MAP once so it has a location, then try again.

### 5.2 Duration, Frequency, Distance: the basic choices

| Column | Choices | Default on a fresh install |
|---|---|---|
| **Duration:** | **2 Min**, **5 Min**, **20 Min**, **2 Hours**, **9 Hours**, **16 Hours** | 2 Hours |
| **Frequency:** | **1 Sec**, **4 Sec**, **15 Sec**, **30 Sec**, **1 Min**, **2 Min** | 15 Sec |
| **Distance:** | **0/any/all**, **1 Meters**, **2 Meters**, **5 Meters**, **20 Meters**, **100 Meters** | 2 Meters |

- **Duration** is how long the event runs before it stops by itself. Every event has a time limit. To run longer, extend it with **Status Update** (5.5).
- **Frequency** is how often the app asks Android for a GPS fix.
- **Distance** is the minimum movement before a new fix is delivered. **0/any/all** delivers every fix. With 20 or 100 m, slow walking records few points.
- Your choices are saved when you press **Start**. The next event (including one started from the map) reuses them.
- Your last frequency and distance also apply to the 5-minute map session (5.7).

**Q:** What does the app recommend for battery life?
**A:** The app's own tip: "Most battery drain comes from requesting GPS more frequently than every 15 seconds, and especially from keeping the screen on while looking at the map." Keep the screen off as much as possible, or carry a power bank on long hikes (5.18).

### 5.3 The Rapid Tracking page: every option

Long-press almost any checkbox on this page to see the app's own explanation (texts in 6.A.3).

#### Always visible

**Capture Cellular Bar Strength?** (default off; disabled on devices without a phone radio)
- Records cell signal strength along your route, at most once a minute. For each visible cell it stores signal strength (dBm), bars, radio type, and cell ID at your current location.
- Long-press text: "Records cell phone signal strength data for map visualization. Prevents duplicate points by not saving when nearby data already exists."
- To view it, use the MAP's More options: **Show Recent Cell Signal**. It shows the last 12 hours, at map zoom 12 or closer.
- **Reset Tracks DB** keeps cell data unless you also tick **Reset Cell Data along with other GPS track data.**

**Resume Active Tracking After Reboot** (default off). See 5.6.

**Advanced** shows the advanced options, and the button then reads **Basic**. Tap **Basic** to hide them again.

#### Advanced section

| Option | Default | What it does |
|---|---|---|
| **Enable Step Counter** | off; greyed out if the phone has no step sensor | Asks for the Physical activity permission. See 5.10. |
| **Use Persistent Step Listener** (indented under the step counter) | on | Saved, but has no effect on recording in version 20261015. Removed in the next update. |
| **Chop Chop For GPS Burst** | off | Turns on the Chop Chop gesture (5.9). |
| **Batch GPS Lower Power** | off | Lets Android hold fixes and deliver them in batches, to save power (see below). |
| **Intersection Alerts** | off | Alerts when you come within 50 m of a known trail or path intersection (see below). |
| **Path System Alerts (driving)** | off | Alerts for walkable trail systems near your drive (5.12). |
| **Minimum combined trail (km):** | 4 | The smallest trail system that alerts. The lowest value used is 1. |
| **Heart Rate Monitor** | off; hidden if the phone has no Bluetooth LE | Pairs and records a Bluetooth heart rate monitor (5.11). |
| **Custom Heart Rate Filter** (text box) | empty | Adds a name to look for when scanning for monitors (5.11). |
| **Enable: Live GPS Snapping** | off | Matches each fix to the OpenStreetMap paths in your Profiles file in the background. No snapped line is drawn. Requires Profiles coverage at Start. |
| **Enable: Periodic Refinement** | off | Every 5 minutes, re-matches the last 10 minutes of points in the background. Nothing visible on the map. Requires Profiles coverage at Start. |
| **Enforce Forward Progress (Anti-Spider Web)** | on | For the app's path matching. Long-press text: "When enabled, the track will NOT show retreats — preventing 'spider web' track patterns from GPS jitter. DISABLE for interval training (e.g., running stairs) where you intentionally go back and forth on the same path." Your recorded raw GPS points are not changed. |
| **Off-Route Detection Settings:**: **Distance Threshold (meters):** and **Consecutive Points:** | 25.0 and 5 | Planned for Live GPS Snapping (a buzz and a chime, no text). Off-route alerts are not finished in this version, so these settings have no effect yet. |

**Batch GPS Lower Power, in detail**
- The fix rate and accuracy stay the same. Fixes just arrive in groups, so the phone wakes less often.
- With batching off, Android may hold fixes for up to about 1.8 × the frequency. With it on, it may hold them for 30 seconds or 6 × the frequency, whichever is longer. At a frequency of 1 minute or more, the limit is 5 minutes.
- Batching is suspended while the MAP is open (if at least 30 seconds of the event remain), so the blue line stays live. It resumes when you leave the map, if more than 60 seconds remain.

**Intersection Alerts, in detail**
- Long-press text: "Notifies you when you're approaching a trail or path intersection. An alert triggers when your GPS is within 50 meters of a known intersection." Intersections come from the selected Profiles file; you can see them on the map with the **Points** button (crossings, 3.6).
- Each alert vibrates and shows the notification **Approaching Intersection** ("Approaching A near B"), which closes itself after 1 minute.
- Each alert also starts a short high-rate GPS burst.
- The setting is read when tracking starts. Change it before **Start**.

### 5.4 The event lifecycle

An event has a START, optional PAUSE/RESUME pairs, optional UPDATEs (end time or settings changed), and a STOP. These records are the event's official timestamps.

#### Pause and Resume
- Pause and Resume are on the MAP's event controls. The Rapid Tracking page has no Pause button.
- **GPS keeps recording during a pause.** Every fix between start and end belongs to the event. Paused time is reported (the Events screen shows **paused** and the time), not subtracted.
- **The countdown keeps running while paused.** A pause does not move the end time.
- Marks (Chop Chop, center double-tap) are **not** recorded while paused.
- The ongoing notification looks the same whether paused or not.

#### Stop
You can stop an event in any of these ways:
- the **Stop** button on the Rapid Tracking page (it shows **Stopping...**, then **Stopped ✓**, and the status reads "Location tracking stopped successfully");
- the map's stop control (after Pause);
- the notification's **Stop Rapid Tracks** button (stops at once, with no confirmation);
- letting the time run out.

If the 5-minute map session still had time left when you stopped, the app restarts map-only GPS. The page's Stop button then reads **Stop Map GPS**. Pressing it shows "Map GPS stopped. Opening the map starts it again for 5 minutes."

#### When the time runs out
- The service checks about every 30 seconds, so recording can end up to about 30 seconds after the scheduled end.
- The event is closed at its scheduled end time.
- There is no end-of-event alert. The ongoing notification simply disappears.
- If the app was killed or the phone was off at the end time, the event is closed at its scheduled end the next time the app starts.

#### Starting a new event while one is open
On the Rapid Tracking page, Start is disabled while an event has time left. If a new event does start while one is still open, the old event is closed with the reason **superseded**.

### 5.5 Status Update and extending the end time

#### With an event running
1. Optionally change **Frequency:**, **Distance:**, or **Batch GPS Lower Power** on the page first.
2. Tap **Status Update**.
3. A dialog titled **Update tracking** shows:
   - "Started HH:mm, X ago." and "Ends HH:mm, in X.";
   - any frequency, distance, or batch changes (for example "Frequency: 15 s to 4 s"), or "Frequency and distance are unchanged.";
   - a choice of **Keep the end at HH:mm** or **Add 2 min**, **Add 5 min**, **Add 20 min**, **Add 2 hours**, **Add 9 hours**, **Add 16 hours** (each with its new end time);
   - the hint "To end sooner, use Stop."
4. Tap **Update**. The snackbar confirms "Tracking ends HH:mm".
   - If nothing changed, you see "Nothing changed".
   - If the event ended meanwhile, you see "The event has already ended".

Gotchas:
- The end time can only be kept or extended. To end early, use **Stop**.
- **Add** choices that would make the event longer than 8 days from its start are not offered (5.16).
- **Duration:** on the page only applies to a new Start. To lengthen a running event, use **Status Update**.

#### With no event running
**Status Update** refreshes the status text and applies the selected frequency and distance to the map session, if one is running.

#### Reading the status text

| Status text | Meaning |
|---|---|
| **status: running** + **Time left to run:** … **expires at** HH:mm | An event is recording. |
| **status NOT running** | The tracking service is off. |
| **( Map-only time left to run: … )** | Time left in the map session (5.7). |
| **no time limit** | Shown in place of a time when there is no limit. |

### 5.6 Resume Active Tracking After Reboot

**What it does:** if the phone restarts while an event still has time left, tracking starts again without opening the app. It starts after the phone has been **unlocked** for the first time.

**Set it up:**
1. On the Rapid Tracking page, tick **Resume Active Tracking After Reboot**.
2. If background location is not yet allowed, the app explains: "… uses your location in the background, even when the app is closed or not in use, to restart an active tracking event after your phone restarts. Locations are recorded to the event's track on this phone. On the next screen, please select 'Allow all the time'."
3. Tap **Continue** and choose **Allow all the time** in Android's screen. (**Not Now** skips this.)
4. If the permission is still missing, the checkbox reads **Resume Active Tracking After Reboot (needs 'Allow all the time')**.

**Without "Allow all the time"** (or with the box unticked), on Android 11 and later the app cannot restart tracking by itself after a reboot. Instead, a notification "<app name> Needs to Restart Tracking Service." / "Bring app to front to restart location service" appears (with vibration). Tap it to open the app; opening the main page while the phone is unlocked restarts tracking if the event still has time left.

**If the event's time ran out while the phone was off,** nothing restarts. The event is closed at its scheduled end.

**Q:** I rebooted and the tracking notification did not come back. Why?
**A:** Check three things: the box is ticked, location is set to **Allow all the time**, and you have unlocked the phone since the reboot. Also confirm the event still had time left. If none of that helps, open the app; it restarts tracking when time is left.

### 5.7 Tracking vs. a plain map session

Every time the MAP opens or comes back to the front, the app starts GPS for **5 minutes** so you can see where you are. This map session:
- **draws the blue GPS line** and **saves its GPS points** to the tracks database, so they show up in **Extract Track File** and **Show Tracks TODAY**;
- is **not an event**. It does not appear on the **Events** screen, records no marks, and does not run Chop Chop;
- uses your last-saved **Frequency:** and **Distance:**;
- shows the same ongoing notification as an event;
- restarts its 5-minute window each time the MAP comes back to the front.

If an event is already running, opening the MAP doesn't start anything new; the event keeps recording. On the Rapid Tracking page a running map session shows "( Map-only time left to run: … )".

Some features are tied to events, by design:
- Chop Chop and marks need an event.
- The Path System Alerts strip on the map needs an event (3.9).
- Reboot resume needs an event.

To stop a map session, use **Stop Map GPS** on the Rapid Tracking page, or the notification's **Stop Rapid Tracks**. As the app says: "Opening the map starts it again for 5 minutes." To record a lasting track, start Rapid Tracking (an event).

**Q:** I only opened the map, but my walk shows up when I extract today's track. Is that a bug?
**A:** No. Map sessions save GPS points too. They just aren't events, so the walk won't appear on the Events screen.

**Q:** Why can't I find my walk on the Events screen?
**A:** Only Rapid Tracking events (started with **Start**) appear there. A map-only session is not an event.

### 5.8 The ongoing notification and other tracking notifications

#### The tracking notification
- **Title:** "Location running."
- **Text:** "Time Remaining:" followed by the time left (H:MM:SS). It updates when a new GPS fix arrives, not every second.
- **Heart rate:** a line "Heart Rate: N BPM" may appear when a monitor is enabled and sent a reading in the last 30 seconds. If you do not see it, expand the notification.
- **Buttons:**
  - **Launch app** opens the app's main page.
  - **Stop Rapid Tracks** stops tracking at once. It ends the running event, or ends the map session if no event is running.
- Tapping the notification body does nothing; use the buttons.
- Paused state and steps are not shown.
- The notification channel is named after the app (for example "PDXWalk", "PDXWalk-Lite", "OsmTrails").

#### Other notifications from tracking

| Notification | When | Channel |
|---|---|---|
| "<app name> Needs to Restart Tracking Service." / "Bring app to front to restart location service" | An event still has time left, but Android stopped the tracking service and the app is in the background (for example after a reboot without reboot resume). A repeating check runs about once a minute. | app name, high importance |
| **Approaching Intersection** | **Intersection Alerts** is on and you are within 50 m of an intersection. Closes after 1 minute. | **Intersection Alerts** |
| "Path system X.X km <direction>" | **Path System Alerts (driving)** is on (5.12). Closes after 10 minutes. | **Path System Alerts** |

Because intersection alerts and path system alerts have separate channels, you can mute either one in Android settings without muting the other. If notifications are off for the app, both alerts are silently skipped.

Chop Chop shows **no notification**. It gives feedback with vibration and a chime (5.9).

### 5.9 Chop Chop (GPS burst gesture) and marks

**What it is:** a phone gesture that, during a running event, records a **mark** at that moment and asks for a burst of frequent GPS fixes. You don't need to unlock the phone or open the map.

**Turn it on:** Rapid Tracking page → **Advanced** → tick **Chop Chop For GPS Burst** (default off).

**How to chop** (the app's long-press text):
> "Hold the phone still for a moment, tap its corner twice on your other palm (about a quarter second apart), then hold still for half a second. A double vibration confirms it: the running event gets a mark here and a burst of frequent GPS fixes. Chop again during the burst to make it longer. Jogging and walking do not set it off. A double tap on the map's center button also adds a mark."

**Details:**
- **Rules:** be still for at least ¼ second before, give two sharp taps 0.1–0.5 seconds apart, then be still for about half a second after. Any movement after the taps cancels it.
- **Cooldown:** for 3 seconds after a chop, further chops are ignored.
- **Jogging and walking do not trigger it.** Strides are followed by more strides, so the phone is never still afterwards, and jogging jolts are weaker than palm taps.
- **Pocket:** detection pauses while the proximity sensor is covered.
- **Events only:** Chop Chop only runs while an event has time left, never in a map-only session.
- **The burst:**
  - during a burst the app asks for a fix about every 2 seconds;
  - a burst lasts at least 30 seconds;
  - chopping again during a burst extends it, up to 3 minutes in total;
  - each extension gives another double vibration;
  - when the burst ends you get a short buzz and a double chime;
  - if your **Frequency:** is **1 Sec** with **Distance:** **0/any/all**, no burst is needed, but the mark and the vibration still happen.

#### Marks
- Each chop is saved as a **mark** in the event. A chop that starts a burst is labelled "chop"; a chop during a burst is labelled "chop extend".
- **Double-tapping the map's center button** during an event also adds a mark ("center") and takes a few seconds of rapid fixes. It does not start the 30-second burst.
- Marks are **not** recorded while the event is paused or when no event is running.
- **Marks are generic:** a mark means "something mattered here". It is **not** a lap button. Lap detection works with no marks at all (5.14). A mark only helps lap detection if it happens to sit at the lap start or the turnaround.

**Where marks appear:** in the event GPX export, each mark becomes a waypoint named **Mark HH:mm:ss**, with "chop", "chop extend", or "center" as its description. It is placed on the GPS fix nearest in time; a mark with no fix within 60 seconds is left out. Marks are not in the GeoJSON export.

**Q:** I chopped and nothing happened.
**A:** Check each of these:
- An event is running and not paused.
- **Chop Chop For GPS Burst** is ticked.
- The phone was still before and after the taps.
- The proximity sensor isn't covered.
- You waited more than 3 seconds after the last chop.

**Q:** Will a burst give me better accuracy?
**A:** It gives more frequent fixes (about every 2 seconds). Accuracy depends on reception; it works best in open areas with good GPS reception.

### 5.10 Step counter

- **Setup:** Rapid Tracking page → **Advanced** → **Enable Step Counter**. On Android 10 and later this asks for the Physical activity permission. If you refuse, a **Step Counter Permission Required** dialog offers **Open Settings**.
- **How steps are recorded:** whenever tracking runs and the permission is granted (always on phones older than Android 10), the app reads the phone's step sensor and stores a step total and a walking/jogging cadence class with each saved GPS point. Ticking or unticking the box does not itself turn step recording on or off.
- **Where to see steps:**
  - in **Rich Data** GPX exports (5.15), as a total and in waypoint descriptions;
  - in the **steps** column of a laps CSV (5.14).
  - Not on the tracking notification, the Rapid Tracking status, or the plain event GPX.
- **No reset at Start:** the stored count is a running total from the phone's sensor, not a count from zero at the event's start. To get the steps for a stretch, subtract the starting total from the ending total.
- **Use Persistent Step Listener** has no effect in version 20261015 and is removed in the next update.

### 5.11 Heart rate monitor (Bluetooth LE)

**Tested with:** Polar OH1. Other Bluetooth LE heart rate monitors may work.

#### Pair a monitor
1. Turn on your heart rate monitor and put it on (many straps only broadcast when worn).
2. Open the Rapid Tracking page and tap **Advanced**.
3. Tick **Heart Rate Monitor**. If asked, allow Bluetooth (Nearby devices) and location permissions, and turn Bluetooth on.
4. The app scans for about 10 seconds ("Scanning for Heart Rate Monitors" / "Searching for devices... Please wait.").
5. In **Select Heart Rate Monitor**, tap your device. Each device is listed with the last 5 characters of its address. **Rescan** searches again; **Cancel** turns heart rate off.
6. **Wait patiently.** Connection can take 10–15 seconds.
7. When readings arrive, the checkbox title shows the BPM in green: **Heart Rate ✓ (N BPM)**.

The app remembers the monitor. On later events it reconnects to the saved monitor automatically.

#### What the checkbox title tells you (updated every second while the page is open)

| Title | Meaning |
|---|---|
| **Heart Rate ✓ (N BPM)** (green) | The next GPS point will carry this heart rate. |
| **Heart Rate ✗ no data (Ns)** (red) | Readings stopped N seconds ago. Points are being saved without heart rate. |
| **HeartRate - Scanning...**, **HeartRate - Select Device**, **HeartRate - Connecting...**, **HeartRate - Connected**, **HeartRate - Ready** (amber) | Setting up; no data yet. |
| **Heart Rate - Disconnected**, **HeartRate - Error** (red) | No connection. |

#### Reconnects
- If readings stop for 10 seconds (or never start within 30 seconds of connecting), the app reconnects to the saved monitor automatically. It retries about every 5 seconds, with no retry limit, until heart rate is turned off or the event ends.
- It only reconnects to a monitor you have selected before.

#### Change monitor mid-event
1. Long-press **Heart Rate Monitor**.
2. Tap **Change Monitor** in the **Heart Rate Monitoring** dialog. The app shows "Scanning for heart rate monitors...". (If heart rate is off: "Enable Heart Rate first".)
3. Pick the new monitor. The event keeps running; your current monitor keeps recording until you switch. Cancelling leaves the current monitor connected.

#### Custom Heart Rate Filter
The app only lists monitors whose Bluetooth name contains one of these: "Polar H", "Polar OH", "TICKR", "HRM", "Heart Rate", "Pulse", "Garmin HRM", "Wahoo", "Myzone", "RHYTHM", "Coospo" (case doesn't matter). If your monitor isn't listed, type part of its Bluetooth name into **Custom Heart Rate Filter**. Monitors that broadcast no name are never listed.

#### Where heart rate goes
- **During the event:** on the tracking notification ("Heart Rate: N BPM"), when shown.
- **Stored:** with each saved GPS point. A reading older than 30 seconds is not reused; such points are saved without heart rate.
- **Exported in:**
  - **Rich Data** GPX, as the standard Garmin heart-rate tag that most fitness tools read;
  - laps GPX/CSV, as average and peak heart rate per lap.
- **Not in** the plain event GPX or basic Extract files.

Troubleshooting is in 6.B.6.

### 5.12 Path System Alerts (driving)

**What it does:** while you drive or bike, the app notifies you **once per walkable trail system** within **3 km** of your GPS position, with its distance and direction. It only alerts for systems with at least your minimum combined trail length.

**Turn it on:**
1. Make sure you have a downloaded Profiles file that covers where you'll drive. The alerts search the selected Profiles file.
2. Rapid Tracking page → **Advanced** → tick **Path System Alerts (driving)**.
3. Set **Minimum combined trail (km):** (default 4; the lowest value used is 1). The app suggests a small value for a quick dog walk, and 20 km or more to keep the noise down.
4. Start an event (needed for the map strip and for automatic file switching; see below).

**How it behaves** (the app's long-press text):
> "While you drive or bike (faster than about 9 mph), notifies you once for each walkable path system within 3 km of your GPS location, with its distance and direction. Only systems with at least the minimum combined trail below alert: small for a quick dog walk, 20 km or more to keep the noise down. Distance only: a system behind you or across a river still counts. Checked about every 600 m traveled, from the selected Profiles file. Tap a notification to see the system on the map. When you drive out of the selected Profiles file or Mapsforge map, the smallest downloaded file that covers where you are takes over."

**Details:**
- **Speed:** below about 4 m/s (about 9 mph) no check runs, because a walker already sees what's near on the map.
- **Notification:** the title is "Path system X.X km <direction>" and the text "X.X km of trail: <names>" (or "Unnamed paths"). Tapping it opens the map fitted to that trail system. Notifications close after 10 minutes.
- **On a motorway:** the search runs from the next exits ahead, and the title says how far the system is from which exit ("… of <exit name>"), so you get the alert in time to take the exit.
- **Once per system:** each system alerts once per tracking session. A new session lets everything alert again.
- **Notifications off:** if notifications are off for the app, no alert is shown. A system you pass while they're off is not marked as alerted, so it can alert once they're on again.
- **Map sessions:** alert notifications are not limited to events; they can also appear during a 5-minute map session.
- **Strip on the map:** with an event running and **Continuously Center** on, the latest alerts also show in a large strip at the top of the map, with **✕**, **N more…**, and a red **Resume centering** button (3.9). If no Profiles file covers your location, the strip says "No Profiles file covers here: no path system alerts".

#### Automatic switching of Profiles and map files
While **Continuously Center** is on and an event is running, if you drive out of the selected Profiles file or Mapsforge map, the smallest downloaded file that covers your location takes over (never MBTiles). A snackbar says "Switched to Profiles … and map …". If other installed files also cover you, tap **Other files** to pick one. Turning centering off (exploring the map) stops automatic switching.

**Q:** I'm driving with alerts on but get nothing.
**A:** Check each of these:
- A downloaded Profiles file covers the area (the strip warns if not).
- Notifications are allowed for the app and for the **Path System Alerts** channel.
- You're moving faster than about 9 mph.
- Trail systems near you are at least your **Minimum combined trail (km):**.
- You've traveled about 600 m since the last check.

### 5.13 Recording quality: sensor-assisted filtering and where points are saved

The app combines GPS with the phone's motion and step sensors to judge each fix:
- **Discarded fixes:** a fix with reported accuracy worse than 24 m is discarded, as is a duplicate fix with the same timestamp.
- **Flagged, not deleted:** every other fix is saved, but the app labels how it was moving and flags doubtful fixes:
  - movement profiles: still, lingering, walking, running, driving;
  - flag reasons: inaccurate (over 50 m), too soon, a jump too big for the movement state, speed too high, inconsistent bearing or speed;
  - a jump-and-return check marks spikes.
- **What flags change:** doubtful fixes are kept out of the app's live path matching. Your saved track and blue line still use the raw points.
- **Where you see it:** in **Rich Data** GPX exports, as the movement profile and class and a quality tag on each point (5.15).
- **Best guess only:** the app's own note is that this is "always a best guess - GPS and sensors have limitations", especially in poor GPS conditions.
- **No adaptive rate:** this version does not change the GPS rate on its own when you stop moving. Older update notes described "Adaptive Tracking", but it is not active in this version. Battery use is controlled by your **Frequency:**, **Distance:**, **Batch GPS Lower Power**, and how long the screen stays on.

#### Where points are saved
- **Your own areas:** main menu → **Set Track Log Boundary** (2.14). Points outside the "only within" box, or inside the "none within" box, are not saved.
- **Built-in limit:** independently of your settings, the app saves points only inside its supported regions. Fixes elsewhere (for example, most of Africa, Asia, and Australia) are not saved to the tracks database or to events.
  - **The Americas:** Alaska (including the western Aleutians) and Hawaii, Canada including the Arctic islands, Greenland, and south to Tierra del Fuego.
  - **Europe:** from the Azores, Canaries, and Iceland east to the Urals, and north to Svalbard.
  - **New Zealand and Fiji**, including the Chatham Islands.
  - The regions are rough boxes, so some nearby areas are also saved, such as North Africa and the Middle East north of 27°N and west of 60°E.
  - Version 20261015 uses one smaller box instead: longitude 179°W to 20°E and latitude 60°S to 75°N, so it saves nothing east of 20°E (eastern Europe included). The next update widens it to the regions above.

### 5.14 The Events screen (last 8 days)

**Open it:** main page More options → **Show Events (last 8 days)**.

**At the top:**
- A day filter (**All days** or a single day).
- A length filter: **Any length**, **5 min or more**, **30 min or more**, **1 hour or more**.
- A status line: "N of M events in the last 8 days. Long-press one to see its shape." or "No events in the last 8 days".

**Each row shows:**
- **Line 1:** day, start to end time, and length.
- **Line 2:** distance and point count, plus any of these that apply:
  - **paused** and the time;
  - **running**, or how the event stopped. Stop reasons appear as short words: **timer** (time ran out), **notification** (stopped from the notification), **superseded** (a new event started). A Stop-button stop shows no reason.
  - **vehicle X.XX km**;
  - **partial, early points purged** (part of the event lies outside the 8-day window).
- **Line 3** (optional): **Trimmed to …**, or **Can be trimmed: long-press to compare**.

**Buttons** (select one or more rows first; otherwise you see "Select one or more events"):
- **Show on Map** saves the event(s) as a GPX file in My Tracks and opens the map on it ("Preparing N event(s)"). It is drawn as one of your own track files, so the **Tracks** button hides and shows it (3.8).
- **Export...** always writes `<name>.gpx` to My Tracks, one track per event. You can also tick:
  - **GeoJSON output**;
  - **Nearby OSM Lines** (one `…PlusOSM_V2.gpx` per event; `…PlusOSM_V3.gpx` in the next update and later);
  - **Rich Data (EXPERIMENTAL)** (one `…rich.gpx` per event).

  These start from your Track File Settings choices, and your ticks are saved back to them. Success: "Exported … to My Tracks".
- An event with fewer than 2 points shows "Too few points to draw this event".

**File names:**
- one event: `event_yyyyMMdd_HHmmss_` (plus `_trimmed` and your file-name TAG if set);
- several events: `events<N>_…`.

**What's in the event GPX:** one track per event, named "Event yyyy-MM-dd HH:mm" with "(trimmed)" if applicable. Its description gives start/end, how it stopped, and paused minutes. Marks are included as **Mark HH:mm:ss** waypoints. Heart rate and steps are not included; use **Rich Data** for those.

#### Long-press an event: shape, trimming, laps
1. Long-press a row. A dialog shows the event's shape: **Whole event, as recorded** and **Trimmed to the activity (grey is cut off)**, with distances and any **In a vehicle** distance.
2. **Trimming** removes driving and still time:
   - **Driving:** three or more fast stretches of at least 12 m/s, covering at least 1 km, count as driving.
   - **Still time:** staying within 50 m for 5 minutes or more at either end is trimmed.
   - The activity is the longest on-foot stretch.
   - Choose **Use trimmed** or **Use whole**; this decides what **Show on Map** and **Export...** use ("Show and Export use this event trimmed/whole"). If there is nothing to trim, the dialog says "Nothing to trim: no drive, and no still time at either end."
3. **Laps** are found automatically for **out-and-back repeats** (hill or stair repeats, out to a point and back):
   - **Trips:** a trip starts when you go more than 50 m from the start point and ends when you return within 25 m.
   - **Laps:** trips that reach the common turnaround (within 30 m) count as laps; others are "other trips". These distances suit laps of about 200 m.
   - **Results:** "N lap(s) to a turnaround X m out", plus a table with time, out/back split, distance, climb, and average/peak heart rate. "Possibly" is added when the result is uncertain.
   - **No laps found:** "No easy laps found. Re-check with hints, or export the event's GPX for a desktop tool such as QGIS."
   - **Hints:** fill in **lap m**, **lap min**, or **laps** and tap **Re-check**.
   - **Marks** only help if one sits at the start point or the turnaround; other marks are ignored. Laps are found with zero marks.
4. **Export laps** (shown only when laps were found):
   - writes `<event name>laps.gpx` and `.csv` to My Tracks;
   - the snackbar has a **Show** action;
   - the GPX has one track per lap ("Lap i of N"), heart rate per point, and **Start** / **Turnaround** waypoints;
   - the CSV columns are: lap, start, duration_s, out_s, back_s, distance_m, pace_min_per_km, gain_m, net_climb_m, avg_hr, peak_hr, hr_drop_60s, steps.
5. In **Show Track File List**, a lap file's summary line says **Laps**, and its title is the first lap's name ("Lap 1 of N"). The CSV is also listed, as an additional file.

### 5.15 GPX export formats

There are two ways to make track files: **Extract Track File** on the main page writes everything recorded in a time period (2.5), and **Export...** on the Events screen writes chosen events (5.14). Both write to the My Tracks folder and appear in **Show Track File List** (2.11).

#### Set Track File Settings (main menu; screen "Track File Settings")

| Option | Default | Adds |
|---|---|---|
| **Select Duration:** **ALL**, **TODAY**, **YESTERDAY**, **LAST WEEK**, **LAST HOUR**, **LAST 15Min** | ALL | Period used by Extract (same setting as the Extract dialog). |
| **Set Optional File Name TAG:** | empty | Up to 16 letters/digits, no spaces, added to file names (e.g. ForestPark). |
| **Include: OSM Snapped Track Export** | off | A `…_SNAPPED.gpx` with your track matched to OSM paths. |
| **Include: Nearby OSM Lines** | off | A `…_PlusOSM_V2.gpx` (`…_PlusOSM_V3.gpx` in the next update and later): your track plus nearby OSM trails as routes. |
| **Include: Rich Data (EXPERIMENTAL)** | off | A `…rich.gpx` with heart rate, steps, movement, and quality per point. |
| **Include: GeoJSON output** | off | A `.geojson` copy. |
| **Storage Location:** **Internal** / **External** | Internal | Where files are saved (External is disabled if the phone has none). |

- The screen shows the naming scheme: **Track File Naming Scheme:** `tracks_[duration]_[date][_tag]_gpx`.
- Both OSM options are greyed out until you have downloaded a Profiles file.
- Tap **Save Changes**. On Back, the four checkboxes are saved immediately; duration, TAG, and storage only save via **Save Changes**, or **Yes** in the "You have made some changes. Would you like to save before exiting?" prompt.

#### Rich GPX extensions
The **Rich Data** GPX is still a standard GPX 1.1 file, so other apps can display it. Per point it adds:
- elevation (whole meters) and time;
- heart rate (Garmin `gpxtpx:hr`, readable by most fitness tools);
- the app's own tags for step total, movement profile and class, and point quality.

Waypoints are added where the movement profile changes or the step count changes, and on points that carry heart rate (named like "Profile: X, Class: Y, HR: N"). Speed and accuracy are not included.

#### OSM routes in export (Nearby OSM Lines, Plus OSM)
- **What's in the file:** your recorded path is a `<trk>` (track). Nearby OSM trails from your Profiles file are written as separate `<rte>` (route) elements, keeping **trail names** and **OSM IDs**.
- **Next update and later:** the trails come from every Profiles file in the selected Profiles file's folder, so a track that runs from one Profiles area into another gets the trails of both; version 20261015 uses only the selected file. A trail shape is written once, even when an OSM way and a route relation share it.
- **Why routes:** this suits offline devices such as COROS or Garmin watches. Trails show separately from your track, with no false connecting lines between separate trail pieces.
- **ADD OSM DATA** on the Track File List or Imported Tracks adds the same routes to an existing GPX (2.11).
- **Example:** the app's guide points to sample output in the GitHub repository "breadcrumb-plus-osm".

#### Snapped GPX
Snapped exports (**Include: OSM Snapped Track Export**, or **CREATE SNAPPED GPX** on a track list) annotate points or segments with the OSM way or route ID and the snap distance, using the selected Profiles file. Viewers that ignore extensions still show the plain track and routes.

#### Catalog metadata
- **What's added:** every app export (period, event, laps, rich, snapped, Plus OSM) carries a small catalog block in the GPX metadata: export type; point count, length, and start/end time; and which extras are present (heart rate, steps, movement, quality).
- **How the list uses it:** **Show Track File List** shows each file with a shape thumbnail, title, "X.X mi • N pts • GPX/Rich/Snapped/Plus OSM/Laps", the date range, and the extras.

**Q:** Which export has my heart rate?
**A:** **Rich Data** (via Track File Settings, or ticked in the Events **Export...** dialog) and **Export laps**. The plain event GPX and basic Extract files don't include it.

**Q:** Which file should I load on a Garmin or COROS watch to see trail names?
**A:** The `…_PlusOSM_V2.gpx` (`…_PlusOSM_V3.gpx` in the next update and later) from **Include: Nearby OSM Lines** (or **Nearby OSM Lines** in the Events export). It holds your track plus the nearby trails as named routes.

### 5.16 Data retention: the 8-day window, Trim, Reset, and files

- **Tracks database** (inside the app): every point recorded while tracking, from events and map sessions. It keeps growing until you trim or reset. It is fine to leave several days of tracks there; **Show Tracks WEEK** on the map draws the past week so you can retrace earlier outings.
- **No automatic deletion:** the app does not delete old GPS points by itself in this version.
- **Events screen:** lists events with any time in the last **8 days**. Older events disappear from the list or show as "partial, early points purged".
- **Extension limit:** an event can't be extended past 8 days from its start.
- **Trim Old GPS Data** (Rapid Tracking page → More options):
  1. It finds GPS entries in the tracks database older than 8 days. If there are none, it says "No GPS entries found older than 8 days."
  2. A **Trim Old GPS Data** dialog offers **Trim Now**, **Export All First**, or **Cancel**.
  3. **Export All First** starts a full ("All") extract ("Full Export Started. Background task processing..."), then offers **Trim Now** or **Wait / Done**.
  4. The result reads "Trimmed N entries older than 8 days."
  5. Trim only affects the points that Extract and Show Tracks read; the Events screen's data is not trimmed.
- **Reset Tracks DB** (main page, 2.7) empties the tracks database and all events, and clears the Path System Alerts history. Cell data is reset only if you tick its box. Extracted files are never deleted. The app's warning: "This cannot be undone. Data is not stored anywhere else, other than in track files you may have already exported/extracted."
- **App's suggested workflow:** **Reset Tracks DB** at the start of an outing, record with Rapid Tracking, then **Extract Track File** (or export the event) at the end. Reset is optional.
- **Files** (extracted, exported, imported, downloaded) are never deleted by reset or trim. They are removed only by you, by uninstalling, or by clearing the app's storage. In version 20261015 there is one exception the other way round: **DELETE** on the Track File List also empties the recorded points (known issue, fixed in the next update; 2.11).
- **Uninstall warning:** uninstalling the app, or **Clear Storage** in Android Settings, deletes the recorded points, the events, and the extracted files in the app's folder. Email or copy important tracks off the phone.

### 5.17 Permissions and what breaks without each

| Permission (Android wording) | Asked when | Without it |
|---|---|---|
| **Location** (precise / "While using the app") | First use; before opening Rapid Tracking. The app first shows the no-warranty notice (**I AGREE** / **I DON'T AGREE**), then a disclosure with **Turn On** / **No Thanks** (2.1). | No map centering, no tracking, no events. |
| **Location: Allow all the time** (background) | When you tick **Resume Active Tracking After Reboot**. | On Android 11+ tracking can't restart after a reboot; you get the "Bring app to front" notification instead. |
| **Notifications** (Android 13+) | First use, with location. | The app's text: "Showing notifications is required to continue to collect GPS track data as you hike. You can leave it off and still access the MAP to see where you are." Intersection and Path System alerts are also silently skipped. |
| **Physical activity** (Android 10+) | When you tick **Enable Step Counter**. | No steps or cadence in recorded points or exports. |
| **Nearby devices** (Bluetooth scan/connect, Android 12+; location on older Android). | When you tick **Heart Rate Monitor**. | If any requested permission is refused, the box unticks and a "Bluetooth Permission Required" dialog offers **Open Settings**. Automatic reconnects also stop if the Bluetooth permission is removed. |
| **Storage** (Android 10 and earlier) | First use. | Required on those versions; the main page shows "Permissions Needed" until it is granted. |
| **Battery optimization exemption** | Never requested by the app. | See 5.18. |

### 5.18 Battery tips

- **GPS rate and screen:** most drain comes from GPS more often than every 15 seconds, and from keeping the screen on while viewing the map. Use **15 Sec** or longer when you can, keep the screen off, and carry a power bank on long hikes.
- **Batching:** **Batch GPS Lower Power** lets the phone deliver fixes in batches. It is suspended while the map is open.
- **Distance:** a larger **Distance:** (for example **5 Meters** or **20 Meters**) means fewer fixes when you're barely moving.
- **Chop Chop:** use it for precise fixes at junctions or viewpoints instead of running a 1-second frequency all day.
- **Extra devices:** an old phone without cellular service can serve as an uninterrupted GPS logger; another device can stay powered off for emergencies, with the app and its files installed.
- **Battery optimization:** the app does not request an exemption, does not show guidance about it, and does not change the GPS rate on its own when you stop. *General Android advice, not app text:* if tracking keeps stopping with the screen off, set the app's battery usage to **Unrestricted** / "Don't optimize" in Android Settings → Apps → <app> → Battery, remove it from any "sleeping apps" or "deep sleep" list some phone makers add, and do not swipe the app away from Recents during an event. Battery-saver modes can also limit GPS.

### 5.19 Quick Q&A

**Q:** How long can one event run?
**A:** Up to 16 hours at Start. Then extend with **Status Update** in steps of 2 min to 16 hours, until the event reaches 8 days from its start.

**Q:** Does Pause stop GPS to save battery?
**A:** No. GPS keeps recording, and the countdown keeps running. Pause only marks the time as paused in the event.

**Q:** I paused and want to stop, but there's no Stop on the map.
**A:** On the map, Stop appears only while paused. You can also stop from the notification (**Stop Rapid Tracks**) or the Rapid Tracking page (**Stop**).

**Q:** Is each Chop Chop a lap?
**A:** No. Marks mean "something mattered here". Laps are found from the shape of out-and-back repeats, with or without marks.

**Q:** My event shows "partial, early points purged". What happened?
**A:** Part of the event lies outside the 8-day window the Events screen looks at.

**Q:** Do the PDXWalk and OsmTrails apps record differently?
**A:** No. Recording, events, and export are the same in both apps. Only the app name in notifications differs.

---

## 6. Messages, troubleshooting by symptom, and version history

For assistants: quote messages exactly as written here, and ask which app and edition the user has when the answer differs. "Full" means PDXWalk or OsmTrails with no suffix. Lite and Loaner have the same download limits; only Lite shows ads.

- 6.A Message index (grouped by feature)
- 6.B Troubleshooting by symptom
- 6.C In-app guides, stale in-app texts, and version history

### 6.A Message index

How to read this index:
- Messages are quoted **exactly** as the app shows them.
- `{x}` marks a value the app fills in, such as a file name, a number, or a time.
- `{app}` is the app name of your edition, for example **PDXWalk** or **OsmTrails-Lite**.
- Kinds: *Snackbar* is a bar at the bottom of the screen. *Toast* is a small floating message. *Dialog* is a pop-up window. *Notification* appears in the Android notification shade.
- Unless a row says otherwise, a message appears in every edition.

#### 6.A.1 Permissions and first start

| Message (exact text) | Kind | When it appears | What it means / what to do |
|---|---|---|---|
| No-warranty text beginning "PDXWalk.com (or OsmTrails.com) (Ron Ledbury) MAKES NO GUARANTEES, REPRESENTATIONS OR WARRANTIES…", buttons **I AGREE** / **I DON'T AGREE** | Dialog (title {app}) | The first time location permission is needed: opening the main screen without precise location, tapping Rapid Track, and similar. | You must tap **I AGREE** before the app asks for location. **I DON'T AGREE** closes the dialog without asking, and location features stay off. Full text in 1.14. |
| "Will use your location:" / "- To center MAP on your location." / "- To capture and store in background to display your tracks on MAP, or build GPX export file for you to optionally share via EMail." / "- Rapid Track option runs continuously for specified time even when you switch to other apps. Can optionally store cell tower strength information, for display on MAP to aid in seeking help when hiking." / "-- The original Background Location option captures location perhaps only every 5 minutes or so. Very low power use, and you can set to start location on boot." Buttons **No Thanks** / **Turn On** | Dialog (location-use notice) | Right after **I AGREE**. | **Turn On** opens Android's own permission requests: precise location, Notifications (Android 13+), and, on Android 10 and older, storage. **No Thanks** cancels. |
| "Global Location is turned off." | Main-screen status text | The phone's Location setting (Quick Settings → Location) is off. | Turn Location on in Android. The app cannot get GPS while it is off. |
| "All permissions granted. GPS ready to go." | Main-screen status text | Everything needed is granted. | Ready. |
| "(Note: Notifications are off. Android requires Notifications to be on for the app to collect GPS track data when the app is turned off. You may have to go to Settings if you had previously turned them off or denied this permission with API 33 or above.)" | Main-screen status text | Android 13+ and notifications for the app are off. | Turn notifications on: Android Settings → Apps → {app} → Notifications. Without them the app cannot record a track in the background. Also, on Android 13+ the main screen counts Notifications as a required permission. **Start Stop Rapid Track** (and other main-screen actions that check permissions, such as the Show Downloaded … List menu items) asks for permissions again instead of opening. |
| "(Note: Notifications are on.)" | Main-screen status text | Notifications are allowed. | Fine. |
| "Permissions Needed\nBoth: Storage (for API 29 or below) and Location\n\nIf you hit 'Don't Ask Again' for Storage then you might have to \nGo to Settings -> Apps -> {app}\n\nOtherwise just hit any of the buttons above for dialog." | Main-screen status text | A required permission is missing. | Tap any main-screen button to get the permission dialog again. If you chose "Don't ask again", grant it in Android Settings → Apps → {app} → Permissions. |
| "{app} App Requires Access to GPS.\"" (the text ends with a stray quote mark) | Snackbar | You denied location. | Location is required. Grant it in Android Settings → Apps → {app} → Permissions → Location. |
| "Thank You for permission. Try task again." | Snackbar | You just granted a permission. | Repeat what you were doing. |
| "{app} App Requires Write Access.\"" / "Thank You for write permission. Try task again." | Snackbar | Storage permission on older Android versions (10 and below). | Same as above. |
| "Resume Tracking After Reboot" — "{app} uses your location in the background, even when the app is closed or not in use, to restart an active tracking event after your phone restarts. Locations are recorded to the event's track on this phone.\n\nOn the next screen, please select 'Allow all the time'." Buttons **Continue** / **Not Now** | Dialog | You tick **Resume Active Tracking After Reboot** and the app does not yet have "Allow all the time". | **Continue** → choose **Allow all the time** on Android's screen. Without it, a restart cannot resume tracking by itself. |
| "Step Counter Permission Required" — "This app needs access to step counter data to track your activity. This permission is required for fitness tracking features." **Open Settings** / **Cancel** | Dialog | You ticked **Enable Step Counter** and denied Android's "Physical activity" permission. | Tap **Open Settings** and allow Physical activity, or leave the step counter off. |
| "Bluetooth Permission Required" — "This app needs Bluetooth permission to connect to your heart rate monitor. Only necessary when using external sensors." **Open Settings** / **Cancel** | Dialog | You ticked **Heart Rate Monitor** and the permission request was not fully granted. The heart-rate box is unticked. | Tap **Open Settings** and allow **Nearby devices** (Android 12+) and Location (see 6.B.6). |

#### 6.A.2 Tracking (Rapid Track), the tracking notification, and restarts

| Message | Kind | When | Meaning / action |
|---|---|---|---|
| "Location running." + "Time Remaining:  {h}:{mm}:{ss} h:mm:ss", buttons **Launch app** / **Stop Rapid Tracks** | Ongoing notification | Whenever the tracking service runs: during an event, and during the map's 5-minute "map GPS". | Normal. **Stop Rapid Tracks** stops tracking at once and ends the event, with no confirmation. **Launch app** opens the main screen. |
| "{app} Needs to Restart Tracking Service." / "Bring app to front to restart location service" | High-priority notification (vibrates) | An event still has time left, but Android stopped the tracking service and the app is not on screen. A repeating alarm checks about once a minute (or at your tracking frequency, if longer). | **Tap it.** This opens the main screen, which restarts tracking if the screen is unlocked and permissions are still granted. Points were **not** recorded while the service was stopped, so the track has a gap. See 6.B.1–6.B.2 to prevent it. |
| "status: running" / "status NOT running" / "Time left to run: … expires at {time}" / "no time limit" | Rapid Tracking status text | Rapid Tracking screen. | Shows whether the service is running and when the event ends. |
| "status: starting location tracking..." | Status text | Up to about 10 s after **Start** or **Update**. | Wait. |
| "Stopping location tracking..." → "Location tracking stopped successfully"; button text "Stopping..." → "Stopped ✓" | Status text / button | After **Stop**. | The event has ended. |
| "( Map-only time left to run: … )" and the button **Stop Map GPS** | Status text / button | Opening the MAP starts a short "map GPS" session (5 minutes) when no event is running. | This only moves the blue location on the map. **It is not an event**: it is not listed on the Events screen, and marks, Chop Chop and the map's alert strip do not apply (5.7). |
| "Map GPS stopped. Opening the map starts it again for 5 minutes." | Snackbar | You tapped **Stop Map GPS**. | Map GPS is off until you open the map again. |
| "Update tracking" dialog: "Started {t}, {d} ago." / "Ends {t}, in {d}." / "Frequency: {a} s to {b} s" / "Distance: {a} m to {b} m" / "Batch GPS: on\|off" / "Frequency and distance are unchanged." Choices "Keep the end at {t}" / "Add {2 min…16 hours}, ends {t}"; hint "To end sooner, use Stop." | Dialog | Tapping **Status Update** while an event runs. | Keeps or extends the end time, and applies any **Frequency:**, **Distance:** or **Batch GPS Lower Power** change you made on the page before tapping **Status Update** (5.5). |
| "Nothing changed" / "The event has already ended" / "Tracking ends {time}" | Snackbar | After **Update**. | Result of the update. |
| "Resume Active Tracking After Reboot (needs 'Allow all the time')" | Checkbox label | The option is ticked but background location is not "Allow all the time". | Grant "Allow all the time" in Android Settings → Apps → {app} → Permissions → Location. Without it the option cannot restart tracking by itself after a reboot. |
| "Resume Tracking After Reboot" — "If the phone restarts while an event still has time left, tracking starts again without opening the app.\n\nNeeds location permission 'Allow all the time'. Without it, a 'Bring app to front' notification asks you to open the app instead." | Dialog (long-press help) | Long-press the checkbox. | Explains the option. |
| "If this is a loaner version it might need to be returned to get updates.\n\nRapid Tracking is disabled." **OK** | Snackbar (stays until dismissed) | **Loaner editions only**, after the loaner period ends, when you press **Start** (Rapid Tracking) or the map's start-tracking button. | The loaner has expired. New events cannot start. See 1.3. |
| "Map location is not available for Profiles coverage" | Toast | Starting tracking when the app has no map location to check Profiles coverage against. | Open the MAP once so it has a location, then try again. |
| "Profiles coverage" dialog (buttons **Use selected** / **Profiles page** / **Cancel**); "Switch Profiles file"; "Tracking is running" — "{file} does not cover your current GPS position (or its bounds are unknown).\n\nSwitching now stops routing, OSM way snapping and intersection detection for the rest of this event." | Dialogs | Starting an event (or switching Profiles during one) when a feature that needs Profiles is on (live snapping, intersection alerts, etc.) and the selected Profiles file may not cover you. | Choose a Profiles file that covers where you are, or continue without one. Switching to a non-covering file mid-event turns those features off for the rest of the event. |
| "Map location is not available" / "Unable to check Profiles coverage" / "Profiles: {name}" | Toast | Same flow. | "Profiles: {name}" confirms the file now in use. |

#### 6.A.3 Tracking options (long-press help on the Rapid Tracking screen → Advanced)

| Title | Exact help text | Notes |
|---|---|---|
| **Chop Chop** | Quoted in full in 5.9 ("Hold the phone still for a moment, tap its corner twice on your other palm…"). | Checkbox **Chop Chop For GPS Burst**. Feedback is vibration plus a chime at the end. There is **no** "burst complete" notification, although the Recent Updates text says there is. |
| **Intersection Alerts** | "Notifies you when you're approaching a trail or path intersection. An alert triggers when your GPS is within 50 meters of a known intersection.\n\nIntersection data is calculated from OpenStreetMap data. Some paths have names, which will be displayed. You can view all intersection points on the map by enabling the 'Points' display layer." | Off by default. Needs a Profiles file and notifications. |
| **Path System Alerts** | Quoted in full in 5.12 ("While you drive or bike (faster than about 9 mph), notifies you once for each walkable path system within 3 km…"). | Checkbox **Path System Alerts (driving)** with **Minimum combined trail (km):** (default 4). Off by default. |
| **Heart Rate Monitoring** | "Retrieves the latest heart rate from a Bluetooth-connected monitor and adds it to your GPS data. This combined data is saved and can be included in GPX export files." Buttons **OK** / **Change Monitor** | **Change Monitor** scans for a replacement strap while the current one keeps recording. |
| **Cell Tower Polling** | "Records cell phone signal strength data for map visualization. Prevents duplicate points by not saving when nearby data already exists." | Checkbox **Capture Cellular Bar Strength?** (disabled on devices without a phone radio). |
| **Forward Progress Ratchet** | "When enabled, the track will NOT show retreats — preventing 'spider web' track patterns from GPS jitter.\n\nDISABLE for interval training (e.g., running stairs) where you intentionally go back and forth on the same path." | Checkbox **Enforce Forward Progress (Anti-Spider Web)**. |

#### 6.A.4 Alert notifications while tracking

| Notification | When | Meaning / action |
|---|---|---|
| "Approaching Intersection" — "Approaching **{path A}** near **{path B}**" | **Intersection Alerts** on, while tracking runs, within 50 m of a known intersection in the selected Profiles file. Vibrates twice and disappears after 1 minute. | Informational. Channel name in Android settings: **Intersection Alerts** ("Notifications for approaching intersections"). |
| "Path system {d.d} km {N/NE/E/…}" (on a motorway: "Path system {d.d} km {dir} of {exit name \| the exit}") — "{d.d} km of trail: {names \| Unnamed paths}" | **Path System Alerts (driving)** on, while tracking runs (an event or a map session), moving faster than about 9 mph (4 m/s), checked every ~600 m. Disappears after 10 minutes. | Tap it to see that trail system on the map. Channel: **Path System Alerts** ("Walkable path systems near you while driving or biking"). During an event with continuous centering on, alerts also appear as a strip at the top of the map (3.9). |
| "No Profiles file covers here: no path system alerts" | Map strip | Path System Alerts are on during an event, and no downloaded Profiles file covers your position. | Download or select a Profiles file for that area. There are no alerts until one covers you. |

#### 6.A.5 Heart rate monitor

| Message | Kind | When | Meaning / action |
|---|---|---|---|
| "HeartRate - Scanning..." → "HeartRate - Select Device" → "HeartRate - Connecting..." → "HeartRate - Connected" → "HeartRate - Ready" → "Heart Rate ✓ ({bpm} BPM)" | Checkbox label, live | After ticking **Heart Rate Monitor**. Amber = in progress. Green ✓ = BPM values are reaching the track. | Wait. The guide says connection can take 10–15 seconds. |
| "Heart Rate ✗ no data ({n}s)" | Checkbox label (red) | Connected earlier, but no BPM received for {n} seconds. Points are being recorded **without** heart rate. | Check strap contact and battery. The app reconnects automatically during an event. |
| "Heart Rate - Disconnected" / "HeartRate - Error" | Checkbox label (red) | The link dropped or failed. | Turn the monitor off and on. Make sure no other app is connected to it. Untick and re-tick the box. |
| "Scanning for Heart Rate Monitors" — "Searching for devices... Please wait." | Dialog | During the scan (about 10 seconds). | Wait. |
| "Select Heart Rate Monitor" (list) with **Cancel** / **Rescan** | Dialog | One or more monitors were found. | Pick yours. The choice is remembered and reconnected automatically. |
| "No Heart Rate Monitors Found" — "No compatible heart rate monitors were detected. Make sure:\n\n• Your device is powered on\n• It's within range\n• Bluetooth is enabled\n\nYou can try scanning again." **Rescan** / **Cancel** | Dialog | The scan found nothing. | See 6.B.6. The scan **only lists devices whose Bluetooth name contains** one of: "Polar H", "Polar OH", "TICKR", "HRM", "Heart Rate", "Pulse", "Garmin HRM", "Wahoo", "Myzone", "RHYTHM", "Coospo", or the text you type in **Custom Heart Rate Filter**. |
| "Enable Heart Rate first" | Toast | **Change Monitor** pressed while heart rate is off. | Tick **Heart Rate Monitor** first. |
| "Scanning for heart rate monitors..." | Toast | **Change Monitor** pressed. | A list of straps follows. The current strap keeps recording until you pick another. |
| "HR Error: {error}" where {error} can be "Bluetooth initialization failed", "Missing Bluetooth permissions", "Nearby devices permission is required", "Scan failed: {Scan already started \| Application registration failed \| Feature unsupported \| Internal error \| Unknown error code: n}", "Failed to start service discovery" | Toast | Setup scan or connection failed (outside an event's automatic reconnect). | Permissions: grant Nearby devices / Bluetooth. "Application registration failed" / "Internal error": turn Bluetooth off and on, then retry. |

#### 6.A.6 Extract (export), email, and text-message location

| Message | Kind | When | Meaning / action |
|---|---|---|---|
| "Export GPS Coordinates\n    From Database to File" with choices All / Today / Yesterday / Past Week / Last Hour / Last 15 Minutes, button **Export** | Dialog | Tap **Extract Track File**. | Picks the time span copied from the tracks database to new .gpx (and optional .geojson) files. The choice is remembered. |
| "Exporting All Tracks" / "Exporting Today's Tracks" / "Exporting Yesterday's Tracks" / "Exporting Past Week's Tracks" / "Exporting Last Hour's Tracks" / "Exporting Last 15 Minutes' Tracks" | Snackbar | After **Export**. | The extract is running. The files appear in **Show Track File List**. |
| "No rich data available for the selected duration." | Snackbar | **Rich Data** is on in Track File Settings, but the rich database has nothing for that span. | The normal GPX is still written. Only the extra "rich" file is skipped. |
| "Email Extracted Track File Help" with a "Right now:" status: "• Newest extract: {when}, {n} files" (or "none yet"); "• Tracks database: holds points since {when}…" (or "empty (reset, or nothing recorded yet)"); "• Latest tracking event: started {when}, reached {x} mi from its start" (or "no real movement" / "none since the last reset"); then one of **"Nothing to attach yet. Tap EXTRACT TRACK FILE first."**, "The newest extract was made before the last reset.", **"Extract again before emailing."** {n} points, reaching {x} mi, were recorded after the newest extract., "{n} points were recorded after the newest extract, without real movement.", **"The newest extract is up to date."** Buttons **Extract Track File** / **Dismiss** | Dialog | Long-press **Email Extracted Track File**. | Tells you whether the files that would be attached include your latest walk. If not, tap **Extract Track File** first. |
| Email preview: "Last Location . . ", AGE, ACC, "Include link to current location?", "using map:", "Include track file attachments?", file list with "Age: Days/Hours/Mins" | Dialog | Tap **Email Extracted Track File**. | Check the attachment list and its age. **FORWARD TO EMAIL** hands off to your email app. You press Send there. |
| "Failed To Invoke Chooser" | Toast | No app could take the email or share request. | Install or enable an email app (e.g. Gmail), then try again. |
| "Failed To Invoke Texting App" | Toast | **Text MSG My Location** could not open a messaging app. | Install or enable an SMS app. |
| "Getting Current Location" | Snackbar | Preparing the text or email location link. | Wait. Check **AGE** and **ACC** in the preview. The preview refreshes for up to 30 s. |
| "SMS template" / "Email template", "Template saved on this device", "Save template changes?" — "Save your changes, discard them, or keep editing." (**Save** / **Discard** / **Keep editing**), "Enter a phone number or leave blank", "Enter a valid email address or leave blank" | Template screens | Menu **Set SMS Text Settings** / **Set EMail Settings**, or **EDIT** in a preview. | Recipients you tick are saved on this device ("Recipients are saved on this device…"). You still review and send in the other app. |
| "You have made some changes." — "Would you like to save before exiting?" | Dialog | Leaving **Set Track File Settings** with unsaved changes. | Save or discard. |

#### 6.A.7 Reset and trim

| Message | Kind | When | Meaning / action |
|---|---|---|---|
| "Reset Track File Databases to Empty" — "This cannot be undone. Data is not stored anywhere else, other than in track files you may have already exported/extracted." / "You can cancel\n   -->> Export/Extract track data into GPX file(s).\n        (There is an ALL option)\n   -->> Come back here to empty the databases." Checkbox "Reset Cell Data along with other GPS track data." with the note "Optional Cell Phone signal strength database can also be reset. It is designed and intended to be useful for your future hikes and not to be regularly reset. But you can still chose to reset it here." | Dialog | Tap **Reset Tracks DB**. | Reset permanently deletes all points that were not extracted. Extract first if you want to keep them. Extracted files are not deleted. Leave the cell-data box unticked unless you really want to clear the signal history. |
| "RESETTING TRACK DATA" | Toast | Reset confirmed. | The database is being emptied. |
| "No GPS entries found older than 8 days." | Toast | Rapid Tracking screen menu → **Trim Old GPS Data** with nothing old. | Nothing to trim. |
| "Trim Old GPS Data" — "Found {n} GPS entries older than 8 days.\n\nWould you like to export all your GPS data before trimming, or just trim them now?" Buttons **Trim Now** / **Export All First** / **Cancel** | Dialog | Trim with old data present. | **Export All First** writes a full extract before deleting. |
| "Full Export Started. Background task processing..." then "Export Started" — "A full export has been started. You can wait for the 'Exported' notification or continue to trim now.\n\nTrim the {n} day old data now?" | Toast / Dialog | After **Export All First**. | You can trim right away. The export has already captured the data. |
| "Trimmed {n} entries older than {d} days." | Toast | Trim done. | Done. |

#### 6.A.8 Track file lists, imported GPX, events

| Message | Kind | When | Meaning / action |
|---|---|---|---|
| "Are You Sure?" — "Do you want to delete selected track files?" | Dialog | **DELETE** in **Show Track File List**, or **Delete Selected** in **Show Imported GPX List**. | Deletion is permanent. In version 20261015, DELETE on the Track File List also empties the recorded points (known issue, fixed in the next update; see 2.11). |
| "Are You Sure?" — "Do you want to copy selected track files to the shared Download folder?" | Dialog | **Copy To Downloads** in the track file list. | Copies the files to the phone's public Download folder, where other apps (and a PC over USB) can see them. |
| "Select a track file first" / "Share one file at a time" / "Track folder is not available" / "Share currently supports .gpx and .geojson files" / "Missing file: {name}" / "Could not share {name}" / "No app available to share {name}" | Toast | **SHARE** in a track list. | Select exactly one .gpx or .geojson file. Install an app that can receive files. |
| "There are not at least 2 GPS points to draw." | Toast | Showing a track file on the map that has fewer than 2 points. | The file is empty or nearly empty. Extract a longer span. |
| "Snap GPX Files" — "Snap {n} GPX file(s) to OSM data?\n\nThis will create: {outputs}" / "Please select GPX files to snap" / "Snapping operation already in progress" | Dialog / Toast | **CREATE SNAPPED GPX** in the track file list. | Makes a copy of the track aligned to OpenStreetMap paths from your Profiles file. |
| "GPX Snapping", "Please select a GPX file to snap", "Snapping GPX file...", "GPX file snapped successfully: {file}", "Snapping failed: {reason}", "Error snapping GPX file: {error}", "Selected file cannot be snapped. Please check it's a valid GPX file.", "File Already Exists" — "The snapped file '{file}' already exists. Do you want to overwrite it?" | Dialog / Toast | **CREATE SNAPPED GPX** in **Show Imported GPX List**. | Same feature for imported files. |
| "Add OSM Data" / "Rebuild OSM Data" — "Add OSM way data to this GPX file?" (or "This GPX file already appears to include OSM route data.\nRebuild nearby OSM route inclusions using the current profile?"), then "Current OSM Profile:" and "Coverage Analysis:" | Dialog | **ADD OSM DATA**. | Adds nearby OSM trails from the selected Profiles file as `<rte>` routes (next update and later: from every Profiles file in its folder). Coverage lines: "Good coverage: {n} OSM lines found…", **"No OSM data found for track region…"**, **"No profile selected"**, "Status: Profile file not found", "No track or route data found in GPX file", "Unable to parse GPX file for coverage analysis". If coverage is bad, select a Profiles file that covers the track first. |
| "Adding OSM data...", "Saved: {file}", "Output file already exists", "Could not parse GPX or no track/route data", "Error: {error}", "Add OSM Data operation already in progress", "Please select a GPX file to add OSM data", "Unable to access track folder", "The file '{file}' already exists. Overwrite?", "Rebuild will overwrite the selected file '{file}'. Continue?" | Toast / Dialog | Same flow. | "Could not parse GPX…" means the file has no `<trk>`/`<rte>` points or is not valid GPX. |
| "No events in the last 8 days" / "{n} of {m} events in the last 8 days. Long-press one to see its shape." | Events screen header | Menu **Show Events (last 8 days)**. | Events are Rapid Tracking sessions. Map-only GPS sessions are not events. |
| "Select one or more events" | Snackbar | **Show** or **Export** with nothing selected. | Tick events first. |
| Export dialog "Always exported to My Tracks:\n{name}.gpx … Also export:" with options "GeoJSON output: {name}.geojson", "Nearby OSM Lines: one ...PlusOSM_V2.gpx per event" ("...PlusOSM_V3.gpx" in the next update and later), "Rich Data (EXPERIMENTAL): one ...__rich.gpx per event" | Dialog | **Export** on the Events screen. | Choose extra outputs. |
| "Preparing {n} event(s)" / "Exporting {n} event(s)" / "Exported {name}.gpx[ + GeoJSON][ + Nearby OSM][ + Rich] to My Tracks" / "Export failed: {error}" | Snackbar | Events show/export. | Exported files appear in the track file list. |
| "Too few points to draw this event" / "Could not draw the event: {error}" | Snackbar | **Show** on an event with fewer than 2 points. | The event recorded almost nothing (see 6.B.1). |
| Long-press details: "In a vehicle: {km}", "Nothing to trim: no drive, and no still time at either end." or "Trimmed: {start} to {end}, {km} on foot"; buttons **Use trimmed** / **Use whole** / **Close** → "Show and Export use this event trimmed" / "Show and Export use this event whole" | Dialog / Snackbar | Long-press an event. | Trimming cuts off driving and standing-still time at the ends. |
| "Exported {name}.gpx and .csv to My Tracks" (action **Show**) / "Laps export failed: {error}" | Snackbar | **Export laps** from an event's long-press. | Lap files are listed as "Laps" in the track list. |

#### 6.A.9 Map screen

| Message | Kind | When | Meaning / action |
|---|---|---|---|
| "Turned off {the tiles map X \| the vector map X}[ and lines from {Profiles}]: not available for this area. Turn it (them) back on to choose a file that is." | Snackbar (about 8 s) | Opening the map when the saved view is outside the selected base map or Profiles file (and you are not continuously centering during an event). | The base map was switched to a blank background, or Profiles lines were turned off, because the selected file has no data here. Turn the layer back on (TILES / VECTOR / LINES toggles) and pick a file that covers this area. |
| "{old Profiles} is out of date; {newer Profiles} is installed." (action **Use it**) | Snackbar | A newer edition of your selected Profiles file is in the same folder. | Tap **Use it** to switch to the newer file. |
| "Continuous centering is off: your location is not inside {the base map X \| the Profiles file Y}." | Snackbar | Returning to the map from a file list during an event after selecting a file that does not cover your GPS position. | The app assumes you are exploring elsewhere. Tap the pill or **Resume centering** to follow your position again. |
| "Continuous centering is off · tap to turn on" / "{n} new fixes · {m} min since centered / event start" | Map pill | During an event, while centering is off. | Tap it to re-center and follow your location. |
| "Your location or files changed. Choose a covering file again." | Snackbar | You picked a covering file from the center-button dialog, but the location or files changed meanwhile. | Open the dialog again. |
| "Base map coverage" — "{status}\n\nNo downloaded MBTiles or Mapsforge file covers this feature." / "Mapsforge coverage" or "MBTiles coverage" — "{status}\n\nNo downloaded {kind} covers the current map center." / "Switch base map" / "Switch Mapsforge map" / "Switch MBTiles file" | Dialog | Checking coverage or switching maps. | You need a map file for that area (see 6.B.3). |
| "Hillshade on" / "Hillshade off"; "Hillshade coverage" — "{status}\n\nNo downloaded Terrain-RGB file covers {lat}, {lon}." / "Switch Terrain-RGB file" | Snackbar / Dialog | **Show hillshade** checkbox and its long-press settings. | Hillshade needs a Terrain-RGB MBTiles file that covers the area (download it from Show Downloaded MBTiles List → Hillshade). |
| "Route highlight enabled" / "Route highlight cleared" / "Previous multiline restored" / "Previous multiline is outside the map view" / "No previous multiline to restore" | Snackbar | **Route highlight** checkbox. | Status of Route highlight. |
| "Choose multiline route" / "Switch extended multiline?" | Dialog | Tapping a segment that belongs to more than one named route. | Pick which route to highlight. |
| "Magnifier off" / "Magnifier 125%" / "Magnifier 150%" | Snackbar | Long-press **+** or **−**. | Map magnification step. |
| "No map app can open this location" | Snackbar | The amber arrow button (open in another map app) found no app. Next update and later: **Open this point in another map** in the arrow's menu. | Install Google Maps, OsmAnd, or another map app. |
| "Google Maps is not installed or cannot open directions" | Snackbar | **Next update and later:** amber arrow → **Directions in Google Maps** without Google Maps installed or enabled. | Install or enable Google Maps, or choose **Directions in OsmAnd**. |
| "Get OsmAnd for offline directions" — "OsmAnd is not installed or cannot open directions. …" (**Open Google Play** / **Not now**) | Dialog | **Next update and later:** amber arrow → **Directions in OsmAnd** without OsmAnd installed. | **Open Google Play** opens OsmAnd's store listing (in the browser if the Play Store app is missing). Download OsmAnd's maps for your route before you lose coverage. |
| "No app can open Google Play. Search for OsmAnd in your app store when you have internet access." | Snackbar | **Open Google Play** in the dialog above, with neither the Play Store nor a browser available. | Install OsmAnd from another app store. |
| "Feature details copied" / "No app can open this link" | Toast / Snackbar | Route-name button details (whole-feature info with OSM links). | — |
| "Would you like to HIDE this RECENT line?" / "Would you like to SHOW longer RECENT line?" | Dialog | Tapping the recent-track line. | Show or hide the recent track. |
| "Invalid Coordinates Found" | Toast | Setting a target/waypoint, or **Set Track Log Boundary**, with an unusable position. | Pan the map to a valid spot and retry. |
| "Profiles catalog is not available" / "Map center is not available" | Toast | Coverage tools before the map or file list is ready. | Wait a moment and retry. |
| Compass gunsight help: "Compass Gunsight" — "Navigate toward your target: • Green lines point North • Red needle shows device direction • Rotate until red dots align • Large colorful dot = perfect alignment! Set Target: Drag map to center desired location, then tap 'Set Target' Gestures: • Tap: Help • Long press: Move • Double tap: Reset" | Dialog | Tap the gunsight. | How to set and use a target. |

#### 6.A.10 Walking route to target / HERE (experimental, release)

| Message | Kind | When | Meaning / action |
|---|---|---|---|
| "Experimental route" — "Experimental: this route may use closed, private, or missing paths. Check it against the map and what you see before following it." Checkbox "I know it is experimental. Auto-close and show only the route data from now on." | Panel | First routes, until you tick the checkbox. The caution also stays in the route's info balloon. | Treat the route as a suggestion only. |
| "Route to target: {x} mi" / "Straight line: {x} mi" | Route balloon | Tap the drawn route. | — |
| "Route to target hides in 20 s" (action **Keep**) / "Route to target hides once Profiles lines are on" (action **Keep**) / "Route to target kept" (action **Hide**) | Snackbar | Tapping the drawn route to the target. | The route auto-hides 20 s after it is shown or tapped. If Profiles lines are off, it hides once they are turned on. Tap **Keep** to keep it on the map. |
| Yellow pin "route {x} mi" / "tap to hide"; "Route to HERE hidden" | Map pin / Snackbar | Long-press the **HERE** marker at the map center. | Tap the pin to hide it. |
| "Too many paths and roads between here and there for a quick route. Try a closer point." | Snackbar | The area between you and the target holds too much path data. | Choose a closer target. Routing is aimed at short distances ("the last 2 miles"). |
| "Switch map for this route?" — "{No Mapsforge map is selected \| The map {X} holds {your location but not {end} \| {end} but not your location \| neither your location nor {end}}}. Route gaps are filled from the selected map's paths.\n\n{Y} holds both." Buttons **Use {Y}** / **Keep {X}** (or **Route anyway**) | Dialog | The selected Mapsforge map does not cover both ends, but another downloaded map does. | **Use {Y}** gives the router more path data. |
| "Dijkstra route: {reason} ({connector summary})", where {reason} is "current location unknown", "no target set", "target is beyond the configured distance", "route graph unavailable", "no nearby line or multiline", or "no route found" | Snackbar | Routing failed. | "beyond the configured distance": by default targets more than 5 km away in a straight line are refused. "no nearby line…": the start or target is not near a Profiles path, so turn on Lines and pick a spot on a trail. "current location unknown": wait for a GPS fix. |
| "Dijkstra route failed" / "Dijkstra route already computing…" / "Dijkstra route hidden" / "Dijkstra {mode}: {n} subsegments, …" | Snackbar | Routing errors, busy, hidden, or a technical summary (shown after you tick "I know it is experimental"). | Retry after the current computation ends. |

#### 6.A.11 Path Name Search and Path Systems

| Message | Kind | When | Meaning / action |
|---|---|---|---|
| "Path systems near {GPS \| map center}" (choices "Within {n} km") → "Finding path systems within {n} km..." → "Closest path systems within {n} km" (rows "{names}\n{n} ways, {x} km of trail, {here \| x km dir}") | Dialog / Snackbar | **Path Systems** button in Path Name Search. | Tap a system to view it. |
| "Path systems need a Profiles file with a tile index (version 4 or later)" | Snackbar | Your selected Profiles file is an older format. | Download a current Profiles file for the area. |
| "No path systems within {n} km" | Snackbar | Nothing found. | Pick a larger radius or another area. |
| "Bike: keep" / "Hike: keep" (dialog) → "Bike: {choice}" / "Hike: {choice}" | Dialog / Snackbar | Long-press **Hike** or **Bike**. | Chooses which road types are included. |
| "Map Center Set For {name}" / "Map Center and Target Set For {name}" / "Kept the current map center" / "No usable location for this item" | Toast | Choosing a search result. | Then tap **GOTO MAP**. |

#### 6.A.12 Route highlight guided tours

| Message | Kind | When | Meaning / action |
|---|---|---|---|
| "Try Route highlight" — "Choose a guided map demonstration. The app reuses compatible offline files already on this device and offers to download only what is missing." (OsmTrails: "Choose a region. …") | Dialog | **Try Route highlight** in About, Recent Updates, the Lite daily-ad thank-you, or Buy Maps' raster notice. | Choose a tour. |
| "United States Route highlight tours" / "United Kingdom Route highlight tours" (OsmTrails) / "Cumbria Route highlight tours" (OsmTrails) / "Mt. Hood Route highlight tours" | Dialog | Tour menus. | — |
| "Checking the offline maps and Profiles files on this device…" | Progress | Starting a tour. | Wait. |
| "Download missing tour files?" — "• {file} … Total download: about {n} MB.\n\nThis explicit tutorial confirmation replaces the usual 123 code. The code remains required on the ordinary download screens." (may add "You can instead supply the Mapsforge map yourself from OpenAndroMaps and let the tour download only the rest.") Buttons **Download and start** / **Not now** / **Own map instead** | Dialog | Some tour files are missing. | You must be online. Tours download only what is missing, without the 123 code. |
| "Preparing {tour}"; "…The download is taking longer than expected. You can close this dialog and reopen the tour later; completed files will be reused." | Progress dialog | During tour downloads. | Safe to close. Files that finished downloading are kept. |
| "Use your own Mapsforge map" — "Any Mapsforge .map that covers {area} works in place of {file}. 1. In your web browser, open openandromaps.org, choose Downloads, then {region hint}. Download the Karte/Map file, not the theme. 2. The browser saves a .zip in your Download folder. Extract it with your Files app so the .map file is visible. 3. Back …" | Dialog | **Own map instead**. | Then use **Import File**. |
| "No web browser is available" / "The app Download folder is unavailable" | Toast | Own-map flow. | Install or enable a browser. Check storage. |
| "After permissions are granted, reopen the Route highlight tour" | Toast | A tour needed permissions. | Grant them, then restart the tour. |
| "{feature} is highlighted" / "Advanced PCT multiline tour" / "Find PCT Oregon Section G" | Dialog | Tour steps. | Follow the instructions in the dialog. |

#### 6.A.13 Downloads (Profiles, Mapsforge, MBTiles, hillshade), common to all download screens

| Message | Kind | When | Meaning / action |
|---|---|---|---|
| "Would you like to download:\n\n{name}?\n{size} MB  -- Enter Code: 123", field **Enter Code**, buttons **No** / **Yes** | Dialog | Profiles downloads, Mapsforge menu downloads, Buy Maps downloads. | Type **123** exactly and tap **Yes**. The code is a deliberate "are you sure" step for large downloads. It is not a password or a purchase. |
| "Download {title} hillshade" — "{file}\n{x.xx} MB, max zoom {z}\n\nEnter Code: 123" (**Cancel** / **Download**) | Dialog | Hillshade (Terrain-RGB) downloads. | Same: type 123. |
| "Download attempt initiated for {name}" | Toast | Code accepted. | The download is queued. Progress shows in Android's download notification. |
| "CODE FAILED to download:{name}" | Toast | Code was wrong or empty (Profiles, Mapsforge, Buy Maps). | Nothing downloaded. Try again and type exactly `123`. |
| "Incorrect code. No download started." | Toast | Wrong code for a hillshade file. | Same. |
| "File Download Queued" | Toast | Android accepted the download. | Watch the Android notification titled with the file name ("Downloading"). |
| "Already Downloaded" | Toast | The file already exists in that folder. | Select it from the list instead. |
| "Already downloaded or downloading: {name}" / "Already downloaded or downloading in this folder: {file}" | Toast | Tapping a file that is present **or has an unfinished download record** in that folder. | In version 20261015 this also appears after a download that failed or was cancelled: the app still remembers it as "downloading" (known issue, fixed in the next update; see 6.B.4). |
| "Not enough disk space" | Toast | Free space is less than the file size + 300 MB. | Free up space or choose another folder (for example the SD-card folder **Private Ext DL**). |
| "Download link unavailable for {name}. Try again later." / "Download link unavailable for {name}" | Toast | The download server did not provide a link (offline, or a server problem). | Check your internet connection and try again later. |
| "Download failed for {name}" | Toast | Unexpected error before the download was queued. | Retry. |
| "Download failed: {file}. {reason}. Try again." (**OK**) | Snackbar | **Next update and later:** Android reported that a queued download failed while an app screen was open. {reason} is for example "Not enough disk space", "Storage not found", "Network error" or "Server replied 403". | Fix the cause if you can, then download again. The file is no longer treated as downloading. |
| "No Internet Connectivity, try later." | Toast | MBTiles or hillshade download with no connection. | Go online. |
| "No download folder available." | Toast | The storage folder cannot be reached (e.g. SD card removed). | Choose another folder or reinsert the card. |
| "This terrain file is not available for this app." | Toast | A hillshade file that is Full-only or OsmTrails-only. | See the edition table in 6.B.4. |
| "{title} terrain is not yet available." / "Zoom {z} · Coming soon" | Toast / list row | The file is listed but not published yet. | Wait for a later release. |
| "Other hillshade specials" — "Terrain RGB for offline hillshade\nTap a heading to collapse; tap a file for download details." Sections "Places & trails", "Country coverage", "Regional coverage"; rows "{size} · Zoom {z} · {Downloading \| Downloaded \| Available to download}" | Dialog | Show Downloaded MBTiles List → **Hillshade only** → **Other specials...** | Choose a terrain file. |
| "Lite Version Note:" — "The Profiles files are large and expensive to make available for download. This feature is limited to full version." (and tips about using your own GPX files) | Dialog | **Lite and Loaner**: tapping a Profiles download that is Full-only (Oregon, West, MidWest, South, NorthEast, UK Britain, West subsets). | Use the free areas (Forest Park, Mt. Hood, PDX Metro, specials) or the guided tours, or use the Full edition. |
| "Lite / Loaner Version Note:" — "The large Mapsforge map files are expensive to make available for download. Downloading them from this app is limited to the Full version." / "You are welcome to download the same kind of Mapsforge map file for your region from OpenAndroMaps, free of charge. Choose the Karte/Map download, unzip it if needed, then use Import File in this app to add the .map file. Tap Open OpenAndroMaps below to visit their site." / "You can still download the lower resolution terrain (hillshade) file for {the US \| the US or the UK} in this version. Open the Downloaded MBTiles List, choose Hillshade only, then Other specials." Buttons **Dismiss** / **Open OpenAndroMaps** | Dialog | **Lite and Loaner**: Mapsforge region menu downloads. ("the US or the UK" appears in OsmTrails.) | Get a free .map from OpenAndroMaps and import it. |
| "Lite Version Note:" — "The MBTiles files are very large and expensive to make available for download. This feature is limited to Full version." (with notes on importing MBTiles made for you) | Dialog | **Lite and Loaner**: Full-only MBTiles in Buy Maps. | Import MBTiles you got elsewhere with **Import File**. |
| "OpenAndroMaps" — "OpenAndroMaps provides open-source map files that you can use with this application. Select the Karte/Map option for download. You can download map files from: https://www.openandromaps.org/en" (**Open Website**) | Dialog | Show Downloaded MapsForge Maps List → menu **OpenAndroMaps Info (Third-Party)**. | Opens their web site. |
| "No application can handle this request" | Toast | No browser available. | Install or enable a browser. |
| "Other free specials" (rows "{title} ({size} MB) - downloading/downloaded"), then "Download {title}" — "Would you like to download:\n\n{file}?\n{size} MB" | Dialog | Mapsforge page **Other specials**. | No code needed here. |
| "Special profiles (sizes uncompressed)" / "West subsets (sizes uncompressed)" | Dialog | Profiles page lists. | Sizes shown are after decompression. |
| "Opened Private Int DL because Buy Maps stores downloads here. Tap this message to dismiss." | Banner | MBTiles list opened from Buy Maps **GoTo Downloads**. | Buy Maps files are stored in the private internal download folder. |
| "Are You Sure?" — "Do you want to delete {file}?" (for files of 1 GB or more, adds "Large-map downloads have a progressive cooldown: 3 days after the first successful download, plus 3 days after each later successful download of the same version. Deleting this file does not erase that history.") | Dialog | Deleting a map or Profiles file. | Think twice before deleting very large maps. |

#### 6.A.14 Buy Maps (MBTiles raster archive)

| Message | Kind | When | Meaning / action |
|---|---|---|---|
| "Before you buy: huge raster files.\nI now recommend Mapsforge + hillshading.\nTap for free alternatives and MBTiles import." → dialog "Before you buy raster maps" (summary in 6.C.5) with **Try Route highlight** | Banner / Dialog | Buy Maps screen, all editions. | The author recommends free Mapsforge maps plus hillshade before buying raster archives. |
| "This list is for the Full version.\nNot available to buy from Lite or Free version." | Snackbar | **Lite and Loaner**: tapping the Buy Maps list buttons. | Purchases are Full-only. The "Bought (or, free included)" list still works. |
| "* Lite Version Note:\nPdxMetro and MultFalls files\nabove are downloadable." | Screen note | Lite and Loaner. | The note names only two; all seven free files listed in 1.4 can be downloaded. |
| "Have Internet" / "No Internet" | Snackbar | Long-press in "Available To Buy". | Connection check before buying. |
| "If you just turned internet back on please wait a few seconds and try again after we build a SKU details list. Thanks." / "Must be some network error. Do not have SKU details list." | Snackbar | Full: Google Play product details not loaded yet. | Wait a few seconds online, then try again. |
| "Would you like start Purchase Flow for:\n{title}?\n\n{size} MB -- Enter Code: 123\n\n{description}" | Dialog | Full: long-press an item to buy. | Type 123 to open Google Play's purchase screen. |
| "Purchase Flow initiated  {sku}" / "CODE FAILED to Purchase:{sku}" / "Purchase Acknowledged" | Toast / Snackbar | Purchase steps. | A cancelled purchase shows no message. |
| "File {file} already downloaded, hit GoTo Downloads below to use" | Snackbar | Bought list, file already present. | Use **GoTo Downloads**. |
| "Download attempt initiated for {sku} See Notifications for download progress." | Toast | Bought list download started. | Watch the Android download notification. |
| "Large map cooldown" — "This map was downloaded successfully before. To limit repeated multi-GB transfers, it cannot be downloaded again until {date}. The cooldown grows by 3 days after each successful download of this version." | Dialog | Re-downloading a map of 1 GB or more. | Wait until the date shown. Deleting the file does not reset the cooldown. |
| "File {file} requires valid purchase, please buy {sku} or delete." | Toast | Showing a paid MBTiles file on the map without a recorded purchase on this device/account. | Use menu **Sync Google Play Purchases** on Buy Maps (Full), buy it, or delete the file. |
| "Purchased MBTiles files cannot be shared: {file}" | Toast | **Share** on a purchased MBTiles file. | Paid maps cannot be shared. |

#### 6.A.15 Import File

| Message | Kind | When | Meaning / action |
|---|---|---|---|
| "Import started. A zipped map is inspected first, which can take a minute." | Snackbar | After you pick a file with **Import File**. | Wait. Large files take time to copy. |
| "Error launching file picker." | Snackbar | Android's file picker could not open. | Retry. Check that a Files app is enabled. |
| "{file} is already imported. The existing file was kept." | Dialog | A file with the same name already exists. | Rename the file if you really want both, or delete the old one first. |
| "Not enough free space to import {file}. Free up space and try again." | Dialog | **Next update and later:** free space is less than the file size + about 10 MB. | Free up space, then import again. |
| "Importing Unknown File" — "Sorry, this app cannot open selected file.\nSorry for any inconvenience." {file} | Dialog | Unsupported file type, or a .zip holding more than one file (or an unsupported file). | Supported: `.gpx`, `.geojson`, `.geojson.json`, `.mbtiles`, `.map`, `.osmprofilesdbz`, or a .zip containing exactly **one** of these (next update and later: one `.gpx`, `.geojson` or `.map` only). Unzip multi-file archives first. |
| "Importing GPX File" / "Importing Geojson File" — "The file still needs to be verified.\nMay be deleted from this list if it fails verification.\n[this is a TODO item]" | Dialog | GPX/GeoJSON import. | The file appears in **Show Imported GPX List**. No verification step runs in this version, so the file stays in the list. |
| "Importing MBTiles File" — "If large it may take time to copy.\n(Swipe list down to refresh.)" | Dialog | MBTiles import. | Pull down the list to refresh after a while. |
| "Importing Profiles File" — "If large it may take time to decompress.\n(Swipe list down to refresh.)" | Dialog | .osmprofilesdbz import. | Same. |
| "{file} imported. The list has been refreshed." / "{file} import failed. Check free space and try again." | Dialog | Mapsforge .map import finished. | On failure, free up space and import again. |

#### 6.A.16 Sharing files from the app

| Message | When | Action |
|---|---|---|
| "Compress for share?" — "{file} is {n} MB. Zip it to .osmprofilesdbz in the 24-hour share cache, then share?" → "Compressing" — "Zipping {file}. You can leave this screen; tap Share again later if the zip is ready." → "Share now?" | Sharing a Profiles file. | The zip is kept 24 hours. Tap Share again when it is ready. |
| "Compress failed" / "Could not create share cache folder" | Profiles share failed. | Check free space. |
| "Select a profile file first" / "Select a map file first" / "Select an MBTiles file first" | Share with nothing selected. | Select one file. |
| "Share currently supports .osmprofilesdb files" / "Share currently supports .map files" | Wrong file type selected. | — |
| "MBTiles catalog is unavailable; sharing is disabled" | MBTiles catalog could not be read. | Retry later. |
| "Profile folder is not available" / "Map folder is not available" / "MBTiles folder is not available" | Storage folder unavailable. | Check the SD card / storage. |

#### 6.A.17 Ads (Lite editions only)

| Message | Kind | When | Meaning / action |
|---|---|---|---|
| "Advertisements:" with a button **Authorize Ads** / **Disable Ads** | Main-screen control | **PDXWalk-Lite and OsmTrails-Lite only.** | The banner ad is **off until you tap Authorize Ads**. Tap **Disable Ads** to turn it off again. |
| "Thanks for opening the app!" — "Happy exploring! This full-page ad appears at most once a day. It is an experiment to see whether ad revenue can cover the future cost of making additional downloads available within the app.\n\nBe sure to try the Route highlight tour! It will offer to download the essential files that are missing. Please allow time for those downloads to finish while you are online. The app is built around using downloaded maps and route data offline.\n\nTap Try Route highlight to choose a tour. You can also find it later under More options → About." Buttons **Try Route highlight** / **Continue to app** | Dialog | Lite only, after the once-a-day full-page ad is closed. | Informational. |

### 6.B Troubleshooting by symptom

#### 6.B.0 Key ideas that explain most problems

1. **An "event" is a Rapid Tracking session.** It starts with **Start Stop Rapid Track → Start**, runs for the chosen **Duration** (2 Min to 16 Hours), and records at the chosen **Frequency** and **Distance** (5.2). Use **Status Update** to extend it and **Stop** to end it.
2. **Opening the MAP alone is not an event.** It turns on GPS for about 5 minutes ("map GPS") so the blue location can move. Those points are saved, but the session does not appear in **Show Events**, and marks and Chop Chop do not apply (5.7).
3. **Two stores of tracks.** Points go into the in-app **tracks database** automatically. Track **files** exist only after **Extract Track File** or an Events export. Email attaches only the newest extracted files. **Reset Tracks DB** permanently deletes un-extracted points.
4. **Offline first.** Base maps (Mapsforge .map or MBTiles), Profiles files, and hillshade files must be downloaded or imported **while online, before the hike**, and they must cover the area you are in.

#### 6.B.1 GPS is not recording / the track is empty

| Check | Why | Fix |
|---|---|---|
| Main-page status says "Global Location is turned off." | The phone's Location is off. | Turn Location on in Android Quick Settings. |
| Main-page status shows "Permissions Needed…" or "(Note: Notifications are off…)" | Precise location (and on Android 13+, Notifications) are required to record. | Grant **Location → Precise**, and **Notifications**, in Android Settings → Apps → {app} → Permissions. Then return to the app. |
| Was an event actually started? | Opening the map alone gives only 5 minutes of map GPS, not an event. | Use **Start Stop Rapid Track → Start**. The status should read "status: running" and the "Location running." notification should appear. |
| The event ended | Events stop when the chosen Duration runs out. The notification disappears without a message. | Choose a longer Duration, or tap **Status Update** to add time before it ends. |
| Distance filter too large | With 20 or 100 m, slow walking records few points. | Choose 0/any/all or a few meters. |
| You are outside the supported regions | The app saves points only in the Americas, Europe (to the Urals), New Zealand, and Fiji, whatever your settings (5.13). Version 20261015 saves nothing east of 20°E, eastern Europe included. | No setting changes this. |
| A **Set Track Log Boundary** box excludes the area | Points outside "Log Tracks Only Within This" or inside "Log NO Tracks Within This" are not saved. | Clear the box with **Reset (only within)** / **Reset (none within)** (2.14). |
| Event shows "Too few points to draw this event" | Fewer than 2 points were stored. | Check the items above. Also check reception: the map's satellite button (GNSS sky observer, 3.10) shows used/visible satellites and signal strength. |

#### 6.B.2 The track has gaps, or tracking stopped in the background

**What the app does:** tracking runs as a foreground service with the ongoing notification "Location running." If Android stops it while an event still has time left, a repeating check posts **"{app} Needs to Restart Tracking Service." / "Bring app to front to restart location service"**. Tapping it brings the main page forward, which restarts tracking (the screen must be unlocked). No points are recorded while the service is stopped, so the track has a gap until it restarts.

**Fixes from the app's own settings:**
- **Keep Notifications on** (Android 13+). The app's text says notifications are "required to continue to collect GPS track data as you hike".
- **Tap the restart notification promptly** when it appears.
- **Resume Active Tracking After Reboot** (Rapid Tracking page) restarts a running event after a phone restart **only** with location permission **Allow all the time** (5.6).
- **Batch GPS Lower Power** (Advanced) and longer Frequency values reduce battery use (5.18).
- **Enforce Forward Progress (Anti-Spider Web)** hides back-and-forth jitter in the app's path matching. Turn it **off** for intervals or out-and-back repeats.
- Do not use **Stop Rapid Tracks** in the notification unless you mean it. It ends the event at once.

**Battery optimization and phone-maker "app killers":** the app does **not** ask for a battery-optimization exemption and shows no guidance about it. *General Android advice, not app text:* set the app's battery usage to **Unrestricted** / "Don't optimize" in Android Settings → Apps → {app} → Battery, remove it from any "sleeping apps" or "deep sleep" list, and do not swipe the app away from Recents during an event.

**Gaps that are not the app's fault:** tunnels, deep canyons, dense tree cover, and indoor starts. The map's satellite (GNSS sky) button shows how many satellites are used and how strong they are. For important spots, use **Chop Chop** (5.9) for a burst of frequent fixes.

#### 6.B.3 The map is blank, or no offline map shows

| Situation | What you see | Fix |
|---|---|---|
| Fresh install | Map with no base map (initially, no map is selected). | Download a map: **Show Downloaded MapsForge Maps List** (vector .map), **Show Downloaded MBTiles List** (raster), **Buy Maps** (raster archive, including free items), or a guided tour (**Try Route highlight**, 4.4). Or import a free OpenAndroMaps .map with **Import File** (1.12). |
| Opening the map outside the selected file | Snackbar "Turned off the vector map {X} \| the tiles map {X}…: not available for this area. Turn it back on to choose a file that is." The background is blank. | Turn the Map Tiles / Vector Tiles button back on. The coverage dialog lists files that cover the current view ("Switch Mapsforge map" / "Switch MBTiles file"). If it says "No downloaded {kind} covers the current map center.", download or import one for this area. |
| A base-map button shows a help dialog instead of a map | No file of that kind exists at all. The help says "Many free .map files can be found online for download to your shared Download folder. Thereafter tap 'Import File' button on main page…". | Download a .map (OpenAndroMaps or the Mapsforge page) and import it. |
| Panning to another region | The selected file does not cover it (the map may pan back by itself, 3.5). | Use the button's coverage chooser, or select another file from the list pages (they show whether each file covers the map center or GPS position). |
| Imported a large .map/MBTiles but it is not listed | The copy runs in the background. | Wait, then pull down the list to refresh. For .map you get "{file} imported…" or "…import failed. Check free space and try again." |
| Paid MBTiles shows "File {file} requires valid purchase…" | No purchase is recorded on this device and account. | Full: Buy Maps → More options → **Sync Google Play Purchases**, or buy it. Otherwise delete the file. |
| Hillshade not visible | No Terrain-RGB file covers the area ("No downloaded Terrain-RGB file covers {lat}, {lon}."). | Show Downloaded MBTiles List → **Hillshade only** → download a terrain file, then tick **Show hillshade** (3.7). Hillshade works over any base map or none. |
| Map too small to read | — | Long-press **+** to magnify to 125% or 150% (3.2). |

#### 6.B.4 A download is blocked or fails

**Edition rules (summary; details in 1.4 and 1.10):**

| Edition | Profiles | Mapsforge (.map) | MBTiles / Buy Maps | Hillshade (Terrain-RGB) | Guided tours | Import File |
|---|---|---|---|---|---|---|
| **Full** (PDXWalk, OsmTrails) | All regions, code 123 | All; code 123 for region menus | Buy and download (Google Play), code 123 | All, code 123 | Yes, no code | Yes |
| **Lite and Loaner** | Small areas only (Forest Park, Mt. Hood, PDX Metro, Tahoe Rim, Foothills Trail). Others show "Lite Version Note:" | Small specials (Forest Park, Portland, MtHood, Tahoe Rim Trail, Foothills Trail). Region menus show "Lite / Loaner Version Note:" with an OpenAndroMaps link | No purchases ("This list is for the Full version…"). Seven free files can be downloaded (1.4) | Places & trails files and country-level z8 (US; US and UK in OsmTrails); more detailed terrain is Full-only | Yes, no code | Yes |
| **OsmTrails only (any tier)** | Cumbria and Ledbury-Malvern specials | Cumbria and Ledbury-Malvern specials | — | UK terrain | UK Tours | — |

**Common blocks and failures:**
- **"CODE FAILED to download:{name}"** or "Incorrect code. No download started." — type exactly `123` in the **Enter Code** box. Some quick-download buttons (the Mapsforge Forest Park / Portland / MtHood buttons, Mapsforge **Other specials...**, and the ForestPk/MtHood MBTiles buttons) start without asking for a code.
- **"Download link unavailable for {name}. Try again later."** / **"No Internet Connectivity, try later."** — get online (Wi-Fi recommended for large files) and retry.
- **"Not enough disk space"** — the app needs the file size plus 300 MB free. Free space or use **Private Ext DL** (SD card) where offered.
- **"Large map cooldown"** — maps of 1 GB or more cannot be downloaded again until the date shown. The wait grows by 3 days per successful download, and deleting the file does not reset it.
- **The download started but never finished.** Watch Android's own download notification (title = file name, "Downloading"); it reports whether the download succeeded or failed. **Known issue in version 20261015 (fixed in the next update):** after a download fails or is cancelled from the notification, **the Profiles, Mapsforge-special and MBTiles/hillshade screens may keep treating that file as "downloading"**: its button stays disabled, or you see "Already downloaded or downloading: {name}". Until you update, retry from the **Buy Maps → Bought** list, or through a **guided tour** that includes the file (tours reuse finished files and download only what is missing). Choosing a different download folder may also allow a new attempt there. From the next update, a failed or cancelled download no longer blocks a retry, and a failure that happens while the app is open shows "Download failed: {file}. {reason}. Try again." (6.A.13). If the download screen was open at that moment, leave it and open it again before retrying. There is no automatic retry.
- **Tours:** "Download missing tour files?" replaces code 123 with an explicit confirmation. If it is slow: "You can close this dialog and reopen the tour later; completed files will be reused."

#### 6.B.5 Profiles lines are not showing

1. **Is a Profiles file downloaded and selected?** Menu **Show Downloaded Profiles List**; the active file is marked **ACTIVE**. Lite and Loaner can download only some areas (1.4). Make sure the page's More options item **Disable Profiles** is **not** checked (selecting a Profiles file un-checks it).
2. **Are the layers on?** On the MAP, enable **Breadcrumbs** (More options → **Show Breadcrumbs**), expand the right-side controls, and tap the **Lines** button. Lines draw only at zoom 11 and closer; points at zoom 10 and closer (3.6).
3. **Does the file cover this area?** If not, the app turns the lines off when the map opens: "Turned off … lines from {Profiles}: not available for this area…". The Points/Lines buttons open "Profiles coverage" with "The selected Profiles file does not cover this location." / "No downloaded Profiles file has confirmed coverage of {lat}, {lon}." Choose **Profiles page** and download or select a covering file.
4. **Older file?** "{file} is out of date; {newer} is installed." → tap **Use it**. "Path systems need a Profiles file with a tile index (version 4 or later)" means your file is too old for Path Systems. Download the current one.
5. **Profiles are curated, not complete.** They contain OSM ways tagged as paths and some nearby roads, not every street. Long-press **Lines** → **Include Roads** shows the roads that are included.

#### 6.B.6 Heart-rate monitor will not connect

1. Turn the monitor on and put it on (many straps only broadcast when worn). Make sure **no other app or device is connected** to it.
2. Rapid Tracking → **Advanced** → tick **Heart Rate Monitor**. Allow **Nearby devices** and Location. If "Bluetooth Permission Required" appears, tap **Open Settings** and allow them. Heart rate does not need "Allow all the time".
3. If Bluetooth is off, Android asks to turn it on.
4. **Name filter:** the scan lists only devices whose Bluetooth name contains one of: Polar H, Polar OH, TICKR, HRM, Heart Rate, Pulse, Garmin HRM, Wahoo, Myzone, RHYTHM, Coospo. If your monitor uses another name, type part of its name in **Custom Heart Rate Filter** (under the Heart Rate option) and scan again (**Rescan**).
5. Be patient: connecting takes 10–15 seconds. Watch the label go "HeartRate - Scanning..." → "Connecting..." → "Heart Rate ✓ ({bpm} BPM)".
6. "Heart Rate ✗ no data ({n}s)" means it is connected but not sending. Check strap contact and battery. During an event the app reconnects automatically.
7. "HR Error: … Application registration failed" or "Internal error": turn Bluetooth off and on, then retry.
8. To change monitors mid-event, long-press the option → **Change Monitor**.
9. If the **Heart Rate Monitor** option is missing, the phone has no Bluetooth LE support.
10. Tested monitor (per the in-app guide): Polar OH1.

#### 6.B.7 Import fails

- Use **Import File** on the main page. The file must end in `.gpx`, `.geojson`, `.geojson.json`, `.mbtiles`, `.map`, or `.osmprofilesdbz`, or be a `.zip` holding exactly **one** such file (next update and later: one `.gpx`, `.geojson` or `.map` only). Anything else gives "Importing Unknown File — Sorry, this app cannot open selected file."
- **Upper-case extensions are fine.** A file named e.g. `TRACK.GPX` is imported and saved as `TRACK.gpx`; the original keeps its name.
- **Unzip multi-file archives** and import the `.map` (or other) file itself.
- **Profiles** import as `.osmprofilesdbz`, or (next update and later) as an unzipped `.osmprofilesdb`. Version 20261015 refuses the unzipped file.
- **"{file} is already imported. The existing file was kept."** — rename the file, or delete the existing copy first.
- **"Not enough free space to import {file}. Free up space and try again."** — the import needs the file size plus about 10 MB free. Free space and retry.
- **No message at all after "Import started…"** — the app found no destination folder, or (version 20261015 only) too little free space (file size + 10 MB). Free space and retry.
- **GPX not shown on the map** — imported GPX files are under **Show Imported GPX List**; select them and tap **Show Selected Files**, then set the map's **Tracks** button to show imported tracks (3.8). "There are not at least 2 GPS points to draw." means the file has fewer than 2 points.
- Snapping and Add OSM Data need a Profiles file covering the track ("No OSM data found for track region…").

#### 6.B.8 Export or email does not attach files

- **Extract first.** Email attaches only what **Extract Track File** last wrote. Long-press **Email Extracted Track File** for a live status: "Nothing to attach yet. Tap EXTRACT TRACK FILE first." / "Extract again before emailing." / "The newest extract is up to date."
- In the email preview, tick **Include track file attachments?** and check the file list and its **Age**.
- Choose which file types to attach in the email template (**edit**): GPX, GeoJson, GPX+OSM. Extra outputs (Nearby OSM Lines, Rich Data, GeoJSON) are set in **Set Track File Settings** (5.15).
- "Failed To Invoke Chooser" → no email app is available. Install or enable one.
- The app never sends mail itself. You must press **Send** in your email app.
- Alternatives: **SHARE** a single .gpx/.geojson file from **Show Track File List**, or **Copy To Downloads** to put files in the public Download folder.
- "No rich data available for the selected duration." affects only the optional Rich file.

#### 6.B.9 My recent points disappeared / Extract produced nothing

- **Did you use DELETE on the Track File List?** Known issue in version 20261015 (fixed in the next update): confirming **DELETE** there also empties the recorded-points database that **Extract Track File** reads from, even when no file is selected. Events are not affected, so the same walk may still be exportable from **Show Events (last 8 days)** if it was recorded as an event. Points that were never extracted or exported cannot be recovered. Until you update, extract any recent tracks before using DELETE.
- **Did you use Reset Tracks DB?** It deletes all recorded points and all events (2.7).
- **Did you use Trim Old GPS Data?** It deletes points older than 8 days (5.16).
- **Wrong period?** Check the period in the Extract dialog (**All**, **Today**, **Yesterday**, **Past Week**, **Last Hour**, **Last 15 Minutes**). Yesterday means the previous calendar day.
- **Were points saved at all?** See 6.B.1 (permissions, Track Log Boundary, the supported regions).
- **Looking in the wrong folder?** The Track File List has **Internal** / **External** buttons; new files go to the folder set in **Storage Location** (5.15).

#### 6.B.10 App restarted, or the phone rebooted, mid-event

- The event's time window is stored. When tracking can resume, the normal "Location running." notification returns. There is no special "recovered" message.
- **Phone reboot:** with **Resume Active Tracking After Reboot** ticked **and** "Allow all the time" granted, tracking restarts automatically after unlock. Otherwise you get "Bring app to front to restart location service". Tap it.
- **App stopped** (by Android, the phone maker's battery manager, or swiping away): Android may restart the service by itself. If not, the "Bring app to front" notification appears. Opening the **main page** (not just the map) while unlocked restarts tracking.
- Points between the stop and the restart are missing. Long-press the event in **Show Events** to see its shape.
- **Do not Reset Tracks DB** to "fix" a broken event. That deletes all un-extracted points.

#### 6.B.11 Ads in Lite

- Only **PDXWalk-Lite** and **OsmTrails-Lite** contain ads.
- **Banner:** off by default. It appears only after you tap **Authorize Ads**; tap **Disable Ads** to remove it.
- **Full-page ad:** at most once a day (the day changes at midnight UTC), when the main page opens. It is followed by "Thanks for opening the app!". It is independent of the banner setting. To avoid ads, use a Full edition.

#### 6.B.12 Walking route to target fails (experimental)

- "Too many paths and roads between here and there for a quick route. Try a closer point." — pick a closer target. Targets more than about 5 km away in a straight line are refused ("target is beyond the configured distance").
- "no nearby line or multiline" — both ends must be near Profiles paths. Turn on Lines and pick a point on a trail.
- "Switch map for this route?" — accept **Use {map}** so the router has map data covering both ends.
- Always check the route against the map and the ground: "Experimental: this route may use closed, private, or missing paths." (4.5)

### 6.C In-app guides and version history

The app ships several built-in help texts. This part preserves their content so an assistant can answer questions without the app open, and lists the places where an in-app text no longer matches what version 20261015 does.

#### 6.C.1 Where the in-app help lives

| In-app place | How to open it | What it contains |
|---|---|---|
| **About** dialog | Main page More options → **About . . .** | Version number, the Lite note (Lite and Loaner, 1.2), and the "Getting Started" instructions (6.C.2). Buttons: **Try Route highlight** and **Dismiss**. |
| **Recent Updates & Feature Guide** | Main page More options → **Recent Updates...** | Expandable "what's new" categories (October 2026, September 2026, Route highlight tour, What's New Since v20260707, Step Counter, Heart Rate Monitor, Database Update, GPS Movement Analysis, ChopChop, GPX Export with OSM Routes, Compass Gunsight, What Stays the Same, Quick Tips). Buttons: **Got it!** and **Try Route highlight**. The header reads "PDXWalk v{version}" in every edition. |
| **No-warranty disclaimer** | Shown before the first location-permission request | Full text in 1.14. Buttons: **I AGREE** / **I DON'T AGREE**. |
| **Long-press help on main buttons** | Long-press **Extract Track File**, **Email Extracted Track File**, **Text MSG My Location**, or **Reset Tracks DB** | Help dialogs (6.C.3). |
| **Long-press help on Rapid Tracking options** | Long-press a checkbox on the Rapid Tracking page or under **Advanced** | Explanations of Chop Chop, Intersection Alerts, Path System Alerts, Resume Tracking After Reboot, Heart Rate Monitoring, Cell Tower Polling, Forward Progress Ratchet (texts in 6.A.3). |
| **Long-press help on MAP buttons** | Long-press almost any MAP button | "… Toggle Help/Explanation" dialogs (section 3). |
| **Path Name Search Help** | **Help** button on Path Name Search | How searching works (4.1). |

#### 6.C.2 "Getting Started" (About dialog), summarized

The About dialog labels these instructions "These limited instructions updated 20250317. It is still a TODO item". They say:

- **Set up before the hike.** Visit OSMTrails.com for video guides. Before a hike, download and select a map file (an .MBTiles raster file or a Mapsforge .map file) and a **Profiles** file. Mapsforge .map files contain compressed data that draws map tiles on demand. Profiles files contain a subset of OpenStreetMap lines tagged as paths (and some nearby roads), with elevation added to each point.
- **No map is selected at first.** Use **Show Downloaded MBTiles List** to pick a downloaded MBTiles map, or **BUY MAPS** for a list that includes free options. You can also import free Mapsforge files from the internet; those files do not include the author's changes that make "path" lines stand out.
- **Profiles.** **Show Downloaded Profiles List** opens a page where you download Profiles files built from OpenStreetMap "path" data, with elevation from USGS/SRTM elevation data. Select one. Then on the MAP page, with **Breadcrumbs** on, tap a line to see a marker with an elevation profile.
- **Route highlight.** On the MAP page, turn on **Breadcrumbs**, tap **Lines**, open the right-side controls, and check **Route highlight** (4.3). **Try Route highlight** offers the guided tours (4.4); OsmTrails splits them into **US Tours** and **UK Tours**.
- **Mapsforge.** Use **Show Downloaded MapsForge Maps List** to download .map files.
- **SMS and email setup (optional).** Save a phone number to prepare a text message with a link to your location (**Set SMS Text Settings**). Save an email address to prepare emails with exported GPX/GeoJSON tracks attached (**Set EMail Settings**). Recipients can open the files in Google Earth or GPXSee.
- **MAP page.** Shows your current or recent locations. Use **TODAY** / **YESTERDAY** to show saved points for those periods.
- **Cell signal.** Tracking can record phone signal strength, shown on the MAP as numbered icons. This can help you judge how far back you would have to hike to get coverage in an emergency. This data is **not** cleared by a normal reset.
- **Rapid tracking.** The **START STOP RAPID TRACK** button opens the GPS tracking settings. The frequency and duration you choose are remembered.
- **Target icon.** With the here-there icon on, the app shows the distance from you to the map center. Tap the icon to make that point your target. Long-press the target icon to move it.
- **Export settings.** **Set Track File Settings** sets export preferences, including the period (All, Today, Last Hour, …).
- **Notifications permission (Android 13+).** Notifications are required to keep collecting GPS track data while you hike. You can leave them off and still use the MAP to see where you are.
- **The author's workflow.** Reset at the start of a hike, extract at the end. This saves the data to a file you can send to others or show on the MAP later.
- **Multiple devices tip.** The author sometimes carries several devices to compare GPS accuracy. An old phone without cell service can log GPS without interruption. Another device can stay powered off for emergencies, with the app and its map and Profiles files installed.
- "One fix at a time. One new feature at a time."

#### 6.C.3 Main-page long-press help

Long-press **Text MSG My Location**, **Extract Track File**, **Email Extracted Track File**, or **Reset Tracks DB** for a help dialog. Their content matches 2.4 to 2.7: the app never sends texts or email by itself; Extract writes new files and removes nothing; Email attaches only the newest extract and shows a live "Right now:" status; Reset empties the tracks database (and cell data only if ticked), keeps every extracted file, and cannot be undone. The Reset help describes the workflow RESET → walk → EXTRACT → email and warns that uninstalling or **Clear Storage** deletes extracted files too. It does not mention that Reset also deletes all events.

#### 6.C.4 No-warranty notice

The full text and when it appears are in 1.14. In short: the author makes no guarantee about the reliability of the app or any GPS data, the app is not certified for navigation, life-safety, or vehicle use, and path data comes from OpenStreetMap contributors and is only as good as the last editor made it.

#### 6.C.5 "Before you buy raster maps" (Buy Maps note, all editions)

A summary of the dialog behind the Buy Maps banner ("Before you buy: huge raster files. I now recommend Mapsforge + hillshading. Tap for free alternatives and MBTiles import."):
- **You do not need to buy the MBTiles archive.** Raster maps are huge files (often many GB). The author now almost always prefers **Mapsforge .map** files, which draw tiles on the fly.
- **Preferred setup: Mapsforge + hillshading.** Terrain-RGB MBTiles add a hillshade overlay on top of a Mapsforge map. Even PDXWalk Lite and OSMTrails Lite can use free OpenAndroMaps maps with hillshading. Download and extract the OpenAndroMaps ZIP, then **IMPORT FILE** the .map.
- **Terrain downloads:** Show Downloaded MBTiles List → **Hillshade only**. Lite includes country-level z8 terrain (US in PDXWalk; US and UK in OSMTrails). Higher-detail terrain is Full-only.
- **Profiles are more than a display map.** They are curated subsets of full OpenStreetMap way definitions (not tiled vector map data). Mapsforge maps and raster MBTiles do not replace them. Lite variants include smaller sample areas.
- **Route highlight is not routing.** It highlights OSM ways that share common reference values. It does not calculate routes or give turn-by-turn directions. The planned routing focus is "the last 2 miles to a target".
- **Make your own small MBTiles** from a GPX track using the author's GPX_to_MBTiles_Tool repository on GitHub. Copy the .mbtiles into the Android Download folder and **IMPORT FILE** it (any edition).
- **Archive generations:** PDXWalk has an older generation of raster maps. OSMTrails has a newer one, including Britain.

#### 6.C.6 In-app texts that no longer match the app

These texts are still shown in version 20261015 but describe older behavior or labels. This file describes what the app actually does.

| Where the text appears | What it says | What version 20261015 actually does |
|---|---|---|
| Recent Updates → Database Update | Trim old data is under "Settings → Database" | **Trim Old GPS Data** is in the More options menu of the **Rapid Tracking** page (5.16). The text is corrected in the next update. |
| Recent Updates → ChopChop Feature | A chopping / up-and-down motion; tap the center button several times; a notification when the burst is complete | Two corner taps on your palm with the phone held still before and after; a **double-tap** on the map's center button adds a mark; feedback is vibration and a chime, with no notification (5.9). The Rapid Tracking long-press help is current. |
| Recent Updates → Step Counter | Steps reset to zero when tracking begins; view the step count on the tracking screen | The stored count is a running total from the phone's sensor and is not shown live; steps appear in Rich exports and laps CSV (5.10). |
| Recent Updates → GPS Movement Analysis | Better battery when stationary | The app does not change the GPS rate on its own (5.13). |
| Recent Updates → Compass Gunsight Navigation | Rotation modes "Target Mode / Compass Mode" | The modes are **North Up**, **Manual Rotate**, **Target Direction**; there is no Compass Mode (3.4). |
| Recent Updates header | "PDXWalk v20261015" | Shown in OsmTrails editions too; it does not identify the brand (1.2). |
| About → instructions | "Show Cell Bars" | The MAP menu item is **Show Recent Cell Signal**. |
| About → instructions | "Show Downloaded MapsForge List" | The menu item is **Show Downloaded MapsForge Maps List**. |
| About → instructions | "RESET TRACK DB", "EXPORT TRACK FILE" | The buttons are **Reset Tracks DB** and **Extract Track File**. |
| About → instructions | "This app does not provide route guidance to the target" | Tapping the target marker draws an experimental walking route (4.5). |
| About → instructions | "(as of March 2025) includes offline MBTiles maps for Wildwood Trail in Forest Park"; "updated 20250317. It is still a TODO item" | Old dates; downloads are described in 1.10. |
| About → Lite note | Says "Lite" | Also shown in Loaner editions, which have the same download rules as Lite. |
| Points button help | Crossings are a "blue X" | Crossings draw as an orange star (3.6). |
| Compass button help (main page) | "The top of the maps always point NORTH" | The MAP can rotate (3.4). |
| Path Name Search Help | The 'PATHS NEAR MAP' button; "just a string compare" | The button is **Any Near Map Center** / **Any Near GPS**; current Profiles files use word-start matching (4.1). |
| PCT Search tour dialog | **GOTO MAP** is "at the bottom of this page" | It is the green button at the top right of Path Name Search. |
| Buy Maps (Lite and Loaner) | "PdxMetro and MultFalls files above are downloadable." | Seven free files can be downloaded (1.4). |
| GPX/GeoJSON import dialog | "May be deleted from this list if it fails verification. [this is a TODO item]" | No verification runs; the file stays in the list (2.10). |
| Reset Tracks DB help | Lists only the tracks database and cell data | Reset also deletes all events and the Path System Alerts history (2.7). |

#### 6.C.7 Version history (most recent first)

Versions are calendar dates (YYYYMMDD). The current version is **20261015**. User-facing items only.

**20261015 (October 2026; in-app "Latest Updates — October 2026")**
- **Path System Alerts (driving):** Rapid Tracking → **Advanced** → **Path System Alerts (driving)**. While driving or biking, one notice for each trail system within 3 km, with a minimum-trail-length setting. Alerts also show as a strip at the top of the map; tap one to see that trail system. The app switches to the downloaded Profiles and map file that cover your drive (5.12).
- **Events screen:** **Show Events (last 8 days)**. Show an event on the map or export it. Long-press an event to see its shape, trim it, or **Export laps**; lap exports appear as "Laps" in the track list (5.14).
- **Path Name Search filters:** **Hike / Bike / Any** and **Named only**; long-press Hike or Bike to choose which road types to include. A new **Path Systems** button lists nearby trail systems (4.1, 4.2).
- **Map magnifier:** long-press the map's **+** or **−** to magnify to 125% or 150%.
- **Tracking that survives a restart:** **Resume Active Tracking After Reboot**. **Status Update** can extend a running event's end time.
- **Better track display:** a GPX file with several tracks shows each one as its own line. Long-press a track file → **Show on map**. Map labels grow when you zoom past level 15.
- **Chop Chop:** no longer triggered by jogging. Each chop is saved as a mark in event exports.
- **More help:** long-press help on Extract Track File, Email Extracted Track File, Text MSG My Location, and Reset Tracks DB.
- **Walking route to your target (experimental):** tap the target marker to draw a walking route; tap again to hide it. Gives up early on far or data-heavy areas.
- **Walking route to the HERE marker (experimental):** long-press the **HERE** marker; a yellow pin shows the route length; tap the pin to hide the route.
- **Open this spot in another map app:** the amber arrow button at the lower left of the map. Links and other map apps now open as their own entries in Recents.
- **Known issue:** **DELETE** on the Track File List also empties the recorded points (fixed in the next update; 2.11).
- **Known issue:** a download that failed or was cancelled can keep its button grey or show "Already downloaded or downloading" (fixed in the next update; 6.B.4).
- **Known issue:** an import with too little free space stops with no message (fixed in the next update; 2.10, 6.B.7).

**20260922**
- Tapping a trail line highlights it with bracket end caps. Waterway crossings get cyan labels. Path Name Search can search near the map center or near your GPS position.

**September 2026 (in-app "Latest Updates — September 2026")**
- **Offline terrain hillshade:** a **Show hillshade** checkbox on the map, with opacity, exaggeration, and sun controls on long-press, over any base map or none. The MBTiles download picker groups hillshade files by places and trails, country coverage, and regional coverage. Overview country terrain is available in every edition; more detailed terrain needs Full.
- **More guided tours:** **Mt. Hood Tours** (Timberline Trail, **PCT Search**).
- **OsmTrails only — Cumbria:** **UK Tours** → **Cumbria Tours** (Aira Force Loop, Scafell Pike with hillshade). If the map is missing, **Own map instead** explains how to get and import an OpenAndroMaps map.

**Between 20260820 and the September/October releases**
- Track-file lists show GPX summaries, route-shape thumbnails, and GeoJSON shape previews. GPX exports embed catalog metadata for better listings.
- Share files from the app (tracks, MBTiles base maps, Mapsforge maps, Profiles), subject to each file type's sharing policy: purchased MBTiles cannot be shared, and Profiles files are zipped before sharing.
- Elevation for OSM points read from the standard `ele` tag.
- Map control buttons show the live state of each map layer.
- Rich GPX track titles include the export timestamp.
- Fixes: out-and-back junctions and GPS "teleport" spikes in exports, more reliable database recovery, safer service start and stop, faster point-name search, notification and compass compatibility.

**20260820 (Google Play, 2026-08-20)**
- **Route highlight** (originally "Extend multiline"): select, highlight, label, and restore connected named paths from Profiles data. Guided tutorials, including the OsmTrails UK tours.
- **What's New** content in the in-app updates dialog.
- **Profiles coverage awareness:** shows whether installed Profiles cover the map center or your GPS position, and offers to switch when Points or Lines are outside coverage.
- **Download catalogs** for Profiles, MBTiles, and Mapsforge with coverage highlighting.
- Named steps and footways on vector overlays.
- **Sensor-assisted GPS filtering**, and a readable location summary on the main page (coordinates, elevation, accuracy, fix age).
- **Heart rate:** automatic reconnection during events, clean monitor swapping, and indicators that show whether fresh BPM data is being recorded.
- Changes: larger point budgets for map and track previews; whole-meter elevations in Rich GPX for device compatibility; markers and gunsight scale with screen density; compass smoothed and corrected for portrait, landscape, and upside-down.
- Fixes: deep zoom restored after turning tiles off; Path Name Search distances; heart-rate freshness and mid-event monitor change; vector-path taps, road widths, and label placement.

**20260707 (Google Play, 2026-07-07)**
- **Rich GPX export** with metadata, route elements, optional GeoJSON, duration presets (Today, Yesterday, Past Week, …), and on-screen completion feedback.
- **OSM routes in GPX:** nearby OSM trails exported as `<rte>` routes (keeping trail names and OSM IDs) for COROS, Garmin, and other watches, without false connecting lines. **ADD OSM DATA** for imported or exported GPX files.
- **Trim Old GPS Data** (removes stored points older than 8 days).
- **Intersection Alerts** with accuracy bursts and notifications. **ChopChop** gesture for an immediate high-accuracy burst. (An "Adaptive GPS tracking" mode listed for this release is not active in the current version.)
- **Bluetooth LE heart rate** (device selection, spike filtering, notification display, optional heart rate in GPX). **Step counter** integration.
- **Interactive target gunsight** and map rotation modes.
- Landscape, tablet, and foldable layouts. In-app **Recent Updates** guide.
- In-place base-map switching and limited MBTiles over-zoom.
- Changes: minimum Android version raised to 7.0. Internal and external download folders are treated as separate stores.
- Fixes: database crashes; track info windows and centering; Profiles selection; **Gmail can attach exported GPX files on newer Android versions**; notification countdowns over one hour.

**20250401 (Google Play, 2025-04-01)**
- Import zipped map and GPX files. A menu action to open OpenAndroMaps. An option to disable Profiles files and their map breadcrumbs. Updated bundled Mapsforge data. Fixes for a Profiles query error and an email-body formatting warning.

**Earlier releases** are not covered here.

---

## About this file

This guide was generated from the apps' source for version 20261015 (PDXWalk and OsmTrails, Android). It will be updated with new releases. If the app on your phone shows something different from this file, the app's newer behavior wins.