Map "spinning" when standing still

[Erdna]

Hi all,

I can confirm this behaviour on Fossibot F101 Pro running Android 13 and Google Pixel 9 running Anroid 16. App is most recent Play Store version on both.

Regards,
André

[TomOnTour]

Hi all,

same here: I had the same issues the last 2 days, but sometimes verything works just fine. I haven‘t been able to find out what gibt trigger it. Remembering some technical details around GPS I know that it is sometimes pretty hard for GPS devices to identiofy the direction, when there is no moment. This would explosion, way it is getting in the right position and direction, as soon as you start moving again.

Greetings
Thomas

[Peter Zehentreiter]

@TomOnTour said in Map "spinning" when standing still:

This would explosion, way it is getting in the right position and direction, as soon as you start moving again.

Hopefully my bike will NOT "explode" tomorrow when I'll open the bike season 2026

[TomOnTour]

@Peter-Zehentreiter said in Map "spinning" when standing still:

Hopefully my bike will NOT "explode" tomorrow when I'll open the bike season 2026

Aaargh, I hate the spelling changes
My intention was th write "explain"

Sorry, for scaring you a bit

Greetings
Thomas

[Peter Zehentreiter]

@TomOnTour Sure, I know that you wanted write " explain" instead of explosion.
My comment was also intended as a joke.

Regards
Peter

[Peter Zehentreiter]

@Corjan-Meijerink

There are currently two of us travelling through Slovenia and Croatia...
My colleague uses MRA on an iPhone; I use Android.

At the moment, whenever we stop at a traffic light or a stop sign – whether in town or in the countryside – the map on both devices starts rotating while we’re stationary 🤬

Earlier, we had to turn around at a roadworks site... I wanted to zoom in to see how we could get round the roadworks... then, whilst searching for an alternative route, the map started rotating.

This is extremely annoying, and it’s also a hassle to search for a different route with the map upside down.

Please fix this bug as soon as possible.

Thanks

[Jörgen]

Read here:

https://forum.myrouteapp.com/topic/10633/turning-of-the-screen-when-standing-stil/2?_=1775735018064

Will be fixed soon.

[Peter Zehentreiter]

@Jörgen Thanks for the link to the other conversation which I have already read.

I just wanted to keep this annoying issue in Corjan's mind.

Slovenia is geil at this moment . Wir are almost alone on the on most of the streets.

[Corjan Meijerink]

The issue has been identified.
Unfortunately the HERE SDK is the cause
They have fixed it in a recent update but that version contains another issue causing us definitely not to update just yet.

Developers informed me that the blocking (other) issue is solved in their next update so hopefully it’s available soon

[peha]

@Corjan-Meijerink Is there any timeline or estimate for when the spinning issue might be resolved-one week, one month, or another six months? (The initial problem description in this thread dates back to November 2025.) I understand it's supposedly a third-party problem, but it's still very annoying, and the lack of transparent communication doesn't help. Could you please share some insight into what a realistic expectation might be for this to be fixed for end users? Thank you!

[Corjan Meijerink]

@peha After my last statement I would not say there is a lack of transparency

I also replied in the other thread, no need to ask twice.

Edit: no hard feeling, I understand the frustration and I really want it solved too

[peha]

@Corjan-Meijerink Thanks for your reaction which I appreciate. I still don't find information regarding what a realistic timrline / expectation would be for the spinning issue to be fixed in the app. Maybe I'm just not looking in the right spots. I'll be going on a longer trip in 7 weeks with lots of navigating through unknown city routes with a lot of intersections, and I keep asking myself if it's a good idea to rely on MRA for that or whether I'd better use an alternative.

Edit: Seeing your edit on your earlier reply just now - I also hope I don't come across as confrontational or provicative, which is not my intention ; there might be some nuance lost (not a native speaker, obviously).

[Corjan Meijerink]

@peha I simply do not have it
HERE has no timelines (just like us? ).

To quote their developer that I contacted personally (really rare I can actually do that): “Regarding the exact delivery date cannot comment right now, as every major version update goes through additional steps, which usually take more time.”

They released 4.25.5 and the fix I need is in their upcoming 4.26.0 update.

[Corjan Meijerink]

@peha nice communicating through edits hahaha
All good! I always applaud criticism as long as it is relevant. I completely agree with you on the subject.

Hope it is resolved soon and definitely some language nuances can be lost in translation. You definitely are not being provocative but just looking for answers. That’s why I wanted to clarify I’m in no way frustrated about you asking again

Thanks for your input on this subject and your contributions!