[APP] - version 4.20.+ ( 11/2023 )

[Menion]

New Locus Map (4) version

Important links
- list of news of public versions
- Public versions
- Beta versions

Versions
23. 11. 2023 - Locus 4.20.0
1. 12. 2023 - Locus 4.20.1

[Menion]

Hi guys, the new version brings a lot of interesting changes and even more on the background. I have to thanks a lot for tests most of you made during last weeks. It really helped a lot!!

Version 4.20.0 was uploaded to the Google Play, but was rejected because of some missing info in subscription screen. It will take some time to fix it, so I've at least uploaded APK to the public Google Drive directory. If anyone wants to test and use this version, feel free to do it.

Have a nice weekend!

[T-mo]

4.20.0
after closing (exit) with confirmation dialog I get the following popup after a while, some 30s or something

[jonny.blue]

Just installed the afk on my S10e ...
I can start LM4 but after 3 seconds there is no movement possible: the app stops working.

When I use these 3 sec to move to settings all screens are working. But the map screen forces the full stop.

On my (test) tablets the version is working.

[jonny.blue]

It seems as if a short time with no movement on map leads to the stop.

[balloni55]

confirm behavior "app stop"
i can reproduce it by zooming in and out

[Tapio]

Thanks. Route planner route still leaking into main screen btw.

[jonny.blue]

confirm behavior "app stop"
i can reproduce it by zooming in and out

Yes ... but only the hardware buttons produces the crash.
With touch zoom it's working.

Disabled hardware buttons till next version 😉

[jonny.blue]

next problem 

I can't use the route planner anymore.
When I start planning only one profile is offered (hiking). no bike, no car, no motocycle ...
and when entering the second point an error occurs.

You cannot view this attachment. 

[jonny.blue]

I tried to go back to 4.19 ... but an error occurs.

What could be done ?

[jonny.blue]

... and I can't reach the brouter settings.
You cannot view this attachment.

[Tapio]

Isn't it normal for external BRouter?

@Menion, I notice recording stop problems via intent, my also be a problem with Falcos plugin. Needs more debugging on my side. This happened since you announced changes to LM startup system.

Tasker log has... see screenshot. My impression is, the intent does not reliably work. The error times in screenshot match with my logging.

20231125_182745 ERR 1.54km ESM 13.12 ASM 4.06 (45bd7284)
20231125_182634 ERR 1.52km ESM 13.12 ASM 4.09 (45bd7284)

[Andrew Heard]

Thanks. Route planner route still leaking into main screen btw.

same here, no change, ~8s from exit route planner until the planned route is removed from map

@menion - this new Aspect map shading is quite interesting but could it be further enhanced with color saturation proportional to the slope? i.e. a very pale color would suggest a flatter area, and very strong color (like the current) suggest steeper areas. This would then combine the best attributes of existing Slope shading. At present even quite flat areas have strong color, perhaps too strong, and maybe defeats the purpose.

[Tapio]

Menion, the intent system seems severely harmed, this kills automation. Record start and stop, that is. IDK yet why recording didn't start today. Tasker tried like 5 times.

As for recording stop + save, I find numerous duplicate tracks in my database. What happened? The intent managed to save the track every time, but did not stop the recording. The script then retries every few minutes, resulting in multiple saved tracks 😒

Reminder - this intent:
ACTION: com.asamm.locus.ACTION_TASK
EXTRA: tasks: { track_record  : { action: "stop", auto_save: true } }

Here's a recording toggle. Checks state via Falcos plugin. Currently I cannot 100% replicate the problem.

https://taskernet.com/shares/?user=AS35m8kdcvHWol%2B4bD9OZoyveTVDShSyXj8tf68JMvG6V2sdgXJjEzBkCnCmXJtkzQ%3D%3D&id=Task%3AToggleRecordingLM4

[Tapio]

@Menion, a first finding.

- Auto pause/Rec only when moving are off
- LM app is NOT started.

Now if the "Recording start" intent is fired, the Android location icon in the top system bar appears for a short while, then disappears.

Turns out that the rec_start intent only works if LM app is fully loaded.