version 2.9.0 & 2.9.1

Hi Menion,

lot`s of cool improvements, but I found a small issue:

When moving the map from a location which is covered by vector map A to a new location which is covered by vector map B, the map is not switched automatically any more. Last version did that properly.

Hi,

please check you have enabled auto-loading in settings. Menu > settings > maps advanced > vector maps part, auto-loading

That`s it.

The best of this app is your lightning fast support... ;-)

Thanks!

when I installed to 2.9.0 yesterday, everything was running ok on my HTC Desire... today morning I found a new update - 2.9.1, installed it and started Locus. Locus started normally. After that I wanted (via Geocaching Live) to Load pocket query. When I clicked on "Import" button, Locus got frozen. I was not able to report it either, as reporting started crashing as well. I have closed the Locus and tried to start it again but without any success. After starting the application, it immediately crashes everytime - again I am not able to report, when I click on report, the window just disappears and that`s it... Please help :(

Good day skubko,

between 2.9.0 and 2.9.1. was really a very few small changes that affect only getting a root directory and small change in bluetooth.

problem with inability to report is bad. May you please check this method http://docs.locusmap.eu/doku.php/manu... is you have Android below version 4.1. If not, I would suggest simply try to restart your device

Hi Menion,

thanks for your reply. I have restarted my device (I have Android 4.1.2), but it was even worse afterwards...I did not see the Locus among list of applications anymore. It disappeared also from the list of "My Apps" on Google Play, so I must have installed it again. After this installation was successfull, I was able to start the Locus normally again.

So the issue is fixed now (I did not want to play with it much before, cause I was affraid of loosing my points but everything is back and ok).

skubko, fact that Locus disappear from list of apps etc. mean that it has to be some problem outside of Locus, because application itself, have no chance to affect this. Anyway I`m really glad that it works now!

Hallo Menion,

Not Sure, if it has something to do with the issues of skubko above, but since I installed your 2.9.0 testing version for BT Zephyr testing I am facing the following issue:

- my standard Locus Pro app has NO custom items anymore!

- in the first place I did panic....all Poi, maps, settings gone...but no

- settings like button, styles are still there

After some investigation I found, that all files and folders of locus directory on my SDCARD0 had been copied to SDEXTCARD (Samsung note 2). Maybe not copied but rather somehow moved, for in the Locus directory on SDCARD0 no more custom items, so now no surprise anymore, way Locus Pro version did not find my customized stuff.

And to make it even more funny, the 2.9.0 testing version has still all my custom item, as it obviously now operates from SDEXTCARD rather than from SDCARD0.

So what should I do now, copy everything back to SDCARD0....AND NEVER EVER INSTALL A LOCUS TESTING VERSION AGAIN :-(

this has nothing to do with testing version. Few hours after 2.9.0, I released 2.9.1 which should fix this problem. Few people already confirmed that new 2.9.1 works again fine, so I suggest to check your Google Play app and update locus before you start to copy all data. Also new created directory, which is empty (except some generated content) should be completely removed

Ok, thanks, works again as usual...only complaining at start up, that it has found to locus installs, but it is using the right one, on the external card.

hmm if you see this notification, then you should remove from your card/internal memory directory that is not used. It`s main reason of this notification

Unfortunately I can`t, for I would loose the links to my old Poi photos, which I shot with my former phone (to SDCARD), pointing now to wrong storage position (EXTSDCARD ). Keeping them in the old locus sdcard folder is much easier than changing 100+ photos by hand in the Poi screen.

then you have two possibilities

1. you may experiment. Locus should be able to locate photos even if you move Locus/data between locations. If you have time, backup both directories and experiment.

2. if you don`t want to waste time on this, you may at least remove this "Duplicate folder notification" by this settings http://docs.locusmap.eu/doku.php/manu... . Just locate "notify_duplicate_root_folder=1" and change value to 0

Wow, I am very impressed. Your obviously already solved this subject without letting me know ! ;-) Yes, locus now finds the photos in the "new" folder, it did not a few month ago, or so! I go now and delete the now redundant folder...but just to letting you know, this notification even popped up, when locus was not running anymore and opened eg ES File Explorer. But thanx again

Hello Menion,

I found a minor problem in the 2.9.1 version: After quitting the app the phones gps reciever isn`t deactivated anymore. Is someone experiencing the same problem? Phone is a Samsung Galaxy Note II running stock firmware.

Regards

I checked and found that there was sill a running process of Locus. So for some reason the app doesn`t shut down properly.

Any ideas how to fix this. Killing the app manually after every use isn`t quite an option....

you`re correct. It`s about month when someone reported this on forum, so even if Locus now search in better way for photos

And notification is quite funny. It was not working for some time, even if it was in code. So I found it, fixed and now everybody reports this :). I`ll have to remove it and do it in better way ...

Hello Paul,

this is related to this https://getsatisfaction.com/locus/top... . Or better, GPS problem is related to fact, that if you close Locus with enabled GPS, it`s not completely closed. Fix will come soon

