Messages

[@slarti76]

@slarti76
"Dashboard button" > are you really using the "Dashboard" item? Because there exists also a "Dashboard toggle" button that behaves exactly as you describe. Also, long-click is always a "hidden feature", so I cannot add some critical functionality (like display of dialog) under it.

Some misunderstanding here. I was comparing with the Dashboard functionality. I am aware of the "Dashboard Toggle" and basically would like the same for "Map Overlay". I get it that the long-click is kind of a workaround, but wouldn't it be possible to add "Map Overlay Toggle" button, same as "Dashboard Toggle" button?

Multiple overlays > not planned, sorry.

Fair enough. I kinda expected this to not be possible...

Custom WMS > a little hidden. Map manager > WMS/WMTS tab > "+" > Add from library > "+" > and here you go ... this does not make sense right? Hmm ...

Yeah, that works. Not intuitive, but I can live with that. However, try to add this link:
https://wms.geo.admin.ch/?REQUEST=GetCapabilities&SERVICE=WMS&VERSION=1.3.0
You get a huuuge list (non-alphabetic, unfortunately), without a way to search. Impossible to find what you're looking for. I tried to add a direct link I found in the file:
https://wms.geo.admin.ch/?request=GetMetadata&layer=ch.bazl.einschraenkungen-drohnen
But this still displays the whole list. Is that a bug? Otherwise, any chance to add a search here?

[@slarti76]

@slarti76
OruxMaps ... funny comment @Tapio  . Unfortunately, I believe there will still be more than slarti .

This is a general topic where all sorts of problems and features are discussed. Most of us use only a minority of what Locus Map can do, but -> when it's implemented and it does not work, it should be fixed (or removed for good), even if used only by a single person.

Back to problem > fix with the "map name" was only aesthetic. I'm also testing one Oruxmap and it works without a problem. Do you have this issue with all such maps?

Turns out this was a totally different problem, nothing with OruxMaps: I was still using the AFA build, and it affected all maps situated in folders other than Android/media or Android/data. Now that the Android/media way is working well, I switched to non-AFA and moved all my maps, and the problem doesn´t appear anymore.
As AFA is not an official thing, you can ignore this problem, I think.

Out of curiosity - why do you use these kinds of maps instead of OAM/Lomaps?

As I wrote above, we have a friend who provides these. And OAM/LoMaps is really not the right comparison, as OruxMaps are bitmap, not vector. And when it's about external bitmap maps, I think there's no alternative to Orux, otherwise Locus only supports its own format, which I have never seen anywhere else. So Orux may be a competition, but offers a format that is at least somewhat known, whereas Locus-bitmap maps are not. I may be wrong there.

New function "Notification on invalid pause and pending recording states"

Where do I find that? I seem to be overlooking the right pointer. Searching in settings for "pause", "recording", or "notification" to no avail.

Which reminds me of something else:
Would it be possible to make the Locus version easier accessible? I first looked for this new function before I realized I didn't have the newest beta. Right now you need 3 clicks plus scrolling to get to the app info screen. At least the version could easily be shown in the bottom bar of the main menu (where it now says e.g. "LOCUS MAP GOLD"). And then perhaps make that bar clickable to get directly to App Info.

[HELP!]

HELP!

I decided to move my main directory to Android/media - it first looked good, then I got the sad droid picture with "Whoops! dDS, code: 12521", and now I can't start Locus anymore. The same code appears all the time, after a toast "Restoring unfinished transfer of the main directory".

What can I do???

I updated to newest beta, just in case.

Ok, I solved the problem by connecting the phone to PC via USB and finishing the copying manually. After that it worked again flawlessly.
There were actually uncopied files, but no indication what kept Locus from copying them itself.

Anyway, I'm a computer expert who knows how to do this, but for others this would be a very bad outcome: No clear indication what happened, no remedy, Locus just broken. I assume re-install could help, as then Android would delete remaining files in Android/data, but, well, that would be data loss.

Menion, any idea what the error message means, internally? A more descriptive message would already go a long way, perhaps with the tip to manually copy with computer in case this repeatedly fails.

Anyway, no need to interrupt your Easter holiday for me
Enjoy your (long) weekend, everyone!

You can still do this. Simply start the route planner directly instead of "Navigate to", then you can select the starting point on the map.

Use plan route by instead of navigating.

Thx. Not quite the same, because the "Navigate" button becomes the "Save" button and now one needs the detour through the menu. But better than adding and removing points.

Still, as written before, best would be to just have "Delete location" on the 3-dot-menu when "Waiting for GPS" is shown...

