Messages

Thanks for the report, but it is quite an unsolvable problem for me.

Except fact that no one in our team has a device with S-pen, I do not use anything special here that may cause a trouble. Sorry.

[@Andrew Heard]

Btw. new version just published on the Google Play.

@Andrew Heard
Do not think about the option to make via-point silent as a third type of point. These points are still via points with tiny options to not notify during navigation, that's all.

Shaping points are a core feature of route planners and I still consider it a very good choice for planning routes, so no changes are planned here.

@slarti76
ah I see it now, thanks. Will be improved in the next app version.

[@Viajero Perdido]

@Viajero Perdido
well, to be true, I prefer direct communication here on the forum, so really no problem. Sometimes it may be useful to post some really specific or private problems over help desk so it won't bother others, but it depends ...

Sync issue: I think I've found a reason for this, thanks.

@Andrew Heard
In short ...

• Via points: used to define shape during route planning, visible in the list of waypoints, used for recalculation, notified during navigation, exported/imported
• Via points - silent: same as via-points, but not notified by voice announcement during navigation
• Shaping points: used to define shape during route planning

@slarti76

because many apps get screwed up by the then unusual aspect ratio

Oki and this is also the case for Locus Map?

Hill shading: well I see quite a big difference in the shading of your screenshots. I'm comparing 224356 and 224409 images.

Hi, there is no direct support for pens and some gestures. But with one finger (so with the pen) you may zoom in with the following gesture:

- tap once down, then release finger up
- immediately tap down again (like a double-tap), but keep your finger (pen) on the screen
- slide up and down to zoom

[@slarti76]

@slarti76
ah, sorry for calling you "tapio". Too many names on my head .

Your screenshot: yes, it may be pointless. Then do not use it . If you need a little bigger, but not the full-screen > use split-screen on your device!

@tapio
The button in the bottom left is doable, it just does not fit into the UI for me. I'll think about it, but for now, this is at least a one-tap improvement.

Offline LoPoins > this screen will be written from scratch. Currently, the priority in development is on the online LoPoins system. A little later we will be working on the new database for offline LoPoints together with UI.

@Andrew Heard
14117 means that "App is not yet initialized". Intersting . Thanks, but let's hope, it won't happen again ...

@Viajero Perdido
ah damn. It is a bigger problem than it may look. Anyway fixed, thanks!

@CabrioTourer
- glitch on the roundabout is interesting, I'll try to simulate it.

- "glitches" on the big route can't be considered a problem. The so-called " Glitch detector" (funny name, thanks Willy), considers problematic parts of segments when they overlap up to 100m. Longer overlaps are currently considered as intent.

---

Btw. did anyone notice the option to create a "Silent Via-points"? There is a new option when creating new via-points during planning. Currently it is a checkbox with label "notify" .

[@tapio]

@tapio@slarti76
PiP display: it is possible that panel ratio affects resize options. Anyway, this panel was made mainly for navigation. For this case it is optimized and because of this, it is a little higher. I do not see a sense to increase its size close to the full-screen.

Automatic zoom & rotation works for me as well as no glitches as balloni55 wrote above. Sorry, there is not much I may do for now.

Text-to-speech: I did no changes here and also did not noticed any "reset", sorry.

@CabrioTourer
When you create a route in any other web planner, then why do you need to "recalculate" it in the app?

I do not understand what magic you all search here. This small improvement should really help to more easily modify recorded tracks without worry, the whole track will be re-computed. Do not search for something more robust behind this.

Btw. points are not placed randomly! App firstly heavily simplifies track shape, thanks to this detect some places where the shape of the track change a lot and place point there.

Ah, I see, Willy nicely described it here, thanks.

@joeloc
Live-tracking > internally live tracking is close to track recording service. App simply collects data in defined internal and sends them when possible. Live-tracking is running as a service so it keeps the device awake. Use it as is as currently there is no time for a major update.

@tapio
quick change to via/shaping etc ... hmm. I instantly agree  ... just do it...

[@Zajdlík Josef]

@Zajdlík Josef, @lor74cas
ah, I probably get it. Not a technical problem you should worry about, just a notification that should not be visible. Fixed, thanks.

@balloni55
Petr just tested it on his new Samsung device and no such problem with PiP as you have. Really interesting. I'll be probably looking on this function a little more later, and because it is not a critical issue, let it be for while, thanks.

@tapio
This change automatically generates shaping points on recorded tracks on places, which should help easily modify the recorded track in the Route planner without a worry, that by movement on a single point, the whole track will be totally changed (as it worked before). If you do not have needs to modify recorded tracks, this feature has no benefit for you ...

