Possible problem with Altitude Manager, Locus 3.20.1
Hello
Using Locus 3.20.1 with Android 4.0.4 phone.
My phone has a pressure sensor.
Using Locus in mountain terrain, I use the pressure sensor for altitudes.
I need to calibrate the altitude reading at the beginning of each trip.
The Locus settings show 3 methods of calibration:
1- Using the GPS altitude
2- Entering the pressure known at sea level
3- Entering the known altitude
The first option works well, but it is has the limitation of the GPS altitude (the altitude reference datum depends on the device as it not always very clear what the reference datum is being used by the device, the GPS altitude is not very good if the satellite geometry is suboptimal which is often the case in mountain terrain where large sections of the sky are obscured by the mountains around)
I haven't tried the second option (this option is useful only if one has access at the time of the calibration to real time data at sea surface nearby)
I am having problems with the third and in my case most useful option, entering the altitude at a known point.
What happens in my case:
In Altitude manager, I tick the circle "Altitude", I input the known altitude, I click on top right screen "SET" , and then I get a message "Loading" for ever (I tried to wait up to an hour, with no success). See attached screen shot.
This problem was also there on version 3.20.0.
I haven't checked on previous versions.
This is not an important problem, but I will be nice to correct it if this is related to a software glitch and not to some weirdness of my phone.
Best regards
The same problem 
Good day Alfonico,
thanks for your report. It is surprising issue. When this dialog is visible ( with text "loading..." ), Locus Map on background connects to pressure sensor, load 20 values, create and average from them and use them. It usually take 1-2 seconds, not more.
I've improved this dialog so it will display a progress, anyway this won't solve this issue. Question is, why pressure sensor do not report any values to Locus Map. Do you have positive experience with this sensor in any other application?
Maybe you may try this application for example: https://play.google.com/store/apps/details?id=com.wered.sensorsmultitool . I've just tried it and it display correctly sensor value for a pressure sensor on my device, so good enough for a quick test.
Good day Alfonico,
thanks for your report. It is surprising issue. When this dialog is visible ( with text "loading..." ), Locus Map on background connects to pressure sensor, load 20 values, create and average from them and use them. It usually take 1-2 seconds, not more.
I've improved this dialog so it will display a progress, anyway this won't solve this issue. Question is, why pressure sensor do not report any values to Locus Map. Do you have positive experience with this sensor in any other application?
Maybe you may try this application for example: https://play.google.com/store/apps/details?id=com.wered.sensorsmultitool . I've just tried it and it display correctly sensor value for a pressure sensor on my device, so good enough for a quick test.
Hello.
Many thanks for your reply. I have been doing some trials.
The problem appears to be intermittent, and only if the GPS is activated on the device, but not yet locked on a position (device still calculating a position).
I have been unable to duplicate the problem consistently, therefore I don't know what is the sequence of events that generates the problem.
But I have been able to find a solution that works consistently if the problem arrises: I turn off the GPS withing Locus, then I do the calibration. Works 100% of the time and doesn't take any time (the GPS locks very quickly when turned on again, so not a problem to turn it off briefly).
Therefore I consider that this problem is solved for me, and possibly that the problem is due to my phone rather than to Locus as nobody else reports this issue.
Hello.
Many thanks for your reply. I have been doing some trials.
The problem appears to be intermittent, and only if the GPS is activated on the device, but not yet locked on a position (device still calculating a position).
I have been unable to duplicate the problem consistently, therefore I don't know what is the sequence of events that generates the problem.
But I have been able to find a solution that works consistently if the problem arrises: I turn off the GPS withing Locus, then I do the calibration. Works 100% of the time and doesn't take any time (the GPS locks very quickly when turned on again, so not a problem to turn it off briefly).
Therefore I consider that this problem is solved for me, and possibly that the problem is due to my phone rather than to Locus as nobody else reports this issue.
Hello Alfonico,
this is surprising. Loading of pressure here (after you tap on "set" button) should not be connected to GPS location, so if GPS is enabled/disabled/loaded etc., should be cause no effect here.
Anyway I've at least added to next version progress, how many values is already loaded, so you will at least see if something happen.
Anyway if this will be really a problem and happen more often, write me here. We may at least try to test this on some special debug version that will print out to log file some useful information.
Menion
Hello Alfonico,
this is surprising. Loading of pressure here (after you tap on "set" button) should not be connected to GPS location, so if GPS is enabled/disabled/loaded etc., should be cause no effect here.
Anyway I've at least added to next version progress, how many values is already loaded, so you will at least see if something happen.
Anyway if this will be really a problem and happen more often, write me here. We may at least try to test this on some special debug version that will print out to log file some useful information.
Menion
Hello
Version 3.21.0 feed back when doing the calibration is welcome!
Many thanks.
Hello
Version 3.21.0 feed back when doing the calibration is welcome!
Many thanks.
At least something that may helps you to check if something is happen in app or it's just stuck.
At least something that may helps you to check if something is happen in app or it's just stuck.
Replies have been locked on this page!