Messages

These were quite long two months. It is probably for the first time, I publish a version after such a long time since the previous release. Last two days I spend by fixing various problems we found and just now, the new version was published on Google Play.

We have an option to publish version only for certain part of users (probably random selection). So today, it will be only for 10% of users. If there won't be any unsolvable problem, I'll enable version for all users tomorrow. Thanks for understaning.

And mainly thanks for the help. Update of map system was a big task for me and I'm really glad, version with this change is out. Now we can fine-tune it .

Got it, perfect, thanks.

Btw, for video, most of us here usually use the very nice tool: https://play.google.com/store/apps/details?id=com.hecorat.screenrecorder.free . Might find useful ...

[@erfi]

@erfi
thanks, you are correct. "Walking" was dependent on speed, but "Hiking" no. It was hardcoded to a single value per km. I've improved it and based on information I've found, changes are: "hiking" will use same values for computing of energy consumption like "walking" + 15%, which should be equal to carry 5kg backpack.

@Žajdlík Josef
hmm. Even with Czech description, I do not exactly understand where is the problem. Should be possible to create a short video of this problem? Thank you!

Uff so seems good news, thanks guys.

What I have found and fixed since 3.37.2.13

• sometimes not reliable "hold map center"
• still visible LoPoints after switching from LoMap to different map (needs a better approach in future)
• not working LoPoints attached to any other vector map (V4 OAM for example). Now it works as well.

[@0709]

@0709
Heh, same as in my answer 11 days ago on the help desk, I mix two cases, sorry .

We talk here about recalculation, so I again wanted to say that for point-priority, via-points are must-pass.

Anyway, new version 3.37.2.13 just published and it should solve
a) issue with via points & route-priority as in attach file (thanks for help)
b) added hopefully nice tool that should prevent recalculation back if user ignore "turn back" 2 times. So if you ride forward, app two times recalculate back and you still ride forward, 3rd recompute should be forward and not backward.

Hi,
package!
"menion.android.locus" > Locus Map Free
"menion.android.locus.pro" > Locus Map Pro

Yes, I'm seriously thinking about it and I already have a solution in the head.

[@michaelbechtold]

Hmm, this one will be complicated, sorry for this.
It's some weird problem in Kotlin language and I have no idea why it appears now and how to solve it. I'm playing with it since morning and I'm unable to simulate it on own devices > so I'm unable to verify if some changes fixed it. Anyway, I updated a few core libraries that create required apk file, so we will have to give it another try with version over Google Play. Thanks for understanding and patience.

@michaelbechtold
I may check the scaling of overlay once more, but I think it works correctly now. App no longer works with "zoom values" as are stored in SQLite database. In map core is so called "zoom scale" parameter and app try to find best available tile zoom to display. Hmm, I'll maybe try to write some blog post with explanation of this system.

@Žajdlík Josef
reset of auto-zoom was mentioned in app news.
I've made now conversion of old values, but still highly suggest to check results, because conversion won't give 100% correct values. Old stored zoom value can't be 1:1 converted to the new value.

@tramp20
funny. I made no change in the auto-backup system

@zossebart
Android 4.x was my pain for maybe 2-3 years. With Android 5.x I have no single problem, all works as I need. So I can't imagine a single reason why to drop support for these Androids. Something will come, but definitely not in the nearest years.

Every app has its a visible name like "3.37.2" but also need a special "version code" number.
In the case of Locus Map, I increment it by 1 with every public update (also Beta versions). So now it is public version 827 since I started to work on Locus app .

Snad máme vše popsáno zde: https://docs.locusmap.eu/doku.php?id=cz:manual:user_guide:tools:dashboards#dashboard

Zdravím,
tohle bohužel aktuálně nejde.
Celá ta navigační obrazovka doufám že již letos dozná zásadnější změny a lépe viditelné informace jsou jednou z těch hlavních.

Dočasné řešení je možná nadefinovat si vlastní Dashboard který zobrazí co je potřeba dle vašeho uvážení (pozice, velikost atd). Pak tam sice bude viset ten horní panel s malými údaji ale jak jsem psal ... věřím že to je dočasné řešení. Díky

[@michaelbechtold]

@michaelbechtold

Downloaded map: W1-8-MBt.mbtiles
Version: new Beta 3.27.2.10

Original map
screen: map_v1.png

Modification
image: map_modification.png

Result, modified map
image: map_v2.png

New scale system is multiplied by this 0.25 value, so app uses two fewer zooms. Anyway, the result won't be the same on all devices because the original scale is still defined by device DPI. Which is absolutely logical and something I really do not want to change.

Yes John, it is a different story. Emux is quite hard working on VTM & MapsForge system so it is used as a core map engine in his apps.

I can't imagine how to use it in Locus Map, sorry. Using of rendered tiles from MapsForge library is one thing, using a complete map system as a base for the whole application is something completely different.

Hi Andrew, thanks for the video.

In your case, it is "sound disabled" and also "vibrate disabled"! Locus Map should display warning "no notification enabled", that is already fixed in Beta.
Reason? You may want vibrate but no sound or opposite.

Sent from my Pixel 2 using Tapatalk

[@CabrioTourer]

@CabrioTourer
thanks for dashboard file. It helped and issue found & fixed

Well, navigation in the app is somewhere ... in the middle. It works well in the case, you ride based on instructions correctly along the road. But once something happens, like a shortcut, change in directions, pause in GPS signal ... bad things sometimes happen.

I currently have priority in finishing updates in improved map system, anyway the number of complaints on navigation is growing so rather start now and improve it till the main season starts .

@jajaballard
ah damn, thanks, fixed!