Re: [APP] - version 4.34.+ ( 05/2026 )

[Menion]

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

[Andrew Heard]

Chart panning when time gaps in the chart now works perfect - thanks!

[hoschilo]

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?

[Tapio]

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.

[Graf Geo]

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

[Graf Geo]

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.

[hoschilo]

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?

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

[WildWortWechsel]

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?

[Joska]

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?