Issues since the 5.1.0-462 update / Crashes and lag

[Roland Busenhart]

Today I navigated 460 km from Copenhagen to Hamburg in just under 5 hours—a total of 2 crashes, the first after about 50 minutes and the second about halfway through the trip. The app closed on my phone, but after reopening it, I was able to continue navigating. Once again, I couldn't save the track log.

[Massimo Cardone]

Sometimes I feel like I'm not being taken seriously. Whether I write diplomatically or let my emotions run wild, there are always people who defend MRA to the bitter end.

What are the typical responses? "I have absolutely no problems. It's most likely your fault." Or "The problem is simply with CarPlay or Android Auto." Or or or…

Here are the facts:

• Before the 5.1.0-462 update, I had absolutely no problems.

• The problems started at the same time as my two friends, after we installed the 5.1.0-462 update. They both have iPhones, while I have an Android phone.

• If only I had the problem, it would have been a local issue with my phone or an Android problem. But no, both my friends also experienced these crashes.

• The problems also occur when I use my phone without Android Auto, mainly in the car, since I don't have a wireless connection to the car and I don't want to use a cable. In those situations, I only use my phone.

• My friend (an iPhone user) uses MRA on his Ducati Monster without CarPlay and also experiences crashes.

• Therefore, the problem cannot be fundamentally related to Android Auto or CarPlay.

On my motorcycle tours, I experience between two and four crashes per day, then there's the issue of the track log not being saved, and finally, the stuttering. The cursor is sometimes 100 to 200 meters behind my actual position. These are the three most serious and main problems.

I've reread every post individually, and everyone reports similar problems, especially since update 5.1.0-462.

I now also have update 5.2.0-474, as does my friend Roland Busenhart, who tested it extensively for three weeks. And the problems persist.

Peter Zehentreiter, Marcel Versluis, MarcM, M. Schrijver, Antonino Aiello, and others report similar glitches and problems.

And let's not forget the other threads where people could have shared their experiences in my thread, as they report identical or similar problems.

We (five friends, all with MRA) are going on the Routes des Grandes Alpes on July 8th. And I really don't have the desire, and especially not the time, to deal with navigation problems.

I know of several people who have opened a ticket and sent their log files to the support team. I hope the MRA support team can locate and solve the problem, because I want to navigate without a care in the world. It's simply annoying when the navigation doesn't work, especially when you need it most. I'm constantly setting off with a bad feeling. Will it work, won't it work, will it work, won't it work…

Dear Support Team, I believe in YOU!

Sincerely,

Massimo

[Marinus van Deudekom]

Massimo did you send in the log files so support can have a look at it.
What you experiance is certainly not meant to be. It is however strange that there is so much diversity. Some users have no problems and others, like you, have a lot.
Can you pinpoint the moments it goes wrong. That might help finding the solution

[Massimo Cardone]

Hi Marinus

Yes, I sent my log file to the support team, and my friend (Roland Busenhart), who has also posted here regularly, sent his log file as well.

He's the one who was traveling in Norway with his camper from June 6th to June 27th and used MRA almost every day. He wrote several posts about his experiences, and in 80% of cases, MRA crashed at least twice a day and didn't save the track log.

We were at Lake Como with another friend at the beginning of June, where we installed update 5.1.0-462 on Friday night, and that's when the problems started.

And as I said, we have different mobile phones. I have an Android, and they both have iPhones. Roland has an iPhone 15 Pro, and the other one has an iPhone 13 Pro.

After that, we also installed the latest update, but the problems persist.

And the following users are experiencing the same problems:

Peter Zehentreiter, Marcel Versluis, MarcM, M. Schrijver, Antonino Aiello, etc.

And user Joseph Malik 0 writes: “Hi, OP’s post is exactly what I experienced on my trip to Garda and Trento last week on my Android phone.”

When you read the facts and realize this isn’t a local problem, but a widespread one.

Best regards,

Massimo

[Aiello antonino]

I also sent my log file to support, saving it immediately after it happened, but I didn't get a response from anyone... but maybe that's the right thing to do... I don't know... I had contacted them previously and they had written to me to send them the log file as soon as it happened again... so I did...

[Aiello antonino]

If I remember correctly, @corjan-meijerink also had similar problems

[Peter Zehentreiter]

@Marinus-van-Deudekom said:

It is however strange that there is so much diversity. Some users have no problems and others, like you, have a lot.
Can you pinpoint the moments it goes wrong.

Hi Marinus,
I don’t think it’s strange.
I agree 100% with Massimo.

The errors don’t occur straight after start-up, nor do they always happen at the same time – sometimes they only appear after hours, sometimes not at all, and sometimes as early as an hour later.

I, too, have friends with all sorts of different set-ups – Android, iPhone and/or Apple CarPlay – who I travel with, and I experience these errors myself with them; however, these people aren’t registered here on the forum at all and don’t express their frustration or report these errors, because not everyone is willing to take the time to contribute here.

It’s more a case of me hearing people say… ‘Oh well, I’ll just try something else.’

Not everyone is as deeply involved in the subject as many users here on the forum; they just want a reliable navigationsystem.

MRA was the best system on the market before the 5.0.1 update, and in my view, it remains the best even after the 5.0.2 update.

In my view, there is also a difference between navigating offline and online.

There are a wide variety of options and settings in MRA – Route, Track, online, offline, etc. – which is why the error does not occur for all users.

However, it makes a huge difference whether I’m driving round on my own or just with one other person and have to stop quickly to restart the system, or whether I’m leading a group and then have to explain problems with the navigation system to the whole group!

I’m absolutely delighted that Corjan was able to identify identical errors whilst on holiday – it’s proof, so to speak, that the many posts and reports of issues from users here are indeed real.

But I’m sure Corjan will find the bug and will provide us an update soon, to make MRA great again

[Marinus van Deudekom]

Its not that MRA dev team doesn't take all those complaints serious. I know for a fact that they are trying with all their power and skills to isolatie the problem and fix it.

[Peter Zehentreiter]

@Marinus-van-Deudekom said:

Its not that MRA dev team doesn't take all those complaints serious

Nobody’s claiming that either!

However, there are users on the forum who, for the reasons mentioned (track, online, offline, use, etc.), haven’t had any problems so far and therefore doubt that other users are experiencing issues.

[Kerbel]

@marinus-van-deudekom Marinus, I fully agree to what @peter-zehentreiter wrote.

• timing of crashing is very erratic: after 30min or a few hours
• previous version 5.0.1 worked excellently without any probs

Okay, one point I cannot confirm as MRA was switching from on- to offline automatically (but very often in the Vercors). So whether offline would help I don‘t know.
And tracking, as mentionend in another post, did not make any difference.
I‘m also confident that the MRA team takes these issues seriously and will provide a solution shortly.
Currently I cannot check my navi-iphone but will do over the weekend and provide logfiles if available.
BR & thanks for all your support
Stefan

[Peter Zehentreiter]

@Kerbel said:

previous version 5.0.1 worked excellently without any probs

I’m afraid I have to disagree with you there.

I did experience a single crash in version 5.0.1 as well… but after that I didn’t use it as often and then updated to 5.0.2.

[Kerbel]

One thing I forgot to mention.
After the crash I could rstart the app from the home screen, MRA asks me to proceed with navigation or not. After confirmation another push on Navigate-Button was necessary and the the navigation proceeded from the current position.
But navigation was then always set to north not driving direction. Had to toggle with the compass icon.

[Peter Zehentreiter]

@Kerbel Please do try riding completely offline.

That would help to find out whether there’s a link to the mobile connection.

I’ve got two devices attached to my motorbike:
1 online, 1 offline

I’ve never had any problems with the offline device

[Peter Zehentreiter]

My DMD-NOR7E is being delivered tomorrow

Then I’ll test straight away to see if the crashes might be down to the hardware.

[Roland Busenhart]

Today: 340 km in just under 6 hours from Hamburg to Eschwege, near Kassel—many sections of the route required frequent navigation instructions (very less highway, mostly country roads). Everything went smoothly; the track log could be saved.

[Marinus van Deudekom]

@Peter-Zehentreiter good luck with your new device.

[Peter Zehentreiter]

@Marinus-van-Deudekom Thank you

[Aiello antonino]

@Peter-Zehentreiter If it were the hardware's fault, we should all change devices...‍️

[Peter Zehentreiter]

@Aiello-antonino ️

[Andries]

@peter-zehentreiter just back from a 5 day trip in france. Have to mention i did 2 week ago update to 5.2.0-474 and first day everthing working nice for a 10h trip.