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

[Andrew Heard]

Any opinions? Maybe introduce a third time?

@Menion I'm happy with current method, but with any change I think there will be opinions for/ against
 

[Joska]

The complete time from start to stop should not be ignored, but maybe, I'd misunderstood that issue.

[Žajdlík Josef]

Total time on the track is important for all types of endurance sports such as trail running, long marches, cycling, triathlon, biathlon, etc. For all of them, the ranking is calculated according to the time spent on the track, including breaks. That is why applications such as Garmin, Strava or Samsung Health also show this time. But it is also important for amateurs. For example, when I want to look back at how long I walked the "Vandrácká 50" five years ago, I'm interested in the total time in order to estimate when I'll probably return home.
Therefore, I propose to unify the indicators with all sports applications:
track time - simply difference in time between the first and last point
track time (movement) - same as track time, but only when speed is above the threshold (around 2km/h)

[slarti76]

Currently, app compute times as:

• track time - all times between trackpoints. Breaks are skipped and not computed
• track time (movement) - same as track time, but only when speed is above the threshold (around 2km/h)

What you want is to change this behaviour to

• track time - simply difference in time between the first and last point
• track time (movement) - all times between trackpoints. Breaks are skipped and not computed

Any opinions? Maybe introduce a third time? 

I'd wouldn't mind a third time or ability to change the threshold. For hiking and snowshoeing, the "movement" times are frequently too low, as in ascent, you easily get below 2km/h.

[Menion]

@Ulrich Kiermayr
Isn't the problem with the dashboard already solved in the latest Beta version?

@WildWortWechsel
track rec button > if you have set the "Auto-hide" option for this button, it should be visible during recording, always. Otherwise, it should be visible or hidden, based on settings.

incorrect search result icon > I understand you have your own icon set in the settings. You wrote about some problems with the search system and I ask to provide some easy-to-follow steps, so I can simulate it. Thanks


Times, thanks for the feedback. I'll have to discuss with the team next week more deeply (also because we have to changes adapt on iOS and web as well).

[Ulrich Kiermayr]

@Ulrich Kiermayr
Isn't the problem with the dashboard already solved in the latest Beta version?

Unfortunately no. The bubbles are gone, but the dashboard still draws over the guidance/navigation panel, intercepting clicks.

You cannot view this attachment.

LG Ulrich

[WildWortWechsel]

incorrect search result icon > I understand you have your own icon set in the settings. You wrote about some problems with the search system and I ask to provide some easy-to-follow steps, so I can simulate it. Thanks.

Hi Menion,

from my side it was only the icon. I removed it --> Problem solved.

[Mick FU]

About times, can't find again the post, but total_elapsed_time (from start to end including pauses) is at least computed during fit file export.
@Menion
You cannot view this attachment.

[Menion]

Locus Map 4.33.0.10

A maintenance release that rounds out the 4.33 line with a brand-new local map server, a fresh online address provider, smarter sensor handling, and a long list of crash and stability fixes.

What's new

• Local HTTP map server — serve your offline maps over HTTP to another device or viewer (Expert settings). web.locusmap.app support in preparation. Online maps should work, offline only partially.
  
• Here online address search — a new provider replacing the no-longer-working Bing backend, with a reworked search screen.
  
• Per-sensor disconnect alert — optional audio / vibration warning when a connected sensor drops out. (topic)
  
• Sensor stability — more reliable handling across ANT+, BT, USB and network sensors.
  
• Custom geocaching icon packs — pick your pack directly from the UI.
  
• Gear watch add-on removed — Samsung no longer supports the platform.
  

Bug fixes

• Fixed the malfunctioning Stop button in the Live-tracking and Parking notifications.
• Several crashes resolved: the navigation menu with an external routing service, "Get location" with an unavailable source, track charts with no drawable data, and an early-startup URI error.
• Transparent state correctly restored for WMS maps.
  
• Correct altitude units in My Library.
  
• Track chart no longer swallows tap events, and chart zoom respects the selected location.
  
• Chart slope data gets stronger optimisation; weather day detail scrolls again when a chart is tapped.
• Smaller fixes: missing translations in vector theme categories, stray "Folder" label in the track-waypoint editor, pre-selected areas in online map download.

Under the hood

• Heap snapshots are now captured on OutOfMemory crashes and attached to bug reports sent within 24 h.
• Major internal migration of the Store, offline search, track editor, online map downloading, and Asamm live-tracking systems — 10+ year old code modernised. You shouldn't notice anything.

[Tapio]

400 Points shown, I turn AR on, rotate the camera a bit fore and back, along the points... LM crashes reliably.

A thought: When approaching a track from inside the library. IF chart has been clicked and then the button top right is used, map view should center on that selection, not the tracks center. Would make life easier.

[WildWortWechsel]

Hi Menion,

great job!

Rotating the phone "eats" away buttons. This happens in both directions.

Edit: the phone itself "eats" the Start/Stop button partial.

Pixel 10 pro XL
4.33.0.10