Re: [APP] - version 4.33.+ ( 03/2026 )

[Andrew Heard]

4.33.0.5 maps button on tracks chart: the map is not correctly positioned if the chart is zoomed in: track list > track > chart > zoom+ > tap Map button (new) > tap + icon > observe map cursor is not in correct position.

Chart zooming suggestion: if the chart has been tapped (vertical line displayed) then maintain that position when zoom+ or zoom- is tapped. At present the position is often lost after the zoom.

Chart panning: seems a little unresponsive - swipe to side multiple times but often the chart does not move.

Chart panning: with zoom+ then pan too far to right (swipe left) and the screen (sometimes) becomes blank! Not sure 100% how to reproduce yet.

4.33.0.6 Locus Store > loading... forever and/or crash confirmed.

Smooth movement: detection of "stopped" is not perfect so still some unwanted rotation, but big improvement. If settings > GPS > Map rotation mode = GPS orientation only, then with only small or no movement, can all rotation be stopped? i.e. ignore GPS jitter of +/-5m?

The slopes in the new charts have always looked larger than the old chart. I checked one @ https://link.locusmap.app/t/wtkubf which is quite flat.
WebPlanner 2.5%:
You cannot view this attachment.

same place on LM chart 8%:
You cannot view this attachment.

[Menion]

Thanks guys, nasty bug ... fixed in 4.33.0.7 (1211)!

@Andrew Heard
thanks for the feedback. I'll look at it during the next week.

[Erelen]

4.33.0.7 - crashes on start (after clean install too). Samsung Note 9, Android 10.

[Andrew Heard]

4.33.0.7 - crashes on start (after clean install too).

Locus Store working for me now

After further analysis of the thorny issue of the difference between WebPlanner & LM for display of slope - at a basic level LM is correct

Code Select Expand

lat        lon        alt (m) dist (km) slope (%)
-42.858939 147.326095 11.2    1.422     
-42.859009 147.326213 12.3    1.434     9.0
I guess LM is calculating slope (9%) point-by-point without filtering or averaging, whereas the WebPlanner must be doing some filtering and/or averaging to calculate 2.5%. I believe 2.5% is more realistic but there will, as in past? be endless debate for how it is done. I'd suggest at least the two platforms should use the same method & display similar charts though?

In my settings, for interest > GPS > Altitude manager > Replace GPS values + heavy filter, pressure sensor = off

[Agus]

In beta version 4.33.07, Lopoints photos are not visible

[T-mo]

4.33.0.7 (1211) crashes on start