Messages

This is the second week in row, we have a free Friday in Czech. And I really miss one work day  . So sorry, still some unfinished tasks from the previous and this ( @slarti76 ) week.

*Version 4.33.0.13 (7.5.2026)*
   - add: clipboard coordinates visible as first item in the search
   - chg: custom locations visible in the list of suggested item in the search
   - chg: improved visibility of selected track on map - highlighted track now shows a contrasting color halo
   - chg: improved rendering of circle map items - outline and fill now draw correctly
   - fix: rare crash on app start when the system rejected early connectivity-monitor registration (Samsung / Android 11)
   - add: "Search on Booking.com" integration for accommodation LoPoints
   - add: APRS receiver — pick a custom waypoint icon per sensor in "Sensors manager > sensor > Settings", default rendering is now a discreet Locus dot (no more Garmin red flag)
   - chg: all running services correctly post a black/white icon
   - fix: APRS receiver — Kenwood-radio waypoints (`$PKWDWPL`) plotted on the wrong continent due to a lat/lon swap; timestamps now use the message's own date instead of the phone's wall clock
   - fix: notification on every uploaded LoMedia photo
   - fix: problem with switch of Silver and Gold pages in "My premium" screen
   - fix: incorrect information when using 'Split' option in track editor
   - chg: minor UI changes in Sensors manager (caused by unification with system used in Locus GIS)
   - chg: removed special GIS-based parameters available for external GNSS devices
   - fix: another attempt to fix sometimes not handled parameters passed to app during start
   - fix: stuck navigation after recalculation
   - chg: major speed-up in loading of Geo-tagged photos

Hello,
sorry for a late response.

Have you already removed the application, so the data are lost now? Error 11556 usually means a serious problem with points/tracks database, but it can usually be fixed if the user is able to connect the phone to a PC and manually copy data out of the app directory.

Your questions:
1. usually the easiest way is to create a full backup in the Locus Classic version and import this backup into a fresh version of Locus Map.
2. all what you wrote will work. Only what will need a Silver Premium is the internal calibration tool. MapItems will work without limits.

If there will be anything I may help with, please let me know.

@Ulrich Kiermayr
this is already in progress 

[Locus Map 4.33.0.12]

Locus Map 4.33.0.12
The headline change is a much friendlier handling of background services — every long-running task (guidance, local map server, ...) now lives in its own notification with its own Stop button.
On top of that, a fresh ads-consent flow, a couple of navigation correctness fixes, and the usual round of stability work.

New & changed:

• Per-service notifications — guidance, the local HTTP map server and other background workers each get their own notification with a dedicated Stop action. No more guessing which task the single notification belongs to.
  
• Track editor — explicit save — edits are now kept in memory until you confirm them, so you can experiment freely and bail out without touching the original track.
  
• Ads & consent — reworked ads handling with the required consent dialog and proper lifecycle behaviour.
  

Navigation fixes:

• BRouter (external app) — roundabout voice hints are no longer announced as u-turns, and navigation icons now show up correctly on freshly planned (unsaved) routes.
  
• LoRouter — corrected "keep left / keep right" commands on highways.
  
• Stability — fixed a rare crash at navigation start (and a deeper PROJ / OOM cascade that was behind a handful of recent reports).
  

Other fixes & tweaks:

• locus-actions downloads — no longer fail with timeout (12569) on slow or fluctuating connections. (topic)
  
• QStarz GNSS — restored visibility of QStarz receivers in the sensors options.
  
• Expert settings — every text validated and tidied up.
  
• Internal cleanups around Dashboard variables, locusActions, compressed-file handling, plus the usual long tail of optimizations.

I'll look at the comments at the start of next week, thanks for it!

Regards search > this is not a new week's work. We've planned it and worked on it for more than a year. I'll push my colleague to give a full explanation here, if needed. Anyway, suggest testing it and thinking about what situations it complicates and if there is an option to keep the new system as is and provide some kind of shortcuts. I can imagine, for example, editing coordinates directly in the "Edit point screen" etc.

Hi Yuri,

app internally works with this merged track, really like with one single track. Split to <trkseg> is made really simply, just by remembering at which index it should break. So storing multiple styles for a single track should bring a huge complexity to the whole system. Sorry.

[@Andrew Heard]

