First experience with MRA as a navigation tool

[Dennis Hoogendonk]

Since a week or 2 I have MRA available as a navigation tool (paid version). This should support my TomTom Rider unit as TT interferes with our intercom system.

My experience sofar. I carry my cell phone in my jacket. I use MRA as constructor for routes. I also use tracks from external parties.

1. Spoken instructions cannot be heard. Volume is way too low.
2. Instructions do not start at beginning of route. Most of the times they start after 1 km driving.
3. If not on the route MRA keeps guiding to the beginning. You cannot start at a random route point, or, as with TT, to the nearest point.
4. MRA consumes 20% per hour of my battery. Yet my Samsung A54 cellphone is brand new.

A long way to go for development team.

[Rob Verhoeff]

@Dennis-Hoogendonk

1. Spoken instructions cannot be heard. Volume is way too low.

Do you have all the settings in the audio menu configured correctly? You can adjust the volume of the voice instructions there in three different levels, and if you've done that, you can also adjust the phone's volume in the same menu to make it sound good to you.

2. Instructions do not start at beginning of route. Most of the times they start after 1 km driving.

That's strange! The first instruction appears for me as soon as I start driving. Is the first route point near where you're starting the route?

3. If not on the route MRA keeps guiding to the beginning. You cannot start at a random route point, or, as with TT, to the nearest point.

Yes, you can! On the map and in navigation-mode, longpress the waypoint where you want to start the route.

4. MRA consumes 20% per hour of my battery. Yet my Samsung A54 cellphone is brand new.

This is a known issue. The development team is in constant communication with Here's development team to work on improvements. This is something that MRA cannot address independently.

[Dennis Hoogendonk]

@Rob-Verhoeff said in First experience with MRA as a navigation tool:

@Dennis-Hoogendonk

1. Spoken instructions cannot be heard. Volume is way too low.

Do you have all the settings in the audio menu configured correctly? You can adjust the volume of the voice instructions there in three different levels, and if you've done that, you can also adjust the phone's volume in the same menu to make it sound good to you.

Current audio setting is #3, so I assume it is the most loudest setting. Also, my cell phone is set loudest possible.

2. Instructions do not start at beginning of route. Most of the times they start after 1 km driving.

That's strange! The first instruction appears for me as soon as I start driving. Is the first route point near where you're starting the route?

This is in fact a double problem. First I can barely hear instructions and secondly I just start 'Navigate' , put my cell phone in my pocket and start riding. I don't actually see what's happening.

3. If not on the route MRA keeps guiding to the beginning. You cannot start at a random route point, or, as with TT, to the nearest point.

Yes, you can! On the map and in navigation-mode, longpress the waypoint where you want to start the route.

I tested your advice. But as far as I can see when I press a wapypint, MRA starts a route directly to that waypoint. I do not really see a method to start a route at that certain waypoint and continues it onwards.

4. MRA consumes 20% per hour of my battery. Yet my Samsung A54 cellphone is brand new.

This is a known issue. The development team is in constant communication with Here's development team to work on improvements. This is something that MRA cannot address independently.

[Lynchy67]

@Dennis-Hoogendonk said in First experience with MRA as a navigation tool:

I tested your advice. But as far as I can see when I press a wapypint, MRA starts a route directly to that waypoint. I do not really see a method to start a route at that certain waypoint and continues it onwards.

Load the route and ignore the start of the of the route completely, just drive directly to the waypoint you want to join at.
When you get close to the Waypoint you want to join at, then long press that waypoint.
It will then continue on from your chosen Waypoint.

[Con Hennekens]

@Dennis-Hoogendonk said in First experience with MRA as a navigation tool:

Current audio setting is #3, so I assume it is the most loudest setting. Also, my cell phone is set loudest possible.

Up the volume while it is talking

But as far as I can see when I press a wapypint, MRA starts a route directly to that waypoint. I do not really see a method to start a route at that certain waypoint and continues it onwards.

