My solution, bought a bigger tablet

Niet dat ik het veel gebruik. Ik dacht dat ik best veel wist over MRA maar deze is voor nieuw. Thnkx

@TuonoPants See this topic. Perhaps you can create also a support ticket with your device specific info refering the ealier mentioned topic!

When the setting "Automatic recalculations" is off the ETA info disappears when I deviate from the track. When I reenter the track the ETA info reappears. So somewhere in the system it is known whether we are on the track or not. Of coarse I don't know where this is and wether MRA can get this info or not.

helemaal met je eens maar zolang het niet zo is moeten sommigen terugvallen of andere alternatieven.

It has nothing to do with tapping on the screen. It is just there. But is disappears to early. My question is. Is this intended?

Super bedankt!

@david-rudgley I do use viapoints when I’m riding with a predefined route. But when I’m just riding freely without a planned route and only recording a tracklog to see where I’ve been at the end of the day, I can’t really place a viapoint in advance. That’s why a custom distance‑based reminder would be useful: after a set number of kilometers, the app could notify me to refuel. I ride motorcycles from the 1930s up to modern bikes, and each one has a different fuel range, so a flexible threshold would help a lot.

Thank you all for your help, AMAZING. Looking forward to becoming a long term user of this great app.

i do not use AI... the fun is half to play arround with routes and then try to find solution for navigation. it can be use off a lot of shaping points or use OSM but then use a OSM navigation app. sometimes i just use a track and then also NN but with some tracks it is better to use other app. i never use google maps for planned routes. for planned routes i use NN, Comaps(track), osmand (osm) and komoot for walking or bike. i am now also looking at bmaps, android app working alone with tracks and osm maps. As long as Here maps are supports the roads i use NN. If road support is better in OSM then i plan in OSM and export track to what ever i like to use.

@Thiebaut, that is of course not really feasible when you consider many people are using the app offline. But I want to stress again that you do not need any tedious logins when you remove a device from the list, if you do not overuse an account.

@richtea999, no problem, if I keep my familiar units, I have no need for a calculator

At first, I was hoping that a red segment at 12 o’clock would indicate that I was within the free speed limit range. The others would then show when I was below the limit. If I exceeded the limit, each segment would then show approximately €50 in most countries and €100 in Switzerland. The north direction is already included in the camera view icon. RT

@Joakim-Granberg, there have been multiple threads where this has been cleared. The problem lies within the HERE platform, it has already been solved by HERE, but other bugs in the updatet platform are preventing the MRA dev team to update to the new SDK version.

Thanks! In that case it will remain as it is. Sorry

@Con-Hennekens It worked, but it sure is a PITA to do...

@ginogino ((If, instead, you start it from the app outside of Android Auto by activating the "Start from nearest waypoint" and "Use current location" options, navigation will correctly start from the nearest waypoint, which is in the direction of the route's end.)) I'm sorry, I disagree with my opinion about this part of your answer. Last week we were discussing this point in another post on this forum... and it was concluded after much discussion that in both iOS and Android, if you activate the boxes you mention, you will indeed go to the nearest point on your route (but the nearest point isn't always in the direction of the route's end). Sometimes the nearest point is very close to you (but behind you), and therefore you will go backward on your route and not towards its end... (I suggested this as an idea if it might be of interest for future updates of the navigation app)... but the only solution offered to me was that I had to manually navigate through the previous waypoints or zoom out and go directly to the next point towards the end of the route) Both solutions don't convince me. Normally, a browser should redirect only from your position to the next point (not to a previous one you've already passed) simply because it's closer.