Closed dominikargast closed 6 years ago
@marikavertzonis use build > 3.0.21 to test. Requires AppFramework version > 3.1.32.
tested with app 3.0.23 with framework 3.1.33. assuming the symptom of this was the continuous flickering between external and internal position sources on android which meant the rapid appearance and disappearance of the 'start moving...' message then this is fixed :). tested on
If the PositionSource component is initialised without a specific NmeaSource set, it will use the default position source available on the platform. After connecting to an external GPS by setting the nmeaSource property, the expectation is that only position information from the external device are reported.
This is not true. Position information from the external device AND the default position source are being reported, leading to unexpected jumps in position and accuracy.
Note that this behaviour does not occur if the nmeaSource property of the PositionSource component is set at startup.