@Andrew Heard & @Tapio
display of track from MyLib > we are just converting this screen to the new UI system (while preserving similar style). So some changes/updates like this later (I've made internal TODO).

@Gerhard57 & @WildWortWechsel
line style not visible > ah, thanks!

@Blihi
exists on highway > already reported to my colleague @Radim V . I'll push a little more.

@wollewolle & @balloni55
ah,so the edit of coordinates > this is a big change in recent Beta versions. We completely removed the old "Grid" screen and integrated all into the search screen. No functionality should be lost, and all features are directly in the top row. So the edit of coordinates, projection etc., is all at the top row.

Just quick info > under the main menu long-click is a new item "Upload crash report".

Probably a wrong naming - it grabs
- logs (Locus/logs directory) for last five days
- memory dump not older than a day (it is now automatically created in the case, app crash because of an out-of-memory crash)
- and now also recorded raw BT4 sensors data (recording may be enabled under every sensor > useful for debugging)

And all this is uploaded to our server. Result will be "ID". With this ID, I may check logs or even memory problems a lot more easily. Give it a try if a problem happens. It is a new feature, not well tested, but I believe it will work fine! And it should be start of a lot easier and more precise reporting of problems.

Btw. data are automatically deleted after 90 days from our server.

[Locus Map 4.33.0.11]

Locus Map 4.33.0.11 is out 🎉

  - add: support for QStarz BLE GNSS receivers (BL-1000ST / BL-1000GT / BL-818GT)
  - chg: map server now support full range of visible map content
  - fix: crash in AR screen when point name is too long
  - chg: united settings for Radar sensor into generic sensors settings
  - chg: Slope chart now have only inner fill and not the gradient below
  - fix: incorrect preview for subsequent "Share as screenshot" calls
  - fix: charts ignoring taps in Dashboard editor
  - fix: incorrectly merged plans for planned routes (Re-route wasn't working as expected)
  - chg: improved fallback line style naming and color options
  - fix: app occasionally stuck on loading screen at start
  - fix: another iteration in problematic usage of IGN over map overlay
  - fix: attempt to fix incorrectly rendered track marks during the recording
  - chg: improved handling failed load of custom icons for points (for example for KML files)
  - add: option to directly upload bug reports to our server
  - chg: plus huge list of various internal optimizations

[@wollewolle]

@wollewolle
can't add points > please specify. I see no problem with this functionality.

@Graf Geo
merged tracks re-route > hmm, I'm surprised it worked before. A little more complicated > will look at it, thanks.

@Andrew Heard
web vs apps > there is a greater disparity between our platforms. We are finally starting to work on a system that will allow us to unify these parts of apps, so we get identical results everywhere, always. Work in progress ...

@Gerhard57 & @T-mo
dotted style > oki oki, renamed to "Trackpoints only" and allowed to change color 

@WildWortWechsel
missing buttons > and what is the problem then? You have "Auto-hide" and the buttons hide. Not exactly after timeout, but after a rotation, but it's not a big problem.

stuck at the start > I see the log, will look at it today, thanks

problem with icons > I've changed the "Default point icon" also to something different and I'll be watching it.

world map > with this map set, it is always used for low zoom levels. We are just working on better quality offline world map, so hope this will solve it correctly.

Zdravím Martine,

díky za report. Chyba by již měla být vyřešená v poslední Beta verzi. Pokud se nepletu, mělo by být vždy použité bílé pozadí. Jde nám o to aby vzhled náhledu byl jednotný bez ohledu na telefon a jeho nastavení, proto ta bílá barva.

[@Tapio]

@Tapio
crash in AR > got something, next version thanks

track from library on the map > remind me this later please (if I forget), once we change the track detail screen (May/June).¨

@WildWortWechsel
missing buttons - it mean that the zoom & centre buttons are lost when you rotate the screen? Have you enabled the auto-hide option?

stuck at start > hmm, unfortunate. Next time, open the list of recently started apps (third button in the bottom navigation panel) and swipe out the Locus Map completely. Anyway, how to solve it? Post a bug report after this happens next time (long click on the main app menu after start). Thanks.

default point icons > hmm, any what icons are defined for a points, that now use this "default" icon? Do the have own valid icon?

map > you are zoomed quite a lot. Please check app settings > maps > Advanced > World map. Maybe you have defined online map here?

@Ulrich Kiermayr
missing settings > ah damn. Only this sensor has special custom settings and I've forgotten about it. Will look at it.

@Andrew Heard
crash after search > may you please record a short video for me? I can't simulate the problem and need to verify what do you see and what exactly you tap. Thanks!

@slarti76
slope coloring > hmmm 

"Share as screenshot" > thanks, fixed

"Dotted style" > also for @Tapio ... this change was created really quickly without extra work, and it is mainly a better text in the preview. I see very low usage in it so consider it as a geeky fallback, nothing more ...

[[DE translation]]

[DE translation]

Hallo Leute,
bitte, ich glaube, es gibt keinen Grund, wütend oder unhöflich zu sein.

Dieses Projekt ist wirklich alt (über 16 Jahre) und die meiste Zeit war Locus Map eine Ein-Mann-Show für Android. Seit einigen Jahren arbeite ich bereits mit meinem Kollegen Marek zusammen, aber er kümmert sich immer noch hauptsächlich um bestimmte Teile der App. Er trägt nicht die Verantwortung für das gesamte Projekt.

Letztes Jahr und zu Beginn von 2026 wurde ich langsam wirklich müde. Zu viele Teile und Funktionen, zu leicht, Fehler zu machen, die meiste Zeit verbrachte ich mit der Fehlersuche und Wartung + keine ordentlichen automatisierten Tests.

Seit etwa zwei Monaten nutze ich nun KI, um fast alle meine Schritte zu überprüfen, Probleme zu analysieren und Lösungen zu entwickeln, und das hat mir wirklich sehr geholfen. Was meine Stimmung und Motivation angeht, aber vor allem in Bezug auf die Fähigkeit, mit viel mehr Selbstvertrauen und viel schneller zu arbeiten.

Was bedeutet das für euch hier? Ich mag keine Versprechungen, deshalb vermeide ich sie. Aber ich persönlich habe das Gefühl, dass dies wirklich helfen könnte, die App zu stabilisieren und endlich viele subtile Fehler unter der Haube zu finden.

Einige von euch haben erwähnt, dass bereits gemeldete Probleme ignoriert wurden. Wenn ihr einen Moment Zeit findet, schickt mir bitte einfach eine PM oder einen Hinweis, wo ich das finden kann. Ich werde mir das sofort ansehen.

Und ja, ich stimme Christian zu, dass ich als neuer Mitarbeiter wahrscheinlich gefeuert worden wäre. Andererseits gibt es nicht viele Projekte, deren Entwicklung so lange dauert, und dank der Art und Weise, wie ich all die Jahre gearbeitet habe, ist es mir gelungen, motiviert und voller Tatendrang zu bleiben. Das liegt an der dynamischeren Entwicklung hier mit eurer Hilfe und daran, dass immer etwas Interessantes los ist. Ohne das hätte ich es definitiv nicht so lange ausgehalten. Es ist also ein Kompromiss ... danke für euer Verständnis.

[EN]

Hi guys,
please, I believe, it is not necessary to be angry or rude in any way.

This project is really old (16+ years) and most of the time, Locus Map itself is an Android one-man show. Few years I have already been working with my colleague Marek, but he still do mainly specific pieces of the app. He does not have responsibility for whole project.

Last year and at the start of 2026 I started to be really tired. Too many pieces and functionality, too easy to make a mistake, most time spent on hunting bugs and maintenance + no proper automated testing.

For around 2 months now, I have been using AI to verify almost all my steps, analyze problems and creating solutions and it really helped ... a lot. In my mood and motivation, but mainly in the ability to work with a lot higher confidence and a lot faster.

What does it mean to you here? I don't like promises, so I avoid it. But I personally feel that this may really help to stabilize the app and finally catch many subtle bugs under the hood.

Few of you mentioned that some already reported problems were ignored. If you find a moment, please simply send me a PM or some reminder where to find. I'll look at it immediately.

And yes, I agree with Christian that as a new employee, I would probably have been fired. On the other hand, there aren't many projects that take this long to develop, and thanks to the way I've been working all these years, I've managed to stay motivated and eager to keep going. Thanks to the more dynamic development here with your help, and thanks to the fact that there's always something interesting going on. Without that, I definitely wouldn't have lasted this long. So, it's a trade-off... thanks for understanding.

[Locus Map 4.33.0.10]

Locus Map 4.33.0.10

A 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)
  
• 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 correctly restored for WMS maps.
  
• Correct altitude units in My Library.
  
• Track chart no longer swallows tap events, and chart zoom respects the selected location.
  
• 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.

[@Ulrich Kiermayr]

@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).

[@Andrew Heard]

@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" will be improved)

Beta map manager > yes, I know. Forget on it for now  . 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 Josef
This 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?