Locus Map - forum

Development => Versions => Topic started by: menion on March 18, 2019, 14:52:24

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on March 18, 2019, 14:52:24
Important links
- blog post (http://www.locusmap.eu/news-version-3-37-0) about major version
- list of news (http://help.locusmap.eu/announcement/version-3-37-18-3-2019) of public versions

Versions
18. 3. 2019 - Locus 3.37.0
20. 3. 2019 - Locus 3.37.1
27. 3. 2019 - Locus 3.37.2
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on March 19, 2019, 00:29:44
quote from @Menion - "interesting, I can't simulate it with any folder. Does this happen to your will just a single folder with tracks or will all you checked?"

I just confirmed on 3.36.2.14 for 3 different folders. Summary - displayed distance is 0m when sorting by  Nearest, but non-zerp & correct when sorting by distance to Starting Point.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tapio on March 19, 2019, 08:30:51
I'm too stupid to find changes at all... Where are the options for GPS filtering? I was not quite sure if the GPS filtering were in "GPS and sensors" before.

- I like the new track sort menu.
- Elevation gain per km would be more useful, we already discussed it
- mf4 themes still not in presets
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on March 19, 2019, 12:50:40
quote from @Menion - "interesting, I can't simulate it with any folder. Does this happen to your will just a single folder with tracks or will all you checked?"
... displayed distance is 0m when sorting by  Nearest, but non-zero & correct when sorting by distance to Starting Point.
Exactly as Andrew describes for me too
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on March 20, 2019, 01:20:20
Where are the options for GPS filtering? I was not quite sure if the GPS filtering were in "GPS and sensors" before.
I thought it was in the hidden "expert menu". Maybe it now replaces the previous filtering setting in GPS and sensors > Altitude Manager > Altitude Filter?
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on March 20, 2019, 09:28:47
Where are the options for GPS filtering? I was not quite sure if the GPS filtering were in "GPS and sensors" before.
I thought it was in the hidden "expert menu". Maybe it now replaces the previous filtering setting in GPS and sensors > Altitude Manager > Altitude Filter?
I think the GPS position filtering has been moved from ( by default hidden ) expert menu in LocusMap Beta to GPS and sensors  menu. The altitude filtering in the GPS and Sensors/altitude manager  has its own independent filter.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on March 20, 2019, 13:06:17
Thanks for feedback guys. We have found one big issue when downloading new maps from Store and also a stupid issue for new users where app creates new track database, so bug-fix version most probably today.

Thanks all for the feedback for our new Live tracking web. It is work in progress > so I've collected all your good ideas and notes to the text document and will grab from it important points to change in next step. The web page is made for us by an external company so changes won't probably be as fast as are in Locus Map.

Anyway a few points:
- top panel in the browser: agree, the map should be close to "full screen"
- not updated data? Hmm nice bug, will check it
- live chat on the web: in current top-priority road plan. Anyway in the first step read-only on the web. It will require login on this web with the same account as in the app etc. so this later.

@Andrew Heard and @john_percy
really interesting problem with these zero values. All my devices display correct values, Petr, Milan and Michal (so whole Locus team work on this :) ), tested it as well and we all see correct values. Same with the latest version? May you send me a complete backup (over backup manager) so I may try to simulate it? Thanks!

Missing "filter" option: as Libor correctly wrote here (https://forum.locusmap.eu/index.php?topic=6502.msg54570#msg54570).
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on March 20, 2019, 15:32:41
@menion @Andrew Heard
It would appear that this is connected with certain historic data.
- Some tracks show zero distance away when sorted by "nearness" but some do not.
- For some of these "zero distance" tracks, clicking on the mini-map to move to the track's location and display it means that the distances are correct on reopening the tracks screen. However closing the app and reopening it resets distances to zero, as does re-sorting the tracks or moving to current location.
- For others of the "zero distance" tracks, the above has no effect.
I'll email my backup.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on March 20, 2019, 16:33:43
@Andrew Heard and @john_percy
guys, it is really necessary to live in the area with negative latitude or longitude? Next time, choose better and live in middle Europe ;). Thanks John, fixed :) (thanks to your backup)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Christian on March 20, 2019, 23:15:40
Quote
chg: permanent display of elevation gain in list of tracks
Thank you.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on March 20, 2019, 23:30:27
I'll email my backup.
Thanks John. I would have taken all day+ to upload my 86MB backup (if it worked at all).
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tapio on March 21, 2019, 08:37:08
Can you allow maps to be part of presets, just like themes?
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on March 21, 2019, 09:29:24
Following a map link from Google Trips, I am offered Open in [Google] Maps, Open in Chrome, Open in Locus [Free] but not Open in Locus [Pro]. I have the latest version of both, so the inconsistency is strange.
Furthermore, it doesn't open in Locus Free but gives a red toast complaining of unsupported file format.
Also, as you will see, the message on the toast is very hard to read!
(https://uploads.tapatalk-cdn.com/20190321/ac21fad2c41b256283c6e87e8ea12bcd.jpg)

Sent from my moto g(6) plus using Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on March 22, 2019, 11:23:27
@tapio
best to vote (https://help.locusmap.eu/topic/add-map-to-presets) and hope :). Update in presets will have to wait a little.

@john_percy
interesting, I have no explanation for the different behavior of both versions. I'll check your format visible in almost invisible text. It should be possible to fix it, thanks!
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tapio on March 22, 2019, 17:28:55
Used LT a bit when walking with my dog.

Changes to an actively running livetracking profile should instantly apply. I added a beep notification, but it only worked after restart of the LT profile.

Also. I am not sure. Maybe stop of recording should not necessarily stop LT.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: lor74cas on March 22, 2019, 18:58:54


Also. I am not sure. Maybe stop of recording should not necessarily stop LT.

Tested in my case run rec profile with LT if I  stop recording also LT stops.
If I stop LT the rec continues.
For me it's ok.



Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: LocusUser#1 on March 23, 2019, 11:15:20
Quote
In the track list, only zero is displayed for all values.
When editing a track or new recording a track, the correct values are displayed.

@LocusUser#1
ah thanks, got it, should be fixed

The bug is still present in 3.37.1

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on March 23, 2019, 12:59:04
However, the zero distance bug has gone now for me.

Sent from my moto g(6) plus using Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tapio on March 23, 2019, 19:27:04
Track manager. Sort by distance to start point, weird behavior? Sometimes sorts by distance from map center, sometimes from GPS position. Will observe.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tapio on March 23, 2019, 22:10:09
Same happens with POI search. First I added 100 Poi from map centre, then re-entered the poi window and it showed poi from the gps centre, not map centre.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on March 23, 2019, 22:20:55
However, the zero distance bug has gone now for me.
fixed for me too; I can't find any problems with other track sort methods
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tapio on March 24, 2019, 11:55:12
LT: user defined ringtone sound on failed position send does not work. After select of sound it seems to forget it. Play button does not play sound.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on March 24, 2019, 20:26:01
@tapio
interesting that setup of notification for LT does not work immediately. You tried Locus based live-tracking or "custom"? I'm testing it and it seems to work correctly.

LT starts automatically only in case, you have this set in track recording profile. In this case, it also automatically ends when you stop track recording. Not otherwise.

Sort by distance in track manager: last known location is GPS? Use it, otherwise, map center is used. You have GPS enabled in Locus Map?

Custom sounds for LT notifications: issue found, thanks!

@LocusUser#1
please double check you have latest version 3.37.1, thanks

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tapio on March 25, 2019, 07:02:17
-LT: I use Locus LT, I tested, you are right, it works.
-Start- and Stop behaviour is perfect, you are right.
- I was under the impression it always searches poi only at map center, which I'd prefer. Ok, it's different. I need to turn off gps at times. I wish Locus had a simple on/off toggle (with no intermediate gps window)[1].

LT web interface not working on existing private group:
- I have a private group setup, LT is running, LM shows the sent position via icon. But the web interface does not show my position. Just the map. It does not seem to work currently. It only shows the correct group name.
LT notification bar says it has sent 30 positions.

[1] I see, you have declined the idea 5 years ago, but I thing GPS on/off is much more needed than the full GPS window. An additional button is needed :-)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: LocusUser#1 on March 25, 2019, 18:47:05
@LocusUser#1
please double check you have latest version 3.37.1, thanks

Yes, version 3.37.1.
Here you can download my last backup if it could help you.
https://drive.google.com/open?id=17GDDxR4Wls1p1A3XIL535QoOq63wcO_6 (https://drive.google.com/open?id=17GDDxR4Wls1p1A3XIL535QoOq63wcO_6)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on March 25, 2019, 22:05:33
@LocusUser#1
weird problem. Seems in your database was incorrectly stored statistics for tracks, do not know why. So I've updated them manually. I've shared your track database (place it to Locus/data/database) over PM (personal message) here at forum. Let me know if it works correctly.

@tapio
issues related to LT web, or generally to some generic problems with LT in Locus (not directly related to some quick changes in beta version ... hard to decide, I know), post it here: https://forum.locusmap.eu/index.php?board=60.0 . It should be useful to have this on the same place, mainly because I've made Milan responsible for whole Live tracking feature, so it will be easier for him to track this on simple place. Thanks for understanding!
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on March 25, 2019, 22:34:31
[1] I see, you have declined the idea 5 years ago, but I thing GPS on/off is much more needed than the full GPS window. An additional button is needed :-)
@tapio - the GPS button has a long tap menu --> Turn on/ Turn off. Good enough? I only discovered this feature myself while writing this post. Useful for me too.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tapio on March 26, 2019, 07:21:23
@tapio - the GPS button has a long tap menu --> Turn on/ Turn off. Good enough?
Ah, I tested it before, but overlooked the menu entry. Just thought there is the normal context menu. Thx yes, good enough.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: LocusUser#1 on March 26, 2019, 19:56:42
@LocusUser#1
weird problem. Seems in your database had incorrectly stored statistics for tracks, do not know why. So I've updated them manually. I've shared your track database (place it to Locus/data/database) over PM (personal message) here at forum. Let me know if it works correctly.

Thanks for your work, now it works correctly.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on March 27, 2019, 13:18:19
Aaaaand, new version 3.37.2 is out :)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tapio on March 27, 2019, 18:26:34
Thanks for the update.

Changes to the new LT password settings make my Locus crash. On a Sony Z1. Also, I have seen no effect on the web interface. No password needed.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: milan.cejnar on March 28, 2019, 08:11:03
@tapio
Could you please send me a more detailed description how I could replicate the crash in LT password setting or send me an android error log via PM, help desk or milan.cejnar@asamm.com?

Password should only be needed to actively join and track into the group. Following the group using web interface is still possible without the password if you know the group's code (i.e. access key).
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tapio on March 29, 2019, 07:51:32
Could you please send me a more detailed description how I could replicate the crash in LT password setting or send me an android error log via PM, help desk or milan.cejnar@asamm.com?
I check the password checkbox, enter the password twice, press confirm (or was it OK?) ... boom, crash. "Locus has stopped working" message box. German language: "Leider wurde Locus Pro beendet". Will send log later if I find the time..
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: milan.cejnar on March 29, 2019, 13:11:23
@tapio Hello, I could not reproduce the error unfortunately :( If you will find the time to send the log I would really appreciate it and it would really help to solve the problem. Have a nice day.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: locus.sv@heime.org on March 29, 2019, 14:45:37
- live chat on the web: in current top-priority road plan. Anyway in the first step read-only on the web. It will require login on this web with the same account as in the app etc. so this later.

It would be nice if it was possible to chat with someone anonymously if they have the link to the private room.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tapio on March 29, 2019, 20:16:30
@tapio Hello, I could not reproduce the error unfortunately :( If you will find the time to send the log I would really appreciate it and it would really help to solve the problem. Have a nice day.
Please point me to how this can be done, I think think there was some info here on the forums...
edit
got it. https://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: TimoG on March 30, 2019, 20:05:35
In the current version crashes locus when creating a geocache waypoint.  :(
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: balloni55 on April 02, 2019, 12:42:14
verifying
https://help.locusmap.eu/topic/anzeige-von-wegpunkten
i´ve activated menu/settings/geocaching/autoload all waypoints and checked "each"
BTW for me it work as expected ;)

 now i deselect all to get my normal view, but all WPTS are furthermore displayed, neither restart of Locus nor restart the phone solve it. WPTS keep "last state"
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on April 03, 2019, 13:37:40
@TimoG
may you please give me steps to simulate this problem? I have no success so far.

@balloni55
this function has an effect in the only moment: you load a point (cache) from your point list. Every geocache has internally stored the list of waypoints that the user loaded last time. This list is restored plus! every waypoint type that is defined in this list. I believe this is a logical solution because you a) always get same waypoints you had last time and b) additionally new waypoints if some new condition in this "auto-loading" system is enabled.

