Messages

[The user may want to export to multiple files.]

I noticed, in case of Export multiple Points, the checkbox "Export to single file" is missing - it does always export to one file. The user may want to export to multiple files. Currently impossible.

Menion, I think the "configuration only" backup is lacking important and time consuming user configuration works... and should be included IMO:

/data/presets
/data/dashboard
/router/profiles2

I was surprised you didn't include them. I was expecting it to backup "all but the point/track databases".

I would not be so strict with "does not get any new features anymore"  . As visible in the changelog of every version, I still do a lot of modifications also in the Classic version. But to be true, by intent I try not to add bigger new functions to the Classic.

The new version will be published probably at the start of December. Google forces us to do a big update in internal libraries so I need a little more time to test the app and fix a few more problems that appeared (mainly on Android 13).

Thanks for understanding guys.

Thx for working on auto pause. Do you use some kind of shake sensors for this? Because Locus asked for Android access.
Please consider an option to auto add a waypoint upon pause end, at pause start position, with pause length info...

I found problems.

1. On track recording + navigation, embedded WPs are added here from outside, via intent. They are visible on the track. But it's almost impossible to tap those WPs. As if there is just one pixel tap area. I think it worked before.

2. Screenshot. Navigation of a track x. Locus then shows track x PLUS the upcoming navigation. Useless? At least a problem with distance markers.

And does it make sense to select for caches with "no sizes"? "Nothing selected" is always considered equal to "all selected".

Extra options > I'll look at it.

@ta-ka
One user reported that a new change in "jpg" in Onboard calibrator broke his new maps. He uses semi-transparent PNG files as a source images. I was firstly thinking about extra optional settings, but maps from photos are so small, that I think it does not worth it. So sorry, in the next version, PNG will be used again. Thanks for understanding.

LMC=3
Diesen Button "Einstellungen" gibt es bei der 3er Version nicht.

Definitely works, starting/stopping recording, with save/without is something my Tasker triggers daily a few times.
I'd guess as for actions Tasker Plugin just translates UI into intents.

@Menion, removing Intents, i. e. Locus Action system at some point, pls comment?
Feeling no itch to rework my numerous tasks.

The site https://www.locusmap.eu/ is down.

I've noticed the Locus sites (this one, maybe others) sometimes don't load, I think due to DNS failure.  Then I try again, and it works.  I don't know what's happening there; it's been that way for months, and other sites aren't a problem for me.  (My DNS is provided by the VPN service I use.)

EDIT: ...but right now, I can't connect to https://www.locusmap.eu either.  Seems to be a different problem, because it's just waiting (ultimately PR_CONNECT_RESET_ERROR), whereas the problem I mentioned (which I consider minor) is always an immediate error.

This is an alternative to the Locus default live tracking, it displays more information and shows the current recorded track as well as the planned route. It also queues all information while offline and sends it to the server when back online.

It will record the current position from Locus every 10 seconds and every 10 minutes it will toggle airplane mode off, try to send the data to the server and then toggle airplane mode back on. This of course is all easily configurable in the scripts.

The server side scripts was based on uatschitchun's code.

The Locus-Addon-Tasker I'm using is a fork of Falcosc's with a few bug fixes and updated to the latest Locus API, I think you could get this working with Facosc's version as well, you would just need to modify the scripts where it queries the API for the GPS accuracy as the latest API version has split the accuracy into vertical and horizontal components.

If anyone wants to give it a go here are the projects:
GPSTracker server scripts
My Locus-Addon-Tasker Fork
Tasker project file

It does require quite a bit of technical knowledge to get it setup though so I do not recommend it for the faint-hearted. It involves setting up a website, compiling and installing an android app and configuring Tasker scripts.

Ich denke es geht hier weder um Kreativität noch irgendeine geldgierige Verschwörung:
- technisch gesehen gibt es einen gemeinsamen Kern beider Versionen - das ist bei einer kleinen Firma wie Asamm nötig (und selbst bei größeren sinnvoll)
- falls / solange die SW-Architektur eine klare Trennung erlaubt, was bei Locus der Fall ist.
- Innovation (jenseits des gemeinsamen Kerns) kommt in der UI und mit extra Features - logischerweise nur in der neuen Version
- Die Umstellung von Einmalkauf zu Subskription ist eine Überlebensfrage in dem Moment wo monatlich Gehälter gezahlt werden müssen, denn dieser spezielle Markt wächst nicht mehr schnell genug (allenfalls in der anderen (Komoot-) Ecke).
- Ein halbes Bier pro Monat sollte niemandes Blutdruck steigen lassen, oder?
- Und ich sehe keinen Hinweis, dass Locus Classic verschwindet (wegen s.o.)

Half a beer per month you call expensive?
Re. full screen: same behaviour for both versions.

Hi @settler, thank you for question.

Fullscreen mode was added to Locus, when Android did not support translucent status bar and navigation bar. Both system bars were pinned to the screen without possibility to style them. The only option was to hide them to increase space for application (fullscreen mode). Over time, options to style system bars were added and also from 2018 there are many devices with notch, which are unusable with fullscreen mode, because some important UI elements are hidden behind notch. So we decided to delete fullscreen mode from application and improve UI in map screens, so the map is properly visible behind system bars in both orientations. On the other screens, fullscreen mode does not make sense at all.

Hi,
the changelog states "automatic loading of fresh info for offline LoPoints" . What is meant by that?
Any chance that it fixes the issue that sometimes prevents the Offline Lopoints from loading (as described here : https://forum.locusmap.eu/index.php?topic=7527.0 )?
It seems to happen less often now, but just last week I ran into the issue again.
Suddenly the LoPoints disappear from the map and when you click on "LoPoints (offline)" they don´t come back.
Also the selection doesn´t stick, so when you go back to the "Map-Screen Content" screen the offline LoPoints are not selected anymore. The Online Lopoints can be selected and work.
Restarting the App does not help, but at some point it just starts to work again. I can´t see any pattern for this behaviour.
I was using the "Germany South" map (dated September 2021).

Keep up the good work!

Edit - corrected some typos.

@freischneider that is not true, I read all topics and posts (except the German thread)! It just sometimes takes me a day or two because of work here and there I have to do (sorry for this delays).

Guys, I spend on this more than a day last week, and in the end, I've found this! It is a problem in the Google library.

Fortunately, at Friday, a new version of the Google library was published so I've immediately updated quite a lot of code and published version 1.5. Well... 7th attempt to publish a new version ended with Google team message: "It is not possible to install on the device". Wtf. My request for detailed info from Saturday > no reaction so far.

Anyway, you may try version 1.5 from Google Drive. It works correctly on two watches we have for testing and also emulator so I believe there is no problem at all. Feedback will be anyway welcome!