- Welcome to Locus Map - forum.
Locus Map - forum
Recent posts
#1
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Ulrich Kiermayr - Yesterday at 22:08:41Hi,
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.
You cannot view this attachment.
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.
You cannot view this attachment.
#2
Free chat / Volunteer for a test using a G...
Last post by 0709 - Yesterday at 18:59:35Looking for Garmin Edge bike GPS owners to test tcx and fit course file imports.
According to the (old) tcx standard the Name should contain 1 to max 10 characters.
I did read a comment that the current Edge models accept more than 10 characters.
I suspect anwyay that the more recent Edge models will only support fit files.
Find the necessary test files in the zip.
See the tcx and fit files to test. (Locus map converted the .tcx to .fit)
Can someone pse check whether the tcx and/or the fit file complies or not?
According to the (old) tcx standard the Name should contain 1 to max 10 characters.
I did read a comment that the current Edge models accept more than 10 characters.
I suspect anwyay that the more recent Edge models will only support fit files.
Find the necessary test files in the zip.
See the tcx and fit files to test. (Locus map converted the .tcx to .fit)
Can someone pse check whether the tcx and/or the fit file complies or not?
#3
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Blihi - Yesterday at 16:17:47Quote 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.
#4
[DE] - deutschsprachiger Forumsbereich / Zahlungsmethode für das jährli...
Last post by Joska - Yesterday at 13:24:19Moin
Gestern bin ich aus Italien zurück nach Deutschland gereist. Heute bekomme ich die Nachricht, dass das jährliche Locus-Abo nicht bezahlt wurde, weil in Play Store jede Zahlungsmethode abgelehnt wurde.
(An anderen Stellen funktionieren die Karten)
In Android Auto und auf den Phone meiner Frau (wir nutzen hier ein genetischens Google Konto) wird Locus jetzt als Nicht-Premium-Version gestartet, auf meinem immer noch "korrekt" als Premium.
Laut KI gibt es derartige temporären Kartenstörungen im Play Store bei Wechsel über Landesgrenzen, was ich aber nicht verstehe, ist das unterschiedliche Verhalten auf den drei obigen Geräten, zumal Android Auto mit meinen Phone gekoppelt ist.
Man mir jemand die Logik erklären?
Gestern bin ich aus Italien zurück nach Deutschland gereist. Heute bekomme ich die Nachricht, dass das jährliche Locus-Abo nicht bezahlt wurde, weil in Play Store jede Zahlungsmethode abgelehnt wurde.
(An anderen Stellen funktionieren die Karten)
In Android Auto und auf den Phone meiner Frau (wir nutzen hier ein genetischens Google Konto) wird Locus jetzt als Nicht-Premium-Version gestartet, auf meinem immer noch "korrekt" als Premium.
Laut KI gibt es derartige temporären Kartenstörungen im Play Store bei Wechsel über Landesgrenzen, was ich aber nicht verstehe, ist das unterschiedliche Verhalten auf den drei obigen Geräten, zumal Android Auto mit meinen Phone gekoppelt ist.
Man mir jemand die Logik erklären?
#5
Locus Map / Re: [APP] - version 4.33.+ ( 0...
Last post by michaelbechtold - Yesterday at 10:05:31Two 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
@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
#6
[CZ&SK] - diskuze o Locusu / Opět problém
Last post by Joska 000 - Yesterday at 09:05:53Tak já nvm. Nadcházející svátky a je potřeba vyrazit. Zapnu aplikaci, načítá a na 60% šlus. Sakra co se děje? A tak si vzpomínám, že jsem omylem udělal aktualizaci, kterou mám zakázanou. Vezmu náhradní foun, porovnám a tam OK. Takže odinstal, stáhnout 4.32.4 , nainstalovat a problém je vyřešen. No příště si musím dát pozor co při aktualizacích potvrzuji.
#7
Troubles & Questions / add moving average speed to au...
Last post by newty - Yesterday at 08:53:49Hi,
I would like to bring up a feature request that I have already submitted to support several times, but without any progress so far.
It concerns the audio coach in Locus Map.
Currently, the voice announcements can include average speed, average pace, and other metrics, but one essential value is missing: moving average speed (i.e. excluding stopped time).
Just to be clear:
* I am not referring to overall average speed,
* nor to average pace,
* nor to any kind of "track average",
* but specifically to moving average speed.
This value is already calculated and shown in the post-activity statistics, so it clearly exists within the app.
The issue is that it cannot be used in the audio coach, which makes the voice feedback much less useful in real conditions, especially for activities like hiking where pauses are frequent.
It would be extremely helpful to have the option to include moving average speed in the audio announcements.
For comparison, other apps like OruxMaps already provide this feature, which shows that it is both feasible and useful.
Is this something that could be considered for future updates?
Thanks in advance for your feedback.
I would like to bring up a feature request that I have already submitted to support several times, but without any progress so far.
It concerns the audio coach in Locus Map.
Currently, the voice announcements can include average speed, average pace, and other metrics, but one essential value is missing: moving average speed (i.e. excluding stopped time).
Just to be clear:
* I am not referring to overall average speed,
* nor to average pace,
* nor to any kind of "track average",
* but specifically to moving average speed.
This value is already calculated and shown in the post-activity statistics, so it clearly exists within the app.
The issue is that it cannot be used in the audio coach, which makes the voice feedback much less useful in real conditions, especially for activities like hiking where pauses are frequent.
It would be extremely helpful to have the option to include moving average speed in the audio announcements.
For comparison, other apps like OruxMaps already provide this feature, which shows that it is both feasible and useful.
Is this something that could be considered for future updates?
Thanks in advance for your feedback.
#8
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Erelen - Yesterday at 04:37:594.33.0.8 - startup is ok.
#9
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Andrew Heard - Yesterday at 04:15:544.33.0.8_1211_beta: startup & Store OK for me; no other testing done.
#10
[DE] - deutschsprachiger Forumsbereich / Re: Bekomme die neue Version (...
Last post by baluster - April 03, 2026, 20:53:27... vor wenigen Tagen gab es erst das Update auf Android 16, auf A15 gab es die gleichen Schwierigkeiten.