I hope that this really works that way, it's some time I write this piece of code :).
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: balloni55 on April 03, 2019, 14:00:01
Quote
I hope that this really works that way,
of course
but my problem is, all WPTS are visible on map although non is furthermore selectet inside 
menu/settings/geocaching/autoload all waypoints

Should i open each Geocache to disable visibility of WPTS????

I expect after disabling all setting checkboxes no WPT is visible on map.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on April 03, 2019, 14:38:45
Hmm to hide waypoints, best, for now, is to use "Hide all temp map items" function. Good old hidden unflexible function :)
As I wrote, this setting is applied only when you load caches. Seems you expect more some general settings that simply say "which cache waypoints are visible" (for all caches).
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: balloni55 on April 03, 2019, 18:40:15
Quote
Hmm to hide waypoints, best, for now, is to use "Hide all temp map items" function. Good old hidden unflexible function :)
thanks, this help ;)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: balloni55 on April 13, 2019, 14:21:34
Link inside this Listing to download cartrige is not clickable
https://coord.info/GC8570Y
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on April 13, 2019, 18:24:13
Hello balloni55, interesting. If you download this file in GPX file, you may see

Quote
<groundspeak:long_description html="False">

And text with links as

Quote
Hier geht´s zur Cartrige:

http://www.wherigo.com/cartridge/details.aspx?CGUID=dcdcd2ff-c171-4487-93bc-678f6d03ac4f


Ihr seid im Besitz einer "Reverse-Cache-Box", welche euch keine

So really, no html code. Seems that it's on the application to detect this and modify listing to offer clickable texts. I'll look at it, thanks.

EDIT: nice, fixed and confirmed over direct download in WhereYouGo app.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: slarti76 on April 15, 2019, 15:31:29
Dunno how long it's been like this, and if it's a bug or a feature:
When I lock the zoom level and zoom out, I cannot zoom out below 100%. Some while ago, it was possible to zoom out to <100%, so you could see a bigger area of a more detailed high resolution zoom level. Granted, at some point the repainting of the tiles got reaaaally slow, so I can imagine that might have been a reason to disallow it. However, I think it would be unproblematic and still usable if it's at least allowed to zoom out to 25%.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on April 17, 2019, 00:04:06
Hello slarti76,
hmm, what is your settings > maps > advanced features > Increase map resolution?
Seems this setting affect lower limits of "zoom lock".

I believe that in the special alpha version we test here on the forum (https://forum.locusmap.eu/index.php?topic=6471.0), this issue no longer exists.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tapio on April 20, 2019, 13:16:50
For whatever reason it sometimes shows 0m track length and elevation gain. Which is wrong, see attachment. I did some track splits before.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on April 20, 2019, 17:57:08
Hello Tapio,
this issue happens when you move a track between folders and probably also when you do some advanced edits. In the next version, this should be fixed. Sorry for this.
Title: Re: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Christian on April 20, 2019, 20:49:38
This happens also to all tracks which exists before the Distance, elevation gain a.s.o are displayed in Track Manager. When tapping more -> add elevation then the values of length and ele. gain are displayed in Track Manager.
Menion, would you please provide an action or a script doing this automatically? For all these thousands of tracks generated before....
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on April 20, 2019, 22:04:30
Thousands? This happens for all of your tracks? I tough we solved one similar issue in the latest version, so this should happen only for newly modified tracks!

With my work on many places last weeks, I have little mess in head what and where is already fixed. Anyway, I'll definitely publish regular Beta version next week, so if with this beta problem still appear, I'll add into the app method to fix this problem for the whole database.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on April 21, 2019, 00:56:42
general sorting/ searching questions (3.37.2 Pro):
I don't know whether the previous posts regards search/ sort are related to my experience, but when I do a global Search in Tracks from the Track screen, with no entered fields, I get a list in some somewhat random order, but the longest tracks are displayed at the top of the list. How is this list sorted? In my test (attached) the tracks at the top of the list are 1000's km away. Note GPS disabled.

If I enter partial text in optional Search Title, the search order still doesn't make sense to me.

So when I sort tracks in a single track folder by Nearest, what is the blue "nearest" distance? If I turn off GPS and move the map center to a position that only passes through a single known recorded track (600km ride), it displays the distance as 64km away, although the order is correct, could the distance be to the start of the track instead of the current position? Sorting by all other means works perfect for me except Nearest.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Christian on April 21, 2019, 18:01:00
Thousands? This happens for all of your tracks? I tough we solved one similar issue in the latest version, so this should happen only for newly modified tracks!

With my work on many places last weeks, I have little mess in head what and where is already fixed. Anyway, I'll definitely publish regular Beta version next week, so if with this beta problem still appear, I'll add into the app method to fix this problem for the whole database.
Only edited / Brouter-generated Tracks has elevation in my tracklist. The other thousands not :(
Yesterday I found a track which did not have a distance value in track list. May be there are some more...
Version is 3.37.2.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: slarti76 on April 21, 2019, 22:08:03
Hello slarti76,
hmm, what is your settings > maps > advanced features > Increase map resolution?
Seems this setting affect lower limits of "zoom lock".
Yeah, I got that activated.

Quote
I believe that in the special alpha version we test here on the forum (https://forum.locusmap.eu/index.php?topic=6471.0), this issue no longer exists.
Didn't have the time yet, but will try out on the next version.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: slarti76 on April 21, 2019, 22:11:46
I reported that before: Almost every action in the track editor leads to a "Process successful" message that stays on for several seconds, which is far too long and covers the < and > buttons. I think you only removed this for "Delet point", but not for the other operations.
Honestly, I don't see the need for this message at all - the user can see the result of all these actions immediately. If I delete a text in Word, it also won't tell me if it succeeded, only if there was a problem.
If you still want to keep the toast, please make it smaller so that the back and forth buttons are usable again immediately.

PS: Also, I again and again get the "To edit the track, tap it" message. Why? Been using the editor for hours and still get it.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on April 22, 2019, 06:45:58
@Andrew Heard
hmm firstly because in the search screen is in "Track around" visible "My location", it means you have GPS enabled, at least Locus thinks it. Otherwise "Map center" should be in this field.

In sort by nearest, the same system is used. So if GPS is enabled, the last known location is used, otherwise, map center is used.

To be true, I see no reason why it should give incorrect results, just check this GPS on/off state, thanks.

@Christian
if possible, wait on next Beta or new version. This is a solvable problem, so no worry.

@slarti76
funny comparison to Word :). Oki agree, messages removed.

"To edit the track, tap it" message also inform that there is no activity running. I do not see a problem with this message to be true.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: michaelbechtold on April 22, 2019, 09:36:17
Hi Menion,
the meaning of "incorrect" is defined by the PURPOSE of the search.
A pretty usual scenario I am used to is:
1) you are on the ride, have a quick break
2) you plan to be in a place 30km away as next target
3) at the break (#1) you think about what to do after the next target
Currently you have to live with irrelevant data, based on your GPS position - OR have to switch off GPS, etc., etc..
4) and finally you forget to switch it on again :-((
What about a radio switch "from: GPS / Map Center" ?
All users happy for any scenario :-))
Cheers
Michael

PS: heading to Karlovy Vary in an hour from now - any hints for this region ?

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on April 22, 2019, 09:45:32
Hmm "nearest" in sorting of tracks should really be nearest. Even a "map center" used in case of disabled GPS is little weird (most probably should be "last known GPS location").

For your use-case, best should be to use "search" function where is really easy to change from GPS to "map center" (just two clicks).

Hmm area of Karlovy Vary, do not know this are well, but definitely city & castle Loket (https://www.google.com/maps/place/Loket/@50.1716151,12.7485216,13z/data=!3m1!4b1!4m5!3m4!1s0x47a0908e5ac04d57:0xb5a56985e4d5c522!8m2!3d50.1860116!4d12.7540621) . There should be also very nice path between Loket and Karlovy Vary along that Ohře river (hike & bike).
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on April 22, 2019, 09:58:42
I have New Point enabled in the side menu.
1. Move map to location of interest. Tap on New Point. Note Save is on top bar of new screen, so should be safe to back out of this screen. Back out. New point saved at current location and map moves there. Lose place of interest. Not what I wanted at all. Bug.
2. Move map to location of interest. Tap on New Point. Fail to note that middle of screen says Current Location (not Map Centre). Save. New point saved at current location and map moves there. Lose place of interest. Not what I wanted at all. Either should remember previous user choice or default to Map Centre.

Conceptually this relates to the discussion of "nearest" above. The question is "Where are you interested in" - where the map is showing or where you are physically. Using the model of paper maps, if you are using a map you are *always* interested in where the map is showing.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on April 22, 2019, 09:59:15
Hmm "nearest" in sorting of tracks should really be nearest. Even a "map center" used in case of disabled GPS is little weird (most probably should be "last known GPS location").

I think "would be nearest" approach explicitly given by the map center is legitimate, no matter if GPS is on or off.

One is not always interested in things related to the current position.

If the map center and GPS position match, then OK, I want the nearest.

If they do not, or location is unknown, I  want to pretend the map center is my position.

Before the searching, I can always rematch the screen with GPS position by the button, or, as fallback, would be good to rematch it with the last known position.

Odesláno z mého Mi A2 pomocí Tapatalk
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on April 22, 2019, 12:13:02
hmm firstly because in the search screen is in "Track around" visible "My location", it means you have GPS enabled, at least Locus thinks it. Otherwise "Map center" should be in this field.

In sort by nearest, the same system is used. So if GPS is enabled, the last known location is used, otherwise, map center is used.

To be true, I see no reason why it should give incorrect results, just check this GPS on/off state, thanks.
@menion - GPS was off. My 1st screen cap for "Track around" shows furthermost tracks sorted to top of list. But the distances are not even strictly descending.

The tracks sorted by Nearest show a weird distance in blue. All of the distances should be close to 0km because all the tracks originate at my house where the GPS position has been set. Locus, or my understanding, is not right.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: slarti76 on April 23, 2019, 08:56:46
@slarti76
funny comparison to Word :). Oki agree, messages removed.
Great, thx! Always happy to make a convincing argument ;)

Quote
"To edit the track, tap it" message also inform that there is no activity running. I do not see a problem with this message to be true.
After writing this, I realized there's two of those: There's a banner below the header that has this message, which takes away a little bit of screen real estate, but OK. Wouldn't mind it to have an "X" to close it on my small outdoor phone... No need for storing a default setting there, just that you can remove it once per session.
But there's also a toast with the same message. I actually don't know quite when it appears, but I assume it shouldn't be too hard to find in the code. It's orange, I think. If there's already a banner, there's no need for a toast, is there?
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on April 23, 2019, 13:02:29
@john_percy
1. hmm point screen is really old and is on top of my priorities right after I get rid of map & LM4 stuff. In the moment you do a tiny change in "new point screen", the back button is equal to "save". The correct system is made in "Track edit screen" and the same needs to be applied here.

2. look on this from the opposite side: on the trip, you are in an interesting place you want to save. And the fact you play with map does not change anything on the fact, that you stand on the place you want to save.

There are situations where the first or second option is useful. Currently, Locus Map use GPS if available. If you do not like this behavior, feel free to change it in the settings > points & tracks > new point default location.

Bringing a paper map to the digital world is not always ideal I think. Here (digital world) we have one powerful information you miss on paper map: your location.

@poutnikl
do you know any other application that sort data by the center of the map? At least Google Maps definitely do not do this. Locus is a little special here.

---

Anyway in config.cfg exists parameter "gui_data_point_list_sort_by_gps" that should affect this. Expect fact it is incorrectly named, it also does not work as expected in all cases, heh.

