Difference between revisions of "Maemo"

From Navit's Wiki
Jump to: navigation, search
m (few code and formatting fixes)
(Notes)
Line 143: Line 143:
  
 
=== Notes ===
 
=== Notes ===
* The navit project now has a project page on the maemo garage site, https://garage.maemo.org/projects/navit/.
+
* The navit project now has a project page on the maemo garage site, https://garage.maemo.org/projects/navit/. But we are considering discontinuing this as it duplicates most or all of what this wiki is about.
* The first binary version of navit for the Internet Tablets was created on another site, http://www.tecdencia.net/navit/. This is a dead project and the author doesn't respond to any emails. Unfortunately the Maemo.org version of Navit is misleadingly out-of-date.
+
* The first binary version of navit for the Internet Tablets was created on another site, http://www.tecdencia.net/navit/.  
 +
* We (dwould, gerritv) are now one of the admins for http://maemo.org/downloads/product/OS2008/navit/. In the 2 hours since this was activated for Click To Install from the daily SVN, there were already 7 downloads!

Revision as of 04:44, 6 February 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>

A better option for the N8x0 is to copy the navit.xml file into your /user/home/.navit directory. Tehn you can edit using XTerm (and don't need to be root).

Compiling Navit from source

Developers may need to compile the source within the scratchbox environment. You need to have Scratchbox and the Nokia SDK installed. These are freely available from MaemoPlace the source inside the scratchbox environment, log in to scratchbox, cd to the source directory and execute the following commands:

export SBOX_DEFAULT_AUTOMAKE=1.9
./autogen.sh
./configure --prefix=/usr --disable-binding-python --disable-gui-sdl --enable-avoid-float --enable-avoid-unaligned --enable-svg2png-scaling-flag="32 48" --enable-svg2png-scaling-nav="8 16 32 48"
make
make install

If you don't want/need the sample map then add --disable-samplemap to the above command.

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

The above will build Navit along with pre-scaled icons. Prescaling the icons is known to greatly improve rendering of the gui/internal displays.

navit/xpm/navit_svg2png uses ksvg2png to pre-build the icons. If you don't have kde installed (which you wouldn't have inside scratchbox) then you will need to install librsvg2. Execute fakeroot apt-get librsvg2 in scratchbox. The Makefile in navit/xpm will automatically use one of rsvg-convert, ksvg2png or Inkscape, depending on which is installed in your development environment.

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. This works best after you have done at least one build using the full set of commands above.

To install librsvg2 inside Scratchbox require you to get the source code and install from there. I obtained mine from the Ubuntu sources. Unpack the directory and then do the usual ./configure && fakeroot make install inside Scratchbox. You need to do this ./configure && fakeroot make install for each Scratchbox target that you want to build with. This same process applies to other tools that you want to add the Scratchbox, e.g. ddd (symbolic debugger), splint (code checker), etc.

--Gerritv 05:53, 4 February 2009 (CET) simplified the build instructions.

BTW: The Hildon support seems not to be that perfect yet. Presently it consists only of +,- and full screen buttons 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 not entirely obvious how to configure the OSD options required to show information. The way to configure navit changed in Navit svn1979 The below is an example of laying out the information on an n810

      <osd enabled="yes" type="text" label="${vehicle.position_speed}" x="5" y="130" font_size="600" w="160" h="35" align="4" background_color="#a60c0f88"/>
      <osd enabled="yes" type="text" label="ETA: ${navigation.item.destination_time[arrival]}" x="5" y="-220" font_size="500" w="170" h="30" align="4" background_color="#a60c0f88"/> 
      <osd enabled="yes" type="text" label="Left to Go" x="5" y="-185" font_size="400" w="170" h="30" align="4" background_color="#a60c0f88"/>
      <osd enabled="yes" type="text" label="${navigation.item.destination_length[named]}" x="5" y="-150" font_size="400" w="170" h="30" align="4" background_color="#a60c0f88"/>
      <osd enabled="yes" type="text" label="${navigation.item.destination_time[remaining]}" x="5" y="-115" font_size="400" w="170" h="30" align="4" background_color="#a60c0f88"/>
      <osd enabled="yes" type="text" label="In ${navigation.item[1].length[named]} " x="5" y="-40" font_size="550" w="235" h="35" align="4" background_color="#a60c0f88"/> 
      <osd enabled="yes" type="navigation_next_turn" x="245" y="-45" font_size="500" w="80" h="60" background_color="#a60c0f88"/>  
      <osd enabled="yes" type="text" label="onto ${navigation.item[1].street_name}" x="310" y="-40"  font_size="550" w="485" h="35" align="4" background_color="#a60c0f88"/>
      <osd enabled="yes" type="text" label="${navigation.item.street_name} Max:${tracking.item.route_speed}" x="10" y="5" align="0" background_color="#a60c0f88" font_size="550" w="700" h="40"/> 	
      <osd enabled="yes"  type="button" x="-80" y="60" command="zoom_in()" src="gui_zoom_in.png"/>
      <osd enabled="yes"  type="button" x="-80" y="180" command="zoom_out()" src="gui_zoom_out.png"/> 
      <osd enabled="yes"  type="button" x="-80" y="280" command="gui.fullscreen()" src="gui_fullscreen.png"/>
      <osd enabled="no" type="speed_warner" x="-60" y="180" w="60" h="60"/> 
      <osd enabled="no" type="button" x="0" y="0" command="gui.menu()" src="menu.xpm"/>




