The navigation cursor gets stuck during track navigation

Graf Geo shared this problem 2 months ago
In Progress

For some time now, I’ve been experiencing a problem where, during track navigation (primarily walking/hiking), the navigation arrow (dark arrow) occasionally gets stuck at a point on the planned route and usually points in the wrong direction, whilst the unfilled cursor arrow (actual position) continues to move correctly with me. This naturally leads to an increasing discrepancy between the two cursor arrows, and once I’ve reached the distance I’ve set, I receive a deviation alert telling me that I’ve strayed from my planned route.

Which, of course, isn’t true, as I’m still on the route; it’s just that the navigation arrow has got stuck.

This usually happens once or several times per trip, mostly when I’ve stopped briefly, but sometimes for no apparent reason. These are ‘normal’ journeys from A to B without any return legs.

If I then switch the GPS off and on again briefly, it works fine again. As it happens quite frequently and beeps every time, it’s a bit annoying. What could be causing this and how can I fix it?

As I don’t have a screenshot and it’s difficult to simulate the situation at home, I’ve drawn up a schematic diagram:

Replies (7)

photo
1

Hi,

we have worked on a similar issue recently regarding a stuck guiding line during guidance. This bug has been fixed. Please test it on the latest beta version at https://bit.ly/lmVersionsTest. Thanks.

This comment is in trash! Restore
photo
1

Hello Michal,

thanks. I’m pretty sure it happened last Sunday as well; I’d already installed the latest beta, version 4.35.0.7. But I’ll test it again and keep an eye out to see if it keeps happening.

Edit: I can see that the fix was already included in version 4.35.0.4 – after that, the problem I described definitely continued to occur.

This comment is in trash! Restore
photo
photo
1

Thanks. We'll need an accurate description of all the steps leading to a successful simulation of the issue, then.

This comment is in trash! Restore
photo
1

I’ve just had a quick go on it on my way to the underground. I planned a route using the route planner (about 200 m). I then navigated the route. After 100 m, I deliberately veered off course by a few metres. The position cursor followed me, whilst the navigation arrow stayed on the route (correct). Then I went back onto the route where I left it; the navigation arrow no longer turned in my direction, but it did follow me. Back on the planned route, both arrows followed me, then suddenly the blue navigation arrow turned by about 180° and remained stationary. The position cursor continued to follow me, albeit still facing the wrong way. Until the distance became so large that it beeped.

This comment is in trash! Restore
photo
photo
1

Thanks. Now please create a manual backup of your settings and send it here for a test. Thank you.

This comment is in trash! Restore
photo
1

Ok, I sent you the backup zip (only settings) with a private ticket.


BTW: The bright position arrow almost never rotates with me when I change direction by about 180° (i.e. when I go back). I’ve tried various settings under GPS & sensors > Orientation, but nothing has changed.

He then walks alongside me, facing the opposite direction...

This comment is in trash! Restore
photo
photo

The navigation cursor gets stuck during track navigation

This comment is in trash! Restore
photo
1

Unfortunately, we still haven't managed to simulate the issue correctly, despite applying your setup. We'll go on investigating the problem further, but without proper reproduction of the issue, we can't do much.

This comment is in trash! Restore
photo
1

I looked into it again at the weekend and was able to reproduce the problem in several tests. I also made two screen recordings.

The main issue is that, when walking slowly and making sharp changes of direction (turning round), the bright navigation arrow does not reliably turn with you and then points in the wrong direction (sometimes for a long time or permanently) whilst still moving along with you. Sometimes increasing the walking speed helps, but not always.

This happens particularly when I change direction by nearly 180°, i.e. when I walk backwards. For example, when I briefly leave the route by a few metres against the planned direction to read a sign, step off the path, or similar.

(This has nothing to do with the map rotation, which happens immediately when the direction changes. The rotation of the navigation arrow, on the other hand, is delayed or does not happen at all.)

The dark arrow remains on the route; sometimes it also rotates (in the same wrong direction), and sometimes it remains correctly pointing in the intended direction.

When I return to the planned route, both arrows follow me again, with the light-coloured arrow possibly pointing the wrong way. At the next junction, the dark route arrow then remains stationary, whilst the light-coloured navigation arrow continues to follow me, triggering a distance warning.

Here are two screen recordings showing the problem. You can download them via the links. In both, I’m navigating a planned route.

screc01: I’m navigating and walking eastwards. Then I slowly cross to the other side of the road and walk diagonally back towards the track a few metres to the west. Then I turn round again and walk eastwards. The light-coloured navigation arrow doesn’t turn with me and continues to point westwards, but moves eastwards with me. At the next junction, the dark track arrow also turns the wrong way and remains stationary (!). When I continue walking eastwards, the distance alarm is triggered.

screc02: The same thing happens on another road, travelling from north to south.

Just for information, in case it’s relevant: route planning is carried out without navigation instructions.

I’ve been using track navigation regularly when walking or hiking ever since I got Locus, so for about 10 years. This problem never used to occur! It’s only been a few months that I’ve been struggling with it – I think since around April or May this year.

*** Translated with http://www.DeepL.com/Translator (free version) ***

This comment is in trash! Restore
photo
1

