@Corjan-Meijerink 336 update 🤘 What’s new/changed?

@richtea999 Fixed in the release (I've heard) 😉

@Stanisław Oh definitely! We will solve this.
Logs can be obtained by long pressing the version number shown at the bottom of your profile / account page (where all the settings are).

@Corjan-Meijerink Made a round tour in the Eifel yesterday of approx 350km using MRA with AppleCarplay in my Z4. No issues (so the stability improved) and changes needed due to roadblocks/maintenance could be made with succes. Referring to that, will it be possible in the near future to see the next way-point on AppleCarplay? (like we had before) This makes is possible to skip waypoints, to avoid a roadblock for example, on the screen without using your iPhone. Thanks.

@Jan-Weerheim Geweldig! 🙂 Heel fijn om te lezen.
We hebben veel tijd gestoken in het intuïtief maken. Mooi als dat lukt

@Hubert-Thoring nice to hear that! 🙂

@Corjan-Meijerink : There would still be something to adjust before the published... at least from my point of view something that could be even better so that the user learns to love it before he does it badly.

Test der neuen v4.2.0 (320)

Small things, but they should also go clean without compromise.

@Tom-Johann And yet we have an even better version, 4.1.3 (311)!

Using the new beta on my motorcycle with CarPlay, I have observed that there is a difference from the previous one related to the audio of the navigation instructions. Before, I used the navigation channel for the instructions.
Since the last beta for the same instructions, use the channel identified as "Vol. Audio."
This causes problems since the radio is cut when it gives an instruction and you have to reactivate it, or it is mixed with the audio of the music causing cuts in the instructions.
Is it possible to return to the previous operation, and use the navigation channel for the instructions?
Thanks!!!

The release version 305 will have some tweaks to the auto skip algorithm 🙂

@RetiredWingMan that’s HERE unfortunately. I’ve informed them and keep pushing for a lightning fast solution 🙂

304 is coming too (nothing related to this issue) https://forum.myrouteapp.com/topic/6691/new-beta-v4-1-2-304

Just rode my motorcycle for two days. Still learned from my mistakes in MRA.

my laziness in not adding extra points led to different choices in MRA on my smartphone than the track on my Garmin (always displayed). the sound on my smartphone is not loud enough when I'm driving and the “subtext” of my waypoint is spoken. That's because my earplugs seal well ⁠⁠MRA corrects very well if you drive incorrectly. It then routes to the route Still, I often don't have a map on my iPhone when I navigate “online”. So I have to turn on “offline” and then have no traffic information. spoken navigation information was sometimes absent

Over all, I'm very happy with MRA and I'm looking forward to further development!.

@Hans-Hüppi said in New beta v4.1.1 (294):

I am using MRA for several years now and was not aware of this typical issue.

No I have never seen this issue either, but that is only part of the advise. Placing waypoints on crossings is recipe for disaster. Since GPS signal is only accurate for a few mtrs, it can be enough for the app to direct you into a street, just for you to turn around. That has always been a problem, also in the previous app. In today's app a waypoint's priority of announcement is higher that a navigation announcement. Effectively killing your turn by turn instructions.

@Hans-Hüppi said in New beta v4.1.1 (294):

the automatic route creator as of today even violate against this guideline.

Yes, when adding waypoints through the toolbox, or converting a track to a route, the planner has the tendency to place WPs at the direct place where the route/track changes direction. Also, in ALL manuals and presumably ALL forum posts about it, it is advised to review them, and replace them away from crossings. But you are right. In my experience it is quicker to draw a route over a track yourself, or add waypoints manually by clicking ON the route line when zoomed in. Therefore I never use those functions at all.

@Corjan-Meijerink yesterday another test with app. Same simple A B route. Started from home and diviated. It took the app about 25 minutes to finaly gave up and recalculated the route correctly. Till that moment it tried to send me back to the starting point, home. During the rest of the route the only flaw was the gass station not beeing detected correctly. I’ve passed several stations not indicated and the onces indicated not showing up.
On the way back I received a phonecall. After answering that the app never showed up again. Since I was in a hurry didn’t have time to restart the app.

@Corjan-Meijerink Ik zie nu dat ik nog een oude versie (276) had. Heb nu een update gedaan naar versie 284. Ik dacht dat dit automatisch ging. Hopelijk gaat het nu beter.

@Peter-Schiefer yes, that is something on the list! 🙂
Given the focus of this update, not for now.

Gisteren een rit gedaan met Android Auto.
Een paar dingen vielen mij op.
Op het Android Auto scherm ging alles goed. Maar op mijn telefoon scherm had ik vaak dat er geen kaart zichtbaar was.
Zodra ik de verbinding met Android Auto verbrak was er wel weer een kaart.

Het stroomverbruik was erg hoog.
Ik heb vorige week ook een route gereden van ongeveer dezelfde lengte. Toen was het stroomverbruik niet zo hoog. Na 3 uur rijden accu was ongeveer 5% kwijt.
Er was 1 groot verschil tussen vorige week en gisteren. Vorige week geen herberekeningen. Gisteren zijn er veel herberekeningen gedaan tijdens het rijden. De meeste in een klein gebied. Juist in deze periode zakte de acculading snel weg. Na 5 uur rijden was ik 60% kwijt.
De telefoon wordt via de Android Auto kabel van stroom voorzien.

With the latest beta update (version 4.1.0. (272) I encounter several problems:

in Apple CarPlay the program does not update the card in Apple Carplay the program does not update the navigation instructions in Apple CarPlay the map is not alway shown after using Apple CarPlay, the MRA app crashes

Hopefully this is fixed in the next beta update.
Keep up the good work!

@Edwin_M Thanks, fixed in the upcoming updated beta 🙂