You first start the route until it navigates. From there you long press the waypoint where you want to join the route. It definitely goes onward from there.

Instructions do not start at beginning of route. Most of the times they start after 1 km driving.

Instructions are only spoken when relevant. When starting a route, that is usually at the first turn.

If not on the route MRA keeps guiding to the beginning.

This happens when you do not "hit" the first waypoint. It is a viapoint (hand symbol) and can therefore only be skipped manually. If you plan your own routes, make sure you place the first WP a bit ahead in the direction you want to start. Then you will not miss that point.

Oh, and everyone can use the app how he/she wants, but personally I consider driving around on audio only as very dangerous. There is a visual map in the app for a reason.

[Dennis Hoogendonk]

@Con-Hennekens said in First experience with MRA as a navigation tool:

@Dennis-Hoogendonk said in First experience with MRA as a navigation tool:

Current audio setting is #3, so I assume it is the most loudest setting. Also, my cell phone is set loudest possible.

Up the volume while it is talking

This is practically impossible. I wear my cellphone in my jacket.

But as far as I can see when I press a wapypint, MRA starts a route directly to that waypoint. I do not really see a method to start a route at that certain waypoint and continues it onwards.

You first start the route until it navigates. From there you long press the waypoint where you want to join the route. It definitely goes onward from there.

This is practically impossible. I wear my cellphone in my jacket.

Instructions do not start at beginning of route. Most of the times they start after 1 km driving.

Instructions are only spoken when relevant. When starting a route, that is usually at the first turn.

Might be. But usually I don't hear any instruction at all.

If not on the route MRA keeps guiding to the beginning.

This happens when you do not "hit" the first waypoint. It is a viapoint (hand symbol) and can therefore only be skipped manually. If you plan your own routes, make sure you place the first WP a bit ahead in the direction you want to start. Then you will not miss that point.

Oh, and everyone can use the app how he/she wants, but personally I consider driving around on audio only as very dangerous. There is a visual map in the app for a reason.

I disagree on that.

But overall, MRA is great for creating and storing routes but as a navigation app it's currently not suitable for my needs.

[Con Hennekens]

@Dennis-Hoogendonk said in First experience with MRA as a navigation tool:

This is practically impossible. I wear my cellphone in my jacket.

Then you need to do that before you leave. That's best practice anyway. Buy a mount. NO navigation app at all is intended for being used like you do. Like I said before, the app shows a map for a reason.

as a navigation app it's currently not suitable for my needs.

You need to adjust your needs

[richtea999]

@Con-Hennekens said in First experience with MRA as a navigation tool:

@Dennis-Hoogendonk said in First experience with MRA as a navigation tool:

Current audio setting is #3, so I assume it is the most loudest setting. Also, my cell phone is set loudest possible.

Up the volume while it is talking

I have the same A54 phone, and can confirm the volume is a problem (with app vol=max and handset = max vol).
I also agree that by increasing the volume whilst the app is speaking does help, it's a work-around at best.

If this can't be fixed then the app could offer a feature where it talks some long test text and that will allow you time to increase the volume.

@Dennis-Hoogendonk said in First experience with MRA as a navigation tool:

This is practically impossible. I wear my cellphone in my jacket.

Then you need to do that before you leave. That's best practice anyway. Buy a mount. NO navigation app at all is intended for being used like you do. Like I said before, the app shows a map for a reason.

as a navigation app it's currently not suitable for my needs.

You need to adjust your needs

You need to adjust your tone!

You can't dictate how users must use the app, you can only advise. If users want to use audio only then why not?

It's safer to watch the road then watch a screen if the audio works well. It's how I use Google Maps in a car for 95% of the time.

[Con Hennekens]

@richtea999 said in First experience with MRA as a navigation tool:

I have the same A54 phone, and can confirm the volume is a problem

I am not denying that.

I also agree that by increasing the volume whilst the app is speaking does help, it's a work-around at best.