Just a friendly reminder – has the issue been clarified and is it still being looked into?


Thanks in advance.

This comment is in trash! Restore
photo
1

Hi, the issue is still in the devs' queue of tasks.

This comment is in trash! Restore
photo
photo
1

Even at the risk of getting on your nerves: 😉


I’ve been on a hiking holiday in the mountains for two weeks now and have been struggling with this problem every day. The bright arrow keeps failing to turn with me when I turn round or when my direction of travel changes by 180 degrees. Usually, a change in direction of around 145–225 degrees is enough to cause this problem. And this happens all the time when you’re hiking: a quick detour to a viewpoint a few metres off the planned route, an information sign, a sharp hairpin bend, and so on… The light-coloured arrow then moves backwards or points diagonally backwards to the side, and when you’re back on the planned route, the dark blue arrow on the track also turns in the same wrong direction and gets stuck. Navigation then stops working and (if enabled) the warning beep sounds after x metres. Sometimes I have to switch the GPS off and on again several times until the arrow points in the direction I’m moving again.


It’s definitely a bug or issue in Locus, which I’ve never experienced in over 10 years of use and which started sometime in early summer. In other apps, such as Organic Maps, the arrow always turns immediately to face the correct direction of travel. Even at very slow speeds and during 180-degree changes of direction.


I’m also surprised that I seem to be the only one with this problem. Or do they all just cycle or hike at a brisk pace, so they don’t have the problem? It can’t be down to the device either, as I’ve had it for much longer than this behaviour first started occurring.


See screenshot. I’m heading south after having visited the viewpoint just a short while ago – and both arrows are pointing north!

This comment is in trash! Restore
photo
1

Hi, sorry for the inconvenience but this issue is still being investigated - without simulation and reproducing the problem, it is tough, though. For the time being, try turning on the "Snap to route" option in Settings > Navigation > Advanced. Only one arrow will appear during navigation.

This comment is in trash! Restore
photo
1

Thanks Michal. I tested it today on my old device (SG S10), and the problem occurs on that one too. So it’s definitely not device-specific and should therefore be easy to reproduce. You don’t need to use the navigation function for this: simply watch the (light-coloured) direction arrow whilst walking at a leisurely pace, take a few steps back or sidewards, wait a few seconds, then turn round and see whether the arrow turns back in the direction of travel or not. Sometimes it does, but often it doesn’t.


Thanks also for the tip about “Snap to route”. I only tried it briefly today, and it seems that the single arrow then rotates more reliably. I’ll test it more thoroughly tomorrow. Even if it takes some getting used to not being able to see straight away where you actually are. 🙂

This comment is in trash! Restore
photo
1

I’d like to come back to this issue, as it’s still very annoying for me. The tip/workaround of using just one cursor during track navigation – “Snap to route” – does help (the problem with the arrow freezing or being misaligned then occurs much less frequently), but it isn’t a solution for me. As I often document for OpenStreetMap and other projects on the side, I also need my actual location – that is, the light blue arrow – whenever I deviate from the planned route, whether intentionally or unintentionally.

I’ve now reactivated my ancient Galaxy S7, which still had the older Locus version 4.32.4 installed. I ran a few tests with it: whilst walking, the light blue arrow did jerk slightly all the time and wobbled a bit erratically, but it responded quickly and reliably to every change of direction, no matter how slowly I walked. When I turned round (approx. 180°), the arrow jumped straight into the new direction within 1–2 seconds at the latest. Just as I’m used to with any other map app.

I then installed version 4.33.0_1210 from the archive. In this version, you’ve incorporated some sort of damping; the light blue arrow now turned more smoothly and slowly, occasionally with a slight delay, rather than being a bit shaky and no longer jerky. At least it always seemed to respond to a change in direction, as far as I could tell from testing it for a few minutes.

I then updated to version 4.34.1_1213, and it was precisely with this version that the problem I described in detail occurred: the light blue arrow no longer reliably turns with me when I change direction significantly or turn round and walk back. It often reacts with a significant delay or, in the worst case, not at all. The arrow then moves along pointing backwards or sideways, as described previously, which is disastrous for navigation. As I said, it doesn’t happen all the time, but it does happen very frequently.

So you must have changed something in version 4.34 at the latest, which is causing this problem. This also fits in with my impression that it started occurring sometime in the spring or early summer. After all, version 4.33 is dated 14 May and 4.34 25 June; it probably started even earlier, as I actually always use the latest beta, which is released sooner.

As I now regularly experience this problem on three different devices (2 x Samsung, 1 x Motorola), I can’t imagine that you wouldn’t be able to reproduce it.

I suspect it might have something to do with the “minor tweak” chg: significantly updated “Smooth movement” system — now also available during navigation (still an experimental setting), which was listed in the changelog for 4.33. I recall that there were requests on the forum at the time to fix the map rotation (sometimes by 180°) when stopping at traffic lights or similar. Or in 4.34, there was this change: chg: another iteration of the “Smooth movement” algorithm.

I really hope you’ll sort this out. It’s actually a real nuisance for me.

This comment is in trash! Restore
photo
Leave a Comment
 
Attach a file
You can't vote. Please authorize!