Difference between revisions of "Android"

From Navit's Wiki
Jump to: navigation, search
(Compatible Android devices)
(Compatible Android devices)
Line 130: Line 130:
| Samsung Galaxy S3 mini I8190 || Android 4.1.2 ||class="cell_yes"| osd gps-status doesn't work - otherwise running fine, unless stated otherwise || 5400, 5419, 5422
| Samsung Galaxy S3 mini I8190 || Android 4.1.2 ||class="cell_yes"| osd gps-status doesn't work - otherwise running fine, unless stated otherwise || 5400, 5419, 5422
| Samsung Galaxy SIII I9300|| || class="cell_yes"| running fine || 5000+,
| Samsung Galaxy Spica I5700 ||Samdroid mod || class="cell_yes"| running fine || 4083
| Samsung Galaxy Spica I5700 ||Samdroid mod || class="cell_yes"| running fine || 4083

Revision as of 09:45, 3 July 2013

First run of Navit

Navit is available on Android! Using the Internal GUI, Navit enables complete offline routing anywhere in the world using map data from OpenStreetMap. Note that this is not an Android app in the traditional sense - it is a direct port of Navit (with a couple of extra features for Android), so isn't as integrated with Android as you may expect from other apps - bear this in mind when using it for the first time!


QR code: scan this to get Navit from Google Play

Most users use one of two routes to get Navit onto their Android devices: install from Google Play, or manually install from apk's built nightly from the latest source code. The apk file is also avalable here.

Installing from the Google Play is perhaps the most simple, and allows for automatic updating. Manually installing from an apk means that you have the very latest features built into Navit, but requires you to install and update it yourself

The following table links through to the nightly apk's. Choose the one which best matches your device. The nightly builds are compatible with devices running Froyo (2.2.X) or later.

Compatible devices
ARM v5 ARMv5TE processors, covers most Android devices including: HTC Desire Z, Motorola Defy/Droid/Milestone, Samsung I7500 Galaxy, Samsung Galaxy S2, Samsung Galaxy Spica i5700, Samsung Galaxy S, SE Xperia X10, Xperia X8, LG Optimus Speed (P990)
ARM v4 ARMv4 processors. Devices which require this version include Neo Freerunner (running Android).

Compatible Android devices

The following tables list Android devices on which Navit has been tested. Please consider editing the table for your own device.

Device OS Status Tested on SVN revision
Allview P4 running fine ICS (market)
Archos 5 IT running fine 4383, 4395, 4411
Acer ICONIA TAB A500 running fine; after suspend GPS must be disabled and enabled again (market)
Geeksphone One RCMod 4.0.0 (Gingerbread) Exits on startup (following crash of PicoTTS) unless speech output is disabled, runs fine otherwise 4319
Geeksphone Zero RCMod 7.0.2 (Gingerbread) running fine (market)
Google/LG Nexus 4 Android 4.2.2 running fine, but not possible to change keyboard-layout to the stock-android software-keyboard 4785 (market), 5357-5365
Google/Samsung Galaxy Nexus I9250 Android 4.2.2 running fine, but not possible to change keyboard-layout to the stock-android software-keyboard 4785 (market), 4909-5365
Google/Samsung Nexus S running fine after brief test (market)
Google/Samsung Nexus S RCMod 7.2.0 running fine 5187
Huawei Ideos X3 (U8510) speech synthesis often incomplete 4696
Huawei M860 running fine 4281
HTC Desire CyanogenMod 7.2.0 current status (latest svn version tested) 5543
HTC Desire CyanogenMod 7.2.0 phone reboots if power suspend mode is activated while navit is running 5395-5543
HTC Desire Android 2.2.2 DISCONTINUED - last version testet 5395
HTC Desire Android 2.2.2 osd gps-status doesn't work - otherwise running fine, unless stated below 4200-5395
HTC Desire Android 2.2.2 android installer refuses to install the apk 5389-5392
HTC Desire Android 2.2.2 typing of adresses terminates after 1st letter 5296-5329
HTC Desire Android 2.2.2 display problems while browsing bookmarks 5279
HTC Desire Android 2.2.2 application freezes as soon as route is calculated 5219-5276
HTC Desire Android 2.2.2 crashes during application start 5208
HTC Desire Android 2.2.2 display remains black 5175-5179
HTC Desire Android 2.2.2 application crashes as soon as gps link is established 5149-5174
HTC Desire Android 2.2.2 modifications for osd navigation_next_turn in config file necessary 5078
HTC Desire Android 2.2.2 starts, icon appears in the upper left corner, application stops 4879-4992
HTC Desire HD (Ace) running fine (market)
HTC Desire S running fine 4281 (market)
HTC Desire Z running fine 4281 (market), 4785 (market), 4808
HTC Explorer A310e Android 2.3.5 running fine - but GPS status & texte: label="${vehicle.position_sats_used}/${vehicle.position_qual}" do not work - Route\Height Profile does not work too (black screen) 5126
HTC Hero Android 2.2, cronos running fine (saving bookmaks made it unusable) 4118
HTC Incredible S running fine 4281 (market)
HTC Magic Android 2.3.4 running fine 5224
HTC Sensation Android 4.0.3 running fine 4785 (market)
HTC Wildfire Android 2.2 running fine (theme changes are not saved) 4997
LG Optimus GT540 running fine 4118, 4281 (Google market)
LG Optimus P500 One running fine current market build, 4383, 4446
Motorola Defy running fine 4281 (market), 4352, 4383
Motorola Milestone 2 running fine (market)
Motorola Xoom Android 3.2 running fine (market) → 0.5.0
Neo Freerunner AoF Cupcake 0.2.0 cannot install, adb install returns [INSTALL_FAILED_OLDER_SDK]. Is Cupcake no longer supported? 4376
Neo Freerunner AoF-SD Froyo runs fine; GPS must be started manually 4548
Neo Freerunner AoF-SD Froyo starts, icon in left upper corner, application stops 4833
Samsung GT-I5500 Android 2.1 update1 running fine 0.5.0-3828
Samsung Galaxy Gio GT-S5660 Android 2.2.1 Froyo running fine svn 4663
Samsung Galaxy Gio GT-S5660 Android 2.2.3 running fine svn 4785
Samsung Galaxy Gio GT-S5660 Android 2.3.6 running fine svn 4997
Samsung Galaxy Ace GT-S5830L Android 2.3.4 black screen then crash svn 5214
Samsung Galaxy S I9000 running fine svn 4183, 4229, 4510 - market 0.5.0-4281
Samsung Galaxy S2 I9100 running fine 4940
Samsung Galaxy S3 mini I8190 Android 4.1.2 osd gps-status doesn't work - otherwise running fine, unless stated otherwise 5400, 5419, 5422
Samsung Galaxy SIII I9300 running fine 5000+,
Samsung Galaxy Spica I5700 Samdroid mod running fine 4083
Samsung Galaxy Tab P1000 running fine 4183
Xiaomi One Plus MIUI 2.3.5k running fine; GPS to start manually 0.5.0 4929
Xperia X8 running fine
Xperia X10 running fine  ??
ZTE Blade Orange San Francisco running fine 4155

