Open GoogleCodeExporter opened 9 years ago
I'm seeing the same but haven't looked into it yet. You might also want to have
a
look at some tickets from navit trac:
http://trac.navit-project.org/ticket/564
http://trac.navit-project.org/ticket/539
http://trac.navit-project.org/ticket/525
to see if one of these is what you're experiencing; symptoms look quite similar.
One mentions a problem with "Map follows vehicle"; navit will work if this
setting is
off.
Original comment by mich...@vonglasow.com
on 21 May 2010 at 11:59
I had a look at the issue with the larger maps which is not the problem as I
can load
>500mb.
the latest version svn 3291 works in loading the maps but crashes once one
tries to
search a location and have it shown on the map.
Is there any way users can add the wiki table about what programs work and what
don't. Another very promising one is Csipsimple (sip client). It is not quite
there
yet but the developer is very much involved in getting it to work.
Original comment by robin.se...@biologie.uni-freiburg.de
on 22 May 2010 at 5:42
I've just done some cross testing; Navit will run fine in the emulator but on a
Freerunner it will crash - it appears the crash occurs as soon as it tries to
display the map. Initially after setup it will run fine, but after waiting for
a GPS fix at a certain point it crashes; without a GPS fix selecting an address
and choosing "View on map" crashes it. So it seems that it's somehow related to
AoF. I'm using RC1 (built 2010-01-30).
Original comment by mich...@vonglasow.com
on 24 Jul 2010 at 8:26
@Robin
Send your upates an what works and doesn't work to the mailing list and the
Wiki table will get updated. Also send any suggestions for apps that you think
are worth adding.
Original comment by hmu...@gmail.com
on 26 Jul 2010 at 9:06
See also
http://trac.navit-project.org/ticket/576
- seems to be the same issue. As long as we can't make out the cause of the
error in either component, I'd suggest keeping both open.
According to my tests with Navit r3490 on AoF Cupcake 0.2.0 RC1 it seems to be
the map display that crashes navit.
There is a slight chance (though highly speculative) that it is in some way
related to #149, but we might want to keep it in mind.
Original comment by mich...@vonglasow.com
on 27 Jul 2010 at 7:01
Having looked at #142 (NDK port), this might explain the error.
Original comment by mich...@vonglasow.com
on 28 Jul 2010 at 6:40
After some research and discussion on the mailing list, NDK issues seem
unlikely as the main difference is the processor generation (default: ARMv5,
Freerunner: ARMv4) and Navit explicitly produces two different versions for
each processor generation.
Logcats indicate a memory issue; Navit gets terminated with signal 11. See
ticket in Navit trac for details.
Original comment by mich...@vonglasow.com
on 4 Sep 2010 at 7:49
Original issue reported on code.google.com by
robin.se...@biologie.uni-freiburg.de
on 20 May 2010 at 5:40