Locus Map - forum

Important links
- blog post (https://www.locusmap.eu/news-release-3-40-0) about major version
- list of news (https://help.locusmap.eu/announcement/version-3-40-2-10-2019) of public versions

Versions
2. 10. 2019 - Locus 3.40.0

Trifle. Autopreset Navigation setting has not been set after restoring PRO version from Beta. Obviously, it is not backed up.

Really weird, should be. There is no exception for any settings in the app.

Are you sure you restored a fresh backup from the Beta version? If so, I'll try to invest it precisely.

Big release, thx, will test happily.
First finding: GPS is started on Locus startup, but I have set it to "Never" in the GPS&SENSORS options.

Quote from: menion on October 02, 2019, 18:01:43
Are you sure you restored a fresh backup from the Beta version? If so, I'll try to invest it precisely.

Yes, but maybe there was an error.  Normally, after the data recovery, a version change screen will appear.  This time, the screen did not appear after an automatic restart.  But everything has been restored except for those navigation presets.  So I set them up manually.  The next time Locus was started, the instruction screen was shown.  It is therefore possible that the first restart was not performed correctly.

On both my daily-use devices (Android 6 & 7), after installing 3.40, Locus was gone from the quick-launch panel at the bottom of the home screen.  (It gets the premium corner spot.)

Minor but interesting.  It was easy enough to put back.  :)

QuoteOn both my daily-use devices (Android 6 & 7), after installing 3.40, Locus was gone from the quick-launch panel at the bottom of the home screen

confirm

A tasker task also failed calling the app. I had to point the "Launch app" command to Locus again.

@tapio
this is interesting. Only idea: automatic live tracking or automatic track recording after the app start? I'm using this setting as default and never had a problem with it. Btw. does it happen always to you when you previously correctly (by double-back) close app?

@Žajdlík Josef
I've just tried restoring the backup from one version to second and it works correctly, so seems to be some temporary one-time glitch. Let's hope :).

@Viajero Perdido, @balloni55
expected behavior, hope not a big problem. I had to change the first starting screen to something different (because of speed optimization of start itself) and the result is, that the old "start icon" does not work so the system removed it.

And tasker task ... if you have any task hardcoded on certain activity within Locus then yes, this is broken with current version.

Question. What does the purple color mean in route planner?
My last point of track in picture is 15.
Even if I set a following shaping point on the purple line it will not draw a green line over it. Means except increasing track length nothing visual happens which is a bit weird.

GPS coordinates in the upper toolbar not shown correctly (at least in the Singapore area) after the update to 3.40, please see screenshot.

Quote from: menion on October 03, 2019, 08:56:10
@tapio
this is interesting. Only idea: automatic live tracking or automatic track recording after the app start?

No, no track recording etc. at start. Idk, now behaviour is gone. I always exit it via menu entry, because it runs as a service. Let's leave it like that.
EDIT it does simply start with the gps state of last session. But I chose the option to have it off at start. See my video. Feels like it is related to the quick startup behaviour. You can see the super quick start of Locus. As if the Locus session stays active after exit Locus.

https://youtu.be/JGxiNqCrUuQ

Track preview is not showing map/theme. Tested with oam+volUk and also Google Sat (online).
May I ask, is there a possibility to define the images resolution? Or even other (hidden) options? Currently it seems fixed and no such option in configuration file...

Planned route lost shaping points and via points. Couldn't find a reliable way to reproduce.

Is it just me or does Locus (latest pro) forget what map items (kml/gpx files) are enabled on every restart? I remember those were kind of permament once, but now they are all gone on each new start. Very painful, especially since the UI to enable them again is a clicky tappy horrible inconsistent mess :-).

Is there a change in action task track record stop with "autosave = on" and no name (don't know if this is relevant). It now gives a track save dialog, before it just silently stopped and saved the track.

Gesendet von meinem D5503 mit Tapatalk

Noticed the same. I recognized, Auto save was off, had to turn it on again.

Quote from: menion on October 03, 2019, 08:56:10
And tasker task ... if you have any task hardcoded on certain activity within Locus then yes, this is broken with current version.

Did the intents also change (like com.asamm.locus.ACTION_TASK)?

@CabrioTourer42
isn't the purple line just a side effect of click on the route segment? If you close the route planner and then re-open again, are all lines green?

"Lost shaping and via points" > method to reproduce needed ;)

@syni
thanks, it should be solved in 3.40.1 version.

