@Corjan-Meijerink Perfect!!! We'll test in upcoming release when solved. Regards!!!

@Jörgen said in "Taschenrechner" while biking? Translation needed !: If possible, always suggest the shortest option. Hi Jörgen, I'll have this in mind next time. @Jörgen said in "Taschenrechner" while biking? Translation needed !: We should get together and talk about the app, we only live a few kilometers apart. Hi, Jörgen, gerne. Ich schick Dir ne PN mit meiner Telefonnummer, dann können wir ein Treffen gerne absprechen. @Corjan-Meijerink said in "Taschenrechner" while biking? Translation needed !: The English spelling of "0h 8m" should be replaced with "00:08 Std." The separator at "43.60 km" in German is a comma "," and not a period "."' Those are not possible as the website does not support this Hi Corjan, I almost thought so. Perhaps it is possible just to replace the english "h" = hour with "Std." = Stunden? @Corjan-Meijerink said in "Taschenrechner" while biking? Translation needed !: All textual improvements will be applied next week! As fast as ever. Greetings Ronni

@Steve-Lynch Happy to hear that! Thanks for the other screenshots

@Corjan-Meijerink No worries; I know you will fix it eventually. It is just dragging for such a long time. Thank you for your attention.

@Corjan-Meijerink Than you.

@Corjan-Meijerink als ik bijvoorbeeld van de Hoge Steenweg in Loon op Zand naar de Edelhertlaan in Helmond een route genereer met extra bochten

@Jesse-Donkers In de routeplanner wordt hier rekening mee gehouden. De Navigatie doet daar (momenteel) niks mee

@Michael-Ferguson The route elevation won't be shown anymore on smaller mobile devices starting tomorrow

@Gerard-23 De grafiek wordt niet meer getoond mobiele apparaten vanaf morgen

@Corjan-Meijerink Thanks for the clarification.

@Dave-J-0 Thanks for the followup!

@Jure-Sirena-0 Thanks for sharing, we’ll see what we can do!

@BikeLover690 we will work on it! Thanks

@roland-herremans Dank voor de feedback!

That indeed sounds like a situation that’s difficult for the app. Especially if it’s unsure if you may drive there. Thanks for the compliment!

I was wondering if I saw the same battery flattening on my iPhone 13 on Sunday. I noticed that the phone, which was receiving a charge from the motorhome, had a nearly flat battery at the end of a 70 mile journey. I had guessed that I hadn’t plugged it in properly but maybe, just maybe, the app was consuming lots of power? I wonder if I was maybe also recording the track, too? If so, I guess that uses more power??? I’ll monitor it and report back. Hopefully it was just user error on my part.

The addition of a large vehicle (like a motorhome) where you can put in the vehicle’s details would be very good. At the moment I either plot out the routes myself or I use Garmin’s very good ‘large vehicle’ GPS device if I am too lazy to create a route myself. Having it all on MyRoute would be very good, not least as I have a motorbike towed behind.

@UltraStar No worries

@Con-Hennekens Correct! Gaan we oplossen Indien het niet mag worden overgeslagen, zou de app het ook niet moeten vragen. Routes met slechts 2 waypoints vindt ie namelijk niet zo leuk

@Johan-Ri Inderdaad is de vraag die @StefanHummelink stelt essentieel. Een route gemaakt in OSM wordt compleet anders gereden in de Navigation Next app. Advies is om de route altijd met de HERE kaart te maken. Indien je bepaalde “vermijd” opties gebruikt kan het ook nog mis gaan omdat de app daar geen rekening mee houdt, dat moeten we nog toevoegen Voor nu zou je de route om elke willekeurige manier kunnen maken, vervolgens uit breiden naar (veel) meer routepunten en dan even controleren in de HERE kaart (als ie daar nog niet op staat). Op die manier weet je vrij zeker dat de route zo genavigeerd wordt als gewenst.