Messages

Dito meine Erfahrung. Das Huawei Mate 20 X kann 30 Satelliten sehen und 4m Genauigkeit berichten - so viel tut das nicht zur Sache. Am Ende gibt es immer zackige Routen rund um den eigentlichen Weg. Die Entfernungs-Statistiken zwischen 2 Geräten weichen drastischer ab, als man meint. Hat das eine 20.4km angezeigt, sieht man am anderen vllt. 19.6 - wäre schön, wenn wir eines Tages einen Dienst (Plugin?) hätten, der alle Trackpunkte an den nahesten Weg ausrichtet/korrigiert.
Ist immer seltsam wenn Dienste Geokoordinaten mit massiv mehr als 6 Stellen hinterm Komma angeben. Die 6. Stelle ist schon nur noch ca. 1-2m, mal ganz grob.

Man kocht eben bei GPS nur mit Wasser. Alle paar Sekunden mal eine grobe Position.

Lovely one, thank you.

- Control point alert via intent is working.

- New navigation icon and panel option could go to the navigation options at some point.

- If no navigation icon is displayed, upper panel should use full width.

- Small nav icon is a few pixels higher than the statistic panel.

- Screenshot. Can't we get rid of the top left nav arrow? It is there in any case. Arrow on track plus voice is enough for me. When hiking, 2nd next command is uninteresting.

- It is not possible to show the embedded waypoints screen, endless loading, screenshot.

Trackpoint screen, jump buttons.

Currently:
Short tap middle buttons: +/- 1 tp
Short tap outer buttons: +/- 1 waypoint or begin/end
Long tap middle buttons: +/- 10 tp (automove)
Long tap outer buttons: +/- 1 waypoint (automove) or begin/end

Tiny Suggestion:
Long tap outer buttons: goto begin/end.

I think the automatic skipping to next WP is rather redundant and not expected here. Being able to quickly jump to the ends is more useful.

Despite the notification, it still works as a full version..., so we can lean back 😊

Fully agree. There already is such an option for guidance, but Menion did not implement it for navigation.

And guys, I'd like to remind you about my idea to optionally hide the big navigation icon at all.
https://help.locusmap.eu/topic/option-to-not-show-the-top-left-navigation-arrow-boxes

Menion are you still planning to make changes on point and trackscreen? Especially in pointscreen, the relevant info (for me) is placed at the bottom (date/time).

Cabrio, the track details screen when coming from the track manager is technically something different. More of a static window like it was before, but stylistically now like the new track screen you refer to. Menion said it's limited, don't expect changes there.

Just in case you missed it: you know if, in track manager, when you tap on the map preview it directly goes to map view and shows the track?

New 012 version instantly crashes (often) when:

- tap a track (planned one, from route planner)
- New track screen is open
- Bottom left icon (to point screen)
- Crash
-

route name > only recorded. Imported or planned has different names. Also, in the recent version, you may modify the pattern for the name of the recorded track, so ...

There's the timestamp there {t} - I was wondering - will you add more variables? Especially (next) city name is interesting.

I would love not to see "Best Interval".

Oh yes. Same, also the waypoints symbols aren't useful for me. Maybe at a later stage we can define which elements are shown, while the rest (their fullscreen windows) can be accessed via a submenu.

[Serious problem.]

@Menion I experienced the same as Andrew! Recording initiated by an intent. I noticed, it wasnt stopped by Tasker, but should have. And so I wanted to stop it manually. Not possible, as Andrew wrote. I stopped Locus, it comes up with that message "recording running", and I think I just dumped the recording with that recycle bin icon, which made the recording stop. Serious problem.

Looks good.
Menion, you know there's some people asking for customization of the new track screen, are you planning to do so, will it be possible at all?
For me, changing of order, hiding sections comes to mind. And initial visibility (vs. fully dragged out). Eg, one may only interested in seeing the tracks name and stats in the initial view, but not the elev. profile. You could allow to define # of elements which are in the visible area initially.

Man kann sich ein G Account für gemeinsamme Apps anlegen zB. Locus. und einen für sich persönlich. Dann geht das auch mit den Spielständen.

Das wäre auch mein Ansatz gewesen. Ich habe mit meiner Frau so einen Account für fas gemeinsame Tablet und auch Google-TV (Chromecast). Familienbibliothek hätte ich für Locus auch gutgefunden. Aber Asamm hat eben anders priorisiert. Silver ist ein großes Angebot, das Gold im Regelfall unnötig macht.

Als PC-Gamerveteran fühle ich mich dank Paras Kommentar mit meinen 49 plötzlich wieder jung 😅

Viel Erfolg, Saturo, im Detail kann ich hier leider nicht helfen.

Button has an ugly cut shadow. Bottom bar is always on, Fullscreen mode, res. 1080x2244

[@tapio]

@tapio
hmm, it may not be connected to dark mode. It looks like that app is unable to pick the correct map for the preview so use the blank map. And because you use dark mode, it is black, nothing more.

Ah no big deal... may be related to my use of an OAM map. I don't use Lomaps because MFv3.

Some thoughts on trackpoint/track view.

1. Stay in view... When I am in new trackpoint screen and tap the track at some position, I wish it would stay in trackpoint screen and display the selected point.
2. Intuitive toggle button needed, toggle between track screen/trackpoint screen.
3. In trackpoint screen I think there's a lot wasted space. The from start/to end information is important, but not initially visible. I hope for some user config/reorder possibility.
If we can intuitively toggle, there may be no need for the track/folder info in the trackpoint screen.
4.In Trackpoint screen, the statistics section with "To start/to end". If navigating a route, there would be the right place to display track distance and todo elev, relative from current position.

As for the track screen AND if I am navigating the track... I wish for more nav related information, like

distance from current position until selection
distance to end/from start (cur. selection)
pos elev todo... to end/from start (cur. selection)