@tapio
maybe this is somehow related to the reported issue with closing app (https://help.locusmap.eu/topic/the-app-doesnt-close-properly-since-the-last-update) ... don't know for sure.

Map preview: check please small improvement in 3.40.1 if it helps.

@joeloc
hmm maybe again related to a problem with app closing? Does it happen when you close the app by a double-back button (and then wait few seconds before start again)?
I see that when closing by swipe away in the list of recent apps, it is really not stored = will improve it, thanks.

@zossebart
interesting issue with autosave. I've checked all my profiles and this is still correctly set for me. Also when set, the track is really correct "autosaved" after press "STOP" button.

So my question: does it work for you when "auto save" is correctly selected or even with this setting it does not work?

@slarti76
definitely not, it should still work. The only change is the entry point that maybe someone for unknown reason used.

That map preview image on sharing track locks Locus, task can only be killed.

Font sizes on offline maps were huge. Because: Text size in the offline map options was on 200.%, Locus must have messed with that setting.

1. after long click on "data button" > hide all, all POI´s and tracks are hidden :)
But  "transparent buttons" to make them visible again are not available :-\
not until after  change of the screen the display is refreched and the buttons are visible
This behavior shows up at every step
https://www.dropbox.com/s/d3lkj0m694emiq0/InkedHide%20buttons_Trim.mp4?dl=0

2. i'm not sure,
visible waypoints of a geocache are no longer displayed after a restart of locus.
Wasn't that earlier so that they kept  "last state"?

Locus has become way too aggressive with centering the map on the gps position. For example, when I click on a position link in WhatsApp or on a web page or on any other external source and send it to Locus, it only moves to the place for a split second and then recenters on current gps pos. At least it should wait for the configured delay, just like when scrollling the map. Maybe even twice that delay, because it is obvious that I am quite interested in viewing the new place.

Also, gps centering seems to interfere with the track editor. Imho, Locus should never jump to gps when the editor is on.

It still auto centers in track editor? I thought this was fixed...

Quote from: tapio on October 04, 2019, 19:25:56
It still auto centers in track editor? I thought this was fixed...

You might be right... I cannot reproduce that now. However... the external link autocenter problem happens every time, eg when a WhatsApp location is sent to Locus.

@tapio
hmm weird issue with map preview & MF4 maps (OpenAndroMaps), with LoMaps it works correctly. Not 100% sure why, but hopefully fixed, thanks.

@balloni55
1. good point, fixed, thanks
2. just tried and still works to me. But maybe it is connected to the problem with the closing of the app. So the next version.

@joeloc
- aggressive centering, ah thanks, fixed
- centering in track editor & route planner should really be disabled

Quote from: menion on October 04, 2019, 10:08:44
@zossebart
interesting issue with autosave. I've checked all my profiles and this is still correctly set for me. Also when set, the track is really correct "autosaved" after press "STOP" button.

Ok, I now set the autosave option in the recording profile and now it works correctly, even when stopped through track record stop intend with auto_save: "yes". I thought when auto_save is send with the intend, it is forced regardless of the recording profile autosave setting. And it seemed to work like this before...

Gesendet von meinem D5503 mit Tapatalk

missing button in landscape

If you change the coordinates of a Geocache waypoint and return to the waypoints list of the Geocache afterwards, then the coordinates are still the old ones.
In order to update the coordinates, you first have to leave that Geocache and enter again.
Steps to reproduce:

• go to the waypoints tab in a Geocache
• tab on a waypoint
• click on the circle dot on the right side of the waypoint coordinates
• now choose any possibility to change the coordinates and change them
• return to the Geocache and observe that the coordinates didn't change
• leave that Geocache and enter again, now the coordinates changed

the coordinates in the top panel are only updated when the map is moving very slowly, this was quite faster in the past
https://www.dropbox.com/s/jihvo20hmeavg11/inkedkoords%20slow%20refrech_trim.mp4?dl=0

Locus dead after saving a track which I create in track editor. Screen turns black, Locus has to be killed.

I can confirm that. Saving a newly created or edited track with the route planner lets Locus freeze regularly.
App must be killed.

Also navigating or guiding along a saved track leads to a crash all the time.

In addition, the map tiles load extremely slowly.

When editing track Locus crashes from time to time. Go to edit. Select "delete everything before marking" and then map builds up very slowly. Locus crashes from time to time. Was already in the version before.

Was outdoor, recorded a track, IIRC it once again did not auto save, it broght up the track edit window after stop recording... and froze again. As in attachment.

After a long time again there was a problem with the endless Autopreset navigation. But maybe this is related to the incorrect termination of Lucus. I found out that Autopreset will end without any problems in short simulations. But the problem is when navigating in tens of minutes. If there are many changes to the route along the way, the route must be recalculated many times and an auxiliary NOGO will be inserted to prevent the turn, so the autopreset will not end. This status then lasts until Locus is manually removed from the last applications that were running. Only after this removal will the Autopreset exit function be restored. Try it out, I don't have much to test right now, because it's dark and cold, so I ride a little bike.

