Next closes immediatly when starting a planned route
-
Just adding my 2 cents here...
I've experienced this problem as well. Once it manifests, it seems to continue to fail (closes immediately when starting navigation). My current work-around is to open a different route and start it. This seems to work consistently. I then go back and select the original route and open/start it. For whatever reason, this seems to work.
Edit...
Just to clarify what I mean by starting a route...
If I get past that point - then all is good. But at times it is an "if".
Edit^2...
Also noted it closing unexpectedly with choosing to edit (pencil icon) from this screen.
@Tim-Thompson, yes, that makes us two of a kind
Bevause it seems to be a very rare problem.I already told @Corjan-Meijerink, this in a support chat, in my experience once my first route-load works then, without quitting the app, I can load all thinkabel routes. But when the first load fails, I can't load any route until perhaps by force-closing the app.
-
This will be investigated coming week!
-
This will be investigated coming week!
@Corjan-Meijerink, I have full confidence
I didn't mean to disturb your weekend!I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@Corjan-Meijerink, I have full confidence
I didn't mean to disturb your weekend!@Con-Hennekens You havenโt at all
No worries! -
For what it ist worth, I'm seeing the same behaviour in a Huawei P20 Pro, Android 10
After selecting and starting the navigation, the screen goes Black and the Desktop appears
I tried several routes, all with the same result.
Starting navigation with the same routes in a Lenovo P11 Pro (Android 12) works fineRegards,
Hans
-
For what it ist worth, I'm seeing the same behaviour in a Huawei P20 Pro, Android 10
After selecting and starting the navigation, the screen goes Black and the Desktop appears
I tried several routes, all with the same result.
Starting navigation with the same routes in a Lenovo P11 Pro (Android 12) works fineRegards,
Hans
@Hans-Kremers Thanks! Tomorrow - Thursday are scheduled for app development so weโll start the investigation shortly!
-
@Hans-Kremers Thanks! Tomorrow - Thursday are scheduled for app development so weโll start the investigation shortly!
@Corjan-Meijerink
Je rencontre exactement le mรชme problรจme avec mon Samsung S20FE.
Si je dรฉmarre Next, je charge un itinรฉraire de la bibliothรจque, je lance la navigation et l'application se ferme. Si je redรฉmarre une seconde fois, รงร fonctionne et je peux ouvrir tous les autres itinรฉraires sans soucis. -
I tried clearing that app cache and then retried starting the route. That seemed to work. Don't know if it was a coincidence. But for what it's worth.
-
undefined Corjan Meijerink referenced this topic on
-
I've upgraded to the latest beta version 3.2.5 - 146. I uninstalled it and reinstalled. Still having the stability issues. In fact, they may have gotten worse. It's now crashing occasionally when going to the menu (upper left) and selecting "Routes". Tried clearing the app cache again. That doesn't seem to be helping (must have been a coincidence before).
In case it helps...
- Pixel 5a
- Android Version 13, Build number TP1A.221105.002
- MRA Beta Version 3.2.5 - 146
-
I've upgraded to the latest beta version 3.2.5 - 146. I uninstalled it and reinstalled. Still having the stability issues. In fact, they may have gotten worse. It's now crashing occasionally when going to the menu (upper left) and selecting "Routes". Tried clearing the app cache again. That doesn't seem to be helping (must have been a coincidence before).
In case it helps...
- Pixel 5a
- Android Version 13, Build number TP1A.221105.002
- MRA Beta Version 3.2.5 - 146
@Tim-Thompson Remarkable how this very annoying problem exists for a limited amount of users
We will continue researching this coming week! The most annoying part is that we never experienced this issue on any of our Android test devices. We will keep you posted about any progress! -
@Tim-Thompson Remarkable how this very annoying problem exists for a limited amount of users
We will continue researching this coming week! The most annoying part is that we never experienced this issue on any of our Android test devices. We will keep you posted about any progress!Another thing I noted... If I really get stuck, I try clearing the app storage. Kind of annoying... But one must do what one must do. So far, this step has worked to get past the issue. However, it may as well be a coincidence too.
Anyway... For what it's worth.
-
Another thing I noted... If I really get stuck, I try clearing the app storage. Kind of annoying... But one must do what one must do. So far, this step has worked to get past the issue. However, it may as well be a coincidence too.
Anyway... For what it's worth.
@Tim-Thompson Indeed, for what it is worth
The issue needs to be resolved by us. It's as simple as that! -
@Tim-Thompson Indeed, for what it is worth
The issue needs to be resolved by us. It's as simple as that!Just a thought. Is it possible to implement logging to help troubleshooting/capture the issue?
-
@Tim-Thompson Indeed, for what it is worth
The issue needs to be resolved by us. It's as simple as that!@Corjan-Meijerink FYI, I too have stability issues. This version gives me more problems than 3.2.4. Continuous closures.
My smartphone:
Pixel 6 pro.
Android 13Ulefone armor 12
Android 11I have problems in both.
-
Unfortunately the logs do not really indicate where the issue is yet. We hope to get more information in a next version!
-
Hi, I also have this issue on the tablets S7, S2 and the smartphone A51.
I have this fault when I push the start button immediately after loading the route. When I wait some time, several seconds the route is loaded and another start can be pushed. -
Unfortunately the logs do not really indicate where the issue is yet. We hope to get more information in a next version!
@Corjan-Meijerink
I have downloaded the new version on Android yesterday and I am having same problems, the unit crashes as soon as I try to start the route. I kept getting a message saying the app had a bug. So deleted the app and re-loaded which seems to have solved the problem. Will re-post if problem comes back. -
undefined Tim Thompson referenced this topic on
-
I just saw there is a 3.2.5 version now. The problem persists however. In fact it has kept me from navigating and testing at all all this time, and it does that on all my devices. I simply cannot start a route, with exception of a few times. More details are already known by Corjan. I just wanted to say that the new version did nothing in this regard.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
I just saw there is a 3.2.5 version now. The problem persists however. In fact it has kept me from navigating and testing at all all this time, and it does that on all my devices. I simply cannot start a route, with exception of a few times. More details are already known by Corjan. I just wanted to say that the new version did nothing in this regard.
@Con-Hennekens Sad to hear that! This week we will research more
-
undefined Corjan Meijerink referenced this topic on
