@Peter-Schiefer

any Idea regard this problem, root caause?

@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 🙂

Yes @Herko-ter-Horst I am. But all good now, the latest version 4.0.8 popped up on Google play this morning. Cheers

There stil seems To be an issue in 4.0.7-239 on Android that makes the music channel volume return lower than it was before a signal (like speed camera or 'trajectcontrole') was given.
It does work ok with the navigation instructions.

@Corjan-Meijerink great work !!

@Con-Hennekens tried that but that wasn’t thé answer. Will keep on trying

@Rob-Verhoeff i got two on my KTM. One less than a day after i bought it, one in the rain somewhere in France in the mountains.

And the repair set could not repair it 😒 I spent all the cartridges and luckily reached a garage 5 minutes before it closed.

@Corjan-Meijerink : Danke die WP werden jetzt scheinbar besser und logischer eingesetzt.

Danke für das kleine Update.

Das mit dem springen zum Startpunkt der Route nach dem WP Einfügen sollte vielleicht wie oben geschrieben noch angepasst werden.

Besser wäre erst am neuen WP nach dem Einfügen zu bleiben, und dann das Starten anzubieten.

Dankeschön für die Weiterentwicklung 👋❗️

Zum Test 6 & 7 jeweils Tankstellen zum Test eingefügt.

IMG_3408.png

@Michael-Rhys, what you also must consider, is that the fuel suggestion is combined with the second instruction window. There are some limits implemented for when the second instruction has a higher prio to the fuel stations. But I can't seem to find the exact info.

@Corjan-Meijerink Super! 🙂 Thanks

@Siepermann-Ronald said in Endurance test MRA Navigation Next:

@Michel-van-Hagen-MRA-Founder
Heb met veel belangstelling je verslag gelezen. Met betrekking tot de melding op het Honda scherm 'wil je een headset pairen' even het volgende:
Na het opnieuw starten van de motor en het verschijnen van de headset pairing moet je de Return-knop zo'n 20 tot 30 seconden ingedrukt houden. Hierna zie je inderdaad dat, in mijn geval de CarlinKit 4.0 gaat opstarten.
De Apple Carplay werkt hierna weer als vanouds.

I read your report with great interest. With regard to the message on the Honda screen 'do you want to pair a headset', the following:
After restarting the engine and the headset pairing appears, press and hold the Return button for about 20 to 30 seconds. After this you will indeed see that, in my case, the CarlinKit 4.0 will start up.
The Apple Carplay then worked as usual again.

Honda NT1100DCT, iPhone 12Pro, CarlinKit 4.0

IMG_0717.jpg

Bij mij ging dat vanzelf. Dus iPhone verbonden met Ottocast. Headset was leeg. Pairen met headset genegeerd en na ongeveer 20 seconden verscheen de route op het scherm. Maar zal jouw optie ook eens proberen een volgende keer.