CZ: Po delší době se vyskytl opět problém s neukončním Autopreset navigace. Možná to ale souvisí s nesprávným ukončením Lucusu. Zjistil jsem, že Autopreset se bez problémů ukončí při krátkých simulacích. Problém je ale při navigaci v desítek minut. Pokud po cestě dojde k mnoha změnám trasy, musí se trasa mnohokrát přepočítat a dojde i ke vložení pomocného NOGO kvůli zákazu otočení, tak se autopreset neukončí. Tento stav pak trvá, dokud se Locus ručně neodstraní z naposledy spuštěných aplikací. Až po tomto odstranění dojde ke znovuobnovení funkce ukončení Autopreset. Zkuste vyzkoušet, nemám už nyní moc možností na testování protože je brzy tma a zima, a tak na kole jezdím málo.

Quote from: Graf Geo on October 06, 2019, 09:14:27
I can confirm that. Saving a newly created or edited track with the route planner lets Locus freeze regularly.
App must be killed.

Also navigating or guiding along a saved track leads to a crash all the time.

In addition, the map tiles load extremely slowly.

Seems to be fixed in V 3.40.2

ufff ... I just tried to change something with hope ... :)

So version 3.40.2 is out as Graf Geo wrote. I'll not answer on the post above as hopefully all reported issues should be solved. Thanks!

Quote
Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« Reply #207 on: September 29, 2019, 11:32:31 »
Beta version 3.40.0 RC1 + Beta version 3.40.0 RC2: Database Menu Track: When saving an already existing track, the app crashes. The thumbnail will also be lost.

First test: Now it works fine in new version 3.40.2. :)

Thank you Menion! Hope was not in vain.

I was surprised that these important bugfixes were not mentioned in the changelog or the history for V 3.40.2.

Since 3.40, buttons in edit track name, fullscreen mode, are too much @ bottom. But usable. 1080x2244 screen res.

In the widget, recording preset is not shown. Only after clicking where it is supposed to be.

@Graf Geo
because some issues I wasn't able to reproduce, I've rather not mentioned them :).

I also made performance improved in rendering MFV4 maps if you made more pan & zoom in the row. Hope it should be noticeable.

@tapio
fullscreen, hmm thanks, will look at it.

And widget ... well, I made a tiny improvement in recent version 3.40.2 because some texts were broken. Anyway these widgets are maybe 5+ years old and does not fit well to modern devices, so I will need a re-work .... I'll look at least on this tiny issue, thanks.

- different language as system
# 21 1+2
# 27
# 29
All my reported problems are solved. 8)
thanks a lot !  :)

Hello Menion
In the current version is the function "Center map at GPS position" no longer works when destination guidance is switched on.
According to my test this only affects Android 5.x, from Andoid 7.x it seems to work.

Greetings
Mips

Quote from: menion on October 07, 2019, 17:40:39
@Graf Geo

------ ***------
I also made performance improved in rendering MFV4 maps if you made more pan & zoom in the row. Hope it should be noticeable.
------ ***------
....

Yes it's noticeable. Not super fast (it never was with V4 maps), but acceptable fast like before in V 3.38. Thanks again.

This one is still an issue in 3.40.2.
It's especially hard if you do a multi cache and have to update coordinates or do a waypoint projection by editing a waypoint rather than creating a new one.

Quote from: Thomas S on October 05, 2019, 12:00:39
If you change the coordinates of a Geocache waypoint and return to the waypoints list of the Geocache afterwards, then the coordinates are still the old ones.
In order to update the coordinates, you first have to leave that Geocache and enter again.
Steps to reproduce:

• go to the waypoints tab in a Geocache
• tab on a waypoint
• click on the circle dot on the right side of the waypoint coordinates
• now choose any possibility to change the coordinates and change them
• return to the Geocache and observe that the coordinates didn't change
• leave that Geocache and enter again, now the coordinates changed

We used to be able to add waypoint directly from the 4x1 widget while recording track, but that option is no longer available.

@balloni55
#41 , fine :). With logs manager, you probably noticed I had to change the selection to dialog from that floating buttons. The issue you reported was because there was not enough space for five items so the button was by accident completely hidden.

@Mips
hmm Android 5, such a feature should be device-independent. When you click on the bottom-left centering icon, what happens? Also, do you have enabled "Hold map center (https://docs.locusmap.eu/doku.php?id=manual:user_guide:settings:control#hold_map_center)" settings?

