3.2.12 findings on Android (landscape)
-
Some findings
- Cursor position lags behind of actual position. Missed some turns because of it.
- One of the times I started the app I had no navigation audio
- Navigation audio is lower then music audio (YouTube Music)
- When stopping for a coffee . I stopped the app. When restarting and trying to pickup the route I had to skip al waypoint passed.
- While driving, skipping waypoint did not always work.
- Behaviour at round about is too slow
- Behaviour after turn also slow but this can be related to point 1 ,i think.
All findings on Android Samsung S21FE in landscape mode
-
Some findings
- Cursor position lags behind of actual position. Missed some turns because of it.
- One of the times I started the app I had no navigation audio
- Navigation audio is lower then music audio (YouTube Music)
- When stopping for a coffee . I stopped the app. When restarting and trying to pickup the route I had to skip al waypoint passed.
- While driving, skipping waypoint did not always work.
- Behaviour at round about is too slow
- Behaviour after turn also slow but this can be related to point 1 ,i think.
All findings on Android Samsung S21FE in landscape mode
@EdwinM-M point 2 and 3 I'll need to retest I just found out . That my sena also has a direct connection with my phone instead of via KTM. So not really sure of the cause.
-
Some findings
- Cursor position lags behind of actual position. Missed some turns because of it.
- One of the times I started the app I had no navigation audio
- Navigation audio is lower then music audio (YouTube Music)
- When stopping for a coffee . I stopped the app. When restarting and trying to pickup the route I had to skip al waypoint passed.
- While driving, skipping waypoint did not always work.
- Behaviour at round about is too slow
- Behaviour after turn also slow but this can be related to point 1 ,i think.
All findings on Android Samsung S21FE in landscape mode
@EdwinM-M thanks for your feedback!
1: known issue, are working on it
2: sometimes that indeed is an issue, will be improved
3: correct
4: that is true and by design. Just long press the waypoint on the map (or in the waypoint list) you want to resume at
5: not sure about that, the feature is pretty stable. Might be because not using offline navigation and temporary a loss of internet or a user error
6: same as 1
7: same as 1 also as you thoughtThanks for sharing your findings!
-
Some findings
- Cursor position lags behind of actual position. Missed some turns because of it.
- One of the times I started the app I had no navigation audio
- Navigation audio is lower then music audio (YouTube Music)
- When stopping for a coffee . I stopped the app. When restarting and trying to pickup the route I had to skip al waypoint passed.
- While driving, skipping waypoint did not always work.
- Behaviour at round about is too slow
- Behaviour after turn also slow but this can be related to point 1 ,i think.
All findings on Android Samsung S21FE in landscape mode
@EdwinM-M said in 3.2.12 findings on Android (landscape):
Some findings
- Cursor position lags behind of actual position. Missed some turns because of it.
Just to add a little detail there:
- The grey progress colour on the road updates much more accurately than the position arrow, whereas the arrow itself updates in discrete leaps, occasionally 2-3 seconds behind
The grey road indication is certainly useful in place of an accurate arrow for the time-being, but on a motorbike (at speed) distinguishing the grey area takes too much concentration. Slow down, you say?

I also had two app crashes on Saturday mid-journey. Is there a way to submit logs to MRA, or are you auto-uploading logs already?
(v3.2.12 - 164 on a OnePlus Nord)
-
@EdwinM-M said in 3.2.12 findings on Android (landscape):
Some findings
- Cursor position lags behind of actual position. Missed some turns because of it.
Just to add a little detail there:
- The grey progress colour on the road updates much more accurately than the position arrow, whereas the arrow itself updates in discrete leaps, occasionally 2-3 seconds behind
The grey road indication is certainly useful in place of an accurate arrow for the time-being, but on a motorbike (at speed) distinguishing the grey area takes too much concentration. Slow down, you say?

I also had two app crashes on Saturday mid-journey. Is there a way to submit logs to MRA, or are you auto-uploading logs already?
(v3.2.12 - 164 on a OnePlus Nord)
@richtea-0 logs are updated automatically!
Thanks for sharing your thoughts.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login