Messages

Regarding comparison old/new recalculation
While checking my videos I noticed I start navigation in Beta in a wrong way.

In release I selected a specific track point while map view and start navigation from this specific point (near sharp point 2).
But it navigates to end point, not specific point.

In Beta by accident I start navigation in track menu. Nevertheless it navigates me to nearest point which was between 1-2 which is very nice.

Redult is even worse for release.
Even if it knows which point I want to start navigation it selects end point by themselves and ignores User.

(Just a comment because it might be forgotten by all the error reports.
Locus is the most powerful navigation software I ever saw. Not only for smartphones. It has unbelievable features. Don.'t be afraid and keep up the great work)

During my comparison between old/new recalculation logic I had the problem that Locus simple stopped and smartphone returned to launcher. It didn't show crash or anything else it just stopped.
This happened multiple times. Because time between locus or navigation start and stop issue were different each time I don't think it is because Firmware accu optimization or something similar. To be sure I disabled Doze mode completely but didn't fix the issue.
Don't know if this helps but I add three logs.

Happens on OnePlus 6, Rom (LR) based on AOSP.

I compared old/new recalculation logic today and the results are mixed.
I append the route I planned.
I'll start navigation at the yellow cross. I'm in direction of route between sharp point 1-2 and much closer to 1-2 than to route end point 8.
Then I follow route.Will left route at red circle and will be back on route at blue circle.

First of all the initial point why you changed recalculation logic didn't happen with release version (it was: Does not notice back on track. Means navigation must be stopped and start again to fix this)
Nevertheless the result is interesting.
Release version.
- start navigation at yellow cross: Wants to navigate you to end point, even route between 1-2 are closer
+ recalculation after left track (red circle) recalculation tries to bring you back on route (purple 1,later purple 2).
+/- because it recalculates back to track correctly the "does not notice back to track" issue didn.'t happen

Beta:
+ navigation starts correctly to route between 1-2
- after route left it allways tried to navigate back to red circle (green/blue sign 1). For many recalculations.
Very short before blue circle it switched to green/blue sign 2 (back to red circle too I guess)
+ After ignoring green sign 2 and turn right back to route it switched to purble 2. Means it noticed back on track and skipped all past points.

Conclusions :
1. With new logic start is much better
2. Recalculation of release logic succeed in this case, new fails.
3. New logic notice back on track correctly.

I.'m sad I didn' t had the initial problem to change recalculation logic described in support forum.

If needed I can provide videos.

At least for me there seems to be a big issue in new map core.
Many graphical errors during navigation.
Navigation is more or less not usable.
I'm using V4 ML maps.
I uploaded an example video here:
https://app.box.com/s/xfaxre1nil8n3ljv07az9xtab2nmtpf2

There is a second video in the link which shows two things with map core during planing.
It's pretty slow on my OnePlus 6.Means with high end Qualcomm by 2018 and not so high display resolution.
. For me it's acceptable but don't know how it looks like on medicore smartphone.
It shows the stuck, too. (sec 20)

Last point: Is there an option to disable 3D view of map?
It might be good while navigation but not for planing.

Don"t know if it's still on todo list or a bug. Theme switching when changing profile with V4 ML doesn't work. No theme available in profile editor.

Without checking new navigation V 2.9 is a big improvement.

Sorry don't understand how to add attachments. Can't find an option (using mobile)

Got 3.37.2.9 today.
Love V4 support and big improvement in map texts. Great.

New map core isn't really fast on my OnePlus 6.I'm not sure how this will be on none high end hardware.

Sometimes map loading stucks for a long time. I did zoom change and movements.
Just for an impression some pictures. Shot after +30 seconds of stuck.