So in the next version will be in "expert settings" new "Sort data by" settings for this. As I see, we had to discuss this long time ago. My bad > default parameter is already set to "map center", sorry :). So I'll leave it as is.

---

So based on the above paragraph, an important change to keep system same (no matter what I think now): sorting of content in the app will remain by default by "map center". Searching, to keep consistent, will use the same settings, so by default, it will use "map center" as searching center-point. Global agree?

@Andrew Heard
hmm, if possible: give a try next Beta version that will come this week. If there will still be this problem, should be again possible to share with me your current track database + current map coordinates you have? Thanks

@slarti76
hmm I see where this "toast" appears, but to fix it correctly, I need to know steps to simulate it. It should appear only when you try to do something and by some accident, no trackpoint is selected (so it should work only as a rare warning in case of a problem).
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on April 23, 2019, 13:25:32


@poutnikl
do you know any other application that sort data by the center of the map? At least Google Maps definitely do not do this. Locus is a little special here.

No, I am not aware of it.

But it  makes sense to me as a non default option, similarly as it makes sense in other places like a favourite creation or navigation point setting.

I am not sure if to have it deep in advanced settings is flexible, OTOH nonGPS sorting is less frequent that the other cases mentioned above.




Odesláno z mého Mi A2 pomocí Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: slarti76 on April 23, 2019, 14:37:18
@slarti76
hmm I see where this "toast" appears, but to fix it correctly, I need to know steps to simulate it. It should appear only when you try to do something and by some accident, no trackpoint is selected (so it should work only as a rare warning in case of a problem).
Ok, will keep an eye out. Perhaps the toast does make sense after all, but it could also be related to the fact that I edited on a rather slow phone, I think it happens more often (or only) on that. Perhaps some race condition...
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on April 26, 2019, 16:38:10
Hi guys,
firstly I wanted to test big changes in map system privately a little longer but seems it is enough stable, to put it into Beta test.

So new Beta version 3.37.2.9.

The long list of changes after an update like usually. Major changes are related to a big rewrite of how app work with map files, with scaling system etc. More about it in the related topic here (https://forum.locusmap.eu/index.php?topic=6471.0). Version merges all changes I made in preparation to the new 3.38 version + half of year work on new map core.

Wish you nice coming weekend!

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on April 27, 2019, 00:19:56
As a result of the changed way the new beta deals with scaling maps for devices of different resolution, I've put together new versions of my Mapsforge version 4 compatible themes. They are effectively add-ons to the Voluntary themes. At present they are solely for the beta version and will simply not appear in the list of available themes in the current release, hence I have named them Voluntary Mapsforge beta and Velocity beta.
Download, unzip and add to your Locus themes directory.
Please let me know if they work for you.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: 0709 on April 27, 2019, 13:40:05
Report 3.37.2.9 test. Does not start on A4.4.2. Ok on A 5.1 and A 9.
Highly improved navigation "route priority" (auto) re-calculation.
First impression.
Had a single short testdrive using a simple (no roundtrip) track.
Comparing by Locus Pro on A 4.4.2 and Locus Free testversion by A9 Phone.
No differences in the navigation results. Both ok.

Disavantage by (auto) triggered recalculate systems is the original trackpath is (partly) lost after re-calculation. So would appreciate this 3 year old idea realisation. See any trackpathchanges by visual control.
https://help.locusmap.eu/topic/navigation-onscreen-trackcopy-of-original-planned-route
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: locus.sv@heime.org on April 27, 2019, 14:51:04
The new app works great and the maps are a lot better  :)

But it would be nice if you could find some time to fix another problem with the map. This is an old problem and not related to the new version.

If I rotate the map manually, this rotation is always reset if the screen is turned off and on again. The map is always with north up when the screen is turned on.

Maybe this is a feature and not a bug, but in that case, could you make it configurable?
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Viajero Perdido on April 27, 2019, 18:06:32
I really like the "tilt" feature.  But I suspect more people will accidentally activate it, then wonder how to reset it back to normal.

Maybe it could be a simple on/off setting, and in the UI beside "Rotate Map"?  (Then I'll know I've got it tilted the maximum; I'd never want it half-tilted.)

I can't repeat it now, but for a while, there was an unwanted panning of the map, after I turned the power off then on again.  This was both with screen lock active (swipe up to unlock), also controlled via "basic screen lock" disabled.  It looked like the swipe-up-to-unlock was being caught by Locus and used to pan the map, but then I saw it happen with screen lock disabled too, no swiping.  And now it's behaving perfectly...
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on April 27, 2019, 23:22:08
Got 3.37.2.9 today.
Love V4 support and big improvement in map texts. Great.

New map core isn't really fast on my OnePlus 6.I'm not sure how this will be on none high end hardware.

Sometimes map loading stucks for a long time. I did zoom change and movements.
Just for an impression some pictures. Shot after +30 seconds of stuck.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on April 27, 2019, 23:24:26
Sorry don't understand how to add attachments. Can't find an option (using mobile)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on April 28, 2019, 01:45:34
Got 3.37.2.9 today.
Love V4 support and big improvement in map texts. Great.
I've noticed a big improvement in map texts too. Now the obvious locality name is displayed rather than some obscure small place name (I've never even heard of).
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on April 28, 2019, 01:57:33
hmm, if possible: give a try next Beta version that will come this week. If there will still be this problem, should be again possible to share with me your current track database + current map coordinates you have? Thanks
3.37.2.9 - still same two issues with GPS disabled:
I will attempt to email combined GPX attachment to you...
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tramp20 on April 28, 2019, 06:39:18
Hi,
I am sure I missed something during the last weeks :-(
With 3.37.2.9 all of my vector maps (LoMaps, Outdoor, Classic OSM) are now without a theme, selecting a theme gives always "the actual map does not support themes".
This happens with Android 5.1.1 and 9.0.

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tramp20 on April 28, 2019, 06:52:02
And another bug with 3.37.2.9.
when I switch back from online maps back to offline then Locus beta crashes repeatedly. I sent you some minutes ago a feedback.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on April 28, 2019, 07:48:47
Don"t know if it's still on todo list or a bug. Theme switching when changing profile with V4 ML doesn't work. No theme available in profile editor.

Without checking new navigation V 2.9 is a big improvement.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on April 28, 2019, 20:20:03
 Preferences / Map Theme.  Click to select.  The list is empty.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: slarti76 on April 29, 2019, 08:32:41
I really like the "tilt" feature.  But I suspect more people will accidentally activate it, then wonder how to reset it back to normal.

Maybe it could be a simple on/off setting, and in the UI beside "Rotate Map"?  (Then I'll know I've got it tilted the maximum; I'd never want it half-tilted.)
With me, tilt was activated after first start, was wondering if that was a mandatory feature now. Then it was suddenly gone, didn't realize why and how and wondered how to get it back. Menion, this desparately needs some information popup or the like.

Anyway, "half-tilted"? I can only seem to get Full or None, no steps in between.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: slarti76 on April 29, 2019, 08:45:50
I stumbled upon the new Quick Action Menu. Did I miss something or has that not been mentioned here/in the release notes? I like it, but when is it planned to go live? Does look basically ready to me...
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on April 29, 2019, 12:08:13
I stumbled upon the new Quick Action Menu
nice find - looks quite useful
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: zossebart on April 29, 2019, 13:49:38
I stumbled upon the new Quick Action Menu.

It's already in Pro, just not the menu item. You can only fire it up via API/public intend in current Pro.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: balloni55 on April 29, 2019, 14:23:53
sorry i´m a old man
Quote
I really like the "tilt" feature.
where to find and how to handle?????
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: slarti76 on April 29, 2019, 14:33:04
sorry i´m a old man
Quote
I really like the "tilt" feature.
where to find and how to handle?????
Don't worry, nothing about being old, it's just not "advertised" at all. And it's no setting, just double tap and move fingers up or down. Actually kind of a "standard" gesture used by other map apps, too. As I wrote, should be explained to users.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on April 29, 2019, 14:33:17
Two fingers on map; drag down.
Two fingers on map; drag up to restore to flat map view.
Menon has said it's not yet working properly.

Sent from my moto g(6) plus using Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Viajero Perdido on April 29, 2019, 18:09:42
My apologies, I should have mentioned how to activate "tilt", rather than just leaving it as a mystery.

I was experimenting with zoom lock (after seeing it mentioned here; never used it before), and managed to get Locus into an endless rendering loop.  This is with an OAM V4 map, new "active RT4" theme, zoom lock on, but can't remember original zoom level.

The screenshot also shows, incidentally, the old glitch of not rendering areas with no content, those big rectangles.  But here, in a loop, Locus would render the screen as shown, then grey out the entire map, then render again as shown, repeating indefinitely.  It's a slow-moving loop, a few seconds each time through.

No idea what's going on here.  Maybe this is one of the problems with tilt that Menion mentioned...  EDIT: Removing tilt doesn't stop the loop, just speeds it up a bit.  :)  Turning off zoom lock doesn't stop the loop either, but then choosing a different zoom level does finally stop it.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: balloni55 on April 29, 2019, 19:12:03
with an OAM V4 map and General LoTheme
- each render ZL9 up to ZL14  takes 10-15 sec./screen
- zooming in and out few times only  check pattern is displayed >solution recall the map
- after some zoom in/out names aren´t displayed complete
- at ZL 11 and ZL12  names of big towns are displayed, but additional also all names or titles  including: german "insel" or name of an island "Reichenau" "Mainau"  or french "ile"
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: 0709 on April 30, 2019, 09:00:03
Q Menion.
A promising tool was tested in previous Beta versions.
"Long push" recalculates complete track (All segments).
Any progress ? 
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on April 30, 2019, 11:45:48
At least for me there seems to be a big issue in new map core.
Many graphical errors during navigation.
Navigation is more or less not usable.
I'm using V4 ML maps.
I uploaded an example video here:
https://app.box.com/s/xfaxre1nil8n3ljv07az9xtab2nmtpf2

There is a second video in the link which shows two things with map core during planing.
It's pretty slow on my OnePlus 6.Means with high end Qualcomm by 2018 and not so high display resolution.
. For me it's acceptable but don't know how it looks like on medicore smartphone.
It shows the stuck, too. (sec 20)

Last point: Is there an option to disable 3D view of map?
It might be good while navigation but not for planing.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: balloni55 on April 30, 2019, 12:50:27
Quote
Is there an option to disable 3D view of map?
@CabrioTourer
Two fingers on map; drag down.
Two fingers on map; drag up to restore to flat map view.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on April 30, 2019, 17:02:51
Uff, too much posts on me after few days off  :P

@0709
recalculation with route-priority should behave differently now. It should not force you to go back to some un-passed points, but always should try to find nearest next point along the route. So it should not be needed to use via-points to keep you moving along the planned route.
Also, just today I've improved option when you start navigation from the map with "Navigate from selected point". The app will now try to navigate you really to this point firstly without skipping.

"Recalculate all" feature is for some time in the right side menu. Does not work as expected?

@locus.sv@heime.org
lost manual rotation: ah, did not know about this, but you are correct! Fixed, thanks

@Viajero Perdido and others with "tilt" questions
tilt was enabled in Beta by accident. It is old app feature that do not work correctly with visible tracks/routes. Sorry for confusion, will be disabled in next Beta again. Till then, use two fingers and swipe up/down.

"Render loop" ... hmm it seems to be a side effect of automatic searching for maps that may fill these gaps (map auto-load). I've fixed at least this "blinking". Now we need some method that will fill these gaps by simple background color.

@CabrioTourer
I also noticed some unexpected lags and slowdown, so performance is definitely something I'll have to look on more carefully.

Problem with navigation: sorry, this is exactly what I wrote to Viajero above. It is a side effect of "tilt" of the screen. Just turn tilt back and it will work as expected :). Sorry for this.

And slow rendering: I'll for sure look at it closer and try to improve it! Thanks

@Andrew Heard
thanks, email received. I'll look at it during the next days.

@tramp20
uff, do not know about any similar problems. If you see "map does not support themes", this should happen only if enabled map really does not support themes. Maybe restart of device and selecting vector map again? Even a crash confirm there was some serious problem.

@Žajdlík Josef
ah, this dialog was commented with one big "TODO" :).
Anyway, you have found one big issue for me now. So, unfortunately, selecting map themes (which was not still perfect) in presets have to be removed for now.

