Issues since the 5.1.0-462 update / Crashes and lag

[Peter Zehentreiter]

Today we drove 335 km
After about 130 km, the MRA App stopped working and the start screen appeared. Restart the app and tap ‘Navigation’ to resume navigation.

My colleague, who uses iOS, experienced a white screen several times and the app stopped responding.

It was only after restarting the app three times that navigation could be resumed.

[M. Schrijver]

Pas few days similar with 5.2.
This is the 5.1 topic but I assume you ride with 5.2

[Peter Zehentreiter]

@M.-Schrijver Yes, of course, I’ve downloaded the latest update, 5.2.0-474

[Roland Busenhart]

Yesterday 315 km in 5 h without any issue completed

[Roland Busenhart]

Yesterday I covered 325 km in 3.5 hours; experienced several crashes during the ride; couldn't save the track log

[Aiello antonino]

It almost seems like after a certain number of hours the problem starts to appear…

[Massimo Cardone]

Not always... We also had this problem a few times after setting off, after about half an hour or so.
But most problems do tend to occur in the afternoon, after about six to eight hours of driving.

[Peter Zehentreiter]

I think that’s difficult to pinpoint.
I’ve experienced crashes after about 2 hours, as well as after about 5 hours or more.

[Bart 9a 0]

This post is deleted!

[Peter Zehentreiter]

@Bart-9a-0 This thread was started in English; please be so kind as to continue using that language

[Bart 9a 0]

@Peter-Zehentreiter , Sorry

[Jozef Malik 0]

Hi, OP's post is exactly what I have experienced on my trip to Garda and Trento last week on my Android phone. First, I thought the Android Auto was the culprit of the lag, but no, even using app just on the phone, each time there was a lag, I had to restart the app for it to work only for a few minutes. The real issue is that you're in hairpins and constantly need to think which turn you are taking. This resulted in countless turnarounds, recalculations, etc, not so great if you are leading the group. Another massive issue is that very tight hairpins on top of each other look to the navigation as if you are still in the same spot, a couple of hairpins below, then it starts recalculating, switching from online to offline mode, and everything is delayed. This is almost unusable in real time.
What can be done to fix this? Because as OP pointed out, in the city or tight mountain roads, this isn't working, and the motorcycling trip is exactly that, not straight roads. I don't need a navigation for that or MRA to be more precise.
thanks
joe

[M. Schrijver]

Hairpins are indeed difficult voor navigations. I've got lot experience with TomTom Go (Expert). At first TomTom had also this issue. But they managed to solve this. I don't how they solved it. But it looks like they do a similar thing as in tunnels. Assuming you stay on track whit the same pace.

[Thomas Neumeyer]

Same problem I was facing. After 2-3 hours app stopped working. New version not used yet for longer time.

[Myles Lubbock]

I wonder if the 'Tracklog' feature is filling the processing capabilities and cachiing the data?
Would it be worth a long trip without recording a tracklog perhaps to see if it frees up some processing bandwidth?

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