New Locus Map (4) version
Important links
- list of news (https://help.locusmap.eu/announcement/locus-map-android-version-4-33-032026) of public versions
- Public versions (http://bit.ly/lmVersions)
- Beta versions (http://bit.ly/lmVersionsTest)
Versions
4. 3. 2026 - Locus Map 4.33.0
Hello.
The problem persists when I select the compass with GPS enabled on Xiaomi 15T Pro (Android 16).
Hello Menion,
viewing a long track is so fast now and without any problems. It seems also the library is faster as before.
There was also no crash until now.
Thank you!
Track thumbnails Line thickness still much too thick
In recent years, changes have been made to the line thickness in the track thumbnails several times. Most recently, they were actually quite optimal, even with version 4.32.4.
With the current beta (Edit: and also in the brand new 4.33, which I have just installed), the lines created are much too thick, making it difficult to see the course of the track. The circuit around a narrow lake becomes a fat sausage. The city tour becomes a thick blob of colour.
See image.
Quote from: Graf Geo on March 04, 2026, 14:00:59Track thumbnails Line thickness still much too thick
In recent years, changes have been made to the line thickness in the track thumbnails several times. Most recently, they were actually quite optimal, even with version 4.32.4.
It seems, the thickness in 4.33 is not the same for all previews. see image.
That depends on when they were created. Try updating them (long press on the thumbnail). 😎
I see.
I tried something with the diagram. When I trace the route on the diagram with my finger, I can easily follow the position on the map. Unfortunately, the kilometer information at the bottom of the diagram is not visible.
Suggestion: When I use the diagram, hide all other information. Just the diagram and map. This can be done with a button or by simply clicking on the diagram. To return, there is a back arrow in the upper left corner.
Optionally, the point information for the current waypoint could also be displayed. Perhaps there could be a button next to the back arrow to display and then return. The heading "Diagram" can be omitted when using the diagram.
See here: https://forum.locusmap.eu/index.php?msg=80555
I have now tested the point notification, and it is working again.
However, I noticed a silly problem concerning geotagged photos. I have activated the point notification. Now I take a photo while on the move. Shortly afterwards, the photo icon appears on the map. And it beeps because the point notification recognises this icon as a point and alerts me. Of course, this does not make sense.
I deactivated all folders in the point notification settings. Now there should be no alarm. Nevertheless, the sound is triggered for every new (geotagged) photo. Very annoying.
Bug? Or how can this be avoided?
Quote from: Agus on March 04, 2026, 11:36:01Hello.
The problem persists when I select the compass with GPS enabled on Xiaomi 15T Pro (Android 16).
I can confirm that. It's the same with my Poco F5.
Quote from: freischneider on March 04, 2026, 18:27:07Quote from: Agus on March 04, 2026, 11:36:01Hello.
The problem persists when I select the compass with GPS enabled on Xiaomi 15T Pro (Android 16).
I can confirm that. It's the same with my Poco F5.
no problem with compass/ GPS enabled for me, Samsung A35 Android 16
>viewing a long track is so fast now
confirmed
>Track thumbnails Line thickness still much too thick
agreed, the thumbnails in web Route Planner are also too thick
20260305-074809-Desktop and 1 more tab - File Explorer.jpg
when 4.33 installed & run for 1st time, this screen below was displayed & never progressed (I left for a few minutes)
20260305-074332-.jpg
I switched to another app, re-ran Locus, then all worked as normal.
Same on two devices. The progress bar remained stuck at 52%. On the S10, restarting Locus helped, while on the MotoE60, waiting a while was sufficient.
Quote from: freischneider on March 04, 2026, 18:27:07Quote from: Agus on March 04, 2026, 11:36:01Hello.
The problem persists when I select the compass with GPS enabled on Xiaomi 15T Pro (Android 16).
I can confirm that. It's the same with my Poco F5.
The error may be with the Xiaomi, Poco, and Redmi brands.
I just updated a Honor 200 to Android 16 and there is no error.
@Agus, @freischneider
crash in GPS screen > unfortunately, I do not see any automatic reports (yet). May you please send me a log from the app? Thanks.
@Graf Geo
line thinkness > I'll look at it, thanks!
POI alert on photos > heh, funny problem. Exclude geotagged photos from POI alert? Is this a solution you always want?
Waiting during start > hmm, some of you are not patiente :-X . App does a "vacuum" task on the database > result should be a lot lot faster access to data. On my own database, it took around 2 minutes, so I expected a very low number of users will have to wait too long.
Quote from: Menion on March 05, 2026, 13:47:12@Graf Geo
POI alert on photos > heh, funny problem. Exclude geotagged photos from POI alert? Is this a solution you always want?
Yes, ideally optional (if anyone would like to be notified when photos are taken). In any case, I don't want to be alarmed when I take a photo. ;)
Quote from: Menion on March 05, 2026, 13:47:12Waiting during start > hmm, some of you are not patiente :-X . App does a "vacuum" task on the database > result should be a lot lot faster access to data. On my own database, it took around 2 minutes, so I expected a very low number of users will have to wait too long.
@Menion - +5 minutes here waiting. I guess I wasn't expecting the startup time to be any different to other startups - just small text "update of databases" - could provide better warning to expect longer delay. But why on 2nd startup did it run immediately then? Was "vacuum" only once-off?
Quote from: Andrew Heard on March 05, 2026, 21:25:52Quote from: Menion on March 05, 2026, 13:47:12Waiting during start > hmm, some of you are not patiente :-X . App does a "vacuum" task on the database > result should be a lot lot faster access to data. On my own database, it took around 2 minutes, so I expected a very low number of users will have to wait too long.
@Menion - +5 minutes here waiting. I guess I wasn't expecting the startup time to be any different to other startups - just small text "update of databases" - could provide better warning to expect longer delay. But why on 2nd startup did it run immediately then? Was "vacuum" only once-off?
Same here. I gave up after 3 Minutes stuck at 52% and killed the app. Some indicator that the App is not stuck or frozen would be helpful. The restart after the kill also went *a lot* faster
Greetings, Ulrich
Thanks guys. I've improved this. During start > no change will happen next time. I'll make this "Optimise database" task optional somehow.
Quote from: Menion on March 05, 2026, 23:50:40Thanks guys. I've improved this. During start > no change will happen next time. I'll make this "Optimise database" task optional somehow.
Maybe an option somwhere around the clear cache in the menu? That would be the place I would look for such an option.
Hello Menion,
since a while sometimes the complete map is covered with hill top POI when zooming. Zooming in/out helps but I cannot use this zoom level.
Three days and Google is still testing and blocking the release ... hmm, nice, I love it ;)
Enough time for fine-tunning.
Version 4.33.0.1 (6.3.2026) - BETA channel
- chg: new chart system now used in Route planner and Track editor as well
- add: option to optimize My Library database (app Settings > FileSystem)
- add: progress animation during database initialization
- chg: more stable POI grouping colors
- chg: reduced default "Recalculate" distance to 50m (new users)
- chg: date selection now remember values during editing
- chg: improved selection of profiles in Route planner
- chg: memory optimization for offline address search
- fix: possible memory problem in the main menu & settings UI
- fix: missing GC Offlinizer images
- fix: track preview line width
@WildWortWechsel
this "hills everywhere" happens to you often? I've noticed something similar during start. Is this your case?
Fingers crossed: the indefinite hang when switching off gps usage (then need to kill on Android level, 1, 2, 3 restarts until proper start, also on my S25u) seems gone
4.33.0.1: I like the cross promotion ;-)
20260307-131659-.jpg
Quote from: freischneider on March 04, 2026, 18:27:07Quote from: Agus on March 04, 2026, 11:36:01Hello.
The problem persists when I select the compass with GPS enabled on Xiaomi 15T Pro (Android 16).
I can confirm that. It's the same with my Poco F5.
Quote from: freischneider on March 04, 2026, 18:27:07Quote from: Agus on March 04, 2026, 11:36:01Hello.
The problem persists when I select the compass with GPS enabled on Xiaomi 15T Pro (Android 16).
I can confirm that. It's the same with my Poco F5.
The problem has been resolved at Xiaomi.
Quote from: freischneider on March 07, 2026, 08:32:10The problem has been resolved at Xiaomi.
It has not been resolved on my Xiaomi.
Quote from: Agus on March 07, 2026, 09:23:35Quote from: freischneider on March 07, 2026, 08:32:10The problem has been resolved at Xiaomi.
It has not been resolved on my Xiaomi.
I have the same problem when I click on GPS/compass; the application crashes in Beta 4.33.0.1
I have Samsung S24 Ultra with Android 16
Quote from: Menion on March 06, 2026, 23:46:12@WildWortWechsel
this "hills everywhere" happens to you often? I've noticed something similar during start. Is this your case?
Never noticed it at/during start. Only during zoom in/out and only sometimes, but regulary whenever I use the App, which is almost daily. [Edit]: Here another example.
testing 4.33.0.1 beta
- My library: track preview is quite small, map size defined by their bounding box get only ~20% of vertical screen and additionally get covered by the (multiline)name. I suggest to make some categories waypoints, interval and details collapsable, at least they are almost empty or rarely of use IMHO but waste a lot of screenspace.
- route planner: planning at home..using 'Navigation/ guidance' and 'close' :) , then re-route doesn't work, everything is lost. I would like to be able to edit routing-details and continue planning, otherwise the temporary-route would be of no use, would be a petty for all the efforts.
- suggestion for routing-profiles
- road or cycling in general: add 'stick to cycle-routes'
- hiking, walking: add 'stick to hiking-routes'
I often prefer those routes as otherwise you might get routed along annoying or boring roads with traffic, traffic lights, small space, non looking pedestrians, etc. or you are facing buildings instead of nature
@Agus ,
@Morris75 amd others with crash in GPS/Compass screen
Unfortunately, I still do no see an automatic crash report on the Crashlytics system, and I'm personally unable to simulate this issue. May someone create and send me a log after the crash by this method (http://docs.locusmap.app/doku.php?id=manual:faq:how_to_create_debug_log)? Thanks!
@T-mo "track preview" > you talk about clicking on the map in My library, that opens a full-screen view to the track with a small map at the top right?
route planner issue > may ylou give me more precise steps? Thanks
suggestions to profiles > it is info for
@Radim V
Quote from: Menion on March 09, 2026, 10:00:30@T-mo
"track preview" > you talk about clicking on the map in My library, that opens a full-screen view to the track with a small map at the top right
route planner issue > may ylou give me more precise steps? Thanks
suggestions to profiles > it is info for @Radim V
- yes. Small map at top, name is overlayed (and covers part of the track, at least with multiline-names. Track-preview is still small, therefore any coverage feels more annoying than it actually is), below date/length/duration/etc, chart, waypoints (mostly empty here with my recorded tracks), Best interval (never used here), Details. I suggest to repeat the activity-icon at top. Activity of course always needs to be set separately, no correlation to used recording-profile. But that's ok.
- route planner > set start, set stop > menu Navigation/ Guidance > Close (nasty move ;) ) > select track > menu Re-route > empty, no start, no stop. I suggest to always make any planned track re-routable with all details once set, in general.
Still like the latest polishing, LM gets better and better..
Quote from: Menion on March 06, 2026, 23:46:12...
Version 4.33.0.1 (6.3.2026) - BETA channel
-...
- fix: track preview line width
...
Ok, for me now it is ok. Best width to recognize track on the tiny map miniatures.
POI alert on photos (see here (https://forum.locusmap.eu/index.php?msg=80595)) still there...
QuoteThree days and Google is still testing and blocking the release ... hmm, nice, I love it ;)
Is it now published? Can't find it in store.
On my (company) phone it isn't allowed to install from unsecure therefore I have to wait till publish.
On my tablet I can install directly from download link ... but is there a problem to use two different versions connected to the same (and only) cloud/web version?
Quote from: jonny.blue on March 11, 2026, 13:06:10QuoteThree days and Google is still testing and blocking the release ... hmm, nice, I love it ;)
... but is there a problem to use two different versions connected to the same (and only) cloud/web version?
No problem.
Hello Menion,
yesterday the App did crash twice during a copy procedere from one folder to another. No warning, just a black screen and a crash message. Happend around 9 p.m.
4.33.0.1
f1b115757
Android 14
I think there ist a nasty bug in Beta 4.33.0.1
Routes created using the route planner cannot be edited. Selecting 'Reroute' displays a brief 'Initialising' message, hides the route to be modified, and brings up the screen where I can create a completely new route. It's as if I were starting the route planner from scratch.
Routes created using the web planner can still be edited (once).
See screenshots.
Quote from: Graf Geo on March 13, 2026, 12:26:11I think there ist a nasty bug in Beta 4.33.0.1
Routes created using the route planner cannot be edited. Selecting 'Reroute' displays a brief 'Initialising' message, hides the route to be modified, and brings up the screen where I can create a completely new route. It's as if I were starting the route planner from scratch.
confirmed. The route is there again after canceling the router.
Hi guys,
it is starting to be a little confusing. The changelog below is my attempt to extract the changes since 4.3.
4.3. - first attempt with 4.33.0 (1205) version
6.3. - Beta version 4.33.0.1 (1206)
10.3. - my next attempt with the new version, but again 4.33.0, this time code "1207" (reason: why to publish bug-fix 4.33.1 when no first version was published. But to pass it to Google, I need to increase the version code).
13.3. - another Beta (Google still refuses to publish the app), now 4.33.0.2, but version code 1207 - no option to downgrade to previous Beta.
Changes since first public 4.33.0 version
- chg: new chart system now used in Route planner, Track editor and Weather forecast as well
- add: option to optimize My Library database (app Settings > FileSystem)
- add: progress animation during database initialisation
- chg: more stable POI grouping colors
- chg: reduced default "Recalculate" distance to 50m (new users)
- chg: date selection now remember values during editing
- chg: improved selection of profiles in Route planner
- chg: memory optimization for offline address search
- fix: possible memory problem in the main menu & settings UI
- fix: missing GC Offlinizer images
- fix: track preview line width
- fix: times in Weather forecast in different time zones
Since 4.33.0 V2
- chg: major unification in Image loading system
- fix: ignoring custom folder sort in rare cases
- fix: inability to reroute saved routes (routes saved with prev. version can't be restored, sorry)
- fix: crash in "Copy items" dialog
- fix: rare crashes when restoring the app from background
- fix: stuck in the GPS/Compass activity
Have a nice weekend!
The GPS/compass issue has been resolved.
Thank you very much.
Quote from: Graf Geo on March 13, 2026, 12:26:11I think there ist a nasty bug in Beta 4.33.0.1
Routes created using the route planner cannot be edited.
identical to pt.2 in #28 and #30
confirmed
maybe obsolete with mentioned fix (menioned fix ;) ) since 4.33.0 V2
fixed with 4.33.0.2 beta
Quote from: T-mo on March 13, 2026, 17:31:58Quote from: Graf Geo on March 13, 2026, 12:26:11I think there ist a nasty bug in Beta 4.33.0.1
Routes created using the route planner cannot be edited.
identical to pt.2 in #28 and #30
confirmed
maybe obsolete with mentioned fix (menioned fix ;) ) since 4.33.0 V2
fixed with 4.33.0.2 beta
4.33.0.2: The route planner editing bug has only been partially fixed. It works again for routes created now, but the error persists with all the routes I created previously.
This is frustrating, as I had planned a large number of routes in advance that I intended to refine later.
Edit 19:50: I should clarify that the bug seems to only occur with routes created in the last few weeks (Feb. – March 2026?), whilst older ones can still be edited. I have to check this in detail...
Why are photos that I added to the track whilst recording it being displayed twice? The duplicate has a mobile phone icon in the bottom right-hand corner.
Similarly, are photos from a POI near track that isn't linked to the track simply being displayed in the track preview with the mobile phone icon?
@Graf Geo
ah, there is probably a problem with routes from 4.33, not just from last Beta. Oki, I'll look at it!
@balloni55
Good point, thanks. System of displayed photos is simple: you display the track, the app finds all photos that were created between time of the first and last trackpoint, and display it. I'll look at it and try to exclude manually added photos.
---
I've also found a crash in "My live location", sorry for this if anyone use this function.
@Balloni, photos are picked by time and thats via Androids Media database.
@menion
oK thanks and why are the track photos displayed twice?
If the photos aren't on your system twice - you may check Google Photos - refresh media store (ask Google). Imo Locus should add such an option at the place where we can clear cache.
@balloni55 it is simply. First photo (without a "Device" icon) is your manually added and the second is from the new tool that display ALL photos in defined time interval. I just have to create some kind of "deduplication". Will look at it ...
Last year I planned two short hikes with Locus "Routenplanner" and usally it looks like pic. 1 (Himmelstädter Runde). But today I saw that route 2 (Retzbach) looks like I already hiked it with times etc. but I did not. Is this a fault or did I something wrong?
4.33.0.2
Android 14
@WildWortWechsel: You're not doing anything wrong. At some point (I can't quite remember when), a feature was introduced to add 'fictitious' timestamps to planned routes.
I'm not particularly happy with it either. It might help to better gauge the stages of the planned tour, but I'm not a big fan of it. Especially as it makes it harder to distinguish between planned and recorded tours afterwards. But I suppose we'll just have to live with it. :)
Quote from: Graf Geo on March 16, 2026, 21:10:30@WildWortWechsel: You're not doing anything wrong. At some point (I can't quite remember when), a feature was introduced to add 'fictitious' timestamps to planned routes.
I'm not particularly happy with it either. It might help to better gauge the stages of the planned tour, but I'm not a big fan of it. Especially as it makes it harder to distinguish between planned and recorded tours afterwards. But I suppose we'll just have to live with it. :)
I think it's good that way. My planned routes always start with an R.
R_Test-2026-03-16
Quote from: Graf Geo on March 16, 2026, 21:10:30@WildWortWechsel: You're not doing anything wrong. At some point (I can't quite remember when), a feature was introduced to add 'fictitious' timestamps to planned routes.
Thank you. A quite unexpected feature ...
Quote from: Morris75 on March 07, 2026, 12:50:57Quote from: Agus on March 07, 2026, 09:23:35Quote from: freischneider on March 07, 2026, 08:32:10The problem has been resolved at Xiaomi.
It has not been resolved on my Xiaomi.
I have the same problem when I click on GPS/compass; the application crashes in Beta 4.33.0.1
I have Samsung S24 Ultra with Android 16
The bug has disappeared with the update to Beta 4.33.0.2. There are no more crashes when using the GPS/compass screen.
Many thanks to the developers!
Google gives me enough time to do some more radical changes ... and they need some weekend testing ;)
Version 4.33.0.3 (13.3.2026)
- chg: new screen with track charts
- chg: track charts visible based on track activity
- chg: updated track chart colors and removed customizable color settings (expert settings)
- add: support for "Pace" in charts
- chg: extend list of supported USB baud rates
- add: notification to Android Auto about missing location permission
- chg: more reliable GPS lifecycle handling (automatic restart, etc)
- chg: highly optimised internal work with world countries (lower memory footprint)
- fix: crash in My Live location
- fix: incorrect opening hours in LoPoints
- fix: prevent unwanted 180° map rotations during Smooth movement
Enjoy the weekend!
Thanks for the update (Beta 4.33.0.3). :)
The new chart overview for the tracks looks nice, but I'm now missing the second elevation chart where the x-axis can be zoomed (screenshot 1). That was very helpful, as the charts in the overview are very compressed for longer routes. Is that actually going to be removed permanently? That would be a real shame.
(The small graphs for speed, pace, etc. show nothing but noise, at least on hikes. These should also be zoomable, screenshot 2).
Quote from: Menion on March 20, 2026, 15:42:39Version 4.33.0.3 (13.3.2026)
- chg: new screen with track charts
oh wow - excellent - far more readable than previous single chart. I hope the next step will be zoom-ability & ability to return to map from tapped point on chart.
The slope chart could do with numbers on the vertical axis. It also needs vertical "expansion" - expand further to top & bottom of chart.
20260321-074639-.jpg
When viewed in the track summary, any slope (green) is vertically compressed so much as to make almost meaningless.
20260321-074934-.jpg
Quote from: Graf Geo on March 20, 2026, 20:11:01Thanks for the update (Beta 4.33.0.3). :)
The new chart overview for the tracks looks nice, but I'm now missing the second elevation chart where the x-axis can be zoomed (screenshot 1). That was very helpful, as the charts in the overview are very compressed for longer routes. Is that actually going to be removed permanently?
I totally agree. The zooming of the elevation chart is one of the major features I use on my long distance hikes ( >1000 kilometers) to plan my daily tours depending on the expected elevation. On the other hand I never used Steigung/Gefälle, Tempo or Pace on a hike. Please bring back the elevation zoom.
more obstacles for beta testing
https://hackaday.com/2026/03/20/google-unveils-new-process-for-installing-unverified-android-apps/
Track chart, no zooming and not being able to center map on the selected track chart position is a big step back.
Speed/pace as separate charts allow to instantly spot pauses, good.
Sliding over speed/pace, line display in the upper charts is inconsistent.
Quote from: Tapio on March 21, 2026, 00:35:11Track chart, no zooming and not being able to center map
am guessing, beta, is only the 1st preview of new charts
Quote from: Andrew Heard on March 20, 2026, 22:38:08more obstacles for beta testing
https://hackaday.com/2026/03/20/google-unveils-new-process-for-installing-unverified-android-apps/
My read is that verified developers (and I bet Menion and company are) do not trigger such barriers. Fingers crossed.
What have you done with the chart values?
The old altitude was much smoother and the new slope chart looks totally different.
Quote from: Gerhard57 on March 21, 2026, 10:21:06What have you done with the chart values?
check other comments since 4.33.0.3 beta release #52 (https://forum.locusmap.eu/index.php?topic=9553.msg80683#msg80683) - I'm guessing/ hoping testing ideas for a new more readable chart; more functionality to come/ be restored
4.33.0.3
Android 14
I guess, the distance markers of the actual hiking route (red) are gone. I'm just on km 1.8 on a trainings hike (violett) and there is no marking. The setting should be fine.
1. Edit: After 3 Kilometers the markers appears.
2. Edit: since Kilometer 4 the markers are gone again.
3. Edit: During the hike I realized that sometimes only the last distance marker was missing. But I did not always checked it. See last picture: red 3 is there, 4 is missing.
Hello Menion,
As there are quite a few requests and minor issues regarding the stylish new charts and other updates, I'd like to summarise them briefly:
- The elevation chart and track should both be visible on the screen. When using the track gallery and/or with multi-line track titles, this isn't currently possible at all. This severely limits the usefulness of the charts. The position marker with the info in the graph obscures parts of the curves and cannot be hidden. See screenshot.
- Furthermore, it is essential that the graphs are zoomable.
- Ideally, the track info panel should be configurable (I know you wrote that this is planned – hopefully soon). ;)
- As has been noted before: the track gallery should be able to be shown or hidden via a toggle. At the moment, you have to go through the hassle of going into the settings first.
- Track gallery: there are many reasons for saving the same photos in different folders. This means they appear multiple times in the track gallery. Therefore, there should either be an option to ignore folders or automatic detection of duplicates, so that no images are displayed multiple times.
Please don't forget:
- When I click on a track point in the track, its date and time should be displayed immediately. At the moment, this is also quite a faff.
- Geotagged photos should be excluded from POI alerts.
Have I forgotten anything else? 8)
BTW: Even though I'm always pointing out issues and making requests, I'd also like to emphasise that the app is developing brilliantly and getting better all the time! :)
I'd actually forgotten something: 8)
On the charts, you can choose between distance or time on the x-axis.
Whilst the distance axis is always logically divided into round kilometre increments (e.g. 5–10–15 km or 50–100 km), the time axis always displays non-round increments (e.g. 1:40 hr, 3:20 hr, 5... hr or 8:20 hr, 16:40 hr, 25.00 hr). Sometimes the last value is also truncated, see screenshot.
I know that, ultimately, a round 100 minutes is shown as the non-round 1:40, but since you usually count in hours on longer trips, I find this unnecessarily inconvenient for a quick estimate. Full hours would be better (2 hr, 4 hr, 6 hr, etc.)
Hi guys,
thanks for the nice feedback!
I've made a bunch of updates over the last few days, and the result is my new attempt to push the version through the Google Play review team. Version 1209 is available in the "Release Google Drive" directory.
Important info: currently, it is not possible to support the zooming or a map+chart layout on the main map screen. I'm with my colleague working on the new system for the track detail, and once it is ready, these changes may also be done. Anyway, the screen with track charts is completely new and ready to do everything we imagine ;). So zoom is there, better scroll as well etc etc.
@Andrew Heard
obstacles for Beta testing > not in our case I believe. We will remain a "verified developer".
@Gerhard57
smoother charts > this is also question to others. Currently, there is no filtration of chart values. Should I invest some time in it and try to apply a little more clever solution that will preserve the shape and cut the biggest peaks? For all chart types? I'm open to discussion ...
@WildWortWechsel
missing markers > interesting. I'm unable to simulate it. Will be watching it ...
@Graf Geo
complex reminder, thanks :)
- chart+map > info above
- zoomable > enabled in "Track charts" screen
- improvements in the gallery + deduplication > also later
Version 1209 (4.33.0):
I can't open any tracks from the library: Locus crashes and restarts.
When I click on a track visible on the map: Locus crashes and restarts.
New routes using the route planner: the app also crashes when you click on the new route.
Unfortunately, the app isn't really usable in its current state.
After every restart, all tracks are hidden...
Hi Menion,
Thanks for the great work - regarding charts: I noticed, that the Dashboard-Charts are now smaller (and the axes are labeled). I'd prefer bigger chats with no labels to fill fully fill the spot in the dashboard.
Would it be possible to make this configurable.
lG Ulrich
Quote from: Graf Geo on March 25, 2026, 15:00:48Version 1209 (4.33.0):
I can't open any tracks from the library: Locus crashes and restarts.
Same. DO NOT UPDATE, GUYS. Log needed?
I think this one is new:
17:46:16.159 E a uncaughtException(Thread[main,5,main])
java.lang.IllegalArgumentException: The x-values are too precise. The maximum precision is four decimal places.
release 4.33-1209 - I tried to crash it with route planner & other reported methods, but all good so far. I find the slope chart nearly useless as not filling vertical space, and any "height glitch" results in +/-200% range, and flat line for example. a vertical zoom will workaround that. The speed chart y axis has unnecessary 1 decimal point, eg 40.0. The pace chart y axis is worse with 2 decimal points, eg 200:00. without a very good eyesight it looks like 20000. I opened the charts with a 1200km recorded track and it was quick to load - very good. Until now I have screen off while cycling/track recording, but last few days with screen on, smooth motion, walking & driving, it's just really silly smoothly bumbling around. Even without the stationary 180 rotate it's not very useful while moving.
Everything is working fine for me with the new version. I'm not experiencing any of the reported crashes.
Hmm, I've now installed version 4.33.0 (1209) on my old SGS10, and it works there.
I then installed it again on my Motorola, and the error is still there. It crashes immediately when I open a track.
So it seems to work on some devices but not on others...
Hi guys,
sorry for the troubles. Please give a try (release) new version 4.33.0 / 1210. Thanks!
Changes compared to 1209
- add: "Map" button in tracks chart to display place on the map
- chg: track chart reacts on clicks on the map
- chg: clock-friendly intervals on "Axis X - time"
- chg: apply light smoothing to charts
- chg: improved track charts text formats
- fix: crash in some cases cased when "Axis X - time" is visible
- fix: improve GPS waiting message when location permission is missing on Android Auto
- fix: not fluent "Show view" and heading line
- fix: correct trackpoint selecting after clicking on the chart
- fix: missing LoRouter custom parameters in "Sharing URL"
Thanks. It seems to be working now, but after all the trouble I've had, I need to test it properly.
In new chat there sometimes is a gap. look at screenshot
In slope chart the colour is expected between zero line and value. Wichtig filter did you use in older version for slope?
Most of the improvements to the charts are a success. Zoomable and "clock-friendly" = very good! 👍
In my opinion, the "smoothing" of the charts isn't quite right yet; on some tracks it looks "jagged" or "stepped". I preferred it better before, when the height chart was smoother/rounder. It's a matter of taste, of course.
The position marker's data field runs directly along the chart's curve (I'd already mentioned this as suboptimal). Suggestion: Perhaps it could be positioned at the top end of the vertical position line; then it would always run above the curve and wouldn't partially obscure it.
Installed latest beta, thanks for the great job.
When one track is selected, it was "yellow" before, and now it is same color but with a white band. Is there a setting for this, please?
Charts are well improved. A bit laggy though.
When we approach the full chart via the track panel, click on the chart, then go for the position on map, via the top map button: it should close the track panel, because in this moment we're interested in the map.
@Gerhard57: The gaps are stops/pauses. I think that's good; you can spot them quickly on the graph. Of course, they only make sense for speed and pace, which is why they're only shown there. Not on the elevation graph. That works.
@Mick FU: I much prefer this now. Previously, selected tracks were highlighted in complementary colours, which (depending on the colour) wasn't always ideal or easy to see.
Although I've just noticed that this might not be ideal for framed lines either, as a light line with a dark border now gets a white border and isn't highlighted as well. So there's still room for improvement here too.
@everyone/Locus Team: another suggestion for improving the new chart overview. When you zoom in on the chart – which apparently can only be done with two fingers – the position marker can no longer be moved. Only the chart moves. The marker can then only be positioned by clicking on the chart, which isn't very precise.
For zooming, additional plus/minus buttons would be useful (as before).
One more thing: The new chart overview does not display elevation profiles for planned routes; it only shows a blank background. See screenshot.
Quote from: Graf Geo on March 26, 2026, 18:54:32@Gerhard57: The gaps are stops/pauses. I think that's good; you can spot them quickly on the graph. Of course, they only make sense for speed and pace, which is why they're only shown there. Not on the elevation graph. That works.
How is the time gap value to be recognized as stop/pause? Can it be set by user? Or marked by a icon?
Quote from: Graf Geo on March 26, 2026, 18:54:32One more thing: The new chart overview does not display elevation profiles for planned routes; it only shows a blank background.
Can not agree. Charts for planned routes are o.k. See screenshot
gap in chart at via point.
@Gerhard57:
You're right. The blank chart is from a track I apparently created using a faulty earlier version, which caused me several problems.
All the other planned routes display the charts correctly.
Although I really don't understand the gaps in the planned routes - yes, they appear where shaping points have been set, but that's pointless, isn't it?
In recorded tracks, the gaps are where we actually took breaks.
Quote from: Graf Geo on March 26, 2026, 18:54:32For zooming, additional plus/minus buttons would be useful (as before).
Hi Menion,
thanks for the great job you have done. The two finger zooming of the chart is great. Nevertheless, "gestures" are a nice weather respectively an indoor feature always causing trouble outdoors: Rain on the display, gloves when its cold etc. makes it very difficult to use gestures. Insofar I support Graf Geos suggestion of additional zooming buttons like before.
I also like the new way of the "framing of a selected track". Is it possible to select the frame color? All my tracks have defined colors. So I could find a "perfect" frame color for them. Would be really helpful.
Quote from: WildWortWechsel on March 26, 2026, 22:23:19thanks for the great job you have done. The two finger zooming of the chart is great. Nevertheless, "gestures" are a nice weather respectively an indoor feature always causing trouble outdoors: Rain on the display, gloves when its cold etc. makes it very difficult to use gestures. Insofar I support Graf Geos suggestion of additional zooming buttons like before.
Since I use Locus as a bike computer/Navi I second this idea to have buttons.
Greetings Ulrich
Just found a strange map glitch.
4.33.0 / 1210
like the improved charts.
track line style:
currently we don't have a line style which marks the track points of a recorded track or? My track is partially precise maybe due to the used profile-settings. I always see the track-line but never its points with markers as line-style-option. Would love to see this improvement, currently it's always a guess to identify the line-vertices and don't want to switch to the trackpoint-panel.
smoother charts:
as you mentioned, smoothing signals is about filtering and a typical topic in signal processing. Often moving average or Savitzky-Golay-filtering is used, eg. https://de.mathworks.com/help/signal/ug/signal-smoothing.html (https://de.mathworks.com/help/signal/ug/signal-smoothing.html). Don't know if it makes sense to use some on-the-fly-processing or to add some simplified representatives.
But maybe you already used this in the past in LM.
Maybe a button or a setting-option is useful to generally switch to smoother charts. I personally prefer smoother charts, "noisy" is always somewhat disgusting.
idea: make the white chart-background transparent to see the map :)
1209 & 1210 APK files have same signature, ending 307FC53. Expected? I can't see any other difference between the 2 files. Solid Explorer doesn't show exact #bytes.
I think the option to choose your own frame color is a bit over the top. Very few people will actually do that.
The zoom buttons aren't really a problem, but in practice, you don't usually look at the chart that closely when you're on the go. The people I know always do that later, on the couch or at a café.
Quote from: freischneider on March 27, 2026, 06:58:20I think the option to choose your own frame color is a bit over the top. Very few people will actually do that.
The zoom buttons aren't really a problem, but in practice, you don't usually look at the chart that closely when you're on the go. The people I know always do that later, on the couch or at a café.
I use the elevation chart on my long trekking tours (up to 2000 kilometers) very often to plan the daily tours and the tent places. Therefore, the buttons are very important for me in case of rain or cold weather or in a harsh terrain/environment using trekking poles. Gestures almost not usable with poles and often don't work on a wet display.
@Gerhard57
gaps in chart > not sure why this happens for now. I'll be watching it, but seems to be a bug, thanks.
@Graf Geo
smoothing > this is on discussion. Maybe some advanced settings later ;)
position marker > thanks, I'll think about it
zoom buttons > hmm, I'll think about it. But even if added, control should still remain as is - after zoom, tap to select location is needed, no swipe
missing elevation > probably selected "Time" for X axis here
@Mick FU
yellow highlight > it was not by default yellow. App took the main color of the track and colored it in inverse color. This caused a lost of coloring and also does not guaranteed, track will be perfectly visible. This solution should solve both problems.
@Tapio
laggy charts > I know, long tracks are laggy when zooming. Complicated and not easily solvable for now, sorry.
@WildWortWechsel
map glitch > uff, interseting. Vector offline LoMap?
@T-mo
trackpoint style > you want to see only a trackpoints dots instead of the full line??
@Andrew Heard
difference between apk > there should be some I believe :)
Have a nice weekend!
Quote from: Menion on March 27, 2026, 15:23:16trackpoint style > you want to see only a trackpoints dots instead of the full line??
- No extra function button.
1px/2px combi or 2px/4px combi.
The minimum trackwidth at the trkpt locations should be 2(4) px.
Set trackwidth 1 px. As a result the trackpoint dots are shown.
A 1 px linewidth is very small, probably better as 2px/4px.
Example image. By Garmin Mapsource.
Black trackline, black trkpt dots. Yellow (highlight) shows the selected (tapped) track.
@WildWortWechsel
map glitch > uff, interseting. Vector offline LoMap?
Standard offline LoMap Germany South.
Have a nice weekend!
Settings- file system - optimise: instead of hiding, can I suggest it be just disabled, or maybe even better, msg box explaining no optimisation is currently required. At present you don't know whether you are in correct group of settings.
New style for track highlighting - I see no change to track style when I tap/ select? Expected?
Some ideas for the chart window:
a) Instead of "Display all charts" (which for me means "Display pace") - A checkbox for every chart type. More clarity.
b) Add (embedded) waypoint to track- on that screen. This would make preparation (also postprocess) of tracks much easier - too exhausting atm. Both types of WP, embedded and non-embedded. But embedded more important as we are in a track context.
As for the track panel, it really needs quickly accessible toggles to select what we want to see there. In a specific situation. For me, often I wamt to see chart+map, but photos make the chart hidden.
Quote from: Tapio on March 28, 2026, 08:39:55Some ideas for the chart window:
a) Instead of "Display all charts" (which for me means "Display pace") - A checkbox for every chart type. More clarity.
b) Add (embedded) waypoint to track- on that screen. This would make preparation (also postprocess) of tracks much easier - too exhausting atm. Both types of WP, embedded and non-embedded. But embedded more important as we are in a track context.
As for the track panel, it really needs quickly accessible toggles to select what we want to see there. In a specific situation. For me, often I wamt to see chart+map, but photos make the chart hidden.
I support these ideas. More clarity especally "on trail" during harsh conditions.
Once again slope chart. Why not use the same algorithm as in web planer? Looks good! See screenshot
Quote from: WildWortWechsel on March 28, 2026, 09:46:51I support these ideas. More clarity especally "on trail" during harsh conditions.
Yes. Pinching in the diagram view is difficult, because it can only be done on the diagrams, not area in between. That's why I also support zoom buttons, which should appear as an overlay.
Hi Menion,
while I was looking for a trail to hike I marked one (screenshot 1). Subsequently, I shiftet the map left and marked another one (screenshot 2). I wanted to see where this trail ended, shiftet the map to the right and both trails were framend/highlighted/marked. Isn't usally only the last one marked (screenshot 4 without shifting the map) or do I missunterstand it?
Edit: It is even possible to mark three and more trails when shifting the marked ones out of view (screenshot 5).
4.33.0 / 26.03.2026
f1b115757
Android 14
In the latest version, 1210, most of my routes cannot be opened in the planner anymore. When I open them in the planner, the planner just shows an empty planner. No waypoints whatsoever.
In the online planner, I can see that the waypoints are still there, so the problem is really in the app, allthough I also have routes that show waypoints in the app, but not in the planner.
Routes are all made on offline lomaps with offline locus planner.
Quote from: Blihi on March 28, 2026, 18:54:29In the latest version, 1210, most of my routes cannot be opened in the planner anymore. When I open them in the planner, the planner just shows an empty planner. No waypoints whatsoever.
In the online planner, I can see that the waypoints are still there, so the problem is really in the app, allthough I also have routes that show waypoints in the app, but not in the planner.
Routes are all made on offline lomaps with offline locus planner.
Tested the route planner with a downloaded track. It crashed with an error message I could not read because it disappeared quickly. The route planner closed, but the track stayed like in the picture.
After a restart of the App nothing changed until I reopend the route planner.
4.33.0
You respond to me, but I'm not talking about downloaded tracks. I'm talking about routes made in the locus planner, which suddenly cannot be opened anymore in the planner in the app.
I do not see any error messages, the planner just shows an empty screen as if you open it the regular way, while it no longer shows the route on the map.
Restarting the app makes no difference and the problem exists on multiple devices and I checked the logs, no exceptions are logged.
The logs are showing a message suggesting that there is a cancellation:
20:40:30.910 E a setToAnimate(MapContent[id: 143188985, textId: MAIN, base: true, maps: Asamm (LoMaps Online), Germany South)
wj0.h1: Job was cancelled; job=v1{Cancelling}@2dc2482
20:40:36.898 E a setToAnimate(MapContent[id: 143188985, textId: MAIN, base: true, maps: Asamm (LoMaps Online), Germany South)
wj0.h1: Job was cancelled; job=v1{Cancelling}@4e95969
20:40:44.398 E a setToAnimate(MapContent[id: 143188985, textId: MAIN, base: true, maps: Asamm (LoMaps Online), Germany South)
wj0.h1: Job was cancelled; job=v1{Cancelling}@5b4f7ab
20:40:49.673 E a setToAnimate(MapContent[id: 143188985, textId: MAIN, base: true, maps: Asamm (LoMaps Online), Germany South)
wj0.h1: Job was cancelled; job=v1{Cancelling}@cccd273
In this example, I tried to open four existing routes in the planner. None of them opened.
I can confirm that this is the exact error message that shows up in the log every time I try to open one of the routes that won't open.
After reading the entire thread, it seems the problem is the same as mentioned here:
Quote from: Graf Geo on March 13, 2026, 12:26:11I think there ist a nasty bug in Beta 4.33.0.1
Routes created using the route planner cannot be edited. Selecting 'Reroute' displays a brief 'Initialising' message, hides the route to be modified, and brings up the screen where I can create a completely new route. It's as if I were starting the route planner from scratch.
Routes created using the web planner can still be edited (once).
See screenshots.
Though, it does not seem to be limited to routes made in a specific small time window. Older routes, i.e. more than a year old, open well, but routes that are from 2026 do not seem to open.
Quote from: Blihi on March 29, 2026, 08:02:51After reading the entire thread, it seems the problem is the same as mentioned here:
Quote from: Graf Geo on March 13, 2026, 12:26:11I think there ist a nasty bug in Beta 4.33.0.1
Routes created using the route planner cannot be edited. Selecting 'Reroute' displays a brief 'Initialising' message, hides the route to be modified, and brings up the screen where I can create a completely new route. It's as if I were starting the route planner from scratch.
Routes created using the web planner can still be edited (once).
See screenshots.
Though, it does not seem to be limited to routes made in a specific small time window. Older routes, i.e. more than a year old, open well, but routes that are from 2026 do not seem to open.
I also found one from February 10, 2026, but it doesn't work either. The route planner is empty when I open it. Luckily, it's just one I forgot to delete.
For me it's the entire holiday planning for this year, unfortunately >:(
Well, I'll just hope it will be fixed soon.
Routes can be restored in the following way: open them in the web planner, recalculate with the correct profile, store as new. Then you can edit them in the app again.
Or, sometimes on a tablet: open the route in the webplanner, select edit, open in planner. Then refresh the page, now the Locusmap app will open with the route in the routeplanner. Here you can save it directly to the app.
@T-mo & @0709
eh, it already exists. Just uncheck all "Line", "Pattern" and "Outline" values in the track style.
@WildWortWechsel
map glitch - ah, I see this. It is an issue in the online backup map. We will probably be changing our base online map during the next few months, so it should be fixed automatically.
two tracks highlighted > yes, this looks like a bug. Thanks, fixed.
@Andrew Heard
hiding of "Optimise" - I made it as you propose at first. But after the discussion, we decided to hide it completely if not needed. All new users will never need it. And this is currently the priority > not to complicate UI to new users.
track highlight - you should see a light or dark border around the selected track
@Tapio
visibility of charts is not based on the track activity. Selecting of every chart separately > maybe later.
waypoints > I'll look at it
@Blihi
share a problematic route with me over "Share by link". Thank you.
Quote from: Menion on March 25, 2026, 13:13:06@Gerhard57
smoother charts > this is also question to others. Currently, there is no filtration of chart values. Should I invest some time in it and try to apply a little more clever solution that will preserve the shape and cut the biggest peaks? For all chart types? I'm open to discussion ...
The way it's done in 1210 looks good to me. But I came across one problem recently: Sometimes, the SRT files contain nonsense, where data obviously oscillates between min and max integer, so -32.767km to +32.768km, which makes all charts display nonsense. Can you filter these out? At least in charts, but perhaps also for the map shading, because those sudden gorges are not natural, I fear...
Question:
Is there a way to jump to the location of the photos shown in the track view? I know, they're selected according to timestamps, but if they also have a location, it would be great to be able to jump there on e.g. long-click.
Or am I overlooking something?
@slarti76
- improved system for interpolation/shading/etc. ... I'm looking forward to it.
During this year hopefully :)
- photos on the map > not yet
Quote from: Tapio on March 28, 2026, 08:39:55b) Add (embedded) waypoint to track- on that screen. This would make preparation (also postprocess) of tracks much easier - too exhausting atm. Both types of WP, embedded and non-embedded. But embedded more important as we are in a track context.
I've been hoping for an "Add waypoint" option in the track editor for ages - not sure if we want the same thing, but perhaps both go together. I know, it's possible to add waypoints to a track, but they're not timestamped, they're more POIs. For example, "Hut" is a feature of the landscape and not really related to the track, but "Put on snowhoes here" is related to the specific track and thus the timestamps is relevant.
Quote from: Menion on March 30, 2026, 09:33:09@T-mo & @0709
eh, it already exists. Just uncheck all "Line", "Pattern" and "Outline" values in the track style.
Seems to work, but then it says "Style not defined", which is at least midleading...
Little update if you're also having problems with GPS reliability on Samsung S24 (or perhaps others), see https://forum.locusmap.eu/index.php?topic=9488.msg80515#msg80515 for my initial post:
I didn't find any setting in Locus to prevent this, so I solved it with a Tasker profile that turns GPS in Locus off and on again every min (configurable, of course). Works well. If you're interested, import attached file. Needs Locus Tasker plugin, of course.
Quote from: slarti76 on March 30, 2026, 13:10:30Quote from: Tapio on March 28, 2026, 08:39:55b) Add (embedded) waypoint to track- on that screen. This would make preparation (also postprocess) of tracks much easier - too exhausting atm. Both types of WP, embedded and non-embedded. But embedded more important as we are in a track context.
I've been hoping for an "Add waypoint" option in the track editor for ages - not sure if we want the same thing, but perhaps both go together. I know, it's possible to add waypoints to a track, but they're not timestamped, they're more POIs. For example, "Hut" is a feature of the landscape and not really related to the track, but "Put on snowhoes here" is related to the specific track and thus the timestamps is relevant.
@slarti76
What about opening your track in the Route Planner (not in Track Editor).
Then you can click on any point,
Screenshot_20260331_064737_Locus Map.jpg
change it into a Via Point,
Screenshot_20260331_064803_Locus Map.jpg
Screenshot_20260331_064833_Locus Map.jpg
do not recalculate, save as new track, and you have a time stamped WP embedded in your track.
Screenshot_20260331_065202_MiXplorer.jpg
Quote from: Mick FU on March 31, 2026, 06:59:40Quote from: slarti76 on March 30, 2026, 13:10:30Quote from: Tapio on March 28, 2026, 08:39:55b) Add (embedded) waypoint to track- on that screen. This would make preparation (also postprocess) of tracks much easier - too exhausting atm. Both types of WP, embedded and non-embedded. But embedded more important as we are in a track context.
I've been hoping for an "Add waypoint" option in the track editor for ages - not sure if we want the same thing, but perhaps both go together. I know, it's possible to add waypoints to a track, but they're not timestamped, they're more POIs. For example, "Hut" is a feature of the landscape and not really related to the track, but "Put on snowhoes here" is related to the specific track and thus the timestamps is relevant.
@slarti76
What about opening your track in the Route Planner (not in Track Editor).
Then you can click on any point,
<snip>
Interesting, never thought of that, will try. Actually sounds weird that this way, the WP gets a timestamp, but I'll take it. Still, the workflow would be much better if everything is available in track editor...
But thx!
Embedded ?
The gpx navigation track mode with instructions in trackpoints offers this "by default."
No more hassle with the "fragile" easily broken gpx waypoint associations based on timestamps.
Imo, the association method is hopelessly outdated given this very simple robuust alternative.
It uses only the track points. This works flawlessly every single time, without fail.
A super-simple, robust proposal was submitted to Locus but not implemented.
https://forum.locusmap.eu/index.php?topic=5953.msg49519#msg49519
Locus Map could have been the first to offer this but gave up before the finish line was reached.
The alternative is therefore a successful implementation realised into another excellent navigation app.
Trackpoints with or without timestamps, in a calculated or a recorded track — it doesn't matter.
Easily promote any trackpoint into an announced via trkpt, silent shaping trkpt, or turn trkpt.
The trackpoint element sym handles the turn instruction.
The track point element type via or type shaping (=muted via) determines whether is announced or not.
(Locus map only supports an promotes the trkpt sym pass_place to be a via point).
The trkpt name than provides the (TTS) via point name announcement.
A combination of a via trkpt with turn trkpt is possible. See a trackpoint example.
<trkpt lat="51.04955" lon="3.9908283">
<ele>3.7</ele>
<name>Just for fun</name>
<cmt>Willebochtenlaan</cmt>
<sym>u-turn</sym>
<type>via</type>
</trkpt>
The "via" point by the trkpt type element is announced by the trkpt name element: "Just for fun".
The turn is announced by the trkpt element sym: "u-turn".
The TTS announcement in the navigation: "Just for fun, make a U-turn"
By the way. Locus does succesfully read an imported gpx navigation track.
(Only the combination by the type via together with a turn sym is not supported)
Locus map navigation announcement: Make a u-turn. (Locus does not offer the via announcement)
For those willing to do a little test. (Using basic notepad++ edits)
Source is a Locus navigation track or a Plotaroute web gpx exported navigation track.
The Locus default navigation track = a gpx track with associated navigation gpx waypoints.
- Add extra into a single selected trackpoint. (INTO THE trackpoint!)
- Add a trkpt sym turn (for example a left or right or straight).
Or better add a tkrpt sym pass_place plus tkrpt name (local language text expression).
Than test the Locus navigation announcement result.
Quote from: 0709 on March 31, 2026, 10:02:16Embedded ?
The gpx navigation track mode with instructions in trackpoints offers this "by default."
No more hassle with the "fragile" easily broken gpx waypoint associations based on timestamps.
It's not about
associating waypoint with trackpoints. The timestamp is an information in itself: During a recording, I can add a waypoint, which marks
that point in time as some kind of event. There don't need to be a trackpoint recorded at the same time.
Obviously, during track edit, that would be a major extra dialog to add a timestamp to a trackpoint (or waypoint, for that matter), so as an approximation, when selecting a trackpoint, it should be possible to set a waypoint at the same location and with the same timestamp. Which should also be kept if the trackpoint were to be removed. Totally independent.
I'm not saying your idea is bad or useless, but I can see how this would be a bigger change for Locus. Waypoints otoh already exist and can be created during recording with timestamp. I'd just like a way to create those I forgot during recording, but still with timestamp.
No problem. Stand alone gpx wpt or embedded trkpt in a trackrecord. No problem. See txt attachment.
Coooool 8) 8) 8)
New version with Android Auto is published and works great. ;D
I don't want to leave my car. 😁
I think Locus Map is one of the rare apps which are allowed to use Android Auto.👍
Quote from: Menion on March 30, 2026, 09:33:09@T-mo & @0709
eh, it already exists. Just uncheck all "Line", "Pattern" and "Outline" values in the track style.
Indeed, this hack works. See pic.
By the way, the trackpoints inherit color and size from the Line, so to change those enable Line again, change color and width, then save and save and edit and disable Line.
After change the track is still highlighted and you might not immediately see the change. Deselect your track.
If you restart LM, the trackpoints (of your track with disabled Line) change to black, small size and outline style, which is surprising and inconsistent. Edit and save brings the old state back (color of track and filled dot of size px-width)
@Menion.
This presentation offers Garmin Mapsource_Basecamp out of the box, without any extra hassle.
A very useful display for tracks calculated by routers and so a relatively low trkpt density.
Insert an extra trkpt (without recalculating) and visually confirm the exact location on the map.
Announce this trkpt at the exact desired location by promoting it than into a via_trktp.
Add trkpt type "via", plus (for Locus) sym "pass_place". Add a trkpt name is optional.
- A nice simple and usefull feature to show and offer in the web planner ?
Quote from: Menion on March 30, 2026, 09:33:09@Blihi
share a problematic route with me over "Share by link". Thank you.
Sure. Here's one that cannot be opened in the app: https://link.locusmap.app/t/1s9v2t
This one does not open in the online planner either.
I can't find my original help (suggestion) topic, so I'll say thanks to the WebPlanner developer(s) here - I note with pleasure after displaying a track from MyLibrary and then clicking the Back <- button, the scroll position in the list is now correctly restored rather than scrolling back to top of the list - a big time saving when the list is long, Thanks so much!
Quote from: Blihi on April 01, 2026, 19:58:23Quote from: Menion on March 30, 2026, 09:33:09@Blihi
share a problematic route with me over "Share by link". Thank you.
Sure. Here's one that cannot be opened in the app: https://link.locusmap.app/t/1s9v2t
This one does not open in the online planner either.
This link is working for me, both in app (latest beta) and in Web planner.
Quote from: Mick FU on April 02, 2026, 07:56:59Quote from: Blihi on April 01, 2026, 19:58:23Quote from: Menion on March 30, 2026, 09:33:09@Blihi
share a problematic route with me over "Share by link". Thank you.
Sure. Here's one that cannot be opened in the app: https://link.locusmap.app/t/1s9v2t
This one does not open in the online planner either.
This link is working for me, both in app (latest beta) and in Web planner.
Interesting. I can open it now in the Web planner on my Windows computer. It did not want to open in the Android version of Firefox on my tablet yesterday.
In the app (latest release 4.33) it does not open, but when I choose "edit route" the app opens the empty planner.
The latest beta is 1207, while the release is 1210. I cannot downgrade to 1207 to test, unfortunately. But it seems to be related to this, i.e. any route made after January 2026 has this problem for me.
Locus Map 4.33.0.6 (1211)
Some nice additional and risky versions before the holidays.
- add: integrated Augmented Reality solution (similar to old malfunction add-on)
- chg: all "config.cfg" settings moved to the Expert settings (and config.cfg support removed)
- chg: track recording widget rework (10+ year old solution rewrote to modern coat)
- chg: major (really MAJOR) update of various internal libraries (unexpected behaviours may happen)
- chg: another iteration in the "Smooth movement" algorithm
- fix: multiple tracks selected at once
- add: option to display waypoints (not the navigation orders) on the charts
- add: support for tap on waypoints on the chart + highlight
- add: zoom buttons in screen with track charts
- fix: crash on Android 16 when setting the language
- fix: rare crash in long click on the main map screen
- fix: prevent crash when Sync screen resumes before sync is initialized
- chg: improved line style to support "dotted style" (just dots on trackpoints)
- chg: "Choose guidance dialog" rework
- fix: geocache wpt list strips '*' due to Markdown italic conversion
- chg: improved reliability of downloading maps from Locus Store
- fix: improved handling of "Route URL" and better match to web planner version
I made a s reen capture of the problem with certain routes: https://drive.google.com/file/d/1hBbUPK2HMt9LgnBQUrV8TfbWYN_fRXpB/view?usp=drivesdk
I also noted the problem is reported as a bug in the helpdesk twice (not by me)
Have you tried the latest version I've just published?
Quote from: Menion on April 02, 2026, 17:58:59Locus Map 4.33.0.6 (1211)
Some nice additional and risky versions before the holidays.
Locus store is broken for me. It is stuck in the loading screen. And when I click on the profile button top right, locus crashes.
Screenshot_20260402_214004_Locus Map.jpg
Greetings, Ulrich
Regarding 4.33.0.6 (1211)
I've only installed it on my secondary device (S10) for now. First impressions:
Integrated Augmented Reality solution: Where can I find it, or how can I view it?
All "config.cfg" settings have been moved to the Expert settings:
Good, this makes it more consistent and clearer.
Fix: multiple tracks selected at once:
Confirmed.
- Add: option to display waypoints (not the navigation orders) on the charts
- Add: support for tapping on waypoints on the chart + highlight:
I've never used waypoints before. Now I've added some to a track as a test. When I highlight them, they appear very large on the map. How do I make them small again? I have to hide the track and show it again; then the icons become small again, but that can't be the solution, can it?
The waypoints don't appear on the charts, even though I've enabled the option.
add: zoom buttons on the screen with track charts:
Good!
Chg: improved line style to support "dotted style" (just dots on track points):
OK, that makes it clearer. Even if you don't immediately realise they're track points and not a normal dot pattern. Maybe "Trackpoints only" instead of "Dotted style only"?
I can't comment on the other changes (yet).
Quote from: Ulrich Kiermayr on April 02, 2026, 21:42:31Locus store is broken for me. It is stuck in the loading screen. And when I click on the profile button top right, locus crashes.
Same here.
Another serious bug:
The track editor causes Locus to crash.
Quote from: Graf Geo on April 02, 2026, 22:19:39Another serious bug:
The track editor causes Locus to crash.
Same here ;)
LG uk
4.33.0.5 maps button on tracks chart: the map is not correctly positioned if the chart is zoomed in: track list > track > chart > zoom+ > tap Map button (new) > tap + icon > observe map cursor is not in correct position.
Chart zooming suggestion: if the chart has been tapped (vertical line displayed) then maintain that position when zoom+ or zoom- is tapped. At present the position is often lost after the zoom.
Chart panning: seems a little unresponsive - swipe to side multiple times but often the chart does not move.
Chart panning: with zoom+ then pan too far to right (swipe left) and the screen (sometimes) becomes blank! Not sure 100% how to reproduce yet.
4.33.0.6 Locus Store > loading... forever and/or crash confirmed.
Smooth movement: detection of "stopped" is not perfect so still some unwanted rotation, but big improvement. If settings > GPS > Map rotation mode = GPS orientation only, then with only small or no movement, can all rotation be stopped? i.e. ignore GPS jitter of +/-5m?
The slopes in the new charts have always looked larger than the old chart. I checked one @ https://link.locusmap.app/t/wtkubf which is quite flat.
WebPlanner 2.5%:
20260403-091927-.jpg
same place on LM chart 8%:
20260403-092307-.jpg
Thanks guys, nasty bug ... fixed in 4.33.0.7 (1211)!
@Andrew Heard
thanks for the feedback. I'll look at it during the next week.
4.33.0.7 - crashes on start (after clean install too). Samsung Note 9, Android 10.
Quote from: Erelen on April 03, 2026, 03:31:294.33.0.7 - crashes on start (after clean install too).
Locus Store working for me now
After further analysis of the thorny issue of the difference between WebPlanner & LM for display of slope - at a basic level LM is correct
lat lon alt (m) dist (km) slope (%)
-42.858939 147.326095 11.2 1.422
-42.859009 147.326213 12.3 1.434 9.0
I guess LM is calculating slope (9%) point-by-point without filtering or averaging, whereas the WebPlanner must be doing some filtering and/or averaging to calculate 2.5%. I believe 2.5% is more realistic but there will, as in past? be endless debate for how it is done. I'd suggest at least the two platforms should use the same method & display similar charts though?
In my settings, for interest > GPS > Altitude manager > Replace GPS values + heavy filter, pressure sensor = off
In beta version 4.33.07, Lopoints photos are not visible
4.33.0.7 (1211) crashes on start
Damn, another complication! All these bugs are caused by the update of the external libraries. In this case, it is the internal so-called "EventBus" that misses updates for 3+ years. It no longer works correctly with the most recent Android tools > another big modification is ahead because of this. For now, patched with a small hack ...
New version 4.33.0.8 (1211). Sorry, and thanks for the help!
In beta version 4.33.0.8, Lopoints photos are still not visible.
Good changes. I still hope for easier ppssibilities to add embedded waypoints. I noticed this: in the attached screenshot we are in a track (trackpoint) context. I'd expect the "Add waypoint" button to add an embedded waypoint. But well, it adds a normal unlinked waypoint.
My wish is that we can add an embedded WP at this place. Maybe a small context menu, which allows to choose which type. Or, IMO better, a submenu checkbox option to "permanently" choose which type.
Fast check 4.33.0.8:
LoPoint photos are visible on my device.
The waypoint icons remain (very) large once you open them.
The Track Editor is working again.
Quote from: Graf Geo on April 03, 2026, 10:59:57Fast check 4.33.0.8:
LoPoint photos are visible on my device.
When I tap a LoPoint, the photos don't appear. On a Xiaomi 15T Pro
I've forced the app to close, and now when I tap a LoPoint, the photos appear.
Quote from: Menion on April 02, 2026, 20:42:47Have you tried the latest version I've just published?
Given the number of problems reported here with the latest beta, I'll hold off for now.
However, there are now multiple reports in the helpdesk about the inability to edit routes. I answer them with a video of the workaround via the web planner.
4.33.0.8 is working great.
4.33.0.8_1211_beta: startup & Store OK for me; no other testing done.
4.33.0.8 - startup is ok.
Two devices with latest beta working so far. Well done!
@Menion: the weird thing is: on the tablet there are only 2 graphs, while the mobile shows all 4.
Still missing: timestamp of the point selected on the track and nicely. With the pace as separate graph there is no need for the weird fixed interval. Well, if you find a way to introduce flexible segments on the graphs - with averages, of course ;-)
Have a nice weekend!
Cheers
Michael
Quote from: Menion on April 02, 2026, 20:42:47Have you tried the latest version I've just published?
I checked with version 4.33.0.8 build 1211. The problem appears to be fixed, i.e. I can edit the route I linked earlier again.
Hi,
I found a dashboard issue: the dashboard draws over the guidance/navigation icons in the top left corner. In guidance this is especially problematic, since the icon is not clickable (covered by the dashboard). Biggest problem with that: I can't stop guidance mode.
I think, this started when the new graphs layout started in the dashboard. In older versions, this was not an issue.
Screenshot_20260404_200158_Locus Map.jpg
Geotagged Media - displayed after a long delay, then when I move map, after again waiting like 20 seconds they suddenly appear, then I move map back and none are displayed again... again waiting...
I observed when I zoom out and LM refreshes map tiles, the the poi all disappear.
It's really rather bad. Now for 2 minutes none of those poi visible, then a few appeared, after some zooming all are gone again...
Anyone? Has Geotagged Media display degraded? 4.33.0.8 build 1211
Here's an example video. Additionally, an embedded WP icon turns to monster size and won't disappear. It's also displayed in the charts, but the other WPs aren't.
https://youtube.com/shorts/vUxR9CcLex4?is=yA6AdHXGSOCwSuYX
LoPoi opened, photo added, camera, Locus crashes. All this during recording.
Another way works. Open POI, add photo, select photo (not camera), then it works.
I have observed similar behavior overall when using a dashboard; all elements below the dashboard, except for the center button, are unusable, pinch-zoom does not work, and switching between north orientation and motion orientation also does not work.
Hi Menion,
because I was on a hike I did not install the latest beta but used version 4.33.0.
The App "stalled" several times with a blank screen after setting "Bildschirm entsperren" active. I had to kill the App and restarted it. After five, six stalls I deactivated this setting and the App did work fine.
Additionally, a small UI bug: during a hike the Stop button is always visible indepentend of the setting.
Android 16/grapheneOS (all rights granted)
Pixel 10 pro XL
Quote from: WildWortWechsel on March 22, 2026, 11:25:40I guess, the distance markers of the actual hiking route (red) are gone. I'm just on km 1.8 on a trainings hike (violett) and there is no marking. The setting should be fine.
It seems the missing distance markers during a hike (red track) are related to the zoom level.
Another bug that appears to be back is that, when editing a route, the time is not updated correctly. If you want a new estimate of the time, you have to recalculate the entire route.
Hi Menion,
with the latest beta 4.33.0.8 the "Wandern&Radfahren" theme language switched to english. Was german before (system language).
Just figured out the search for LoMaps update does not work. The search says all maps are uptodate, but in the shop it says "update".
Beta 4.33.0.8
Edit: Most of my maps can be updated, not only Danmark.
Hmm, I've just checked for updates and got a list of four maps to update. So it seems to be working fine for me.
Beta 4.33.0.8
Maybe it is related to my new phone although all maps are visible in the map manager.
Pixel 10 pro XL / Android 16 (GrapheneOS)
Since a couple of versions we have a mess of nav wpts on the screen difficult to hide again. Same behaviour in the track details preview.
@menion - can we please avoid this?!?
The way Locus mananges the nav wpts in general has a lot of potential.
Nav wpts are generated silently in the background and used silently in guidance / navigation. No reason to display them all the time.
So I would suggest to hide them by default and have a switch to display them - if needed.
Good morning Menion,
since I test the beta version 4.33.0.8 the App sometimes does not fully start. I press the App-button, it seems to start but the App "disapears" from the screen. Pressing the Android "last use" button shows the App in Startup-Mode (Screenshot 1). Selecting the App shows it again on screen, but the App did crash shortly after(Screenshot 2).
Pixel 10 pro XL / Android 16 (GrapheneOS)
Hi guys,
I wasn't reading your responses (just really quickly), so sorry. Will look at it next week.
Instead, on the Google Drive is another version 4.33.0.9 ... more of an "alpha". So, do not update if you are ok with 4.33.0.8 and need a stable weekend version.
Otherwise, short list ;) of changes for the brave :D
- chg: completely new picker for locations integrated into main search view
- add: support for custom user-defined locations in Android Auto
- fix: AR view, incorrect points movement
- fix: Android Auto - centering on the found point
- fix: Android Auto - crash when starting navigation in some cases
- add: Android Auto - "Route overview" mode during active navigation
- fix: clear highlight of selected (track) waypoint
- fix: crash when taking a photo to LoPoints
- fix: minor problems in chart system
- fix: new chart consuming tap events if not needed
- add: support for In-app updates system (app will inform about the new version if not updated for 1+ month)
- fix: crash when 2+ track recording widgets were used
- fix: memory leak in scanner for BT4 devices
- fix: memory leak in main screen panels
- fix: crash when cache directory is temporarily unavailable on external storage
- chg: Dashboard charts now do not display value bubbles
- fix: wrong colors and checkbox ignoring in track overview generator
- fix: Dashboard charts correctly use defined text color
- chg: improved prevention of navigation on overlapping segments
- fix: too early "End of navigation" on circular routes
- fix: photo description/caption missing from KMZ export
- fix: internal server error when downloading multiple Pocket Queries
- fix: severe performance regression with large point folders (1 000+ points)
- chg: ensure visible directional arrows when highlighting a track
Quote from: Joska on April 05, 2026, 18:05:47I have observed similar behavior overall when using a dashboard; all elements below the dashboard, except for the center button, are unusable, pinch-zoom does not work, and switching between north orientation and motion orientation also does not work.
After backup, deleting LM and erasing the hole folder of LM, restarting my phone and reinstalling LM4, the above described issues are gone :-)
Alpha 4.33.0.9 :)
Three UI issues:
a) searching a city --> a shelter icon is shown where no shelter is. I guess its the default icon I've chosen in the expert settings.
b) after changing a button in the right panel everything beside the panels is gone.
c) the new elevation chart: I really appriciate the buttons there. Thank you. Unfortunately, they are not able to zoom a long track as wide as the gesture zooms it. And, as soon as I press the + button, the zoom level jumps back to a lower zoom level.
Additionally, the GUI is slowlier as before.
Quote from: WildWortWechsel on April 10, 2026, 23:08:46Three UI issues:
a) searching a city
@menion - I hadn't tried Search for a while - Search > Online > Place & addresses > "glen lusk" - nearby place > only result is in Ireland half way around the world > LM super slow then crash. Screen cap below:
20260411-075824-.jpg
I should have typed (all 1 word) "glenlusk" then my online search would have worked. But that is irrelevant to the crash about bogus message "too many points and tracks".
Just playing around with the UI to test it and found the beta map manager again.
Changing the main menu shows it to add. See pictures.
After tipping on the "Files in Folders" in the Library the numbers disappeared. They were shown at the red marker.
Klick on the X just below your marker on the right and they are back.
small bug:
I've downloaded the geocaching icon pack and selected it in the expert settings (writing the name)
It's not possible to get the standard icons back without getting n error, that the field for the icon pack name can't be empty.
I tried to write a problem with the route time on the Help Desk, but Michal refused, saying that it was not a problem. But it seems to me that this is a problem. So I'll try again here. Locus on the website and in the application does not show the entire time of the route from the start of the recording to its end, but only the time when the recording is running. It just completely ignores the time the recording is in Autopause. So it is impossible to find out anywhere how long I was on the route in total even with breaks. Details are here: https://help.locusmap.eu/topic/40053-cz-%C5%A1patn%C4%9B-vyhodnocen%C3%BD-%C4%8Das-na-trati
Here are samples on the difference between Locus and exporting to Strava.
Snímek obrazovky 2026-04-13 112839.jpgSnímek obrazovky 2026-04-13 112717.jpg
@Andrew Heard slope chart > I've increased the strength of the filter, so it should better match what you see on the web.
zoom with respect of the current selection > done
Smooth movement > yeah, I know. It still needs more time and testing on my side.
Online search problem > it was completely rewrote in last few days so give a try to the next app version, thanks.
@michaelbechtold 2 vs 4 charts > check please menu in the "Charts screen" > Settings > Display all charts
@Tapio slow loading when a huge number of photos is on the device > same experience on own device. Will look at it
@WildWortWechsel rec STOP button > it is always visible as an indicator that recording is running. Settings ignored by intent
missing translations in theme > ah, nice. Fixed
update of maps > there is something not working correctly when dealing with maps manually (or restoring some backups etc). I know, but it needs a lot bigger update under the hood. Check for updates should work correctly for maps updated directly on the device over the app.
Crashes at start > hmm, hard to say what may be the problem. Anyway, please wait for the next 4.33.0.10 version at the end of this week. I'll do a lot of fine-tuning this week. Thanks!
searching a city > not sure about the icon. There should be a better general search icon. Steps to reproduce?
change of the button in the right panel > it looks, based on the distance to your location, that you are somewhere really far away from your home. Center ;)
elevation chart zooming > I'll look at it. And performance - yes I know, not ideal mainly for longer tracks. It will improve itself over time I believe (as the Vico "chart library" (https://github.com/patrykandpatrick/vico) will be improved)
Beta map manager > yes, I know. Forget on it for now :D. I have to hide it correctly.
@Blihi problem with times > steps I can follow to simulate this problem? Thanks
@Christian visible nav points > please check app settings > Points & Tracks > "Show navigation commands on map". Any chance you enabled by yourself accident?
@Diddi gc icon pack > hmm, good point, improved. Thanks.
@TrulloF nice try!! I've never used this API in production so we will have to fine-tune this a little.
I've moved your post here: https://forum.locusmap.eu/index.php?topic=9593.0 and will look at it during the week.
@Žajdlík JosefThis is more complicated and on discussion with everyone.
Currently, app compute times as:
- track time - all times between trackpoints. Breaks are skipped and not computed
- track time (movement) - same as track time, but only when speed is above the threshold (around 2km/h)
What you want is to change this behaviour to
- track time - simply difference in time between the first and last point
- track time (movement) - all times between trackpoints. Breaks are skipped and not computed
Any opinions? Maybe introduce a third time? :)
Quote from: Menion on April 14, 2026, 15:26:17Currently, app compute times as:
- track time - all times between trackpoints. Breaks are skipped and not computed
- track time (movement) - same as track time, but only when speed is above the threshold (around 2km/h)
What you want is to change this behaviour to
- track time - simply difference in time between the first and last point
- track time (movement) - all times between trackpoints. Breaks are skipped and not computed
Any opinions? Maybe introduce a third time? :)
I would expect (and am used to) the current behaviour.
If a third time is introduced, then add a "wallclock time" which is the delta between first and last point of track.
@MenionIs it possible to do something about https://forum.locusmap.eu/index.php?msg=80839 (https://forum.locusmap.eu/index.php?msg=80839)? If not, I'd have to redesign the Dashboard somehow.
Greetings, Ulrich
Quote from: Menion on April 14, 2026, 15:26:17@WildWortWechsel
rec STOP button > it is always visible as an indicator that recording is running. Settings ignored by intent.
...
searching a city > not sure about the icon. There should be a better general search icon. Steps to reproduce?
...
change of the button in the right panel > it looks, based on the distance to your location, that you are somewhere really far away from your home. Center ;)
Hi Menion,
thank you for your answer!
In the earlier Versions the stop button did "vanish" from the screen. That's why I mentioned it.
About the icon: see the screenshot with the expert setting of the "default point icon." Isn't it the default POI Icon?
And because the side panel etc. The center button disappeared 😉
Greetings, Dieter
Quote from: Menion on April 14, 2026, 15:26:17@Christian
visible nav points > please check app settings > Points & Tracks > "Show navigation commands on map". Any chance you enabled by yourself accident?
Thanx. that solved the problem.
Quote from: Menion on April 14, 2026, 15:26:17Any opinions? Maybe introduce a third time?
@Menion I'm happy with current method, but with any change I think there will be opinions for/ against
The complete time from start to stop should not be ignored, but maybe, I'd misunderstood that issue.
Total time on the track is important for all types of endurance sports such as trail running, long marches, cycling, triathlon, biathlon, etc. For all of them, the ranking is calculated according to the time spent on the track, including breaks. That is why applications such as Garmin, Strava or Samsung Health also show this time. But it is also important for amateurs. For example, when I want to look back at how long I walked the "Vandrácká 50" five years ago, I'm interested in the total time in order to estimate when I'll probably return home.
Therefore, I propose to unify the indicators with all sports applications:
track time - simply difference in time between the first and last point
track time (movement) - same as track time, but only when speed is above the threshold (around 2km/h)
Quote from: Menion on April 14, 2026, 15:26:17Currently, app compute times as:
- track time - all times between trackpoints. Breaks are skipped and not computed
- track time (movement) - same as track time, but only when speed is above the threshold (around 2km/h)
What you want is to change this behaviour to
- track time - simply difference in time between the first and last point
- track time (movement) - all times between trackpoints. Breaks are skipped and not computed
Any opinions? Maybe introduce a third time? :)
I'd wouldn't mind a third time or ability to change the threshold. For hiking and snowshoeing, the "movement" times are frequently too low, as in ascent, you easily get below 2km/h.
@Ulrich Kiermayr
Isn't the problem with the dashboard already solved in the latest Beta version?
@WildWortWechsel
track rec button > if you have set the "Auto-hide" option for this button, it should be visible during recording, always. Otherwise, it should be visible or hidden, based on settings.
incorrect search result icon > I understand you have your own icon set in the settings. You wrote about some problems with the search system and I ask to provide some easy-to-follow steps, so I can simulate it. Thanks
Times, thanks for the feedback. I'll have to discuss with the team next week more deeply (also because we have to changes adapt on iOS and web as well).
Quote from: Menion on April 15, 2026, 09:09:31@Ulrich Kiermayr
Isn't the problem with the dashboard already solved in the latest Beta version?
Unfortunately no. The bubbles are gone, but the dashboard still draws over the guidance/navigation panel, intercepting clicks.
Screenshot_20260415_093048_Locus Map.jpg
LG Ulrich
Quote from: Menion on April 15, 2026, 09:09:31incorrect search result icon > I understand you have your own icon set in the settings. You wrote about some problems with the search system and I ask to provide some easy-to-follow steps, so I can simulate it. Thanks.
Hi Menion,
from my side it was only the icon. I removed it --> Problem solved.
About times, can't find again the post, but total_elapsed_time (from start to end including pauses) is at least computed during fit file export.
@Menion
Screenshot_20260415_073226_Chrome.jpg
Locus Map 4.33.0.10A maintenance release that rounds out the 4.33 line with a brand-new local map server, a fresh online address provider, smarter sensor handling, and a long list of crash and stability fixes.
What's new- Local HTTP map server — serve your offline maps over HTTP to another device or viewer (Expert settings). web.locusmap.app support in preparation. Online maps should work, offline only partially.
- Here online address search — a new provider replacing the no-longer-working Bing backend, with a reworked search screen.
- Per-sensor disconnect alert — optional audio / vibration warning when a connected sensor drops out. (topic) (https://help.locusmap.eu/topic/35897-varia-disconnect-alarm)
- Sensor stability — more reliable handling across ANT+, BT, USB and network sensors.
- Custom geocaching icon packs — pick your pack directly from the UI.
- Gear watch add-on removed — Samsung no longer supports the platform.
Bug fixes- Fixed the malfunctioning Stop button in the Live-tracking and Parking notifications.
- Several crashes resolved: the navigation menu with an external routing service, "Get location" with an unavailable source, track charts with no drawable data, and an early-startup URI error.
- Transparent state (https://help.locusmap.eu/topic/39910-wms-layer-content-is-rendered-with-a-white-backdrop) correctly restored for WMS maps.
- Correct altitude units in My Library (https://forum.locusmap.eu/index.php?topic=9591.0).
- Track chart no longer swallows tap events (https://forum.locusmap.eu/index.php?msg=80839), and chart zoom respects the selected location (https://forum.locusmap.eu/index.php?msg=80809).
- Chart slope data gets stronger optimisation; weather day detail scrolls again when a chart is tapped.
- Smaller fixes: missing translations in vector theme categories, stray "Folder" label in the track-waypoint editor, pre-selected areas in online map download.
Under the hood- Heap snapshots are now captured on OutOfMemory crashes and attached to bug reports sent within 24 h.
- Major internal migration of the Store, offline search, track editor, online map downloading, and Asamm live-tracking systems — 10+ year old code modernised. You shouldn't notice anything.
400 Points shown, I turn AR on, rotate the camera a bit fore and back, along the points... LM crashes reliably.
A thought: When approaching a track from inside the library. IF chart has been clicked and then the button top right is used, map view should center on that selection, not the tracks center. Would make life easier.
Hi Menion,
great job!
Rotating the phone "eats" away buttons. This happens in both directions.
Edit: the phone itself "eats" the Start/Stop button partial.
Pixel 10 pro XL
4.33.0.10
Quote from: WildWortWechsel on April 17, 2026, 15:44:19...
Rotating the phone "eats" away buttons. This happens in both directions.
...
On my device, all the buttons are displayed in landscape mode. It seems to depend on the device.
Quote from: Tapio on April 17, 2026, 15:35:01400 Points shown, I turn AR on, rotate the camera a bit fore and back, along the points... LM crashes reliably.
...
Quick test with over 1200 points displayed and then AR – no crash for me.
Quote from: Menion on April 17, 2026, 15:07:54Locus Map 4.33.0.10
Per-sensor disconnect alert — optional audio / vibration warning when a connected sensor drops out. (topic) (https://help.locusmap.eu/topic/35897-varia-disconnect-alarm)
That's great, but...
... For the sensor, that gave me the idea, I don't see it: The bike radar (I lost that day). Could you add the alarm for radars (RTL515) as well.
Screenshot_20260417_192838_Locus Map.jpg
Greetings, Ulrich
Quote from: Graf Geo on April 17, 2026, 20:14:19Quote from: WildWortWechsel on April 17, 2026, 15:44:19...
Rotating the phone "eats" away buttons. This happens in both directions.
...
On my device, all the buttons are displayed in landscape mode. It seems to depend on the device.
Thank you for testing!
I have Fullscreen mode in the expert settings active. Maybe it is related to this mode?
Even with full-screen mode enabled, all the buttons are still displayed on my screen.
Quote from: Graf Geo on April 17, 2026, 21:17:39Even with full-screen mode enabled, all the buttons are still displayed on my screen.
Maybe the settings?
Quote from: Menion on April 17, 2026, 15:07:54- Track chart no longer swallows tap events (https://forum.locusmap.eu/index.php?msg=80839), and chart zoom respects the selected location (https://forum.locusmap.eu/index.php?msg=80809).
- Chart slope data gets stronger optimisation
@menion 4.33.0.10 - confirmed improvement of chart slope - below is comparison of Web Planner (top chart) & LM (bottom chart) with my previous example - now LM shows 5% instead of 8% slope - far more realistic; zoom respects the selected location - great, thanks.
Untitled.png
The example of my online search for "glen lusk" instead of "glenlusk" still crashes LM. online search > "glen lusk" > single search item in Ireland (other side of world) > tap item > map zooms out to full world > slow crash. On next app start - "Do not visualise too many points and tracks".
Hello Menion,
since beta 4.33.0.10 the problem with "stall during start" is back (Screenshot 1). I waited 20 minutes just for testing it. Pressing the < Android button lets the App crash without any messsge. The next start the map freezes. Normal Buttons are working but neither gesture nor zooming with the buttons is functional (Screenshot 2). This happens every 5-6 times I start the App, more or less.
Pixel 10 pro XL