@devrtz has got it. I used navit a fair bit ~10yrs ago, but not a lot since. I only ever tried the OSM-based maps which sometimes led to navigation oddities (ways not joined so they look fine when rendered, but can't be used as a route) but OSM data has improved a lot since then. Navit doesn't seem to have moved on much in the intervening years, but it's still highly configurable IF you're fine editing raw XML configs.
Copy /etc/navit/navit.xml into ~/.navit/ to get a custom config to edit. You'll be editing the raw XML file - I think there was once a 3rd party editor gui for navit configs but i never tried it. The first thing to edit is in the gui section so the display is a sensible size. I've used the fullscreen option, but it's also possible to define the window size. It should look like:
<gui type="internal" enabled="yes" fullscreen="1">
That will hide the top and bottom bars from phosh, but if you touch at the top or bottom of the screen they'll reappear so you can switch apps or whatever. You won't have any map to display yet, so you'll just see a sandy coloured background in the map view. Touch anywhere to get the controls (black background with an icon grid) if you want to experiment.
Next you need to define the maps to use, and download the map data. This is where I hit problems. You'll need a section of config something like:
<mapset enabled="yes">
<map type="binfile" enabled="yes" data="/home/mobian/.navit/maps/osm_england_midlands_20200702.bin"/>
</mapset>
See https://navit.readthedocs.io/en/latest/maps.html for details, including where to get the map data. The problem I've had is that it fails to read the map data, both on Mobian and an Ubuntu desktop. I've tried data both from the online extractor and copied from a working instance of Navit from f-droid, running on an android phone. If you want to chase the problem further you'll need to increase the debug level in the config. It gave a warning about 'eocl wrong' for the map file, which I think is a check on the zip file before extracting the data.
If you get the maps working please let us know how. Beyond that their wiki has examples for things like changing the rendering to look like the usual OSM one, night modes, changing what's on screen and used in the underlying calculations for different navigation profiles (car, cycle, pedestrian etc.) and more. I haven't checked yet whether I still have my old config archived.
Copy /etc/navit/navit.xml into ~/.navit/ to get a custom config to edit. You'll be editing the raw XML file - I think there was once a 3rd party editor gui for navit configs but i never tried it. The first thing to edit is in the gui section so the display is a sensible size. I've used the fullscreen option, but it's also possible to define the window size. It should look like:
<gui type="internal" enabled="yes" fullscreen="1">
That will hide the top and bottom bars from phosh, but if you touch at the top or bottom of the screen they'll reappear so you can switch apps or whatever. You won't have any map to display yet, so you'll just see a sandy coloured background in the map view. Touch anywhere to get the controls (black background with an icon grid) if you want to experiment.
Next you need to define the maps to use, and download the map data. This is where I hit problems. You'll need a section of config something like:
<mapset enabled="yes">
<map type="binfile" enabled="yes" data="/home/mobian/.navit/maps/osm_england_midlands_20200702.bin"/>
</mapset>
See https://navit.readthedocs.io/en/latest/maps.html for details, including where to get the map data. The problem I've had is that it fails to read the map data, both on Mobian and an Ubuntu desktop. I've tried data both from the online extractor and copied from a working instance of Navit from f-droid, running on an android phone. If you want to chase the problem further you'll need to increase the debug level in the config. It gave a warning about 'eocl wrong' for the map file, which I think is a check on the zip file before extracting the data.
If you get the maps working please let us know how. Beyond that their wiki has examples for things like changing the rendering to look like the usual OSM one, night modes, changing what's on screen and used in the underlying calculations for different navigation profiles (car, cycle, pedestrian etc.) and more. I haven't checked yet whether I still have my old config archived.