Messages

Not my experience. In case of Android crash/reboot I never lost a track and Locus continued recording the restored track. Happened to me ~3 times over the years.

I confirm, in the rare cases in which it happened I was always amazed how the track was then easily recovered when restarting locus.
To be sure that something hasn't changed, I did a test: I started the track and after a few minutes I switched off and restarted the device, when in locus the track is automatically resumed.

Buddy tracking is super unreliable btw, if anybody still cares about that function. It stops working at least least five times per day and we have to manually turn it off and on to see our points again.

It always happens when network reception is bad for a while. Locus seems to mess up internally and never gets back on track.

Btw... if you have code in there like

if phone.isOnline()
  do_stuff();
else
  do_other_stuff();

that might be the main problem. Once you leave your LTE development couch and travel through the real world, your phone will quite often only THINK it's online... like in zero bars 4G or even Edge. Transmitting a single byte might take ages though or come back with a failure after some longish timeout. Quite likely Locus hickups on that... maybe if the network error timeout is longer than the tracking interval? Just guessing.

And nope... we're not in rural India... we're in the mountains of southern France right in central Europe. Buddy tracking still fails plenty.

There are obviously at least a dozen other things wrong with buddy support in general. But unless the likely answer is different from "not a priority" (as for the last five(?) years), I won't bother repeating myself over and over again. Ask if you want two more pages of neccessary fixes... or just go cycling with a buddy, then you might finally notice yourself and do something about it :-)

I have experienced the LT fails so many times that I no longer use it.Unfortunately, I confirm that where there is reception difficulty, it freezes. I understand the technical difficulties and now I turn off data reception to save battery life.I prefer a tried and tested system I made with tasker based on text messages only, using only the telephone network is very reliable. The applicant asks for the position and the phone answers.

https://taskernet.com/?user=AS35m8kc9lYIafma1bmhSsdc5aW41wXP5NeuM1RwE0hptzS4hAh4n%2Fj3ZJVJ%2BEksDoEnzn7H%2FxM%2BAQ%3D%3D

Hello, in the daily forecast detail panel it would be useful to have a link to the next and previous day at the bottom, avoiding having to go back to the main forecast menu each time.

Hello,
"add: option to hide all other tracks except the currently active one"
useful, but a little too hidden in the track menu under tools, an icon on the track info header would be better.

Be aware that if you use my attached icon you have to pay me the rights 

But isn't "search this area" exactly this? Or do you missing it even for category highlighting?

I usually use a zoom that allows me to see a very small area on the screen because I prefer to see the details.
So when I do a search as the area is small I get few results as they depend on the zoom. I would prefer to set up the search with a filter of, for example, a fixed radius of 5 km. So I would always have the list of found items regardless of zoom.
Or
You could show on the map the elements found that obviously fit on the screen, but also list those that don't fit in order of distance.
So if in the list I see what I was looking for that is outside the on-screen map, I can click on it without having to zoom out on the map and be directly centered to that point

A filter could be introduced to limit searches to a radius of x kilometers.
We thus avoid useless occurrences of results that are too distant both on the map and in the list.

@lor74cas It is correct behavior - this just indicates directions of results outside of your map while you can be anywhere else in the real. We plan to add distances from GPS position to the list of results bellow the map.

IMHO It's not what I would have expected.
If the search is done from the center of the map or from the GPS position, it is from that point that I would like the distance to be measured.

Hello,
The distance shown in the icon does not refer to GPS location or cursor, It seems the distance form screen border in mt.
Is this the correct behavioir?

For me, track recording is 4%, and optional navigation increases that to 8% (total). Will depend completely on battery size & condition & screen brightness. I therefore (mostly) never use navigation, and simply turn on the screen briefly before any potential turn. I find looking at the map far more informative & reliable than turn instructions. I have the screen timeout for 6s. Sometimes I use POI alert but to replace navigation commands would be very tedious if lots of turns.

