Messages

navigate from a selected point > what exactly does not work? Thanks

If, while moving towards the selected route point, another route point is closer, it will become the destination.

I'd also like to remind you that the "navigate from a selected point" feature hasn't worked for a long time. I doubt it ever worked at all.

MapGooglePlayAfa_4.31.3.10_1195_beta -
I updated to the latest test version (Honor 20 phone, Android 9). The app keeps crashing when trying to perform various functions. The restore error from backup persists. I saved the Locus and Logcat logs.

version 4.31.3.5 - 4.31.3.7

When I try to restore data from the backup, I get a UUUPs
On my Honor20 (Android 9) phone, I tried to restore data that was saved on my Samsung A40 (Android 11) phone. This has always worked.

version 4.31.3 release -
The recovery completes without errors, but not all information is recovered, for example, the mapItems folder is not recovered.

I use the Afa version

After Menion explained the priorities, the logic behind using the "straight ahead" navigation command became clear to me. I hadn't known this before, which was why I'd been so clumsy when planning a route. :-)

Will have to test it more precisely during the weekend

I tested the new version on two phones in GPS emulation mode.

1. "Straight ahead" commands are still generated at every small intersection. This is bad.
2. Navigation commands at major intersections no longer disappear when recalculating the route. This is good.
I plan to ride my bike for the next two days. I'll be using it extensively in real-world conditions.

https://drive.google.com/file/d/1BHyOoZ-rhACUb1MSE5HZTwNtDdJdnKc4/view?usp=drivesdk

I tried creating a route that took into account the shortcomings described. And it didn't work; everything worked perfectly.
But two days ago, I created a route in the planner several times, and each time there were shortcomings.

This got me thinking. But this morning, I remembered that I had automatic route recalculation enabled, and while driving, the route automatically recalculated. I repeated the steps for creating a route in the planner, then enabled route guidance. After that, I performed a manual recalculation. All navigation commands disappeared.

And one more thing. Now the navigation says "Straight ahead" at every intersection. This didn't happen before. It's incredibly annoying. It seems obvious to me that you should go straight unless you're told to turn.

4.31.3.5.
When plotting a route in the planner, navigation prompts sometimes get missed. This sometimes happens at certain important intersections.
I also noticed that the route might include stairs.

I'm not into those overlays.

I disagree with you. Locus's ability to create a calibrated map is simply unique. I don't know of any other phone apps with this feature.
At night, by the light of my bike's headlight, I take a photo of the sports map with my phone and within 5 minutes I'm confidently heading to the checkpoint using the linked map. :-) It's simply a miracle.

a) Look if you can control it via sending an intent from Tasker to LM4. https://github.com/asamm/locus-api/wiki/Action-tasks-(Broadcasts)

I know this document by heart. :-)

b) Can you control them via presets (I don't think overlays are in)... Presets can be run from Tasker.

there is no such possibility

c) Tasker plugin has some more possibilities, but that is rather on the data retrieval side (from LM to Tasker)

This plugin does not use Locus's internal libraries and will not solve the problem.

A little history of the issue here: https://help.locusmap.eu/topic/38879-showhide-active-elements-with-one-action

I tried to solve this problem directly using Tasker by pressing "input tap x y" three times. I managed to do it with just one tap, but it's terribly slow :-(

Does anyone know how to solve this problem using Tasker by directly calling Locus functions?

You must realise Locus has got so many options it's not easy to find stuff sometimes.

You need to disable the side key screen lock in your phone settings.
To make this work, go to your phone's settings, then screen lock settings, and disable the "Side button lock" option. You can then control your phone's locking using the "Auto-lock when screen off" setting. If you use Locus, set the "Auto-lock when screen off" setting to the maximum time. You can set it to 10 hours using Tasker. If you don't use Locus, set the "Auto-lock when screen off" setting to 0 seconds or another convenient time.
With Tasker, you can fully automate this process, eliminating blocking issues. Locus and other apps will always be available.
In Android 15 (Security & Privacy - Device Unlock - Gear - ...)

is there a way of doing this without having to use biometrics/passwords

This will also allow you to switch between apps without locking the screen.

As a temporary solution, when using Locus, in your phone settings under "Lock Screen - Secure Lock Options," try disabling the side key lock and setting a maximum auto-lock time. This will allow you to turn on the screen without any issues, while your phone's security settings will still work as before. If you're familiar with Tasker, you can automate this process.

"Hardware controlling plus" ver 2.

We use Tasker to extend the remote control capabilities of Locus using any Bluetooth device. For example, Wireless Bluetooth remote control on the steering wheel  - like this or similar. You can even use the headset buttons :-).

Locus is controlled by single/multiple/long pressing of buttons and depends on the screen state and selected usage modes.
For example, when the "in pocket" mode is set, it is possible to use the phone "blindly" and move along a complex route for a long time only by voice commands.

Description of features

The project itself can be downloaded here.
The project successfully works on Samsung A40 Android 11. ROOT is not required, but you will have to enable WiFi ADB.

Version MapGooglePlayAfa_4.31.0 RC1_1188_beta.
Automatic and manual backups do not work.

Logcat:
https://drive.google.com/file/d/10__Lq5vZ8VO4aCO1CE2Pv9a905P7EhgD/view?usp=drivesdk

Recovery works at the same time.

ERROR:
Settings - search - "preset" - Connection with presets - Preset settings = restart Locus
Tested A7 and A10.