Main Menu

Recent posts

#1
Ah, understand, thanks for the screenshot.

The label "folder" is visible by accident here. So only a "comment". And comments are visible only for the track waypoints and should be used as special text that is used in notification during navigation (a little unclear feature, even to me currently).

I can only offer to merge the comment and description into a single text. Anyway best solution is to simply ignore "comment" and use "description" only.
#2
[DE translation]
Hallo zusammen,
tut mir leid, aber das ist das richtige Verhalten. Wir sprechen hier von Vektorkarten, bei denen sich der Inhalt an den aktuellen Zoomfaktor anpasst. Auch Texte verhalten sich nun entsprechend.

[EN]
Hi guys,
sorry, but this is correct behavior. We talk about vector maps, where content adapt to current zoom. Texts finally do this as well.
#3
Ein Problem in der App. Wird behoben, danke.
#4
Promiň za chybějící odpověď k linkům ... kluci slibovali, že se na to na webu podívají, tak snad.

Ohledně "fav bodů" - koukám, že to není zase tak jednoduché, jak by se mohlo zdát. Píšu si a zkusím později, až budu mít větší čas rezervovaný pro geocaching.
#5
Relativne nedavno GS pridal k logum informaci, jestli dany log pridal ke kesi i FP bodik. Je toto v API tak, aby se to dalo u logu v Locusu taktez zobrazit?
#6
Locus Map / Re: [APP] - version 4.33.+ ( 0...
Last post by Žajdlík Josef - Yesterday at 11:30:44
Here are samples on the difference between Locus and exporting to Strava.
You cannot view this attachment.You cannot view this attachment.
#7
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Žajdlík Josef - Yesterday at 11:26:10
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
#8
[CZ&SK] - diskuze o Locusu / Re: Opět problém
Last post by Joska 000 - Yesterday at 09:28:21
Tak  jsem znovu experimentoval a stopnul jsem si čas naběhnutí apky. Stará verze 7vteřin. Aktualizace nová verze 1m40vt.  Nechám to tak. Zatím není nic zajimavého co bych v nové verzi využil.
#9
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by TrulloF - Yesterday at 08:49:49
[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!
#10
Troubles & Questions / Re: Locus Map Gold is too dark
Last post by Wolfgang - April 12, 2026, 20:56:22
Hi,
In Good Lock from Galaxy Store there is a module named Display Assistant. There is a switch Brightness Limit Profile, this can be set from Standard to Light.
I have tried this and it will work. With a table lamp directly to the brightnesss sensor there will no throttling the brightness. A test in sunshine must follow.
Greetings
Wolfgang