New Locus Map (4) version
Important links
- list of news (https://help.locusmap.eu/announcement/locus-map-android-version-4-34-052026) of public versions
- Public versions (http://bit.ly/lmVersions)
- Beta versions (http://bit.ly/lmVersionsTest)
Versions
13. 5. 2026 - Locus Map 4.34.0
20. 5. 2026 - Locus Map 4.34.1
Hi Menion,
thank you for the new version. The start is stable even with many tracks on the map.
I like the elavation view on the upper frame so the trail is visible.
The halo for long trails is not optimal but ok. In principle I like the new halo.
Greetings and have a nice day!
Edit: Added screenshot.
Thanks for the new relase version! It's made a good impression so far!
Regarding track highlighting: We could experiment with this a bit more, but the current effect is perfectly acceptable.
However, there are two line colours where, strangely, the arrows are white (and therefore hard to see) when highlighting, even though black would make more sense: cyan and light green (see screenshot).
But that's not an issue.
Edit: I can now see the more discreet "data bubbles" above the charts; they no longer cover them up. Very good!
Have a lovely weekend from me too!
I'm glad it works fine, super!
About highlight ...
@WildWortWechsel , hmm it should not look like this, damn! Guys, if you, anyone, share a track over "Share by link", I'll gladly look at it!
Quote from: Menion on May 14, 2026, 22:00:45I'm glad it works fine, super!
About highlight ... @WildWortWechsel , hmm it should not look like this, damn! Guys, if you, anyone, share a track over "Share by link", I'll gladly look at it!
The track is on the way ...
Now that the charts have been improved so nicely, here's another request or suggestion:
The labels partially cover large areas of the two bar charts for way types and surfaces (see screenshot).
Perhaps the labels could be placed above the charts here too, as is the case with the other charts.
It would be even better if these bar charts could also be included in the chart overview so that they can be zoomed in on as well. For longer routes, they have always been too compressed, which makes analysis difficult.
Quote from: Graf Geo on May 14, 2026, 23:29:52bar charts could also be included in the chart overview so that they can be zoomed in on as well. For longer routes, they have always been too compressed, which makes analysis difficult.
great suggestions; my use-case - 80km route for day with tiny 200m unsealed which I'm interested to decide further, but super difficult at present w/o zoom to determine where on the map/ route this section really is
4.34: @menion - this behavior started with the new chart system - track > chart > tap "+" a few times without tapping elsewhere on the chart > now single-finger-drag on the X axis instead of the chart body > observe that the chart is further zoomed instead of panned - is this intended behavior? I am using X axis: time. Sometimes while panning until near end of the chart then further dragging results in zooming until the X scale is hugely magnified. Quite confusing. Have to unzoom & start again. It is a little difficult to reproduce, I don't fully understand the "trick" yet.
As discussed in 4.33, from the chart, tapping the Map icon does not position the map at the currently selected position on the chart.
Is 4.34 a record for most changes?
@Andrew Heard:
I can't quite understand the issue with zooming on the x-axis, nor can I reproduce it.
Map icon in the chart overview: The map centres correctly on the position I click on in the chart. The only thing that doesn't work: I click on the track on the map, e.g. at the start of the track. The track info panel opens with the elevation chart, and the position at the start of the track is correctly marked there. Then I open the chart overview and click on a different position, e.g. a peak of a hill. Clicking the map icon takes me back to the map, which is now correctly centred on the peak. However, the track info panel is still open, and the old position at the start of the track is still marked on the elevation graph there. So it isn't updated. But that's not a big deal.
"Most change record": I thought the same thing. 😉
Quote from: Graf Geo on May 15, 2026, 10:02:30I can't quite understand the issue with zooming on the x-axis, nor can I reproduce it.
Sorry. I'll try to record the screen sometime when I understand how to reproduce it too.
Hi Menion
Any updates on the topics I sent you by video? I might have overlooked something in the news, but I assume you didn't get to it yet.
Also, last thread I had this: https://forum.locusmap.eu/index.php?topic=9553.msg81082#msg81082
I looked at it again, and it seems better, but still somehow off. Let me give you an example: I'm in Zurich, the map is centered on Gdansk, and I'm searching for Krakow. Now the arrow points due east and the distance is 886km. The distance may be correct from Zurich, but due east is neither correct from Zurich nor from Gdansk.
Furthermore, it would be really nice to have access to a history of entered searches. I think we had something like that before?!
New version 4.34.1 just uploaded on Google Play & Drive.
Changelog: here (https://help.locusmap.eu/announcement/locus-map-android-version-4-34-052026).
---
@slarti76 & others
I think I was looking at something, but ... :-X ... I'll confirm & write more till the end of the week. Was fully focused on fixing of problems for the new bug-fix version. Thanks for understanding.
Impressive changelog for version 4.34, I needed five minutes alone for reading 8)
Hi Menion,
the halo for long tracks is fixed. Thank you!
Just noticed something weird: I was scrolling through the directory list in Geotagged Photos (which really needs a search or filter, but that's another topic), and at least one folder was missing. I checked on the storage, it's definitely there, contains JPGs, just like the one before and after. I did a full reload (the menu entry is still having a "T:" string, but also another matter), no change.
What could I be missing? Or what info could I give to help with debuggin? I can hardly copy my images folder (>20GB)...
Ignore that, was my mistake.
Are there definitely some geotagged JPGs in the missing folder?
Are those shown in Google Photos? I'd refresh the Android MediaStore. @Menion, does LM maybe trigger that, via "Full Rescan"?
Quote from: Graf Geo on May 21, 2026, 22:27:13Are there definitely some geotagged JPGs in the missing folder?
Oh man, I'm so sorry! I checked again with another app, and the Geotags in this folder are missing. I have all my pictures geotagged since at least 10 years, but this folder from 5 years ago is missing them.
So nevermind!
@slarti76
I was already looking at the problems with the track editor mentioned here (https://forum.locusmap.eu/index.php?topic=9553.msg81127#msg81127). It should already be fixed in the latest version, isn't it?
Version 4.34.1.1 (22.5.2026) .. have a nice weekend!
- chg: completely new Garmin IMG map renderer
- add: (SILVER) track elevation chart area fill is now color-coded by slope magnitude — green (<6 %), yellow (6–12 %), orange (12–20 %), red (>20 %)
- add: (SILVER) support for Bosch eBike Smart System sensors (v19+) — live battery, speed, cadence, rider power, odometer over the Bosch Live Data Interface
- chg: (SILVER) Specialized eBike sensor support extended to TCX 2/3/4 protocol generation (post-2019 Vado / Como / Creo / Levo gen 2 / PLW)
- add: (SILVER) support for Shimano STEPS e-bikes (EP-8 / EP-801 / E5000 / E7000 / E8000 / EW-EN100) — live battery, speed, cadence and assist mode over BLE
- add: (SILVER) dedicated picker entry for Fazua e-bikes (Ride 50 / Ride 60) — collapses the previous "pair as power meter + pair as speed/cadence" two-step workflow into a single connection
- add: (SILVER) extended e-bike telemetry — motor power, motor temperature, battery health, battery temperature, battery charge cycles, remaining range, altitude gain/descent and gradient (surfaced when the bike exposes them); Shimano STEPS now surfaces the current gear and uses Shimano-specific assist-mode labels (Boost / Walk)
- add: (SILVER) bicycle gear and remaining range from e-bike sensors are now selectable as dashboard variables (Add panel/cell → Sensor)
- add: (SILVER) support for BT4 footpods (SIG Running Speed and Cadence profile) — Stryd, Polar, Wahoo, Suunto and others; complements the existing ANT+ footpod with the more common BLE flavour
- chg: Expert settings: the two separate "high precision" toggles for altitude / angle are replaced by a single "High precision mode" switch that also covers distance rendering
- fix: crash in NTRIP client when the caster dropped the TCP connection while the app was in the background
- fix: direction arrow in search/MyLibrary now always hardware to display proper orientation
do you ever sleep @menion? latest beta just 2 days after 4.34.1!
The bike sensor is great. Added the Shimano EP8 sensor / battery level to the dashboard. Works great.
Thanks
Question: Does the Bluetooth connection drain the battery constantly? Or only when the screen is on?
Quote from: Menion on May 22, 2026, 11:04:28@slarti76
I was already looking at the problems with the track editor mentioned here (https://forum.locusmap.eu/index.php?topic=9553.msg81127#msg81127). It should already be fixed in the latest version, isn't it?
Oh, sorry, didn't check that correctly - can confirm it's fixed! :)
Quote from: Menion on May 22, 2026, 16:01:30- fix: direction arrow in search/MyLibrary now always hardware to display proper orientation
Cannot confirm :( Now, being based in Zurich, search e.g. for Warsaw shows an arrow pointing to NNW - and Warsaw is clearly east. I did some other searches, and there doesn't seem to be a consistent pattern (like 90° rotation or the like). Distance seems correct, tho.
I think, it depends on the vertikal and horizontal orientation of the phone, the arrows turns depending on both.
Quote from: Joska on May 24, 2026, 10:25:01I think, it depends on the vertikal and horizontal orientation of the phone, the arrows turns depending on both.
Now I get it: It's not screen orientation, it's phone orientation! They arrows actually turn when I rotate the phone. I guess that makes sense for closer destinations, not so much looking for a far away city. ;D
The main misunderstanding is that I'm thinking "planning", but the actual purpose is "on the road".
I think ideal would be to have two modes:
- On the road: As now, direction from current location, using phone orientation
- Planning: From current map center, using static compass directions
But I admit, probably too much effort for small detail...
Quote from: slarti76 on May 24, 2026, 11:00:20Quote from: Joska on May 24, 2026, 10:25:01I think, it depends on the vertikal and horizontal orientation of the phone, the arrows turns depending on both.
Now I get it: It's not screen orientation, it's phone orientation! They arrows actually turn when I rotate the phone. I guess that makes sense for closer destinations, not so much looking for a far away city. ;D
The main misunderstanding is that I'm thinking "planning", but the actual purpose is "on the road".
I think ideal would be to have two modes:
- On the road: As now, direction from current location, using phone orientation
- Planning: From current map center, using static compass directions
But I admit, probably too much effort for small detail...
Testing and thinking about it:
When the map is locked in "north up", the search should also respect that and show the arrow with respect to north up. (To be consistent with the map shown)
When map rotation is on, then the search should behave like it does now.
I think, this would resolve most of the confusion. Search should simply behave like the actual behavior of the map
Greetings, Ulrich
Quote from: Ulrich Kiermayr on May 24, 2026, 11:44:12Quote from: slarti76 on May 24, 2026, 11:00:20Quote from: Joska on May 24, 2026, 10:25:01I think, it depends on the vertikal and horizontal orientation of the phone, the arrows turns depending on both.
Now I get it: It's not screen orientation, it's phone orientation! They arrows actually turn when I rotate the phone. I guess that makes sense for closer destinations, not so much looking for a far away city. ;D
The main misunderstanding is that I'm thinking "planning", but the actual purpose is "on the road".
I think ideal would be to have two modes:
- On the road: As now, direction from current location, using phone orientation
- Planning: From current map center, using static compass directions
But I admit, probably too much effort for small detail...
Testing and thinking about it:
When the map is locked in "north up", the search should also respect that and show the arrow with respect to north up. (To be consistent with the map shown)
When map rotation is on, then the search should behave like it does now.
I think, this would resolve most of the confusion. Search should simply behave like the actual behavior of the map
Greetings, Ulrich
Very good idea! +1
Ok, tbh, I'm a little bit angry now: I just spent 30min editing a track and then did what I always did: Tap "X" in the upper left corner, because all edits are saved immediately, right? Well, I didn't see the new "Save" button (and the changelog entry "track editor now saves the track after user confirmation"), which is a great idea, absolutely!
But simply undoing all edits without asking the user on a single tap??? Sorry, that's an absolute no-go!
Please add a user confirmation here! Thx.
Quote from: slarti76 on May 24, 2026, 11:00:20Now I get it: It's not screen orientation, it's phone orientation!
@slarti76 good observation; I never knew that. North up seems more intuitive to me.
The waypoints are not displayed on charts. Not in existing tracks or new created tracks neither. "Show waypoints" in chart settings is activated.
What do I wrong?
V4.34.1
@Andrew Heard
hehe :). It looks like a lot of work was done. But it just sits on quite well prepared code from years before and adds a small AI-driven code, that needs a manual field testing.
@freischneider
hmm the first brave and successful at the start, amazing! Yes, it works as all other sensors > they need a permanent connection. It is based on BT4, so battery consumption should be really low.
@slarti76
I'm probably still confused. All seems to work correctly to me.
My situation: current GPS location in Prague, search for "Kyiv" clearly displays 1130km to the east. Arrow correctly rotates as I rotate with the phone. App Settings > Miscellaneous> Default search/sort location settings have no effect here. GPS or the last known location is always used in the search screen.
Do you have the same experience?
Track editor > check on changes is already wired on the Back button click. I'll improve it, thanks ... and sorry :P
@Christian
Track waypoints > when you open the track detail and scroll down, do you see waypoints in the block under charts?
Quote from: Menion on May 25, 2026, 13:17:04@slarti76
I'm probably still confused. All seems to work correctly to me.
My situation: current GPS location in Prague, search for "Kyiv" clearly displays 1130km to the east. Arrow correctly rotates as I rotate with the phone. App Settings > Miscellaneous> Default search/sort location settings have no effect here. GPS or the last known location is always used in the search screen.
Do you have the same experience?
Yeah, sorry, wrote in my last post that I finally realized it's always current location + phone rotation. As Andrew writes, one can argue about what's more intuitive. But I now agree there's no obvious bug here, so let's leave it at that, more important things...
Quote from: Menion on May 25, 2026, 13:17:04Track editor > check on changes is already wired on the Back button click. I'll improve it, thanks ... and sorry :P
Apology acdcepted 8) Thx!
Quote from: Menion on May 25, 2026, 13:17:04@Christian
Track waypoints > when you open the track detail and scroll down, do you see waypoints in the block under charts?
Yes. All of my wpts.
Hi @Menion,
Quote from: Menion on May 25, 2026, 13:17:04@slarti76
I'm probably still confused. All seems to work correctly to me.
My situation: current GPS location in Prague, search for "Kyiv" clearly displays 1130km to the east. Arrow correctly rotates as I rotate with the phone. App Settings > Miscellaneous> Default search/sort location settings have no effect here. GPS or the last known location is always used in the search screen.
Do you have the same experience?
This is, what I meant by confusing. This always confused me, but the discussion triggered the report.
Compare the 2 screens. On the map (without rotation, north up) I use for planning, Götzendorf is to the left (west, blue arrow)
Screenshot_20260525_201652_Locus Map.jpg
In the search screen from the position I was sitting, Götzendorf is up (because I was facing west when sitting)
Screenshot_20260525_201756_Locus Map.jpg
I find it confusing because when planning I don't know where north actually is, but I have a map with fixed orientation. So I would expect the search screen arrows to point on the direction, where I find the results on the map.
Greetings, Ulrich
Quote from: Christian on May 25, 2026, 20:04:51Quote from: Menion on May 25, 2026, 13:17:04@Christian
Track waypoints > when you open the track detail and scroll down, do you see waypoints in the block under charts?
Yes. All of my wpts.
Same here, the embedded WP don't show up on charts. It's checked in the chart options.
I've noticed, although could have been like this for a while, when you now tap a track that is being recorded, there is less than 1-in-30-taps chance the track details will be displayed in the bottom panel. Previously this was quite reliable i.e. tap the track & details displayed. It generally required North-up for the compass i.e. not rotating. Bug?
20260526-170237-Desktop - File Explorer.jpg
@menion Last week I reported (https://forum.locusmap.eu/index.php?topic=9614.msg81196#msg81196) that under "unknown circumstances" the track chart would zoom instead of pan, while using a single finger drag. I now have a screen video of it. Maybe it requires the X-axis to be time instead of distance, or to have a gap/ pause in the recording? In the video I tap +/zoom once, then single tap-drag to try to pan but you can clearly see it zoom instead. The tap position is faintly visible.
https://youtube.com/shorts/2y-jXB_XU5I
Quote from: Andrew Heard on May 26, 2026, 09:10:15@menion Last week I reported (https://forum.locusmap.eu/index.php?topic=9614.msg81196#msg81196) that under "unknown circumstances" the track chart would zoom instead of pan, while using a single finger drag. I now have a screen video of it. Maybe it requires the X-axis to be time instead of distance, or to have a gap/ pause in the recording? In the video I tap +/zoom once, then single tap-drag to try to pan but you can clearly see it zoom instead. The tap position is faintly visible.
https://youtube.com/shorts/2y-jXB_XU5I
Yeah, I can confirm that and also reported sth similar recently: The charts don't seem to be able to move consistently over pauses/gaps - instead when dragging, for a while the zoom changes, until the end of the gap is reached and the chart snaps to there. I don't see any good reason why the gaps should have any effect on dragging at all, so to me this is a bug.
after reading the latest news @ https://www.locusmap.app/search-chart-android-auto/ I have some comments I think more appropriate here than at the end of the post
1) Why are some location sources disabled even when I have Wifi enabled?
20260527-130122-.jpg20260527-130134-.jpg
2) As previously discussed a few times with @tapio et.al., tapping the Map icon for a just-saved track recording does not center the map on that point, just the middle of the whole track
20260527-130220-Desktop - File Explorer.jpg
@Andrew Heard:
Re 1: because it doesn't make much sense to search for "My location", "select on map" or "screen centre" in the main search bar – you're already on the map view anyway. ;) "My points": You can search directly for a point; after submitting the search term, a button with the points symbol and the number of hits ("x items") appears at the top.
Re 2: For me, the map centres correctly on the point clicked in the chart.
Quote from: Graf Geo on May 27, 2026, 09:10:24Re 2: For me, the map centres correctly on the point clicked in the chart.
Not if you approach the track by starting the library first. From there, go into a tracks full diagram view and try it.
OK, you're right. That's not my use case, so I never noticed it.
@Christian
waypoints on chart > share a one track with me (Share by link), please. I can't simulate it. Thanks.
@Ulrich Kiermayr
direction arrow > thanks for the push, we will discuss this more in the team as I've no clear opinion here.
@Andrew Heard
track detail > we are in the process of a complete rewrite of this screen into a new technical solution (while preserving the same UI for now).
chart with gaps > thanks, I'll look at it.
disabled options in search > some are disabled in certain moments, because they are not needed. It should be consistent with the old grid solution. It has nothing to do with the internet connection.
centre from the chart > and as mentioned many times, this waits on the new track screen.
Quote from: Menion on May 29, 2026, 11:00:53@Andrew Heard
track detail > we are in the process of a complete rewrite of this screen into a new technical solution (while preserving the same UI for now).
Hi Menion, is there an approximate timeline for when a new track info screen will be made available, at least as a beta version? I've been looking forward to a customisable track info screen for ages... 😉
Today :)
Do not expect much now. We first need to switch the old UI system to the new UI system. Once it works correctly, we can move to UI modifications. Currently, there should be an improvement in the landscape and on tablets.
Version 4.34.1.2 (29.5.2026)
- add: (SILVER) Locus now opens to community sensor adapters — third-party apps can expose their own sensors (e-bike protocols, niche BLE devices, custom hardware) and they appear in the regular sensor picker with live values feeding dashboards, audio coach and track recording exactly like built-in sensors; developer SDK at github.com/asamm/locus-api
- chg: completely new system behind track screen. Improved functionality in landscape and tablets, preserved UI
- chg: (SILVER) slope colour scheme reworked — downhill now shown in blue (darker = steeper), flat in grey, uphill in a pale-yellow → amber → orange → red ramp; applies to both the map track line and the elevation chart fill
- chg: custom slope range setting for the line style removed
- fix: (SILVER) smoother panning of the zoomed track chart across recording gaps — the chart no longer snaps and the x-axis keeps moving while the window crosses a gap
- chg: location picker row now opens the full source chooser; a dedicated trailing icon jumps straight to manual coordinates entry
- fix: tapping a track in MyLibrary no longer crashes the app when the tracks database is corrupt; the database is now reliably rotated out on each corruption event and the first corruption snapshot is preserved as `.backup.1` for recovery, so the app does not get stuck in a perpetual crashloop
- fix: crash when a foreground service notification failed to post; the underlying error is now captured and the service is shut down cleanly instead of triggering "Bad notification for startForeground"
- fix: crash in the Route planner when a route was computed while the selection points were being modified on a background thread
- fix: crash when refreshing a KML network link whose icon points to a local file instead of a web address
- fix: crash when rotating the screen on the Parking setup screen; the entered location is now kept across rotation
- fix: crash when a background task service exceeded the Android foreground-service time limit
- add: sharing a point as text can now include a standard geo: link, so any map app can open the exact location
- fix: rare ConcurrentModificationException in the track-recording home-screen widget — overlapping Glance update / preview composes are now serialized
- chg: Track editor "cross" button ask for "save changes" before closes the screen
- fix: crash when opening the map import dialog while the source map was still loading
- fix: ConcurrentModificationException in Route planner when a track was reloaded while map selection items were being iterated on a background thread
- fix: crash when computing a BRouter route twice in quick succession in the Route planner
- fix: crash in Store when re-opening a no-longer-available item detail — back-press now defers correctly past the active fragment transaction
- fix: rare crash during track guidance when a fresh location arrived before the next navigation point was prepared
Chart panning when time gaps in the chart now works perfect - thanks!
Adapter API Beta feedback:
When the bike is stationary, the sensor adapter keeps sending valid data (battery %, assist mode, range) every 1.5s via the SEC batch. Locus clears the sensor display anyway after a short time. In the previous direct-BLE approach, values persisted. Could there be a persistLastValue option per <refId> in the manifest, or a minimum hold-time before Locus clears adapter values?
Ooh, that track panel view when starting from inside the media library is a big change. It's probably good that it's now looking the same, but now we can't see that we're inside the library. Ok Tiny differences, the two buttons on the map, no trackpoint button. Interesting.
Menion, it was possible to minimize the track panel to a very small state, so only its title was visible. It was useful. That got lost.
Quote from: Tapio on May 30, 2026, 03:11:20... but now we can't see that we're inside the library. Ok Tiny differences, the two buttons on the map, no trackpoint button.
The two buttons are striking enough. And track is not highlighted. So I think it's easy to tell apart.
The display of the track info panel in landscape mode is a very welcome improvement. At last, you can view the track and the elevation profile at the same time when geotagged photos are enabled. You can then scroll through the panel (albeit a bit clunky). Funnily enough, the scroll position (not exactly, but roughly) is retained when you switch back to portrait mode.
Edit: The new landscape view only works for tracks, not for points. Or not yet?
What I don't like so much is the new font for the track title. It now seems even larger than before and therefore takes up even more space, especially with multi-line titles.
Quote from: hoschilo on May 30, 2026, 02:11:23Adapter API Beta feedback:
When the bike is stationary, the sensor adapter keeps sending valid data (battery %, assist mode, range) every 1.5s via the SEC batch. Locus clears the sensor display anyway after a short time. In the previous direct-BLE approach, values persisted. Could there be a persistLastValue option per <refId> in the manifest, or a minimum hold-time before Locus clears adapter values?
Quick update: the issue with power fluctuating between -1 W and real values is now fixed.
Root cause: The Brose motor returns -1 as a sentinel value for power when the bike is stationary (no pedalling). The adapter was passing this raw value directly to Locus Maps, which displayed it as -1 W.
Fix: Clamp the value to a minimum of 0 before sending — so Locus always receives either 0 W (idle) or the real wattage while riding.
https://github.com/hoschilo/locus-brose-adapter
Hi Menion,
first of all: thank you for the latest beta. I like the new track/elevation panel especially that the distances are visible without the need of shifting the panel upwards.
- Is it possible to keep the gps position during a hike fix on the elevation chart indepentant of a click on it? At the moment you loose your position when clicking somewhere on the chart e.g. for distance measurement to find a camp spot etc.
- during map zooming the trails of the hiking routes are "smashed" of the Germany south map.
Have a nice weekend!
Pixel 10 pro XL
Android/GrapheneOS 16
Latest Beta
Edit: the elevation chart in landscape mode is relatively small. It doesn't use the max. screen size. For longer tracks it would be usefull if the chart would be wider because the max. zoom is 25 km/screen by a 600 km track. Or is it possible to add more zoom levels so the resolution would be better?
I've just installed the latest beta. When I tap on a track now, the track info pops up from the bottom; the associated images are visible as the top entry, with just a small section of the elevation profile barely visible below that.
Now I can click on specific points on the track and see that something is happening 'below', or I can scroll the track info up and click on the elevation profile, but then I can no longer see where exactly on the track this is.
The only thing I can think of is to turn off the display of the images, but previously I was usually able to see both the track and the elevation profile at the same time.
There was also talk at one point of using checkboxes to select which track information should be visible on the screen at the same time as the track itself.
Collapsible and expandable panels were also an option.
What is the latest status on this?
Maybe, it's my fault, and I should use another configuration?
@Joska there is no such change so far. The panel is still not configurable. The fight of pictures vs. diagram is ongoing.
What has changed is, when you go from Library into a track, UI now looks the same as in map view.
Something more. With last Beta, trackrecording shows a few interruption of a track record. This lead to minor distance and strong reduced total recording time.
With regular version (my wifes phone), no interruptions.
Just realized that in the trail view the lower menu is gone. Will it come back? Or is it a bug?
Quote from: WildWortWechsel on June 01, 2026, 00:03:27Just realized that in the trail view the lower menu is gone. Will it come back? Or is it a bug?
Here it works. Maybe Fullscreen mode related?
Quote from: Tapio on June 01, 2026, 01:33:01Quote from: WildWortWechsel on June 01, 2026, 00:03:27Just realized that in the trail view the lower menu is gone. Will it come back? Or is it a bug?
Here it works. Maybe Fullscreen mode related?
Thank you for testing! I also did some more tests and figured out, the lower menu is sometimes visible, sometimes not. Seems not related to full screen mode.
I don't like the new colors for the track in "Colored Gradient." I'm having trouble following the course of the track. The colors are very pale. With the old colors, I could see the track much more clearly, and I could spot steep sections much more easily. They stood out right away.
Yes, I can see that; colours have their pros and cons. It works quite well on the elevation profile. When I colour-code the route, I always add a black outline so that it's easy to make out.
Ultimately, you'll never find colours that are the best solution for everyone. It's just the same when it comes to highlighting routes.
Quote from: freischneider on June 01, 2026, 16:34:59I don't like the new colors for the track in "Colored Gradient." I'm having trouble following the course of the track. The colors are very pale. With the old colors, I could see the track much more clearly, and I could spot steep sections much more easily. They stood out right away.
+1
@hoschilo
nice one! Every sensor value has own parameter that defines how long the value is valid. In the case of a bike battery, it is 15 minutes, but most of the sensors are valid for 5 seconds.
@Tapio
minimising on title tap > heh, we tested if anyone noticed it. A small complication, but we will look at it.
@Graf Geo
not points in landscape > what happens in the track screen on the background is huge. It took us a month of work :) . Points later.
New font > there is no new font. It will be a side effect of the unification of the panel with the rest of the app. Anyway, understand. Will think about it ...
@WildWortWechsel
- GPS position on the chart > added
- max. chart scale > increased
- problem with trails > what exactly is the problem? Not clear from screenshots. A partially missing line is probably a small graphical problem in the used library. Hard to solve, sorry.
missing buttons > does it happen everytime or are you able to describe to me a steps that lead to this state?
@Joska
attachments and chart at once > improvements are "work in progress". Patience please.
gaps in recording > there were no changes in the recording system. I may only point to our docs here (https://docs.locusmap.app/doku.php?id=manual:faq:gps_lost_fix_android6).
@freischneider
slope colouring > ok, I'll prepare better visible version
Quote from: Menion on June 02, 2026, 10:10:24@WildWortWechsel
- GPS position on the chart > added
- max. chart scale > increased
Hi Menion,
thank you!
Quote- problem with trails > what exactly is the problem? Not clear from screenshots. A partially missing line is probably a small graphical problem in the used library. Hard to solve, sorry.
Parts of the hiking trails are missing or the lines are not complete drawn. No problem for me.
Quotemissing buttons > does it happen everytime or are you able to describe to me a steps that lead to this state?
Every time with the same recorded track, but not with every recorded track. See the screenshots: both are recorded. One shows the buttons, the other not when clicking on it.
Quote from: Menion on June 02, 2026, 10:10:24@Joska
attachments and chart at once > improvements are "work in progress". Patience please.
gaps in recording > there were no changes in the recording system. I may only point to our docs here (https://docs.locusmap.app/doku.php?id=manual:faq:gps_lost_fix_android6).
Hi Menion, I know, but as you said, there were no changes, same here, from one day to the next, these interrupts occured, without changing the configuration. My wife used an earlier version, no interrupts.
But of course, I'll check again.
Locus Map 4.34.1.3AI-generated news...
This update sharpens day-to-day track recording and the elevation chart, and opens Locus up to more sensor hardware. Track recording gains a single, clearer "Movement detection" control, the elevation chart shows where you are on the route and gets a reworked slope palette with a built-in colour legend, and community sensor adapters can now advertise their hardware by BLE service UUID for more reliable e-bike connections. A batch of fixes restores third-party routing, guidance arrows, and login, and hardens the image map calibrator.
What's new- Movement detection — auto-pause and "record only when moving" are now one setting: record continuously, drop points while stopped, or auto-pause.
- Position on the elevation chart (Premium) — a blue dot shows your current GNSS position on the chart when you're within 100 m of the track.
- Reworked slope colouring (Premium) — tuned palette so gentle slopes are no longer washed out and steep sections stand out; the colour fill now sits beneath the chart lines so they stay crisp.
- Colour legend (Premium) — tap the question-mark next to "Line style" to see what the active track colouring means.
- Wider sensor support (Premium) — adapter apps can declare their hardware by advertised BLE service UUID, giving e-bike and vendor-protocol devices reliable, low-power scanning.
- "Last points" quick toggle — My library search can now show your most recently saved points. (topic) (https://help.locusmap.eu/topic/40496-new-mylibrary-search-add-quick-toggle-last-also-for-points)
Smaller improvements- Track chart pinch-zoom now goes all the way down to 1 km / 1 minute on any track length (Premium).
- Tapping the track chart now also shows the distance or time at that point, not just the values. (topic) (https://help.locusmap.eu/topic/40457-display-distance-or-time-in-tooltip-for-tapped-chart-point)
- Alternative-route de-duplication (Premium). (topic) (https://help.locusmap.eu/agent/object/37369#comment-162179)
- OpenTopoMap moved to its new server and now shows more detail (zoom level 17).
Bug fixes- Fixed the user profile screen getting stuck on loading after signing in with Google / Facebook / email.
- Third-party routing add-ons appear in the routing-source list and work reliably again.
- Track guidance again shows directional arrows along the route.
- "Record only when moving" no longer drops valid points when GPS speed dips briefly while you're nearly still.
- Fixed a rare track-recording widget crash on app start.
- Opening recording-profile settings from the home-screen widget — Back now returns straight to your launcher. (topic) (https://help.locusmap.eu/topic/40496-new-v4-34-widget-back-behaves-not-logical-and-not-as-useful-as-possible)
- Image map calibrator (Premium): KMZ export no longer fails with "Process unsuccessful" on common image sizes; the export can be cancelled mid-process, failures now show the real cause with a Retry button, and the map picker centres on the estimated location when adding the 4th+ point. (topic) (https://forum.locusmap.eu/index.php?topic=9632.0)
- Image map calibrator (Premium): no longer crashes when a selected photo can't be copied, and shows a clear message when an image fails to load.
All Features, Search Box, enter some letters: The window can only be left if I delete the entered letters. It's an older issue.
Hi Menion,
great job! Thank you!
BTW, the lower buttons still not visible sometimes. But now I can see the "head" of the buttons at the lower screenframe.
Have a nice weekend!
Edit: I guess, I figured out why the lower buttons sometimes gone. It seems to depend on the length of the title. One line - buttons visible. Two lines - buttons not visible.
Thanks, fine!
Two first questions:
Slope colouring now in all charts, also speed and pace - intended?
Where can I find the legend: question-mark next to "Line style"?
Can't see the question-mark.
Have a nice weekend!
Crash when using external routing addon after cold start is gone. Nice work!
Quote from: Menion on June 05, 2026, 13:53:33Smaller improvements
- Tapping the track chart now also shows the distance or time at that point, not just the values. (topic) (https://help.locusmap.eu/topic/40457-display-distance-or-time-in-tooltip-for-tapped-chart-point)
sometimes the value of the y axis right is missing. See screenshot
Quote from: Menion on June 05, 2026, 13:53:33,,Nur beim Bewegen aufzeichnen" führt nicht mehr dazu, dass gültige Punkte verloren gehen, wenn die GPS-Geschwindigkeit kurz abfällt, während Sie fast still sind.
Maybe it is the issue, I've written about in #64?
Quote from: Menion on June 05, 2026, 13:53:33Locus Map 4.34.1.3
AI-generated news...
I hope @Menion isn't being replaced by @AI
can someone help
<Colour legend (Premium) — tap the question-mark next to "Line style"> - where is the question-mark icon in the track chart? thanks
Quote from: Andrew Heard on June 05, 2026, 23:29:48Quote from: Menion on June 05, 2026, 13:53:33Locus Map 4.34.1.3
AI-generated news...
I hope @Menion isn't being replaced by @AI
can someone help <Colour legend (Premium) — tap the question-mark next to "Line style"> - where is the question-mark icon in the track chart? thanks
At the bottom
Quote from: freischneider on June 06, 2026, 07:31:22Quote from: Andrew Heard on June 05, 2026, 23:29:48can someone help <Colour legend (Premium) — tap the question-mark next to "Line style"> - where is the question-mark icon in the track chart? thanks
At the bottom
@freischneider example of bottom of a track chart; what am I missing?
20260606-170606-.jpg
Quote from: Andrew Heard on June 05, 2026, 23:29:48can someone help <Colour legend (Premium) — tap the question-mark next to "Line style"> - where is the question-mark icon in the track chart? thanks
Its in the track detail when the line style in NOT plain color.
Quote from: Andrew Heard on June 06, 2026, 09:06:21Quote from: freischneider on June 06, 2026, 07:31:22Quote from: Andrew Heard on June 05, 2026, 23:29:48can someone help <Colour legend (Premium) — tap the question-mark next to "Line style"> - where is the question-mark icon in the track chart? thanks
At the bottom
@freischneider example of bottom of a track chart; what am I missing?
20260606-170606-.jpg
OH "REORDER SECTIONS" FOR THE TRACK PANEL.
Just noticed it's in the Hamburger menu. @Menion please include photos there! Also, let us disable sections.
Hi,
New bug (edit as noted below):
Track editor Route planner > Select start > My location
Does not work any more
LG uk
Quote from: Gerhard57 on June 06, 2026, 09:41:32Quote from: Andrew Heard on June 05, 2026, 23:29:48can someone help <Colour legend (Premium) — tap the question-mark next to "Line style"> - where is the question-mark icon in the track chart? thanks
Its in the track detail when the line style in NOT plain color.
@Gerhard57, @freischneider (@menion) - ok thanks - but clearly the new chart in my screen cap has varying colors, so a legend that describes those colors should be accessible too? To me, the most obvious place for access to the legend ('?' icon), is from within the chart panel.
Quote from: Tapio on June 06, 2026, 19:06:39OH "REORDER SECTIONS" FOR THE TRACK PANEL.
Also, let us disable sections.
@Tapio +1; yes I noticed too. Not listed in last 2 release notes.
Quote from: Ulrich Kiermayr on June 06, 2026, 20:46:49Track editorRoute Planner > Select start > My location
Does not work any more
"REORDER SECTIONS" FOR THE TRACK WINDOW
First of all, thanks for this initial configuration option!
I agree, please make it possible to hide or disable sections.
And is it possible to split the "Details" section? I don't need the line type in the info window (I can see that on the map), only in the edit menu. The same applies to "Activity" – I don't need that in most cases.
And it would be brilliant if you could save the settings for each folder individually. I don't need a elevation chart for my jogs or walks around town, but I certainly do for hill or mountain walks. 🙂
First of all: Great list of new features and fixes, thx!
One question:
Quote from: Menion on June 05, 2026, 13:53:33- Track chart pinch-zoom now goes all the way down to 1 km / 1 minute on any track length (Premium).
Is there a reason the minimum distance is still 1km? Comparably, that is much less ability to zoom in than when choosing time, where 1min makes sense, I think. But for slow activities like hiking, I think 100m would be much more helpful (which is roughly what you're walking in 1min normal speed).
I see that for long tracks like car rides this might slow down the panning, so the minimum might be made dependent on track length again, e.g. 100m for <=10km, 200m for <=20km, 500m for <=50km, 1km >50km
"REORDER SECTIONS"
Maybe this way: :)
I'm also very much in favor of
a) Adding the photos to the "Reorder Sections" dialog (which probably means "Statistics" become explicit section, too)
b) Being able to hide section in that dialog (e.g. I *never ever* need intervals because I don't do that kind of training)
c) Being able to choose which sections are show immediately on select and which only by pull-up. Perhaps the reorder dialog could have a divider which can be put after first, second, or third entry; so e.g. you could customize it to only show title (always) and statistics, leaving more space for map.
While we're at it:
- Is "Line style" really necessary in the Details? I mean, I see the line style on the map, and unlike "Folder" I can't do anything here. Imho would only make sense if that was a direct link to the edit line style dialog.
- Similar with "Activity" - it's of interest, but being able to change activity directly there would be nice.
- Lastly, I also like Google Map's ability to copy the name of a POI by simple long tap on the title. That would be great for Locus tracks and POIs - right now, you need to do "Edit" > Long-Tap somewhere in title > Tap "Select All" > Tap "Copy"
EDIT: About the Details: Thinking about it again, the "Activity" is also duplicate, we already have the icon in the top-left. That could be made clickable to show a selection menu which a) gives you the name of the activity, and b) allows quick change.
Then "Folder" could become it's own section.
Now we only need a ">" to the right of "Description", directly opening the "Edit" dialog, and the whole track popup would have consistent design.
Quote from: Graf Geo on June 09, 2026, 14:03:08"REORDER SECTIONS"
Maybe this way: :)
I like the idea of being able to choose what's displayed. It's also good that you can move it around.
I'll select everything except "Interval," maybe in a different order.
But when I look at the chart, everything above it gets in the way.
You should be able to hide it temporarily. Then there would just be the chart and the map. I drew a button behind the word "Chart."
That lets you hide everything above it.
But when I open the track, everything should be displayed. Then, if I want to take a closer look at the chart, I'll hide everything above it.
Hi,
Since a few versions, I noticed a change in how bike-routes are represented. Locus shows a lot of Streets as "demanding Surface", that are perfectly normal paved streets. I think the interpretation of the OSM flags seems to be off sometimes:
An example:
This is shown as demanding:
15db64c58de2fe559eba571f8a28103f29f81fcdbbf3462b3ce09fbab416218e.jpgd45ce6400ed12cc0fd03fbdf18ebdf01485b55bf721ad411ec7459b8e4c13841.jpg
On the other hand the way types and surface are the same between demanding and not demanding parts:
cd00e242882fb9549e560b7a405f4040ea4eb94fb650b485ef083d84e0d4411f.jpg
The OSM Object is https://www.openstreetmap.org/way/16901568 (https://www.openstreetmap.org/way/16901568)
There the way is shown as asphalt *and* grade1 - which means paved. So - at least for me - this does not imply "demanding".
For those interested, this is the streetview of the Road: https://maps.app.goo.gl/9LpCCxVVD4yCGRWd6
So I think there should be some tuning regarding the classification and/or representation as "demanding", because now it is more often misleading than helpful in route planning.
Greetings, Ulrich
Quote from: Ulrich Kiermayr on June 09, 2026, 23:18:22Hi,
Since a few versions, I noticed a change in how bike-routes are represented. Locus shows a lot of Streets as "demanding Surface", that are perfectly normal paved streets. I think the interpretation of the OSM flags seems to be off sometimes:
An example:
This is shown as demanding:
15db64c58de2fe559eba571f8a28103f29f81fcdbbf3462b3ce09fbab416218e.jpgd45ce6400ed12cc0fd03fbdf18ebdf01485b55bf721ad411ec7459b8e4c13841.jpg
On the other hand the way types and surface are the same between demanding and not demanding parts:
cd00e242882fb9549e560b7a405f4040ea4eb94fb650b485ef083d84e0d4411f.jpg
The OSM Object is https://www.openstreetmap.org/way/16901568 (https://www.openstreetmap.org/way/16901568)
There the way is shown as asphalt *and* grade1 - which means paved. So - at least for me - this does not imply "demanding".
For those interested, this is the streetview of the Road: https://maps.app.goo.gl/9LpCCxVVD4yCGRWd6
So I think there should be some tuning regarding the classification and/or representation as "demanding", because now it is more often misleading than helpful in route planning.
Greetings, Ulrich
The route is marked as poor in OSM. Potholes, cracks, etc. Bad for road bikes. You should adjust the OSM data if it's better in your local area.
Quote from: freischneider on June 09, 2026, 17:21:49Quote from: Graf Geo on June 09, 2026, 14:03:08"REORDER SECTIONS"
Maybe this way: :)
I like the idea of being able to choose what's displayed. It's also good that you can move it around.
I'll select everything except "Interval," maybe in a different order.
But when I look at the chart, everything above it gets in the way.
You should be able to hide it temporarily. Then there would just be the chart and the map. I drew a button behind the word "Chart."
That lets you hide everything above it.
But when I open the track, everything should be displayed. Then, if I want to take a closer look at the chart, I'll hide everything above it.
I think that's too specific - much better would be to be able to toggle/move all sections (also statistics) to define your favorite way the popup appears, as I describe in my post above. Including the line indicating what to show immediately and what on scroll-up.
One can dream, right? 8)
Quote from: freischneider on June 10, 2026, 06:18:54The route is marked as poor in OSM. Potholes, cracks, etc. Bad for road bikes. You should adjust the OSM data if it's better in your local area.
If you are referring to the smoothness=intermediate tag - I think to classify this as "demanding" still is a bit to harsh. Since there is only one category of bad road in locus, it is s bit broad to classify this the same way as some really unrideable roads.
All the smoothness=intermediate I found in my neighborhood do not qualify as demanding. The OSM description also just says "may cause trouble for racing bikes." This is a Konjunktiv and only refers to a small subset of bikes.
So in my opinion the cutoff is better suited at smoothness=bad.
Greetings, Ulrich
Quote from: Ulrich Kiermayr on June 10, 2026, 09:54:43Quote from: freischneider on June 10, 2026, 06:18:54The route is marked as poor in OSM. Potholes, cracks, etc. Bad for road bikes. You should adjust the OSM data if it's better in your local area.
If you are referring to the smoothness=intermediate tag - I think to classify this as "demanding" still is a bit to harsh. Since there is only one category of bad road in locus, it is s bit broad to classify this the same way as some really unrideable roads.
All the smoothness=intermediate I found in my neighborhood do not qualify as demanding. The OSM description also just says "may cause trouble for racing bikes." This is a Konjunktiv and only refers to a small subset of bikes.
So in my opinion the cutoff is better suited at smoothness=bad.
Greetings, Ulrich
It's not impassable. It is passable and has been graded. But with a warning—and that's important. If you ride your road bike into a pothole like that, you'll crash. That's why the warning is important.
Quote from: freischneider on June 10, 2026, 11:18:35It's not impassable. It is passable and has been graded. But with a warning—and that's important. If you ride your road bike into a pothole like that, you'll crash. That's why the warning is important.
I think it is a problem that there is only one fixed cutoff for all classes of "bad" surface. In my experience riding a rodadbike the smoothness=intermediate roads that I know do not pose a problem for road biking (except in a race maybe).
So in light of the discussion it would be useful if eiter
- More than one class of "bad" surface to get a better feeling of what to expect without checking every section, what exactly is meant by "demanding"
- make the cutoff configurable to get some liberty to what is accepatable as surface condition and what should generate a warning to accomodate different expectations/material
Greetings, Ulrich
Quote from: Ulrich Kiermayr on June 10, 2026, 12:05:59Quote from: freischneider on June 10, 2026, 11:18:35It's not impassable. It is passable and has been graded. But with a warning—and that's important. If you ride your road bike into a pothole like that, you'll crash. That's why the warning is important.
I think it is a problem that there is only one fixed cutoff for all classes of "bad" surface. In my experience riding a rodadbike the smoothness=intermediate roads that I know do not pose a problem for road biking (except in a race maybe).
So in light of the discussion it would be useful if eiter
- More than one class of "bad" surface to get a better feeling of what to expect without checking every section, what exactly is meant by "demanding"
- make the cutoff configurable to get some liberty to what is accepatable as surface condition and what should generate a warning to accomodate different expectations/material
Greetings, Ulrich
I think it would be most sensible if you submitted a suggestion to the helpdesk. Discussing this here is the wrong place.
Hi guys,
I had a shorter hike + team meeting, so this week > nothing extra new. At least some answers ...
@Tapio left search screens > can't simulate it, sorry. Back event firstly closes the keyboard and on second event, it correctly do a "back step". Does anyone else have a problem here?
@WildWortWechsel problem with bottom bar > thanks. Give a try to next app version (tomorrow or next week). We've created an improved system for auto-resize of top bar based on the length of the text, so it should help here.
@Graf Geo slope coloring > in all charts, yes intent. Useless? I found it pretty useful to see for example speed on bike with colored slopes.
legend > next to track style in the track detail (if coloring is enabled)
@Gerhard57 missing Y value > hmm, and no gap (missing data) in this place? I'll be looking at it.
@Ulrich Kiermayr not working "My location" > thanks, got it
"demanding surface" > If possible, yes, post it please on the help desk as an idea. This is more on my colleague
@Radim V and it will be a lot easier to discuss it with him in a single place there.
@slarti76 100m range > no serious reason. Improved, give it a try in the next version.
Reordering of track screen content:
thanks for the interesting ideas. As I see, everybody has a huge list of ideas and it leads me to stay with minimal customisations for now. So, do not expect too much from it for now. Thanks for understanding.
Anyway, I'll read your posts more carefully, do some summary and definitely think about it.
Version 4.34.1.4 (12.6.2026) - mainly bug-fixes.
- fix: occasional crash at app start while the initial loading screen is visible
- fix: geocaching waypoint projection now starts from the waypoint's own coordinates
- fix: selecting a result in the offline POI search now correctly shows it on the map
- fix: handling of incorrect track when switching over them directly on the map screen
- fix: not working "My location" location in Route planner itinerary
- fix: thin seams no longer show between map tiles on dark maps
- fix: crash when selecting a vector map theme with no style layers
- fix: crash when pressing back on a web page that failed to open
- fix: crash when opening My live location while a live-tracking session was running
- chg: reduce minimum X-axis distance width to 100m in track charts
- chg: local map server now works with the Locus web portal over HTTPS (Private Network Access preflight supported)
Thanks for the update.
When I zoom in with two fingers or move the chart in the chart overview, Locus crashes.
Quote from: Ulrich Kiermayr on June 10, 2026, 09:54:43Quote from: freischneider on June 10, 2026, 06:18:54The route is marked as poor in OSM. Potholes, cracks, etc. Bad for road bikes. You should adjust the OSM data if it's better in your local area.
If you are referring to the smoothness=intermediate tag - I think to classify this as "demanding" still is a bit to harsh. Since there is only one category of bad road in locus, it is s bit broad to classify this the same way as some really unrideable roads.
All the smoothness=intermediate I found in my neighborhood do not qualify as demanding. The OSM description also just says "may cause trouble for racing bikes." This is a Konjunktiv and only refers to a small subset of bikes.
So in my opinion the cutoff is better suited at smoothness=bad.
Greetings, Ulrich
Hello Ulrich. I checked the osm manual for mappers. (I always do, when making any kind of osm related configuration). Indeed smoothness=intermediate as seen in the manual (https://wiki.openstreetmap.org/wiki/Key:smoothness) is not what I enjoy when riding a road bike. Anyway I have seen more than one report of surface warnings being too strict, so I have changed "intermediate" to ok for road bikes and "bad" to ok for gravel bikes. These are opinionated choices and I have no problem with it, in this particular case. But what I see on the street view is not "intermediate". Inaccurate mapping is also an issue here. Regarding more than one class for warnings - this is already possible (router side, not user side). I have just not yet configured the yellow, orange and red levels. These levels are treated in slightly different way, e.g. yellow warnings disappear first on the map, red are more sticky. The change will be deployed to online router tomorrow, offline with new app version.
Quote from: Radim V on June 15, 2026, 17:27:04Hello Ulrich. I checked the osm manual for mappers. (I always do, when making any kind of osm related configuration). Indeed smoothness=intermediate as seen in the manual (https://wiki.openstreetmap.org/wiki/Key:smoothness) is not what I enjoy when riding a road bike. Anyway I have seen more than one report of surface warnings being too strict, so I have changed "intermediate" to ok for road bikes and "bad" to ok for gravel bikes. These are opinionated choices and I have no problem with it, in this particular case. But what I see on the street view is not "intermediate". Inaccurate mapping is also an issue here. Regarding more than one class for warnings - this is already possible (router side, not user side). I have just not yet configured the yellow, orange and red levels. These levels are treated in slightly different way, e.g. yellow warnings disappear first on the map, red are more sticky. The change will be deployed to online router tomorrow, offline with new app version.
I agree. It is also kind of individual, what is still considered as 'ok'.
Your change sounds reasonable (for me), I'll check and can give feedback :-)
Thanks and lG Ulrich
Version 4.34.1.4.
I have a preset profile for navigation – for example, moving the map cursor down. If I view the route details during navigation and then go back, the cursor no longer moves down but stays in the center of the screen.
Version 4.34.1.5 (19.6.2026)
- add: (SILVER) pinch-zoom and pan the chart right on the track detail screen — no need to open the full chart first
- add: (SILVER) zooming the track-detail chart now highlights the matching section directly on the map
- add: pin the chart on the track detail screen to keep it only visible item + map
- add: (SILVER) GPS accuracy can now be shown as a track chart variable
- add: reorder the sections of the track detail screen (chart, description, waypoints and more) to your preference
- add: optionally stop guidance and navigation automatically after you stop moving, to save battery
- fix: crash when pinch-zooming a track chart at the deepest zoom level
- chg: (SILVER) Geocaching Live Map now works on the Android Auto map and updates as you move
- chg: smoother panning and zooming of track charts on long tracks
- chg: more accurate calorie estimates — terrain (uphill/downhill) now affects the estimate, and reported calories represent the total energy burned during the activity
- chg: per-activity calorie values refreshed to the 2024 Compendium of Physical Activities (walking, running, cycling, skiing and more)
- fix: more accurate calorie estimates when walking, hiking or running uphill
- fix: more accurate heart-rate-based calorie estimates for female user profiles
- fix: missing photo overview when picking coordinates on the map in "Image map calibration"
- fix: crash when entering an invalid value in a BRouter routing-profile parameter
- fix: incorrect visible URL in the track detail
- fix: points without a custom icon now show their folder or default icon in lists instead of a plain dot
- fix: (SILVER) online map overlays such as IGN now load reliably at app start instead of showing a "map is not ready" warning
Some really great improvements! 👍👍
One of the best features is the option to fix and view the elevation chart separately and zoom in on it directly. At last. 🙂
And now you can also move attachments (media) in the 'Reorder Sections' menu. Very good!
I'd also like to be able to sort the charts freely in the overview or hide individual ones, but perhaps that's still to come.
Have a lovely weekend! 🌞
regards the nice improvement "track-detail chart now highlights the matching section directly on the map", although not specific to this beta release, would it be worthwhile to disable map rotation and auto-centering, while showing the map based on the chart? I find it confusing when I've just saved a track, but the map preview at top is continually rotating, and when I tap the chart & the map is panned, it will revert to GPS position after auto-centering timeout.
Quote from: Graf Geo on June 19, 2026, 23:16:05One of the best features is the option to fix and view the elevation chart separately and zoom in on it directly. At last. 🙂
When pinch-zoomed, it shows some weird parallel track. As if it wants to highlight the zoom area, but distorted. Anyone? The orange-white line.
@Menion, to unify behaviour and make geotagged photos awesome, you could move the map, just like a click on the graph - if we click a geotagged photo. And if geoposition access is an issue, maybe same file time approach as the selection of photos itself: use closest track timestamp and center track there.
And picture viewer then would be started by long click.
Quote from: Tapio on June 20, 2026, 16:57:10When pinch-zoomed, it shows some weird parallel track. As if it wants to highlight the zoom area, but distorted. Anyone? The orange-white line.
This marks the section that has been enlarged on the elevation profile. Generally speaking, this is fine, but on sections with sharp bends or tight curves, the orange-and-white markings occasionally overlap the route in an unsightly manner. A bit of fine-tuning might be needed here.
Is it me, or did overlay maps stop working. No matter which overlay I select, they all stopped working. I either get a message "cannot load map" or no message at all, just no overlay.
I used the m*, G* or M* traffic overlays occasionally.
Quote from: Blihi on June 22, 2026, 20:43:44Is it me, or did overlay maps stop working. No matter which overlay I select, they all stopped working. I either get a message "cannot load map" or no message at all, just no overlay.
I used the m*, G* or M* traffic overlays occasionally.
I have a (custom) overlay for OpenRailwayMaps. This still works fine.
lG uk
Could you share it via private message? I'd be interested to try and see what may be going on. It can of course be that all external providers started blocking my requests :)
Quote from: Blihi on June 23, 2026, 09:21:18Could you share it via private message? I'd be interested to try and see what may be going on. It can of course be that all external providers started blocking my requests :)
Here it is: openrailwaymap.provider.xml
Greetings, Ulrich
Thanks! I can confirm the problem is not with Locus, but apparently with the external provider that seems to have removed the specific layer from the ZXY tile server.
Hi guys,
do you have so hot out there as well? Tomorrow almost 40°C, uff ...
And next to it, new version: 4.35 (https://forum.locusmap.eu/index.php?topic=9662.0) ;D.
It will again take some time till Google verify it. Meanwhile, there will be enough feedback for a bug-fix version, I'm sure ;).
Have a nice weekend, and thanks for your very valuable feedback. Hope you will like the changes regarding track & charts and a few more...