Messages

Zdravím,
omluva za pozdní reakci.

Pády jsou divné. To, že se aplikace zpomalila před pádem zavání nějakým problémem s pamětí. Jeden takový velký jsem aktuálně opravoval ale děl se pouze v případě, kdy běžící navigace dělala velmi mnoho přepočtů.

Opravil jsem ještě jednu drobnost, která snížila náročnost záznamu trasy, tak jestli můžeš vyzkoušet poslední Betu (link v mém podpisu), nebo pak počkat na další veřejnou verzi ... mohlo by to pomoci.

Hello Jack,
good observation. Indeed, points with identical names to the category they belong to, do not appear in the search results. I see currently no simple solution, sorry.

During the second half of this year, we should start work on the new version of the offline LoPoints database, which should also solve this problem. Unfortunately, this will be available only in the Locus Map 4.

Zdravím,
díky za další report. Tam těch chybek je ...

Lab kešky se mi povedlo akorát opravit (po té co jsem o víkendu konečně první svojí odlovil  ). Tedy tohle bude opraveno v další Beta verzi.

Počet logů > díky, máš pravdu. To je již opraveno v poslední veřejné betě a lze tedy vyzkoušet.

Hello David,
it has been some time. Sorry, I forget to answer here.

Is there still interest in fixing this issue, if you still have it?

Hello, almost year old topic. Is this still a problem or do you have your solution for this? Because no other person complained for the last year, so I would like to stick with the current solution.

Hello Florian,
what app and what version are you using?
Are you able to display content of the "info" file stored in the root of the Locus Map directory in the device? There should be "user ID" value that may help identify problem. And sorry for the complications!

I`ve read it, but even if I agree it may be done better, app does not have any united simply map-screen system for notifications. We have to create one (soon). Anyway agree it may be improved ...

A, Classic, pardón. Tam je to v nastavení > různé > Výchozí adresáře > Nastavit hlavní adresář.

Pozor jen, kromě komplikované dostupnosti adresáře se i maže při odinstalaci aplikace, tedy je potřeba zálohovat před od-instalací/pře-instalací aplikace.

Jinak to popsané chování je opravdu divné a rozhodně ani update apky by tohle neměl způsobit. Za mě omluva, ale doufám, že v tomto jsem nevinně .

Kdyby cokoliv, hned piš, raději než o něco přijít.

Could you please post more about this issue? Steps to reproduce, exact error description or screenshot of this problem. Thanks

May you post a screenshot of how it looks on your device? Thanks

Hello,
hmm simple and useful idea, but no simple method in the app ... 

What I would do, is to split this long route into separate smaller routes, one for every day and using the navigation (or simply guidance) to let the app navigate along. Then, values from the navigation are visible on the screen or may be used in the dashboard.

Hi Joska,
I`m worried, this one won`t be solvable on my side .

Add-on for Android Wear does not work with the Bluetooth directly, but instead uses internal Android API for it. This internal library then does the hard work ... the communication between devices.

I of course understand that this issue happens only when you start than Locus Map app, so it has to be somehow connected, but I have absolutely not idea how to detect the real reason, sorry.

Hello bongo,
as far as I know, there were no changes in the way, app communicates with 3rd party apps. Can you please point me to the Google Play to app that does not work correctly? There is quite a lot of apps from Garmin, so I need to test the correct one. Thanks

New Beta just published and the issue that caused memory problems on my own device should be fixed now!

https://forum.locusmap.eu/index.php?topic=8855.msg75429#msg75429

Give it a try please, thanksů

[MapGooglePlay_4.23.1.3_1132_beta]

New Beta version MapGooglePlay_4.23.1.3_1132_beta with a few very interesting additions

- fixed! an issue with the app stuck during navigation after recalculations
- finally working the outline color for tracks
- and more

---

Btw in the previous Beta was also highly reduced battery consumption during track recording when the screen was on. On my device, during 3h simulated recording, it was reduced from 30% to 18% (only when the screen is on).