Height Problem

Hi Orux Team,

I notice i have a problem with the height data.
The programme showing always 0 meters,whether it be in 50 or 2000 meters, instead "gps status" showing the right heights.
GPS height correction in the programme shows no reaction.
I have the Samsung Galaxy ACE (GT-S5830) Android 2.3.3.
How can I correct this height mistake?

Thanks,
Roberto

steka wrote:Hi Orux Team,

I notice i have a problem with the height data.
The programme showing always 0 meters,whether it be in 50 or 2000 meters, instead "gps status" showing the right heights.
GPS height correction in the programme shows no reaction.
I have the Samsung Galaxy ACE (GT-S5830) Android 2.3.3.
How can I correct this height mistake?

Thanks,
Roberto

Hi, Roberto,

There are problems with some android versions, when OruxMaps tries to read Nmea sentences to correct altitude over the geiod.

try disabling 'Nmea altitude correction' in oruxmaps gps configuration.

orux

Thanks orux

I disable 'Nmea altitude correction', and now show right height.

Hi Orux,

I'm not sure, if this is a postreply (and I have disabled NMEA correction). My device is an Galaxy S with DarkyRom 2.3.6 JW4. OM has tracked a route, which I've loaded in my MagicMaps (German Topo 1:25.000) with about 800 HM, the handmade track in the map gives me about 1.450 HM - same as my speedo on the bike. I've loaded this handmade gpx-file into OM, height is right?

So from where comes the difference - any idea??

May be that's a stupied question, but how does OM gets the height - through GPS-position and height-data from the map?

Thanks for help,
Norbert

norbertk wrote:Hi Orux,

I'm not sure, if this is a postreply (and I have disabled NMEA correction). My device is an Galaxy S with DarkyRom 2.3.6 JW4. OM has tracked a route, which I've loaded in my MagicMaps (German Topo 1:25.000) with about 800 HM, the handmade track in the map gives me about 1.450 HM - same as my speedo on the bike. I've loaded this handmade gpx-file into OM, height is right?

So from where comes the difference - any idea??

May be that's a stupied question, but how does OM gets the height - through GPS-position and height-data from the map?

Thanks for help,
Norbert

Hi;

are you talking about altitude climbing/descending along the track?

if yes, it is a gps accuracy problem.

can be reduced in two ways:
- correcting the altitude at the end of the track (see the manual; recommended google service, it is more accurate).
- change the gps settings, to take fewer points (increase time between measurements).

orux

Hi Orux,

do I understand right, that I have to do use at the end when the track is finished: Manage track > Correct Altitude?
I have also changed in "Application" the Custom elevation service to Google - as described in the EN Manual ...

Thanks, Norbert