Tak perfekt.

A nastavení se určitě s "obnovou nastavení" přenáší ale dost věcí je závislých na tom co je v telefonu. Takže pokud už máš nšjakou novější verzi Text-to-speech nebo tam třeba chybí nějaký jazyk apod, obnova tyhle věci nedá a pak se začíná v nějakém "defaultním" nastavení.

Zdravíčko,
audio trenér mluvil Eliškou? To není možné 

"Eliška" je hlas dělaný pro TomTom navigace a obsahuje jen omezené množství povelů. Aplikace určitě pro audio trenéra vybírá "Převod textu na řeč", tedy Text-to-speech systém zabudovaný v Androidu.

Výběr hlasu/jazyka se pak provádí v nastavení Locusu > Jazky a jednotky > Převod textu na řeč. A nebo pak detailní nastavení jednotlivých zdrojů se dělá v systémovém nastavení telefonu. Bývá to někde trošku zanořené.

Hello, "Android/media/x" directories are automatically used for maps. So for example in the case of Locus Map 4, maps placed into "Android/media/menion.android.locus/maps" are automagically used ...

And this is the reason why I wrote

"Share" will be reserved for the more robust sharing system we are working on.

[Beta version 4.8.2.3]

*** Beta version 4.8.2.3 ***

Among some fixes etc, one specialty for @balloni55 . Expert settings > Premium for LoCoins. And then check the screen with "Premium purchase". There should be a new option. We are still not perfectly sure where to please this option, so for now, it is hidden behind "Expert settings".

@slarti76 & @joeloc, thanks for your posts. I'll look at it (and answer) in the next few days ...

[@razvaneduard]

@razvaneduard
I'm quickly testing it and it seems to work correctly even for planner routes. You may give a try and modify "speed_for_moving_cursor_when_gps_off" parameter in the Locus/config.cfg file to something like "speed_for_moving_cursor_when_gps_off=3.0" if this makes a difference.

@balloni55
identical dashboard & custom screen buttons > ah thanks. I'll have to get rid of this old "Custom screen" system soon 

@Viajero Perdido
I see the problem probably. When you plan a really short route where are none! navigation commands (no instruction to turn) and you have disabled generating of navigation commands by the shape (settings > navigation > advanced > Frequency of commands), app does not recognize route as navigation route so it starts a guidance mode instead. Hmm ...

This looks like quite confusing behavior. I'll change it to the next app version and when you select "navigation", it will always start this mode even without a valid navigation command.

@Christian
I know I know, sorry. It should be already fixed in the latest beta version and the new version is in preparation.

@luce
I agree with michaelbechtold. Maybe not so nice, but definitely a little more detailed. Anyway as you may see on your screenshots, there are some graphical glitches that I was not yet able to solve. Hope that current style is not a problem.

[Beta version 4.8.2.2]

*** Beta version 4.8.2.2 published ***
- PiP fine-tuned
- and 11 other changes

@Andrew Heard
They have problems only as tickets > so only a private.

Anyway, thanks you've reported it! We also report issues there, maybe once per month and they usually publish a new version of the help desk system once a month, so I'm sure, it will be fixed with the next update.

[PiP]

PiP > thanks all for the feedback. I did a few improvements over the weekend so in the next Beta, it will be a lot better!

@lor74cas
What exactly is the problem with the WMS map in this post? When I play with it, all seems to work correctly.

Recorded speed > this is an old problem with detection of the "not moving" behavior. You are correct that the app currently simply records a speed value received from the GNSS unit. What should be done is to, based on the device sensors (or by attached speed sensor), register movement and based on this modify speed values. The task to do.

@joeloc
Disappearing points: this sounds like a serious issue. There were no changes in the database system for a very long time. Hmm, sorry, no idea.

Restoring recording after crash: Do you mean the small "rec" button on the left above the menu & map content buttons? Interesting, I'm trying to simulate it and it is always correctly restored to the red button with small green <> white animation in the inner circle.

@luce
PiP is available only since Android 8+, sorry I forget to mention this.

WMS > which layers you have enabled? All I've tried looks ok, thanks.

@CabrioTourer
thanks for the description. You are right, current behavior is really weird. I'll look at it.

@slarti76
I did some benchmarks and spend some time on it.
Result: agree that difference is significant. Even that detailed shading is around 60% slower, I've moved limit from the zoom level 12 to 15! You will see in the next app version.