Trouble with track navigation

[twil69]

There are lots of matches for "track" and "navigation" here, but none seems to quite fit my problem.
Which is: I want to use the polygon-based navigation that should work for tracks without embedded navigation instructions - but can't get it to work

I recall that I had it once working, but now, after changes in Locus version, Android version and device, its gone.
I don't expect this method to be 100% perfect for e.g. forks with a small angle, but at least one would expect it to work for a rectangular turn, right?. I  simply don't get a notification tone when I approach the next track point or when there is a significant change in direction. I set up strict routing, notify every point etc. - nothing, zero, niente, nada, nitschewo.
Recently I was really fed up: I spent some effort to create a nice trail running track on small pathes with many turns. Relying on appropriate notifications I set out to follow it with my headphones on (as I need my eyes on the path and not on the display). But Locus wasn't of any help here because it simply remained silent and thus spoiled the entire run. I had a similar experience with a mountainbiking trip before, which was not as bad as I had the phone mounted to the bike and had visual control of the track.
Any help on this one is appreciated because this really reduces Locus' value for me drastically. If I cannot resolve it I may need to seek another solution. But I cannot believe that Locus cant do this - I guess I am rather too dumb to find the right settings.

[Andrew Heard]

My comment here does not address your overall issue, but it could help a little with your testing. Instead of having to test "in-the-field" you can just disable the GPS - tap the GPS icon/button then tap the GPS circle to turn off; then you start your navigation from your armchair and slowly drag/pan the map around as required to simulate your changing GPS position. When the notifications are working properly, as you move over each turn, the appropriate voice will be heard and the display updated (next turn, distance, etc.).

[Michal]

Hi,

I would check these settings:
- settings > navigation > voice (watch for TTS - it doesn't have to be functional for all languages - testing recommended)
- settings > navigation > advanced > strict route navigation OFF (if you miss some of the points due to e.g. poor GPS signal, navigation will direct you to the missed point and won't continue in navigating along the route)
- navigation > advanced >number of commands > medium or high (depends what you need)

If you prefer guidance along a track, check following:
- settings > guidance > set next trackpoint distance
- _"_ > set notification of the next direction change ON > set sound/beep/TTS...
- _"_ > advanced > strict route guidance OFF, number of alerts medium or high, notify on every trackpoint OFF

If all this is done and voice or alerts don't work, send me GPX of your route at pr@asamm.com I'll test it

[twil69]

Thanks for your input and suggestions, guys.
I'll will gradually work through it and come back with the results.

[twil69]

My comment here does not address your overall issue, but it could help a little with your testing. Instead of having to test "in-the-field" you can just disable the GPS - tap the GPS icon/button then tap the GPS circle to turn off; then you start your navigation from your armchair ...

Now this was an useful hint 
I was not aware that it is that easy. Always thought I will need something like FakeGPS for this type of dry run - which I considered too cumbersome for using it with this problem.

First test results
1. Observation:
I can see that guiding switches to the next trackpoint before I get a proximity notification.
Well, this makes sense if I consider that the "proximity distance" parameter is set to 30m and the "switching distance" parameter to 80m. On the other hand: the behavior I want is that I will get a 2-beep notification if I approach a track point and after that guiding shall pick the next point, which usually is further away than the track point I just passed. What are proposed settings here?

2. Observation:
There are absolutely no notifications of direction changes. Example: I approach one point before a  crossing and the next point is right of the crossing. Guiding will change to this next point and displays me a bearing line to it. But I dont get a notification that I have to turn right. Changing the number of commands doe not change anything.

3. Observation:
I see guiding picking the next point based on the settings, e.g. 30m. But there is no proximity notification when I approach this point. Only notification I got was the "off track" vibrations, which I set off for now to ease debugging. This at least indicates, that sound is working in general, but not for all events.

[twil69]

I just noticed that there is a correlation with the track format/origin.
I am using a mixture of recorded tracks, tracks from gpsies and tracks that were created natively with Locus as a result of route planning.
What I can say so far: when I use guiding along a track that was recorded with Locus it works as expected:
I see blue point icons where a direction change will be reported and upon approaching it the configured notification occurs.

For all other formats there seems to be a problem, not sure about the details yet.
One thing that all problematic tracks have in common: I dont see those temporary blue point icons that are visible only during guiding and that indicate direction changes.