hi~
Mock location app is used in the locus map club with many people.
After upgrading to version 3.71, use Mock location app to receive gps data and run locus map, which breaks the signal in between.
It works well in version 3.32.
I need a solution, please.
Have a nice day.
The same problem 
Hello,
may I ask what device and Android version are you using? You tried version 3.32 right now and no problems? if so, is it possible to enable NMEA recording (in app settings > GPS > record NMEA) and after some testing, send us NMEA file found in Locus/data/nmea? Thank you!
Menion
Hello,
may I ask what device and Android version are you using? You tried version 3.32 right now and no problems? if so, is it possible to enable NMEA recording (in app settings > GPS > record NMEA) and after some testing, send us NMEA file found in Locus/data/nmea? Thank you!
Menion
The device in use is Samsung s 10.
The Android version is 10.
It's good to connect to the Bulutus gps.
The device in use is Samsung s 10.
The Android version is 10.
It's good to connect to the Bulutus gps.
Hello,
thanks for the NMEA message. Seems to work correctly on my device.
If you will have a moment, I've prepared a special version that will print out various information into log.
APK for download is here: https://asamm.myqnapcloud.com/share.cgi?ssid=0879TzH . It is special Free version, so you may keep Pro version as is.
After install, enable the expert menu by long click on the main app menu (more here https://docs.locusmap.eu/doku.php?id=manual:advanced:customization:config#expert_settings ).
Than in settings > expert menu > enable "Logs to file" (at the end).
Since that moment, app should log various GPS information into a file stored in Locus/logs. So try your GPS and if the result will be same, send me please file(s) from this directory. Thank you.
Hello,
thanks for the NMEA message. Seems to work correctly on my device.
If you will have a moment, I've prepared a special version that will print out various information into log.
APK for download is here: https://asamm.myqnapcloud.com/share.cgi?ssid=0879TzH . It is special Free version, so you may keep Pro version as is.
After install, enable the expert menu by long click on the main app menu (more here https://docs.locusmap.eu/doku.php?id=manual:advanced:customization:config#expert_settings ).
Than in settings > expert menu > enable "Logs to file" (at the end).
Since that moment, app should log various GPS information into a file stored in Locus/logs. So try your GPS and if the result will be same, send me please file(s) from this directory. Thank you.
The beta version is the same thing.
This is when you use the mock in the locus.
https://drive.google.com/file/d/1pa_dhF2buxgxUFL47ACOEAiIIqmg7Quv/view?usp=sharing
The beta version is the same thing.
This is when you use the mock in the locus.
https://drive.google.com/file/d/1pa_dhF2buxgxUFL47ACOEAiIIqmg7Quv/view?usp=sharing
This is what it looks like when you use external gps (BT).
https://drive.google.com/file/d/1oAPitu9pyHM4BfgF7ufV0Gr6R-CVoE9k/view?usp=sharing
This is what it looks like when you use external gps (BT).
https://drive.google.com/file/d/1oAPitu9pyHM4BfgF7ufV0Gr6R-CVoE9k/view?usp=sharing
(MOCK) Using APK (droger-gps) in (locus)
Receive gps data
https://drive.google.com/file/d/1JorDj7-swhICyAxlzAKjTsm4zUp0CLjm/view?usp=sharing
(MOCK) Using APK (droger-gps) in (locus)
Receive gps data
https://drive.google.com/file/d/1JorDj7-swhICyAxlzAKjTsm4zUp0CLjm/view?usp=sharing
(locus) Logging history.
(locus) Logging history.
Hello,
thanks for the video and log file.
So in case of direct connection to BT device over Locus Map (without using droger-gps app), it works correctly without any problem? From the second video, it looks that connection is stable.
In case of using mock location, I only see that accuracy value is switching between 0m and 4m. As I see in logs, this is correct behavior, see these values. For unknown reason, mocked location change accuracy between these two values.
What about your location on the map? Is there stable blue circle/arrow that indicate valid GNSS fix?
Menion
Hello,
thanks for the video and log file.
So in case of direct connection to BT device over Locus Map (without using droger-gps app), it works correctly without any problem? From the second video, it looks that connection is stable.
In case of using mock location, I only see that accuracy value is switching between 0m and 4m. As I see in logs, this is correct behavior, see these values. For unknown reason, mocked location change accuracy between these two values.
What about your location on the map? Is there stable blue circle/arrow that indicate valid GNSS fix?
Menion
When we start BT GPS with Locus Map on same position, it's accuracy is 0.8m~1m.
Accuracy 1m was shown from 3.2 version but 0~4m shown on from 3.7version.
When we start BT GPS with Locus Map on same position, it's accuracy is 0.8m~1m.
Accuracy 1m was shown from 3.2 version but 0~4m shown on from 3.7version.
(Korea osm.map Approximately 3GB)
(Korea OSM.DB approximately 900 MB)
It is self-produced and used.
There are about 820,000 LO POINTs.
Also, the road name address of Korea is perfectly expressed.
Korea's hiking trail is made of BROUTER.DB.
I will share it with you if you review it.
The map of Korea cannot be leaked overseas, so you can only review it.
(Korea osm.map Approximately 3GB)
(Korea OSM.DB approximately 900 MB)
It is self-produced and used.
There are about 820,000 LO POINTs.
Also, the road name address of Korea is perfectly expressed.
Korea's hiking trail is made of BROUTER.DB.
I will share it with you if you review it.
The map of Korea cannot be leaked overseas, so you can only review it.
Android version 6.02 does not cause problems.
It's working fine.
This problem only occurs in Android version 10.
Is there a solution?
Android version 6.02 does not cause problems.
It's working fine.
This problem only occurs in Android version 10.
Is there a solution?
Hello,
unfortunately, I'm still not sure from your description, what is the problem. I miss the answers to my previous questions. If the problem is really only accuracy value, nothing more, than, based on the log, it is not a problem on the Locus Map side!
In case, accuracy value is correct on Android, you may try to disable Settings > GPS & sensors > Google Services assisted location. This may cause app to use little bit different source of mock location.
Menion
Hello,
unfortunately, I'm still not sure from your description, what is the problem. I miss the answers to my previous questions. If the problem is really only accuracy value, nothing more, than, based on the log, it is not a problem on the Locus Map side!
In case, accuracy value is correct on Android, you may try to disable Settings > GPS & sensors > Google Services assisted location. This may cause app to use little bit different source of mock location.
Menion
We use handmade gnss receicer which accuracy shows less than 1m error and it is connected to Locus Map not only by BT connection directly but also using mock location assist application.
Once GPS signal fixed it's location, the accuracy less than 1m is constantly kept during track recording.
Before 3.47 version, this kind of phenomenon is not happened.
I think there might be something different between before 3.47 and after 3.47.
If you can compare your Locus version what is different between old and new, it will be much appreciated.
I consider to send my gnss receiver to you for your confirmation.
Hope your kind efforts to solve this problem.
But after upgrade 3.47version, when we use mock location service ,
the accuracy less than 1m changed to 4~5m for a moment and back to it's original accuracy .
Recorded track also shows wrongly indicated point on the track.
We use handmade gnss receicer which accuracy shows less than 1m error and it is connected to Locus Map not only by BT connection directly but also using mock location assist application.
Once GPS signal fixed it's location, the accuracy less than 1m is constantly kept during track recording.
Before 3.47 version, this kind of phenomenon is not happened.
I think there might be something different between before 3.47 and after 3.47.
If you can compare your Locus version what is different between old and new, it will be much appreciated.
I consider to send my gnss receiver to you for your confirmation.
Hope your kind efforts to solve this problem.
But after upgrade 3.47version, when we use mock location service ,
the accuracy less than 1m changed to 4~5m for a moment and back to it's original accuracy .
Recorded track also shows wrongly indicated point on the track.
Hello guys,
I'm checking the provided information for the second time and unfortunately, I'm unable to find out any reason for this "visible accuracy" problem on your device(s). For now, I'm unable to simulate this problem and I see no issue in the app code as well, sorry. Based on log created by Beta version, accuracy values are already delivered to the Locus Map app, so the issue seems to be in mock provider itself.
Menion
Hello guys,
I'm checking the provided information for the second time and unfortunately, I'm unable to find out any reason for this "visible accuracy" problem on your device(s). For now, I'm unable to simulate this problem and I see no issue in the app code as well, sorry. Based on log created by Beta version, accuracy values are already delivered to the Locus Map app, so the issue seems to be in mock provider itself.
Menion
Replies have been locked on this page!