New Locus Map (4) version
Important links
- list of news (https://help.locusmap.eu/announcement/locus-map-android-version-4-32-122025) of public versions
- Public versions (http://bit.ly/lmVersions)
- Beta versions (http://bit.ly/lmVersionsTest)
Versions
3. 12. 2025 - Locus Map 4.32.0
12. 1. 2026 - Locus Map 4.32.1
19. 1. 2026 - Locus Map 4.32.2
Hello to all,
This one was long. And the game is not at the end. It took us almost two months till we satisfied Google Play requirements > system for Edge-to-edge (app UI control also status, and navigation bar) and the new requirement for native libraries, that needs to be compiled with special parameters.
Unfortunately, we are now completely blocked on the Google Play. AAB file can't be uploaded and the Google Play support team is still answering "We are looking at it". So not just the Android Auto is blocked, now also the whole app.
So, because I believe, the latest 1198 build is very stable, it has been uploaded into the "Release" folder on the Google Drive. Consider this as first official release out of Google Play :) . Hope the last one ...
Sorry to read your news @menion. Huge release based on release notes/ huge # changes. The Edge-to-edge is working nicely on my Samsung A35 with A16.
Just letting you know I installed 4.32.2.1 auto and the purchased USGD John Thorn maps don't load. I reinstalled the Google play version, downloaded the John Thorn maps again and the maps worked as expected.
Thank you
Sorry for bringing up dashboards again. Just to be clear: almost all dashboards are now displayed differently (i.e., almost broken) than in 4.31 and earlier.
Of course, I understand that compared to the enormous work involved in migrating to sdk35 (including edge-to-edge and 10 yeard old libraried update), this is really a minor issue :)
I'll patiently await a fix. And good luck with Google Play!
Quote from: Erelen on December 06, 2025, 04:31:43almost all dashboards are now displayed differently (i.e., almost broken) than in 4.31 and earlier.
@Erelen - what is broken? I did a quick check & all my (4 most common) dashboards display as expected in the editor.
Not sure if that's new, but I'm trying to edit the attached GPX after importing, and whatever I do, Locus crashes. Some operations (Delete all before) crash it already in the editor, all other when closing the editor.
For comparison, I edited another track recorded by Locus itself, that worked fine.
Quote from: Andrew Heard on December 06, 2025, 04:57:52Quote from: Erelen on December 06, 2025, 04:31:43almost all dashboards are now displayed differently (i.e., almost broken) than in 4.31 and earlier.
@Erelen - what is broken? I did a quick check & all my (4 most common) dashboards display as expected in the editor.
To be precise, as far as I can see, all dashboards with at least one visible element in a proportional row or below a proportional row have problems. If all visible elements are in rows of absolute height and all these rows are aligned at the top, there won't be any problems.
In the editor, the bottom border of the viewport was and is the navigation bar (if present). But when viewing in 4.32, the bottom border is higher. Examples are here: https://forum.locusmap.eu/index.php?msg=80029
@Erelen - all my dashboards have proportional rows. I don't see problems. In fact until your comment, I didn't realize fixed height rows were possible - thanks.
Hello everyone,
I have now installed the new version 4.32 and, like Erelen, noticed that all my dashboards no longer appear where I had placed them, but appear significantly higher up. I have not yet found a way to move them back to the lower area. A dashboard that appears in the middle of the map view is not a solution for me.
Another silly question: What does edge-to-edge mean?
Quote from: Wole on December 09, 2025, 07:41:28Hello everyone,
I have now installed the new version 4.32 and, like Erelen, noticed that all my dashboards no longer appear where I had placed them, but appear significantly higher up. I have not yet found a way to move them back to the lower area. A dashboard that appears in the middle of the map view is not a solution for me.
Another silly question: What does edge-to-edge mean?
Edge-to-edge (Full screen) can be set in the expert settings so you can use full screen. I made a new dashboard based on Locus on top of the screen without any problems.
PS: Locus 4.32, Android 14.
@Mark_Again
maps should work with updated theme. Theme is available in the Locus Store, just search for "John Thorn".
I made a hint in the app about this, but seems, it does not work as expected. Will improve it to the next app version, sorry for this.
@Erelen
dashboard > hmm I see a problem will "Whole screen overlay" type. Will look at it.
@slarti76
crashes > maybe related to this issue (https://help.locusmap.eu/topic/39323-version-4-32). Already fixed.
---
Edge-to-edge for explanation is not equal to "Full screen". It is a new requirement from Google. Now apps fully control what is draw behind the bottom navigation and the top status bar. In all cases. No exceptions. So all screens and dialogs have to provide correct offsets from sides, handle camera cutouts on all devices, draw correct background colours etc. And because Locus Map consists of a few hundred screens and dialogs, it took us almost two months to make it all work as needed.
Nice overview from Google for example here (https://developer.android.com/design/ui/mobile/guides/layout-and-content/edge-to-edge).
Quote from: Menion on December 09, 2025, 11:32:59@Mark_Again
maps should work with updated theme. Theme is available in the Locus Store, just search for "John Thorn".
I made a hint in the app about this, but seems, it does not work as expected. Will improve it to the next app version, sorry for this.
@Erelen
dashboard > hmm I see a problem will "Whole screen overlay" type. Will look at it.
@slarti76
crashes > maybe related to this issue (https://help.locusmap.eu/topic/39323-version-4-32). Already fixed.
---
Edge-to-edge for explanation is not equal to "Full screen". It is a new requirement from Google. Now apps fully control what is draw behind the bottom navigation and the top status bar. In all cases. No exceptions. So all screens and dialogs have to provide correct offsets from sides, handle camera cutouts on all devices, draw correct background colours etc. And because Locus Map consists of a few hundred screens and dialogs, it took us almost two months to make it all work as needed.
Nice overview from Google for example here (https://developer.android.com/design/ui/mobile/guides/layout-and-content/edge-to-edge).
Oh. Than I missunderstood this feature.
@Menion
I been using Locus Map for several years and was completely unaware of the themes. I installed the John Thorn theme and not only does it work but, the details are cleaner. Thank you, Mark
Quote from: Mark_Again on December 09, 2025, 23:36:17@Menion
I been using Locus Map for several years and was completely unaware of the themes. I installed the John Thorn theme and not only does it work but, the details are cleaner. Thank you, Mark
I also heard about it for first time - it doesn't help that it doesn't show up in store when you search for "theme".
Menion, could you perhaps add a separate category "Map themes" in store?
Anyway, I find it terrible, in a city I mainly see gas stations and parking spots. Looks like it's targeted at car drivers - is that right? Or am I overlooking some configuration ability?
This theme is especially for John Thorn maps. It has no usage for LoMaps, OAM or other vector maps.
I am running 4.32.0.1. When I click on release notes the app crashes.
Quote from: Andrew Heard on December 09, 2025, 05:24:33@Erelen - all my dashboards have proportional rows. I don't see problems. In fact until your comment, I didn't realize fixed height rows were possible - thanks.
I completely forgot that dashboards have modes other than "Whole screen overlay" :) Yes, my statement "all dashboards are broken" is too bold.
You could also show Google who writes the apps for Google.
Instead of constantly being harassed by Google, you can also publish the apps on F-Droid.
If Google doesn't want to, they should just leave it alone and write their own apps.
I wish all developers would do that.
Then a Google-free smartphone would finally be possible.
Yes, that would be nice.
But the vast majority of Android smartphone users don't even know that there are other app stores. For them, there is only the Play Store. Anyone who doesn't place their app there will only reach a minority. Unfortunately.
Most people also don't know that there are other search engines besides Google and other map applications besides Google Maps... etc.
Quote from: Graf Geo on December 12, 2025, 22:40:44Yes, that would be nice.
But the vast majority of Android smartphone users don't even know that there are other app stores. For them, there is only the Play Store. Anyone who doesn't place their app there will only reach a minority. Unfortunately.
Most people also don't know that there are other search engines besides Google and other map applications besides Google Maps... etc.
Other app stores can certainly be an alternative to the Google Play Store.
However, F-Droid isn't always the best option, as it's an installable catalog of FOSS (Free and Open Source Software) apps for Android.
Not every Android developer wants to or can market their apps as free and open source software. This should also be taken into consideration.
Is there any ETA on a new beta? Especially with the fix for the track editor - I'm really backlogged on some track cleaning up.
I know, there's 4.32.0.1, but that has the lower release number, so as I already installed 4.32.0.0, I cannot use that. Please provide a 4.32.0.2 with updated release number, thank you!
I've been testing the functionality with old V3 maps.
An old OAM V3 map from 2019 displays perfectly using both the internal themes and external V4 themes. Good.
However I have an old LoMap V3 map from 5 November 2021 of England. If I select that map, instead of showing it Locus displays the latest version England map I also have installed. If I uninstall the newer map, Locus shows a blank map when the older map is selected.
The older map displays perfectly in Locus Classic.
Can confirm the crash when opening the release notes on 1197
hey all - our good German epic (huge distance) bike trekking friends who I introduce to Locus, tell me <I'm struggling with the name locus for this mapping app. In Germany we use it when we go to the toilet 🙂: "Locus" comes from Latin, "locus necessitatis" means "place of need".>
best wishes to all the hard working Locus/ place of need team from down under
Old story, but yeah it sounds like. My wife also was irritated by the name. To be precise the german word is Lokus, it's a toilet. A slightly dated word, not sure if too known in the very young generation.
Hi guys,
it is weird December. Not just the weather in the czech is terrible, but also again and again some technical complications ... I looked at what we did in Android this year > not much :( . Many technological puzzles on the background, many unexpected requirements from Google itself (most of them make sense) and so on ...
This time, I had to change a very old system I used for app protection (10+ years) to a different one. This means that again, the whole app is not as stable as before.
I did a lot of manual testing during the last 14 days. But still not feeling 100% confident saying > all works perfectly. I believe it is, but still ...
New Beta version 4.32.0.3 on the Google Drive.
This time in the directory "alpha"! Use at your own risk and keep the previous 4.32.0 APK on the device, just for sure.
@menion - if problem with MapGooglePlay_4.32.0.3_1198_beta.apk, do I just "install" MapGooglePlay_4.32.0_1198_release.apk, or need to "uninstall" first?
Quote from: Menion on December 19, 2025, 16:41:19I looked at what we did in Android this year > not much
huge # changes in release notes!!!
PS. no problems in testing so far; just ordinary preset/ track record stuff
Quote from: Menion on December 19, 2025, 22:36:02simply a maintenance of the old project.
unfortunately it's the nature of "old" code; employ an AI to do the maintenance/ boring stuff?
I know, huge list, but ... I'm not satisfied with it :). Too many tasks affecting the structure and "invisible" stuff ... simply a maintenance of the old project. Never mind, 2026 has to be better ;)
And you need just "update". Both have identical code 1198, so there is no need to un-install!
Updating a bunch of libraries is often a challenge.
I do recognise your ongoing love, so there is love and world a good place :)
I launched LM Afa 4.32.0.3_1198 alpha and clicked a bit here and there and all was fine.
I realised that RoutePlanner has issues with offline-router LoRouter Offline, see pic.
Track-segment results in error-notification and a direct line with draw-manually pencil-icon, maybe due to missing calculation-result.
I updated routing-segments, tested tts in settings, chosed different profiles, didn't help.
Online-routing is working, all fine.
Ah, this is exactly the kind of possible errors ... thanks, will fix it asap.
4.32.03
When I click on the Locus Store, the app closes.
4.32.03
1) Crash when I open MapItems list (Map-screen content - button in right of Active items).
Earlier bugs:
2) Two "Presets" screens do not take into account the height of android navigation bar:
- Presets - Edit (last item under "Pencil" button)
- Presets - Edit - Pencil (last item under navigarion bar)
3) Dashboards. Sorry.
Everithig ok in edit mode (ok == "like in 4.31 and earlier").
But in view mode:
- bottom row is under navigation bar
- top row is under notification bar (hm. top row in view mode was ok in 4.32.0.1 - https://forum.locusmap.eu/index.php?msg=80029)
Quote from: freischneider on December 20, 2025, 21:16:584.32.03 When I click on the Locus Store, the app closes.
confirmed - crash - nasty ;-(
Quote from: Erelen on December 21, 2025, 02:38:241) Crash when I open MapItems list (Map-screen content - button in right of Active items).
confirmed crash
Quote from: Erelen on December 21, 2025, 02:38:24- top row is under notification bar (hm. top row in view mode was ok
confirmed - as a quick fix I simply added a new row above each of my existing dashboard rows to compensate for "immersive mode" - figured that was simpler to fix this way
Quote from: Erelen on December 21, 2025, 02:38:242) Two "Presets" screens do not take into account the height of android navigation bar:
- Presets - Edit (last item under "Pencil" button)
tried to reproduce, but unsure how; sounds related to "immersive mode"
4.32.03
Crash on open "Online map downloader" (tiles downloader).
And after downgrading to 4.32.0-1198 (to use MapItems and offline LoRouter with my own profile) - it crashes in 1-2 seconds after start. So, I'm really looking forward to the next build :)
Thanks for the tests ... 4.32.0.4 published!
@Erelen
Presets UI > indeed there is something wrong when returning back from "Select settings" page. Hmm, can't find the real reason of this ...
Dashboard problem > in the "Dashboard over full screen" mode, this is starting to be more complicated :). What to do with it here? Offset it by the status bar? But what if you want to draw dashboard panel also below the status bar? ::)
Quote from: Menion on December 22, 2025, 15:28:29What to do with it here?
leave it "as is"
4.32.0.4 - all good now
Merry Christmas everyone!
Sorry for bug reporting in the holidays, but this one's severe:
I edited a track, did the following:
- Insert/edit trackpoint
- Remove section
- Insert/edit trackpoint
The last operation instead deleted like half of the track, I'm not 100%, but it was probably same as "Remove all after".
Track and screen recording of what I did can be found here: https://web.tresorit.com/l/UwA4T#NoxPRGDwfym3Key277zm1A (that video contains a "Remove all before" as first operation, but I tried it without again and could reproduce - the first "Insert/edit" however is necessary to reproduce)
I used latest beta, so not urgent, but definitely disconcerting...
Merry Christmas from me as well:
I hit a serious bug in 4.32.0.4
1. app crash in navigation
When in navigation or guidance when the screen goes off, the app crashes/closes/disappears.
This is regardless of the settings of screen control or run as a service. (Problem is: this makes this version quite unusable).
I checked the log and it seems, the app dies, when the screen goes back on. This is the error message:
16:57:03.820 E a uncaughtException(Thread[main,5,main])
java.lang.RuntimeException: Unable to resume activity {menion.android.locus/com.asamm.locus.basic.features.mainActivity.MainActivityMap}: java.lang.RuntimeException: All children of ConstraintLayout must have ids to use ConstraintSet
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:6269)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:6342)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:73)
at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:63)
at android.app.servertransaction.TransactionExecutor.executeLifecycleItem(TransactionExecutor.java:169)
at android.app.servertransaction.TransactionExecutor.executeTransactionItems(TransactionExecutor.java:101)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:80)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:3150)
at android.os.Handler.dispatchMessage(Handler.java:110)
at android.os.Looper.loopOnce(Looper.java:273)
at android.os.Looper.loop(Looper.java:363)
at android.app.ActivityThread.main(ActivityThread.java:10060)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)
Caused by: java.lang.RuntimeException: All children of ConstraintLayout must have ids to use ConstraintSet
at d5.n.e(r8-map-id-713f30a2f4f8e28d5aebf4691608998936cbbd65c4e770313d706e83b1353b1a:45)
at bx.c.invoke(r8-map-id-713f30a2f4f8e28d5aebf4691608998936cbbd65c4e770313d706e83b1353b1a:354)
at com.asamm.locus.basic.settings.dialogs.PrefDashboardSelection.q(r8-map-id-713f30a2f4f8e28d5aebf4691608998936cbbd65c4e770313d706e83b1353b1a:108)
at mt.c.onResume(r8-map-id-713f30a2f4f8e28d5aebf4691608998936cbbd65c4e770313d706e83b1353b1a:110)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1720)
at android.app.Activity.performResume(Activity.java:9691)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:6239)
... 14 more
2. Nav Bar draw over (inconvenient):
The nav Bar draws over the sensors manager, which makes the connect button of the last sensor (almost) unreachable.
(Fun fact: also the screenshot ends above the nav Bar, therefore i had to take a photo 😉)
PXL_20251226_153902131.jpg
Greetings Ulrich
And as always, if I can help debugging, just tell me, what I should do 👍🙂
Crash on navigation would indeed be serious. Cannot confirm after a quick check though. I started navigation, then turned off screen for some seconds and then back on. Manually.
Quote from: Tapio on December 28, 2025, 11:13:49Crash on navigation would indeed be serious. Cannot confirm after a quick check though. I started navigation, then turned off screen for some seconds and then back on. Manually.
I did a quick check and the issue seems to be related to my dashboard. Have to do some more checking
LG uk
LM 4.32.0.4
the bug once mentioned in the german post you answered shortly is still existent.
With GPS location on but crossed moved out of current position and center the icon still keeps its white center and does not switch to empty/non-white. This is only with lock on, with lock off the center of the icon immediately switches.
See pic, center not on current position (far away) but icon filled white, obviously wrong and easy to doublecheck.
btw i use the dual centering button (expert setting > maps).
There's also sth. wrong with north direction and center on current location and map-rotation, you definitely have to move center-cross out of location to enable northing, otherwise it switches always back to map-rotation when centered. I know this move but might be irritating to others.
Guess all that is supersimple to solve.
Quote from: Tapio on December 28, 2025, 11:13:49Crash on navigation would indeed be serious. Cannot confirm after a quick check though. I started navigation, then turned off screen for some seconds and then back on. Manually.
So I did some testing: crash only happens when a dashboard is Active. It does not matter what is in the dashboard - even a completely empty one triggers the crash. If I disable the dashboard, crash is gone.
Can someone confirm this?
Greetings, Ulrich
Quote from: Ulrich Kiermayr on December 28, 2025, 16:12:00Quote from: Tapio on December 28, 2025, 11:13:49Crash on navigation would indeed be serious. Cannot confirm after a quick check though. I started navigation, then turned off screen for some seconds and then back on. Manually.
So I did some testing: crash only happens when a dashboard is Active. It does not matter what is in the dashboard - even a completely empty one triggers the crash. If I disable the dashboard, crash is gone.
Can someone confirm this?
Greetings, Ulrich
This workaround is only valid for guidance mode. Navigation always crashes, regardless of the dashboard (or anything else navigation draws on the screen).
Maybe also related to the Android version (S23, Android 16).
Greetings, Ulrich
Not crashing even with Dashboard on. Android 10
Quote from: Tapio on December 29, 2025, 06:47:27Not crashing even with Dashboard on. Android 10
Thanks, so the Android version could in deed be a contributing factor. 🤔👍
LG uk
OAM users, new maps are out, I initiated the download via OAMs "Map and Poi" button, so a Locus Task managed the download.
But it does it now multiple times. Also after every restart of LM. Download and unpack. Erm wut.
BEWARE
Ah new year is here ... happy to all ;).
I hope, we will be able to publish the app on Google Play at least :).
@Ulrich Kiermayr
Dashboard crash > should be fixed now, thanks.
Space in sensors screen at bottom > fixed
@T-mo
Center icon > current behaviour is intent. It means that centring is still enabled thanks to the "Hold map center" function. Anyway oki, I'll think about a little bit different icon ...
Problem with map rotation (the second) > can you describe in more detail or record a short video? Thanks
@Tapio
Re-download > nothing like this happens to me. Does the download finish correctly?
@Menion: Sorry to bother, but what about my report https://forum.locusmap.eu/index.php?topic=9488.msg80161#msg80161 ? Usually, you mention all open reports in your round-up messages, so I fear you might have overlooked mine? Loosing half of the track when doing an insert/edit is surely a severe problem...
Ah thanks. I was reading it and decided to look at it later ... and forgot :(. It was complicated ... and serious! Thanks a lot for the video! Fixed.
On 4.32.0+auto, the label rotation occasionally stops during navigation. The labels are shown north up again for a while and then all of a sudden they start rotating again.
Quote from: Tapio on January 03, 2026, 16:13:54OAM users, new maps are out, I initiated the download via OAMs "Map and Poi" button, so a Locus Task managed the download.
But it does it now multiple times. Also after every restart of LM. Download and unpack. Erm wut.
BEWARE
The same happened to me today. I downloaded Great Britain from OAM, generating a Locus action, and while it was downloading queued a download of Spain, which downloaded successfully as did the download of great Britain. When I restarted Locus and started to download elevation data I found that Great Britain was downloading again. I then cancelled the download and manually deleted the temporary zip file.
Unfortunately in debugging another issue I've been installing/ uninstalling various app versions for hours; in that process, is the following a bug, something I did wrong, or something to maybe improve... I had all files in android/media/menion.android.local. I later installed a release version which used the default android/data/menion.android.local. When I went settings > Backup & filesystem > File system manager > Set the main directory, and changed from data to media, it appears that Locus overwrote all/ most of the real files with the default ones. Did I miss something? And I thought media was the best folder anyway/ should be default?
A backup of all points & tracks: the progress bar goes to 100% nearly immediately (few seconds) although for me the actual backup takes many minutes. The progress bar is of little use at present.
On 4.32.0.4 label rotation seems to have stopped completely on zoom levels below 12.
In fact, there is no zoom level below 12 anymore. When zooming out with the zoom buttons, you can zoom out to 12, 100% and after that, it is 12, 53% with unrotated labels, no matter how far you zoom out.
The problem goes away if you disable a worldmap for lower zoom levels.
(I also have a similar download problem of an OAM-map (Austria). Locus always stops with "timeout" (Code:12569) after some minutes and already 100eds of MB downloaded.)
edit: no problem, in 5th time it worked after I restarted download at OAM-website, i cleared some temp/cache files in locus folder :)
V 4.32.0.5 afa fc on app start ::)
05 version on Android 10 - Instant ctd and it doesn't even write a log. In lack of the 04 installer I cannot use it now.
When is 4.32 expected to be available on google play?
Hi @Menion. 4.32.0.5 fixes all Dashboard crashes.
But there is a new odd issue: The Map items button does not open the map Items sidebar, but now the NTRIP Manager.
Screenshot_20260109_171816_Locus-Map-2026-01-09_05_21_PM.jpg
Screenshot_20260109_171832_Locus-Map-2026-01-09_05_23_PM.jpg
Lg Ulrich
Quote from: Tapio on January 09, 2026, 16:29:0405 version on Android 10 - Instant ctd and it doesn't even write a log. In lack of the 04 installer I cannot use it now.
Android 16 - no FC for me 🤷
lG Ulrich
Hi guys,
version 4.32.0.6 published. Sorry for the previous .5 version. Minor issue on A11-.
Yesterday, after a month, Google finally fixed the issue on their side, and we are ready to publish a new version. At least I hope. So maybe next week ...
Quote from: Menion on January 09, 2026, 21:59:11version 4.32.0.6 published. Sorry for the previous .5 version. Minor issue on A11-.
Just for completeness: Map items Issue (https://forum.locusmap.eu/inhttps://forum.locusmap.eu/index.php?msg=80239https://forum.locusmap.eu/index.php?msg=80239dex.php?msg=80239) also present in 4.32.0.6
Greetings, Ulrich
One more thing: since the Map content button is not working:
Is there any other way to turn on/off or configure the LoPoint highlighting?
Greetings
Hi,
There are 2 more "hidden underneath the Android home Bar" issues in the preset editor:
1. Editor itself
Screenshot_20260110_015924_Locus Map.jpg
2. The sub editor, where the visible items are selected
Screenshot_20260110_015947_Locus Map.jpg
Greetings, Ulrich
Quote from: Ulrich Kiermayr on January 09, 2026, 17:24:14The Map items button does not open the map Items sidebar, but now the NTRIP Manager
as noted by Ulrich, same bug in 4.32.0.6
Sorry for these issues :(
4.32.0.7 published.
@Ulrich Kiermayr
The old "Presets" screen, for some reason, resists. On the first open, it seems to work correctly. But later ...
I'll probably have to update this screen to the new system we use for UI. I consider this a minor problem. Will try to look at it, but can't promise a quick solution for now. Thanks for understanding.
Quote from: Menion on January 10, 2026, 09:41:27I'll probably have to update this screen to the new system we use for UI. I consider this a minor problem. Will try to look at it, but can't promise a quick solution for now. Thanks for understanding.
I also consider it a minor problem. I just wanted to note it for completeness, so that you are aware of the issue. 👍
greetings, Ulrich
Hi there!
Just two really minor points:
1. Having the distance marker activ and setting the track color to "using folder style" does not change the color of the distance markers.
2. Creating a new folder showing the icon I did set in the expert settinge as "default point icon". Shouldn't it be a folder icon?
4.32.0.7
Android 14
Hi there!
I'm out in the woods right now on a hike and figured out that the "keep the position" get lost as soon as I zoom in or out. Can someone confirm this, please? Thanks.
4.32.0.7
Quote from: WildWortWechsel on January 11, 2026, 13:12:20Hi there!
I'm out in the woods right now on a hike and figured out that the "keep the position" get lost as soon as I zoom in or out. Can someone confirm this, please? Thanks.
4.32.0.7
I think, it is because you have "hold map center" turned off (no lock on the center symbol. Can you confirm this?
Screenshot_20260111_154254_Locus Map.jpg
Greetings, Ulrich
Thank you!
This setting was indeed off. Guess, it was to cold today for me to realize it.
@Ulrich Kiermayr
Presets screen > maybe finally fixed!
@WildWortWechsel
distance markers colors > thanks, fixed
icon of the folder > it is small confusion - this icon is also used as a base icon for points. So here is used the default icon for points.
Finally, version 4.32.1 was uploaded to the Google Play (and on the Google Drive).
Google confirmed the issue on their side and, after a few weeks, fixed it.
Thanks a lot for the help with testing last few weeks. The changes I had to make in December were unexpected, and without your help, the stable version would have taken me a lot longer. Even a simple usage without reporting here on the forum is very welcome, because of automatic crash reports to Firebase. :-*
Quote from: Menion on January 13, 2026, 10:21:43Finally, version 4.32.1 was uploaded to the Google Play (and on the Google Drive).
Google confirmed the issue on their side and, after a few weeks, fixed it.
Does this include the Android Auto feature?
Fingers crossed ...
No 8) ... I hope for at least a "basic" version. Android Auto (again) in the next row....
Menion, you have broken app language again. The old issue is back. Android 10.
- In settings, I set LM to english.
- App and themes are now in english. Good.
Restart LM.
- App is in english, but themes are now in OS language (german)
- In the language settings, German is highlighted.
Hello Menion,
related to map language, in Germany North are two cities with german and english names at the same time: Hannover and Braunschweig.
@WildWortWechsel - You're right. For cities, both the local name and the English name are often displayed, which is particularly helpful for non-Latin scripts (and vice versa). However, the English names depend on the data source we use for map rendering (Thunderforest), so we don't have control over which cities include an English name.
@Tapio
Android 10-, it is a pain with languages. Another modification done now ... thanks and sorry!
Beta version 4.32.1.1 (16.1.2026) with minor fixes
- fix: import of not 100% valid GPX files
- fix: scale bar not changing when moving the map in low zoom level
- fix: incorrect app language on Android 10- in some cases
Since the update to version 4.32, I am experiencing frequent crashes in the route planner. If I move too fast, change too much or click on the 'wrong places' the app just freezes and restarts (and you loose the planned route). This also happens in the latest version 4.32.1.1
Quote from: Menion on January 16, 2026, 15:38:23Android 10-, it is a pain with languages.
Yeah, seems so,
the behaviour didn't change with the latest beta. After all only the themes show the wrong language, so no real problem.Hmm, maybe my testing was flawed, it's OK now
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.
Old MF issue with IIRC no solution.
@Blihi
may you please write to me your "User ID"? Thanks (in the about app screen > 9 characters)
@TrulloF
we were just looking on this few days ago with Petr and decided to do something with it after years ...
I have noticed the following problem with the current version:
Settings > Language & Units > Text-to-Speech: Locus crashes regularly.
This also happens in Audio Coach > Text-to-Speech.
Thanks guys, version 4.32.2 just published on the Google Play.
Changes
- chg: removed support for Android 6 (SDK 23)
- fix: failed import of partially invalid GPX files
- fix: crash at start of the route planner on Android 7.0
- fix: scale bar not respecting the Mercator projection when shifting the map
- fix: incorrect app language on Android 10- in some cases
Text-to-speech crash no longer occurs with 4.32.2. :)
Quote from: Menion on January 19, 2026, 08:13:20@Blihi
may you please write to me your "User ID"? Thanks (in the about app screen > 9 characters)
Sure, it's a3cb44c74
It appears to be a memory issue. The app works for a while, then slows, typically when showing the magnifier glass. At that point it becomes unresponsive and reboots. Android by now also suggests to put the app in deep sleep because of frequent crashes.
The issue appears both on the phone (Samsung S22) and the tablet (Samsung Tab9FE). I turned logging off, but that did not make a difference.
Language stays broken for me, behaviour as previously reported.