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
28. 1. 2026 - Locus Map 4.32.3
5. 2. 2026 - Locus Map 4.32.4
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.
@Blihi
Thanks for the "ID". Unfortunately, I do not see any automatically reported issues. The current version seems to be more stable than I expected. So there are no unusual memory problems reported. This happens to you even when you start with an empty route planner and just add a few points? Does it make a difference what map you use? (online require a lot less memory, so give it a try).
@Tapio
Still is valid your info here (https://forum.locusmap.eu/index.php?msg=80265)? I'm unable to simulate it on Android 10 :(. System se to Czech, app to English. Even after a restart, all is correctly set with the latest 4.32.2 version. Hmm ...
Quote from: Menion on January 22, 2026, 12:29:01Still is valid your info here (https://forum.locusmap.eu/index.php?msg=80265)?
Yes, but now it works again. It's really strange, like after an update the problem is back, nothing I can do, then I forget about it and at some unknown point it's perfectly in english, setting, ui and themes. A mystery. Next time I see it I will look if the log tells something.
Quote from: Menion on January 22, 2026, 12:29:01@Blihi
Thanks for the "ID". Unfortunately, I do not see any automatically reported issues. The current version seems to be more stable than I expected. So there are no unusual memory problems reported. This happens to you even when you start with an empty route planner and just add a few points? Does it make a difference what map you use? (online require a lot less memory, so give it a try).
The problem occurs randomly in the routeplanner. It does not really matter if I start from an empty route or open an existing route for editing. I'm typically using offline LoMaps, not the online maps. It's unclear when the crashes exactly happen, but the way they appear is always the same: the screen freezes and the app reboots.
I'll try to debug a bit, but it's a hard problem to reproduce. I'll try to see if it also happens when I'm offline. Maybe the cloud synchronization in the background is interfering with the planner in some way.
I include a log file of today. Crashes happened a few times, no clear indication why, but there are a lot of exceptions in the log.
Hello menion
Until now, I had always set the permission for location tracking in Locus to 'when Locus is in use'.
In V4.32.2, the 'stabilised GPS' function only works if I always allow Locus to track my location?!
Example: GPS fix is available, I create a POI and want to stabilise the coordinates.
At this moment, the GPS is switched off (no popup why) if the setting is set to 'when Locus is used'
stabilised GPS window > searching,
This was not the case before. Is there a reason for this change?
The save button for notes and routes is now hidden under the keyboard. When entering text I have to minimize the keyboard in order to save. This is extremely annoying when collecting notes for changing osm
@Blihi
Thanks for the log. Unfortunately, there are just some generic errors that most probably do not caused crash of the app. Hmm, this is complicated. May you please try to create a big system log with this method (http://docs.locusmap.app/doku.php?id=manual:faq:how_to_create_debug_log) right after the crash happens? Ideally, register a time when this happened.
@balloni55
this is very interesting. Until a few months ago, all crucial features required "All the time" permission. And a few months ago, I've changed the system for the track recording a little, so this one now DOES NOT require this permission.
But all other features that may run in the background > guiding, Live-tracking, POI alert, stabilised GPS and probably some others, require "All the time".
@Manuel
may you please post me a screenshot of these problematic screens? Thanks.
Hello,
I've just recently migrated from Locus Map Classic to Locus Map 4 in November, so forgive me if some of my problems are caused by user confusion. When I migrated, everything went well and I was able to use Locus Map 4 normally. However, after one of the most recent updates, the custom map of Finland I'm using hasn't worked (shows just gray background). I'm pretty sure this has to do with the custom map theme my custom map requires. If I reimport the custom map theme, it seems to go ok (Locus map shows a dialog about the theme and says it was imported succesfully). However, there's no place I can select the import theme. What's even weirder, when I choose the map in the the map selector, it shows "Hiking and cycling" under my custom map's name and the name of my custom theme under the "LoMaps Online" map. If I try to use "Map themes" under the "Map tools" menu, I get that no maps with themes are active.
How should I proceed in solving this problem?
Hello @bitti
the recent Locus Map 4 version dropped support for a very old MapsForge V3 map themes. So now, also old V3 maps require a new themes with "version 4+". Maps and themes are your own creation?
If so, you should be able to use the script we provide here (https://github.com/asamm/lomaps-mapsforge/tree/main/theme-v3-to-v4-converter), or simply update the theme on your own. Now it has to be 100% compatible with official MapsForge documentation. Otherwise, suggest contacting the maps & theme author to adapt to these changes (if not yet adapted).
Thanks @Menion!
Although the map theme isn't written by me, I was able to convert it, and it now works (it required some extra tweaks to render properly).
But if the app now requires the theme to be 100 % compatible to be imported, it would be nice to get an error message if that's not the case... ;)
Since some versions the library is damn slow
I have some Geocaching folders..one of them includes 10.000 Caches.
I have to wait seconds, just to open it. Filtering and oder stuff lasts about 20 seconds. Often der percentage line increases up to 300 percent while waiting.
Some times the app crashes and says "wait" or "end" the app
@Diddi
hmm, my 14k caches big folder opens between 1-2 secs. Filtering, for example by "difficulty", is almost instant. Interesting. We may try to create a log, but I'm worried, I won't see a real problem there. Are you willing to share a backup of the database with me? Thanks
Version 4.32.3 was published on the Google Play.
News:
- info: If you have problems with older LoMaps, please re-download them from the Locus Store for free.
- add: support for the new route plan URL sharing
- chg: added info about need to update old LoMaps when necessary
- add: "Guide to" as another option for the custom geocache button
- chg: MapsForge library updated to 0.27.0
- chg: border around texts above the map increased a bit
- fix: bulk point import missing "Apply to all" check
- fix: crash when obtaining initial user location
- fix: crash when preparing UI for Locus Store
- fix: crash when opening app settings from the widget
- fix: (SILVER) crash caused by automatic clearing of WMS/WMTS tiles
- fix: rare crash when moving data in My library
- fix: minor fix of case-sensitivity of search in My library, Settings etc.
since a few versions ago, after track > Export, there are 2 new buttons
20260129-105609-.jpg
what is the purpose of the OPEN IN APP button? I'm using the LM4.32 app, and when I tap this button, below is displayed
20260129-105630-.jpg
there appears 2 overlays of text, and how is Import relevant when the track has just been exported?
After yesterday's update, the automatic loading of Lomap Czechia/Slovakia does not work for me. Maps are updated. Manual switching works.
Quote from: Andrew Heard on January 29, 2026, 00:55:56.. what is the purpose of the OPEN IN APP button? I'm using the LM4.32 app, and when I tap this button, below is displayed
20260129-105630-.jpg
there appears 2 overlays of text, and how is Import relevant when the track has just been exported?
I cannot confirm this overlay message. A bar with several apps is displayed at the bottom of my screen, from which I can select one. The exported track is then displayed there or offered for import.
@Andrew Heard
Unfortunately, not all apps were able to open the track with a single "Share" command. Some of them need a slightly different "Open" command, so I had to add a second button here (for example Garmin Connect app). Error ... aren't you still using the Locus Classic version? Can't this error be from the old Classic?
@Žajdlík Josef
Hmm, I see no problem here. Both maps version 2024+? No other vector Czech or Slovak map in the device? Auto-loading for vector maps in the settings enabled?
@Diddi
thanks for the backup. More over PM.
1) Automatic loading is turned on (it worked without problems in the previous version).
2) The maps are from 6/12/2025.
3) There is no other map in the device.
4) map theme from Lomap
Screenshot_20260129_144603_Locus Map.jpg Screenshot_20260129_144541_Locus Map.jpg Screenshot_20260129_144525_Locus Map.jpg
Quote from: Menion on January 26, 2026, 11:12:28@Manuel
may you please post me a screenshot of these problematic screens? Thanks.
(https://i.postimg.cc/JyFSSfhJ/Screenshot-20260129-175932.png) (https://postimg.cc/JyFSSfhJ) (https://i.postimg.cc/rdsvnVqG/Screenshot-20260129-180008.png) (https://postimg.cc/rdsvnVqG) (https://i.postimg.cc/QBCR48jf/Screenshot-20260129-180020.png) (https://postimg.cc/QBCR48jf) (https://i.postimg.cc/gw711C08/Screenshot-20260129-180028.png) (https://postimg.cc/gw711C08)
1st is the screen for a new note.
2nd the same scrolled down just for reference (IMHO a lot of blank space for the attachment placeholder and the address. Who even enters that on GPS coded notes?)
3rd one shows me editing a title. Keyboard is on the bottom as it is default and the case for likely most users. The save or cancel button is not visible. I think they were on the bottom of the visible form before, but not on the absolute bottom of the screen under the keyboard.
This means, I cannot just enter a title and save as I did before dozens of times per tour to keep notes for mapping.
4th one shows the same screen, but the form scrolled all the way to the bottom. Note that the save (or cancel) button is still not visible. It is fixed in position under the keyboard.
Not shown: I have to close the keyboard to be able to click the save button.
And like I said, it is the same behavior when saving routes. And probably other forms.
Quote from: Manuel on January 29, 2026, 18:13:27Quote from: Menion on January 26, 2026, 11:12:28@Manuel
may you please post me a screenshot of these problematic screens? Thanks.
(https://i.postimg.cc/JyFSSfhJ/Screenshot-20260129-175932.png) (https://postimg.cc/JyFSSfhJ) (https://i.postimg.cc/rdsvnVqG/Screenshot-20260129-180008.png) (https://postimg.cc/rdsvnVqG) (https://i.postimg.cc/QBCR48jf/Screenshot-20260129-180020.png) (https://postimg.cc/QBCR48jf) (https://i.postimg.cc/gw711C08/Screenshot-20260129-180028.png) (https://postimg.cc/gw711C08)
1st is the screen for a new note.
2nd the same scrolled down just for reference (IMHO a lot of blank space for the attachment placeholder and the address. Who even enters that on GPS coded notes?)
3rd one shows me editing a title. Keyboard is on the bottom as it is default and the case for likely most users. The save or cancel button is not visible. I think they were on the bottom of the visible form before, but not on the absolute bottom of the screen under the keyboard.
This means, I cannot just enter a title and save as I did before dozens of times per tour to keep notes for mapping.
4th one shows the same screen, but the form scrolled all the way to the bottom. Note that the save (or cancel) button is still not visible. It is fixed in position under the keyboard.
Not shown: I have to close the keyboard to be able to click the save button.
And like I said, it is the same behavior when saving routes. And probably other forms.
The same thing happens when saving a recording. When I type the title, the keyboard covers the save button.
I'm glad I'm using an older version on my main device. On that one, the "Save" button still pops up and isn't covered by the keyboard.
This should be fixed as soon as possible in the current version.
Quote from: Menion on January 29, 2026, 14:38:04@Andrew Heard
Unfortunately, not all apps were able to open the track with a single "Share" command. Some of them need a slightly different "Open" command, so I had to add a second button here (for example Garmin Connect app). Error ... aren't you still using the Locus Classic version? Can't this error be from the old Classic?
ah I see - the full meaning "open in
another app" - I understand its
purpose now. Old Classic? I've been using LM4 Gold (as per my signature at bottom of post) since day #0. Huf. But still the orange toast message(s) - and appears to be 1 toast on top of the other if you look closely. Toast sandwich.
change existing route in route planner - switch to manual mode - all segments are drawn as straight lines between via points. switching back to another profil and hit re-calculate: nothing happens.
Is this intented?
Version 4.32.4 (5.2.2026)
- add: Catalan translation (thanks to Rafael and Ramon)
- fix: getting stuck at 100% during start in rare cases
- fix: need to unlock the screen when taking a photo on some devices
- fix: incorrect align of tiles for the base map
- fix: incorrect coordinate transformations for some custom projections
- fix: hidden "save" button in point/track edit metadata screen
- fix: (GOLD) not working link to "synchronization" user guide page
- fix: (GOLD) crash in personal live-tracking dialog in case of incorrectly loaded user
- fix: crash when re-allocating floating waypoints to the track
- fix: crash when displaying UTM coordinates at the "edge of the world"
@Christian &
@Andrew Heard > I'll look on both issues next days ... thanks
Quote from: freischneider on January 29, 2026, 21:22:53Quote from: Manuel on January 29, 2026, 18:13:27Quote from: Menion on January 26, 2026, 11:12:28@Manuel
may you please post me a screenshot of these problematic screens? Thanks.
(https://i.postimg.cc/JyFSSfhJ/Screenshot-20260129-175932.png) (https://postimg.cc/JyFSSfhJ) (https://i.postimg.cc/rdsvnVqG/Screenshot-20260129-180008.png) (https://postimg.cc/rdsvnVqG) (https://i.postimg.cc/QBCR48jf/Screenshot-20260129-180020.png) (https://postimg.cc/QBCR48jf) (https://i.postimg.cc/gw711C08/Screenshot-20260129-180028.png) (https://postimg.cc/gw711C08)
1st is the screen for a new note.
2nd the same scrolled down just for reference (IMHO a lot of blank space for the attachment placeholder and the address. Who even enters that on GPS coded notes?)
3rd one shows me editing a title. Keyboard is on the bottom as it is default and the case for likely most users. The save or cancel button is not visible. I think they were on the bottom of the visible form before, but not on the absolute bottom of the screen under the keyboard.
This means, I cannot just enter a title and save as I did before dozens of times per tour to keep notes for mapping.
4th one shows the same screen, but the form scrolled all the way to the bottom. Note that the save (or cancel) button is still not visible. It is fixed in position under the keyboard.
Not shown: I have to close the keyboard to be able to click the save button.
And like I said, it is the same behavior when saving routes. And probably other forms.
The same thing happens when saving a recording. When I type the title, the keyboard covers the save button.
In the new version, it's back to how it used to be. Everything's fine.
just curious - up until V4.31.3.7 the APK size was around 90MB for a few years, then suddenly it jumped by a large amount to 146MB and has been around that size since - was that a new 3rd party library, or has @Menion been coding around the clock/ working too hard?20260206-082123-Locus and 1 more tab - File Explorer.jpg
Andrew, you could look into the apk, it's a zip file, eg rename extension. I don't have an old apk. Totalcmd can btw show all folder sizes.
@Andrew Heard
There was a lot of work last year with the update of native libraries for databases, coordinate conversion etc. And this caused a massive increase in the size. On the second side, updates over Google Play increased by only a few MB.
"Open in app toast" > it looks like Locus Map itself is trying to read the shared file and it ... fail :). "Share the file" works ok for you?
@Christian
Check route planner menu > settings > Keep manual segments option
Quote from: Menion on February 06, 2026, 11:50:28@Christian
Check route planner menu > settings > Keep manual segments option
No. Unfortunately that will not do it.
'Recalculate all' after switching back to another profile is not working either...
Quote from: Tapio on February 06, 2026, 06:46:23you could look into the apk, it's a zip file, eg rename extension.
thanks @Tapio - I never knew!
Quote from: Menion on February 06, 2026, 11:50:28"Share the file" works ok for you?
@Menion - that gives an error too - brief similar orange msgbox "problem with file" + <name of the track> to share, but then 2nd green msgbox "process successful". I am using main directory Android/media, without any other issues other than above.
@Andrew, did you find anything? In TC you can also longtap apk, "Open as zip". There's many file types out there which are just renamed pkzips, eg epub.
Quote from: Menion on February 05, 2026, 12:25:49- fix: getting stuck at 100% during start in rare cases
I have not seen this for quite some time, but now the issue is back.
- I leave house. LM may be running in the background or not.
- Tasker detects I left house.
- Recording is started via ACTION_TASK, "tasks: { track_record : { action: "start", name: "AutoRec", auto_save: true } }"
- At some random point in time I turn on my phones screen and tap Locus, and the 100% screen instantly appears. I'm having a hard time to make it start then.
I think I reported this long ago, then the situation was OK until your recent fix. Android 10. Will look if there's some usable log next time. OAM maps.
Quote from: Tapio on February 07, 2026, 09:23:48@Andrew, did you find anything?
@Tapio - as per Menion's comment, I just assume there was some library change. I did open two as ZIPs, and note there are a huge # folders, so to be honest, I then couldn't be bothered searching each one & comparing for a different file and/or size.
@Christian
I'm unable to simulate it. With "Keep manual segments" disabled, the app always recalculates all, even manual, segments. If this is crucial for you, a short video with steps from the clean route planner to this problem may help here a lot. Thanks
@Andrew Heard
opening shared track > it looks like the app is trying to open its own shared link and fails. May you try to "Clear defaults" for the Locus Map in system settings? Thanks
@Tapio
same with the recent 4.32.4 version? We made a change there, that may have influence on this problem.
Quote from: Menion on February 09, 2026, 09:18:40same with the recent 4.32.4 version? We made a change there, that may have influence on this problem.
That's the thing, this version re-introduced the problem for me.
Quote from: Menion on February 09, 2026, 09:18:40May you try to "Clear defaults" for the Locus Map in system settings?
@Menion - after clearing "temporary files", I performed an Export with both SHARE THE FILE and OPEN IN APP, but exactly the same orange error messages as previously reported. I had Wifi enabled.
20260210-082536-.jpg
Quote from: Menion on January 29, 2026, 14:38:04@Žajdlík Josef
Hmm, I see no problem here. Both maps version 2024+? No other vector Czech or Slovak map in the device? Auto-loading for vector maps in the settings enabled?
Today I noticed the same between Austrian and Hungarian offline maps. No automatic loading.
Greetings, Ulrich
New Beta version 4.32.4.1
- chg: (GOLD) Android Auto support - seamlessly connect Locus Map on your phone and tablet to your car's infotainment system, view your favourite maps, search for places and addresses and navigate on your in-car screen!
- add: enabled display of local photos/videos in the track detail for recorded tracks
- chg: experimental enabling of possible map tilt
- chg: Android Auto now Gold Premium only
- chg: (GOLD) LoPoints visible in the Android Auto
- chg: (GOLD) improved Android Auto notifications
- chg: (GOLD) correct street name reporting in Android Auto
- fix: (GOLD) Android Auto notification updates for navigation
- chg: (GOLD) active auto-zoom working in Android Auto as well
- chg: (GOLD) keyboard not appearing by default in Android Auto search
- fix: autoload of vector maps
- fix: search in cyrillic script
- fix: rare crash during sorting of tracks in My library
- fix: crash when using Aghem language on the device
- fix: duplication of Geocaching filters when using "All geocaches" filter
- fix: handling of osm.org links
Quoteexperimental enabling of possible map tilt
"tilt" is not found in search dialog, where to find and enable?
Quote from: Menion on February 13, 2026, 15:46:39- fix: autoload of vector maps
Yes, you've successfully prevented my OAM map from loading. Not showing up after refresh any more. It's /Android/media/menion.android.locus/MapsVector/Nordrhein-Westfalen_oam.osm.map
Photos in track window, maybe needs a menu entry or some show/hide toggle. But definitely good stuff. I noticed it probably works by date, not pos, because WhatsApp photos showed up.
Maybe you can clarify how it finds them. I have some tracks where it didn't display any, but they exist.
Quote from: Tapio on February 13, 2026, 17:19:02...
Photos in track window, maybe needs a menu entry or some show/hide toggle. But definitely good stuff. I noticed it probably works by date, not pos, because WhatsApp photos showed up.
...
@Tapio: I will install and test the new beta on my second device next week, but in the earlier beta from last summer, there was a "show Media" option in the settings under Points and Tracks, Cut Tracks. Perhaps it can be found there now as well.
Yes, the photos are displayed based on the timestamp if it is within the track recording. Regardless of the source and regardless of geotagging. And regardless of where they are stored on the device or even if they were moved later. At least that's how it is in my old beta 4.30.1.8.
Curiosity got the better of me and I ended up installing the current beta on my main device. Everything looks fine. 🫡
A question for Menion: In the track gallery, there is a small icon displayed on the thumbnails, which was not present in the earlier beta. What is the purpose of these icons?
Most of my pictures aren't displayed in track window. I found the reason - LM uses file system date/time, not EXIF.
After hiking, I usually convert the photos for my smartphone, then they'll have a different timestamp on file system side.
I will re-convert them and preserve the original timestamp. Or maybe exiftool can copy the timestamp from exif to file system, hmm....
The advantage of using pictures in this track view context over the "geotagged media" is, here we have at least some very basic picture viewing system: swiping from one picture to the next...
Btw, attached: My wife sent me a picture of her breakfast while I was hiking. LM thinks this is important 😁
@Tapio
For android
https://play.google.com/store/apps/details?id=eu.duong.imagedatefixer
And/or
https://play.google.com/store/apps/details?id=eu.duong.picturemanager
My current photo work flow is :
Take photos with my smartphone but without localisation.
Modifiy them if needed, then export gpx of my activities, and use second app to geotag my pictures thanks to gpx timestamps vs exif taken one.
And cherry on the cake, file modification date is setup again to exif taken date.
Lots of possibilities.
Quote from: Tapio on February 14, 2026, 07:59:40Most of my pictures aren't displayed in track window. I found the reason - LM uses file system date/time, not EXIF.
After hiking, I usually convert the photos for my smartphone, then they'll have a different timestamp on file system side.
I will re-convert them and preserve the original timestamp. Or maybe exiftool can copy the timestamp from exif to file system, hmm....
The advantage of using pictures in this track view context over the "geotagged media" is, here we have at least some very basic picture viewing system: swiping from one picture to the next...
Btw, attached: My wife sent me a picture of her breakfast while I was hiking. LM thinks this is important 😁
I have the same problem: images are displayed that don't belong there. WhatsApp images, screenshots...
I only want to see pictures there that I took with the camera. I don't have the date problem, but sometimes I get pictures without EXIF data and I save them in the folder where the pictures from the camera are. So it would be good to use the EXIF data first, and if that's not available, the save date or date in the name. If I get the pictures later, the save date won't be correct. Or can that be changed?
Photo workflow for me is complex... backup, add exif timestamp from gpx if missing (Geosetter), add City etc. names (GeotagNinja on Github, since Geosetter is forever broken here), imprint some info and position QR code via XNview batch processing.
Then copy from PC back to smartphone. For LM mostly into very few folders with many files, because "Geotagged media" functionality can not be handled if there's 100s of folders.
Mick thx for the img date fixer link, I quickly fixed all my pictures.
In the picture viewing, swiping to the next picture is weird. On first swipe attempt, the Android top bar becomes visible. A second swipe is required to move to the next picture.
BIG THANK YOU @Menion, LM now quickly finding the related pictures is so cool.
But it all comes at a price. Anyone able to still use OAM maps? Mine didn't auto load and upon manually loading t it doesn't get listed in LM. And it complains.
EDIT. I re-imported via locus-actions://https/www.openandromaps.org/wp-content/library/xmlV5/Nordrhein-Westfalen.xml and it works now.
Suggestion. Longtap small thumbnail picture and start system photo app? Or even vice versa. For me system viewer is F-Stop. From there I can instantly swipe through pictures in fullscreen. Makes things very usable!
Another thing. If those pictures have gps positions one would want to jump to the related position. So another idea: longtap thumbnail picture - if has gps pos, close track window, center to place and show a photo waypoint.
I don't like the symbol on the small pictures.
Quote from: balloni55 on February 13, 2026, 16:39:22Quoteexperimental enabling of possible map tilt
"tilt" is not found in search dialog, where to find and enable?
Yesterday, I discovered this feature by chance; it appears to be enabled by default. If you swipe down lightly with two fingers, the map tilts slightly.
Unfortunately, there does not seem to be a way to disable this feature yet.
Speaking of tilt: for me, the map is incomplete, when tilted.
Screenshot_20260215_174935_Locus Map.jpg
LG uk
@ Ulrich Kiermayr:
I assume that this is intentional or perhaps unavoidable. Due to the perspective, the map elements would have to be displayed smaller and smaller/closer together on the horizon (theoretically infinitely), which would no longer be possible to render meaningfully.
Quote from: Graf Geo on February 15, 2026, 20:45:48@ Ulrich Kiermayr:
I assume that this is intentional or perhaps unavoidable. Due to the perspective, the map elements would have to be displayed smaller and smaller/closer together on the horizon (theoretically infinitely), which would no longer be possible to render meaningfully.
I don't think so. Given the visible street names in the blank area, there is no (in) visible horizon. It is just a little tilt where there is still only ground visible. Moreover, a horizon would be a straight line (not a 90°corner)
To me it looks like there are just three tiles missing on top.
Greetings, uk
@Ulrich Kiermayr:
seems like tile-rendering is as usual (screen plus some super small margin), but with using tilt you can look into the not-rendered-tile-area.
This small tile-rendering-window is generally somewhat annoying, you can move the map back and forth or slip while checking your area and everything needs to get rendered each time. Waste of processing.
Tilt is very nice with map shading enabled, like it 8)
A strange error when the map is tilted: I am searching for a location that is outside and south of the current map section, e.g. Innsbruck. The red circle with an arrow is displayed at the top and points north. When I flatten the map again, the arrow jumps down and points in the correct direction.
This also happens (sometimes irregularly) with locations in the west/east. E.g. Warsaw, see screenshot.
@Graf Geo icon at photos > it should indicate that these photos are only local, not stored directly in the track or Locus Map. It is a small preparation for the future synchronisation of attachments. Then we will need to distinguish which photos are persistently attached in the Locus Map and which are not.
@Tapio date > Locus Map is not taking data directly from photos. It communicates with the Android system that has its own "Media database". How exactly they get data from photos > we do not know for sure. But I really expect that EXIF plays the main role.
Breakfast > now you perfectly know, what happended during your trip :)
Swiping problem >
will look at it, thanks., hmm can't simulate it. No matter if top panel is visible or not, swipe works as expected.
Opening in external app > first request on this here. Not sure if this is extra useful. Locus Map should not replace a photo browser app, but here we should get a quick overview of a few photos taken during trip, nothing more. But you still can open a photo and in the three-dot top menu is "Open" option.
Display on photos on the map > I already had an idea to display these photos directly on the map when the track is highlighted. Maybe later ...
@freischneider filter some WhatsApp etc photos ... I'll look at it. About "EXIF" first > as I wrote about it to
@Tapio, we do not have this under control.
And tilt, yes. Area of rendering in larger than without a tilt, but still not enough. Hmm... ::)
After installing the new beta version, switching maps works without problems. Thanks.
Yeah for me swiping only works perfectly, when top (15/32) and lower bar (with the filename) are shown. They disappear after one tap. Now in that state, it requires two swipes. After the first, the Android top bar appears and after the second, the swipe works.
Fullscreen option in Locus Expert settings is off. Android 10.
Do we really need that icon on the small pictures?
Being able to display the track related photo pois on/off would be nice. Maybe you can link them to the displaying of the track in some way. Also, centering to it, coming from the thumbnail or photo viewer.
I noticed a consistent crash. I did some heavy file dates changing on 1000s of pictures. I then used "Full reload" in Geotagged media. I always saw the number of listed (in the "Geotagged media" screen) per directory photos decrease down to zero, as if it unloads, as a first step.
Then it crashed. After restart LM, the scan worked its way through.
Serious problem with recording:I did some longer tours this weekend, and everytime after a longer break (>5min, I think), Lotus was not recording anymore. Recording mode itself was still on, I didn't pause the recording. I could recover by turning GPS off and on again, which is of course annoying with gloves in the snow.
I first thought I had some setting wrong, but all of these were off:
- Auto-pause
- Record only when moving
- Record when GPS is off
- Notify of (pausend/pending) recording
Dunno in which version that started, I noticed some problems already end of last year, but didn't go on tour for a while, only used Locus for navigation, and it doesn't happen when screen stays on.
However, I can say with conviction it's not a hardware problem: I recently recorded skiing holidays with two different special skiing apps, and both had no problems, screen off, in my pocket, even with 1hr+ lunch breaks.
Anyone have similar experience?
Quote from: slarti76 on February 16, 2026, 17:11:41Serious problem with recording:
I did some longer tours this weekend, and everytime after a longer break (>5min, I think), Lotus was not recording anymore. Recording mode itself was still on, I didn't pause the recording. I could recover by turning GPS off and on again, which is of course annoying with gloves in the snow.
I first thought I had some setting wrong, but all of these were off:
- Auto-pause
- Record only when moving
- Record when GPS is off
- Notify of (pausend/pending) recording
Dunno in which version that started, I noticed some problems already end of last year, but didn't go on tour for a while, only used Locus for navigation, and it doesn't happen when screen stays on.
However, I can say with conviction it's not a hardware problem: I recently recorded skiing holidays with two different special skiing apps, and both had no problems, screen off, in my pocket, even with 1hr+ lunch breaks.
Anyone have similar experience?
If you also have Android 16, then it's a Samsung problem.
https://forum.locusmap.eu/index.php?topic=9452.0
Quote from: freischneider on February 16, 2026, 17:43:55Quote from: slarti76 on February 16, 2026, 17:11:41Serious problem with recording:
I did some longer tours this weekend, and everytime after a longer break (>5min, I think), Lotus was not recording anymore. Recording mode itself was still on, I didn't pause the recording. I could recover by turning GPS off and on again, which is of course annoying with gloves in the snow.
I first thought I had some setting wrong, but all of these were off:
- Auto-pause
- Record only when moving
- Record when GPS is off
- Notify of (pausend/pending) recording
Dunno in which version that started, I noticed some problems already end of last year, but didn't go on tour for a while, only used Locus for navigation, and it doesn't happen when screen stays on.
However, I can say with conviction it's not a hardware problem: I recently recorded skiing holidays with two different special skiing apps, and both had no problems, screen off, in my pocket, even with 1hr+ lunch breaks.
Anyone have similar experience?
If you also have Android 16, then it's a Samsung problem.
https://forum.locusmap.eu/index.php?topic=9452.0
Thank you, but as I already mentioned in the original post: Multiple other apps with recording functionality have
absolutely no problem picking up recording after breaks of even more than an hour. Without fail. While yes, I have S24+ with Android 16, it still must be on Locus side (of course, could be an interaction with specifics of A16, but it's definitely not a Samsung HW bug).
I'd cautiously agree with that. At the very beginning, when I had the S24, all GPS systems like Google Maps, GPS Status, and Locus Map had these problems. However, I no longer have any issues with navigation on the S24 using Google Maps. There may have been a problem with GPS usage some time ago, but Google Maps seems to have resolved it now.
Menion, I noticed a side-effect regarding the track-display of geotagged photos.
If I made manual extensions to tracks in the past, e. g. because a part was missing, geotagged photos do not show up.
Either it does not like the internal additional track segment or it gets confused because the track has 1970-01-01... timestamps in trackpoints. So what I did to resolve this was: gpx export, merge track segments, replace 1970 dates with surrounding ones, then gpx import.
Track display of geotagged photos. great feature, did I say that already? 😁 👍
Maybe it's a good idea to include it as a display option for tracks and folders (like the track coloring, thickness etc.)
Reason: I also store tracks of other people. Locus ofc shows my photos also there.
New Beta version 4.32.4.2
- chg: completely new chart system in the track detail
- chg: improved track guidance auto-zoom logic & fix jumps when zooming to nav points
- chg: highly updated "Smooth movement" system. Now also usable during navigation (still needs more love next week)
- chg: major speed update in unloading points (and partially also loading)
- chg: updated list of add-ons/co-apps
- add: option to purchase missing LoCoins during map mass update
- fix: open quick bookmark correctly in preferred app
- chg: disabled optional map tilt, again, sorry
Few notes:
- tilt is not working properly. I've disabled it for now. It simply needs more "love"
- new Chart library is now used only in the detail of the track. Let's play a while with it. If all works as expected, I'll step by step unite (finally) all charts in the app. Info: Colours for the chart in the expert settings are ignored here. Because I need colours for light and dark mode, these settings no longer make sense and should be removed later.
@slarti76
recording problem: try to switch Settings > GPS & sensors > Google services assisted location. You probably have this enabled (default), but it starts to cause a problems on some devices so give it a try and disable it.
I just installed the new beta 4.32.4.2. Thanks!
The favourites function (quick bookmarks) now opens the desired app correctly. 👍
The new settings options for the track diagram are nice, but it would be even better if you could hide it completely.
Tilt removed: well, it wasn't that important to me.
Do you mean to hide the chart panel completely? For all tracks, or just recorded, planned, imported, ... ? ???
I had mentioned before (and I wasn't the only one) that the diagram takes up a lot of space when you don't need it. For example, in flat regions.
Now that you've added this setting option (for x, y-axis, etc.), an additional option to "hide diagram completely" might be a good option. This would allow you to set it individually for each track. I want the elevation chart for tracks in the mountains, but not in flat terrain.
If it's easier to implement, an option in the settings would also be conceivable (like "show media"), only then "show charts".
Addendum:
Here are two examples. In the mountains, the diagram is informative and useful, but the second diagram (flat terrain) is completely superfluous and a waste of space.
Setting speed instead of altitude doesn't help either. We usually hike at a fairly steady pace of around 4.5 km/h.
Hello Menion,
after installing the latest Version 4.32.4.2 the App freeze after chosing a track. Shortly afterwards an error message appears.
The track panel didn't respond.
Android 14
The beta test of the map manager doesn't fit screen-to-screen while the "Add"-button is under the lower Border.
Android 14, App 4.32.4.2
Hi guys,
if there is a chart that does not look ok, please share it with me over the "Share by link" option. With this, I should get an identical copy to what you see on your device. There are a lot of changes in the background, so it is possible that some charts won't look ok. I'm ready to fine-tune it next week!
And
@WildWortWechsel , where have you found this Map manager version? :D. It is already 5+ years old, and I thought it was private. Anyway, don't use it. It needs to be rewritten from scratch. Hopefully this year ...
And the problem ... tap few times on "Wait" please ... and then share the track. I'll look at it as soon as possible. Thanks!
That chart view, it feels great swiping over it - and the map smoothly moves in the background. BUT. This can only be done while the chart is almost not visible. Not sure how a solution could be like.
EDIT Ah, it's because of the photos, maybe there should be a way to collapse them.
Yes, and its not possible to hide the position marker in the chart (with height and/or other data)...
Quote from: Menion on February 20, 2026, 20:35:46And @WildWortWechsel , where have you found this Map manager version? :D. It is already 5+ years old, and I thought it was private. Anyway, don't use it. It needs to be rewritten from scratch. Hopefully this year ...
Quote from: Menion on February 20, 2026, 20:35:46And the problem ... tap few times on "Wait" please ... and then share the track. I'll look at it as soon as possible. Thanks!
Can I send it to you per email?
Quote from: Menion on February 20, 2026, 15:19:56@slarti76
recording problem: try to switch Settings > GPS & sensors > Google services assisted location. You probably have this enabled (default), but it starts to cause a problems on some devices so give it a try and disable it.
Already tried that during the tour, pretty sure it didn't make a difference, but I'll play around with it some more...
A few thoughts and suggestions regarding the diagram in the track info panel:As Tapio already mentioned, it is difficult to display both the map and the diagram simultaneously in a meaningful way. Currently, there are only three options:
- Map with track only
- Map and track info panel approximately 50:50 on the display, with the diagram too far down
- Track info panel covers the entire display, map is not visible.
Option 2 is particularly bad if you have activated the track gallery and/or the track title spans several lines. Then you can't see anything of the chart. Perhaps the track info panel could be made scrollable or allow more vertical positions so that the map and chart can be viewed simultaneously.
See image 1.
As I mentioned earlier, the chart is not always useful or necessary, and sometimes it just takes up space. The chart settings should include an additional option to "Hide chart".
The new chart settings (axes, units, etc.) are currently applied globally. They are applied to all tracks in all folders. In my opinion, this is not useful.
I would like to be able to choose how they apply:
- Only for the current track
- For the folder
- For all tracks
In principle, this would be similar to the line colour settings. This could be included in the corresponding menus, see image 2.
These are just ideas and suggestions that I would like to put up for discussion.
It's great for me. But I rarely need the height diagram. Images are more important to me. But still, here's an idea. Most sections have a small arrow on the right for more details. There could also be one on the left for less or hide. Only the heading for the section remains and the small arrow to show it again.
Another idea is to add a small option, arrow, or ? to the height diagram to hide the other information. That way, I can view only the map and the diagram. Clicking on it again makes everything visible again. However, everything is visible again the next time it is opened.
The new route detail chart is great. I would also like to add a button to it: "show only graph and map". So that I can then move my finger along the graph to follow the map and check, for example, data about the slope of the track or the hills.
@WildWortWechsel
give a try to the next version tomorrow and if there are still any problems, the best is to send it over a personal message here at the forum (small icon under my photo).
---
Thanks to all for the tips and wishes regarding the chart. I see it similar in many ways ... but not yet. I need to first invest a little more time to track detail, to make it more flexible. Customisation is planned, but as a second step.
As I wrote before: if the new chart works correctly, I'll try to adapt it in the rest of the app.
What seems overdue to me since years: when I tap on a track, the overview window pops up, you can slide maniacally through the graph, the map following lightning fast - but you never know the point in time. To get there you have to start a tedious clicking. Easy fix for Menion, I suppose :-)
Quote from: michaelbechtold on February 26, 2026, 22:05:39but you never know the point in time
@michaelbechtold - worse for a recorded track, and wanting to know clock-time of an arbitrary point - tell me if a quicker way - library > track > make visible > tap desired point on map > tap "i" icon (bottom LHS) > drag up - note created timestamp. Not even for first or last point is there a quick statistic or method. Has been discussed before, maybe a few years ago with configurable track statistics, but it never made it to public.
New Beta version 4.32.4.4
- fix: (GOLD) navigation line correctly sized in Android Auto
- chg: improved track chart axis step calculation
- fix: missing charts for 200+ km long tracks/routes
- chg: another iteration in the "smooth movement"
- chg: improved speed of map rendering for vector maps
- fix: (GOLD) problem with clicks on smaller Android Auto devices
- chg: (GOLD) improved Android Auto map rendering and notifications
- fix: invalid chart in case of track without times
- fix: (SILVER) problem with incorrectly defined WMS maps
- add: (GOLD) option to enable/disable termination of navigation when Auto disconnects
- fix: (GOLD) missing start of voice commands on Android Auto
- chg: minor graphical update in track detail bottom statistics
@michaelbechtold & @Andrew Heard
You both speak about the absolute time of a certain trackpoint, right? Hmm ... ???
Quote from: Menion on February 26, 2026, 14:40:13@WildWortWechsel
give a try to the next version tomorrow and if there are still any problems, the best is to send it over a personal message here at the forum (small icon under my photo).
---
Problem solved! Thank's!
Quote from: Menion on February 27, 2026, 15:46:03You both speak about the absolute time of a certain trackpoint, right
@Menion - yes I chose my word "clock-time" (or time-of-day) HH:MM{:SS} - eg. what was the time I started or finished the ride, or what was the time when I got to point I tap on map. I don't know an easier way to find this out at present.
Yes, Andrew.
@Menion: Locus has all information at hand when you tap on a track:
- Locus correctly finds the point on the graph
- i.e. it knows the delta time from start
- it displays the start time on top
- addition is a no-brainer, right?
Cheers
Michael
The problem is only a place, where to add it.
And also a simple fact, that I would firstly like to do rework to the UI system we have been using in the app for the last two years. It simplifies the modification and creation of UI a lot.
"Best interval" as it stands now is pretty mus useless - my opinion. But if you like that still: the font for distance, duration, ups and downs is huge, you can easily put the absolute point in time in there reducing that for all of them. You could even drop those two, as the graph gives a clearer picture anyway. And when people are religious about cm, those are one click away.
While the point time is a dozen clicks away, as Andrew pointed out in detail.
We have waited for years, hence if you put that into your overall restructuring of that screen, I'd be happy still ;-)
While I understand, we have two distinct views (track / point) I also think, trackpoint absolute time is of highest interest in analysis situations. Too buried rn.
And now since the map jumps and selects trackpoints when clicking on the graph, the interest in trackpoint time is even higher.
"Best interval" section, useless for me. And the waypoint representation on that screen - They could rather appear as tiny markers in the graph.
Hello Menion,
since the latest beta 4.32.4.4 the App did crash several times. The last few times during a track copy procedere but also while analyzing the elevation graph.
Android 14
I have also recently experienced crashes since Beta 4.32.4.2.
This happened several times during track recording when I set a quick point.
A message then appears stating that memory overload may be the cause and that one should not display an excessive number of tracks and points. However, I only had a few tracks and a moderate number of points visible. Shading was off.
I will continue to monitor this.
I've never used the "Best Interval" setting. I think very few people use it. For me, it's just part of the general track data. That's where the general statistics for the track are. That also includes energy consumption, which is related to performance.
About best interval, in fact, i didn't understand really this feature (in Locus :) )
To me, the best interval (for example the best 1km) should be the best "moving interval", meaning the best kilometer (faster for example) over the entire activity.
But Locus is "just" splitting the activity into interval (1km for example) and then highlight the best and worth of those splits.
This is same activity split and best interval from Locus : fastest = 6km to 7km = 8:08
Screenshot_20260301_105215_Locus Map.jpg
, while the real best kilometer is 7:09, between 6km51 and 7km51
Screenshot_20260301_105159_Chrome.jpg
Hello menion,
the point notification isn't working for me. I can't say how long it's been like this, but it's been the case for at least the last two betas.
My settings are one-time notification, 20 metres, 2 beeps, vibration.
The tests in the settings window work.
A few more comments:
Point notification: (see ballonis post) – error confirmed, does not work.
Crashes: (see here (https://forum.locusmap.eu/index.php?msg=80552)): It happened again yesterday. I was just recording while on the move and taking the occasional photo. When I looked at the screen again a few minutes after last looking at it, Locus had already crashed. I restarted the app, the recording continued, but I had a gap of about 100 metres.
This probably doesn't help, but I don't know if my user ID helps (eeee4156c), or if and when I should create a log (immediately after restarting?).
Route planner: I hadn't noticed the new profile management in the route planner (app). Finally, you can set whether a profile change should generally recalculate the entire route or not (checkbox at the bottom). Good!
"Best Interval" (Mick FU's post): I'm happy with the current display. I use it occasionally for my jogging routes, so I can see when I start to slow down, for example. ;) It's perfectly adequate for me as an overview. You can set short intervals if you want to have sections that are as accurate as possible.
Track point time: I would also find it very helpful to be able to see the time when I was at a track point more quickly. Currently, it is really very cumbersome, as already described.
@WildWortWechsel
your route seems to be 2k+ long :( ... may you share it with me for test over track detail > bottom "Share by the link"? Thanks
@balloni55
thanks for the bug-report! Serious problem caused by the work on "Smooth movement" that also causes problems in track navigation!
@Graf Geo
Unfortunately, I do not see any error in Crashlytics. After that crash, long click on the main menu > "Report bug" and send it over email to locus.map@asamm.com, thanks! Just add not "For Menion, forum". I'm not too active on the help desk now.
"Best interval" > many ideas without any comments and now everyone (almost) considers this useless ;D. Later, but should be improved, agree. I was also never happy with it, but no one complained ... :P
Bes
Quote from: Graf Geo on March 02, 2026, 11:55:28Crashes: (see here (https://forum.locusmap.eu/index.php?msg=80552)): It happened again yesterday. I was just recording while on the move and taking the occasional photo. When I looked at the screen again a few minutes after last looking at it, Locus had already crashed. I restarted the app, the recording continued, but I had a gap of about 100 metres.
me too, 2 silent crashes around 4.32.2.2 while recording track (no UI activity); I hadn't previously had any for years; it is when I wrote about a (Tasker) watchdog (https://help.locusmap.eu/topic/39687-is-there-a-watchdog-style-app-to-ensure-locus-map-remains-running) (which I haven't yet written). Unfortunately when in the middle of an activity it's often not a good time to be reporting bugs/ crashes sorry.
@Andrew Heard: Yesterday evening at home, I created a log like this for the very first time. The logs.zip contains six txt files from the last six days (see screenshot).
I have no idea what the log texts mean, but I was able to find some of the restarts ("NEW START") I performed after crashes, as I still remember exactly when they happened. So apparently you don't have to do the reporting immediately while on the road.
(Question for the experts: am I right?)
@Graf Geo, sure that, logs are created for later analysis (here, through asamm). And it always helps if you can tell at what time the issues exactly happened.
Quote from: Andrew Heard on March 03, 2026, 00:42:54I wrote about a (Tasker) watchdog (https://help.locusmap.eu/topic/39687-is-there-a-watchdog-style-app-to-ensure-locus-map-remains-running) (which I haven't yet written).
Simple. Basic concept see below. Requires Locus Tasker plugin (essential anyway).
I did that once because an unnoticed crash is eeeevil worst case scenario 👹
https://taskernet.com/shares/?user=AS35m8kdDIMDeveQcQfRglam%2Fah1mTW%2FWcg05FZ39c0i1q%2F77iY3E7cIwxCkXqJTaTA%3D&id=Profile%3ALocusAliveTest
@Tapio: Where can I get the Locus Tasker plugin? It is no longer available in the Play Store.
Oh, didn't know that. Maybe contact Falco via his Github.
I asked: https://github.com/Falcosc/locus-addon-tasker/issues/41
Hello.
In Beta 4.32.4.4, the application crashes when the compass screen is displayed.
Quote from: Agus on March 03, 2026, 16:58:34In Beta 4.32.4.4, the application crashes when the compass screen is displayed.
Which Android? Not crashing here, Android 10.
Hello Menion,
switching between some visible Tracks sometimes cut off the upper line of the track info, if there are more then one line of text.
I (Android 16) also have no crashes with the compass.
Quote from: Graf Geo on March 03, 2026, 19:01:37I (Android 16) also have no crashes with the compass.
This happens when GPS is enabled. If I do not enable GPS, the application does not close.
Quote from: Tapio on March 03, 2026, 10:08:00Simple. Basic concept see below. Requires Locus Tasker plugin (essential anyway).
thanks @Tapio @GeoGraf. My idea for a "tasker profile" for more basic - if Android process Locus not found in list then simply restart.
Quote from: Tapio on March 03, 2026, 17:42:15Quote from: Agus on March 03, 2026, 16:58:34In Beta 4.32.4.4, the application crashes when the compass screen is displayed.
Which Android? Not crashing here, Android 10.
In Android 16
Quote from: Agus on March 03, 2026, 19:28:51Quote from: Graf Geo on March 03, 2026, 19:01:37I (Android 16) also have no crashes with the compass.
This happens when GPS is enabled. If I do not enable GPS, the application does not close.
No crash even with GPS enabled. Sorry.
Quote from: Graf Geo on March 03, 2026, 21:52:06Quote from: Agus on March 03, 2026, 19:28:51Quote from: Graf Geo on March 03, 2026, 19:01:37I (Android 16) also have no crashes with the compass.
This happens when GPS is enabled. If I do not enable GPS, the application does not close.
No crash even with GPS enabled. Sorry.
On a Xiaomi 15T Pro (Android 16), I turn on the GPS, go to the compass screen, and after a few seconds the screen freezes and then the application closes. This does not happen with Locus Map 4.32.4, nor does it happen on other devices with Android 10 or Android 15.
I have uninstalled and reinstalled the latest Beta several times on the Xiaomi 15T Pro and it continues to fail.
Hi guys,
new version 4.33.0 just published. Also on the Google Play to the 5% of the users. But firstly, it needs to pass a validation and I'm still not 100% sure, that Android Auto won't cause a troubles.
Anyway, the version is out and ready to play. It should be stable and I believe that most of the reported crashes will be fixed.
Forum link (https://forum.locusmap.eu/index.php?topic=9553.0).
What I see that miss my comment ...
@WildWortWechsel
cut to panel > let it be for now, please. We will work on the track detail next week(s), so I hope it will be fixed as a "side-effect".
@Agus
try please also the final 4.33.0 version, thanks