Messages

[@slarti76]

@slarti76
recording problem: try to switch Settings > GPS & sensors > Google services assisted location. You probably have this enabled (default), but it starts to cause a problems on some devices so give it a try and disable it.

Already tried that during the tour, pretty sure it didn't make a difference, but I'll play around with it some more...

[Serious problem with recording:]

Serious problem with recording:

I did some longer tours this weekend, and everytime after a longer break (>5min, I think), Lotus was not recording anymore. Recording mode itself was still on, I didn't pause the recording. I could recover by turning GPS off and on again, which is of course annoying with gloves in the snow.
I first thought I had some setting wrong, but all of these were off:

• Auto-pause
• Record only when moving
• Record when GPS is off
• Notify of (pausend/pending) recording

Dunno in which version that started, I noticed some problems already end of last year, but didn't go on tour for a while, only used Locus for navigation, and it doesn't happen when screen stays on.

However, I can say with conviction it's not a hardware problem: I recently recorded skiing holidays with two different special skiing apps, and both had no problems, screen off, in my pocket, even with 1hr+ lunch breaks.

Anyone have similar experience?

If you also have Android 16, then it's a Samsung problem.
https://forum.locusmap.eu/index.php?topic=9452.0

Thank you, but as I already mentioned in the original post: Multiple other apps with recording functionality have absolutely no problem picking up recording after breaks of even more than an hour. Without fail. While yes, I have S24+ with Android 16, it still must be on Locus side (of course, could be an interaction with specifics of A16, but it's definitely not a Samsung HW bug).

[Serious problem with recording:]

Serious problem with recording:

I did some longer tours this weekend, and everytime after a longer break (>5min, I think), Lotus was not recording anymore. Recording mode itself was still on, I didn't pause the recording. I could recover by turning GPS off and on again, which is of course annoying with gloves in the snow.
I first thought I had some setting wrong, but all of these were off:

• Auto-pause
• Record only when moving
• Record when GPS is off
• Notify of (pausend/pending) recording

Dunno in which version that started, I noticed some problems already end of last year, but didn't go on tour for a while, only used Locus for navigation, and it doesn't happen when screen stays on.

However, I can say with conviction it's not a hardware problem: I recently recorded skiing holidays with two different special skiing apps, and both had no problems, screen off, in my pocket, even with 1hr+ lunch breaks.

Anyone have similar experience?

@Menion: Sorry to bother, but what about my report https://forum.locusmap.eu/index.php?topic=9488.msg80161#msg80161 ? Usually, you mention all open reports in your round-up messages, so I fear you might have overlooked mine? Loosing half of the track when doing an insert/edit is surely a severe problem...

Merry Christmas everyone!

Sorry for bug reporting in the holidays, but this one's severe:
I edited a track, did the following:

• Insert/edit trackpoint
• Remove section
• Insert/edit trackpoint

The last operation instead deleted like half of the track, I'm not 100%, but it was probably same as "Remove all after".

Track and screen recording of what I did can be found here: https://web.tresorit.com/l/UwA4T#NoxPRGDwfym3Key277zm1A (that video contains a "Remove all before" as first operation, but I tried it without again and could reproduce - the first "Insert/edit" however is necessary to reproduce)

I used latest beta, so not urgent, but definitely disconcerting...

Is there any ETA on a new beta? Especially with the fix for the track editor - I'm really backlogged on some track cleaning up.
I know, there's 4.32.0.1, but that has the lower release number, so as I already installed 4.32.0.0, I cannot use that. Please provide a 4.32.0.2 with updated release number, thank you!

@Menion

I been using Locus Map for several years and was completely unaware of the themes. I installed the John Thorn theme and not only does it work but, the details are cleaner.  Thank you, Mark

I also heard about it for first time - it doesn't help that it doesn't show up in store when you search for "theme".

Menion, could you perhaps add a separate category "Map themes" in store?

Anyway, I find it terrible, in a city I mainly see gas stations and parking spots. Looks like it's targeted at car drivers - is that right? Or am I overlooking some configuration ability?

Not sure if that's new, but I'm trying to edit the attached GPX after importing, and whatever I do, Locus crashes. Some operations (Delete all before) crash it already in the editor, all other when closing the editor.
For comparison, I edited another track recorded by Locus itself, that worked fine.

Hi Locus Team!

I just deleted three larger GPX from the folder "Gesamtstrecken". Now there a four Trails. Going one step back in the folder Hierarchie, the amount of files in the folder "Gesamtstrecken" is still seven.

Because the trails are really large, Android did ask me if I want to stop Locus or just wait. I did stop and restarted Locus.

Speaking as a programmer myself, but you can't really expect all internal bookkeeping in a database to be correct if you kill a process while manipulating that database.

No offence meant.

I ignored it maybe twenty times before I stopped Locus.

Best regards, Dieter

Fair enough, I apologize. It sounded like the delete took a little longer, Android complained a little eagerly and you killed the process immediately, which would be, well, a little quick.

Hi Locus Team!

I just deleted three larger GPX from the folder "Gesamtstrecken". Now there a four Trails. Going one step back in the folder Hierarchie, the amount of files in the folder "Gesamtstrecken" is still seven.

Because the trails are really large, Android did ask me if I want to stop Locus or just wait. I did stop and restarted Locus.

Speaking as a programmer myself, but you can't really expect all internal bookkeeping in a database to be correct if you kill a process while manipulating that database.

No offence meant.

[Beta version 4.31.3.11]

Beta version 4.31.3.11 just uploaded to Google Drive.

Sorry it took so long. We had to finish some fine-tuning.

Changelog:
 - fix: layout in Track editor

Only quick test, but seems to be working again 

One more thing:
I already brought this up a while ago (don't find the post), and it's still the case: When leaving the "Insert/edit trackpoint" function, the map jumps back to the initially selected point, which may be quite a ways away from the current position. For me, the natural thing is to edit track points along the route in chronological direction, so the jump back is quite annoying. Menion, when I brought that up before, you answered that this was probably due to some other change - so I'm not sure now whether you tried to fix that (and it didn't work) or forgot about it?

Similarly, while this was a new behaviour, it was always the case that when removing a section, you would sometimes be taken to different position. What happens here, I think, is this: Say you're on point 100 and remove points 50-100. Then Locus repositions you on point 100 again which is the former point 150, far far away. This should be easy to fix, I'd assume.

[Beta version 4.31.3.11]

Beta version 4.31.3.11 just uploaded to Google Drive.

Sorry it took so long. We had to finish some fine-tuning.

Changelog:
 - fix: layout in Track editor

Only quick test, but seems to be working again 

Menion, any ETA on a beta? I would really like to be able to use the Track Editor again Thx!

The track editor is also equally useless for me like the track chart because the bottom buttons are overlapping with the standard Android buttons.

See comments #101 and #102, previous page.

1. New design system for screens that allows control of drawing below the top status bar, bottom navigation bar and also better handles the cutout (camery in the display). It should have zero impact on stability, but some UI glitches (like buttons below the navigation bar), may appear.

Well, for me (on Galaxy S24+ and Tab S9), Track Editor is completely broken: All important buttons (Zoom, Point Forward/Backward, Menu) are hidden under my navigation bar. This sounds very much related to that change. What's weirder is that also Undo/Redo buttons (top left) don't appear when e.g. moving a point.
I made the mistake of updating while I still had several holiday tracks to clean up, so now I'm stuck

You need screenshot or sth else or can you reproduce?