I agree with Andrew.
In addition to keeping the consumption of Locus under control, it is also necessary to reduce that of the device.
If you don't need to be contacted by phone, you can put it in airplane mode.
If, on the other hand, a telephone connection is needed, but it is possible to give up the internet connection, data connectivity can be disabled.

I "relaxed" the policy towards permissive access in hike and bike

Yes confirmed, on the web planner now is available.
Thank you

4 months and 3 versions ago I reported this issue with the planners
https://forum.locusmap.eu/index.php?msg=69978
still not solved

Military road
access = no
but ...
foot = permissive
https://www.openstreetmap.org/way/220542005

I also allowed her to poll my position. Ie, she sends an SMS to me, my phone then sends position SMS in return. From what I understand this is what you also do.

Yes it is, but I like also your way. ICE it's a correct approach.

The reason is currently pretty simple. We do not have (yet) a system for the automatic distribution of 1' files on mobile devices. Because of this, web and also LoRouter data are computed with 3'' SRTM data > to make it "wrong" identically on all platforms.

Btw. did anyone notice the "Altitude threshold" parameter in the track edit screen? I'm experimenting with this value. For now, this may be set only for single route. Automatically is used value 5, when using SRTM data it is equal to 3.

For my use, the app and the PC are two separate worlds that communicate with each other thanks to the cloud.
On the app, to avoid memory saturation, I would be inclined not to install the LIDAR data (only let expert and aware users do it) while maintaining the updating of altimetric data as it now happens in an automatic and precise way.
But the web server doesn't have space problems, so it could contain LIDAR data where available, updates can also be made periodically based on communications from Sonny.
You could also add a feature like this:

• in Locus, in tracks settings an option "update altitude automatically during cloud sync"
• tracks are sent from the app to the cloud where the altimetry is reprocessed and then sent back to the app with a flag or description indicating that the altimetry has been reprocessed
• if you don't want an automatism, you could add an item to the already present "update altitude" in the tools with an "update altitude in cloud"

If then the problem is that of having two instruments that return two different results, just put a link on the web planner that explains what and how the altitude is calculated on the web and on the app.
Obviously it would be good to specify that it makes little sense to use a 1' reticle if you don't have a gps accuracy filter set at least below 50mt, preferably under 20mt.

[@lor74cas]

@lor74cas
...
because with the switch to android 13, I can't place them in the folder.
...

I just tested with x-plore on Android 13: even on EXT SD, this app can write to the private folders of /Android/data.
BTW: 1" alone is not delivering better results per se; only 1" plus LIDAR (Sonny's DTMs) will do.

HI,
I finally managed to install the 1" hgt files plus LIDAR (Sonny's DTMs) and they really make a difference.
To get around the problems accessing the srtm folder, I copied the files from the PC with adb by connecting the mobile phone to the PC with a USB cable.
There are several hurdles here as well:
you must have adb installed
You must have developer options enabled on your phone
you must have a good usb cable
you need to authorize the phone to connect
and you need to locate the full path to the srtm folder
but if you already have all or most of what you need then everything is resolved in a single command:
adb push /home/lorenzo/Scrivania/hgt/*.hgt /storage/self/primary/Android/data/menion.android.locus/files/Locus/data/srtm

I am more and more convinced that the webplanner must have 1" plus LIDAR data (Sonny's DTMs). There is too much difference between what locus compute with LIDAR data on the same trace computed on the webplanner.
If, for reasons of occupied space, it is reasonable that not all the 1" data be downloaded to the mobile phone, but only those of the most used areas, I don't see why on the server hosting the palnner it is not possible to have this data for all areas where they are available.

For me it is so that Strava currently always shows more altitude than Locus. Yesterday I had in Locus 905 hm and in Strava 1022. Use the Current Beta
Small differences should already be taken into account. Only unrealistic jumps should be filtered out. E.g. 3 hm within 3 meters.

Different algorithms for calculating the height difference can obviously give different results, but the top of a mountain must have the correct height regardless of the algorithm.