You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Firmware 2.3.6 ad Android 2.3.7 though suspect occuring in earlier releases. If I set my position and height manually and have 'Use fixed position' turned on, if I connect my Android Galaxy A13 with app permissions for Meshtastic on then the manually entered figures are overridden and the phones GPS data is used. If I turn off Meshtastic's app permissions of then the node reverts to the manually entered figures. When 'Use fixed position' is in operation although the height ASL shows correctly when manually entered it falls to zero at the next position broadcast. The correct manually entered height is displayed if the node is rebooted for any reason but again falls to zero at the next position transmission.
The text was updated successfully, but these errors were encountered:
Sorry I don't understand If I turn Use fixed position off where do I enter the values as the boxes for fixed positions are not visible ? Reading what you have said again I have done as exactly as you have said turned off Use Fixed position and sent it. Turned it back on and entered the fixed values and sent them. This doesn't seem to make any difference to the problems I describe.
Using Firmware 2.3.6 ad Android 2.3.7 though suspect occuring in earlier releases. If I set my position and height manually and have 'Use fixed position' turned on, if I connect my Android Galaxy A13 with app permissions for Meshtastic on then the manually entered figures are overridden and the phones GPS data is used. If I turn off Meshtastic's app permissions of then the node reverts to the manually entered figures. When 'Use fixed position' is in operation although the height ASL shows correctly when manually entered it falls to zero at the next position broadcast. The correct manually entered height is displayed if the node is rebooted for any reason but again falls to zero at the next position transmission.
The text was updated successfully, but these errors were encountered: