Messages

I like the old track overview better. In comparison to the new one, these are its advantages:

– More map details --> more information about the track. An improvement of the old diagram could be to increase the image resolution to get a better quality when printed out (what I sometimes do to produce a backup paper map for hiking)
– No grey overlay --> Map is better readable and looks better when printed out
– more statistical information about the track
– The ratio between the map information and the font size makes more sense. When reading the map, you usually zoom in, why are the fonts so huge?
– hight diagram is easier to read (see comparison). An improvement of the old diagram could be to show more than one hight indicating (horizontal) line.

The new overwiew looks more like a thumbnail, I don't exactly understand the use case. When I wanted so send a track overview to someone who doesn't have Locus App, I would use the one with the best image resolution and the most (relevant) information about the track, so that the receiver gets the best idea of it.

Wrong topic I know, sorry, but charts below (time vs. battery current milliamps each 2 minutes) comparing Locus with just track recording vs. Locus with navigation and track recording. Just thought it was interesting & confirms for battery misers when riding all day why avoiding navigation mode could wring out the life of the battery before it goes flat. Ignore the -250mA spike on the 1st chart - was when camera used, not just Locus running. I have found/ discovered recently that measuring/ logging current with Tasker rather than %level is a better indication of energy usage. At 10:45 in 2nd chart, navigation stopped and was then just track recording.

@menion- I note in v4.23.1 release notes "reduced app refresh in the background when not active" - charts below are for 4.23.0 so would be interesting now to see whether this affects the battery current. Did you make this change to save battery energy?

[@Diddi]

@Diddi
thanks for the tests! And "Presets" ... good old topic. We'll have to think about them more later. The current solution is usable, but has mainly these limits > a limited number of available items to cover all possible use-cases.

@Graf Geo
thanks for the tests as well, perfect.
Empty base map ... damn, why this does not happen to me  . I'm sorry, but I still have no clue why this happens, because if you see the map on the screen or in the top panel, than it should be available here.

@michaelbechtold
Huge "sync.db" > this happen because of the problem we discussed on the help desk. This file contains the history of all your sync tasks! My file after all years with sync has 350kb! Delete it, it may cause no problem. And you may watch it to see if sync finally behaves correctly for you.

@loudini
error in GC live map > got it, fixed, thanks.

@Tapio
seconds > no please  ... anyone really interested in these values? Eh, no 

Someone wrote in another forum:  "It's also pertinent to know that Google recently closed the scoped storage Files app loophole, so many file manager apps no longer can see inside the private folders in the Android directory."

Thank you for clarifying this. I knew I wasn't crazy. I got a new phone a little while back running android 13 and I was able to use solid explorer to get in there and then last week I tried again, and it just wouldn't work.

I will try the method cited above after my ride tomorrow.  thanks.

Damit werde ich mich am Abend beschäftigen. Bis hierhin vielen Dank für deine Unterstützung und Einschätzungen, Michael! 

Nach einem Neustart von Locus Map wurde der durch den Fehler unterbrochene Verschiebevorgang fortgesetzt und erfolgreich beendet. Jetzt ist wieder alles so wie es sein soll. Vielen Dank!

https://forum.locusmap.eu/index.php?topic=8672.0

Ist Android/Media sichtbar? Locus evtl. dies verwenden lassen.

[@Tapio]

@Tapio
Choose location > under this menu is quite a lot of options, so I would rather stick with the united system across the app. Anyway, what is unexpected on the "Navigate to" call?

The search is unexpected. I already know where I want to navigate to and don't need the search. Most of the time when I use "Navigate to" I want to nav from gps pos to screen center.

Wouldn't it be more logical if it came up with the screen as attached?

The route planner should appear first. Then I choose whether I want to set the start or the destination. If I then go to Select destination, Tapio's screen should appear. From there I have all the options, including search.
If I go to navigate from a POI. Then the procedure should be the same. Only that the destination is already selected and I only have to set the start.

Das Problem ist, dass ich das nicht erkannt habe ... 

Und dass ich einfach davon ausgegangen bin, dass nur die Routen in dem Bildschirmbereich gezeigt werden. Weil ich dann so viele Routen gesehen habe, bin ich von einer Fehlfunktion ausgegangen.

Danke für die Erklärung

The problem is that I didn't realize that ... 

And that I simply assumed that only the routes were shown in the screen area. Because I then saw so many routes, I assumed that there was a malfunction.

Thanks for the explanation

[@Diddi]

Hi guys,

weekend, again? Damn
At least a bug-fix Beta version on the Drive.

@Diddi
update of single cache in new Beta! An update of a bunch of caches at once will have to wait a little. Remind me this once the new "Data manager" will be published (this year).

@slarti76
how do you share the location? There are more options and not all may work ...

@loudini
icons, thanks. I hope it is fixed now (because I can't simulate it).

Die gleichen Probleme hatte ich auch. Ich habe es dann mit dem Widget probiert und konnte dort dann beenden.
Den Post findest du hier: https://forum.locusmap.eu/index.php?board=62.0
Es ist bestimmt nützlich wenn der Fehler bei mehreren auftritt.
Ich hätte mich wegen Google einfach mal in der Drive App abgemeldet. Aber es müsste auch eine Übersicht geben bei Google wo man sieht welche Apps Zugriff haben und den dort eventuell entziehen. Genaues kann ich da aber nicht sagen. Zur Not warten ob vom Locus Team das hier liest oder Helpdesk. Dann aber auf hier verweisen.

Ich habe z.B. in Locus den Backup Ordner so eingestellt, dass die Backups in einem Unterordner von Download gesichert werden.
Der Grund liegt darin, dass ich den Download Ordner mit Foldersync auf meinen PC sichern lasse.
So sind im Falle einer Havarie oder eines Handy Verlustes nur die letzten Tage weg.

[@jonny.blue]

Thanks Michael,
unfortunately, the version with a fix (problem with choosing a routing profile), that came an hour later, was not refused by Google, again because of some insufficient informing of users about subscription, omg. So, most probably one more version will have to be published next hours/days, who knows? But nothing serious. The version on the Drive is perfectly fine to use. Sorry for this mess. 

@jonny.blue & @AgusOrux
hmm, perfect, at least something positive!

---

Uff, hopefully with 4.20.1 (1121) version, all major problems are solved. Thanks and have a nice weekend!

Sorry Michael, I discovered one minor issue right after release, so I've immediately republished the new version 1120. Uff ... 

[Locus Map 4.20.1 published]

Locus Map 4.20.1 published.

Available over Google Play or the Drive directory. I've made a bunch of various fixes, so hope it helps.

@jonny.blue & @AgusOrux
Unfortunately, I'm unable to simulate your issues. If the new version does not help, I'll need a full bug report right after the crash happens by this method. Thanks.