Opened 12 years ago

Closed 12 years ago

#732 closed defect/bug (duplicate)

startup on wrong location (from xml file?)

Reported by: zoff99 Owned by: KaZeR
Priority: major Milestone:
Component: core Version: git master
Severity: Keywords: location, startup


major bug (in SVN 3861) in android version: ===========================================

now navit starts at some strange location (probably from xml file) and it takes very long to get a fix indoors. it should really start from the last known fix location (which should be saved regulary, or at least on shutdown)

Change History (5)

comment:1 Changed 12 years ago by tegzed

Hi Zoff99,

This is really the way it should work and on my ubuntu box it seems to be ok. I see in the source that the map center position is loaded from "center.txt" in the navit data dir on init and saved to that file on exit. Do you have that file on your device, if so what is the content, what is the access time of that file? Maybe you have an unclean shutdown and that file is not written.

comment:2 Changed 12 years ago by zoff99

i have a center.txt but the coords are in navit format :-( which i can not understand easy. it starts somehwere in africa

comment:3 Changed 12 years ago by tegzed

You can also check the access time of that file after closing navit. Is it the same as the time of exit from navit? If so are you sure navit got your coordinates from you device(ie the vehicle is configured successfully)? You can also try the demo vehicle to check if it's a problem with your vehicle(gps) settings.

comment:4 Changed 12 years ago by sanderd17

I don't have that problem on android, it doesn't take longer for navit than for other apps like google maps.

could it be that is related to this? e.g. that google thinks your network is in africa?

comment:5 Changed 12 years ago by zoff99

  • Resolution set to duplicate
  • Status changed from new to closed

i think its the same bug as:

Note: See TracTickets for help on using tickets.