I like the change in the Satellite screen with the red and yellow circles.

I can confirm the "Locus not stopping when GPS is active " issue, in 2.9.1. But I see no difference in behaviour when I first switch off GPS (with my Widgetsoid button) before I close Locus.

State Vector 17 Vector13 Vector10

2.9.1 16/12/16 28/18/25 35/27/33 seconds

2.8.7 14/14/12 18/19/18 28/27/31 seconds

I must confirm Jusc`s remark (in the forum) about no speed gain with 2.9.1

On my Defy android 2.2.2 using the "famous" Netherlands HIke Vector map I compared 2.9.1 vs 2.8.7 ; three measurements each in the same order without GPS (was switched off through Widgetsoid). Vector 17 is my start state. After the measuring I zoomed out to 13, closed Locus and then started the measuring for zoom 13 etc (so the zom state was loaded once before the measurement started).

Measured from hitting the Quick Button on my screen till disappering of the white info screen (the map is complete then on the screen).

With 2.9.1 the second measurement is without stopping Locus through the task manager. The third is then after stopping it through the taskmanager.

This comment is not about speed of render process!

Henk, I think you used Locus in this strange way (zoom to a certain level, close Locus and then start it again) in order to be able to measure the time it takes.

But are you really leaving Locus while being on a tour?

If yes, I`d recommend to activate "Use Locus as a service" and leave Locus screen with Home key instead of back key then you should see the map again almost instantly, i.e. without rendering it again. The price for this optimization is that Locus stays in memory.

Hmm I did some optimizations between 2.8.7 and 2.9.1, it`s true, on second side, in styles are some new features like symbols over hiking paths and some others, so generally 2.9.1 version draw little bit more items at once then before. I also reduced a little bit number of cached object. Many people reported "OutOfMemory" errors cause by this, so maybe in final, speed is little bit slower then in 2.8.7 ...

Anyway if someone have free time and want to help make new version better, here is opportunity ;)

http://forum.locusmap.eu/viewtopic.ph...

Thanks Tommi. No. I do`nt close Locus during a tour but I thought, since Locus shows an empty screen at startup, it was rendering the vector maps also during startup. If my measurements were not relevant I am sorry.

I think that measurements are fine, only there were small changes in increased number of rendered items and in system of caching. So I personally think, that results are possible, so new 2.9.1 is little bit slower then previous.

I think it needs to render also during startup (if the tiles to display are not cached).

I wanted to show you a way how you can use your phone`s homescreen or whatever also during a tour without the need to wait such long times when you return back to Locus. Did you try (on the sofa)?

Again Tommi, I do not shut down Locus. When not on the couch, we mainly use it for guiding along marked tracks with audible notification - beep when to far away from track - so always on and GPS always on but screen off. Either by phone-system settings (1 minute) or by hardware button short press. When it beeps or when the markings on the physical track fail, I simply switch the screen on and there is Locus instantly.

This way we manage easily 8 or 9 hours guiding a day on one battery.

I tried "running Locus as a service" but I see no difference with my "screen off" usage. Locus does not get killed on incoming phone calls or anything else.

The only waiting in the field is when zooming in or out on the vector maps for more orientation or more detail. But I can live with that.

Henk, if Locus is alive for whole 9 hours even if you receive phone call etc. than 1) it`s quite a luck

2. or you have more free ram so your device do not has need to kill background processes

I think, that tommi though you kill locus in same way also in terrain. Anyway if sometimes happen to you, that you`ll see locus loading screen when you turn screen on, then it`s because locus was killed and now you know simple settings, how to prevent this.

Hmm as i think about it, fact that guiding is active, keep Locus awake for a while, so it`s maybe reason that it`s not simply killed

Hi. Great news that HRM like Polar & Zephyr are supported now. I tried my Polar Wearlink and it is detected in BT manager without problem. But I have`t find any use of it in Locus, e.g. include heart rate in track record or display it on screen. It is not implemented yet or some plugin is needed? Or am I only missing something? (have PRO version)

you can create a dashoard to view values: eg:

Download: -> here

Open the zip - copy files to ..locus/data/dashboard/..

Add the dashboard function to the right panel and select your dash.