Messages

@Andrew: hmm I'm almost sure that my small change should have no influence on this. I may disable it, as it's just one line of code, but it really should work without a problem.
EDIT: maybe I've found some weird combination, so next version probably during weekend, thanks

@menion - for my testing/ observation - does 3.17.0.2 beta have this fix?

The Locus 3.17.0.2 beta fixes the issue we are discussing here. Well done Menion.

Yep - 2nd video is exactly my sequence and experience. Thanks 0709 (!) A picture often tells a 1,000 words (although file size for 1,000 words is probably far far smaller than video LOL).

Thanks 0709. That's very interesting that you could go into navigation mode with my long track. To my surprise I could go into navigation mode with your test track 100% reliably too (attached). That now suggests to me the bug has something to do with the imported track. Not much to do with any Locus navigation or guiding settings. @Menion, are you following this discussion?

I have not mentioned any export. Also, BRouter does not generate TCX. Brouter can pass the route to Locus Either as GPX to import, either via Locus navigation API. The latter probably chokes on the hints for now.

@poutnikl - no I am pleased to say that Locus displays the hints (you mean waypoints as navigation commands?) when track generated with BRouter is imported via Locus navigation API.

From the Question mark in top left corner ?

I don't understand your question. Do you mean tap "nearest point" from the Question mark in top left corner? - yes

I note another user has now reported on this experience http://help.locusmap.eu/topic/problem-with-version-3-17 although surprised not more.

After some more walking tests I find that even tapping "nearest point" isn't always 100% reliable. Worked 4 out of 5 times:

Clearly displayed GPS position is within 10m of track, and walking in direction of track, but still Locus doesn't go into navigation mode.

settings: max. allowed deviation:200m, auto-recalc:Never, strict following:off

Any other relevant settings or details I can report?

However you can send me some mistakes and I'll check them.

I think for now it's OK for me. You have done a fantastic job. In fact for me the Offline Address Search + BRouter GPX waypoints are best new features in last year. Thanks.

thanks @menion

"Maximum allowed deviation"

I had default 50m, but I've never modified this setting, I have now set to 200m, but it has not improved the situation

What I see on your first screenshot looks like second option - navigation, but you are too far away from track

how can you tell that? I have position precisely over the displayed track in screenshot?

Do not know how you get into this state yes

easy - I started navigation mode on the GPS position shown in 1st screenshot, with recalculation=Never

button "Nearest point" in navigation menu, do not helps here?

yes - mode switches from from guidance to navigation mode when "Nearest point" is tapped

The central issue seems to be with seting navigation recalculation=Never. In this mode navigation is very unreliable in "locking onto" the start of the track even when I am within few metres of the track as displayed on map. It is quite easy to simulate when GPS is disabled. When the track is simple/ short navigation will start reliably, but as soon as track is more realistic Locus never switches from guidance to navigation mode. Also while in guidance mode the UI is extremely "unresponsive" - using all CPU.

Have attached 2 tracks (short.gpx, long.gpx).

BRouter seems to recognize roundabouts, wow !

Not sure how your comment is related to the topic?

Hi Andrew,  No brouter app installed !

On common paths "nearest point" not always helps to *adjust position on track. How to tell locus exact track position progress on a common trackpath ? = not implemented !  Idea ? By Tap => Navigation Arrow => Open Itenerary list => tap new target navpoint  => opens navpoint on map: IF agree, confirm as next navpoint target ?

@0709 - are you testing with navigation recalculation=Never - that is the central issue for me! If I set recalculation=Route then Locus starts navigation OK, BUT I don't want recalculation on, I just want a notification if turn wrong way.

Regards your simulation topic suggestion - I had similar suggestion - http://help.locusmap.eu/topic/display-itinerary-and-map-side-by-side-simulation-mode but no interest. Now that BRouter can accurately calculate track waypoints I think it would be very nice to have a method to move from waypoint to waypoint to simulate riding the track.

@Andrew: hmm I'm almost sure that my small change should have no influence on this. I may disable it, as it's just one line of code, but it really should work without a problem.

Do you have exact steps I may follow to get exactly same problem?

I'm trying to play with it little bit, but GPS is always turned of correctly in Locus, hmm :/.

EDIT: maybe I've found some weird combination, so next version probably during weekend, thanks

@menion - something definitely different in 3.17.0. No amount of GPS disable/enable will wake it up. I also tried "GPS Status" app - also dead. Thanks for checking.

Only when I go Android > settings > Location > off > on > will the GPS wake up once in this new "sleep" mode. It seems connected to being in house/ office for long time (hours) that this new problem occurs? Sorry not exact steps yet. These things are often so hard to hunt down. Similar to this one - http://forum.locusmap.eu/index.php?topic=5119.msg42845#msg42845 - first I thought was BRouter/ GPX issue only after hours of testing to change opinion and think it was navigation recalculation=Never issue.

@menion - regards "chg: connection to GPS automatic restart in case of connection troubles" - I have now experienced twice that GPS never starts if the device has been inside with GPS disabled for few hours then I run Locus outside with GPS enabled. The satellite map just sits with nothing on the map forever:


It makes no difference if I disable > re-enable the GPS from the satellite map.

Only workaround (so far) - drag down Android top notification panel > disable Location > enable Location > then from Locus satellite map disable GPS > enable GPS > then satellites appear as normal, fairly quickly.

With some help from @poutnik I have more to report. I have navigation recalculation mode = Never. It appears in this mode that when navigation along existing track, and if GPS position is not precisely over track, then navigation mode never occurs, or is very unreliable:


I started navigation 10 times, and only once did it work. The other 9 times guidance mode commenced, and never switched to navigation. It also seems that the longer the track the less likely navigation will commence.

When I set recalculation mode = Route, operation automatically switches from initial guidance to navigation shortly after moving, so for now I'll use this mode.


When I read the manual http://docs.locusmap.eu/doku.php?id=manual:user_guide:functions:navigation:settings&s[]=recalculation it is still not clear when mode = Never why starting navigation is so unreliable if the position (as shown in screen cap) is directly over the track.

Just guessing -  Is possible you have for any reason too low value of off-route threshold,
when Locus switches to guidance instead of naviagtion ?

I generally use "Maximum allowed deviation"= 50m. It has never been a problem before.

Other reason may be Locus gets confused and under mysterious conditions interprets Hint waypoints as waypoints for Guidance.

Either new setting or something else has changed because I never had this problem before now.