Incompatibility with mock location (and maybe more)
M
Mapa Ambon (PL)
started a topic
4 days ago
Hi.
Track recording profiles does not allow to disable accuracy requirement:
You can set the accuracy value sky high, but not disable completely. This causes problem with mock location provider which seems to report accuracy (at least as seen on the recording screen in Locus GIS) but this information is not recognized properly by Locus GIS:
Attempting to save recorded line I'm prompted with "Tolerance exceeded [...] Current value: ? Expected at most: ..." message. Neither of available options allow me to save the recorded track - "Force Save" causes the recording to disappear and be replaced by a ruler tool (to measure distance), and with "Repeat" it just disappears (the behavior after "Force..." looks like a bug itself or I'm unable to understand the rationale behind?):
This problem was checked on two Android devices, both with Locus GIS 1.23.10 (I'm unable to install 1.24.x on them for unknown reason, it's not present in the store - but I have it on one other device). I'm using Bluetooth GNSS 1.0.69 app as a mock location provider (which works fine otherwise).
And to complicate things more.. On one of these devices (#1 below) the same problem is present if I skip mock location completely and connect GPS Receiver directly, using GNSS Manager / GPS Device Manager in Locus GIS. The other device (#2) was able to save tracks recorded this way without problem.
Allowing users to disable the accuracy requirement in the profile would solve the problem for strange cases like here. This makes lots of sense to me. But it would be extremely useful if the app was also able to utilize accuracy value reported by mock lock. provider.
As you can see there're 3 different problem topics above. If you want me to split them to different reports then just tell me. I put them in one report for now to show how they influence/depend on each other mutually.
Mapa Ambon (PL)
Hi.
Track recording profiles does not allow to disable accuracy requirement:
You can set the accuracy value sky high, but not disable completely. This causes problem with mock location provider which seems to report accuracy (at least as seen on the recording screen in Locus GIS) but this information is not recognized properly by Locus GIS:
Attempting to save recorded line I'm prompted with "Tolerance exceeded [...] Current value: ? Expected at most: ..." message. Neither of available options allow me to save the recorded track - "Force Save" causes the recording to disappear and be replaced by a ruler tool (to measure distance), and with "Repeat" it just disappears (the behavior after "Force..." looks like a bug itself or I'm unable to understand the rationale behind?):
This problem was checked on two Android devices, both with Locus GIS 1.23.10 (I'm unable to install 1.24.x on them for unknown reason, it's not present in the store - but I have it on one other device). I'm using Bluetooth GNSS 1.0.69 app as a mock location provider (which works fine otherwise).
And to complicate things more.. On one of these devices (#1 below) the same problem is present if I skip mock location completely and connect GPS Receiver directly, using GNSS Manager / GPS Device Manager in Locus GIS. The other device (#2) was able to save tracks recorded this way without problem.
Allowing users to disable the accuracy requirement in the profile would solve the problem for strange cases like here. This makes lots of sense to me. But it would be extremely useful if the app was also able to utilize accuracy value reported by mock lock. provider.
Devices used:
1. Blackview Tab 50 WiFi (tablet, no internal GPS module), Android 13;
2. Cubot X70 phone, Android 13.