Locus Map - forum

31.10.2016 - Locus 3.20.0 - new version
- Blog post about major version: blog post (http://www.locusmap.eu/news-version-3-20-0)
- Detailed list of news: list of news (http://help.locusmap.eu/announcement/version-3-20-0-26-10-2016)

01.11.2016 - Locus 3.20.1 - bug-fix version
- news after app start

09.11.2016 - Locus 3.20.1.1 - beta version
- news after app start

18.11.2016 - Locus 3.20.1.5 - beta version
- news after app start

25.11.2016 - Locus 3.20.1.6 - beta version
- news after app start

03.12.2016 - Locus 3.20.1.8 - beta version
- news after app start

08.12.2016 - Locus 3.20.1.9 - beta version
- news after app start

12.12.2016 - Locus 3.20.1.11 - beta version
- news after app start

14.12.2016 - Locus 3.20.1.12 - beta version
- news after app start

@menion - I don't see new sound file PassPlace.ogg in navAudio ZIP in 3.20.0.1 - ref. http://forum.locusmap.eu/index.php?topic=5417.msg45464#msg45464. What exact navigation scenario is it supposed to cater for, and does the user need to manually add this file into the ZIP? Thanks.

Hi, is there some problem with Play Store update? Mine is still showing previous version.

Hmm sorry guys ... bad communication in company. Michal write blog post too slowly today and I won't publish new version in Thursday evening ... from previous experience, not before weekend. So at least new Beta, what you think ;) ... I'm going to publish it ...

3.20.0 release notes has this very interesting new feature:

<add: option (in config.cfg) to pan & zoom in track chart in vertical axis as well>

In 3.20.0.1 when I click on About > Release Notes > ">" to get more info for this topic I get error "Application for selected feature is missing...". It seems half the topics with links back into Locus website are valid/ working, but other half also give this error - mistyped URL?

New setting gui_track_screen_chart_vertical_scale=0|1.

My first experience with setting=1 and tap the chart + button: not very useful because X and Y zoom at same time. Pinch/zoom seems quite unreliable. Could the Y axis have own +/- zoom buttons when setting=1, or why not forget special setting, and just have Y axis buttons +/- zoom buttons always displayed?
(http://postimg.org/image/svk1agm9j/)

Finally version is coming out, so within one or two hours, it should be available for update!

Quote from: ta-ka on October 30, 2016, 15:49:43
On version 3.19.0.1, "Map items > 3-dot Menu > Open in file browser" doesn't open Locus internal file browser. Is it normal? Even if so, external file browser, in my case Total Commander, didn't start but foobar2000(music player) started. :-[

hmm, for me it works with TotalCommander.
Are you able to remove file assignment for foobar?
If not, try to remove/reinstall foobar. So system will ask again for assignment.

Quote from: gynta on October 31, 2016, 13:56:02hmm, for me it works with TotalCommander.
Are you able to remove file assignment for foobar?
If not, try to remove/reinstall foobar. So system will ask again for assignment.

I confirmed it works now on version 3.20.0, though more than 80 candidate apps are shown in the list before selecting default app assignment.

@ta-ka , @gynta: yep, little funny. It more like > nothing or all . Unfortunately there is no common method that use all file browsers that open certain directory. So I've rather created really basic call to system that should work in all filebrowsers and  ... well .. also in many other unwanted apps. Better then nothing? @voldapet was quite against this button, I on second side like it. So maybe small voting ... keep it or remove it? :)

QuoteV 3.19.0.1
-Test download of Kompass map stopped at ZL 16, and now???

is there any solution to complete my unfinished downloaded map with ZL16 with V 3.20.0 ?

Ah sorry, I forget to write you about this.
I've tried it twice and both time, it was success from start till end. I do not understand why it fails so only option I see, is some problem in database itself. May you please also share with me your partially downloaded map file? Thank You! And do not worry, LoCoins are never lost, so I'll gladly give them back to You if there will be any unsolvable problem.

QuoteMay you please also share with me your partially downloaded map file?

https://www.dropbox.com/s/sh3z86frl17v743/kompass%20M%C3%BChlacker.sqlitedb?dl=0

Quoteso I'll gladly give them back

it´s not neccesary !!!  it will be like "carry water in the river"  8)  (german proverb) ;)

Wow!  :D
+++add: option to toggle between normal/via-points during creating a track with "add new route" function+++
I think, perhaps it's better to set the blue color of the Via-points a little bit darker.
Wonderful function! Many thanks, menion!

Quote from: voldapet on October 31, 2016, 10:22:19
@gynta and Kompass map (799 LoCoins)
- more info please
- screenshot
- the name of map
- why are not Kompass maps "detailed"? Some real experiences?
- the text "Detailed" is adopted form official Kompass product description

Hello Petr, thx for reply.
If i use the Addon https://play.google.com/store/apps/details?id=com.mjk.locusmaptweak from GooglePlay Kompass maps gives me Zoom2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 
No words about sense! - but it's fact. (btw. Zoom 16 is also a 200%Zoom15 fake)
Locus offers Zoom10, 12, 14, 15
Anyway - i know, it's not your fault but it's also not my taste for a good map. thx for your effort.

Quote from: gynta on October 31, 2016, 18:50:34
If i use the Addon https://play.google.com/store/apps/details?id=com.mjk.locusmaptweak from GooglePlay Kompass maps gives me Zoom2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 
Locus offers Zoom10, 12, 14, 15

OK, I thought that there is really some "white" area on map. Well we offer KOMPASS map "as is". When it comes to missing zoom-levels:
zoom <  10 - there are some technical limitation, menion can give more info. But this is not important. Important is that minimal level for maps is level = 10 (at this moment)
zoom = 13 - zoom is skipped due to size of map. We decided to skip this level to make map little bit smaller and cheaper
zoom = 16 - as you noticed, level is the same as 15 and again size of the map

Quote from: menion on October 31, 2016, 15:08:07
@ta-ka , @gynta: yep, little funny. It more like > nothing or all . Unfortunately there is no common method that use all file browsers that open certain directory. So I've rather created really basic call to system that should work in all filebrowsers and  ... well .. also in many other unwanted apps. Better then nothing? @voldapet was quite against this button, I on second side like it. So maybe small voting ... keep it or remove it? :)

Doesn't work: total commander can't read the file. So better remove it.

Quote from: Christian on October 31, 2016, 21:15:35

Quote from: menion on October 31, 2016, 15:08:07
... keep it or remove it? :)

Doesn't work: total commander can't read the file. So better remove it.

??? ? The Filemanager simply open the Items folder.
...and if you have configured your TotalCommander you can do what you want with displayed files.

Quote from: Andrew Heard on October 27, 2016, 00:42:45
@menion - I don't see new sound file PassPlace.ogg in navAudio ZIP in 3.20.0.1 - ref. http://forum.locusmap.eu/index.php?topic=5417.msg45464#msg45464.

traps for young (& old) players - the reason I didn't hear my new PassPlace.ogg - it appears the notification sounds are cached only when the voice is changed. Workaround - if I select a different voice, then re-select my desired voice, now I hear the updated PassPlace.ogg. hmmm.

Quote from: Andrew Heard on October 27, 2016, 00:42:45
What exact navigation scenario is it supposed to cater for, and does the user need to manually add this file into the ZIP?

So to answer my own question - navigation scenario for example using generic cue point in RWGPS - this now invokes PassPlace sound - excellent. Yes, you need to manually add this file into your chosen voice ZIP file.

So I had to publish one more version today because of some "funny" issues with Kompass maps, sorry for this. Mainly to @balloni55 and @gynta who already purchased some maps. Anyway all affected people should get from Hanka an email with instructions and also refunded all spend LoCoins, sorry for this.
I had anyway one day to fix at least issue with missing "destination" waypoints for route planner (thanks @0709) and also reported crash in chart and few tiny issues. Hope new version will work fine and stable!

@Christian : thanks for a feedback. This "open in .." button is mainly made not to open files in "mapItems" directory, but to allow some advanced tasks that I do not wont to do in Locus, like copy, paste, edit text files, etc.

@Andrew Heard: hmm sounds like issue with using modified files. I'll check it, thanks

@0709: Willy yes I'm aware that other icons are missing. It is because currently it is not possible to create/attach basic points to tracks, it is allowed to add only "navigation waypoints". I plan to change this and offer full point edit screen also for these track waypoints, I just not yet found time on this.

update time is "mark as read" time...
(https://postimg.org/image/sm4gg79r7/)
Why Locus isn't able to remember my already marked news?

Hello. I note a small shortcoming when adding a new track or waypoint. The suggested folder seems to be choosen quite randomly. Should be pre-selected either last used folder from previous add or user preference for default category for new track and waypoint.

Sent from my phone by Tapatalk

Quote from: Bucky Kid on November 05, 2016, 07:47:27
Hello. I note a small shortcoming when adding a new track or waypoint. The suggested folder seems to be choosen quite randomly. Should be pre-selected either last used folder from previous add or user preference for default category for new track and waypoint.

Yeah, noticed that too on holiday, kinda forgot about it again. But I also saw no pattern or way to influence the proposed folder. IMHO, should be the last one something was added to.

Another issue I stumbled across many times but forgot to report: there are sometimes only one or two distance rings.
This should be corrected to have ALWAYS three. If the outer one should be cut a bit - so be it, and in fact such happens.
The pattern I see is:
ZL 5: all missing - should be 500, 100 & 2000 km
ZL 6: 200km - two missing (maybe here only one additional makes sense: 400 km)
ZL 7: 100 & 200 km - one missing (should be 400 km)
ZL 8: 50, 100 & 200 km - good
ZL 9: 25, 50 & 100 km - good
... all good
ZL 13: 1, 2 & 5 km - good
ZL 14: 500m, 1 & 2 km - good
ZL 15: 500m, 1 & 2 km - outer ring nearly invisible - a 200m ring would make more sense
ZL 16: 500m - 2 missing (100 & 200 m e.g.)
ZL 17: 100m - 2 missing (200 & 500 m e.g.)
To make life more interesting - this is latitude dependent, too :-)

Hello,

I have strange issue with track recording.

I use offline 1 arc second srtm data, that replaces gps values and when I finished recording I noticed strage things on track chart.

1. I was biking on really plain surface, but on chart it looks I passed really short but very steep hill (slope over 20% which is weird)

2. I stopped couple times by traffic lights and was waiting for the green light at least 30 second each time. On chart I can't see that speed drops to 0 value

3. My configuration is: record every 20m OR 3s so I should have had couple times 0 values on my time chart.

4. The problem with crazy high slope doesn't happen if I change recording conditions for example: record every 20m AND every 1 second but speed doesn't drop to 0 which is obvious (no moving by 20m - no points to record)

Is there any option where I can change interval for chart data for example - show slope and speed by every 100m or every 2 minutes? I think, the problem is, because it takes slope from each point to next one and ig there are 2 points that are really really close to each other it cause calculation issues.

Michael

(https://postimg.org/image/mjurh366l/) . (https://postimg.org/image/u13ywavpp/) .  (https://postimg.org/image/hnr4pe619/)

@gynta: hmm not sure I understand. Topics are marked as read when you tap on them to open in browser or when you tap on an eye in top right corner of post.

@Bucky Kid: I've already read about similar problems, have to check it, thanks.

@michaelbechtold: thanks for test with rings. Generally they are all incorrect. These rings should be on normal online/vector maps elipses, and not real circles. It is not visible for small distances, but for distances more then100km , this should be visible a lot. Also because of this, I see no sense in values above 100km. I've anyway added at least 200m ring.

@cokeman: not sure how may I help you. I've downloaded attached gpx file and filled values with SRTM 3'' downloaded over Locus and values are in range -5% / +2.5% , so it looks a lot better. MAybe a source of your 1'' isn't as accurate as you think? :).

Quote from: menion on November 09, 2016, 09:30:28Topics are marked as read when you tap on an eye in top right corner of post.

yep, and after new versions update - Locus mark  same old news as unread and i  have to read/mark old news again.

(https://postimg.org/image/562xat0gz/) (https://postimg.org/image/hyr1aqc2r/)

hmm and we are talking about Locus Map Free installation right? Have to check it then, thanks

i didn´t know since when, but i didn´t get any notification (FREE and PRO) from auto backup anymore

OS Street View is still categorised wrongly as "OSM Other" in the list of online maps. It ought to be "Ordnance Survey". Possibly confusing, but nothing to do with OSM.
Previous post: http://forum.locusmap.eu/index.php?topic=5199.msg45169.msg#45169

@gynta: hmm I was not watching this too carefully. Because this "news list" is just a simple rss reader (http://www.locusmap.eu/feed/), there are no ID of topis. So Locus keep information if topic was read or now, just by using it's title! And maybe Michal changed title of some topics, which made them "unread" for all users? Hmm ... I'll change this system to next version to be more robust, thanks! Expect that all topics will be "unread" in next version ... for the last time I hope :).

@balloni55: for you, auto-backup stopped work at all? Seems another topic that needs more time invest. I wasn't ever 100% satisfied with it ...

@john_percy : hmm and I thought, I've already fixed it, thanks

@menion: fixed in Store but not in Map Manager.

Quoteauto-backup stopped work at all?

no, autobackup work with FREE and PRO, i get no notification althought it is selected in backup dialog

BTW, where is my post :o
Re: [APP] - version 3.20.x (31. 10. 2016+) by balloni55 (Versions)
    Today at 08:12:36

on track overview i see some tracks with "strange" info, whats that?
(https://postimg.org/image/mhzwzmq7z/)

V 3.20.1.1
if dots between words are missing, i get unintelligibly info
(https://postimg.org/image/u6npi55q3/)

Weird with backup, because as I see in code, there is still exactly same system. Even a quick check seems to work correctly. I'll be watching it ... EDIT: sorry, I've got it ... thanks!

About "strange info" ... you ask me? :). It has to be some description in track itself, probably caused by import?

Problem with input of w3w ... hmm, I'll improve it little bit, thanks

QuoteIt has to be some description in track itself, probably caused by import?

thats it ;)
i´ve importet some track.kmz where this infos are insert, sorry

Quote from: balloni55 on November 10, 2016, 12:35:57
BTW, where is my post :o

Code Select Expand

Re: [APP] - version 3.20.x (31. 10. 2016+) by balloni55 (Versions)
    Today at 08:12:36

??
here:
http://forum.locusmap.eu/index.php?topic=5430.msg45716#msg45716

Quote??
here:
http://forum.locusmap.eu/index.php?topic=5430.msg45716#msg45716

my post 8:12 was between yours # 29 from last night and Johns # 30 today at10:51
menions give me answer #31
i see my activity on main page "Infocenter/Recent Posts"

Quote from: 0709 on November 10, 2016, 22:13:26
An old item....how to make gesture control more reliable.
Triggered by new report in Idea:
http://help.locusmap.eu/topic/add-power-off-button-on-screen#comment-34508

On desk I know how to generate succesfull gesture control by single wave.
Not using double wave control, as is even more "time" critical.

When last discussed (a year ago?) I spent ages trying to get gesture control working. The Sony Xperia Z1 IR sensor was working fine with simple diagnostic app, so clearly hardware is OK and sensitive enough, but Locus was always totally unreliable so I just gave up. Would be happy if this could be made useful with single wave action, because manual turning on power button with glove while cycling is problematic.

With the present user interface, changing overlays is rather complicated. The current overlay has to be removed with the "Remove" button , then a new one has to be selected with the "Select" button. As the overlay can be simply switched on and off, either with the eye icon on the map Layers slide-out menu or the switch on the Map Overlays pop-up screen, the "Remove" button is someone superfluous. I suggest either (a) click on the overlay name to change to a different overlay or (b) change the "Remove" button to "Change overlay" button. That reduces clicks by one.

And a little history of overlays would help nicely, too !

Hello menion
on german board a member reported that panoramio didn´t work
another one reported this service has terminated :-[

and if i try to display it with current BETA locus stop ???

Quote from: balloni55 on November 13, 2016, 09:29:32
Hello menion
on german board a member reported that panoramio didn´t work
another one reported this service has terminated :-[

and if i try to display it with current BETA locus stop ???

Confirmed. Panoramia photos no longer display on current app. Beta app crashes. Panoramia discontinued.

@0709, @Andrew Heard : hmm so let's imagine, I'll change "gestures" to support also something like "long cover". Are there any negative possibilities? What if you put device with screen turned off, into pocket? Then this will turn it on, right?

@john_percy, @michaelbechtold : as many other features, this one I think is not used in some urgent hurry, so one more tap is not considered as a problem. I'll think about it anyway ...

@balloni55 , @john_percy: yep, it took me few years till I finally added this feature to Locus and then they terminate it ... http://www.panoramio.com/maps-faq , well, what to say :).

Weird routing announcements for roundabouts.

Have used BRouter and Locus for routing again since a longer break. Latest beta tells "Take minus one exit" for the first, etc., i.e. subtracting 2 from the correct counting.

Any idea ?

TXs Michael

Quote from: michaelbechtold on November 16, 2016, 21:09:03
Weird routing announcements for roundabouts.

Have used BRouter and Locus for routing again since a longer break. Latest beta tells "Take minus one exit" for the first, etc., i.e. subtracting 2 from the correct counting.

What the profile, the roundabout location and course, to reproduce ? For the latter two, the best if provided with the "permalink" from BRouter web (http://brouter.de/brouter-web/).

But I guess it has more to do with hint generation, that is not defined by profiles. But especially older profile can use "hard way ignoring" with costfactor >=10000, that leads the BRouter to pretend the way does not physically ever exist.

TXs for the instant reply, poutnikl.

BRouter is current on my Android. And the route shown on the map is perfectly OK. Only audio message sucks.

The profile I used in the standard Locus profile "Short"; advanced mode shows "Car-eco". No "avoids" set.

I had saved the route and just checked. It correctly shows "Take exit 2", while the voice had said "Take exit zero" this morning.

Saw the video - good to be not alone :-)

hi guys,
thanks for a report with roundabout. Issue found and fixed! There was indeed a problem with shifted number by 2 , so first exit was -1 exit :).

@0709: in next version will be another gesture option "cover" so please try it. I'm still not perfectly sure how to handle it correctly, so now "cover" is event when proximity sensor will be covered for longer then 500ms and shorter then 2000ms. Shorter cover (less then 500ms) is detected as "single wave", longer then 2000ms as a permanent cover (like place of device into pocket etc.).

New Beta version 3.20.0.5 just uploading!

1. warning! I've updated big number of various tools needed for developing as well as few libraries that are used in Locus, all at once. Because of many changes mainly in Google libraries, I had to do also many changes in source code of Locus itself. So if you notice any unexpected behavior (crashes or not working function that previously worked), problem is definitely not on your side , so please just write me shortly where to find this problem. Thanks!

@0709 : I didn't tried new gesture control option in the field, so if it won't work, just leave it, don't waste too much time on it! Thanks. Btw. nice photo :)

Hello menion
backup notification is back again  :)

behavior of "route and measure" in PRO and Beta and i didn´t know it´s what you want

- if i click anywhwere on the map on +button i get a green point (no blue icon) :)
- if i click on an existing POI label+, i get a blue point (WPT) with a blue icon named similar as the POI :-[
ok, i know how to change, but for me it would be more logically i always get a green point if click once

@0709: thanks, good point. I think thanks to this, I've found optimal combination ... so in next version.

@balloni55: hm in this case, it is intent. I made it because I've considered that if you add point with mentioned steps, points is more important for you so it deserve to be automatically "via point". You think that more common scenario is opposite, so added point is rarely changed to "via point"? Heh .. it's quite individual problem ... maybe a work in terrain should help to decide ...

I tried 1-wave lots of times again. It crashed once - you should have received crash report. Other times it now works (a little) but quite unreliable. Sometimes screen turns on 5 seconds after wave, sometimes soon after wave, mostly never. The Sony diagnostic app for testing IR sensor always works reliably. Oh well.

Hello menion
if i use route&measure and before created waypoints are out of the visible screen, lines between this waypoints disappear when i create next waypoint.
This lines are visible again if i zoom, or if i these "lonely" points are visible on screen when next waypoint is created, sorry for complicated description, please view screencast
https://www.dropbox.com/s/41f410zshq5qmdv/refrech_line.mp4?dl=0

behavior is on PRO and Beta

@balloni55: ah nice video. I noticed this already few times, but was never sure, how to simulate it, perfect, I'm going to fix it ...

@0709: hmm nope. Why and where you need this?

Ok oh. Main reason why I enabled this, was really bad speed results after export/import of GPX files. In case of recording every second, then every millisecond counts :).

my post #36 "what3words"
your answer

QuoteProblem with input of w3w ... hmm, I'll improve it little bit, thanks

no improvement :-[

Hello menion
V3.20.1.6
- tigger guiding notification, solved :)
- WMS rescale based on parent map and center map, solved :)

- w3w,  not solved :-[
- "lonely points" while route$measure, not solved :-[

new problem:
- some caches display "-1" Fav point in POI list indepndent they have non or more, till i update the cache

idea:
please remove "Items tab" from data screen

Thanks for a tests balloni!
- what is a problem with w3w?? I though that your issue is error message you see. So I've changed it little bit, that's all ...
- lonely points not solved? Hmm this s really weird. You see exactly same issue as on your video before?
- "items tab" .. it's too early for now

Hello menion

QuoteI though that your issue is error message you see. So I've changed it little bit, that's all ...

ok, but the new message "Field value is not valid" didn´t help an inexperienced user when he  insert three words separated by space :-[
this screen is so large to impement an example e.g. search term word.word.word
or words must be separatet by a dot

Quote- lonely points not solved? Hmm this s really weird. You see exactly same issue as on your video before?

sorry i have deleted the video, so i cant say it´s exactly the same..
try it in ZL12 or ZL13 with length of a line >10Km, if created lines are out of screen the lines disapeare while creating the next point. If necessary i provide a new video ;)

can you confirm behavior with FAV points?

Geofun is in list of Co-apps available but not in list of Co-apps to place as "funktion to panel".
"Add link to app" work
BTW, what is the difference if both options are possible?

@balloni55: hmm not sure why (if) wasn't visible -1 for favorites before. -1 means that value is not defined in cache. So I'll hide "favorites" icon with number in next version in this case.
"Geofun" added to list, thanks. Difference ... there is no difference at all. Option as "co apps" was made first and when new option as direct link to application was added, I've left option over "co-apps" (which is a little bit more simple from my point of view).
"w3" ...ah ok, thanks, I'll try to improve it ...
"lonely points" ... hmm I'm not able to simulate it anymore with latest version, interesting. Video won't help here. I'll try it later with other device. Not a serious problem though, as it's in Locus for years :).

@0709: hmm glad to hear, thanks!

Quote from: 0709 on November 27, 2016, 12:52:07
Locus V 3.20.1.6.
Field test: Single wave/touch gesture control proximity sensor. For me = reliable.
So far the best (in Locus) "gesture function" version I've seen.

single wave gesture very much improved thanks, not 100% but I hope may now be usable

Bug with full screen> edit track > save > there is no back button

I like the new track waypoints list, bravo.

Single wave now works reliably and well. Too well for me in fact. I run Locus in full screen mode and it has become impossible to swipe downwards to reveal the soft Back button in order to tap it twice to exit. A downwards swipe is interpreted as a single wave and turns the screen off.

Hello menion
Beta and PRO
if i record a audio as an attachement to a poi, it´s stored as .3gb file and work well :)
but it is not possible to select these .3gb files (it´s grayed) as an attachement to a poi :o
.mp3 files could be attached well

@john_percy ... hmm interesting side-effect. Any idea that may helps here? Slide from bottom > up, so reverse then now? Or if you have sensor on one side, sliding on opposite side may help as well

@balloni55: in this case, Locus only request from system ... allow user to pick an audio file that has defined mime type "audio/*". Unfortunately it looks like Android ignore 3gp files in this case.
Seems I have found same problem asked (http://stackoverflow.com/questions/35482036/correct-intent-to-show-only-audio-files), but no answer helped here. Hmm best looks like use total commander or other file browser (tested and works fine) for selecting these audio files.

@menion. Slide from bottom up works for me. Or choosing double wave. But I wondered if adjusting the timing of the wave detection might be a more general solution.

QuoteHmm best looks like use total commander or other file browser (tested and works fine) for selecting these audio files.

confirm, use TC work in this case
thanks

We may try it, but I'm not sure it will help here. Or better, maybe it help anyway it again create from short quick wave, something like before ... "long wave". Because exists option to show bars by pull from bottom, I should with current system for now ...

EDIT:
@balloni55: I thank You!

V3.20.1
- The preview in the track list is again not taken after an update.

Beta V3.20.1.6
- Updating the track preview by a long press on the thumbnail works only with the first track, the second does not work anymore, in V 3.20.1 it is still in order

- With Vectorkarten is no more cache used? Please re-enable it, preferably equal the cache still larger


(https://postimg.org/image/5uixtqwk3/)

Hi,
hmm maybe I've found one issue in this track preview, I'll try to fix it, thanks!
And about cache of vector maps > there were no changes for very very long time. Cache for vector maps should work in case of disabled autoloading and disabled shading.

I see changes, note the reloading of tiles when you move the map
both versions are with the same settings (shading is on and autoloading is on).

This is the Beta Version Screencast
https://onedrive.live.com/embed?cid=8AF4739A80D3388B&resid=8AF4739A80D3388B%2116375&authkey=ANdh7GDmyHvvSqs (https://onedrive.live.com/embed?cid=8AF4739A80D3388B&resid=8AF4739A80D3388B%2116375&authkey=ANdh7GDmyHvvSqs)

This is the Pro Version Screencast
]https://onedrive.live.com/embed?cid=8AF4739A80D3388B&resid=8AF4739A80D3388B%2116376&authkey=ACc30VsDA26R2z4] (https://onedrive.live.com/embed?cid=8AF4739A80D3388B&resid=8AF4739A80D3388B%2116376&authkey=ACc30VsDA26R2z4)

hmm I do not see big difference on video, to be true. It has definitely nothing to do with a cache, because in case of enabled autoloading, cache is disabled at all.
If, then it may be connected to one optimization I had to disabled in last few beta versions. It had almost zero effect on my device, but it is possible that on slower devices, it will have bigger effect. Thanks for notification, will keep this in my mind.

Quote from: menion on November 30, 2016, 15:39:55
...maybe it help anyway it again create from short quick wave, something like before ... "long wave". Because exists option to show bars by pull from bottom, I should with current system for now ...

@menion @0709 - although the gesture system is now working for me, it relies on detecting the object within a minimum/ maximum time window, and the display toggles on the "trailing edge" of detection. If hand is too fast or too slow then no action, only frustration. As Willy suggested a long time ago, maybe a further improvement and simplification is trigger on "leading edge" rather than "trailing edge" of detection - just wait until object is detected for minimum time then toggle display state, and completely ignore the maximum time? Example - I just hold hand over sensor, and maybe 50ms later display toggles. I remove hand any time later, no change. I again hold hand over sensor, display toggles. Simple and more timely operation, simple to document, simpler to code, more reliable.

I had been having trouble for quite a while because of Sony "Stamina mode". Gesture would work well for many minutes, then not at all. Probably after inactive time the IR sensor was turned off in this power saving mode. Thanks @0709 again for solving problem.

@menion 3.20.1.8 release notes in app: link from 1st topic "option to disable internal..." doesn't work - "application missing". Other links work, so I assume URL is broken.

@menion I reported this bug a few days ago but no acknowledgement - maybe you missed it - in full screen mode > edit track > save > there is no "back" button, no way to exit this screen without dragging down status bar.

Hello Andrew,
there should be no "minimal" time limit. On single wave event, Locus should react as soon as possible. Maximum time limit is set to 2 seconds! Reason for this, is to prevent action in case of cover of sensor by some flipcase, or placing device to pocket etc. 2 seconds should be enough time to cover sensor and then move hand away I believe.

Problem with " I just hold hand over sensor, and maybe 50ms later display toggles" is as I wrote ... how to detect for example device placed to pocket?

- link on web page: damn, thanks ... I always copy link from help.locusmap.eu, but it is sometimes copied without starting "http://", thanks
- issue, sorry. If this is what I think it should be, it will be solved in next version, thanks!

Quote from: menion on December 05, 2016, 09:28:19
...On single wave event, Locus should react as soon as possible.

@menion - it appears the display toggles on the "trailing edge" i.e. when hand is removed. Could Locus react faster if display toggles on the "leading edge" i.e. when hand is detected? This would save 0 to 2 seconds of delay.

Quote from: menion on December 05, 2016, 09:28:19
...Problem with " I just hold hand over sensor, and maybe 50ms later display toggles" is as I wrote ... how to detect for example device placed to pocket?

@menion - separate flipcase mode? it appears in order to accommodate the flipcase scenario the single wave mode is compromised.

But there should be really no delay. It's all about what is "wave"? You wants mode "cover". So simple cover of sensor trigger change. Currently it's in mode "wave", which means "cover" and "uncover". Immediately when Locus detect this uncover activity, screen should "toggle".

I now cannot say if current solution is perfect, because on me & bike it's too cold out now :) and unfortunately without some field tests, hard to say ...

I think we agree. You say "cover" and "uncover" so there is a delay. "uncover"=my term "trailing edge". I was just suggesting "toggle" on "cover" (leading edge) instead of "uncover". No need for field testing, should work just as well in office. Now even with thick gloves I can toggle the display, previously I had difficulty feeling where the tiny power button was. Other good news - I haven't noticed any increased power consumption on short 2hr ride. Normally 2%/hr with track recording, 3%/hr with track+navigation. Will do 13hr ride on weekend to confirm these numbers.

So why do I keep getting this Activate Device Administrator screen now. Not all time, but every so often.

Seeing a consistent FC in the moment I activate Live Tracking in latest Beta. Anybody else ? Deleting all data in Android does not fix it.


Gesendet von meinem LG-H850 mit Tapatalk

@menion - another idea/ observation/ suggestion regards gesture control - I've noticed a few times, not many but still annoying, that when I gesture to turn on the display, that a menu or screen or other app is displayed because the gesture is also a tap. I find the most reliable way to register as an object is to hold my palm over the IR sensor, but of course there is risk that Android thinks I am tapping display. With non-conductive gloves it then becomes impossible to return to the main map without taking off the gloves. Suggestion: would it be possible to have a short period after turning the display on in which all taps are ignored? I can't think of any reason a user would gesture then expect to accurately tap within say 100ms.

@0709 has just recorded a video https://youtu.be/uTJNALgAawE (https://youtu.be/uTJNALgAawE) demonstrating leading & trailing edge trigger of display toggle. His DSTO app is using leading edge trigger, and is clearly more responsive than Locus single wave trailing edge trigger.

Related, and good news, I had suspected that Sony Xperia "stamina" power saving mode was causing unreliability of Locus gesture mode - I had a "theory" that after a period of inactivity Stamina mode was turning off the IR sensor. But I've now done many hours riding and testing, and Stamina mode has made no difference, and more importantly there was no obvious increase in power consumption with IR sensor turned on with Stamina mode disabled and gesture enabled.

@menion - have you recently improved navigation behavior for situation where initial position is not directly on the track? I had observed in the past that with auto-recalculation off, sometimes when navigation is started the large question mark icon never changes to a proper turn icon even once position is directly along the navtrack:
(https://postimg.org/image/jyfcpypuh/)
I have been testing this again and certainly for a few walking tests with 3.20.1.8 I now observe that navigation may switch between question and distance icon a few times, but will correctly stabilize once the track is reached:
(https://postimg.org/image/pj6b521zr/)
Maybe you improved behavior but forgot to mention in release notes? If so, thanks for the worthwhile improvement.

@john_percy: this screen should appear just once. After you tap on "activate", for current install of Locus Map, it should not appear anymore. But you see it everytime, Locus tries to turn on/off screen?

@michalebechtold: I have no such experience, sorry. Log needed

@Andrew Heard: issue with Locus Map vs DSTO application is still the same ... how DSTO detect if device is covered by cover or placed into pocket? I consider current solution as final. If you need something like DSTO, then why don't use this application for this task?

And behavior was little bit improved for navigation started off the track. Good to hear it works fine now.

Should have reported earlier: I deleted the ID and created a new one. Now no FC any more with LifeTracking :-)

thanks willy, issue on 4.x devices, damn ... I'll fix it tomorrow ...

Quote from: menion on December 08, 2016, 12:32:39
how DSTO detect if device is covered by cover or placed into pocket?

@menion - DTSO (not DSTO) has separate flipcover & "single wave" configuration, so subtly different use-cases in-pocket and on-handle-bars are optimised instead of one-size-fits-all compromise solution; don't get me wrong - it's still a great feature

Quote from: menion on December 08, 2016, 12:32:39
I consider current solution as final. If you need something like DSTO, then why don't use this application for this task?

pity, It would be interesting to see how many users are actually using Locus gesture as there has been so little comment, DTSO didn't work for me when I tried it a year ago; I have just installed the latest version, it now turns on the display with single wave on "leading edge", so very quick & responsive, although I can't get it to turn off the display; I'll discuss with @0709; the Locus implementation does work but I think could just be improved further; I love Locus & tell everyone about it, but if Locus aims to be the best GPS app for cyclists then why have to install another app for even better gesture control

Another reason to favor Locus: DTSO is working for all apps whereas I only want gesture control to operate while running Locus. DTSO can be disabled of course but...

Quote from: menion on December 08, 2016, 12:32:39
And behavior was little bit improved for navigation started off the track. Good to hear it works fine now.

in few short tests, navigation start has improved a lot, previously sometimes never "started", now actually works

Quote from: Andrew Heard on December 08, 2016, 23:11:07
pity, It would be interesting to see how many users are actually using Locus gesture as there has been so little comment

I also use gesture for display on/off all the time when riding mtb with my Sony Z1 Compact. The single wave detection with current non-BETA versions is not perfect, but "OK" I think.
Actually, waving in front of the phone doesn't work very reliable for me, I have to wave pretty near by the sensor for the detection to work, so I ended up touching the front of the phone where the sensor is located much like pressing an "invisible" button. Anyway, it still is a lot easier than finding and pressing the tiny power button on the side of the phone! So it's ok for me.
I guess the distance for reliable detection might be different with every phone model. Maybe Locus could implement a "calibration mode" for the sensor in order to adept to different phones/sensors?

One problem with gesture control I'm experiencing is it's behaviour in my pocket. When I forget to disable gesture activation and put the phone into my pocket while Locus is still active, I oftentimes end up with the phone in some settings menu or even "writing" a message to someone ;-)
Maybe this could be improved somehow.

I did not have the time to test the modified gesture control with the current BETA, though.

Quote from: zossebart on December 09, 2016, 13:20:57
Actually, waving in front of the phone doesn't work very reliable for me, I have to wave pretty near by the sensor for the detection to work, so I ended up touching the front of the phone where the sensor is located much like pressing an "invisible" button.

@zossebart - my exact experience, the Xperia sensor only works over short distance, so I have to hold (not just wave) the top/left of phone, but like you end up "tapping" some Locus button along top of screen, so end up with some other screen displayed instead of main map. I prefer Locus full screen mode (on small screen) but if I keep non-full-screen then there is one "row" of space at top of display, and this reduces chance of a false-tap. I also experimented with moving all Locus top buttons to right side, but wastes more space. Nearly easier to stick with power button. All it would need (sounds trivial from user point of view) is for Locus to ignore all taps for short period after toggle of display state. I am also experimenting with phone in 180 degree portrait mode so IR sensor at bottom (maybe less false taps), but results in new problems (of course!).

Point detail location not displayed on latest beta. See screenshots which are self explanatory
.
The first screenshot is with the beta, the second screen shot with the latest full release.

Ah thanks John! I've completely missed this unwanted side effect. Fixed

Hi Menion, the near freezing effect in high zooms is now reproducible: switching on GPS in Locus creates the effect. Switching off will make Locus fast after the slow reaction time.
Unfortunately Tapatalk does not show the resp. issue report, hence reporting here.

Gesendet von meinem LG-H850 mit Tapatalk

Just upgraded Android 4.4.2 tablet to latest beta 3.20.1.9 - immediately crashes at start. 3.20.1.9 working fine on 5.0.1 phone. I think @0709 reported same, but I can't now find his comments or which subject.

@michaelbechtold: quite a problem ... I have two +- new devices and both waits on Android 7 (manufactured promised December/January) ... on simulator it works fine for me and without simulation on own device, I have almost no chance to fix it.

@Andrew Heard: I spend on this almost two days. Currently it looks I'll have to remove support for Android 4.x :(. Testing anyway in progress ...

Quote from: menion on December 12, 2016, 07:48:22
@Andrew Heard: I spend on this almost two days. Currently it looks I'll have to remove support for Android 4.x :(. Testing anyway in progress ...

@Menion - seems problem introduced between 3.20.1.8 & 3.20.1.9. Tablet was fine with 3.20.1.8. I'll have to stick with 3.20.1 Pro, uninstall free/beta on the tablet & ensure no further updates. I assume I should never upgrade Pro on tablet otherwise will become totally useless for any route planning while cycle touring. Hopefully not similar problem with Android 5.0.1 otherwise phone will suffer the same fate. There needs to be a version compatibility test in Google Play to prevent any accidental upgrades:
(https://postimg.org/image/dpd2tqk85/)

Yep, issue started with 3.20.1.9. I'm now anyway unable to generate working version for 4.x devices. Locus Map Pro on Google Play is fine. When Android 4.x will be removed (hope not), udpate won't offer on 4.x devices, so no worry. Only issue now, are people with 4.x that use Beta versions for testing ....

Hello guys,
who had troubles with latest Beta on Android 4.x? May someone (more > better), test this version

https://nas.asamm.com/share.cgi?ssid=0eMOMZ0

Thank you! (in case of same crash, please create me a log)

While playing with new Beta i´ve compared new and old 3D skyplot and i can´t see any benefit of the new version :-\
no difference between GPS and glonass in new version and much more difficult to recognice the sats in the lower part of the display
(https://postimg.org/image/6k5q1o9a5/)
don´t worry, i dont use it and till now also no other user make a comment, so it´s not important but a pity about your wasted time

@balloni55: no worry, there is absolutely no wasted time :). I'm learing OpenGl (hardware rendering) system and best is to learn on something specific, not just by reading books. And only what is in Locus for now that use OpenGl is this Skyplot system. So consider this as first step and I'm accepting feature requests here ;).

What is problem with bottom numbers? Fact that numbers are rotated? It's because for example on my device, I see usually more then 20 satellites and numbers were one over another .. completely unreadable.

@0709: very good, we are saved :). Uff ... thanks!

Quote from: menion on December 13, 2016, 11:19:07
Hello guys,
who had troubles with latest Beta on Android 4.x? May someone (more > better), test this version

https://nas.asamm.com/share.cgi?ssid=0eMOMZ0

Thank you! (in case of same crash, please create me a log)

As written in the help section, this version works fine for me! SGS3 with Android 4.x. Thank you very much! Hope the support for Android 4.x will last for some more time! Really like the app.

Android 4.4.4 (device Teclast A10HD), rooted
Locus 3.20.1.9 - crash on start
Locus 3.20.1.11 - Normal start, my congratulations!

Quote from: menion on December 13, 2016, 11:19:07
who had troubles with latest Beta on Android 4.x? May someone (more > better), test this version
Thank you! (in case of same crash, please create me a log)

@menion - crash on Android 4.4.2 with 3.20.1.9 (as previously reported). Now with 3.20.1.11 first run had crash, but then 2nd run it works, although completely default screen, no offline map, no user buttons, I assume config.cfg not read, other data read from test folder. Probably this is not a problem/ was expected. 3.20.1 (Pro) still working. Well done to find the A4.4.2 problem. Thanks.

Thanks guys for a testing, really useful, thanks!!

So new version published as Beta version on Google Play right now. There are some minor improvements, nothing serious. I would like to publish this version at start of next week as final public version, so feel free to report anything you consider as bug :) ... + small Christmas gift to @balloni55 because I appreciate he care about my spend, not wasted, time ;).

