Opened 13 years ago
Closed 12 years ago
#623 closed defect/bug (fixed)
svn-3506 for maemo (N810/OS2008): not providing directions
Reported by: | gigapus | Owned by: | KaZeR |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | core | Version: | git master |
Severity: | Keywords: | maemo, N810, routing | |
Cc: | http://wiki.navit-project.org/index.php/user:nioui |
Description
Yesterday I upgraded to svn-3506 via the maemo application manager and since then I do not get navigation directions.
After GPS lock, the route is calculated correctly and shown on the map. The OSD gives the first direction, but there is no speech output, and the initial direction is never updated after that (either via OSD or speech).
The map does update to show current location during the trip, and the OSD correctly names the current street, but if I leave the specified route it does not do rerouting.
Basically everything works, except the navigation directions, which behave like I never left my point of origin. No such issues existed prior to the update.
Change History (8)
comment:1 Changed 13 years ago by gigapus
comment:2 Changed 13 years ago by tiiiim
Looks like you're having the same problem as me? See ticket 622: http://trac.navit-project.org/ticket/622
comment:3 Changed 13 years ago by gigapus
That's possible. I saw your ticket, but I was not sure if it was describing the same thing. I think in my case it is navigation.item[1].xxx stuff that is frozen.
comment:4 Changed 13 years ago by nioui
- Cc http://wiki.navit-project.org/index.php/user:nioui added
This seems to be the same issue as http://trac.navit-project.org/ticket/633
Can you try the corresponding patch?
comment:5 Changed 12 years ago by gigapus
If you mean removing code and rebuilding, I do not have the ability to do this (I just use the pre-built maemo package).
comment:6 Changed 12 years ago by noradtux
I was seeing this problem on my Palm Pre port aswell, disabling those lines seems to help.
comment:7 Changed 12 years ago by gigapus
This is working again in svn-3520. Thanks!
comment:8 Changed 12 years ago by kazer
- Resolution set to fixed
- Status changed from new to closed
For what it is worth, last night I reverted to svn-3495 and all these issues went away.