Messages

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.

[@jonny.blue]

@jonny.blue
firstly, please merge multiple posts in a row into a single one, or create a separate topic to your problem. This only complicates the readability of the whole, very important, topic. Thanks

Then, as balloni wrote .. are you using the latest app version 4.20.0 (1118)? Also, can you estimate how many points & tracks were visible? When hidden, no problem at all, right?

@Andrew Heard
"Locus Map has stopped" > This does not look like a system dialog and the app can't display such dialog when stopped . Hmm, full system log right after this will be necessary I'm worried ...

[new version 4.20.0 (code 1118)]

Oki, the new version 4.20.0 (code 1118) just published also on Google Play (second attempt to pass verification).

Minor fixes along the way ...

@Andrew Heard
these are not some minor versions, but regular release versions. Better should be 4.20.0 RC1, RC2 etc, but because I also publish them on Google Play, all are simply named 4.20.0.

Dashboard resize issue ... hmm, will look at it.

[App version regenerated 4.20.0 (code 1117)]

App version regenerated 4.20.0 (code 1117)
Available in the "release" directory.


"App stop" problem, probably got it, thanks!

@jonny.blue
thanks for the testing and sorry for the complications.
BRouter error > do you use an unsupported combination? We made a bunch of big improvements (due to new system of customization + route warnings) so internal LoRouter profiles are no longer compatible with routing data provided by the BRouter application itself. There is also an opposite "problem". BRouter now introduced a few parameters that are not (yet) compatible with offline LoRouter, so profiles from the original BRouter repo may report an error when used with offline LoRouter.

So:
- use "public brf profiles for BRouter" only with the Google Play BRouter app. Offline LoRouter currently does not support all BRouter features (this will change in the near future), but if you don't see any error, it should work fine.
- use "LoRouter profiles" only with offline LoRouter. They most probably won't work with BRouter app

Thanks for understanding.

Installation of the older version is more complicated because it requires un-install the current version first. Suggest waiting a day (or in the worst case two) till a new update is generated/published.

What settings do you want to modify for BRouter? All are available in the Route planner directly.

@Tapio
Intent problem > this is unfortunate. The plugin uses a hardcoded name of the starting screen, but this has changed in the latest version and this old screen no longer exists.

Problem with recording > problem with the start may be connected to the crash at start. The worst is "action: stop".

@Andrew Heard
Plan visible after closing planner > grrr, so another try, even more aggressive plan removal in the next version.

Aspect colored by slope > I've had this prepared, but wasn't satisfied with the colors ... so later.

Perfect 

Hi druki,

"update" is visible in case, you have already purchased an older version of the map, than the current newwest.

"download" is visible in case, you do not purchase this map yet or you have already the latest version available for download.

Hi guys, the new version brings a lot of interesting changes and even more on the background. I have to thanks a lot for tests most of you made during last weeks. It really helped a lot!!

Version 4.20.0 was uploaded to the Google Play, but was rejected because of some missing info in subscription screen. It will take some time to fix it, so I've at least uploaded APK to the public Google Drive directory. If anyone wants to test and use this version, feel free to do it.

Have a nice weekend!

[@balloni55]

@balloni55
I have two options here.
- a current solution where the cache is sent to the "Import" system
- or the app may display the cache as a temporary point on the map where this first bottom button will be "+" > so add to own library. Maybe this second is better, right?

@Michael Bechtold
I was not touching the map core at all, so there has to be another change. You are talking about Maps > Advanced features > Pre-load global map, right?

Slowdown with a longer plan > ah, thanks for this. Another serious issue, will look at it.

@Tapio
Aspect coloring > I'll insert a legend into the app later. For now, this picture should help. Aspect coloring colorizes hills based on it's orientation.
You cannot view this attachment.

Stuck at the start > it happened to me twice too. Hmm ... another try in the next version.

Delay in removing the content of planner > I've noticed it as well, hopefully improved now.

@Andrew Heard
problem with saving of track > hmm, will have to test it a little more...

@freischneider & others
Usage of the space in the route selection dialog > what you see is the result of quite long testing and I'm quite happy with it to be true. As mentioned - there is enough space, so the app uses it to make it easier to work with the whole screen. Some options for quick selection of last used profiles? I was already thinking about it, but was not sure how to do it. So maybe later.

[Beta 4.19.0.12]

Beta 4.19.0.12

