This object is in archive!
Wrong elevation gain during recording
Solved
Hi
this is the old helpdesk thread
https://help.locusmap.eu/topic/wrong-elevation-gain-during-recording
it worked for years but with the newest version (classic) it stopped.
The same problem 
Hello Mike,
it has been quite a long time since we discussed this topic. Nice to see you still with us (me) :).
Anyway, I'm not aware of any problem with the recent app version. What exactly seems to be wrong compared to previous versions? Do you see a too big difference between values during recording and after saving?
Are all settings, mainly in the altitude manager, same as you used before?
Hello Mike,
it has been quite a long time since we discussed this topic. Nice to see you still with us (me) :).
Anyway, I'm not aware of any problem with the recent app version. What exactly seems to be wrong compared to previous versions? Do you see a too big difference between values during recording and after saving?
Are all settings, mainly in the altitude manager, same as you used before?
Hi
yes. im still using the app, a few times a week and am still happy. And the app is one of the reasons why i use an android phone. So thank you and you may ask google to pay you.
But i also have to say sorry. the problem from above was my fault. the silcone bumper on my phone produced the wrong barometer data. the sensor measures the pressure on the phone . and with the bumper it produces wrong data. without the data is correct.
But i discovered another problem.
I have a pixel 6a with newest android.
And an old sony X Compact.
Both have a barometer.
When i switch gps on, both search for satellites.
Sony X Compact finds enough and shows the actuel height. So everything ist correct.
The Pixel 6a finds enough satellites. But the acutual heigh starts at Zero and counts up in many steps. So when you start recording and you are on 500m you gain at the start 500m.
I can bypass the problem when i start gps. wait 1 minute and then start recording.
I don´t know if it is an Pixel 6a problem or because of the newest android
Hi
yes. im still using the app, a few times a week and am still happy. And the app is one of the reasons why i use an android phone. So thank you and you may ask google to pay you.
But i also have to say sorry. the problem from above was my fault. the silcone bumper on my phone produced the wrong barometer data. the sensor measures the pressure on the phone . and with the bumper it produces wrong data. without the data is correct.
But i discovered another problem.
I have a pixel 6a with newest android.
And an old sony X Compact.
Both have a barometer.
When i switch gps on, both search for satellites.
Sony X Compact finds enough and shows the actuel height. So everything ist correct.
The Pixel 6a finds enough satellites. But the acutual heigh starts at Zero and counts up in many steps. So when you start recording and you are on 500m you gain at the start 500m.
I can bypass the problem when i start gps. wait 1 minute and then start recording.
I don´t know if it is an Pixel 6a problem or because of the newest android
Hello Mike,
silicon bumper made a such difference? Good to know, thanks!
Altitude problem: it is quite often that altitude accuracy is not ideal right after the GNSS hardware is enabled ... but counting since 0? When you look on the skyplot screen (screen where you turn on/off GPS & see sats) right after you turn GPS, what values do you see? Mainly hor. accuracy values. Are they low since begin also in time, altitude is completely off?
In the latest app version, also some special parameters are read and used (DOP values from NMEA messages), so the app should prevent recording values that have incorrect horizontal or vertical accuracy.
Hello Mike,
silicon bumper made a such difference? Good to know, thanks!
Altitude problem: it is quite often that altitude accuracy is not ideal right after the GNSS hardware is enabled ... but counting since 0? When you look on the skyplot screen (screen where you turn on/off GPS & see sats) right after you turn GPS, what values do you see? Mainly hor. accuracy values. Are they low since begin also in time, altitude is completely off?
In the latest app version, also some special parameters are read and used (DOP values from NMEA messages), so the app should prevent recording values that have incorrect horizontal or vertical accuracy.
I have Made a Video
https://www.filemail.com/d/akdxkvtfgfffkim
I have Made a Video
https://www.filemail.com/d/akdxkvtfgfffkim
Hello Mike,
omg, really interesting! You wrote you use a barometer. Did you try to disable it? Does it make a difference? If this helps, what calibration mode are you using (last tab in the "Altitude manager")?
Hello Mike,
omg, really interesting! You wrote you use a barometer. Did you try to disable it? Does it make a difference? If this helps, what calibration mode are you using (last tab in the "Altitude manager")?
hi
calibration is auto
when i turn the barometer off i have the same behavior
it is also interessting. when i switch locus off after the count ended and reopen it again it does not show this behavior
but when i reopen locus after a few hours i have the behavior again.
it don´t matter if i changed my position in the waiting time.
hi
calibration is auto
when i turn the barometer off i have the same behavior
it is also interessting. when i switch locus off after the count ended and reopen it again it does not show this behavior
but when i reopen locus after a few hours i have the behavior again.
it don´t matter if i changed my position in the waiting time.
May I ask you for another favor? Should be possible to test your device (GPS) with a different app? For example "GPS status" or something similar? You wrote that "with the newest version (classic) it stopped", but this looks to me like some problem in the device and not the app itself, so I would like to verify that this really is a Locus app problem. Thanks!
May I ask you for another favor? Should be possible to test your device (GPS) with a different app? For example "GPS status" or something similar? You wrote that "with the newest version (classic) it stopped", but this looks to me like some problem in the device and not the app itself, so I would like to verify that this really is a Locus app problem. Thanks!
You wrote that "with the newest version (classic) it stopped",
that was about the original problem with the elevation gain were i was wrong. just igbore it.
i tested it with gps status.
it don´t get the counting there. the value vary a bit, but not more then on the old sony x compact
You wrote that "with the newest version (classic) it stopped",
that was about the original problem with the elevation gain were i was wrong. just igbore it.
i tested it with gps status.
it don´t get the counting there. the value vary a bit, but not more then on the old sony x compact
Hmm, so it seems to be a problem in the Locus Map itself. The only place that affects altitude value is the "Altitude manager". So try please also disable the "Altitude filter" on the first tap. If this does not help, you may try to set "SRTM data" to "No usage" if this option is enabled.
Hmm, so it seems to be a problem in the Locus Map itself. The only place that affects altitude value is the "Altitude manager". So try please also disable the "Altitude filter" on the first tap. If this does not help, you may try to set "SRTM data" to "No usage" if this option is enabled.
both (alitutdefilter+srtm) were disabled from the beginning.
activation don´t affect the effect.
but i found something different.
under pressure
the are the options: automatic, pressure at sea level and altitude (choose between gps and add)
when i use automatic i have the behavoir.
when i choose sea level or altitude its gone and it works normal.
so the automatic function is the problem.
is there a quicktab(?) on the sidepanel to this menu?
or do i always havo to go -settings- gpssensors-altitudemanger-circle-choose-confirm
both (alitutdefilter+srtm) were disabled from the beginning.
activation don´t affect the effect.
but i found something different.
under pressure
the are the options: automatic, pressure at sea level and altitude (choose between gps and add)
when i use automatic i have the behavoir.
when i choose sea level or altitude its gone and it works normal.
so the automatic function is the problem.
is there a quicktab(?) on the sidepanel to this menu?
or do i always havo to go -settings- gpssensors-altitudemanger-circle-choose-confirm
Hello Mike,
perfect, this helped so I've found an issue you describe. App needs a 15 seconds for full pressure sensor calibration and this was not handled correctly. I do not understand why I did not noticed this earlier.
Thanks a lot! In the next app version it should be fixed.
Hello Mike,
perfect, this helped so I've found an issue you describe. App needs a 15 seconds for full pressure sensor calibration and this was not handled correctly. I do not understand why I did not noticed this earlier.
Thanks a lot! In the next app version it should be fixed.
works perfect.
thank you
works perfect.
thank you
Replies have been locked on this page!