gives: Screenshot-2009-02-04-22-04-43.png

Note the above linewraps are added to make it display nicely, but you'll want each osd items as a single line in the navit.xml file 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 550 point to be able to comfortably read the information whilst I'm driving. Also this layout only looks right full screen.

The new style has type="text" which are effectively free text fields that understand \n for newline and a number of variables which get switched for information values. eg ${navigation.item.destination_time[arrival]} shows the time at which you are expected to arrive at destination. All the text is added for my own preference as a first pass. Please add additional layout variations that you'd like to share.

To make updating this item easier, and maybe sharing different OSD setups easier you can replace the OSD entries in navit.xml with:

       <xi:include href="/home/user/.navit/navitOSD.xml"/>

Then you can create a new file navitOSD.xml in which you place all the OSD items. This means you can create and share layouts by providing just the navitOSD.xml file and people can drop them into place without having to hand edit their navit.xml files. The same trick will work for any subset part of the navit.xml file

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

---Daniel Would

Here's another option with each item in its' own text box. The layout also works without overlaping when in windowed mode.

<osd enabled="yes" type="compass" x="5" y="5" font_size="250" w="60" h="62" background_color="#48852faf"/>
<osd enabled="yes" type="gps_status" x="70" y="5" w="50" h="40" background_color="#48852faf"/>
<osd enabled="yes" type="text" label="${vehicle.position_sats_signal}/${vehicle.position_qual}" x="70" y="45" font_size="300" w="50" h="22" align="0" background_color="#48852faf"/>
<osd enabled="yes" type="text" label="${vehicle.position_speed}" x="5" y="72" font_size="400" w="115" h="35" align="4" background_color="#48852faf"/>
<osd enabled="yes" type="text" label="ETA: ${navigation.item.destination_time[arrival]}" x="5" y="-220" font_size="400" w="170" h="30" align="4" background_color="#1a6ad780"/>
<osd enabled="yes" type="text" label="Left to Go" x="5" y="-185" font_size="400" w="170" h="30" align="4" background_color="#1a6ad780"/>
<osd enabled="yes" type="text" label="${navigation.item.destination_length[named]}" x="5" y="-150" font_size="400" w="170" h="30" align="4" background_color="#1a6ad780"/>
<osd enabled="yes" type="text" label="${navigation.item.destination_time[remaining]}" x="5" y="-115" font_size="400" w="170" h="30" align="4" background_color="#1a6ad780"/>
<osd enabled="yes" type="text" label="In ${navigation.item[1].length[named]} " x="5" y="-40" font_size="500" w="235" h="35" align="4" background_color="#000000c8"/>
<osd enabled="yes" type="navigation_next_turn" x="245" y="-45" font_size="500" w="60" h="40" background_color="#000000c8"/>
<osd enabled="yes" type="text" label="onto ${navigation.item[1].street_name}" x="310" y="-40"  font_size="500" w="485" h="35" align="4" background_color="#000000c8"/>
<osd enabled="yes" type="text" label="${navigation.item.street_name}" x="150" y="5"  font_size="500" w="500" h="35" align="0" background_color="#ff71004b"/> 
<osd enabled="yes" type="button" x="-60" y="0" command="zoom_in()" src="gui_zoom_in.png"/>
<osd enabled="yes" type="toggle_announcer" x="-65" y="95" w="60" h="60" background_color="#1a6ad700"/>
<osd enabled="yes" type="button" x="-60" y="200" command="gui.fullscreen()" src="gui_fullscreen.png"/>
<osd enabled="yes" type="button" x="-60" y="-105" command="zoom_out()" src="gui_zoom_out.png"/> 

gives:Osd2.png

This gives a nice display with (to me) similar information grouped by color. However, the text can be difficult to read, so I have changed all the background colors to 000000c8. Very readable and still slightly transparent.

The speaker icon is to toggle the announcer on/off (color is 00000000, transparent), but isn't working at this time.

I am also using some changes suggested by Daniel Would which change the navigation to same size as the street, and place the blue line on top of the street.

---lemmyslender



  • 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 with the 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]

As of SVN 1843 (Dec 19, 2008) Navit for N8x0 will autostart gpsd for you, at least on the device itself. If you are running Navit under Scratchbox then you will need to get gps data from somewhere. On the ARMEL target, there does not seem to be a way to connect to gpsd running elsewhere. If running under the X86 target, running gpsd under your native OS will allow gps data to get to Navit.

Notes