Messages

[@michaelbechtold]

@michaelbechtold
offline wikipedia is not even planned. Anyway, many places are already integrated into our LoPoints, as you wrote. I've already asked @Radim V , if Wikipedia in the app may be removed completely, and I was told no. Currently, only articles that are directly registered in the OpenStreetMap are included. But there are many places, that do not have this record.
Some clever detection is planned...

@Sup
DEV version. Sorry, it is the second time, this version was uploaded by accident to the Google Drive. Ignore it.

@Tapio
small nav. button > yes, duplicated functionality, because many many people do not know that the top panel is clickable!

[Beta version for the weekend 4.29.0.1]

New Beta version for the weekend 4.29.0.1 (17.4.2025)

Changelog
   - chg: Android Auto is now working for none-Premium users for 60 minutes daily
   - chg: closing My library by back press from restored folder
   - chg: restoring scroll position when return to MyLibrary folder during open
   - chg: (SILVER) full rework of the Wikipedia search > design unite with new search system
   - chg: major background rework of online Lopoints re-loading
   - fix: incorrect display of tile-sizes for local maps
   - fix: incorrect restore of track segments upon re-route of saved route

You still miss my responses to some posts, sorry, next week!

Není, nic se tu neměnilo. Prosím o kontrolu v nastavení apky, kde se formát souřadnic vybírá.

There is currently a plan (will be done in the next months) to "PIN" certain categories and highlight them on the map. This should probably solve issues like this.

Hi guys,
sorry, this is not possible.

There were no changes in the router itself. Could you please provide a link to the route that does not work or at least a screenshot where this problem is visible? Thanks

Hi tkansgar,
thanks for bringing this topic up. You are correct, that lines are now too thin. I've modified inner code a little, so the next version should prevent too thin lines. Let me know once 4.30+ will be out, if all looks ok now. Thanks.

Yes, the entire map screen is considered. Panels do not make a difference here. They are very dynamic, and everyone may set quite a different UI, so taking them into consideration may be problematic.

Hello, already reported and I believe, my colleague should be working on it.

Hi guys,

since the last version, I've spent a lot of time, mainly on various memory and performance optimizations. I hope the app will be more stable and sometimes even a little faster.

A new version 4.29.0 just published (today for 10%, more later).

Meanwhile, I've tried 3 versions with the Android Auto > no success so far  . No comment ...

[Locus Map (4)]

New Locus Map (4) version

Important links
- list of news of public versions
- Public versions
- Beta versions

Versions
10. 4. 2025 - Locus Map 4.29.0 (10% of users)

Zdravím,

zajímavý nápad. Nic takového v Locus Map není. Náročnost výroby střední, jen si nejsem jist přínosem. Alespoň z vlastní zkušenosti mám raději celkový přehled a k šetření baterie doporučuju spíše automatické zhasínání displeje během navigace. Nicméně rozumím, na AMOLED displejích tohle černé provedení může opravdu něco udělat.

Hmm, skoro to spíše zavání nějakou černou verzí mapového tématu.

Zdravím,

jak se tak dívám, tato a dlaždice pod tím se zdají vadné a na tom se stahování sekne. Je tedy nutné nahlásit Martinovi (správcovi webu) s touto informací.

Dlaždice
https://outdoor.tiles.freemap.sk/16/36260/22512@3x

Hello Michael,
I've removed your private post on the help desk, so we should have this info public.

As my colleague Radim is intensively testing Android Auto on the motorcycle and is also using a hardware controller, I'm pushed from more directions. So yes, I plan to support hardware controllers in this way. Currently, I'm still stuck on publishing Android Auto support itself on Google Play, so this feature will have to wait for now.

The best is to add ideas to our help desk with "android auto" tags, like these: https://help.locusmap.eu/search/tag%3Aandroid+auto . It also allows more users to push on me with specific requests, which is always welcome  (and usually necessary).

I'm unable to simulate it, btw. thanks for the report.

If possible, try it with a version I'll prepare today. There are some changes how internally bottom point panel is handled, so maybe it is already fixed as a side-effect, thanks!