Useful information

In-app map downloading


There are two ways to get a map into Navit.

  1. Press your device's Menu button, and choose Download first map. Maps will be greater than 50MB, so it's best to turn on your wifi.
  2. Download a map from the Navit Map Extractor, connect your device to your pc, choose Select to copy files to/from your computer on the device and save the downloaded map as navitmap.bin into the navit folder on your device.

Advanced configuration

When Navit starts, a copy of /data/data/org.navitproject.navit/share/navit.xml matching your display resolution is extracted from the apk. If you have root permissions on your device, you can use this file as a starting point for a customized configuration. Otherwise unzip the apk file and use the xml file from the subdirectory res/raw/ which matches the display resolution (ldpi, mdpi or hdpi). You can save your configuration as /sdcard/navit/navit.xml which is then used instead of the one from the data directory.

  • If you'd like to configure the initial view of the map (it should automatically center on your position if the on-board GPS has a fix) change the <navit center=... attribute to your home coordinates.


By default Navit uses the Internal keyboard for menu items which require text input from the user, such as POI search. To use your default Android keyboard instead, just press and hold your device's Menu button until the keyboard pops up.

Launch via Google

When you click on a place in Google Maps, you can choose to navigate to it with Navit (assuming that there isn't already a default navigation app set).

Bookmarks file

The bookmark.txt file is stored on the device at the location


and each line in the file looks like

mg:0x112233 0x445566 type=bookmark label="Home" path="Home"

You will need root access on your device to be able to see this file. An other way without the need of root access is using the Android Debug Bridge. If you installed the Android SDK on your computer, the following command transfers the bookmark.txt file from your device to the current working directory:

adb pull /data/data/org.navitproject.navit/home/bookmark.txt

It is also possible to transfer the changed file back to your device by using adb push. See [1] for a more detailed description of the adb client.

There is another option, which doesn't need your Android device to be rooted, nor ADB. You just need to have SSHDroid installed. Start it and connect to it with ssh (on windows you can use putty) and then do a cd /data/data/org.navitproject.navit/home/ from the comfort of your keyboard equipped machine. You can then read the bookmarks.txt file (if need be just cat it to display, then copy past or whatever, and cat text back into it or what not). Note that you can also get to the right location with terminal apps, so there may be plenty of ways to actually get at this file without root and/or adb.

Get the log for debugging problems

There are two options here:

  • Install the Android SDK, run adb logcat and save the output to a file
  • Install an app like Log Collector and send the data via mail

See also