Thanks for christmas gift 8)
now user recognizes gps and glonass :)

a few minor remarks, but i didn´t think they depend on 3D/OpenGl
- # 83 with US flag ?!
- # 83, yellow solarpanel (mean used?) no number in below list
- # 68 + # 80 yellow solarpanel but white number > not used?

(https://postimg.org/image/g9z2ro87x/)

Quote from: menion on December 14, 2016, 15:52:30
Thanks guys for a testing, really useful, thanks!!

So new version published as Beta version on Google Play right now. There are some minor improvements, nothing serious. I would like to publish this version at start of next week as final public version, so feel free to report anything you consider as bug :) ... + small Christmas gift to @balloni55 because I appreciate he care about my spend, not wasted, time ;).

Hello,
Crash detected switching from 2d to 3d skyplot on last beta.
Android 4.4.2
Restored 2d works fine.
Sorry I have no time for better testing

Inviato dal mio SM-G800F utilizzando Tapatalk

Quote from: menion on December 14, 2016, 15:52:30
So new version published as Beta version on Google Play right now.

@menion - good Christmas present with 3.20.1.12 now working again on my Android 4.4.2 tablet, relief. Also confirm crash with 3D skyplot. Best Christmas wishes to whole hard working Locus team.

QuoteCrash detected...3d skyplot on last beta.