@Thomas S
very old problem I know about and for some reason, I had big problems to fix it without breaking some other feature. Screen with "Point detail" will receive complete redesign over winter, so this issue will be definitelly fixed as a side-effect of this change.

@teokcmy
it is still there. Just seems that icon is missing ... issue found, will be fixed in 3.41+

@Menion

QuoteWhen you click on the bottom-left centering icon, what happens?

The icon is activated and deactivated shortly afterwards and the map position is shifted.
In the normally map view it's all right.

Mips

Can't be sure, but it seems I'm seeing more texts being cut-off again.  Is this a by-product of the speed-up to map rendering in .2? 

(Or to rephrase, was the "fix" to the text problem an intended byproduct of extra rendering done in 3.40, now removed?)

@Mips
we have one more guy on help desk who have same problem. And ... you are the only two. None of us is able to simulate it, weird.

If you are willing to help a little more, "Backup of settings" (over backup manager) and recorded short video may help here a lot. I should restore your settings and try to simulate it exactly based on the video. If you want to do this, send the result on jiri.mlavec@asamm.com email, thank you.

@Viajero Perdido
Hmm ... sometimes, I'm more than stupid. I was searching for source of this slowdown and during testing I've disabled internaly this feature. It has no effect, but remain disabled in production version. Sorry!

In GPX import screen, bottom option: Is there a reason why Locus always has it unchecked initially? I always prefer srtm elevation data. I think Locus should remember the state. I see no problem here... if user decides to use the recorded elevation data, he can re-import the gpx again.

on the past version i lost 20% battery when  i use locus just to log my track for 3 hours.
display off and in the pocket

with the new version i tried it two times
both time i lost wtih the same procedure 40-45%

any idea where this difference come from?

@ Skawal: Have you ever looked how much share Locus had on the battery consumption. It could be synonymous with what else has consumed a lot of battery. I did not notice any difference.

Modify track with many waypoints: Screen turns off (sometimes), Locus crashes (always).

Quote from: tapio on October 13, 2019, 16:55:55
Modify track with many waypoints: Screen turns off (sometimes), Locus crashes (always).

since ancient times  :(

Galaxy S8 w/ latest Locus final release:
Screen is locked (w/out PW) - starting Locus from the side panel - share track preview - preview is generated - tap share button - Locus goes to background - Lockscreen is shown for one second - then Locus is shown again with map screen and track. No selection of apps :(
Workaround: close Locus - unkock Screen - starting Locus again - share track preview works.
I miss the possibility to unlock the lockscreen or a hint of "unlock screen at first" or something like that.

Since v3.40.x or so: tap track on map screen - tap into popup to go into track detail screen - tap on small arrow to go into the folder the track is stored -  activate another track by tapping on the eye symbol  - then go back by using the Android back button.
Before v3.40 you tap two times and you are out of track manager and back on map screen - if i remember well. Now you have to tap billion times and go back the whole bread crumbs.
Possible Workaround: please provide a link in the track popup for "(go into) folder". I remember there is always a request on the help desk.
Thank you.

when creating a new geocaching waypoint its default values are generated with '°' ... but with this symbol the waypoint can't be saved.
If the '°' is removed ... the waypoint can be saved without error message.

Quote from: jonny.blue on October 13, 2019, 19:13:15
when creating a new geocaching waypoint its default values are generated with '°' ... but with this symbol the waypoint can't be saved.
If the '°' is removed ... the waypoint can be saved without error message.

In the German forum was discussed. Both types of writing should be possible.

@tapio
I still think that this setting "Fill elevation" is usually not needed to change and if, then definitely with awareness. Yes, you may re-import your data if you notice this problem on time. You may also by accident overwrite more precise data then Locus is able to generate without notice. So I still consider manual selection and in case of need, later manual "Fill elevation" as a better solution.

Modify track with many waypoints: eh, you just do editing and during that process, device turn screen off?? App crashes and it happens since "ancient times" (@Christian)? Am I aware of it? A better description for simulation is welcome, thanks!

@Christian
problem with generating preview sound quite complicated to me. What means "start Locus from side panel"? Maybe the video of this process is possible?

Display additional track ... click billion times? :). I see that first back press display list of folders and second click than return to the previous track. So maybe the first click does not work as before? I'm checking the app source code and see no difference, hmm. Anyway fastest how to display new track, same as with points, is to tap on track overview. This immediately display track on the map and return directly to the map screen.

@jonny.blue
another interesting problem where I see no difference in code (last edit before 10 months), but the same issue happens to me as well, interesting. It will be fixed in the next version, thanks.

Menion, Locus not responding:
https://youtu.be/3VQMVraKQt0
Trach has ~4800 trackpoints.

V3.40.2.1
set GC coords solved :) thanks
one additional whish: is it possible to open the "numeric keyboard" in place of the "letter keyboard" if user click  line of coords?