@balloni55
well, the rendering problems itself or slowness, aren't currently top priority. My first interest is to offer the same or better experience for current existing features. MapsForge V4 was still more or less experimental and only a fraction of users use it now. So sorry, I do not know how to solve the mentioned problems. It will need some deeper testing and hard to say if it's even easily solvable when MF V4 is completely out of my control.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on April 30, 2019, 19:15:49
@Žajdlík Josef
ah, this dialog was commented with one big "TODO" :).
Anyway, you have found one big issue for me now. So, unfortunately, selecting map themes (which was not still perfect) in presets have to be removed for now.

I don't know if I understand correctly? The PRO version selects the map theme. The preferences would make no sense if the map theme could not be selected. What would be the prefix "tourism" with a car theme map?
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: erfi on April 30, 2019, 19:24:11
There is now a problem with track statistic Energy in new Beta-Version, here 3 Examples:
Track Walking: 3.37.2 Pro:    341 kcal; 3.37.2.9 beta: 4464 kcal
Track Bicycle:  3.37.2 Pro:    845 kcal; 3.37.2.9 beta: 1187 kcal
Track Hiking:    3.37.2 Pro: 2454 kcal; 3.37.2.9 beta: 8340 kcal.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on April 30, 2019, 19:40:14


I don't know if I understand correctly? The PRO version selects the map theme. The preferences would make no sense if the map theme could not be selected. What would be the prefix "tourism" with a car theme map?
Now that Locus is supporting two parallel sets of themes - for LoMaps/MF3 and for MF4 - selecting a theme is not sufficient as the theme has to be the right type for the current map. Really the map type has to be selected as well. But that presupposes that type of map is available on your device.


Sent from my moto g(6) plus using Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on April 30, 2019, 20:06:52
This shouldn't be a problem, the map theme and maps come from the same OSM Paws: https://osm.paws.cz/ However, I understand that the map should be selected in combination with the map theme.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on April 30, 2019, 20:35:17
I had to remove this preference completely (from the quick switch and from presets).
The new system is internally completely different and I have to write this setting different (do now know exactly how yet).

I'll also try to create something more generic that cover also selecting specific settings of every theme as requested by many people over the help desk. It will anyway definitely take more than a day so little later ...

@erfi
ah thanks, I'll check it.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on April 30, 2019, 21:00:33
I understand it's not easy.  But I think it should be resolved before the Pro release.  For the current user with Lomaps, V4 maps will not bring anything new.  Conversely, losing important preference settings would look more like a deterioration in functionality.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on April 30, 2019, 21:24:59
Understand Josef, I'll try to do it :). But just inform, that most probably in next Beta, this feature will be missing.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: 0709 on April 30, 2019, 22:25:48
@Menion
"Recalculate all" feature is for some time in the right side menu.
Right side menu ?  Aaaah the Hamburger.  I missed that.
Tnks for hint. Works as expected.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: michaelbechtold on April 30, 2019, 23:01:35
When recording a track, always a FC happens with 3.37.2.9
Report by system sent.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on May 01, 2019, 08:38:45
I have thought notes about incoming improvement of route priority recalculation.

Lets imagine route priority autorecalculation , strict following off.

I go along 10 km deviation from the route, that goes in parallel to the planned route and then rejoins.

Both ways are equivalent in sense of routing preference and there are no shortcuts along the deviation.

As it is supposed to aim navigation recalculation toward closest route point, then after 5 km on deviation, it would point (generally) to 5 km point of the planned 10km segment.

Q1: Does it mean it would try to turn me back in first 5 km, as that way to the respective point on the route would be shorter ?

Q2: When recalculation aims me forward, with chosen closest route point, and I finally get on the route somewhere ahead, I guess it will be reasonable enough not going after that point. :-)

Additional note:
It may be good not to choose the closest route point, but project it ahead, along the route, depending on route deviation. (I guess something similar is applied for guidance, but not sure)

E.g., if I am 3 km off the route, it may project the route meeting point a x 3=3 km     
ahead of the closest point., if a=1.

Odesláno z mého Mi A2 pomocí Tapatalk
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on May 01, 2019, 09:53:07
Zoom lock on Pro: First tap on button restores the last zoom lock magnification immediately. Second tap reverts to initial unmagnified view.
Zoom lock on beta: No immediate effect on first tap. (That's ok but not so convenient) Second tap keeps the same magnified view until I adjust the zoom when it reverts gracefully to a standard magnification and zoom to display the same area. Personally, I don't find that intuitive or nearly as useful as the current Pro method which gives one tap to magnify an area of interest or confusion, second tap to revert.


Sent from my moto g(6) plus using Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 01, 2019, 10:33:21
@michaelbechtold
hmm I just fixed few reported issues, but I do not see anything related to track recording. Maybe some side-effect. Please try next Beta version and if it will still crash, create for me a log manually, thank you!

@poutnikl
Understand
Q1: you think about this also because of discussion on BRouter forum right? I'm still not perfectly sure how BRouter handle request from Locus Map so without precise testing I think that yes, app will guide you with the shortest possible path to the nearest point along the route.

Q2: with "strict following" disabled, in moment you connect back to original route, you should continue forward.

You think that using some "projected" point will work always? Imagine your situation. The route may after these 10 km turn sharp left or sharp right or even u-turn and in all these cases, projected point 3 km from "meeting point" should really not be what you want.

Anyway, I believe it needs some test :).

In Beta version is under Skyplot screen > menu > simulation option with simulation over a recorded track. I've just improved it a little bit so it now correctly follow recorded (planned) track also with the correct speed. So it is a nice method to test the navigation system.

@john_percy
hmm I'll check it. This option has settings over config.cfg but seems it does not work correctly. Thanks
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tramp20 on May 01, 2019, 11:26:45

@tramp20
 If you see "map does not support themes", this should happen only if enabled map really does not support themes.

As I wrote:
With 3.37.2.9 all of my vector maps (LoMaps, Outdoor, Classic OSM) are now without a theme, selecting a theme gives always "the actual map does not support themes".

I can reproduce this behavior on two smartphones with your LoMaps even after a complete new installation of the beta.
But if I install the OAM V4 map with some themes then I can select my old V3 themes with LoMaps cards again.
Perhaps your program does not read the correct configuration?
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on May 01, 2019, 11:39:13
[

@poutnikl
You think that using some "projected" point will work always? Imagine your situation. The route may after these 10 km turn sharp left or sharp right or even u-turn and in all these cases, projected point 3 km from "meeting point" should really not be what you want.

As I do not know what Locus passes to BRouter, I neither know how it is managed. I would just guess it would be treated as an ordinary short route.

I mean projecting along the route, not geometrically. So it would lead me to a route point 3 km forward from the closest point on the route.

If we consider both route and deviation segments of the same length,
and if the recalculation happens at km5, 3km off the route,
it would point me to the route km8, still 2km before route/deviation meeting point.

My whole idea was optimizing the track length, to return to the route in a relaxed way, as trade off between route following and passed distance. Sure, it would need testing.

Thanks for the tip, I forgot/never knew it is there.

Odesláno z mého Mi A2 pomocí Tapatalk
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on May 01, 2019, 14:30:44
I compared old/new recalculation logic today and the results are mixed.
I append the route I planned.
I'll start navigation at the yellow cross. I'm in direction of route between sharp point 1-2 and much closer to 1-2 than to route end point 8.
Then I follow route.Will left route at red circle and will be back on route at blue circle.

First of all the initial point why you changed recalculation logic didn't happen with release version (it was: Does not notice back on track. Means navigation must be stopped and start again to fix this)
Nevertheless the result is interesting.
Release version.
- start navigation at yellow cross: Wants to navigate you to end point, even route between 1-2 are closer
+ recalculation after left track (red circle) recalculation tries to bring you back on route (purple 1,later purple 2).
+/- because it recalculates back to track correctly the "does not notice back to track" issue didn.'t happen

Beta:
+ navigation starts correctly to route between 1-2
- after route left it allways tried to navigate back to red circle (green/blue sign 1). For many recalculations.
Very short before blue circle it switched to green/blue sign 2 (back to red circle too I guess)
+ After ignoring green sign 2 and turn right back to route it switched to purble 2. Means it noticed back on track and skipped all past points.

Conclusions :
1. With new logic start is much better
2. Recalculation of release logic succeed in this case, new fails.
3. New logic notice back on track correctly.

I.'m sad I didn' t had the initial problem to change recalculation logic described in support forum.

If needed I can provide videos.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on May 01, 2019, 14:45:34
During my comparison between old/new recalculation logic I had the problem that Locus simple stopped and smartphone returned to launcher. It didn't show crash or anything else it just stopped.
This happened multiple times. Because time between locus or navigation start and stop issue were different each time I don't think it is because Firmware accu optimization or something similar. To be sure I disabled Doze mode completely but didn't fix the issue.
Don't know if this helps but I add three logs.

Happens on OnePlus 6, Rom (LR) based on AOSP.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 01, 2019, 15:57:09
@tramp20
ok thanks. I'll have to play with it a little more than...

@poutnikl
I was of course also thinking along the route, not as a projection, don't worry. It is additional logic to the current system, so let¨s firstly try this first system and we will see.

@CabrioTourer
thank you for such precise testing! I just a few days back did some more tests and another small improvement that may affect this test as well, sorry for this.

Thanks also for crash logs. Unfortunately, I'm unable to perfectly find the reason of this issue but seems to be somehow connected to some active dashboard. Is this possible? If so, may you share this dashboard with me as well? Dashboard files are in Locus/data/dashboard directory. Thank you!

Method for navigation simulation

With the Beta version, there is a nice method of how to test the navigation system. I just improved it little more so the current method will work correctly in next Beta version (probably tomorrow):
Now it's possible to test navigation with "Navigate to" function or also on the route, planned with route planner.

You may also start the simulation with own recorded track > nice for repeating field problems.

In case of the problem with navigation, best is to share the track used for simulation and navigation route itself. Then, everybody may simulate exactly the same what happens to you on your device.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on May 01, 2019, 16:07:08
Regarding comparison old/new recalculation
While checking my videos I noticed I start navigation in Beta in a wrong way.

In release I selected a specific track point while map view and start navigation from this specific point (near sharp point 2).
But it navigates to end point, not specific point.

In Beta by accident I start navigation in track menu. Nevertheless it navigates me to nearest point which was between 1-2 which is very nice.

Redult is even worse for release.
Even if it knows which point I want to start navigation it selects end point by themselves and ignores User.

(Just a comment because it might be forgotten by all the error reports.
Locus is the most powerful navigation software I ever saw. Not only for smartphones. It has unbelievable features. Don.'t be afraid and keep up the great work)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on May 01, 2019, 16:11:39
@tramp20

Thanks also for crash logs. Unfortunately, I'm unable to perfectly find the reason of this issue but seems to be somehow connected to some active dashboard. Is this possible? If so, may you share this dashboard with me as well? Dashboard files are in Locus/data/dashboard directory. Thank you!

Method for navigation simulation

With the Beta version, there is a nice method of how to test the navigation system.

dashboard was active and same as in release. Its appended.

Nrw simulation :
Wooowwww that's great.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: jajaballard on May 01, 2019, 21:44:57
Hello Folks,
during my ride to I observe some strange behavior of Locus Map:

I usually have switch on: "Center map at GPS Position" after 5 sec.
Now in the current Beta, if I look at the map and pan a little around (moving the map), the map is not centering back after 5sec as before. The button is still highlighted.
To center back to GPS Position , now I have to manually switch off and on the "Center Map at GPS Position" button   ( for me at lower left corner)
This is very uncomfortable to handle, special in rougher terrain.
Regards
Ralf
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 01, 2019, 23:37:24
@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!
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on May 02, 2019, 02:02:01
Method for navigation simulation With the Beta version, there is a nice method of how to test the navigation system. I just improved it little
@menion - nice feature - my only suggestion is some way to speed up the simulated speed. I changed the recorded track activity from Not Specified or Cycling to Car, but still often too slow for testing. Some form of dynamic speed control would help. But very low priority.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on May 02, 2019, 12:36:50
Zoom lock on Pro: First tap on button restores the last zoom lock magnification immediately. Second tap reverts to initial unmagnified view...

Maybe it's related.  Manually zoom the map while driving will cause it to lock in one place.  The map is not in doubt.  When the screen goes out, the movement resumes.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 02, 2019, 14:51:38
@Andrew Heard
speed problems > I wrote "I just improved it little more so the current method will work correctly in next Beta version" ;)

@Žajdlík Josef
hmm should be related thanks. I'll probably not be fast enough to create version today, so hopefully tomorrow.

----

Geocaching question

When logging a cache, there is an option "Log date only". Is there any reason for this setting now? When we enable this settings, defined time is used to replace {t} parametr in log, but on geocaching server is send log with time set to 12:00.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: c.s.g. on May 02, 2019, 15:15:39
Hi menion,
Geocaching question

When logging a cache, there is an option "Log date only". Is there any reason for this setting now? When we enable this settings, defined time is used to replace {t} parametr in log, but on geocaching server is send log with time set to 12:00.

For me it never makes sense, to log a geocache without the exact found time. So for me the checkbox could be removed. Then I expect the exact log time in {t} parameter and in online log at groundspeak when sending log to geocaching server or exporting it to a fieldnote-file . I. e. exact the same way the checkbox is not checked.

As far as I know the time is not storred at groundspeak server. Maybe it is changed with the new API, I do not know But I am using the time part of the log to get a chronological order of my founds per day. An, thanks to the {t}-parameter the found time is present at least in my logs.

In this forum there are even two posts about this checkbox I have answered. There the checkbox was accidentally checked and the user wondered why all logs where set to 12:00 at groundspeak server. Unfortunately the checkbox is hidden under the keyboard. So the state of that checkbox is not visible immediately.

c.s.g.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 02, 2019, 15:31:51
Yes, exactly because of these problems (hidden checked settings etc), I'm thinking about removing this setting and always log caches with an exact defined date. So I'm asking here if there may be any possible problem when logs will be sent with defined time and not with 12:00.
Thanks for answer c.s.g.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: JoxM on May 02, 2019, 19:59:39
For me the exact time for logging is absolutely necessary while fixed logging time 12.00h makes no sense at all to me.
The main reason for that is to keep the online logs in the right order (like found outdoors) even when logging in disorder (happens sometimes when logging additional (special/very good) caches done during a trail )
So no need to keep the checkbox from my side. Honestly I already wondered why it could possibly be there...
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: jonny.blue on May 02, 2019, 20:46:18
... 12.00h makes no sense for me too.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: T-mo on May 03, 2019, 00:10:31
Menion, congrats to this great step and your efforts to rework the vector-engine for improved dpi-awareness and adaption to newer mapsforge, happy to see this.

I am also using some raster-maps with limited zoom-levels, Z13 and Z16,to keep the map-size low and as Z14+Z15 doesn't brought a real gain in informations. But this only works if the zoom-transition between Z13 and Z16 is fine tunable, may depend on screen-dpi and personal taste. Sometimes I would prefer Z16 with value lower 50% instead of Z13 at 200%.
i guess currently I'm not able to finetune this or? Maybe in the future, not high prio, just realized this while using the new beta.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 03, 2019, 06:10:06
Geocaching
if I remember correctly, 12:00 time was needed to keep logs from people on geocaching.com in correct order under one cache. Something like this, but not perfectly sure now as it's really really long history.

Oki, so if even geocaching master @balloni55 :) does not have anything against it, I'll remove this option to next (Beta) version.

