Map "spinning" when standing still

[Lex.Kloet.RX]

@Jörgen das ist mir bekannt, es ging mir um das verschiedene Verhalten. Aber ich habe das öfters, das bei mir bei Ampeln am Rad gedreht wird. ‍

[Corjan Meijerink]

I've investigated the issue, found a possible cause and implemented changes in 5.0.2.

Will need some extensive beta testing on different devices but I'm hopeful the issue will be resolved

[white.mouse]

Wanneer ongeveer komt deze Beta (5.0.2) beschikbaar zodat ik eventueel wat kan plannen om te testen; Ik heb ook last van dit "spinning" als ik bij verkeerslichten of een kruising stil sta!

[Corjan Meijerink]

Expecting after the weekend but maybe I'll submit it tomorrow
Depending on the platform you are using it will also take another day or two before it's available.

[peha]

@Corjan-Meijerink Are more beta testers needed? I'd be willing to test a little, if it helps (my setup is noted in the footer: Android with two AA-devices).

[M. Schrijver]

I did see it on my normal navigation phone on a few trips. Today i use my daily phone, which i only use in the car for navigation (not on my bike). On this phone i saw the behaviour also
Both were running Android Auto.
On the bike it spins more than once on the same spot (but not constant) mostly back and forth. In the car mostly it spins only once. Just as soon as i stopped.

Let's what the new version brings

[Albert van den Elsen]

This issue may simply be due to a weak GPS signal. I don’t think it’s related to MRA.

[Marinus van Deudekom]

@Albert-van-den-Elsen my Guess is that it's the combination of some type of phones, mostly Android based and some AA/CP devices. I havent seen the issue at all.

[Corjan Meijerink]

Yeah, that’s the annoying thing of these issues. It’s definitely device related so some have it, others do not. GPS positioning and especially on Android devices is not always as accurate as you’d hope.

[peha]

With my Samsung S22 Ultra, it is reproducibly a problem that occurs with MyRouteApp, but not with Google Maps: Sitting on my couch at home, phone laying on a table (i.e., not moving at all, not being touched), after I have opened MRA on the phone, the "view direction" (map orientation) changes several times for about 90 or 180 degrees, the movement pauses some seconds and then moves again. When it finally settles, it doesn't point in the actual direction the phone faces. Moving the phone after it has "settled", the map doesn't react any longer (map not moving). The compass needle symbol changes from "triangle shape" (map rotation follows phone) to a "strike-through compass needle" (?). No AA device involved at this point. This happens only with MRA, Google Maps doesn't show any problems, and another navigation app I had (but have uninstalled a few days ago), Magic Earth, didn't either show this problem. For me, it's clearly isolated with MRA, and while I may have seen an occasional map spin in earlier versions, it is now a constant problem (as soon as the device doesn't move) and, unfortunately, dramatically reduces the actual usefulness of the app for navigation. Phone is the same; the only thing that has changed is, there have been security/firmware updates by Samsung over the years.

[M. Schrijver]

It is also MRA related. Why?
At least on my phones, only MRA has this problem. Maybe Here is the cause. I don't know
But just like i wrote in other topics. There are other GPS related things which only occur in MRA and not in other navigation apps

[Con Hennekens]

Some phone have not only GPS but also a hardware compass. These are able to "see" in which direction they are held. Phones that don't have a compass, extrapolate direction from movement. That gets very inaccurate while standing still. Then there are apps that that rely on location services only (I don't know if direction is taken from compass if available), and there are apps that have different methods of approaching hardware. It all is a little more complicated then one might think...

[Donovan Smith]

same with me on i phone. not touching phone or anything. It flips and then flips back. doesn't happen every time but sometimes even when riding

[peha]

I don't doubt that it's complicated. I also didn't mean to "blame", should it have come across like this, stating that Google Maps doesn't show this phenomenon, but rather point out that it is possible to somehow avoid this problem (i.e., there's hope). I do, however, wonder why (for my setup at least) the severity/frequency of the spinning has increased to a level where it occurs at practically every stop. Something must have changed.

[M. Schrijver]

@Con-Hennekens said in Map "spinning" when standing still:

Some phone have not only GPS but also a hardware compass. These are able to "see" in which direction they are held. Phones that don't have a compass, extrapolate direction from movement. That gets very inaccurate while standing still. Then there are apps that that rely on location services only (I don't know if direction is taken from compass if available), and there are apps that have different methods of approaching hardware. It all is a little more complicated then one might think...

It is true what you say but when you have multiple navigation apps on your phone and use all of them also. And only one app have issues. Than it is pretty obvious that this app is the one which needs to fix it.

I know it not easy to fix this. As @Corjan-Meijerink wrote. There so many different phones and not all have these issues.

[Nick Carthew]

@M.-Schrijver When version 5.0.2 is released you may see an improvement.

[LE DIZES Freddy]

I just tried version 5.02 and the problem with the map spinning while stopped is still there.

Happy holidays to everyone!

[Nick Carthew]

@LE-DIZES-Freddy said in Map "spinning" when standing still:

I just tried version 5.02 and the problem with the map spinning while stopped is still there.

Happy holidays to everyone!

Are you one of the BETA testers?

[LE DIZES Freddy]

@Nick-Carthew oui

[Corjan Meijerink]

@LE-DIZES-Freddy is that on Android itself or in Android Auto?

A big part of my fix for the map spinning caused a major issue on some Android Auto devices leading to the position not updating al all