Skip to content

Troubleshooting

Lwb89dev edited this page Oct 19, 2026 · 1 revision

Troubleshooting

Before anything else: note the version (Settings → Info → Version) — it is the first thing a bug report needs.

Installing and updating

The update says “protected data unavailable” or “could not bring your data over”

Nothing was erased. Restart the phone and choose Try again. Continue without importing starts empty and leaves the old data on the phone untouched. If the problem persists, export your data before reinstalling.

Android refuses to install the APK

Allow installs from the app you opened it with. If it says the package conflicts with an existing one, the file was signed with a different key — check the certificate as described in Installation.

Navigation

GPS unavailable

Roadstr asks for location on first launch. If you denied it, go to Settings → Apps → Roadstr → Permissions → Location and grant Precise location. Roadstr uses a foreground navigation service and does not need permanent background-location access.

Navigation stops when the screen turns off

It should not. Allow notifications for Roadstr (the trip is held by a foreground service with a notification) and check that battery optimisation is not restricting the app.

The speed limit is missing

Roadstr shows a limit only when OpenStreetMap states it (maxspeed). An unknown limit stays unknown rather than being guessed.

Map tiles do not load

Check your connection. Tiles are fetched at run time (OpenStreetMap by default) and the dark themes recolour those same tiles on the device. If you set a custom Map tile URL, check it too.

A route cannot be calculated

Try another routing provider (Settings → Map). The public OSRM server is a free community service and can be busy. For a GraphHopper server or an API key, use Verify.

Voice

Voice guidance not working

Download the voice models from Settings → Navigation voice → Voice model. Voice is available for Italian, English, Spanish, French, Japanese, Chinese, Portuguese and German; other languages keep text instructions on screen.

The microphone button opens another app, or does not use the offline recogniser

That is the fallback. Roadstr uses its own recogniser only when the model is installed (Settings → Voice search), the language is one of the model's 25, the microphone permission is granted and the phone is 64-bit Arm with enough memory. Otherwise it hands over to the recogniser your phone provides. See Voice search.

Voice search is marked unusable on this phone

The engine could not load the model (for instance, too little memory). Close other apps and restart Roadstr; if it persists, delete the model — the microphone button then keeps using your phone's recogniser.

The model download stops

Tap Download the model again: it resumes from where it stopped. If you see a checksum message, the file was discarded; download again. If storage is short, free some space (the model needs 485 MB plus a margin).

A house number or street name comes out wrong

Numbers and street names are the hardest case for a speech model. Roadstr repairs Italian numbers and snaps street names to the streets around you when one is clearly closest. Edit the text before searching if it is still wrong, and tell us which phrase failed.

Nostr

Amber shows “invalid request”

Make sure your version of Amber supports NIP-55. Roadstr uses get_public_key, sign_event and the NIP-44 methods.

A bunker login says the bunker did not answer

For a pasted link, check that it starts with bunker:// and names at least one wss:// relay. Or choose Open signer app and approve Roadstr's nostrconnect:// offer. Make sure the signer is online and approve the request there; public relays can rate-limit or be down for a while.

My report did not appear

With no connection it is saved (will publish once you're back online). Otherwise check your signer approved it. Public relays may be slow; other phones see a report as soon as a relay delivers it.

Journey sync stopped

Your signer cannot do NIP-44, so sync stopped and kept the local data. Use a signer that supports it (Amber does).

Two markers for one report

Older Roadstr versions cannot tell that a report and its jooray/roadstr copy are the same report. Turn Also publish in the compatible format off, or update the other phone.

Public transport

No public-transport result

Coverage depends on which operators publish open data. Where there is none, Roadstr says so. You can help by adding the feed to Transitous.

MeshCore

A MeshCore radio is not found or will not connect

MeshCore is experimental and has not been tested on real radios. Check that the radio runs companion firmware 1.12 or later, is on, close to the phone and not connected to another app, and that Roadstr has the Nearby devices permission. Roadstr says “firmware too old” when the radio does not know channel datagrams. The full checklist is in the specification.

Reporting a bug

Open an issue with: the Roadstr version, your Android version and phone model, what you did, and what you expected. Do not paste private keys, bunker:// links, wallet URIs or exact home addresses.

Clone this wiki locally