Awesome, new beta with navigation track color change. I like it.

Beta tts speaks czech again...

@tapio
- is the problem with stuck Locus Map happen also with new Beta?
- color change, hmm ;)
- Czech TTS ... Locus Map and system set to DE? Damn, why Czech? :)

@balloni55
- small problem here. Android open keyboard automatically based on defined supported so-called "input type" for an edit field. And in this case, I would have to set the input type to "number" values only. Which will prevent to insert characters like "space" or "°" ... may this be a problem? It's a question ...

New beta V3.40.2.1: Great, the street names are now displayed more and better.  :)

Yes, Locus and Android both DE. No change at Locus stuck on modify track. If you wish I can send GPX.

Edit: I found, the higher the zoom level, the more there is a delay before the modify tool starts. Locus fully bricked is starting at ZL20. I. e., a track with many wp on zl 20,then "modify track", may cause the problem.

Quote from: menion on October 15, 2019, 21:24:24
@balloni55
Which will prevent to insert characters like "space" or "°" ... may this be a problem? It's a question ...

not for me..... and available "space" depend on used keyboard
BTW: click on "grid-button" or "circle-dot button" open numeric keyboard  ;)

With the new UI design, the "Nearest Points" sidebar looks a little odd and wastes space: There's a lot of white around the rather small icon, thus cutting off the text more than needed. Also, when a point is selected, you can see that the text cuts off without any pixel margin to the blue background of the "selection eye". Doesn't look nice.

I'd also like to take the opportunity to repeat that selecting/deselecting points from the sidebar is still far too cumbersome. There should at least be a Select All/Deselect All, even better would be "Select within x km radius". I find myself clicking on dozens of points all the time to see what's of interest in the currently centered area.

@balloni55
hmm oki. Let's change it a little. What about allowing only decimal numbers in these two visible fields for lat and lon? This prevent some incorrect copy&paste and also allows to quickly edit & display numeric keys. For the need to insert precise numbers in a different format (like X° YY'), there is still the "Edit coordinates" screen available.

@slarti76
I've checked the current recommendation and compare this side panel with other Google-based apps. Result: I've increased the width of this side panel, so it will definitely cover space that was "lost". And btw. it is not a new "UI design", but more a unification of the design across app.

About the content of "Nearest points" itself ... well, it is a tragedy, I know ...

Today I was playing with the locus and ant + sensors to set up Locus for Garmin.
My intent was to clean up the list of unused ant + sensors leaving only the heart rate monitor, but I made a mistake:
I activated the cadence and then removed it.
I didn't notice that when I deleted it it was active, so I also kept the only heart rate monitor sensor in the menu, but Locus was also looking for the cadence I didn't have.
I had to reactivate the cadence sensor visibility, disable it and then remove it from the menu.
I think when removing a sensor from the menu, Locus should disable it by default.

Another little bug, I deleted all useless ant sensors from ant menu, but when I choose the one I need in rec panel, automatic hardware start, they are still all proposed.

New beta, Navigation along existing track: I pick a preset, start navigating, but Locus does not apply the chosen preset. Everything stays as it is.

V 3.40.2.2
"different language as system" problem is back again

