Third test while trail running with smartphone in my hand. Guiding works!
Today i set "numbers of alerts" to "low" and "missed" some junctions - not really missed 'cause i know the way. After running i created a copy of the track with commands (attached) and had a look into it.
I noticed that some waypoint are wrong or unnecessary and makes me wired.
Wrong means = i.e. "keep right" in front of a junctions, but the right command should be "straight on" or nothing. (see wrong_1) i.e. @ 48.039008°N, 11.378582°O .
Wrong means also = miss two commands on path on a junction going short right and than left. After this situation there is a command "keep left"

(see wrong_2) i.e. @ 48.034783°N, 11.364872°O
Unneccesary means = Path is going quite straight and w/o any junctions, but commands are generated.(see unnecessary_3) i.e. @ 48.034560°N, 11.367620°O
If i'm guided "by display" i'm not worried about this, guided by sounds only will directly lead into serious errors.
So it needs still a little bit of tuning.
All waypoints created by Locus for commands had a wrong create time stamp = 1970-01-01 01:00:00. (The scary timestamp monster is crawling through the database again

)