Messages

Zdravím Henrieto,

zkus se prosím podívat do menu > Nastavení > Navigace > Pokročilé nastavení > Striktní navigace po trase.

To by mělo pomoci a opravdu vynutit navigaci po všech bodech bez přeskakování.

Ahoj,
záleží kde je a jakou máš verzi Androidu.

Nejsnazší metoda která funguje všude a bez ohledu na telefonu či kde Locus je, je připojení k počítači a ve Windows (v jiných systémech jsem nezkoušel) lze v pohodě procházet celým telefonem.

Jinak pokud je aplikace v privátní složce, tedy v podadresáři ".../Android/data", pak do Androidu 13 funguje v poho např. "Es File Explorer" či "X-Plore" aplikace. Od A13+ zatím asi jen "FV File Explorer".

Bohužel, Google přitvrzuje 

[@CabrioTourer]

Hi guys

progress during sync: oki oki, I'll look at it. There are a lot of calculations at the beginning and comparing users' local and server data.

@CabrioTourer
if you PM your email address used to sync your data, we may completely clear the content already existing on the server so your first sync only send data to the cloud.

Btw:
"sync" - merge local and server data
"download" - throw away local data and download data from server

@Andrew Heard
The problem with the editing of the reversed route is interesting. I was able to simulate something similar once, but can't repeat it.

I'll look at it later, because it looks like a tiny but "hard to find" problem.

@joeloc & @Jethro10
Adding point problem: this happens directly on the main screen by simple long-click > + button?

