[APP] - version 3.18.x (27. 6. 2016+)

[Andrew Heard]

Using 3.18.9.6 for navigation I found the usual magenta line was not being displayed. I've never seen this before.


I then swapped to 3.18.0 Pro & restarted navigation, and the normal magenta navigation line was displayed properly.


I then swapped back to 3.18.9.6 & restarted navigation again. Same problem - invisible navigation line. But maybe 10 minutes later I found that the magenta navigation line was again displayed.

Unlike 0709 I didn't find any other problems with navigation. I also performed same navigation with GPS disabled and normal magenta navigation line was displayed properly. Weird.

[0709]

05-10-2016
Trackrecord by phone THL 4000 (GPS).  Using Locus Beta V 3.18.9.6 and Locus PRO  V 3.18.9

Track segment 1:  "Navigate to" by Beta AND track record by Beta. "Navigate" result unstable/unreliable !
Track segment 2:  "Navigate to" by Beta AND track record by the PRO version. "Navigate" result stable/reliable.
Track segment 3.  "Navigate to" by Beta AND track record by Beta.  "Navigate " result unstable/unreliable !

A double check recording was made by Locus V 3.18.9.5 and  Samsung tablet TAB 4  (GPS + GLONASS)

Both track recordings in the attached .zip.

[menion]

@Andrew Heard: hmm line is not on the first screenshot visible completely, so even a thin line on part you already passed is not visible. It may only means that Locus a) considered that track is not visible in current view, b) has any problems with rendering of this line. Never noticed something like this on own device, do you have steps to reproduce it please?

@0709: uff. Willy, please find a while and use for a few minutes [ur=https://nas.asamm.com/share.cgi?ssid=0IgvFm5l]this beta version[/url] I made for you. It may be little slower as it will print out few information into Locus/logs/X.log file. Try to simulate this problem and after a while stop it and send me please latest log(s). Maybe if you enable in Locus settings recording of NMEA messages and send me also this message, it will be useful. Thank you and sorry for a complications. I still have absolutely no idea how may something like this happen.

[Andrew Heard]

@Andrew Heard: hmm line is not on the first screenshot visible completely, so even a thin line on part you already passed is not visible. It may only means that Locus a) considered that track is not visible in current view, b) has any problems with rendering of this line. Never noticed something like this on own device, do you have steps to reproduce it please?

@menion - I've been using navigation for the last year. I can tell when it isn't displaying correctly. I've never noticed it before either, and although I don't have great screen captures sorry or steps to reproduce (yet), but as I said, it rendered perfectly on Pro, but not (at times) with latest Beta, on simple road/ route I use a lot for previous testing over the last year. I will try to reproduce next week

[balloni55]

Navigate to:
arrow on map "keep left" thats ok, but top left icon advice me to go right ?


pofile on/off:
sec 0 > locus profile is switched on and i get direction advices
sec 12 > i switch profil off
sec 19 > recalculate, i get no direction advices only destination is visible
sec 37 > i switch on locus profil
sec 44 > direction advices are back
https://www.dropbox.com/s/x5z791h6r708or0/profil%20on%20off.mp4?dl=0

[menion]

@Andrew Heard: understand, thanks. If you find something that may helps, let me know. Seems that publishing version next week (and not this one) was a good idea. I'll try to get out for some longer testing because of this and as well, because of Willy's (0709) issues. Thanks

@balloni55: if I remember correctly (@poutnikl corrects me), default BRouter profile do not generated navigation commands for a foot profile. Please try it with cycle/car profile if it works correctly. It was also one more reason, why I was in hurry with creating custom settings for BRouter directly in Locus > because many users wrote us that for cycle it works correctly, but for "foot", Locus do not navigate.

[balloni55]

Please try it with cycle/car profile if it works correctly.

work with both thanks
any idea to my question in screenshot?

[0709]

Had a look at my historic records. A first such strange record was at 1/10/2016.
Did not report as I thought this to be a serious hardware phone gps issue.
Back home now. Installed this test .apk Beta version 3.18.9.7.
Had a 11km testdrive. "Navigate to" AND "trackrecord" active.
No problems reported.  Trackrecord attached.
Will do some more test. I keep you informed.

[poutnikl]

@balloni55: if I remember correctly (@poutnikl corrects me), default BRouter profile do not generated navigation commands for a foot profile. Please try it with cycle/car profile if it works correctly. It was also one more reason, why I was in hurry with creating custom settings for BRouter directly in Locus > because many users wrote us that for cycle it works correctly, but for "foot", Locus do not navigate.

Correct, the Brouter default foot profile is Shortest, that is for some reasons about a year old, not updated and not aware of the Brouter navigation instructions. The Hiking/Walking should work fine.

[menion]

@poutnikl thanks!

@balloni55: give me please coordinates so I may try it. There should be no problem in Locus anyway, it will be more a "problem" of routing service (BRouter?).

@0709: I'm glad to hear it. I have no idea how this may happen anyway I made one small change on every possible place that may mess coordinates little bit and seems it helped. Perfect, uff

[balloni55]

give me please coordinates so I may try it.

to get the situation from screenshot
start on
N 48°55.350  E 8°51.880
navigate to
N 48° 54.975  E 8°52.470

[erfi]

@balloni55: Du kannst im profile2-Ordner die Original-shortest.brf gegen die im nachfolgenden Link (Beitrag vom 27.05.16) leicht angepasste Version austauschen. Dann sollte BRouter Anweisungen erzeugen. Ich nutze sie seither mit Erfolg.
http://forum.locusmap.eu/index.php?topic=4064.msg43212#msg43212

@0709, @menion: Habe gestern und heute bei Autofahrten die Locus-Navigation bei gleichzeitiger Trackaufzeichnung getestet. Keine Probleme, alles perfekt!    Locus Beta 3.18.9.6 benutzt.

[balloni55]

@ erfi, thanks works perfect !

[abrensch]

arrow on map "keep left" thats ok, but top left icon advice me to go right ?

It's the other way round: go left but keep right. It's perfectly reasonable to go left but keep right, if there are two close-by choices on the left side. Unfortunatly, a navigation command can only express one aspect so sometimes you have to decide and in a complex situation there are cases where it's confusing

[balloni55]

@ arndt, thanks for your answer i understand what you´ve explained
but in this example it´s only one forest path leading left i have to go
and  not a  multi-lane highway.

I suspect, if i use morse signal with disabeled screen for navigation  i´m lead to the wrong direction