@T-mo
Understand that with a new system, this may be a little worst then before. Currently there is no settings that affect this behavior. I'll look at it if there isn't any option how to improve it in app and give a little higher priority to use in your case Z16 instead of Z13 if possible. Good point, thanks.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: balloni55 on May 03, 2019, 07:34:47
Geocaching
Oki, so if even geocaching master @balloni55 :) does not have anything against it, I'll remove this option to next (Beta) version.
LOL....
thanks hint from c.s.g. long time ago  8) each of my logs start with real time from "offline field log"
{t} > HH:mm
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 03, 2019, 11:35:06
*** new pre-weekend Beta version 3.27.2.10 ***

Huge list of changes after app start.

Only known problem > start on Android 4.x should be probably still there. Fighting with it again and again and ...
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on May 03, 2019, 12:23:30
Regarding label layers and so on, Emux's Cruiser GL on android is a great example of what can be done with a separate text layer. Two finger rotate and perspective view keeps the texts horizontal. It even has an optional 3d building view. The rest of the app isn't a patch on Locus however but as an example of map rendering and routing it's excellent.
It uses Mapsforge maps and themes but (I think) a different rendering engine.


Sent from my moto g(6) plus using Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 03, 2019, 12:29:08
Yes John, it is a different story. Emux is quite hard working on VTM & MapsForge system (https://github.com/mapsforge/vtm) 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.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on May 03, 2019, 18:00:45
@Menion
To focus on new map core and finalize navigation later is fine.
Just that you are aware of some problems which might not be directly related to navigation logic I want to show you some things upfront.

Simulation in V10 is much slower than V9.
Funny thing: Airplane is slower than car in V10. Airplane means it counts meter by meter. That's slow ;)
I checked recalculation in Simulation in V9 and V10. In V10 it's detect "back on track" but pretty late. V9 it doesnt detect recalculations before back on track isn't improved.

Simulation might not show what happens on the street.
I tried the tour I did on Tuesday with Simulation multiple times. The results are sometimes different. My simulation started more or less same as Tuesday but later it changed and I see something different.
I uploaded the settings, planned route, simulation route and video which shows the issue here. All from V9 because simulation in V10 are too slow.

https://app.box.com/s/xfaxre1nil8n3ljv07az9xtab2nmtpf2

Then a question.
Which parameter influences when second, third etc. recalculation starts ?
The first recalculation is influenced by settings but all other seems to be random.
Sometimes after 300m, sometimes 600m etc.
Can't find any settings to change the time/distance. Tried all settings (I think) in navigation and guidance.
I'm asking because the place where recalculation happens influences the result of recalculation.
Without able to influence recalculation time Simulation might show other things than on street.

Again : it' s fine to focus on new map core first. Just that you are aware of some issues any maybe my sample might be good for testing.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on May 03, 2019, 18:24:31
Increase Map Resolution for vector maps unchanged in the new beta, I think. Reducing zoom level and then magnifying really doesn't work. Texts are enlarged, yes, but other details disappear, depending on the zoom level at which they appear. And roads are no more visible.

Sent from my moto g(6) plus using Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: jonny.blue on May 03, 2019, 18:40:33
Quote
The first recalculation is influenced by settings but all other seems to be random.
Sometimes after 300m, sometimes 600m etc.

Same to me ... but when you leave Locus and switch back: recalculation starts (most times  :-\)immediately.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 03, 2019, 19:10:31
@CabrioTourer
slower simulation is possible, not all "activities" have defined average speed. Best is to use base activities like walk, run, bike, car.

Thanks for the very precise bug report. The problem here: you took a really huge shortcut here. To improve performance, app tests only following 100 trackpoints, so seems that whole missed part is more than 100 trackpoints. As a save-button, in navigation menu is "nearest point" button. Anyway this is interesting and probably common use case. I'll think about it, thanks.

Frequency of recalculation: there is a limit to once per 30 seconds. Was there always. Anyway seems, based on @jonny.blue confirmation, there is any new problem. I'll check it.

Map core has priority, but without navigation working at least same as in 3.37.2, I cannot publish new version, so thank you for testing!

@john_percy
it is correct. I spend on this today maybe two hours and it really isn't so easy task. Currently not solved without a clear idea how to easily solve. It just needs some sleep and good tea :).
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: balloni55 on May 03, 2019, 19:44:28
if i start route planner map center to Prague :-[
in my case blank map is visible, available world map isn´t loaded.
With center button inside routplanner window, map center return to last known position
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on May 03, 2019, 20:05:01
@Menion
You talk about trackpoints, not sharp/via points, right.
Then it's a pretty short way for a lot of activities. That's for sure a problem.

Solution might be not to choose 100 in a row but every x trackpoint where x depends on the activity (or actual speed?)

If this does not work for activities which needs defined ways (street etc) then selecting trackpoint located on crosses etc might be the solution.

Just an idea.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on May 03, 2019, 20:31:53


@Menion
You talk about trackpoints, not sharp/via points, right.

I see you repeatedly use the term "sharp points", possibly because they are displayed as triangles, that are sharper then squared via points.

But AFAIK, Menion has coined for them the term "shaping points", giving to the route a particular shape between start/destination/viapoints., being e.g. a manual correction of the computed route between those points.

Just for completeness, they do not count as points in context of the point priority recalculation,  in contrary to the via points you "must visit".


Odesláno z mého Mi A2 pomocí Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on May 03, 2019, 22:25:27
Just for completeness, they do not count as points in context of the point priority recalculation
This is what I thought. I just asked to be sure because 100 trackpoints isn't much for activities like car and even not much for bike in rural area.

Thanks for "shaping point" correction.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on May 03, 2019, 22:57:18



This is what I thought. I just asked to be sure because 100 trackpoints isn't much for activities like car and even not much for bike in rural area.

When I analyzed GPX files of multiple bike routes, generated by BRouter, I realized, that as a "rule of thumb", the is in average 1 trackpoint about every 50 m. I suppose less dense for car routes, more dense  for hiking routes.

Trackpoints from recorded tracks will be probably much denser, depending on the recording settings.


Odesláno z mého Mi A2 pomocí Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 03, 2019, 23:07:15
Well, for the planned route it may be a few kilometers. Anyway, for the manually recorded track used later for navigation, this may reduce to a quite short distance, so agree it is not an ideal solution.

As I think about it, testing on nearest trackpoint may not be so big problem. Because automatic recalculation is trigger max. once per 30 seconds, app should search over whole track without any limit.

On the second side, this quite nicely solves a possible issue with round routes.

EDIT: as Pountik wrote.

Generally, using any exact limit is usually not the best solution. So why 100 trackpoints? Usually it will work, sometimes not, like on your case.
On second side, what if you ride in the middle (on your video it's a first char "a" in name "Leiblachtal"), app snap to the bottom line, but it was only some detour and then you return back close to start of this route?
Just want to show that any change may on cause malfunction of different use-case. So I still see here as backup solution easily accessible button "nearest point".
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on May 03, 2019, 23:32:54
Slight change to hillshading is not sufficient IMHO. The screenshots here are of OAM v4 GreatBritainML using Locus internal theme at zooms 16-12. The road is quite visible at high zooms but disappears into the shadows as the zoom gets less.

PS This forum software is trying very hard to prevent me from posting but I will not be beaten.

PPS you may need to download the screenshot on a PC to view it properly.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on May 04, 2019, 01:41:27
3.37.2.10: sorting of Nearest & global tracks in southern hemisphere now working.
Where has the map theme selection gone though? I had a Theme button in Quick Selections but gone is beta.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tramp20 on May 04, 2019, 07:43:34

With 3.37.2.9 all of my vector maps (LoMaps, Outdoor, Classic OSM) are now without a theme, selecting a theme gives always "the actual map does not support themes".

Perhaps your program does not read the correct configuration?

With v 3.37.2.10 problem is solved.
Thanks.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 04, 2019, 08:11:40
@john_percy
hmm, yellow road on yellow background :/

Forum isn't ideal in more ways, agree. I think a lot longer time to move it to a different system. Discourse looks nice, but we use it on our help desk for Locus GIS (http://discuss.locusgis.com/) and can't say I'm 100% convinced it is the best system.

@Andrew Heard
yep, I had to remove this option for now, because it does not work as needed. Will have to find more time and create a new system for this setting.

@tramp20
perfect
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on May 04, 2019, 09:36:31
@menion: Yeah I agree yellow road on yellow background is not very visible. I didn't choose it purposefully though, it was just what the Locus internal theme displayed. In any case, it does show the shading is getting too dark too soon. It's much the same with a LoMap and V3 renderer, though the road and background are not yellow but pale off-white.
As for the forum, I got a series of errors when I attempted to post. First, "attachment too large"; then when I changed the attachment, "posted again too soon"; then after I waited, "you have already made this post". Grrr. I had to back out and start again.


Sent from my moto g(6) plus using Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: jonny.blue on May 04, 2019, 09:39:08
Quote
Because automatic recalculation is trigger max. once per 30 seconds, ...

Knowing about this 30 secs I started a new test series ... and yes, with enough patience  ;) this is what Locus does.
But there is a second condition: recalculation only starts if you are moving.

Therefore switching programs seems to start navigation in my earlier tests ... but now I know it were the gone 30 sec and movement when I came back.

But I'm really not sure if there should be a 30sec delay ...

What is the reason for this?
Isn't the distance a better criteria?
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: balloni55 on May 04, 2019, 10:44:15
after each start of Beta it is not possible to download PQ´s with GCtool.
I can solve it > run update of a cache, next download of PQ´s work till next start of Beta
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: slarti76 on May 04, 2019, 11:05:21
New Beta (.10):
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 04, 2019, 13:19:38
@john_percy
I'll discuss this with Petr this week. Not sure if a little decrease in shading is necessary because of one bad combination of yellow & yellow that is not so usual.

And forum, well, next time smaller attachments. Hard to help :).

@jonny.blue
recalculation should work also when the screen is off (except known problem to me with BRouter on Android 8). Weird. 30 second is there as a simple prevention of too frequent computations. Distance is definitely not enough to limit it. Distance even a 200m in car is really short and recalculation every few seconds, hmm not sure if ideal.

@balloni55
right after start, thanks, I'll test it.

@slarti76
tilting was again removed. It was enabled by accident, sorry.

And nearest points: good point. I've added this to list of "LoPoints improvements".
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tommi on May 04, 2019, 14:58:01
if i start route planner map center to Prague :-[
in my case blank map is visible, available world map isn´t loaded.
With center button inside routplanner window, map center return to last known position
Same issue for me.
If there is a uncompleted route in route planner you can continue it. But if route planner starts from fresh map center is moved to Prague - might be handy for Menion  ;) but not for users elswhere on the world.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Viajero Perdido on May 04, 2019, 17:59:53
There was a temporary glitch with loading Pocket Queries last night.  This happened on two devices (one with Beta, one with Pro), but did not happen on a third device with Pro.  The problem was repeatable for a few minutes until suddenly it started working again.

Geocaching tools -> Load Pocket Queries
[thinks for longer than usual]
"Whoops! [very strange message and code] code: 429

Of note, I have 21 fairly full PQs available right now.  And that funny text before the "code: 429", I'm not sure that's even ASCII.

Whether this is a potential problem, you can judge better than I.

Also, in Beta, after successfully loading some PQs (no "Whoops"), I noticed it sometimes returned me to the map, sometimes returned me to the Geocaching Tools screen.  (The latter is more convenient, for loading the next set.)  Haven't yet figured out what I might've done differently.  (Dragged my finger on the screen to keep it from going asleep while processing PQs; would that change anything?)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on May 04, 2019, 21:51:42
I don't get the point why to use x trackpoints in a row. Doesn't matter what x is. Only few of them are important. For all others you must touch one of the important ones to reach.
I mean for a lot of activities you are using streets, ways etc. So all trackpoints which doesnt touch another street/way are useless to check.
But don't know if it's easy to select.

For a starting point.
A recalculation which send me back has no real information. It's always the case that a return to the missing point will bring you back on track.
For the first recalculation it might be ok to show the point you missed (?). But maybe it's a good start to assume a "no go area" behind for the following recalculations.

If user didn't follow the advice for 30 sec or over a minute. The user might have a reason to do so.The following recalculation can respect that.

As allows just an idea.

Just a quick comment.
I'm using Locus for two years now and my example shows nothing special. This is what happened quite often to me.

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Viajero Perdido on May 04, 2019, 22:53:47
I don't understand Zoom Lock.  In the beta I've assigned it to the lower-right button, and tapping it toggles between 12 / 100% and 12 / 1600% (or any other number in place of 12).

That's not intended, is it?

If it is supposed to work that way, maybe it needs another name.

Ah, I get it.  It's kind of an "alternate zoom".  I can choose 100% and other%, and toggle.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on May 04, 2019, 23:49:39
@Viajero Perdido:
(a) Taking your starting view as ZL12/100%, tap on the Zoom Lock button. View is now a magnified version of current zoom, say ZL12/1600%.
(b) Tap the [ + ] or [ - ] buttons and the magnification changes but the zoom is locked at ZL12.
(c) Now tap Zoom Lock to turn it off and display reverts to (say) ZL12/100%.
(d) Next time you tap Zoom Lock you will see the map view magnified by the same percentage as you left it with last in (b) above.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: erfi on May 05, 2019, 00:24:56
3.37.2.10 beta: route planner starts on false position.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on May 05, 2019, 00:52:06
when I changed the attachment, "posted again too soon"; then after I waited, "you have already made this post". Grrr. I had to back out and start again.
has happened to me on a number of occasions too; confusing & annoying the 1st few times; now I just know how to workaround it
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 05, 2019, 10:04:12
@tommi, @erfi
ah, thanks for the route planner issue with the center of the screen. The same issue happens also on other secondary screens with the visible map: fixed and also fixed correct map scale, thanks.

@CabrioTourer
I'll have to look on this topic more this week, thanks.

@Viajero Perdido
I think I've got it. The issue with the loading of PQ fixed.
Importing of PQ files should finish on the map I think. App should load a PQ from the internet and start an import. If you want to import more PQ at once, isn't better to directly select all of them in the list?
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tramp20 on May 05, 2019, 12:07:10
@menion
Since 3.37.2.10 the auto backup does no longer work on my two Z1c with custom PIE ROM.
I tried all possibilities but the date of the next backup never changes. So I assume there is a problem with the "timer" and not with write rights.


On my stock LP 5.1.1 the auto backups are fine.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Viajero Perdido on May 05, 2019, 18:05:36
Importing of PQ files should finish on the map I think.
Sounds totally reasonable for most use cases.

My use case is probably less common, 7 PQs into this folder, 6 into that one, and so on.  Different folders, so different import steps.  But it's only an extra couple of taps, so I don't mind.  I mentioned it only because it seemed to be acting inconsistently.  Anyway, thanks!

PS, my opinion on slope shading:  I wouldn't lighten it tooo much.  At lower zooms, shading nicely takes the place of topo contours - which presumably disappear at such zooms.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on May 06, 2019, 16:12:35
Search address (offline), select country no longer works in beta. List of countries appears, tap on any one briefly highlights it but nothing further. Works OK for me in my current full Pro version.
(Edit)
Furthermore, Search Contacts loads contacts (OK), tap X in top corner to back out gives screen with back arrow in top left, hamburger menu top right, neither of which work. Use system back arrow to get search side menu to appear, select a different option and then exit from search OK.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on May 07, 2019, 00:26:08
Search address (offline), select country no longer works in beta. List of countries appears, tap on any one briefly highlights it but nothing further.
confirmed
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: T-mo on May 07, 2019, 08:35:14
Route Planner:
starting with brouter-engine and then switching to Graphhopper and hitting recalculate all from the hamburger menu always gives the message 'you can calculate..brouter only'.
If I then select a route segment (vehicle type symbol) and use the recalculate button next to the shown graph, or move a point back and forth, recalculation with graphhopper works as intended 8)
So recalculate all has some flaws.
recalculation with brouter as engine works always.

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 08, 2019, 09:41:43
@tramp20
weird, all work for me on Android 9. What happens when you "cancel" backups and then set them up from scratch?