And guys, with Android 13, even a hack that filebrowsers used to access Android/data stopped to work (I've discovered this yesterday). One additional option exists for now that use Locus Map 4 to access private data of Locus Map Classic and that seems to be used also the (till today unknown) "FV File Explorer" ...

And I really expect this hack will be patched in Android 14. Long life to Locus Map AFA version 

[@Andrew Heard]

@Andrew Heard
hmm error 10102 is a generic problem with the internet connection so it probably happened when the app was on background > system decided that Locus Map should not use the internet now. The app should anyway handle this more gently. Weird is that the "refresh" button does not help. Will have to try it ...

@luce
thanks for the shared settings, it helped! The issue was found and will be fixed in the next version.

@Tapio
The problem with the image when visible for the first time should be fixed in the next version, thanks!

The issue with recording & tasker > hmm, yes, there was a minor change in the recording system because of some optimization around ignoring points with "invalid" accuracy. But it should not affect the recording life-cycle & handling of such events.

What you may try > enable "Log to file" in the Beta version (long click on the main menu). When this issue happens, remember the time when it happened and send me the log from Locus/logs directory. There should be (maybe) some info ... at least something to start with. Thanks!

[Beta version 4.11.1.3]

The new Beta version 4.11.1.3 is finally published.

@Andrew Heard, @freischneider, @CabrioTourer, I'll look at it after weekend, thanks.

[@freischneider]

@freischneider
It is a really interesting problem with rotation. Because the map should stay the same the moment you turn the screen off as when you turn screen on. I do not really know why it internally rotates to the north in your case. I'll be watching it but if there will be a such problem, I'll for sure notice it ... weird.

Just for sure > what Settings > GPS & sensors > Map rotation mode do you use during the navigation?

@Tapio
there should be close to no difference. The only difference I see is that small maps more often trigger "search for the map that may fill empty space" > so auto-loading. That takes some power. So in the end, a bigger map = better

Convert of trackpoints to shaping/via > hmm, when you tap on any segment, you see details of this segment. So working with trackpoint here a generally a little problematic. It is similar problem to working with trackpoints when clicking on the recorded track directly on the map screen.

So current solution? Far from ideal, agree. Placing to the bottom? Not a lot better I think. I have some ideas on improvements in the route planner, so later probably ...

@ta-ka
comment in the mentioned topic, thanks

@CabrioTourer
nice icons for waypoints  . And thanks, graphics glitch fixed

[@freischneider]

@freischneider
ah thanks for the reminder.

"Map rotation during navigation" > I'm playing with it and unfortunately no such problem was detected. Rotation is always made without any animation, so instantly. In your case, the map rotates based on the GPS movement so align with the navigation track itself?

@joeloc
white copyright > and what about the dark mode in the app? Then even a copyright button will be dark and not white.

problematic recorded point > in the next app version will be the detection of the HDOP & VDOP values that should block the recording of points with bad signal, so we will see if it helps. "Speed" is not an ideal solution. In your case, it will be 30m jump > oki, it is wrong, but second, it will be 30m/2sec, 30m/3sec etc and in some moment, the point will be saved.

... ah I see that @Andrew Heard already answered, thanks

[So what should be updated (todo list)]

Hi guys,

it has been almost 12 years since I created this forum and posted my first post here. Heh, a long time.

Unfortunately, for a few years, the forum was stuck on the older version without an option to update (because we still used a really old server). And now, we get info that the server is shutting down.

So what should be updated (todo list)

• missing "Last post button"
• make a "Recent post" slim
• enable Tapatalk system

EDIT: just to make it clear (based on comments of my colleagues): this was the only old server we used .

So > new server, a new version of this forum, new problems, and many plugins + theme that does not work!

Important is to keep in touch and update the app itself, anyway I'm creating this topic to

• inform about these changes
• discuss what features are missing here (on this forum) most and try to do something with it

Thanks for understanding and let me know if there will be any requirement or any problems I did not notice.

[@baegas]

@baegas
thanks for the report regards the NTRIP client. I think I've found a serious problem when the client reconnects after any connection problem. Should be improved in the next version. Hope it will help to audio-coach as well.

@balloni55
KMZ is not supported in the map manager so it is ignored. Anyway what you see is older problem with using maps from deeper directories. You may use an alternative solution and name your directory "LoMap_split". The ending "_split" cause that all maps will be handled separately. Otherwise, app tries to merge maps in your subdirectory into a single "multi-map".

@Andrew Heard
Info in the quick settings is really weird and I currently have no idea how to fix it, sorry. It works to me on two devices correctly ...

All seems to look correct in the NMEA messages, so I also have no idea here, why xDOP values are not visible here, hmm. I'm also checking the dashboard if this works correctly and seems so ... damn. Will be watching it ...

[@tapio]

@tapio
someone read the news?  Nice, thanks, indeed there was an incorrect link.

@freischneider
ah, it is still named as "Street name" > should be more something like "Extra info about next navigation point".

@Andrew Heard
Notifications in the quick settings were working but were placed below the dialog. Anyway now it seems to work correctly to me in all cases, weird. Do all buttons behave like this?

Accuracy before some sats are loaded may not be wrong. Android cache and re-use some older data, so it may provide a few minutes of old data with these parameters. The fact that is not "fresh" is another problem.

xDOP values are read from the GSA message. There is no guarantee it will be available on all devices. You may try to record an NMEA message and check if the recorded file contains any line with the GSA message (messages are stored in the Locus/data/nmea directory).

@baegas

and Locus Map 4 stops

... you see a system dialog that application crashed? If so, the log will be needed here right after this happens.

What problem is with the audio-coach?

[Locus Map 4.11.1.1]

Reported problems should be solved in the recent Locus Map 4.11.1.1 Beta version.

[@Andrew Heard]

@Andrew Heard
it is a problem. "hdop" value from the Locus Map in the GPX file is fake. App writes into GPX file received "horizontal accuracy". Android system does not report real hdop/vdop/pdop values over base API. What I may anyway do is read also NMEA messages and extract these values from there. Hmm, I'll look at it ...

Invisible info: an old problem with some longer info messages. Solved, but I had to shorten the info box duration.

Problem with "Optimize GPS values" > this is bad. I never read about any problem with this settings. So now I'll use this to test ...

@freischneider
Problem in merging of segments in the route planner: uff, this was hard , should be fixed now, thanks!

"Comment field" > should be visible during navigation in the top panel. It is difference to "Description field".

Hmm good to hear it. Because of the system in the background, it should have also almost zero battery consumption.
Shame, that it is not easily available ...

HDOP and VDOP may be problematic as well to be true. These values are not equal to "accuracy". It describes the situation of satellites in the sky and if they are able to provide an accurate location. So low HDOP value does not immediately mean accurate location.

Currently, the recording service ignores the first 10 locations after GPS is enabled. So first 10 seconds of fresh "fixed" locations are ignored. Good enough in most cases. Should be interesting to watch a visible horizontal accuracy. For this, already exists settings in the recording profile. Simply enable GPS in the skyplot screen and check visible accuracy.