Messages

Hier meine 2 Cent. Ich nutze Locus nun seit mehr als 10 Jahren. In der Zwischenzeit habe ich eine Menge anderer Apps ausprobiert inklusive der bereits hier im Thread genannten.
Ja, Locus hatte schon immer Fehler, die mich teilweise an den Rand eines Nervenzusammenbruchs gebracht haben, aber ich bin immer wieder zurückgekommen.
Keine Navigations-App lässt mich so viel personalisieren und anpassen, wie Locus. Punkt.

Problem is fixed with the latest build. Great work. Now I can route with my TomTom-addon in Locus and use traffic information to avoid traffic jams. That was the only thing missing for me. Thanks to Claude Code... 😊
By the way, if you enabled Google location services in GPS & Sensor settings, but have only MicroG installed, GPS position will be found but the GPS icon stays yellow and position doesn't follow during routing, even though the signal is strong. Only disabling this option fixed it for me.

Thanks for looking into it. BRouter, if installed as separate app is also affected by this bug. It crashes Locus, if you try to plan a route or try to navigate from the point menu. Because BRouter is now integrated into Locus Map, probably nobody noticed.

Hi @TrulloF
Nice to see someone playing with the API! To be honest, this API functionality is not used by any addon, so it is, as you see, not well tested.

Anyway, in this case > issue found and should be fixed in the next (Friday probably) version.

[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!

I have a problem with themes using transparency. If areas are drawn with transparency (doesn't matter if using transparency with area or line colors or svg graphics, whith transpareny) I get visible tile borders, which is pretty annoying and ugly to my eyes. Happens with internal theme too (look at forest areas), but mainly with smaller maps. Germany North isn't affected by this, but for instance Brandenburg or other counties. Seems to me like a rendering bug. If I stop using transparency in my theme the tile borders are gone.

Danke, aber das ist leider nicht das vollständige Theme, sondern nur die XML für Vectormaps ab Version 4. Die reicht leider nicht aus, um das Theme a
in Locus zu verwenden. Trotzdem Danke für den Hinweis.

New beta, release notes aren't displayed at the top. Then I went to the menu under App Info. As soon as I click on Release Notes, the app crashes.

confirmed

same

here too

When trying to open a poi > fc

Here too. Reverted back to previous version. It's good, that you removed it from Google drive. It's not usable at all.

New version crashes immediately when tapping a search result in LoSearch (Xperia XZ1 Compact, Android 12).

Hallo zusammen,
hat jemand noch das alte Waymark Theme im Einsatz? Falls ja, würde ich mich sehr freuen, wenn Ihr das hier posten könntet. Danke im Voraus für die Mühe. 🙏

It happens to me regularly.

Same here. Routing data gets updated without any problems for me and there's a message every time it's done.

In the latest beta version theme defined icons don't get drawn on map, if you activate map rotation. If map rotation is off, they get drawn again. Doesn't matter if the icons are png or svg. This doesn't affect LoPoints. They are shown with and without map rotation activated.

LineSymbols are back again in latest beta. Thanks.
Wrongly calculated line decorations with dy-values are still there.

Straight lines are less problematic and it doesn't matter if you use curve="cubic" or not for the lines. Problem remains the same.

The missing line symbols for cliffs are a rather new phenomenon I think.

[@TrulloF]

@TrulloF
- missing clifs and some other line symbols > it is starting to be complicated. Anyway will be fixed, thanks.
- problem with dy offset > it is important to me, if this started to happen now with the latest version or not. Do you know?

No, it's a long standing issue present since pre LM4 😊.

@Andrew Heard
- impossible to do, sorry. Both lists are based on completely different technology and it is now hard to merge them. Anyway, have you tried the online base search (in latest app version) and here write "backup"?