Difference between revisions of "Maemo"

From Navit's Wiki
Jump to: navigation, search
m (Configuration options)
m (Configuration options)
Line 45: Line 45:
 
* Navit offers several GUIs. If you are not pleased with the GTK GUI, maybe you want to use the "internal" GUI. You can switch it on via the navit.xml configuration file.
 
* Navit offers several GUIs. If you are not pleased with the GTK GUI, maybe you want to use the "internal" GUI. You can switch it on via the navit.xml configuration file.
  
The n810 for driving is best used with the internal GUI. it is note entirely obvious how to configure the display. Here are the settings I use:
+
The n810 for driving is best used with the internal GUI. it is note entirely obvious how to configure the OSD options required to show information. Here are the settings I use:
 
         <gui type="internal" />  
 
         <gui type="internal" />  
 
         <osd enabled="yes" type="compass"/>
 
         <osd enabled="yes" type="compass"/>

Revision as of 20:57, 19 January 2009

Installing Navit on the Nokia n770/n800/n810

General instructions

  1. Install Navit. There's a Maemo project which provides some (currently rather dated) binaries. Alternatively, there are some "bleeding edge" binaries available in the download section.
  2. Get maps. It is possible to use Garmin maps, but maps of openstreetmap, a wiki like world map, also should do a good job. There are several sources where you can download Navit maps based on openstreetmap data. Save them anywhere on your device, e.g. somewhere on the flash memory.
  3. Configure Navit. Search for the file navit.xml as superuser root. Replace the path to the map file to fit your device and configuration:
<mapset enabled="yes">
<map type="binfile" enabled="yes" data="/media/mmc2/map/planet.bin"/>
</mapset>

Compiling Navit from source

Developers may need to compile the source within the scratchbox environment, which currently (2008-12-20) will not compile out of the box. You need to have Scratchbox and the Nokia SDK installed. Place the source inside the scratchbox environment, log in to scratchbox, cd to the source directory and execute the following commands:

./autogen.sh
./configure --disable-binding-python --disable-gui-sdl --disable-samplemap --enable-avoid-float --enable-avoid-unaligned
make
make install

Others have used slightly different options for configure:

./configure --prefix=/home/user/navit --disable-garmin --disable-samplemap --disable-hildon --disable-binding-python --disable-graphics-sdl --disable-gui-sdl --disable-postgresql --disable-svg2png
./configure -q -disable-binding-python -disable-gui-sdl -disable-samplemap -enable-avoid-float -enable-avoid-unaligned -prefix=/usr

If you are using SDK 4.1.1, then you will see errors from autogen. Those can be resolved by setting

SBOX_DEFAULT_AUTOMAKE=1.9;export SBOX_DEFAULT_AUTOMAKE.

As of SVN 1843, --enable-hildon is no longer required. Configure auto-detects that you are building for Maemo.

As of SVN 1843 you should get libgpsbt-dev before compiling. Execute fakeroot apt-get install libgpsbt-dev in scratchbox.

A debian directory is available so that you can build your own packages. Download and unpack in your top Navit source directory. Build a .deb file by using 'fakeroot ./debian/rules binary'. The .deb file will appear in the directory above where you are.

BTW: The Hildon support seems not to be that perfect yet. Presently it consists only of +,- and full screen buttonns plus gpsd autostart.

Configuration options

  • Navit offers several GUIs. If you are not pleased with the GTK GUI, maybe you want to use the "internal" GUI. You can switch it on via the navit.xml configuration file.

The n810 for driving is best used with the internal GUI. it is note entirely obvious how to configure the OSD options required to show information. Here are the settings I use:

       <gui type="internal" /> 
       <osd enabled="yes" type="compass"/>
       <osd enabled="yes" type="vehicle_gps_satnum" x="20" y="110" font_size="450" w="50" h="50"/> 
       <osd enabled="yes" type="vehicle_speed" x="360" y="10" font_size="650" w="80" h="80" />
       <osd enabled="yes" type="eta" x="-200" y="10" font_size="650" w="180" h="80"/> 
       <osd enabled="yes" type="navigation_distance_to_target"  x="-200" y="100" font_size="650" w="180" h="80"/> 
       <osd enabled="yes" type="navigation_next_street_name" x="100" y="430"  font_size="650" w="600" h="50"/> 
       <osd enabled="yes" type="street_name" x="100" y="370"  font_size="650" w="600" h="50"/> 
       <osd enabled="yes" type="navigation_distance_to_next" x="-200" y="190" font_size="650" w="180" h="80"/> 
       <osd enabled="yes" type="navigation_next_turn" x="-200" y="280" font_size="650" w="180" h="80"/> 
       <osd enabled="yes" type="button" x="0" y="-300" command="gui_internal_fullscreen" src="toggle_fullscreen.xpm"/> 
       <osd enabled="no"  type="button" x="-96" y="0" command="gui_internal_menu" src="menu.xpm"/>
       <osd enabled="yes" type="button" x="0" y="-196" command="zoom_in" src="zoom_in.xpm"/>
       <osd enabled="yes" type="button" x="0" y="-96" command="zoom_out" src="zoom_out.xpm"/> 

The important settings are w (width) and h (height) which allow you to set the boxes big enough to then use a large font. I'm using 650 point to be able to comfortably read the information whilst I'm driving. Also this layout only looks right full screen.

NOTE: not all of the above OSD settings actually work for me. They display boxes because the internal_gui does actually know about these options. However I get no information for vehicle_gps_satnum, vehicle_speed, street_name & navigation_next_street_name.

I'll try to update this when I figure out new settings, and keep it showing a reasonable setup for the n810

---Daniel Would

  • It is possible to make Navit recording and displaying a track. First let Navit record the track in the vehicle section, then add the resulting file to the mapset section:
<log type="textfile" data="/home/user/.navit/tracks/ActiveLog.txt" flush_size="1000" overwrite="30" />
...
<map type="textfile" enabled="yes" data="/home/user/.navit/tracks/ActiveLog.txt"/>

Using Navit

If everything went fine, Navit can be started from the menu and you should see the map on the display. In the upper panel of the tablet, you should see a satellite icon with a green tail, indicating that your device has a GPS fix. If so, Navit should show your current position on the map.

Starting GPSd manually

Navit does not necessarily start the GPS subsystem (driver and gpsd) on the Tablet. Therefore you need to do this by starting another application (Map, Gpxview) which is capable of starting it. This "helper application" needs to run as long as you want to use Navit.

As of SVN 1843 (Dec 19, 2008) Navit for N800 will autostart gpsd if your GPS BT receiver is on. For N810 this will work witht he internal GPS receiver as well.

Starting GPSd automatically

Some additional details (Nov 28, 2008): I spent an evening getting Navit working on my N800, here are what else you need to do on Diablo with a Bluetooth GPS

  1. Install bluez-utils-test, have to get this from a Chinook repository for now
  2. Follow the instructions here [1]
  3. Change your navit.xml vehicle definition to use file:/dev/rfcomm0 instead of gpsd

Now each time you start Navit, the GPS connection gets made for you. This avoids workarounds such as starting Map or gpsview.

As of SVN 1843 (Dec 19, 2008) Navit for N8x0 will autostart gpsd for you. But the info above might be of use so I left it here.

Notes