@Viajero Perdido
hmm, specific use-case. Anyway, I'll check it, but correct should be to close whole big screen with available PQ files right after import starts.

@john_percy
ah, ugly issue. Thanks, offline search fixed.

This problem with contacts is in the app for many many years. Press "back" twice and it will be ok :).

@T-mo
well, not sure what is the problem. Fact that you can't recalculate the whole route with other then BRouter engines? This is not an issue as notification say.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tramp20 on May 08, 2019, 15:22:27
@tramp20
weird, all work for me on Android 9. What happens when you "cancel" backups and then set them up from scratch?

Ofc I did this many times :-(
If I reboot the next morning some times the missing auto backup is generated with the actual day/time, but at the next configured date nothing happens.
This occurs only since 3.37.2.10.
What can I do for you?
A catlog started at the configured time and stopped after 10 mins? What should I filter?

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on May 10, 2019, 09:48:40
"Zoom according to speed" setting doesn't display a map as a visual clue for me, unlike current Pro version. Also, as the significance of zoom values has changed, is setting this by zoom values the right approach? If I use a Locus or MFv3 map, ZL15 typically gives an equivalent area to ZL13 with a MFv4 map now.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 10, 2019, 10:36:54
@tramp20
the current auto backup system is based on Android library that decides on it's own, when to perform backups. So time defined in an application may not fit exactly (the difference may be an hour even more).

Because of this, it is really complicated to fix something around incorrect starting. Anyway if you have defined backup and it does not start in the worst case a few hours after it should, and you have active wi-fi, then it looks like a problem.

Because I did no changes in current backup system, I'll let it be for now and write me once final 3.38 version will be out and same issue happens. Thanks

@john_percy
hmm good point. Visible zoom levels are just labels. Internall app use so called "camera scale" value which is independent on used map.
So we need here some replacement for this "zoom: x" texts. Ideas? Small image similar to "scale bar" at main screen in every row?
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on May 10, 2019, 11:27:53
@menion
If you can get the map display working again in this setting screen, then the text for the scale bar length itself may be sufficient, eg "60 yd" in the screenshot.
In the screenshot, also note the ellipsis ("...") is not needed in the first column.
(https://uploads.tapatalk-cdn.com/20190510/2911e7e7567888e14914edc9a54dd07e.jpg)

Sent from my moto g(6) plus using Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on May 10, 2019, 13:36:23
Returning to the matter of double contour lines with MFv4 maps where more than one map covers the area in question, which is apparently linked with map auto loading. With the latest version, this still happens but it's always resolved by selecting the map again or by selecting the theme again, which makes me think the problem is not insoluble.

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 10, 2019, 16:08:30
*** new Beta 3.27.2.11 ***

Biggest changes:

@john_percy
Improved layout for auto-zoom will probably need some more time. Anyway, I've found that indeed, the old system used hardcoded integer values for interpolation between defined intervals. So I've changed this system. Unfortunately, I also had to change it internally quite a lot, so please redefine auto-zoom values manually again.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: erfi on May 10, 2019, 19:37:42
Beta 3.27.2.11: After starting the route planner, the visible waypoints disappear.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on May 10, 2019, 19:59:45
@menion
I understand that you need to work on the autozoom settings screen but the current one now displays incorrect values. If I attempt to do the settings while I have a MFv4 map displayed, the map magnification value it shows for zero speed is 16|100% (which is correct for LoMaps and MFv3) but the map image and scale corresponds to 18|100% for my device for MFv4. I've not yet checked it on the move.

Sent from my moto g(6) plus using Tapatalk
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on May 10, 2019, 20:06:13
The new Beta does not run on Android 8.  In addition, the Beta installation has changed the settings in the Pro version.  Specifically, the map theme has changed everywhere.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on May 10, 2019, 20:19:16
Interesting, as it does run on Android 9. Could the issues be related to incidental parallel running both Pro and Beta ?

Odesláno z mého Mi A2 pomocí Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: balloni55 on May 10, 2019, 20:34:42
- FC while start initialisation window
- after restart of device, Beta run one times, but with light(Blank) map
- next start FC
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: 0709 on May 10, 2019, 22:18:42
Locus map has stopped.  (A5.1.1)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 11, 2019, 09:09:40
Hi, interesting issue these crashes at start. On none of my device, I'm able to simulate it.

Made a quick fix based on automatic reports I received, so give a new version a try, thanks.

@Žajdlík Josef
Beta really should not change any settings related to map themes also in Pro version.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: michaelbechtold on May 11, 2019, 10:40:46
No start issue on my LG G5 and Note 3 and M5 tablet. Will try newest version later today again.
World map fix confirmed.
Overlay zooms still in disarray - need more data points, Menion, beyond my mail ?
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: michaelbechtold on May 11, 2019, 11:17:06
Just tried ...12 on G5 and M5. What worked before now crahses at start. Sometimes after a long wait and the initial messages, sometimes right away.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: michaelbechtold on May 11, 2019, 11:30:41
Not 3: now crashed, too, after initial Locus messages.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on May 11, 2019, 11:39:41
Interesting.
The beta from yesterday have not crashed yet on my Xiaomi MI A2 with Android 9.

Odesláno z mého Mi A2 pomocí Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on May 11, 2019, 11:48:31
New Beta so far without problems
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tramp20 on May 11, 2019, 14:14:52
- FC while start initialisation window
- after restart of device, Beta run one times, but with light(Blank) map
- next start FC

here the same on Pie.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tramp20 on May 11, 2019, 14:21:22
@tramp20
the current auto backup system is based on Android library that decides on it's own, when to perform backups. So time defined in an application may not fit exactly (the difference may be an hour even more).


I made a catlog today with 3.37.2.11 on Pie 9.0, there are some problems listed.
I have this problem (no autobackups since 3.37.2.10) on two Sony Z1c with Pie.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: jajaballard on May 11, 2019, 14:54:12
Latest version ..12? still crashes on Nokia 8. Sorry release number con not be read.
Regards
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: balloni55 on May 11, 2019, 15:10:01
Quote
Sorry release number con not be read.
open your device settings/Apps/Locus Map
there you´ll see version numbre also if app didn´t run ;)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on May 11, 2019, 15:37:53
Big problem with presets.  Too difficult for my English.  I'll describe it in Czech, sorry.
Instalace Bety nezmění ve verzi Pro v Přednastaveních jen mapové téma, ale zresetuje i všechna nastavení autozoom. Viz scr. Ve verzi Pro jde toto nastavení obnovit ze zalohy. Bohužel spuštění Bety a otevření Presetů zase vše zresetuje i ve verzi Pro. Doporučuji všem co používají autozoom raději Betu zatím nepoužívat, dokud Menion nevyřeší převod hodnot ze starého systému do nového.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: erfi on May 11, 2019, 17:50:18
Quote
Beta 3.27.2.11: After starting the route planner, the visible waypoints disappear.
Beta 3.27.2.12: The problem is still there.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: jajaballard on May 11, 2019, 18:56:45
Latest version ..12 still crashes on Nokia 8
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on May 12, 2019, 01:18:01
3.37.2.12 working OK for me on phone 8.1 & tablet 7.1
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on May 12, 2019, 05:24:23
While previous beta was perfectly stable for me while crashing for others, now 3.37.2.12 is exactly the opposite.

I was successful to launch and use it several times,  but now it has periods of reproducible crashing at the moment of appearing of the start checklist and periods of reproducible running.

I have not found patterns yet when they switch.

Odesláno z mého Mi A2 pomocí Tapatalk
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tramp20 on May 12, 2019, 06:16:29
@tramp20
the current auto backup system is based on Android library that decides on it's own, when to perform backups. So time defined in an application may not fit exactly (the difference may be an hour even more).


I have this problem (no autobackups since 3.37.2.10) on two Sony Z1c with Pie.

With 3.37.2.12 auto backup is running again and I have no more crashes at app start :-)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: zossebart on May 12, 2019, 14:05:26
I also have FCs with latest .12 Beta (Android 5.1.1 on Sony Z1 Compact).