Little weird observation in my recent holidays:
I split a track A into A1 and A2. Then both tracks had the same creation date/time (I think we discussed this a while ago, before that both parts got the current DT as new creation dates). Now when I sort the folder by "Created", it shows

• A1
• A2

- correct!

But when I reverse sorting, it still shows

• A1
• A2

- not really correct, as the second part of the original track is surely after the first part and thus should be shown before in the reversed list.
I assume, as both tracks have exactly the same created date/time, Locus then reverts to alphabetic sorting as "tie-breaker", which keeps A1 before A2.

Proposal:
As we agree that it's not helpful to set the Created DT of split tracks to the current DT, why not set the DT of the second part to its first trackpoint?

I do see the complexity in combining all searches together, and I can live with having to select different search "means". But one major bother, that should be not too difficult to change is this:
Everytime the search scope is changed, there's a new, empty input field. Why not prefill with the search term already entered in another search? All the time I start typing into a search field before realizing I have the wrong search - then I change it and have to start from scratch (unless I thought of that and copy-pasted the term, which of course is also a bother).

PS: I just realized that this works between internal point and track search, but that's the only place I found.

What about then at least adding support for PlusCode? That can be copied from Maps with one tap and surely be parsed by Locus search without ambiguity?!

@slarti76 - thanks, hadn't used +codes before. Still slower (many more taps) than direct "share" of a point from my testing:

• drag POI details down a few times
• tap on "See all"
• tap on +code (very little visual feedback BTW)
• switch back to LM4
• open Search (maybe side panel button)
• paste clipboard (maybe more steps here)

Yeah, agreed, but
a) if we don't have another always-working solution,
b) surely no problem with parsing (well-defined as far as I understand)
c) at least last two steps could be improved if Locus adds a PlusCode support by automatically inserting clipboard content in search field (if it parses as PlusCode).
Heck, Locus could parse the clipboard when opening the search and automatically switch to PlusCode if it parses.

Honestly, I'm a little diappointed how the missing ability to correctly share positions from Google is waved away here. Menion et al should be aware that this is an ability that is absolutely crucial for "normal" users. OSM is nice and well, but let's face it, GMaps will always be more up-to-date. Rarely anyone relies on OSM POIs alone, so we all search stuff in GMaps all the time and want to easily enter the points in Locus. This is not something to just say "hasn't been working for a while, so what?"...

Hi guys, sharing points from Google Maps does not work for years as I know. Somewhere in 2021 maybe even later, they changed the format and the information app receives can no longer be simply converted to any text or coordinates.

What about then at least adding support for PlusCode? That can be copied from Maps with one tap and surely be parsed by Locus search without ambiguity?!

Hi there, also my 2 cents to the new side panel:
First, like it! Wouldn't mind some more configuration (e.g. rarely using LoPoints, so would rather be able to hide those lines).

What I'm not quite happy with yet is the theme selector: When you change the theme, you still first have to go through the options screen everytime, even though now there's a dedicated button for that. When switching between themes, I rarely also need to change the current selection, so this is a superfluous step.
Also, the "layers" button may be technically correct, but I think most users will be confused and would rather call this "theme settings", so I propose to use a cogwheel icon.

I would like to add Management of Track Waypoints as No. 5.

Yes, please don't forget about this. There's a bunch of improvements needed here, many very basic (it's not even possible to multi-select and delete trackpoints!)

You will also need to improve search. It should work simultaneously in addresses and points.

I completely agree. Locus search is pure usability horror from last century. A proper search is ONE SINGLE TEXT FIELD that simply searches EVERYTHING at once and shows results as they come in.

Making me decide in advance on where I want to search is just wrong on every level imaginable.

Even worse is when I start typing, realize I got the wrong "place" to search in, change it, and the input field is cleared - why's that? Makes no sense and would be easy to fix...

We have of course some plans and things that need to be done, but still ... simple question (that may influence my personal preferences). What is the biggest pain/requirement you mostly have with the app, I should solve during the next cca 3-9 months? I have in mind a few main categories:

1) management of the track waypoints (not surprisingly my favorite
2) improve dashboard (missing items, simplify edit, improve charts, ...)
I would add
3) rotating labels in vector maps (or, rather, make labels non-rotating in relation to the (rotating) map. That's the main area where Locus just looks so much worse than other concurrent map apps - and of course it's not just looks when actually navigating...
4) better overlay handling, e.g. with overlay presets. For example, I have overlays with hike routes, skiing routes, public transportation stops, all are best at different alpha values, changing between them is such a pain that I usually don't use the feature, even though it's quite good in principle.

All locus notifications are active
Permissions for Locus are active except physical activity.
Out of my curiosity, what is "physical activity" in locus for?
Thank you

I think that's for the new (but beta) auto-pause detection.