add WP to geocache, in first window the coord format is "dezimal degree" :-[
in next window format is as expected "degree and dezimal minutes"

In today's new beta, moving a geocache into position under the crosshair no longer causes a little summary window to pop up.

Intentional?

I kind of miss that, but could get used to it.  (EDIT: I do have "Labels on map" set to "On hover", so I guess it's a bug.)

no Track recording - again!

Today I had to recognize, that track recording (Locus Map Pro 3.40.2 / OAM v4 maps / Android 6.0.1) is again not working:

- I do not know why, but suddenly reccording stops (see screenshot 1) + individual map-cursor is gone
- switching the display off and after a while on again, the track can be seen - but directly (linear distance), not the way gone along the way! (see screenshot 2) AND, the position cursor is still not to see... (stopping and deleting the track recording - individual position cursor appears again)

(https://thumbs2.imagebam.com/5d/a9/bb/ef1d591323985529.jpg) (http://www.imagebam.com/image/ef1d591323985529) (https://thumbs2.imagebam.com/e6/b6/ce/94b6bf1323985538.jpg) (http://www.imagebam.com/image/94b6bf1323985538)

note:
GPS is always on - and no "Energy mode" or something like that!

It is really disappointing that this happens again (problem appeared some months ago already and was fixed by you after a while).

@lor74cas
understand. Complicated to solve because of the system I wrote almost 5 years ago. It is planned to rewrite and this is something that will definitely have to be changed, agree!

@tapio
quite interesting, can't simulate. May you share with me your preset definition? It is stored in Locus/data/presets. Thanks.

@balloni55
well, it is a result of: https://forum.locusmap.eu/index.php?topic=6752.msg57528#msg57528 , where I wrote Which will prevent to insert characters like "space" or "°" . This means, only coordinates in decimal format may be inserted. For insert in different format exists button top button on the right side.

@Viajero Perdido
ah, good point! (side-effect of new clickable track waypoints during navigation). Thanks, fixed

@bezel
I have no idea, how may i help here, sorry. Don't you have some too strict parameter for "min accuracy" in recording profile? Also, does this happen even when screen is on and you clearly see that your GPS position jumps every second?

See attachment, it is independent from the picked preset. It just does not change preset at all on start of routing.
TTS speaks czech again.

Quote from: menion on October 14, 2019, 16:00:05@Christian
problem with generating preview sound quite complicated to me. What means "start Locus from side panel"? Maybe the video of this process is possible?

Display additional track ... click billion times? :). I see that first back press display list of folders and second click than return to the previous track. So maybe the first click does not work as before? I'm checking the app source code and see no difference, hmm. Anyway fastest how to display new track, same as with points, is to tap on track overview. This immediately display track on the map and return directly to the map screen.

Side Panel means Samsung UI's Side Panel / Edge Display.

Regarding the number of taps to go back on map screen - there was a faster way before :(
A "folder" item in track popup would be helpful.

Sometimes Track editor (since ancient times) and also Route Planer crash without any warning when it is used excessively. I guess it's a matter of memory. This happened frequently on my old Note and on my new S8 also.

Waypoints stored within / merged with a track can not deleted since last final version. I'm so tires of this.
btw: the user manual  (https://docs.locusmap.eu/doku.php?id=manual:user_guide:tracks:import)is not up to date.

@tapio
thanks, I'll try to play with it little more, because I'm still unable to simulate it.

@Christian
"Back press": I've just installed fresh 3.37.2 version
- tap on the track on the map > open detail > click on the right arrow opens list of tracks in the same folder > eye to display another track > back press display list of folders! > back press display first track detail > back press to map .. so 3x back press

Current version:
- exactly the same steps! - so 3x back press

Whare is the difference? As I wrote before, tap instead of the eye on the track preview to get directly to map!

Track editor, Route planner crashes, as usually, needs an error log (https://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log) after the issue happens.

Waypoint:
- open track detail, waypoints tab > delete button in context menu works.
- track on the map, tap on track waypoints > popup menu "delete" works

Christian, you seems little angry, but sorry, I see nothing I may help here (not "nothing I may improve", for example back should be reduced logically on two steps by excluding "folders" view, will check it). (EDIT: should be improved in next Beta).

Preset on routing along track is working now. Also, after routing, it switches back to the prior settings. Very good.
But TTS insists on speaking czech. I toggled between System and German language, no change.

Presets: perfect.

Czech in TTS is more interesting. Write to me please what is language of your device, language set in Locus Map and TTS engine and language in Locus TTS settings. I'll try to set the same to simulate it ... thanks.

Quote from: menion on October 29, 2019, 18:13:14
@tapio
thanks, I'll try to play with it little more, because I'm still unable to simulate it.

@Christian
"Back press": I've just installed fresh 3.37.2 version
- tap on the track on the map > open detail > click on the right arrow opens list of tracks in the same folder > eye to display another track > back press display list of folders! > back press display first track detail > back press to map .. so 3x back press

Current version:
- exactly the same steps! - so 3x back press

Whare is the difference? As I wrote before, tap instead of the eye on the track preview to get directly to map!

Track editor, Route planner crashes, as usually, needs an error log (https://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log) after the issue happens.

Waypoint:
- open track detail, waypoints tab > delete button in context menu works.
- track on the map, tap on track waypoints > popup menu "delete" works

Christian, you seems little angry, but sorry, I see nothing I may help here (not "nothing I may improve", for example back should be reduced logically on two steps by excluding "folders" view, will check it). (EDIT: should be improved in next Beta).

I'm not angry but disappointed about the quality of your new code in existing modules, the way you respond and my wasted time and all the recurrent questions of my bikemates ("why is this broken? When will it be fixed? Last time it ran properly, today not. Why? When will it be fixed again?").
Yes the waypoints can be deleted, but the screen was not refreshed. So it looked like that nothing happened even when i tried ten times. That took me some hours and phone calls to figure it out and report back to the mates...
A similar case happened some weeks ago when waypoint could not created. Quite boring :(
There are still some issues to report.

Note: I'm the one who recommended Locus Map to all my bike and running mates to have the same platform. Now I'm the one being asked when something is not working properly and the one to have to care about. Now we wait for the new Locus Map Platinum Expert Eternity Version and it's amount of fee and check the quality of the app next year. When the errors remain in the developement process we will switch to another app all together. An app is a tool not a lifelong task for users. Imho. Our task is to plan some tracks easily, go outdoors and have some fun guided by a reliable app and than forget all the stupid things of the working days. When the app produces some errors the stupid things remain and the fun is broken down.

When the Track Editor or the Route Planer crash I'm p***** 'cause all my edits are gone and the time is wasted. I have to do this again with the fear of that can happen again. Some times I do it three or more  times.
So I will NOT spend any more additional time in creating debug logs, sending big personal data over Internet, writing description in the forum with screenshots or something else! As I wrote it some years ago I'm not a beta and software tester nor for money. Do you have an sufficient error reporting in your App? Fine! Otherwise you have to figure it out by yourself because you are the responsible person. Call me old and conservative - in my youth the developers debuged and tested  the software excessively by itself BEFORE releasing it. But that is quite oldfashioned nowadays. Today the users do it. Except me.
Thank you for reading and understanding.

And thank you for the improvement of the "3x back press" by excluding "folders" view. An additional item in track popup would be enough.

Hi Christian,
partially understand. So just a few points
- The quality of the code is average. It always was. I never wrote tests and did all testing in the field and thanks to active users. Can't imagine different workflow for a complex app with a single developer.
- the way I respond: direct, open, friendly ... anything wrong? Point me on a problem to make my communication better, thanks.
- your wasted time: we communicate maybe 6 or even more years? I just hope, not all the time you spend on the forum and with Locus was not completely wasted ...
- problems & questions from bikemates: you may always simply forward them on our support, it is our problem, not yours.
- Platinum Eternity version is our chance to have more than three people in the team and also a chance for all to receive updates for more than a few next years.
- quality of the app based on subscription has to be definitely higher, so I expect less frequent updates and more internal testing
- If I do not miss anything, you did not reported crashes in RP or TE. You spend more time writing about it here and writing about "I won't do any logs" , then, in reality, take creating one log. But ok, the issue won't be solved until I receive from any other guy log, or information on how to simulate this problem.
For your information, I use the so-called "Crashlytics" system for automatic collection of app crashes. Currently, I see total of 9900 crashes during the last 30 days (557 different problems). I always solve the first 10 - 50 most often. So rare problems like yours are definitely hidden somewhere deep ... maybe 50% or more problems are specific for some devices. Most of them is currently unsolvable because they are in some system component and I spend days and days by searching how to hack it ...

Thanks all ... anyway, understand your points and no one force anyone to help fix bugs I made during my dark nights.

One thing about the backups I just stumbled over:
When I do the "Settings only" backup, it diesn't include the "presets" folder. That kinda seems wrong to me - presets are a very important part of settings system, I'd say.

Are you sure? Just check the content of the generated zip backup. Presets should be there (directory data/presets).

Quote from: menion on October 31, 2019, 06:22:48
Are you sure? Just check the content of the generated zip backup. Presets should be there (directory data/presets).

Yes, I'm sure, I checked the backups of several devices, all only included data/config (plus config*.cfg and _various). Mind you, talking about the "settings only" backup, the full backups contain the presets alright.

Ah sorry, you are correct.
Maybe a question: does it make sense to do "settings only" backups? When I see it now, for me "Backup of settings" should be removed. Isn't it much better to have a backup of all important stuff and later decide what to restore (if you need)?

Quote from: menion on October 31, 2019, 08:29:26
Maybe a question: does it make sense to do "settings only" backups?

I think a backup of  settings makes sense for exchange of settings between the release and the beta, where backuping all data is not that useful.

As release/beta  settings are independent, while "big data" are shared.

Sent from my Xiaomi MI A2 / Android 9, via Tapatalk

Understand. This is true only partially. Part of backup (one in "various" directory inside backup) is not shared, but rest is also shared by both apps.

Btw, we will have (generally many apps) huge problem since Android 11, where apps will not be able to write even to internal memory anymore. At least not in the way Locus Map needs. So Free/Pro won't be able to simply share data anymore ... I still do not know how to solve it, but most probably "synchronization" over our server will be the key ...

I use backup settings when switching from BETA to PRO and back. It's much faster than creating a full backup. It would be great if the presets were added.

Why cannot Google manage within Android an extra,  shared folder, where all apps would have access ? (a rhetorical question)

Like shared documents in Windows.

Sent from my Xiaomi MI A2 / Android 9, via Tapatalk

I ask myself a similar question Libor :). Security, protection, "sandbox" for apps ... all this together ends in highly limited storage access ...

So you both have same use-case: backup of settings only to work with Beta versions. Beta testers: ~0.5% of all users ... hmm

I guess beta testers will survive the removal :-)

Sent from my Xiaomi MI A2 / Android 9, via Tapatalk

Quote from: menion on October 30, 2019, 17:45:45and language in Locus TTS settings.

Oh, I wasn't aware of the tts language setting, I thought it's derived of the UI language. My bad, sorry. Changed tts language in Locus from czech to german, works.

For my beta testing, I do not use backup/restore, but use either the same data sources or copy some folders from stable to beta before Locus start. I hope its a valid approach. See screenshots.
Means also, settings, toolbar, config file, those are independent and have to be managed independent from stable.

I'm using Foldersync to share Locus to multiple devices. I sync some subfolders wich includes tracks, setup etc.
For beta it might be enough to collect all in one folder and ask beta testers to use an external sync app.

.....

This app will not work in Android 11. Wtf.......

Multiple crashes when searching for an adress online.
I have the feeling it depends on the adress I search for.
Might be an old bug. I don't know.

V 3.40.2.3

@tapio
heh, you have really sophisticated system, nice :)

@CabrioTourer42
thanks for the log, got it!

And "This app will not work in Android 11. Wtf." ... it will, just app will have to store data in private "android/data" directory => a) not shared between Free & Pro and mainly b) whole directory deleted when app un-installed  :(

Are the FIT files exported from locus compatible with Garmin Connect?
I tried to export from locus to FIT format to uplaod the file to Garmin Connect.
The track was recorded with locus using also the ant+ data from hr of my garmin 235, for this reason I used the FIT format but, Garmin Connect doesn't like it not in the form of activity neither as route.
So I used the gpx 1.1 to include hr data, Connect liked it but HR data were not imported, this is a fault of Garmin because I can see the hr data in the gpx file.

Hmm with FIT files it is really a pain to do anything. So the current system is made with the method "try this, try that" and it will be maybe working.
Generally, if something does not work as expected, I need to simulate it. In this case, I need in the best case a file from Locus Map and file how it should look like. So if is possible to supply me something like this, I'll gladly look, where is the difference.

Quote from: menion on November 04, 2019, 08:52:38
Hmm with FIT files it is really a pain to do anything. So the current system is made with the method "try this, try that" and it will be maybe working.
Generally, if something does not work as expected, I need to simulate it. In this case, I need in the best case a file from Locus Map and file how it should look like. So if is possible to supply me something like this, I'll gladly look, where is the difference.

Hello Menion,
I do not usually upload FIT files to Connect, but I send there GPX files exported by Locus, the FIT files are provided directly form my Garmin Forerunner 235.
If you need it I'll try to create a Locus FIT file with HR and a Garmin Fit file from the 235 at the same time so you can compare the results but meanwhile I tried to upload the Locus FIT file to Strava and it worked like a charm. So the issue is from Garmin Connect side, I think they want only special FIT files created from their devices.

Tracks are frequently not loaded completely into the Route Planer. See two screenshots here (https://c.web.de/@337566466565996910/mtcNKN5EQH-5oak773DAxg).
The Track shown in the screenshot was generated by Brouter Web and imported and edited in Locus Map some days ago. Now when i load it into the Route Planer the part of the track from start to waypoint 1 is missed. That happens to me some weeks ago with another track. :(

And another month behind us ... and winter is almost here ... seems to be a quite "quick" year for me this time.

The little sentiment, sorry. New version published *** 3.41 *** and available to all users already for a few hours. No serious issue is known to me after a day of public testing = so looks good :).

@lor74cas
Garmin is always too strict with handling its own format. I and many users spend many days to give proper support for Basecamp app so what you wrote is no surprise. On second side, I remember reports that FIT from Locus worked to some people also in Garmin Connect. So there maybe is something to fix.

@Christian
I never noticed this problem, but it will be definitely a little complicated to solve. Tracks stored in Locus Map database has, among others, stored small configuration how they may be loaded into route planner. Any of this config is not exported to any format. So to be able to properly fix it, I, unfortunately, need a) exact steps to simulate it or b) full backup of your Locus Map where will be points&tracks database so I'll be able to use the same data as you.

New version: https://forum.locusmap.eu/index.php?topic=6789.0