Btw.: for how long can I expect Locus to be supported on Android 5.1.1?

Gesendet von meinem D5503 mit Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 12, 2019, 15:56:35
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.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on May 12, 2019, 17:23:29
Here no crashes on Android V9 with Locus V12.
Very short check of new route priority with Simulation. No more problems wit longer abbreviation/detour. If near by back to track recalculation works fine.
For my liking still to often U turn recalculation.
Get perfect recalculation with manual set of no-go area to avoid U turn.
@menion
Much (!) better than before but please consider option to stop U-turn navigation after 2-3 recalculations. Then the new algo will be perfect.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 12, 2019, 17:35:47
Yes, I'm seriously thinking about it and I already have a solution in the head.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: T-mo on May 12, 2019, 19:33:51
.12 worked, but then I replaced a v4-vector-map and also changed to the latest elevate-theme. Now Locus crashs during beginning of initialisation. I replaced the theme to the version before but still the same. Doubt it's the map.
Let's wait until the situation is stabilised..
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on May 12, 2019, 20:13:21

My crashing mentioned above may be related to the V4 map deletion as well, as I had previously installed both V3 and V4map of Austria from OAM, with the Elevate theme.  About the time I deleted V4 map, keeping just V3., the problems started.

Odesláno z mého Mi A2 pomocí Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: michaelbechtold on May 12, 2019, 21:26:12
Hello Menion,
I understand that ZL is no longer the guiding principle on the surface.
Still it is essential that Locus takes the appropriate data from the SQLite DBs, which IS still organized in tables along zoom levels. I would do a systematic and in depths documentation to help clarify, but currently V12 goes FC on all my devices ... :-(
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on May 13, 2019, 11:11:56
Even reinstalling of beta does not help. The beta, after displaying the news and receiving file access privilege, immediately crashed again.

I have sent the debug log recently via Google dusk sharing to locus.map@asamm.com, I hope it arrived.

Odesláno z mého Mi A2 pomocí Tapatalk
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 13, 2019, 12:50:54
Thanks Libor, email received.
In Locus Map is used a system called "crashlytics" that automatically sends these serious crashes to web console where I may see them. And I see exactly this problem that affects 11 Beta testers. But as I wrote ... no exact idea why this crazy error happens... which happens sometimes :).

I made some changes and the new version is in preparation.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on May 13, 2019, 13:53:24
I'm using V4ML maps and Elevate theme in V12 beta without any crash.

By the way. Theme Support in Presets (V4ML, Elevate) works ! 
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: jajaballard on May 13, 2019, 14:47:26
Ok 
V.3.37.2.13 start without crash. Top
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on May 13, 2019, 15:19:15
Confirming beta.13 runs fine, without crashing anymore.

Odesláno z mého Mi A2 pomocí Tapatalk
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on May 13, 2019, 16:19:47
Convert auto-zoom values ​​seamlessly.  Good work.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 13, 2019, 17:20:57
Uff so seems good news, thanks guys.

What I have found and fixed since 3.37.2.13
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: michaelbechtold on May 13, 2019, 17:46:53
On Note 3, LG G5 and M5 10.1 Beta V13 working fine now - TXs a lot!!
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: locus.sv@heime.org on May 13, 2019, 17:52:29
When you open the geocache description on some caches, the + and - buttons for making the text larger/smaller does not work well. Try on https://coord.info/gc5jnpw

This happens on both beta and released version
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on May 13, 2019, 18:42:35
Route recalculation in V13
@menion
After 2 recalculations back stop back Navigation doesn't work if there is another way in forward direction where the missed point can be reached.
Remeber my first example. Attached is the route after 2 recalculations.
I guess you avoid the actual position or the position where last recalculation based on..You shoud avoid the first  point where the route was lost.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: zossebart on May 13, 2019, 21:50:48
Confirm .13 does not crash on me any more. Good work! Thanks!

Gesendet von meinem D5503 mit Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: T-mo on May 14, 2019, 00:00:25
.13 starts without problems, v4 (OAM) and latest Elevate4.3.0,all running smooth.

With my Raster-Map Z13+Z16, the switching between while zoom-in and zoom-out. I guess what I might need is 'decrease map resolution' at settings>maps>advanced features  ;D
Lock-zoom currently helps, I can stay at Z16 and zoom-out, without getting (information reduced) Z13@274%.
I guess I can show a video once, if of interest.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tramp20 on May 14, 2019, 07:33:17

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



It is mysterious :-(

Locus beta <=  3.37.9   auto backup ok on two Sony Z1c with Android Pie
                           3.37.10 broken
                           3.37.11 broken
                           3.37.12 ok over two days
                           3.37.13 broken again

               
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 14, 2019, 08:18:44
Fine, so major problem ... crash at the start ... seems to be solved, perfect.

@locus.sv@heime.org
zooming was always a problem. I'll look at it, thanks.

@CabrioTourer
I'm thinking if there is really any problem.
What is the purpose of this your trip?
To ride along predefine route? In this case, Locus Map correctly tries to get you back on route, isn't it?
Or to ride to the destination? Then point-priority is needed.

Here is a general problem that you skipped quite a long route segment. Thanks for the GPX file, I'll try to play with it, but now sure I'll find any simple solution now  :-\.

@T-mo
well and how works current Locus Map Pro with this map? There should be a similar problem. Well right, in LM Pro, upscale of level 13 isn't so visible as is in Beta. Two missing levels may be a problem here.
At which scale app switch from 16 to 13 and opposite? It is mentioned 13/274%? And when you zoom out from 16 then it's 16/?%

@tramp20
if it's not a huge problem, leave it for now. There is a chance, it will work in the next version. Maybe you expect exact on-time backups but it does not work like this. There may be a really big time difference between planned and real backup.

I would like to finish the biggest problem and publish a new version next week and we may solve this later, ok? Thanks.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: slarti76 on May 14, 2019, 11:17:31
.13 starts up without problems again for me, too. Thx!
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: tramp20 on May 14, 2019, 12:44:17
@tramp20
Maybe you expect exact on-time backups but it does not work like this.
No problem for me to wait.
I know that the auto backups occur within 10-15 mins but these are never done.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on May 15, 2019, 08:36:22
The Beta version does not display a green box with information about successfully exporting the route to Strava.com. Is that right? The PRO version displays information.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on May 15, 2019, 12:01:09
3.37.2.13: today with track recording, turned display on, map is not refreshed no matter how long I wait, until I drag to force refresh. Haven't ever experience this before, although I think others have reported.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: poutnikl on May 15, 2019, 12:15:57
I have noticed several times something similar, redrawn after forced zooming in/out. 

Odesláno z mého Mi A2 pomocí Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 15, 2019, 14:05:57
Interesting. I noticed and already fixed one problem like this in one previous version and since that, I never saw it again.
Does this happen only with vector maps? At least that zoom in/out fit it :)

@Žajdlík Josef
testing and seems that it works correctly. Are we talking about manual export from the detail of the track?
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on May 15, 2019, 14:16:50
@Žajdlík Josef
testing and seems that it works correctly. Are we talking about manual export from the detail of the track?

This is an automatic export. The report of the ongoing export will show up, but not the success.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 15, 2019, 14:27:26
Result of automatic export should be visible in the notify center in the top-right corner of the map. There is no need for extra floating notification.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on May 15, 2019, 14:48:06
Yes it's okay. Just point out the difference between PRO and BETA. It is not clear whether this is a intention or a mistake.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 15, 2019, 14:54:29
I remember I made some smaller changes here based on some discussion on the help desk, so yes, if there is the difference, it is intent. But the link to discussion is not stored in my memory, sorry :).

Anyway, the idea behind this was for sure fact, that result of export is a) not so important because automatic = "I do not want to care at that moment" and also the result is visible in notify centrum.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on May 15, 2019, 15:13:41
It might be worth considering whether to display the information center details in the event of automatic export failure. But it is just such a thought, I have no problem with it because Strava.com will announce a new route notification anyway.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: zossebart on May 15, 2019, 20:05:44


@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.

I just wanted to thank you for your answer. This means I might get along with my trusty little Z1c for some while. Thanks!

Gesendet von meinem D5503 mit Tapatalk

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: CabrioTourer on May 15, 2019, 22:06:39
@menion
Sorry for the late answer. I'm quite busy with my buisness.


@CabrioTourer
What is the purpose of this your trip?
Just fun.
In case I travel from A to B I don't use Locus. I use Google Maps.


In this case, Locus Map correctly tries to get you back on route, isn't it?

I think your Definition of route priority is too strict.  Yes in principle the idea of the planned route is to touch every route point when you select route priority.
But there are two different reasons why to leave the planned route. First you simply missed the navigation or you took the wrong street if there are two close together. In this case your approach is right. Redirect will be short and turn you back to the missed point is totaly fine.
The second reason is the fact that the route can't be followed. Let's say a
roadwork or the road is closed etc. In this case guiding back to the missed point doesn't help.
Then the alternativ route might be longer because it simply depends on the sreets which are available. At least for me (and I think for the majority of users) the recalculation should bring you to a useful point of the track. "Useful" in terms of easy reachable.
After back on track it should continue the route and don"t send you back to the (more or less long) part of the route you missed. In very common cases this will be a oneway because of the roadwork/road closed etc.