That is not a workaround, that's how Android volume setting works. And it being in your pocket does not help that. So I think my advice was accurate.

If this can't be fixed then the ap could offer a feature where it talks a sentence or three and allows you to increase the volume.

It does that in the menu where you can select your voice. There is a play button that produces a test sentence.

It also does that by pressing the loudness setting in the app settings. This could be improved though, because it only does that when you change to another setting, not by multiple pressing the same button.

And it also does that when pressing the upcoming instruction tile while navigating. But an instruction must have been spoken before that works I think.

You need to adjust your tone!

I think there was nothing wrong with my tone. Did you miss the smiley?

You can't dictate how users must use the app

No I can't, but I can indicate that no single navigation app is intended to be used this way. Again: they show a map for a reason.

It's how I use Google Maps in a car for 95% of the time.

It's that other 5% where it is dangerous...

[richtea999]

@Con-Hennekens said in First experience with MRA as a navigation tool:

It does that in the menu where you can select your voice. There is a play button that produces a test sentence.

Ah, good point Con. But that's on iOS only, at the moment.
The 'pseudo' test sentence on Android is a bit short: 'Voice instructions are enabled', but you can keep repeating it by tapping the medium and then high volume buttons repeatedly, and that gives you a chance to increase the volume.

A 'Play audio sample' button on Android similar to iOS would be appreciated.

Having experimented with that (on A54) it's still not as loud as Google Maps audio, and both are quieter than music (to my ears).

I will give it another try next time I'm out.

[Con Hennekens]

@richtea999 said in First experience with MRA as a navigation tool:

Ah, good point Con. But that's on iOS only, at the moment.

Not completely true
The current Beta has a choice of voice within the app, also for Android. Each voice has a play button. This will be in the announced public version as well.

Having experimented with that (on A54) it's still not as loud as Google Maps audio, and both are quieter than music (to my ears).

I agree. I use a JustSpeak helmet-set (Caberg) and I max out the volume on BT and on the device itself too. For scenic riding that's completely fine, but for riding highways not so much. The relatively low volume on the voice has been a problem from the get go.

[richtea999]

@Con-Hennekens said in First experience with MRA as a navigation tool:

@richtea999 said in First experience with MRA as a navigation tool:

Ah, good point Con. But that's on iOS only, at the moment.

Not completely true
The current Beta has a choice of voice within the app, also for Android. Each voice has a play button. This will be in the announced public version as well.

The Google TTS Norwegian voices speaking English are very pleasant!

Welsh - almost broken, but not MRA's fault.

[M. Schrijver]

Again a discussion about skipping waypoints. This shows the developers have some work to do.

Manually skipping points should not be necessary. Only real waypoints should be skipped manually.
When start a route. Only one question.

Would you ride to the start of the route or closest point?

Make your choice and from there on it should not be neccesary to touch your phone again. The software should take care of your choices while riding

[Dennis Hoogendonk]

Today I made a test in my car with MRA app. Mainly to verify the advice given about changing volume while getting spoken road instructions.

1. Volume emitted by Samsung A54 smartphone is sufficient in my car.
2. Volume cannot be changed during emitting instructions.
3. Road instructions work well in my car.

So far so good.

But my problem with spoken instructions in my helmet is not solved. This seems to be a completely different technical issue.

[Con Hennekens]

@M-Schrijver said in First experience with MRA as a navigation tool:

Manually skipping points should not be necessary. Only real waypoints should be skipped manually.

That's a rather big contradiction, isn't it?

Would you ride to the start of the route or closest point?

Choosing the waypoint from where you want to drive the route yourself is much more flexible. The closest point is often not where I want to start the route.

from there on it should not be neccesary to touch your phone again.

In almost all cases that's exactly how it happens. My Garmins needed much more user input during a ride than the MRA app...

[M. Schrijver]

@Con-Hennekens said in First experience with MRA as a navigation tool:

@M-Schrijver said in First experience with MRA as a navigation tool:

Manually skipping points should not be necessary. Only real waypoints should be skipped manually.

That's a rather big contradiction, isn't it?

No, In my opnion shaping points should always be skipped automaticly when neccesary (i.e road works). Manual involvement should never be required for shaping points.
For those Hand symbols (waypoints i presume) a manual action is not strange. Because waypoints are chosen for a reason.

Please be aware that user input on Android Auto is very limited compared to the phone interface

Would you ride to the start of the route or closest point?

Choosing the waypoint from where you want to drive the route yourself is much more flexible. The closest point is often not where I want to start the route.

With TomTom Go i make use of one of the two options mentioned before or i drive to my prefered starting point and there i start the route. When starting the route when i'm on the route or in close proximity TomTom Go doesn't ask anything it just start navigating. Very nice.

from there on it should not be neccesary to touch your phone again.

In almost all cases that's exactly how it happens. My Garmins needed much more user input during a ride than the MRA app...

With TomTom Go, i start the route and normally i'm done touching my phone for the rest of the day. TomTom nearly fixes al my problems i create while riding. The rare moments i need to touch my phone is mostly when i 'm on a route deviation and i think TomTom does something wrong but in 95% of these cases TomTom did a good job. So basicly i can trust TomTom. This is a relaxed idea.
My neighbor still use a Garmin and just like your Garmin it needs more user input. This is something i don't miss (i also did drive with Garmins in the past).
I suspect a part of the required user input has something to do with the stability of MRA. Which will be improved over time.

[Con Hennekens]

@M-Schrijver, may I ask what your motivation was to leave TomTom?

[M. Schrijver]

I am always curious about new product and the MyRouteplanner is a good product. So MRA Next could also be this good.

I bought a lifetime membership for the navigation app at the moment is was a real sale.

While TomTom Go is a really good product for me (hard to beaten). It is just route with a start and endpoint. No visible shaping or waypoints in between. When i am on vacation is miss those visible points sometimes. I can't remember all the interessesting things along a route for a whole vacation even not for a whole day.
This is where MRA Next scores some very good points. To hear the text written at a way/shaping point through my headset is a very nice feature

Let be fair.

• MRA Next is still a young product. So stablity is still not what some mature app (like TomTom GO) offers.
• Android Auto is also a very good feature. This feature narrows the choice of apps a lot. There are only a few good apps which can handle routes and Android Auto (Apple Carplay) properly. MRA Next is one of those few apps
• While the smartphone app looks good and seems to work pretty well. Android Auto and Apple Carplay still needs a lot of development. Partially due to the limitations set by Google and Apple, partially because the foundation (the apps itself) needs to be solid to work well in AA and ACP and partially my Android Auto headunit has no touchscreen (Honda Goldwing)

Those limitations set by Google and Apple are a big reason why i'm so on top the auto skipping function.

Once you exeperience a 14-day motorcycle trip where you have only start the route in the morning, after this let the software do it's job. You are gonna appreciate the comfort of not having the need fiddeling with your navigation through the day.

B.T.W
TomTom Go is still my main navigation app.

[Drabslab]

@M-Schrijver said in First experience with MRA as a navigation tool:

a 14-day motorcycle trip where you have only start the route in the morning, after this let the software do it's job. You are gonna appreciate the comfort of not having the need fiddeling with your navigation through the day.

Yep, this should be the target!

Although I love that barbutton idea, we should not need to play with the navigation tool while riding

[Con Hennekens]

@M-Schrijver said in First experience with MRA as a navigation tool:

Once you experience a 14-day motorcycle trip where you have only start the route in the morning, after this let the software do it's job.

Does a 7 day trip count? I did that in september, and basically did what you say: only start the route in the morning. Honesty makes me admit that it was in offline-mode. Concerning online-mode I must say that this young product still has to mature indeed But hey, the 3 Garmins I owned were also offline. The more features it has, the higher the expectations get.