confirmed...

Quote from: gynta on December 14, 2016, 22:42:19

QuoteCrash detected...3d skyplot on last beta.

confirmed...

Same here. On the other hand newer tried or really "realized" about the 3d skyplot before.

@balloni55: hmm interesting issue with satellite numbers. From where came sat no. 83 ... no idea :). Looks for me more like wrong visible number. I'll be watching it ...

Color of numbers is still same (sometimes is lighter when sun shine on it :) ). Color of satellites should match bottom colored line. So red is satellite with bad signal, yellow is better, green is best (to be true, I've never saw green color, seems I'll have to improved range ...)

Thanks all for bug report about crash. Fortunatelly Willy (@0709, thanks!!) send me a log. There seems to be some issue with memory. I'll try to reduce size of earth texture, hope this will help on 4.x devices.

Hello my dear and patience friends,

seems that it's two months since last version. I've probably completely forget to publish new version sooner, funny.

Anyway after two days of testing, it's finally uploading into Google Play. List of changes is quite nice (and long) and even that there aren't any huge changes, there is many smaller and I believe that everybody find something useful there. At least I hope.

Have a nice last days of this year, I'm preparing for bug-fix version (that simply have to come after such changelist) and then really awaits some free days, so excuse me :).

And thanks for help and intensive testing even during winter!