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 - CabrioTourer

Pages: 1 [2]
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 03, 2019, 22:25:27 »
Just for completeness, they do not count as points in context of the point priority recalculation
This is what I thought. I just asked to be sure because 100 trackpoints isn't much for activities like car and even not much for bike in rural area.

Thanks for "shaping point" correction.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 03, 2019, 20:05:01 »
You talk about trackpoints, not sharp/via points, right.
Then it's a pretty short way for a lot of activities. That's for sure a problem.

Solution might be not to choose 100 in a row but every x trackpoint where x depends on the activity (or actual speed?)

If this does not work for activities which needs defined ways (street etc) then selecting trackpoint located on crosses etc might be the solution.

Just an idea.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 03, 2019, 18:00:45 »
To focus on new map core and finalize navigation later is fine.
Just that you are aware of some problems which might not be directly related to navigation logic I want to show you some things upfront.

Simulation in V10 is much slower than V9.
Funny thing: Airplane is slower than car in V10. Airplane means it counts meter by meter. That's slow ;)
I checked recalculation in Simulation in V9 and V10. In V10 it's detect "back on track" but pretty late. V9 it doesnt detect recalculations before back on track isn't improved.

Simulation might not show what happens on the street.
I tried the tour I did on Tuesday with Simulation multiple times. The results are sometimes different. My simulation started more or less same as Tuesday but later it changed and I see something different.
I uploaded the settings, planned route, simulation route and video which shows the issue here. All from V9 because simulation in V10 are too slow.

Then a question.
Which parameter influences when second, third etc. recalculation starts ?
The first recalculation is influenced by settings but all other seems to be random.
Sometimes after 300m, sometimes 600m etc.
Can't find any settings to change the time/distance. Tried all settings (I think) in navigation and guidance.
I'm asking because the place where recalculation happens influences the result of recalculation.
Without able to influence recalculation time Simulation might show other things than on street.

Again : it' s fine to focus on new map core first. Just that you are aware of some issues any maybe my sample might be good for testing.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 01, 2019, 16:11:39 »

Thanks also for crash logs. Unfortunately, I'm unable to perfectly find the reason of this issue but seems to be somehow connected to some active dashboard. Is this possible? If so, may you share this dashboard with me as well? Dashboard files are in Locus/data/dashboard directory. Thank you!

Method for navigation simulation

With the Beta version, there is a nice method of how to test the navigation system.

dashboard was active and same as in release. Its appended.

Nrw simulation :
Wooowwww that's great.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 01, 2019, 16:07:08 »
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)

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 01, 2019, 14:45:34 »
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.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 01, 2019, 14:30:44 »
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

+ 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.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: April 30, 2019, 11:45:48 »
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:

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.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: April 28, 2019, 07:48:47 »
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.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: April 27, 2019, 23:24:26 »
Sorry don't understand how to add attachments. Can't find an option (using mobile)

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: April 27, 2019, 23:22:08 »
Got 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.

Pages: 1 [2]