With two new features
And many fixes regards routing profiles and app start.

@Andrew Heard
Anything related to "How the app computes routes - routing profiles", to @Radim V here.

[@Tapio]

@Tapio
thanks, I've made some improvements to make it more robust, so next version.

@Andrew Heard
Hmm interesting ... I have identical problem in Vivaldi 

[@slarti76]

@slarti76
agree, it may be useful. Unfortunately, I do not have "first trackpoint time" easily available for sorting in the database. There will be a major database update during next year, so I'll try to keep this in my mind 

@Andrew Heard
inconsistency with categories is only partial. For me is more important consistency with the "Link with presets" system + as I mentioned before > the possibility of having a working fallback to the working internal profile in case, the external profile does not work.

Track recording problem > Unfortunately this does not happened to me yet. Anyway, I will try to add a small delay till the final screen is visible, if it helps.

[@T-mo]

@T-mo
update of profile icon > thanks, got it

@Andrew Heard
deletion of internal profiles is indeed not possible and won't be in the future. I need to keep base profiles available because they serve as a fallback (based on categories) in case of any problem with custom profiles.

What is anyway doable and what I've expected you (all here) will want, is an option to hide them from the selection. I'll look at it ...

Categories ... this is used not just as visual separation of profiles, but also internally to know, which profiles are "similar" and may be selected in case, any custom profile has a problem. What category are you missing?

UI problem on screens ... hmm, will check it, thanks.

@freischneider
"Other" category ... right, it is visible currently only for manual drawing, because this does not belong to any other category. Making it as selectable option should help right? Hmm ...

@Tapio
the stuck on the loading screen was with the latest X.10 version? Hope not 

@slarti76
not exactly overlooked. I wanted to answer later and forget. Thanks for the reminder!
As I see in the code, this was modified at 31. 10. 2022 and it works as it should: the second part of the route should have time of this first trackpoint. Anyway, there is the condition when this is applied: "Created time" of the original route is identical to the first trackpoint. Is this your case? Otherwise app considers the original route time more important than trackpoint times and preserves it.

[@freischneider]

@freischneider
Map content panel > it is probably the same issue as reported by Andrew here right?
May someone of you, enable (long-click on the main menu) logging to the file + "Initialize" logs, close the app, re-start and open the side panel again? In the log (placed in the app "logs" dir) should be useful info, I hope. EDIT: I was able to simulate it on older SGS2. Big-fix will be today, thanks.

@balloni55
"enabled: false" is the problem. You have to enable it so Locus Map has full filesystem access. One option is to open the menu > Settings > Backup & Filesystem > File system manager > and here should be a blue box at the top with the "Grant permission" button.

@T-mo
- access to routing settings > and is it useful at all? I expect, that you want to modify profiles mainly in the route planner. There is no big reason to do this outside of this screen.

- extra parameters for router customization: here is a topic, where @Radim V will gladly discuss anything 

- missing icon: thanks. Partially fixed, anyway solution is not ideal now. If you change a router, the custom icon will be lost. Will have to improve it later.

- recently used: I've improved default selection a little, thanks

@Andrew Heard
1. + 2. above

3. hmm this is connected to "App is not yet fully initialized" error. We have to solve this and ...

[New Beta version 4.19.0.7]

Hi guys,

I have a feeling, that I do not spend enough time here on the forum. Sorry if you feel the same. The tasks I did last weeks took too much time to me and colleagues 

Anyway, here we go!

It is partially funny, that the last posts are focused on the customization of profiles. Well ...


New Beta version 4.19.0.7

Major changes

- internal offline LoRouter and online LoRouter are fully united. So they use the identical system. All customizations, systems for warnings, profiles, etc., all are identical!

- with this, I've made completely!! new system of how routing profiles are selected and also customized. Because the old system was a little "hacky", the new was rebuilt from scratch. This also means (and I've tried to keep old data), that you will have to setup custom profiles again, sorry.

- The second major (mainly on the background) change, a few weeks of work and testing, is a united and simplified system of how the app starts and destroys. Together with it, we have recreated the start screen and made it a little "nicer". The main reason was that it was quite a mess inside of the app over all these years and I had to have a single place of truth where all happens.

Both main changes are very complex and I also expect that some problems may arise. That's why I kept old Beta version on the Google Drive, so it may be easy to revert to the older version in case of serious problems.

So shortly: kudos to the brave and test at your own risk  !