Messages

That's right, you can only scroll through the first 50 entries; you can't go any further down...

[4.33.0.1]

...
Version 4.33.0.1 (6.3.2026) - BETA channel
  -...
  - fix: track preview line width
...

Ok, for me now it is ok. Best width to recognize track on the tiny map miniatures.

POI alert on photos (see here) still there...

Today, I wanted to add photos as attachments to several points. Once again, I noticed that this is quite cumbersome and requires a lot of clicks:

1. I create a point.

2. I open it, select edit and then attach file.

3. I select "Select photo" . (BTW: Now it depends: if I select a photo directly from the system gallery, a copy of the photo is created under menion.android.locus/data/media/photo. However, if I select the photo from my gallery app, a link to the photo's storage location is set, e.g. ... /DCIM.)

4. Now I have to choose whether the photo should be used as an icon.

5. Now I want to add a description. To do this, I have to click on the pencil icon on the photo. The text input field opens. However, I cannot write my text straight away, but have to click on the pencil icon to the right of it again. (Why??)

6. Now I write the description and click on the tick.

7. Now I have to save it, but the save button is hidden by the text input field.

8. I first have to swipe away the text input field before I can finally save it.

This should be much easier:

When I select a photo, the text input field could appear directly below it, where I can write directly if necessary or leave it blank. The save button could be there immediately so that I can save the photo straight away, regardless of whether I enter a description or not.
Similarly, the selection field (photo as icon or not) could be displayed in the same dialogue box and retain the last selected status permanently until I change it.

Everything in one dialogue box would save a lot of clicks.

[@Graf Geo]

@Graf Geo
POI alert on photos > heh, funny problem. Exclude geotagged photos from POI alert? Is this a solution you always want?

Yes, ideally optional (if anyone would like to be notified when photos are taken). In any case, I don't want to be alarmed when I take a photo. 

Same on two devices. The progress bar remained stuck at 52%. On the S10, restarting Locus helped, while on the MotoE60, waiting a while was sufficient.

See here: https://forum.locusmap.eu/index.php?msg=80555

I have now tested the point notification, and it is working again.

However, I noticed a silly problem concerning geotagged photos. I have activated the point notification. Now I take a photo while on the move. Shortly afterwards, the photo icon appears on the map. And it beeps because the point notification recognises this icon as a point and alerts me. Of course, this does not make sense.

I deactivated all folders in the point notification settings. Now there should be no alarm. Nevertheless, the sound is triggered for every new (geotagged) photo. Very annoying.

Bug? Or how can this be avoided?

That depends on when they were created. Try updating them (long press on the thumbnail). 😎

[Track thumbnails Line thickness still much too thick]

Track thumbnails Line thickness still much too thick

In recent years, changes have been made to the line thickness in the track thumbnails several times. Most recently, they were actually quite optimal, even with version 4.32.4.

With the current beta (Edit: and also in the brand new 4.33, which I have just installed), the lines created are much too thick, making it difficult to see the course of the track. The circuit around a narrow lake becomes a fat sausage. The city tour becomes a thick blob of colour. 

See image.

I (Android 16) also have no crashes with the compass.

This happens when GPS is enabled. If I do not enable GPS, the application does not close.

No crash even with GPS enabled. Sorry.

I (Android 16) also have no crashes with the compass.

@Tapio: Where can I get the Locus Tasker plugin? It is no longer available in the Play Store.

@Andrew Heard: Yesterday evening at home, I created a log like this for the very first time. The logs.zip contains six txt files from the last six days (see screenshot).

I have no idea what the log texts mean, but I was able to find some of the restarts ("NEW START") I performed after crashes, as I still remember exactly when they happened. So apparently you don't have to do the reporting immediately while on the road.

(Question for the experts: am I right?)

[Point notification:]

A few more comments:

Point notification: (see ballonis post) – error confirmed, does not work.

Crashes: (see here): It happened again yesterday. I was just recording while on the move and taking the occasional photo. When I looked at the screen again a few minutes after last looking at it, Locus had already crashed. I restarted the app, the recording continued, but I had a gap of about 100 metres. 
This probably doesn't help, but I don't know if my user ID helps (eeee4156c), or if and when I should create a log (immediately after restarting?).

Route planner: I hadn't noticed the new profile management in the route planner (app). Finally, you can set whether a profile change should generally recalculate the entire route or not (checkbox at the bottom). Good!

"Best Interval" (Mick FU's post): I'm happy with the current display. I use it occasionally for my jogging routes, so I can see when I start to slow down, for example.    It's perfectly adequate for me as an overview. You can set short intervals if you want to have sections that are as accurate as possible. 

Track point time: I would also find it very helpful to be able to see the time when I was at a track point more quickly. Currently, it is really very cumbersome, as already described.

I have also recently experienced crashes since Beta 4.32.4.2.
This happened several times during track recording when I set a quick point.
A message then appears stating that memory overload may be the cause and that one should not display an excessive number of tracks and points. However, I only had a few tracks and a moderate number of points visible. Shading was off.

I will continue to monitor this.

Es ist nicht nötig, Beiträge doppelt einzustellen (englisch und deutsch).