Show Posts

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

Messages - menion

Pages: 1 [2] 3 4 ... 741
seems you try to compute route with an engine that requires internet. Not sure what exactly you try to do, anyway suggest to read about route planner in our manual, mainly this section that probably solve your issue.

Hello Nick,
after download, the map works correctly? Then it looks to me that your transfer was not successful. In the case of using MTP protocol on Windows, it is not un-usual.

Versions / Re: [APP] - version 3.40.+ ( 2. 10. 2019 )
« on: November 07, 2019, 20:53:15 »
And another month behind us ... and winter is almost here ... seems to be a quite "quick" year for me this time.

The little sentiment, sorry. New version published *** 3.41 *** and available to all users already for a few hours. No serious issue is known to me after a day of public testing = so looks good :).

Garmin is always too strict with handling its own format. I and many users spend many days to give proper support for Basecamp app so what you wrote is no surprise. On second side, I remember reports that FIT from Locus worked to some people also in Garmin Connect. So there maybe is something to fix.

I never noticed this problem, but it will be definitely a little complicated to solve. Tracks stored in Locus Map database has, among others, stored small configuration how they may be loaded into route planner. Any of this config is not exported to any format. So to be able to properly fix it, I, unfortunately, need a) exact steps to simulate it or b) full backup of your Locus Map where will be points&tracks database so I'll be able to use the same data as you.

New version:

Versions / [APP] - version 3.41.+ ( 7. 11. 2019 )
« on: November 07, 2019, 20:46:21 »
Important links
- blog post about major version (not yet published)
- list of news of public versions

2. 10. 2019 - Locus 3.40.0

Troubles & Questions / Re: New geocache waypoint bug
« on: November 07, 2019, 08:25:20 »
... and do not worry too much if the update won't be available for you. I'm publishing a new version just for a limited number of users to fix a few more possible problems before all users receive it ...

Versions / Re: [APP] - version 3.40.+ ( 2. 10. 2019 )
« on: November 04, 2019, 08:52:38 »
Hmm with FIT files it is really a pain to do anything. So the current system is made with the method "try this, try that" and it will be maybe working.
Generally, if something does not work as expected, I need to simulate it. In this case, I need in the best case a file from Locus Map and file how it should look like. So if is possible to supply me something like this, I'll gladly look, where is the difference.

Versions / Re: [APP] - version 3.40.+ ( 2. 10. 2019 )
« on: November 01, 2019, 09:28:50 »
heh, you have really sophisticated system, nice :)

thanks for the log, got it!

And "This app will not work in Android 11. Wtf." ... it will, just app will have to store data in private "android/data" directory => a) not shared between Free & Pro and mainly b) whole directory deleted when app un-installed  :(

Versions / Re: [APP] - version 3.40.+ ( 2. 10. 2019 )
« on: October 31, 2019, 09:50:44 »
I ask myself a similar question Libor :). Security, protection, "sandbox" for apps ... all this together ends in highly limited storage access ...

So you both have same use-case: backup of settings only to work with Beta versions. Beta testers: ~0.5% of all users ... hmm

Versions / Re: [APP] - version 3.40.+ ( 2. 10. 2019 )
« on: October 31, 2019, 08:51:41 »
Understand. This is true only partially. Part of backup (one in "various" directory inside backup) is not shared, but rest is also shared by both apps.

Btw, we will have (generally many apps) huge problem since Android 11, where apps will not be able to write even to internal memory anymore. At least not in the way Locus Map needs. So Free/Pro won't be able to simply share data anymore ... I still do not know how to solve it, but most probably "synchronization" over our server will be the key ...

Versions / Re: [APP] - version 3.40.+ ( 2. 10. 2019 )
« on: October 31, 2019, 08:29:26 »
Ah sorry, you are correct.
Maybe a question: does it make sense to do "settings only" backups? When I see it now, for me "Backup of settings" should be removed. Isn't it much better to have a backup of all important stuff and later decide what to restore (if you need)?

Versions / Re: [APP] - version 3.40.+ ( 2. 10. 2019 )
« on: October 31, 2019, 06:22:48 »
Are you sure? Just check the content of the generated zip backup. Presets should be there (directory data/presets).

Versions / Re: [APP] - version 3.40.+ ( 2. 10. 2019 )
« on: October 30, 2019, 20:24:04 »
Hi Christian,
partially understand. So just a few points
- The quality of the code is average. It always was. I never wrote tests and did all testing in the field and thanks to active users. Can't imagine different workflow for a complex app with a single developer.
- the way I respond: direct, open, friendly ... anything wrong? Point me on a problem to make my communication better, thanks.
- your wasted time: we communicate maybe 6 or even more years? I just hope, not all the time you spend on the forum and with Locus was not completely wasted ...
- problems & questions from bikemates: you may always simply forward them on our support, it is our problem, not yours.
- Platinum Eternity version is our chance to have more than three people in the team and also a chance for all to receive updates for more than a few next years.
- quality of the app based on subscription has to be definitely higher, so I expect less frequent updates and more internal testing
- If I do not miss anything, you did not reported crashes in RP or TE. You spend more time writing about it here and writing about "I won't do any logs" , then, in reality, take creating one log. But ok, the issue won't be solved until I receive from any other guy log, or information on how to simulate this problem.
For your information, I use the so-called "Crashlytics" system for automatic collection of app crashes. Currently, I see total of 9900 crashes during the last 30 days (557 different problems). I always solve the first 10 - 50 most often. So rare problems like yours are definitely hidden somewhere deep ... maybe 50% or more problems are specific for some devices. Most of them is currently unsolvable because they are in some system component and I spend days and days by searching how to hack it ...

Thanks all ... anyway, understand your points and no one force anyone to help fix bugs I made during my dark nights.

Versions / Re: [APP] - version 3.40.+ ( 2. 10. 2019 )
« on: October 30, 2019, 17:45:45 »
Presets: perfect.

Czech in TTS is more interesting. Write to me please what is language of your device, language set in Locus Map and TTS engine and language in Locus TTS settings. I'll try to set the same to simulate it ... thanks.

Versions / Re: [APP] - version 3.40.+ ( 2. 10. 2019 )
« on: October 29, 2019, 18:13:14 »
thanks, I'll try to play with it little more, because I'm still unable to simulate it.

"Back press": I've just installed fresh 3.37.2 version
- tap on the track on the map > open detail > click on the right arrow opens list of tracks in the same folder > eye to display another track > back press display list of folders! > back press display first track detail > back press to map .. so 3x back press

Current version:
- exactly the same steps! - so 3x back press

Whare is the difference? As I wrote before, tap instead of the eye on the track preview to get directly to map!

Track editor, Route planner crashes, as usually, needs an error log after the issue happens.

- open track detail, waypoints tab > delete button in context menu works.
- track on the map, tap on track waypoints > popup menu "delete" works

Christian, you seems little angry, but sorry, I see nothing I may help here (not "nothing I may improve", for example back should be reduced logically on two steps by excluding "folders" view, will check it). (EDIT: should be improved in next Beta).

the exactly same problem is already reported on our help desk here: .

Unfortunately, we are still unable to find our real reason and steps to reproduce this on own device.

Pages: 1 [2] 3 4 ... 741