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

[WildWortWechsel]

Good morning Menion,

since I test the beta version 4.33.0.8 the App sometimes does not fully start. I press the App-button, it seems to start but the App "disapears" from the screen. Pressing the Android "last use" button shows the App in Startup-Mode (Screenshot 1). Selecting the App shows it again on screen, but the App did crash shortly after(Screenshot 2).

Pixel 10 pro XL / Android 16 (GrapheneOS)

[Menion]

Hi guys,
I wasn't reading your responses (just really quickly), so sorry. Will look at it next week.

Instead, on the Google Drive is another version 4.33.0.9 ... more of an "alpha". So, do not update if you are ok with 4.33.0.8 and need a stable weekend version.

Otherwise, short list of changes for the brave 

   - chg: completely new picker for locations integrated into main search view
   - add: support for custom user-defined locations in Android Auto
   - fix: AR view, incorrect points movement
   - fix: Android Auto - centering on the found point
   - fix: Android Auto - crash when starting navigation in some cases
   - add: Android Auto - "Route overview" mode during active navigation
   - fix: clear highlight of selected (track) waypoint
   - fix: crash when taking a photo to LoPoints
   - fix: minor problems in chart system
   - fix: new chart consuming tap events if not needed
   - add: support for In-app updates system (app will inform about the new version if not updated for 1+ month)
   - fix: crash when 2+ track recording widgets were used
   - fix: memory leak in scanner for BT4 devices
   - fix: memory leak in main screen panels
   - fix: crash when cache directory is temporarily unavailable on external storage
   - chg: Dashboard charts now do not display value bubbles
   - fix: wrong colors and checkbox ignoring in track overview generator
   - fix: Dashboard charts correctly use defined text color
   - chg: improved prevention of navigation on overlapping segments
   - fix: too early "End of navigation" on circular routes
   - fix: photo description/caption missing from KMZ export
   - fix: internal server error when downloading multiple Pocket Queries
   - fix: severe performance regression with large point folders (1 000+ points)
   - chg: ensure visible directional arrows when highlighting a track

[Joska]

I have observed similar behavior overall when using a dashboard; all elements below the dashboard, except for the center button, are unusable, pinch-zoom does not work, and switching between north orientation and motion orientation also does not work.

After backup, deleting LM and erasing the hole folder of LM, restarting my phone and reinstalling LM4, the above described issues are gone :-)

[WildWortWechsel]

Alpha 4.33.0.9 

Three UI issues:

a) searching a city --> a shelter icon is shown where no shelter is. I guess its the default icon I've chosen in the expert settings.

b) after changing a button in the right panel everything beside the panels is gone.

c) the new elevation chart: I really appriciate the buttons there. Thank you. Unfortunately, they are not able to zoom a long track as wide as the gesture zooms it. And, as soon as I press the + button, the zoom level jumps back to a lower zoom level.

Additionally, the GUI is slowlier as before.

[Andrew Heard]

Three UI issues:
a) searching a city

@menion - I hadn't tried Search for a while - Search > Online > Place & addresses > "glen lusk" - nearby place > only result is in Ireland half way around the world > LM super slow then crash. Screen cap below:
You cannot view this attachment.
I should have typed (all 1 word) "glenlusk" then my online search would have worked. But that is irrelevant to the crash about bogus message "too many points and tracks".

[WildWortWechsel]

Just playing around with the UI to test it and found the beta map manager again.

Changing the main menu shows it to add. See pictures.

[WildWortWechsel]

After tipping on the "Files in Folders" in the Library the numbers disappeared. They were shown at the red marker.

[Graf Geo]

Klick on the X just below your marker on the right and they are back.

[Diddi]

small bug:
I've downloaded the geocaching icon pack and selected it in the expert settings (writing the name)
It's not possible to get the standard icons back without getting n error, that the field for the icon pack name can't be empty.

[TrulloF]

[Bug] InvalidObjectException crash when tapping navigation tile with external routing providers - ACTION_COMPUTE_TRACK_PROVIDER service not yet bound

Hi Menion,

I'm developing a third-party routing addon with the help of Claude Code that registers as an ACTION_COMPUTE_TRACK_PROVIDER service. Routing and rerouting work correctly, but Locus crashes whenever the navigation tile is tapped during active navigation (or when the navigation menu is opened, e.g. from the point menu, without having gone through Navigation → Routing first).

Crash:

java.io.InvalidObjectException: Service does not return valid 'trackTypes'

Root cause:
The navigation tile/menu ViewModel enumerates all registered ACTION_COMPUTE_TRACK_PROVIDER services and calls getTrackTypes() on each one synchronously, before onServiceConnected() has fired for services that haven't been bound in the current session. Internally, the API proxy guards every call with an isConnected flag that is only set inside onServiceConnected(). If the service wasn't previously bound, isConnected is still false at call time → InvalidObjectException.

100% reproducible steps:

Install any app (e.g. BRouter) that exports a service with action="locus.api.android.ACTION_COMPUTE_TRACK_PROVIDER".
Start a navigation session without going through Navigation → Routing (so the service was never bound in this session).
Tap the navigation tile during active navigation.
Crash.
Suggested fix (Locus side):

Wrap the getTrackTypes() call in a try/catch and treat the service as temporarily unavailable rather than crashing:

try {
    int[] types = service.getTrackTypes();
    // use types
} catch (InvalidObjectException | RemoteException e) {
    Log.w(TAG, "Routing service not yet connected, skipping: " + e.getMessage());
}

Alternatively, collect track types asynchronously inside onServiceConnected() and update the UI once binding completes, rather than calling eagerly before the connection is established.

Thanks for looking into this!

[Žajdlík Josef]

I tried to write a problem with the route time on the Help Desk, but Michal refused, saying that it was not a problem. But it seems to me that this is a problem. So I'll try again here. Locus on the website and in the application does not show the entire time of the route from the start of the recording to its end, but only the time when the recording is running. It just completely ignores the time the recording is in Autopause. So it is impossible to find out anywhere how long I was on the route in total even with breaks. Details are here: https://help.locusmap.eu/topic/40053-cz-%C5%A1patn%C4%9B-vyhodnocen%C3%BD-%C4%8Das-na-trati

[Žajdlík Josef]

Here are samples on the difference between Locus and exporting to Strava.
You cannot view this attachment.You cannot view this attachment.