Altitude does not match

[Corjan Meijerink]

We indeed received some reports that different Android devices seem to report a wrong altitude.
Will be investigated.

I know this sounds weird so unsure how that then works in the other apps but we literally just show the altitude as received by the GPS without any correction.

[M. Schrijver]

Doesn't most phone also have a barometer/pressuremeter for the altitude.
In one of the apps i tried. It shows a correct altitude but no position because the GPS couldn't detect a position (i was inside my house).

[M. Schrijver]

Just for comparison.
Altitide according MyRoute:

Altitude according random GPS Tool:

[hawebo]

Habe dasselbe Problem: Die Höhenangabe in der MyRouteApp, Vers. 5.1.0-462, zeigt ca. 50 m höher an als der Barometer und Höhenmesser auf demselben Smartphone (Gigaset GX 4Pro, Android 14), siehe Bilder.

Die Höhenmesser-App ermittelt die korrekte Höhe von 508 m üNN aus dem GPS und dem Drucksensor des Smartphones (Sensor: Bosch ICP101XX).

[M. Schrijver]

I have a Pixel 6a and 6 Pro. in my case both phones show the same exact altitude but around 50 meters to high. Both with the final 5.1 version
Last weekend I was in Westerwald (Germany). There the altitude was also around 50 meters off.

[Stanisław]

I can see the same on my Iphone 15 - compass app vs MRA:

[M. Schrijver]

@stanisław Maybe i look wrong. But in your screenshot MRA says 291 meters and the other app 290 meters. That is within limits.
Or am I wrong?

[Stanisław]

I meant that they are the same values in both applications, so I can not see any problem on my side.

[Robineke]

Ik ervaar ook een verschil van ongeveer 45mtr. Mij camper navi gebruik ik nauwelijks maar voorheen voor de hoogte indicatie. Dat klopt overal, zeeniveau en bergpassen.
Overigens een waardevolle toevoeging, ben er blij mee. Top MRA Team.
Wellicht nog wat finetunen, het is tenslotte een beta versie die wel heel professioneel is.

[Corjan Meijerink]

@robineke Please try to stick to the thread language.

I can confirm we are now testing a fix for the next update.
I expect this to be solved