Tagged: osm navit maps
July 26, 2011 at 6:12 pm #922
According to this comment
the bug tracker of Navit moved to:
http://trac.navit-project.org/reportJuly 26, 2011 at 6:12 pm #758
Navit 2.0 is out, but the repository still only has 1.0. Also, the website has changed.
July 26, 2011 at 6:27 pm #759
- This reply was modified 4 years, 11 months ago by daithib8. Reason: changed title
I take that back, it is downloading 2.0, but it says 1.0, that should be updated.June 3, 2012 at 3:20 pm #2051
The current version here is old and has buggy version information.
says it’s version 1.0. However, the downloaded version says it’s 0.2.0 (in app about). I’m not aware that a version 1.0 exists at all.
However, version 0.5.0 exists (svn 4***) and is a huge usability improvement over the current version on f-droid.org. Please update.
Infos can be found on: http://wiki.navit-project.org/index.php/Navit_on_Android
Ask for details via firstname.lastname@example.org
Disclamer: I’m just a user who wanted to use navit from f-droid.org.November 13, 2012 at 1:57 pm #5170
Disabled. The build has simplified, using cmake, but I can’t find AndroidManifest. Our build setup always runs $ ant release at the end, so we would need to remove that command from the makefile. Also current version is inscrutable.March 26, 2013 at 10:39 am #6577
Category:Travel & Local
Summary:Navit is an open source turn-by-turn car navigation software.
Navit is an open source (GPL) turn-by-turn car navigation software for Linux, Windows systems and portable devices.
supports offline vector maps from different providers
display 2.5D bird view
customizable routing profiles
adress and POI search
spoken commands via TTS support
easy to extend and embedd
Nightly builds are available for android too:
It’s THE free alternative to gmaps, as it can eat, but not only, maps from OpenStreetMap.
Thanks for all the great FOSS apps!
M.March 26, 2013 at 12:01 pm #6581
Navit is almost unusable. Osmand+ is a good alternative. With its nativ GUI it is much more userfriendly and quite powerful. Osmand+ is already in F-Droid (unfortunately an old version). A new version can be obtained here: http://download.osmand.net/latest-night-build/ (the default versions are those with many limitations). Osmand also uses OpenStreetMaps. Their website is here: http://osmand.net/
You can also vote for new features.March 26, 2013 at 1:22 pm #6582
I’ve spent time trying to build it both with cmake (the preferred method) and autotools, but to no result. But hopefully the recipe can be fixed. The market apk hasn’t been updated since last August, yet there is plenty of activity.July 3, 2013 at 1:36 pm #7771
Hi, this is Usul and I’m comming over from the Navit team 🙂
I was already in contact at IRC and some pointed out, that you had troubles in building the Android port. We like to offer our help to assist you on this work.
As I’m personally currently not that familar with all details of the build process, maybe it would be wise to move the discussion over to the navit forums to avoid any man-in-the-middle communication and to get in contact with the right people:
Would be great, as we currently plan a new release and are very interested in feedback. If here is somebody willing to asisst us on development with a focus on Android, you are very welcome, too!
You are right Osmand+ has a farely better UI and was designed with usability in mind.
But to be fair, you might remember, that Navit is a mature candidate (2005) and started long time ago bevor anybody thought about things like OSM or even smartphones. Our focus is a widely native support on a lot mobile platforms and Android came up very lately. Currently our team is pretty small, so we can’t offer solutions within minutes. But what I can say, the components are quiet powerfull and it’s very easy to alter a lot of things in navit, without getting in touch with the sourcecode.
I can’t promise anything, but I’m optimistic, that the tool will get better step by step 🙂July 3, 2013 at 1:51 pm #7772
We already have a work in progress which can be found here: http://gitorious.org/f-droid/fdroiddata/blobs/master/metadata/org.navitproject.navit.txt. The f-droid manual at http://f-droid.org/manual helps with understanding what each thing means. I wrote the metadata but I’m not very familiar with cmake and I don’t have a lot of time so I hope somebody else can pick it up.July 3, 2013 at 8:13 pm #7782
@usul: That was also my impression, components in background seemed powerful. I doubt that Navit will ever make it on Android without native GUI. Age is no excuse for software. 😉 And don’t get me wrong, I like your efforts to make good software. How about to merge the best of OSMAnd and Navit and work in one team?July 3, 2013 at 8:16 pm #7783
And of course we all like to see your latest version in F-Droid. The more apps we have the better it is.July 4, 2013 at 10:01 am #7791
@daithib8 No problems, thanks for your hints, I will try to attract somebody that will help you to create/update the metadata. Currently we look for sombody experienced with Android, OSM, Navigation who can disburden our maintainer. As also some others had problems to compile the Android port, we might need to improve our docs:
@alterechtschreibung I don’t understand your opinion as a general negativ critic on our project 🙂
As I pointed out, Android is not in our main focus (as Osmand does), but to offer a flexible offline navigation tool for many platforms, esp. on Linux. Because you can have free hardware, free operating systems and free geodata, there is a lack on a solution to allow to use all that together to allow users to route along their environment. I already pointed out, that we currently have not the manpower to offer all the features to the android build, which it deserves as one of the major platforms. As Navit is highly modular, you can embedd only the engine and create a completely native UI. There is the ZAnavi fork, that tries to put the focus more on Android, but is not created by the main dev team.
I don’t think that Osmand and Navit can be merged, as they have completely different codebase (and maybe slightly different mission statements). What I wish would be more exchange with others that work on OSM navigation solutions, but currently we have enough todos on improving our own internal communication. Active external communication will be next, esp. if we get more contributors and a better workballance.
But this is getting more and more offtopic, so if you like, we can continue this discussion at other places…July 9, 2013 at 3:21 pm #7852
So Usul was successfull and i got myself into building the current SVN Revision (5532) with F-Droid and had success with this metafile:
Category:Navigation License:GPLv2 Web Site:http://www.navit-project.org Source Code:http://navit.svn.sourceforge.net/viewvc/navit Issue Tracker:http://trac.navit-project.org/ Summary:Car navigation system Description: It's modular design is capable of using vector maps of various formats for routing and rendering of the displayed map. It's even possible to use multiple maps at a time. The routing engine not only calculates an optimal route to your destination, but also generates directions and even speaks to you. Navit currently speaks 27 languages. You can help translating via the web-based: [http://translations.launchpad.net/navit/trunk/+pots/navit translation page]. . #http://wiki.navit-project.org/index.php/Android_Development #apks at http://download.navit-project.org/navit Repo Type:svn #Don't clone into navit/trunk/navit to leave space for dir required by cmake Repo:https://navit.svn.sourceforge.net/svnroot/navit/trunk Build Version:5532,5532,5532,\ novcheck=yes,\ update=no,\ build=sed -i 's/cd android && ant debug/cd android/g' navit/navit/Makefile.am && \ sed -i 's/cd android && ant release/cd android/g' navit/navit/Makefile.am && \ mkdir android-build && \ cd android-build/ && \ cmake -DCMAKE_TOOLCHAIN_FILE=../navit/Toolchain/arm-eabi.cmake -DANDROID_API_VERSION=8 -DDISABLE_QT=true ../navit && \ make && \ make apkg && \ cd .. && \ ln -s android-build/navit/android/* .
One disadvantage of this File is, that it messes up the build directory due to the symlinking in the last build step. The symlinking is neccessary since F-Droid will look for the build.xml file in the subdir path which cannot be set to a different location, because it has to exist before the init command is executed.
This could be circumvented with the following:
antcommand=release -f android-build/navit/android/build.xml
But as it turns out, antcommand will only use the first command (release) and discards the rest.
I hope this helps you a little bit, daithib8.
The last tagged release (0-2-0) revision 3708 will not build with this file, but i can not get it to build by hand either.July 9, 2013 at 11:35 pm #7853
The following steps actually do nothing, as Makefile.am is part of autotools build process and is not used by cmake.
sed -i 's/cd android && ant debug/cd android/g' navit/navit/Makefile.am && \ sed -i 's/cd android && ant release/cd android/g' navit/navit/Makefile.am && \
During cmake builds, we do not run ant automatically for the “all” target. It’s rather called while building special targets “apkg” and “apkg-release”. So there’s no need to mangle with that sed magic at all, just replace “make apkg” call with “make android_resources” if you do not want ant to be called.
Another problem, sourceforge has recently changed our repository path to svn://svn.code.sf.net/p/navit/code/trunk , old one https://navit.svn.sourceforge.net/svnroot/navit/trunk is still online but is not updated anymore.
Building svn revision 3708 does not worth it, as it is too ancient to have current bugs^H^H^H^H features.
So I see following metafile to be working:
Category:Navigation License:GPLv2 Web Site:http://www.navit-project.org Source Code:http://sourceforge.net/p/navit/code Issue Tracker:http://trac.navit-project.org/ Summary:Car navigation system Description: It's modular design is capable of using vector maps of various formats for routing and rendering of the displayed map. It's even possible to use multiple maps at a time. The routing engine not only calculates an optimal route to your destination, but also generates directions and even speaks to you. Navit currently speaks 27 languages. You can help translating via the web-based: [http://translations.launchpad.net/navit/trunk/+pots/navit translation page]. . #http://wiki.navit-project.org/index.php/Android_Development #apks at http://download.navit-project.org/navit Repo Type:svn #Don't clone into navit/trunk/navit to leave space for dir required by cmake Repo:svn://svn.code.sf.net/p/navit/code/trunk Build Version:5543,5543,5543,\ novcheck=yes,\ update=no,\ build=mkdir android-build && \ cd android-build/ && \ cmake -DCMAKE_TOOLCHAIN_FILE=../navit/Toolchain/arm-eabi.cmake -DANDROID_API_VERSION=8 -DDISABLE_QT=true ../navit && \ make && \ make android_resources && \ cd .. && \ ln -s android-build/navit/android/* .
The forum ‘Submissions Complete’ is closed to new topics and replies.