Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Menion

#166
Troubles & Questions / Re: possible memory leak?
March 23, 2023, 14:26:47
Ah, thanks balloni for the reminder ... visible truth is that I've forgot about it. I remember I tested it and noticed a very similar (not so critical) problem, but even after some testing, I wasn't able to find out why this happens.

Hmm ... complicated problem.

I may only add it higher in the never-ending list of priority tasks.
The following users thanked this post: balloni55
#167
Hallo Leute, bitte denkt daran, dass die "Voreinstellung" keinen "aktiven" Status hat. Wenn Sie auf eine "Voreinstellung" tippen, wenden Sie nur eine Reihe von vordefinierten Einstellungen an und das ist alles. Die Voreinstellung ist nicht aktiv und alle Änderungen in den App-Einstellungen haben keine Auswirkungen auf die zuletzt verwendete Voreinstellung. "Voreinstellung" = einfach schnell mehrere Einstellungen auf einmal ändern, mehr nicht.
The following users thanked this post: freischneider, kodela
#168
Hello,
this really looks like a very aggressive battery optimization on your device. If you need to start navigation again manually, this may only mean that the system killed Locus Map while on the background.

Suggest checking this nice website and check tips for your device. Hope this helps.
The following users thanked this post: mlun58
#169
Hi guys,
seems that IGN changed the certificate to access their services that are not natively supported on some Android devices. It needs an updated version of the Locus Map app. Sorry for this.

I'm not sure if I'll be able to publish a new version this week, but there will definitely be a stable Beta version that may be used instead.
The following users thanked this post: tannenzäpfle
#170
Another two tiny issues, with a major consequences, were found and fixed:
- on some devices, the app did not record any points (because of problematic detection of correct point precision)
- and also someone may suffer from slow GPX import

Uff, so another version was published. This one was not planned and already contains more untested code than I would like. Anyway, it's out ...
The following users thanked this post: Tapio, Andrew Heard
#171
Right. We've tested it quickly with Petr and had positive results.
The following users thanked this post: michaelbechtold
#172
Hmm, I've just created and published the new Beta version, but this, already fixed, is not yet there.

So next beta is during the week ... I'm also curious :)
The following users thanked this post: Andrew Heard
#173
@luce
Improved sharing & generally better work with points & tracks at once ... this is something we started work on last year, also because of the new iOS version. Not sure if results will be available this year on Android, but for sure next year and it will be a really nice big change ... you will see  ;)

@Mick FU
settings of paired sensors are already backed in the "Backup of settings". There is most probably the problem in restoration, that the app may not always correctly detect sensors under the old known "ID". So it is harder to solve.

@Tapio
long click to delete attachments does not work? Anyway, there is no way to exclude links automatically. You may edit GPX manually ...

@CabrioTourer
Navigation commands > should be hidden. If they aren't it usually means, that for some reason, the connection between the track and these waypoints breaks and they are no longer considered as navigation points, but ordinary waypoints. ... ah, seems you find this. The question is why and how this happened.
The following users thanked this post: luce
#174
So update ...

The "text-align" parameter is not necessary as it is already included in the "position" parameter. There is just a small issue that was just fixed and if confirmed, will be in the next version as well.

How "position" works together with wrapping may be visible in the new pull-request here.
The following users thanked this post: michaelbechtold
#175
Ah got it. Problematic wrapping in the latest app version was found & fixed, thanks!
The following users thanked this post: karlchick, Tapio, T-mo, Andrew Heard, LocusUser#1
#176
The setup of the guidance line is in the app settings > Guidance > Appearance ...
The following users thanked this post: Will C
#177
Thanks for the route. It was a different one in the first post.

Anyway even here is also a clearly visible problem, so thanks. I think I've found one obvious problem (with the incorrect sum of the used distance for computing of the slope) and after the fix, I have these results (screen).

And now tell me ... is it wrong? Because here are the changes registered by the algo:

addElevationToStats, distance: 858.5077, elevation: 5.119999237060547
addElevationToStats, distance: 588.86194, elevation: -5.02999969482422
addElevationToStats, distance: 1270.1581, elevation: 5.179999084472655
addElevationToStats, distance: 411.74136, elevation: 5.209998779296875

It simply displays that after the first 858m, elevation change was finally above +-5m, then -5m after another 588m, etc. In the end, changes are so small, that distance up/down are simply = 0m! And I think it is correct.

App requires at least 2% slope change to be registered for up/down distance. So at least 2 metres change per 100m!

@Michael Bechtold
and here is the problem. I really do not want to have this parameter customizable. The main reason is to have exactly the same algorithm (results) on all three platforms. So track re-computed on the web after sync should be able to get identical results (that does not happen now).

@lor74cas
thanks. But it was worst before I believe  :). You may also find apps that will have a higher values...

The difference 14% is not bad. Anyway best is to get better results of altitude values instead of tuning algorithm that filter these values. So suggest checking the "replace of SRTM data" or "Pressure sensor" values in the Altitude manager.
The following users thanked this post: lor74cas
#178
Hi guys, nice bunch of ideas, thanks. So when I noted and analyzed all, seems that we have here four major categories
  • better work with online/offline LoPoints
  • robust search system
  • dashboard improvements
  • geocaching features

Where
2. search system is currently (already for a few months) in massive rework. During the next week or two will be in Beta a completely new online search. More about it later ...

LoPoints & Dashboard are very high on my priority list, so definitely something I would like to work on this year.

And geocaching ... good question. Will have to think a little more.

---

Other smaller tasks
- backup system: agree, I'll look at it soon
- 3D maps: huge amount of work that still does not worth it I believe
- recording statistics: I would love to see them too, but we are not the majority :)
- live tracking: I know, sorry @joeloc. This has to start with a rework of our old server and uniting it to a new web.locusmap.app site. I'll try to push it a little more.
The following users thanked this post: Andrew Heard, freischneider, luce
#179
Yes, engines for LoMaps and OAM will be the same. And current Locus Map has already a highly enhanced MapsForge library version. I'll inform @voldapet about this, because we were playing with word wrap and ...
The following users thanked this post: karlchick
#180
Tasker / Re: Locus Tasker addon not working
March 09, 2023, 12:46:53
I'm not much skilled with tasker (unfortunately), but a simple task I made to execute quick bookmark, seems to work as expected, interesting. Do you think there are exact steps I may try to simulate this issue?
The following users thanked this post: Tapio