Messages

Something I noticed again recently, but I think it's been like that for a while:
On my tab (Galaxy Tab S5e), Locus shows the track and point details as panel on the right in landscape, which is good. In portrait, however, tracks are shown on the bottom (good!), but points on the right, taking 50% of the screen (with only a few lines of text and lots of white space) - really bad!
Is that intentional or a bug?

I'd like to see the phone accelerometer used for motion/ stopped detection.

Wasn't that tried, and it turned out it couldn't be done reliably due to Google?

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.

Not sure if that was reported already, but since a while*, the "Recording" notification is not updated anymore. Ever. Always shows something like "1 point". Reproducible with Galaxy S21 and XCover Pro.
Perhaps related with me always starting recording with intents or Locus Tasker app.
Am I the only one?

* Didn't report it earlier because it doesn't really bother me, don't really need the info displayed there, but now I once or twice thought "sh**, it's not recoeding", when it actually was...

Did someone also notice that the "Supplementary Map Download" functionality is basically broken, at least starting with Android 13? Even though I'm using the sideloaded AFA build.
The problem is that Locus seems to always store downloaded maps in its Android/data/menion.android.locus directory, but when I choose "Supplementary Download", I cannot choose that directory (Android/data is shown empty). I can choose Android/media/menion.android.locus, but I don't get the map there. Even Total Commander with AFA is not able to read the downloaded map file within Android/data, so I can't move it manually.

Menion, could the file chooser be changed such that it can also show Locus' internal directory?

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.

Hi Menione. Backup files sent to the cloud are too big. The last one has over 0.5 GB. Most of the space is occupied by the track.db (800 MB) file. It is unnecessary to back up routes and points for the Gold version because they are stored in the Webplaner. Would it be too difficult to miss these files for Gold users from autonatic backups?

I strongly oppose leaving out the *.db by default. As an option, ok, but in my view, this is an absolute necessity - you can never rely on online storage service, I want to be able to restore my database even when e.g. Locus Web is down.

UI - I think SET/Recalculate position should be swapped. Typically, bottom right has OK (what you could say "Set" is, and it was there before). In my quick workflow I almost end up recalculating all when I just wanted to change routing profile.

My thought precisely. "Special operation" in the lower right is a recipe for disaster

Yes, it should be by its "Created time" parameter. And well, you know. Waypoints in the app are painful and need a new system for handling them. Old problem ...

I could start again about my hope to at some point being able to create waypoints in the track editor, so they have a datetime. It's one of my biggest annoyances that waypoints created during recording have a timestamp, but when I forget them and want to add them later on, they won't have a timestamp that fits to the track.
Not all waypoints are POIs, like "hut", but things like "put on snowshoes", "removed crampons", etc. For those things, times are of relevance, especially if you use the same trail several times.
Well, I'll keep hoping...

@Menion, waypoints embedded in tracks, can you make them display them in alphabetical order? Currently it's by distance, which is not always useful.

Aren't they sorted by datetime when created? Anyway, I agree it's not always ideal, so best would probably be custom sort order button...

Today Auto Stop activated. Looks quite good.

I'm wondering, what's the difference?

Yeah, that should probably be re-worded to make clear that first setting is about "device movement" and second about received GPS positions. Well, or vice versa

The time of splitted tracks > can't confirm. Even in the code - the app assigns the "Creation time" of the original track to both two newly generated tracks. Please check it again, thanks.

But that's exactly what I'm saying: Splitted tracks have the same Creation time. So they can't be sorted-by-creation-time anymore, even though one of those tracks clearly "happened" earlier in time. You're just lucky if the titles are alphabetically in the correct order.
What I'm asking for is sort-by-start-time, sorting by the date/time of the first timestamped point in the track.

Were the Android intents removed in 4.12? Didn't see anything in the changelog, perhaps overlooked it. Anyway, my old Tasker tasks didn't work anymore, using Locus Tasker plugin now instead. I assume that is the recommended solution now?!

That would be a desaster. I cannot confirm, what exactly? My 4.12.1 auto recorded yesterday and Tasker added a waypoint to the recording. Just fine.

Code Select Expand

Action: com.asamm.locus.ACTION_TASK
Cat: None
Extra: tasks: { track_record  : { action: "add_wpt", name: "Pause: %pause_minutes minutes", auto_save: true } }
Package: menion.android.locus
Target: Broadcast Receiver


For me, starting/stopping recording didn't work anymore. But I didn't investigate further, just replaced the calls with Tasker plugin, which worked, so I was happy. That's why I'm asking (and also because I have a faint remembrance that Menion at some point mentioned that intents were outdated and to-be-removed at some point, but I could be wrong).