This object is in archive! 

Recalculation cause exception

Stephan shared this problem 3 years ago
Solved

I tried, whether the new beta solved the track navigation problem. I am not able to say that, because the recalculation cause java.lang.runtimeexception.


4a31a0c543f2981a76cb5c2feb587962


Scine 3.37 or 3.38 I am watching, that the recalculation last a very long time. Sometime two, three minutes.

Replies (2)

photo
1

Where can I find and download the BETA?

photo
1

ah, found.

photo
1

Hello Stephan,

never saw such error message during recalculation. May you please create a log by this method? Thank you!

Btw. you are using offline BRouter routing engine?

photo
1

There was no bug report created. I have lost this week so much time because of your coding, so I will not go on giving you support to making a repair of your mistakes.

photo
1

Oki, no problem.

Anyway thanks for the bug report, I'll try to keep watching it if the same issue happens to me as well.

Till then, I'm closing this issue because I do not have enough information to solve it.

photo
1

Look at this message in the forum, this problem exist, https://forum.locusmap.eu/index.php?topic=6622.msg56061#msg56061

photo
1

Good day Stephan,

thanks for additional information. I still do not know why, but even if I follow exactly the same steps as on the video, I do not have the same issue.

Anyway, I've spent some time on it by comparing changes made during the last weeks and found one possible change that may have a side effect here as well. Because I'm unable to simulate it, I'm also unable to verify if the change I made now helps. I hope it will. New version 3.38.7 is just uploading on Google Play now.

Menion

photo
1

I can not cause this exceptions errors in the new version. But it seems automatic recalculations starts not every time it should start.

In this post https://forum.locusmap.eu/index.php?topic=6636.msg56161;boardseen#new in the forum, somebody complain that problem using the new version in reallife.

So I will cycle the next four weeks in the UK. i started to use Locus instead of Osmand, because I get voice hints for the roundabouts using Brouter. This makes cycling in the UK much safer. But if the navigation is not reliable it is better to do the cycle trip with Osmand.

Putting this in a short way, you should take more care in the quality of coding, because it is also a issue of safety of your customers.

You wanted a bug log. I was not able to create a bug log. Osmand has a function included in the app, to create such logs.

Do you see the difference? The people of osmand also earn money with their app. But the bug reports are more easier than for Locus.

I am not happy with the bug reporting of Osmand, but at Locus is one of the standard answers, we can not simulate the problem.

You will start a subscription model. Think about how many people will quit their subscription, if you destroy the navigation like you did with 3.38.5.

We are no testers, we are customers.

photo
1

Stephan, please, use Osmand, really. Android world is amazing. There are so many applications out there, that I see no reason to use the one, I do not believe in. Like in your case.

We do our best and yes, mainly I personally do coding mistakes. I never told anyone that I'm a good developer. I personally consider myself as quite an average developer, but I'm at least trying to fix problems, if possible, as soon as possible. But I do not have time and taste to read repeating stupid complaints that we do not test, we just sit home, we miss function to create bug reports (yes it is not in Locus Map because, since Android 5, application itself cannot create a full bug report when the device is not rooted and the method we use is the only possible to obtain full log) and so on.

If we start the subscription and no one will be interested, we will search for reasons. Thanks for understanding.

Problem solved.

Replies have been locked on this page!