All MRA problems solved.
-
Hello everyone!
I recently had a run-in with @Michel-van-Hagen-MRA-Founder. The reason was to present the problems that MRA was suffering on my Ullefone X10 Armor ruggedized cell phone.
These problems made browsing in MRA unbearable. To the point that I was considering installing TomTom on my motorcycle and abandoning MRA.
Per @Michel-van-Hagen-MRA-Founder's comment, last week I tried navigating MRA with my Samsung A71. The MRA problems did not recur, but the mobile battery did not reach 2.5 hours and the location lag was longer than on the Ullefone.
I started to consider buying a new phone to leave the Samsung A71 as a navigator. Of the options on the market I opted for the Pixel 7. I got into the Pixel 7 group on Telegram to see their ratings. And I found something that caught my attention. Testers of Android beta 14 had had problems with system processes when using already used Android services. So I tried doing a hard reset on the Ullefone. This time I only installed MRA. I tested it this morning and it works perfectly. It has not given a single failure. Only the BarButtons "n" button problem persists, but I'll bring that up in another thread. It has maintained the waypoint names, as well as their notes, and track names throughout. It has not crashed. It has recognized all the waypoints it passed through. And, most importantly, he has had no location lag.
@Corjan-Meijerink, I am not a programmer. I don't know what processes MRA uses. But it seems clear that when it uses shared resources with other applications, MRA fails, and badly. Maybe because it requires a very powerful mobile. But I don't think the Samsung A71 is underpowered.
I hope you will soon be able to find out what causes all this. Thank you very much.
-
@Maicro thanks for sharing!
-
@Corjan-Meijerink said in All MRA problems solved.:
@Maicro thanks for sharing!
Thanks to you for your attention and work.
-
@Maicro ofcourse! Only by communicating with our community we can lift the app to a higher level
