Re: [APP] - version 4.32.+ ( 12/2025 )

[Tapio]

While I understand, we have two distinct views (track / point) I also think, trackpoint absolute time is of highest interest in analysis situations. Too buried rn.
And now since the map jumps and selects trackpoints when clicking on the graph, the interest in trackpoint time is even higher.
"Best interval" section, useless for me. And the waypoint representation on that screen - They could rather appear as tiny markers in the graph.

[WildWortWechsel]

Hello Menion,

since the latest beta 4.32.4.4 the App did crash several times. The last few times during a track copy procedere but also while analyzing the elevation graph.

Android 14

[Graf Geo]

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.

[freischneider]

I've never used the "Best Interval" setting. I think very few people use it. For me, it's just part of the general track data. That's where the general statistics for the track are. That also includes energy consumption, which is related to performance.

[Mick FU]

About best interval, in fact, i didn't understand really this feature (in Locus )
To me, the best interval (for example the best 1km) should be the best "moving interval", meaning the best kilometer (faster for example) over the entire activity.
But Locus is "just" splitting the activity into interval (1km for example) and then highlight the best and worth of those splits.
This is same activity split and best interval from Locus : fastest = 6km to 7km = 8:08
You cannot view this attachment.

, while the real best kilometer is 7:09, between 6km51 and 7km51
You cannot view this attachment.

[balloni55]

Hello menion,
the point notification isn't working for me. I can't say how long it's been like this, but it's been the case for at least the last two betas.
My settings are one-time notification, 20 metres, 2 beeps, vibration.
The tests in the settings window work.

[Graf Geo]

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.

[Menion]

@WildWortWechsel
your route seems to be 2k+ long  ... may you share it with me for test over track detail > bottom "Share by the link"? Thanks

@balloni55
thanks for the bug-report! Serious problem caused by the work on "Smooth movement" that also causes problems in track navigation!

@Graf Geo
Unfortunately, I do not see any error in Crashlytics. After that crash, long click on the main menu > "Report bug" and send it over email to locus.map@asamm.com, thanks! Just add not "For Menion, forum". I'm not too active on the help desk now.


"Best interval" > many ideas without any comments and now everyone (almost) considers this useless  . Later, but should be improved, agree. I was also never happy with it, but no one complained ... 
Bes