The App doesn't know for which reason the route was left. For this I brought up the 2 recalculation idea.
First, Locus can assume it's just a simple missed navigation etc.
After this 2 recalcs the App should assume the route can't follow this way and should find another way which means it's fine to skip a part of the route.

Here is a general problem that you skipped quite a long route segment.

That's not up to me. This depends on the available streets. As I wrote some days ago. "long" in city environment is a different thing as in rural area. In first case it might be 2 km. In the second case it's 10-20 km or whatever.
I think the distance doesn't matter. The number of streets connected to the part which follows the missed point is the similarity.

It's totaly fine to wait for the good solution of recalculation logic.
The logic is the same for 1-2 ywars now. No problem to wait a bit. Main point is to do it and do it good.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: T-mo on May 15, 2019, 23:58:44
@T-mo
well and how works current Locus Map Pro with this map? There should be a similar problem. Well right, in LM Pro, upscale of level 13 isn't so visible as is in Beta. Two missing levels may be a problem here.
At which scale app switch from 16 to 13 and opposite? It is mentioned 13/274%? And when you zoom out from 16 then it's 16/?%
To be honest, the 13-map isn't the best. Mostly I use a difference of 2, z10+Z12 and Z7+Z9. Just realised a difference.
Attached pictures show the difference between PRO and beta.13
PRO Z16 @100% is different than beta Z16@100%, beta is much more 'zoomed in', too much to be of use @100%.
In the past at PRO I increased the map-resolution by 175% to find my sweet spot. The pictures are without increased resolution.
Beta.13 @35% is the spot where it switches from Z16 to Z13@274% btw. Very similar to my PRO-sweet-spot.
I guess that's my 'problem': to get my PRO-like-view I have to manually zoom out..and it might happen that it switchs to Z13.
I can also not get this view to 100%, I guess it would mean sth. like 'reduce resolution'..
I have to test further. just have the feeling that auto-zoom-levels might result in less-usable-views..
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Andrew Heard on May 16, 2019, 00:47:54
Does this happen only with vector maps? At least that zoom in/out fit it :)
@menion - sorry can't help as I only use vector maps.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: slarti76 on May 16, 2019, 09:46:52
I know, this is more "Idea" territory, but I always think it would be fantastic if that Track info bottom bar that is shown in route planner could also be activated in normal view when selecting a track? Especially the quick elevation profile looks great and is super-helpful. Otherwise, have to go to the Track Details, where I might not have set the chart to "altitude vs. distance" right now, and which always gives a slightly wrong idea of the track because of the extreme Y axis enlargement.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 16, 2019, 10:54:44
@zossebart
I had also Z1C ... it was the best phone I ever had. By my stupidity I broke it maybe a year ago, anyway it is my personal interest to keep Locus Map working on this device as long as possible ;).

@CabrioTourer
really no need to sorry :).

The App doesn't know for which reason the route was left. For this I brought up the 2 recalculation idea.
First, Locus can assume it's just a simple missed navigation etc.
After this 2 recalcs the App should assume the route can't follow this way and should find another way which means it's fine to skip a part of the route.

This is partially implemented. After two "failed" recalculations (user ignored new route), app place temporary no-go place behind the user to force routing engine to compute forward and not backward. Anyway, this logic does not affect "target" where recalculation is done and this is what we talk about here.

I still do not see a simple solution. I perfectly understand your reasons anyway as you wrote: "The App doesn't know for which reason the route was left.". In this case (your route) it is almost circular route which complicates the situation. App has absolutely no idea if you are off route because you want to skip the whole circle or you just pick some detour because of complications on road. In rare cases when this happens, exists in the navigation menu button "Nearest point" that should fix this situation.
It is not automatic, which means it is not an ideal solution.

I'll keep thinking about it and collecting ideas. For now, I really think that changes from last weeks are quite big and this not-so-often use case may be solved in another iteration.

@T-mo
understand and thanks for screenshots.
Hope you got the point of these changes in app. If now, simply: app try to unite visibility of content of all maps. Compare vector maps and some online (raster) in Pro and in Beta. Mainly check visible texts. In Beta, there should be very similar in terms of size. On modern devices (with huge DPI), all raster maps are useless in LM Pro.

You, as well as almost all other users,  had to solve this by "Map resolution" option. This unfortunately scaled also vector maps = problem.

So generally, "Map resolution" should be no longer important settings. It may be left on default 100% except for cases, you had worst eyes and really need a larger map.

@Andrew Heard
no problem. I found an issue in pinch zoom when work with world map = fixed. On your screenshot was higher zoom so it won't be this issue, but I'll keep watching it carefully, thanks.

@slarti76
something close to what you want is planned. Anyway, some other priorities firstly :)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: erfi on May 16, 2019, 20:43:02
Quote
Beta 3.37.2.11: After starting the route planner, the visible waypoints disappear.
Beta 3.37.2.14 RC: This Problem is now eliminated. Thanks!  :)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: jonny.blue on May 16, 2019, 23:00:08
There seems to be a numbering problem in route planer:
When creating a route with planning points ... then create a via point ... the via point gets a lower number then last planning point.
Pic1: 4 planning points
Pic2: new via point

PS: checked it in 3.37.2 ... there is the same poblem.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: john_percy on May 17, 2019, 15:10:38
I don't know if this is a BRouter problem or a Locus problem, but it occurred in real life using the latest beta version of Locus. I've boiled it down to a particular junction for this example but it's not the only time it happened.
Navigating from N 32.38866, W 03.90318 to N 52.38831, W 03.90242 using BRouter offline set for Locus profile Fast Eco I got an instruction to "turn around" instead of "turn left". The map show a "turn left" symbol on the route, but the itinerary shows a U-turn.

Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 17, 2019, 15:34:29
@jonny.blue
hmm, it depends on what you clicked. If on the middle button, it says to Locus: "insert this point to the nearest place in planned route as possible". In your case, it is inserted into previous points 3 and 5. So you probably really get a route from 3 to 4 and almost back to 5.
Try to use the last third button to add cache to the route. This says "insert this point to the end of the planned route".

@john_percy
Here is exact content from BRouter that is send to Locus Map (just fresh downloaded routing data).

<wpt> has name "u-turn" and also rtePointAction: 13 (https://github.com/asamm/locus-api/blob/master/locus-api-core/src/main/java/locus/api/objects/enums/PointRteAction.java#L68) indicate to Locus that navigation command is u-turn.

Code: [Select]
<?xml version="1.0" encoding="UTF-8"?>
<!-- track-length = 201 filtered ascend = 11 plain-ascend = 11 cost=610 -->
<gpx
 xmlns="http://www.topografix.com/GPX/1/1"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:locus="http://www.locusmap.eu"
 xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd"
 creator="BRouter-1.4.11" version="1.1">
 <wpt lon="-3.903960" lat="52.388070"><ele>293.0</ele><name>u-turn</name><extensions><locus:rteDistance>110.0</locus:rteDistance><locus:rtePointAction>13</locus:rtePointAction></extensions></wpt>
 <trk>
  <name>brouter_remote_0</name>
  <extensions><locus:rteComputeType>5</locus:rteComputeType></extensions>
  <extensions><locus:rteSimpleRoundabouts>1</locus:rteSimpleRoundabouts></extensions>
  <trkseg>
   <trkpt lon="-3.903181" lat="52.388660"><ele>282.75</ele></trkpt>
   <trkpt lon="-3.903502" lat="52.388477"><ele>285.5</ele></trkpt>
   <trkpt lon="-3.903802" lat="52.388360"><ele>287.75</ele></trkpt>
   <trkpt lon="-3.903931" lat="52.388255"><ele>289.75</ele></trkpt>
   <trkpt lon="-3.903960" lat="52.388070"><ele>293.0</ele></trkpt>
   <trkpt lon="-3.903483" lat="52.388088"><ele>293.75</ele></trkpt>
   <trkpt lon="-3.903146" lat="52.388137"><ele>293.75</ele></trkpt>
   <trkpt lon="-3.902419" lat="52.388305"><ele>293.75</ele></trkpt>
  </trkseg>
 </trk>
</gpx>
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on May 18, 2019, 14:17:31
Beta RC. Incorrect calculation of driving time and average speed.
I add SCR of the same route from BETA, PRO, Strava.com.
Cycle Computer Length: 51.72, AVG 23.3, 2:12 Travel Time
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: erfi on May 18, 2019, 19:22:52
Beta 3.37.2.14 RC: The statistics energy consumption are not correct. They are too high.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 19, 2019, 09:34:44
@Žajdlík Josef
hmm, seems that Strava use exactly same old system that Locus Map used > so it computes directly from coordinates of current and next trackpoint. Not an ideal solution I think. I've reverted this part of the code to keep it as is anyway expect that I'll most probably change it in the future to the result very similar to current Beta, thanks (based on a floting average from previous & next trackpoint)

@erfi
anything new compares to Pro version?
And too high ... heh ... you may check five other apps or web pages to find that every compute values differently. I believe that values in Locus Map should be somewhere in the middle ...
Also depends if you use Heart rate monitor or not ...
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: erfi on May 19, 2019, 11:24:44
No, I do not use a heart rate monitor. To Pro version are only small differences. In my opinion the difference between walking and hiking is too big. Maybe you are right and I am wrong. Look at yourself, is this difference realistic?
(https://i.postimg.cc/RWYNYPk0/Beispiel-Track.jpg) (https://postimg.cc/RWYNYPk0)
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on May 19, 2019, 13:37:10
Beta RC, autozoom lock, V3 map. Button at bottom right. The autozoom shows 700 m, manually adjusts to 100 m and locks the lock. After 10 seconds, the map returns to 700 m. The cursor and the trip line flash. I think the chateau worked with scales of 11, 12, and so on. The scales are not used now, so the lock should be rebuilt to lock the meters.

CZ:
Beta RC, nefunkční zámek autozoom, mapa V3. Tlačítko vpravo dole. Autozoom ukazuje 700 m, ručně upravím na 100 m a zamknu zámek. Po 10 vteřinách se mapa vrátí na 700 m. Kurzor a linka ujeté trasy blikají. Myslím, že zámek pracoval s měřítky 11, 12 atd. Ty se nyní nepoužívají, proto by bylo třeba zámek předělat na uzamknutí metrů. Omlouvám se, ža na to upozorňuji až u RC verze, ale špatné počasí nedovolovalo jízdu na kole.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 20, 2019, 08:11:03
@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!
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: Žajdlík Josef on May 20, 2019, 10:10:25
@Ž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!

Due to complexity only Czech. Sorry.
CZ:
Omlouvám se Menione, ale video obrazovky vytvořit neumím. Zkusím problém ale popsat podrobněji, snad to bude stačit.
Předpokládám, že zámek (tlačítko vpravo dole) by měl fungovat takto: Mám nastavený autozoom, který mění měřítko mapy na obrazovce podle rychlosti v rozsahu od 100 do 900 m. Potřebuji ale dočasně zafixovat měřítko na 100 m (třeba ve městě). Změním tedy měřítko tlačítky nebo prsty na 100 m a stisknu tlačítko zámku. Dokud je zámek aktivován, mělo by být měřítko stále 100 m. Po deaktivaci by se měl znovu spustit autozoom v rozsahu 100-900 m. Takto alespoň zámek doposud fungoval, a dal se tak využít třeba když bylo za jízdy v neznámém městě potřeba vidět názvy ulic, najít restaurace apod.

Nyní ale zámek funguje takto: Změním ručně měřítko na 100 m a stisknu tlačítko zámku. 10 sekund je měřítko stále 100 m, ale pak se naráz změní na 900 a tak už zůstane. Současně začne nějak divně problikávat kurzor a červená linka ujeté trasy. Jakoby se Locus snažil měřítko měnit, ale něco mu v tom bránilo.
Zkoušel jsem i obrácený postup: napřed stisknout tlačítko zámku a pak teprve ručně změnit měřítko na 100 m. Výsledek je stejný jako v prvním případu.

Pokud bude třeba video, potřeboval bych poradit jako po vytvořit.
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 20, 2019, 12:43:35
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 ...
Title: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
Post by: menion on May 22, 2019, 13:22:47
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 :).