Opened 6 years ago

Last modified 15 months ago

#1101 new defect/bug

navit not retouting after change of vehicle (when no gps fix is available)

Reported by: ah be Owned by: cp15
Priority: major Milestone: version 0.5.2
Component: port/android Version: git master
Severity: Keywords: android, routing, input


on my archos g9 running android ics navit will route nicely with the default vehicle (eg car) but if I change the vehicle eg to pedestrian the route is not recalculated but sticks with the first type of vehicle, even if I then change the initial end position. this bug only occurs if navit has no gps fix (!!!), so eg you are sitting indoor and want to check what routes are possible.

Change History (4)

comment:1 Changed 6 years ago by usul

  • Component changed from core to port/android
  • Keywords android routing input added
  • Milestone set to version 0.5.1
  • Owner changed from KaZeR to cp15

So please tell me if I understand this issue correctly?

  • keep GPS disabled
  • launch Navit
  • set a target -> get a route
  • switch your routing vehicle -> no update of the route or switch of routing criterias

Please tell us what version did you use exactly and where you get it from,too.

comment:2 Changed 6 years ago by ah be

yes, what you describe is my problem. It is not android related though as I figured out: I tried the following with the latest .tar.gz version:

turn on gps (but no fix yet)
set vehicle to car-fastest
choose destination
choose position

->>->> routing takes place
set vehicle to car-shortest
--X--X no rerouting

this is very limiting if you want to plan routes (where you do not need a gps fix for as you have to restart navit each time to calculate routes for different vehicle setups.



comment:3 Changed 6 years ago by ah be

  • Summary changed from android not retouting after change of vehicle to navit not retouting after change of vehicle (when no gps fix is available)

comment:4 Changed 15 months ago by

  • Milestone changed from version 0.5.1 to version 0.5.2

This ticket was pushed back in order to bring 0.5.1 out soon.

Note: See TracTickets for help on using tickets.