13. FAQ

FAQ

Language: English. Chinese version: 13. FAQ (中文)

This page answers recurring questions briefly. If you need a symptom-by-symptom troubleshooting flow, go to [[14. Troubleshooting]].

Is Trail Mate just a Meshtastic reskin

No. Trail Mate is an independent MCU terminal close to a decentralized phone, centered on anonymous operation, decentralization, offline operation, and TAK. Meshtastic, MeshCore, and Reticulum are its three network paths, not its product definition.

Does “close to a decentralized phone” mean copying a smartphone

No. Trail Mate locally owns identity, contacts, messages, position, maps, and awareness, which makes its organization phone-like. It does not copy cellular service, app stores, broadband media, or public social platforms.

Does TAK mean ATAK, WinTAK, or CoT compatibility

Not currently. TAK describes Trail Mate's on-device team/tactical awareness: members, positions, maps, tracks, markers, assembly points, and messages form shared awareness. The repository has no ATAK, WinTAK, or Cursor-on-Target interoperability implementation, so the wiki does not claim one.

Will major MCU features continue to be added

No. The MCU feature set is defined. Continued work covers defects, security, reliability, interoperability correctness, resource efficiency, hardware adaptation, tools, tests, and documentation. It will not add major product domains or let position transmission drift away from anonymous authorization and Team/TAK semantics.

Can it run Meshtastic, MeshCore, and Reticulum at the same time

Not currently. The runtime activates one protocol role selected by configuration. It does not inspect incoming packets and switch protocols automatically. A large share of “why does this not match” problems are simply cases where the devices are not on the same protocol path.

Does it support Reticulum and LXMF

Yes, and not only as a future plan. Select Reticulum to run the device-side Reticulum/LXMF stack. Interfaces and propagation load from /trailmate/reticulum/config.json on the SD card. LXMF is the messaging layer; USB RNode/KISS is an external-host modem capability in an explicitly enabled HostLink runtime, not another settings protocol.

Why can I not send messages

Check the most common causes first:

• are both sides on the same protocol role
• did the Reticulum SD configuration load, and is at least one interface ready
• do region, preset, channel, PSK, or RNode carrier parameters really match
• are you using a target that intentionally trims the capability you expect

If you are using MeshCore, remember that the clearest stable loop today is still text communication. More complex app-data expectations should not be assumed automatically.

Can I bulk-add Reticulum contacts by editing an SD-card file?

Not in the current release. Contacts are stored in the firmware-owned binary /mesh/peers.bin, not a TSV/JSON configuration file. Do not modify peers.bin; the legacy lxmf_addresses.tsv is not imported by the current ESP runtime. Add an LXMF destination through Contacts or save a peer already discovered through announce/path traffic. See 4.1 Reticulum, LXMF and RNode Bridge for the complete persistence behavior.

Why can I receive but not transmit

That usually looks more like a transmit-side or configuration-side issue than a total radio failure. Check:

• whether the wrong build target was flashed, especially for radio variants such as Pager SX1262 versus SX1280
• whether transmit-related settings are disabled or constrained
• whether region, power, and carrier parameters really match the intended network

If you can reliably receive packets, the UI is rarely the first suspect.

Why does the map not display

The most common cause is resource preparation, not firmware logic:

• the directory must follow standard z/x/y
• satellite tiles must be .jpg
• mbtiles is not supported
• the selected layer must match the layer you actually prepared

If GPS works but the map is blank, start with [[5. Offline Maps]].

Why does GPS never get a fix

First confirm that the current target actually enables GPS. T-Watch S3, for example, currently has HAS_GPS=0. That is not a failed fix. It means the target itself is not using a GPS path.

If the hardware does support GPS, then check the environment. Indoors, garages, and partially obstructed locations are poor first-fix conditions. Move outdoors into an open area, then use GNSS Sky Plot to see whether satellites are actually visible.

Why do Team pages or some features differ across devices

Because the project dynamically enables or hides pages based on hardware capability and resource budget. The clearest example is GAT562 Mesh EVB Pro, which explicitly removes Team, HostLink, SD, CJK, and pinyin IME support.

That is often a deliberate boundary, not simply unfinished work.

Why do input direction and interaction feel different across devices

Because the hardware input models are different. T-Deck combines keyboard, touch, and trackball. T-Watch S3 is mainly touch. GAT562 uses a 5-way joystick. Large-screen devices follow yet another path. Trail Mate tries to keep page structure coherent, but it does not force identical tactile behavior everywhere.

Why is Chinese or Unicode rendering incomplete on some devices

That is often a target boundary issue. GAT562 Mesh EVB Pro, for example, explicitly does not support CJK or pinyin input. It should not be expected to match the text capabilities of the fuller ESP32 handheld targets.

How should I choose region

Do not treat the code default as a recommended deployment value. Region, frequency, and power should be chosen according to the actual protocol path, your local regulations, and the network your team intends to join. Those settings are among the first things worth checking manually after first boot.

Can I package the map into one file and copy it over

Not currently. The device reads directory tiles and does not support mbtiles. If you prefer managing offline caches on desktop, the practical route is to use Trail Mate Center to prepare and export the directory structure the device expects.

Why do routes or tracks not appear

Check the paths first:

• KML goes under /routes
• track files go under /trackers

If the directory does not exist, the device simply shows that there is nothing available there.

Why does power-off or sleep behavior look different from what I expected

Some of that behavior is board-specific. For example, T-LoRa-Pager does not follow the normal power-off path while USB is still attached, and will prompt Unplug USB to power off. That is closer to hardware and power strategy than to ordinary app-level logic.