Map "spinning" when standing still
-
The thread (at least how I meant it) is about the spinning when at a standstill; for me, there is no problem while moving. Unfortunately, the difficulties also occur on my phone (Samsung S22 Ultra) alone, without any Android Auto device involved, and they keep occurring with 5.02 as well. It happens at practically every stop, and almost every time the map then turns 180 degrees (facing the direction from where I came), causing the navigation to recalculate. Something must have changed compared to earlier versions-be it the app, the phone, or hardware conditions-because I did not have the problem this massively in the past. It drastically reduces the usefulness of the app, and it is not good news that seemingly not much can be done to solve this.
I do, however, appreciate the attempts to fix it, and I am hopeful that a new solution can be found and designed over time. I like the app a lot; it's been my everyday navigation app (and especially now, with free drive, even more so)-I believe in the team's ability to eventually find a fix for the phenomenon. 
@peha said in Map "spinning" when standing still:
It happens at practically every stop, and almost every time the map then turns 180 degrees (facing the direction from where I came), causing the navigation to recalculate.
That in itself already is a strange phenomenon, since at speeds under a certain level, no recalculation should be triggered at all (because it is considered a stand still).
-
The thread (at least how I meant it) is about the spinning when at a standstill; for me, there is no problem while moving. Unfortunately, the difficulties also occur on my phone (Samsung S22 Ultra) alone, without any Android Auto device involved, and they keep occurring with 5.02 as well. It happens at practically every stop, and almost every time the map then turns 180 degrees (facing the direction from where I came), causing the navigation to recalculate. Something must have changed compared to earlier versions-be it the app, the phone, or hardware conditions-because I did not have the problem this massively in the past. It drastically reduces the usefulness of the app, and it is not good news that seemingly not much can be done to solve this.
I do, however, appreciate the attempts to fix it, and I am hopeful that a new solution can be found and designed over time. I like the app a lot; it's been my everyday navigation app (and especially now, with free drive, even more so)-I believe in the team's ability to eventually find a fix for the phenomenon. @peha For me, the problem already existed with previous versions.
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
